Method and apparatus for supporting data collection and reporting

Abstract

Various aspects of the disclosure relate to methods and apparatuses that support data collection and reporting. An exemplary UE for wireless communication can include at least one memory and at least one processor coupled with the at least one memory and configured to cause the UE to receive a first long term evolution (LTE) positioning protocol (LPP) message that configures the UE to perform data collection and report collected data via LPP messages over a dedicated radio bearer, determine whether to report the collected data via the dedicated radio bearer, and report the collected data via LPP messages over the dedicated radio bearer in response to determining to report the collected data via the dedicated radio bearer.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more specifically, to technologies that support data collection from a remote side, such as methods and apparatus that support data collection and reporting. Background Technology

[0002] A wireless communication system may include one or more network communication devices (e.g., base stations) that support wireless communication for one or more user communication devices, which may otherwise be referred to as user equipment (UE) or other suitable terms. The wireless communication system can 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, etc.)). Furthermore, the wireless communication system can support wireless communication across various radio access technologies, including third-generation (3G), fourth-generation (4G), fifth-generation (5G), and other suitable radio access technologies beyond 5G (e.g., sixth-generation (6G)). Summary of the Invention

[0003] The article “a” preceding an element is unrestricted and is understood to refer to “at least one” or “one or more” of the elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, “or” as used in the claims, such as in a list of items (e.g., a list of items preceded by phrases such as “at least one of…”, “one or more of…”, or “one or both of…”), indicates a list of inclusions, 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 a reference 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 understood in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, a “group” may comprise one or more elements as included in the claims.

[0004] Some embodiments of the methods and apparatus described herein may further include a UE for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory and configured such that the UE: receives a first Long Term Evolution (LTE) Positioning Protocol (LPP) message configuring the UE to perform data collection and report the collected data via a dedicated radio bearer through the LPP message; determines whether to report the collected data via the dedicated radio bearer; and reports the collected data via the dedicated radio bearer through the LPP message in response to determining whether to report the collected data via the dedicated radio bearer.

[0005] In some implementations of the methods and devices described herein, the first LPP message configures the UE to report the collected data periodically, once, or in an event-triggered manner.

[0006] In some embodiments of the methods and apparatus described herein, the dedicated radio bearer is a different radio bearer from signaling radio bearers (SRB)1, SRB2, and SRB3.

[0007] In some implementations of the methods and apparatus described herein, determining whether to report the collected data via the dedicated radio bearer includes: determining whether the dedicated radio bearer is available in response to receiving the first LPP message.

[0008] In some embodiments of the methods and apparatus described herein, the at least one processor is configured to cause the UE to transmit information to the NE indicating a need for a dedicated radio bearer when the dedicated radio bearer is unavailable.

[0009] In some embodiments of the methods and apparatus described herein, the at least one processor is configured to cause the UE to: start a timer to wait for the dedicated radio bearer to be configured if the dedicated radio bearer is unavailable.

[0010] In some embodiments of the methods and apparatus described herein, in response to the expiration of the timer and the configuration that the dedicated radio bearer has not been received, the at least one processor is configured to cause the UE to: transmit a second LPP message to notify that the collected data, as configured by the first LPP message, has failed to be reported.

[0011] In some embodiments of the methods and apparatus described herein, determining whether to report the collected data via the dedicated radio bearer, when the dedicated radio bearer is available, further comprises: determining whether a second LPP message for reporting the collected data has a low priority based on a configured or predefined priority for reporting the collected data; and transmitting the second LPP message via the dedicated radio bearer if the second LPP message has a low priority.

[0012] In some embodiments of the methods and apparatus described herein, the at least one processor is configured such that the UE: transmits the second LPP message via SRB2 or SRB1 when the second LPP message has a high priority.

[0013] In some embodiments of the methods and apparatus described herein, determining whether to report the collected data via the dedicated radio bearer, when the dedicated radio bearer is available, further comprises: determining whether to report the collected data via the dedicated radio bearer through the LPP layer of the UE.

[0014] In some embodiments of the methods and apparatus described herein, in the case that the memory of the UE buffering the collected data is full, performing the reporting of the collected data via the dedicated radio bearer includes: discarding the collected data in the memory in one or more of the following orders: from old data to new data, or from a low-priority data type to a high-priority data type; or switching the dedicated radio bearer used to report the collected data to a different radio bearer that is configured or predefined.

[0015] In some embodiments of the methods and apparatus described herein, when the dedicated radio bearer is unavailable, the at least one processor is configured to cause the UE to: begin collecting data as configured by the first LPP message and buffer the collected data until the dedicated radio bearer becomes available; or begin collecting data as configured by the first LPP message and transmit a report of the collected data via a configured or predefined radio bearer.

[0016] In some embodiments of the methods and apparatus described herein, in response to a handover being initiated, the at least one processor is configured to cause the UE to either discard or retain the collected data that has been delivered to memory and is awaiting transmission and is to be reported.

[0017] In some embodiments of the methods and apparatus described herein, where the dedicated radio bearer configured by the target NE after the handover is completed is available for reporting the collected data, the at least one processor is configured to cause the UE to: retransmit the collected data to the target NE if the buffered collected data to be reported is discarded; or resume reporting the collected data to the target NE if the collected data to be reported is retained.

[0018] Some embodiments of the methods and apparatus described herein may further include a processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured such that the processor: receives a first LPP message configuring the UE to perform data collection and report the collected data via a dedicated radio bearer through the LPP message; determines whether to report the collected data via the dedicated radio bearer; and, in response to determining whether to report the collected data via the dedicated radio bearer, reports the collected data via the dedicated radio bearer through the LPP message.

[0019] Some embodiments of the methods and apparatus described herein may further include a network equipment (NE) for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory and configured such that the NE: receives information indicating the need for a dedicated radio bearer associated with a UE, wherein the UE is expected to report collected data via LPP messages through the dedicated radio bearer; determines whether to configure the dedicated radio bearer; and is configured to transmit the dedicated radio bearer to the UE in response to the determination to configure the dedicated radio bearer.

[0020] In some embodiments of the methods and apparatus described herein, the information indicating the need for a dedicated radio bearer is information indicating the need for a dedicated radio bearer for LPP message transmission, or information indicating that the collected data is expected to be reported via LPP messages with relaxed latency requirements.

[0021] In some implementations of the methods and apparatus described herein, the information indicating the need for a dedicated radio bearer is carried in a New Radio Positioning Protocol A (NRPPa) message.

[0022] In some embodiments of the methods and apparatus described herein, the at least one processor is further configured such that the NE: receives UE identifier (ID) information of only the UE or a group of UEs including the UE.

[0023] In some embodiments of the methods and apparatus described herein, the at least one processor is configured to cause the NE to: transmit a response to the information indicating the need for a dedicated radio bearer via another NRPPa message to indicate whether the dedicated radio bearer is configured.

[0024] In some embodiments of the methods and apparatus described herein, the at least one processor is further configured such that the NE: receives a first LPP message that configures the UE to perform data collection and report the collected data via the LPP message.

[0025] In some embodiments of the methods and apparatus described herein, in response to determining the configuration of the dedicated radio bearer, the at least one processor is configured such that the NE: configures the dedicated radio bearer based on configured or predefined Quality of Service (QoS) requirements for data collected via LPP message reporting.

[0026] In some implementations of the methods and apparatus described herein, the information indicating the need for a dedicated radio bearer is received from the UE.

[0027] In some embodiments of the methods and apparatus described herein, the NE is the source NE of the UE in handover, and the at least one processor is configured to cause the NE to: transmit information to the target NE indicating the need for the dedicated radio bearer associated with the UE.

[0028] In some embodiments of the methods and apparatus described herein, the NE is a target NE of the UE in handover, and the at least one processor is configured such that the NE: receives from the source NE the information indicating the need for a dedicated radio bearer associated with the UE.

[0029] Some embodiments of the methods and apparatus described herein may further include a location management function (LMF) for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to cause the NE to: transmit LPP messages configuring the UE to perform data collection and report the collected data via dedicated radio bearers through LPP messages; and receive information from the UE via the dedicated radio bearers or another radio bearer related to the data collection via LPP messages.

[0030] In some embodiments of the methods and apparatus described herein, the at least one processor is configured to cause the LMF to: transmit information indicating the need for the dedicated radio bearer via an NRPPa message; and transmit the first LPP message after receiving a response indicating that the dedicated radio bearer has been configured or will be configured.

[0031] In some embodiments of the methods and apparatus described herein, the at least one processor is configured to cause the LMF to transmit information indicating the need for the dedicated radio bearer and the first LPP message toward the Access and Mobility Management Function (AMF). Attached Figure Description

[0032] Figure 1 Examples of wireless communication systems according to aspects of this disclosure are described.

[0033] Figure 2 This document describes an example of a data collection and reporting procedure under scheme 1, based on aspects of this disclosure.

[0034] Figure 3 This describes another example of a data collection and reporting procedure under scheme 1, based on aspects of this disclosure.

[0035] Figure 4 This document describes an example of a data collection and reporting procedure under scheme 2, based on aspects of this disclosure.

[0036] Figure 5 Examples of data collection and reporting procedures during the handover period are provided in accordance with aspects of this disclosure.

[0037] Figure 6 Examples of UEs based on aspects of this disclosure are described.

[0038] Figure 7 Examples of processors according to aspects of this disclosure are described.

[0039] Figure 8 Examples of NEs based on aspects of this disclosure are described.

[0040] Figure 9 Examples of LMFs based on aspects of this disclosure are described.

[0041] Figure 10 A flowchart illustrating a method performed by a UE according to aspects of this disclosure.

[0042] Figure 11 A flowchart illustrating the method performed by NE according to aspects of this disclosure.

[0043] Figure 12 A flowchart illustrating the method performed by NE according to aspects of this disclosure. Detailed Implementation

[0044] AI, which incorporates at least machine learning (ML), is used to learn and perform certain tasks by training neural networks (NNs) with large amounts of data. AI has been successfully applied in computer vision (CV) and natural language processing (NLP). Deep learning, a sub-concept of ML, utilizes multi-layered NNs as "AI models" to learn how to solve problems and / or optimize performance from large amounts of data. If the AI ​​model used for AI-based methods is well-trained, then AI-based methods can achieve better performance than traditional methods. Therefore, since 2016, the 3rd Generation Partnership Project (3GPP) has been considering introducing AI into 3GPP, for example, for UE positioning in wireless communications, also known as AI / ML-based positioning.

[0045] Regarding AI / ML-based positioning, it includes direct AI / ML positioning and AI / ML-assisted positioning. For direct AI / ML positioning, there are two LMF-side model cases, such as Case 2b and 3b. Case 2b involves UE-assisted / LMF-based positioning using an LMF-side model, direct AI / ML positioning. Case 3b involves next-generation (NG) radio access network (RAN) node-assisted positioning using an LMF-side model, direct AI / ML positioning. According to 3GPP Release (Rel) 19 AI of the Air Interface Work Item (WI), it will support the use of AI models operating at the LMF side using inputs (e.g., measurement or auxiliary information) collected from the UE or gNB side to determine the UE's location.

[0046] For example, to train an LMF-side model, the LMF can initiate an LPP session with the UE and configure the UE to measure and transmit the required training data via LPP messages. In older 3GPP specifications, both uplink and downlink LPP messages containing measurements and / or estimation results for a single location estimation are transmitted as Non-Access Plane (NAS) messages. These NAS messages are carried within UL / DL Radio Resource Control (RRC) messages (e.g., UL / DL Information Transmission messages) transmitted via SRB2 or SRB1. These LPP messages may be associated with exemplary procedures such as LPP Capability Exchange, LPP Auxiliary Data Exchange, or LPP Location Information Exchange. However, training data may have more relaxed latency requirements compared to these older LPP message transmissions. Therefore, training data may not require high-priority radio bearers, such as SRB2 or SRB1. Using appropriately prioritized radio bearers for transmitting training data via LPP messages will improve network throughput and capacity compared to older solutions.

[0047] While the above issues are illustrated in light of training data collection via LPP messages, the LMF may require the UE to report other collected data via LPP messages. Similarly, in some other scenarios, considering network throughput and capacity, LPP messages used to carry collected data other than training data may not require SRB2 or SRB1 as in older LPP message transmissions.

[0048] Therefore, various aspects of this disclosure propose the use of dedicated radio bearers for data collection and reporting via LPP messages. The dedicated radio bearer is a different radio bearer from SRB1, SRB2, and SRB3 and has a lower priority than SRB1, SRB2, and SRB3. Exemplary dedicated radio bearers may be SRB4 or SRB5, or new SRBs (e.g., SRB6), or data radio bearers (DRBs), etc., which can be configured by an NE (e.g., gNB).

[0049] For example, according to aspects of this disclosure, an LMF or similar device can configure a UE (which may be a Location Reference Unit (PRU) in some scenarios) to perform data collection and report the collected data via dedicated radio bearer through LPP messages, for example, periodically or once (also known as on-demand) or event-triggered. Data collection and reporting configuration information configured by the LMF can be transmitted via LPP messages. The collected data can be used by the LMF for AI / ML operations, such as training, updating, and / or monitoring of AI / ML models with relaxed latency requirements. Exemplary data to be collected and reported may include measurement results, tag types, ancillary information, or any combination thereof (e.g., a combination of measurement results and tag types, or a combination of measurement results, tag types, and ancillary information, etc.). Exemplary measurement results may include: Channel impulse response (CIR) based on uplink (UL) or downlink (DL), power delay characteristics (PDP) based on UL or DL, and delay characteristics (DP) based on UL or DL; or include: DL positioning reference signal (PRS) received power (RSRP), DL-PRS received path power (RSRPP), UL sounding reference signal (SRS) RSRP or UL SRS RSRPP, DL reference signal time difference (RSTD), DL UE receive (Rx)-transmit (Tx) time difference, DL gNB Rx-Tx time difference, UL relative time of arrival (RTOA) or UL angle of arrival (AOA), or DL-AoD or SS / PBCH block (SSB) RSRP, channel state information (CSI)-reference signal (RS) RSRP, DL received signal code power (RSCP), DL reference signal carrier phase difference (RSCPD), and UL RSCP. Exemplary tag types may include: location coordinates; time series estimates; line-of-sight (LOS) or non-line-of-sight (NLOS) indicators, including soft indicators for LOS / NLOS probabilities, such as [0, 0.1, 0.2, …1] and / or hard indicators for binary Boolean LOS or NLOS, such as [True (LOS), False (NLOS)]. Exemplary auxiliary information may include: timestamps, measurement or tag quality indicators, and reference signal (RS) configurations, etc.

[0050] Upon receiving the data collection and reporting configuration information in the LPP message, the UE will perform data collection and determine whether to report the collected data via a dedicated radio bearer. For example, the UE may determine whether a dedicated radio bearer is available. If a dedicated radio bearer is available and another data report exists via the dedicated radio bearer, the UE may further determine whether to report the collected data via the dedicated radio bearer based on a configured or predefined priority for reporting the collected data. Only if it is determined that the collected data will be reported via the dedicated radio bearer will the UE report the collected data via the dedicated radio bearer through the LPP message. Otherwise, the UE may transmit the collected data via another radio bearer (e.g., via SRB2 or SRB1 as a legacy solution) via the LPP message, or transmit data collection-related information to the LMF (also via another radio bearer) without transmitting the collected data, thereby indicating a failure to report the collected data via the dedicated radio bearer.

[0051] Considering that the dedicated radio bearer required for data collection via LPP message reporting will be configured by the NE (e.g., gNB), two schemes are proposed to ensure that the NE (e.g., gNB) is aware of the need for a dedicated radio bearer. One scheme is that the LMF indicates to the NE that a dedicated DRB is needed for data collection via LPP message reporting (Scheme 1); and the other is that the UE indicates to the gNB that a dedicated DRB is needed for data collection via LPP message reporting (Scheme 2). Therefore, for a UE that expects to collect data via LPP message reporting via a dedicated radio bearer, the gNB can receive information from the LMF or the UE indicating the need for a dedicated radio bearer associated with the UE. The gNB can determine whether to configure the required dedicated radio bearer, for example, based on configured or predefined QoS requirements for data collection via LPP message reporting. If the gNB determines that a dedicated radio bearer needs to be configured, the gNB will transmit the configuration of the dedicated radio bearer to the UE.

[0052] Aspects of this disclosure are described in the context of wireless communication systems.

[0053] Figure 1This section describes an example of a wireless communication system 100 according to aspects of this disclosure. The wireless communication system 100 may include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some embodiments, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-A network. In some other embodiments, the wireless communication system 100 may be an NR network, such as a 5G network, a 5G-A network, or a 5G Ultra Wideband (5G-UWB) network. In other embodiments, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G, such as 6G. In addition, the wireless communication system 100 can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0054] One or more NEs 102 may be distributed throughout a geographic area to form a wireless communication system 100. One or more of the NEs 102 described herein may be, include, or be referred to as a network node, base station, network element, network function, network entity, radio access network (RAN), NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. NEs 102 and UEs 104 may communicate via a communication link, which may be wireless or wired. For example, NEs 102 and UEs 104 may perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface.

[0055] NE 102 can provide a geographic coverage area for which NE 102 can support services for one or more UEs 104 within the geographic coverage area. For example, NE 102 and UE 104 can support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcasting, etc.) according to one or more radio access technologies. In some embodiments, UE 102 can be mobile, such as a satellite associated with a non-terrestrial network (NTN). In some embodiments, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, but different geographic coverage areas can be associated with different NEs 102.

[0056] 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 remote unit, mobile device, wireless device, remote device, subscriber device, transmitter device, receiver device, or some other suitable term. In some embodiments, UE 104 may be referred to as a unit, station, terminal, or client, and other instances thereof. 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, and other instances thereof.

[0057] UE 104 may be able to support direct wireless communication with other UE 104 via a communication link. For example, UE 104 may 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, the communication link 114 may be referred to as a side link. For example, UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.

[0058] NE 102 may support communication with CN 106, or with another NE 102, or both. For example, NE 102 may interface with other NE 102 or CN 106 via one or more backhaul links (e.g., S1, N2, N2, or network interfaces). In some embodiments, NE 102 may communicate directly with each other. In some other embodiments, NE 102 may communicate with each other or indirectly (e.g., via CN 106). In some embodiments, one or more NE 102 may include sub-components, such as access network entities, which may be instances of access node controllers (ANCs). The ANC may communicate with one or more UE 104s via one or more other access network transmitting entities (which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs)).

[0059] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities (e.g., Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) that manage access and mobility, and user plane entities (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) that route packets or interconnect to external networks. In some implementations, the control plane entities may manage non-access plane (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) of one or more UEs 104 served by one or more NEs 102 associated with CN106.

[0060] CN 106 can communicate with the packet data network via one or more backhaul links (e.g., via S1, N2, N2, or another network interface). The packet data network may contain an application server. In some implementations, one or more UEs 104 can communicate with the application server. UE 104 can establish a session (e.g., a Protocol Data Unit (PDU) session or the like) with CN 106 via NE 102. CN 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, and the like) between UE 104 and the application server. A PDU session may be an instance of a logical connection between UE 104 and CN 106 (e.g., one or more network functions of CN 106).

[0061] In the wireless communication system 100, NE 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, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some embodiments, NE 102 and UE 104 may support different resource structures. For example, NE 102 and UE 104 may support different frame structures. In some embodiments, such as in 4G, NE 102 and UE 104 may support a single frame structure. In some other embodiments, such as in 5G and in other suitable radio access technologies, NE 102 and UE 104 may support various frame structures (i.e., multiple frame structures). NE 102 and UE 104 may support various frame structures based on one or more parameter sets.

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

[0063] Time intervals for organizing resources (e.g., communication resources) can be based on frames (also known as radio frames). Each frame may have a duration, such as 10 milliseconds (ms). In some embodiments, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, and each subframe may have a duration, such as 1 ms. In some embodiments, each frame may have the same duration. In some embodiments, each subframe of a frame may have the same duration.

[0064] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may contain a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth parameter sets (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single 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, respectively. Each time slot may contain a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some embodiments, the number (e.g., quantity) of time slots in a subframe may depend on the parameter set. For a conventional cyclic prefix, a time slot may contain 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier spacing), a time slot may contain 12 symbols. The relationship between the number of symbols per time slot for the regular cyclic prefix and the extended cyclic prefix, and the relationship between the number of time slots per subframe and the number of time slots per frame, may depend on the parameter set. It should be understood that references to the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) can be used interchangeably between subframes and time slots.

[0065] 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 may support one or more operating frequency bands, such as frequency range names FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some embodiments, NE 102 and UE 104 can perform wireless communication through one or more of the operating frequency bands. In some embodiments, FR1 can be used by NE 102 and UE 104, as well as other equipment or devices, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by NE 102 and UE 104, as well as other equipment or devices, for short-range, high data rate capabilities.

[0066] FR1 may be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 may be associated with a first parameter set containing a 15 kHz subcarrier spacing (e.g., μ=0); a second parameter set containing a 30 kHz subcarrier spacing (e.g., μ=1); and a third parameter set containing a 60 kHz subcarrier spacing (e.g., μ=2). FR2 may be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 may be associated with a third parameter set (e.g., μ=2) containing a 60 kHz subcarrier spacing; and a fourth parameter set (e.g., μ=3) containing a 120 kHz subcarrier spacing.

[0067] Figure 2 This document describes an example of a data collection and reporting procedure under scheme 1, based on aspects of this disclosure.

[0068] refer to Figure 2 In some embodiments of this disclosure (Symbol 1-1), before or during configuring the UE to perform data collection and reporting via LPP messages (which are expected to be transmitted via a dedicated radio bearer) (or via LPP messages or the like) (hereinafter, for simplicity, also referred to as LPP data collection and reporting or the like), the LMF may, for example, notify the gNB in ​​step 201 via an NRPPa message that a dedicated radio bearer is needed for LPP data collection and reporting. In step 201a, the information indicating the need for a dedicated radio bearer will first be transmitted from the LMF to the AMF, and then in step 201b, it will be transmitted by the AMF to the gNB.

[0069] According to TR38.843, for location applications, when considering LMF-side inference, it is assumed that the LPP protocol should be applied to data collected by the UE and terminate at the LMF, while the NRPPa protocol should be applied to data collected by the gNB and terminate at the LMF. For LMF-side performance monitoring, it is assumed that the LPP protocol should be applied to data collected by the UE and terminate at the LMF, while the NRPPa protocol should be applied to data collected by the gNB and terminate at the LMF. Therefore, in this paper, communication via or through LPP messages also implies communication between the UE and the LMF (which can be forwarded via the gNB and / or AMF, etc.), and communication via NRPPa messages also implies communication between the gNB and the LMF (which can be forwarded via the AMF, etc.).

[0070] LMF can request a dedicated radio bearer for one or more UEs via an NRPPa message (or in an NRPPa procedure).

[0071] For example, for a single UE, the LMF can generate a UE-associated NRPPa message containing information indicating the need for a dedicated radio bearer. The UE-associated NRPPa message can be an older NRPPa message, such as an NRPPa location information request message, or a newer NRPPa message (compared to an older NRPPa message). The NRPPa message is then included in a message sent from the LMF to the AMF (e.g., Namf_Communication_N1N2MessageTransfer) as an NRPPa PDU with UE ID information (e.g., the UE's Subscription Permanent Identifier (SUPI)). The AMF will forward the received NRPPa PDU, etc., to the UE's serving gNB, for example, in a Next Generation Application Protocol (NGAP) message (e.g., NGAP DL UE-associated NRPPa delivery) containing the NRPPa PDU and associated UE ID information (e.g., the UE NGAP ID corresponding to the SUPI).

[0072] In a single NRPPa procedure requesting dedicated radio bearer configuration for multiple UEs, the LMF may generate a non-UE-associated NRPPa message containing information indicating the need for a dedicated radio bearer and a set of UE ID information (e.g., a list of SUPIs). Similarly, the non-UE-associated NRPPa message may be an older NRPPa message or a newer NRPPa message (compared to an older NRPPa message). This non-UE-associated NRPPa message is then included as an NRPPa PDU with the ID information of the aforementioned set of UEs in a message sent from the LMF to the AMF (e.g., Namf_Communication_NonUeN2MessageTransfer). The AMF forwards the received NRPPa PDUs, etc., to the serving gNBs of those UEs in an NGAP message (e.g., NGAP DL Non-UE-Associated NRPPa Delivery).

[0073] The information (or indicator) indicating the need for a dedicated radio bearer can take various forms. For example, in some embodiments of this disclosure, the information may indicate a dedicated radio bearer needed for LPP data transmission (e.g., for those LPP data transmissions with lenient latency requirements) as a general indicator. In some embodiments of this disclosure, the information may indicate that LPP data collection will be triggered (e.g., those LPP data collections with lenient latency requirements), or that the collected data (e.g., which has lenient latency requirements) is expected to be reported via LPP messages, etc. In some embodiments of this disclosure, the need for a dedicated radio bearer may be indicated by other information elements (IEs) associated with the data collection configuration.

[0074] The LMF can also configure QoS requirements for LPP data collection and reporting, and, for example, transmit QoS requirement-related information to the gNB in ​​the same NRPPa message. Examples of QoS requirement-related information may include QoS-related information, which allows the gNB to configure dedicated radio bearers accordingly. In some cases, QoS requirements for LPP data reporting are specified (or predefined) by a default configuration. The gNB can configure the radio bearer according to the default configuration specified in the 3GPP specification. For example, the default configuration of a radio bearer may include the radio link control (RLC) mode of the radio bearer and the value of a timer (e.g., a Packet Data Convergence Protocol (PDCP) drop timer). Therefore, in these cases, exemplary information related to QoS requirements may include latency-related or reliability-related information, or both, which allows the gNB to configure the RLC mode or timer (e.g., a PDCP drop timer) of the radio bearer, for example, based on predefined QoS requirements.

[0075] Upon receiving information indicating the need for a dedicated radio bearer, the gNB may determine in step 203 whether to configure the dedicated radio bearer. If the gNB determines to configure the dedicated radio bearer (which may be based on configured or predefined QoS requirements as described above), the gNB will configure the dedicated radio bearer for the UE (an individual UE in the group of UEs or each UE) in step 205, for example, via an air interface through an RRC reconfiguration procedure or similar. For example, if the information indicating the need for a dedicated radio bearer relates to an individual UE, the gNB may determine to configure the UE with a dedicated radio bearer, for example, for LPP data collection and reporting (e.g., with lenient latency requirements). If the information indicating the need for a dedicated radio bearer is for a group of UEs, the gNB may determine to configure each UE with a dedicated radio bearer, for example, for LPP data collection and reporting (e.g., with lenient latency requirements). However, in some cases, the gNB may refuse to configure the required dedicated radio bearer, for example, due to a lack of radio resources.

[0076] In step 207, the gNB may respond to the received NRPPa message by replying to the LMF with information (or an indicator), such as "acknowledgment" or "unacknowledgment," via another NRPPa message, indicating whether, for example, a dedicated radio bearer has been configured for the UE (or the group of UEs) (or, the success or failure of the dedicated radio bearer configuration). For example, if the information indicating the need for a dedicated radio bearer is related to a single UE, the NRPPa message carrying the response may be transmitted as an NRPPa PDU, for example, from the gNB to the AMF via an NGAP UL UE-associated NRPPa delivery message in step 207a, and from the AMF to the LMF via a Namf_Communication_N2InfoNotify message in step 207b. When the information indicating the need for a dedicated radio bearer is associated with a group of UEs, the NRPPa message carrying the response can be transmitted as an NRPPa PDU, for example, from the gNB to the AMF via an NGAP UL non-UE associated NRPPa delivery message in step 207a, and from the AMF to the LMF via a Namf_Communication_NoeUeN2InfoNotify message in step 207b.

[0077] In some embodiments of this disclosure, it can be predefined that the gNB may transmit only a message indicating that a dedicated radio bearer is not configured (or has failed), or only a message indicating that a dedicated radio bearer is configured (or has succeeded). The LMF may also determine whether to configure a dedicated radio bearer based on predefined rules.

[0078] When configuring a dedicated radio bearer for the UE, for example, upon receiving an "acknowledgment" (or the LMF assuming a dedicated radio bearer is configured), the LMF will initiate or start an LPP procedure (e.g., a location information transfer procedure) in step 209 and send an LPP message (e.g., a RequestLocationInformation) to configure the UE to perform data collection and report the collected data via the configured dedicated radio bearer through LPP messages. For example, in step 209a, the LMF may transmit an LPP message (or as a PDU) containing the configuration for LPP data collection and reporting via the dedicated radio bearer to the AMF in a message (e.g., Namf_Communication_N1N2MessageTransfer), and then, in step 209b, the AMF forwards the LPP PDU containing the configuration for LPP data collection and reporting via the dedicated radio bearer to the gNB in ​​a message (e.g., NGAPNAS Transport), and then, in step 209c, the gNB forwards the LPP PDU containing the configuration for LPP data collection and reporting via the dedicated radio bearer to the UE in a message (e.g., RRC DL Information Transfer).

[0079] In cases where information related to data collection indicates that a dedicated radio bearer is not configured for the UE, for example, receiving an "unacknowledged" message (or the LMF assuming no dedicated radio bearer is configured), in some embodiments of this disclosure, the LMF may not configure any LPP data collection and reporting for the UE. In other embodiments of this disclosure, the LMF may configure LPP data collection and reporting via a legacy procedure that uses NAS-based signaling via SRB2 or SRB1 to request and receive collected data from the UE.

[0080] In some embodiments of this disclosure, the LMF may transmit a configuration for LPP data collection and reporting to the UE before or during the transmission of information to the gNB indicating the need for a dedicated radio bearer, but without activating the configuration. Upon receiving an "acknowledgment" (or the LMF assuming a dedicated radio bearer is configured) from the gNB, the LMF will send an "activate" message to the UE to activate the configuration, causing the UE to initiate or start the LPP data collection and reporting procedure. Otherwise, the LMF will not activate the configuration.

[0081] On the UE side, upon receiving an LPP message that configures the UE to perform data collection and reports the collected data (and, if necessary, an "activation message") via a dedicated radio bearer through an LPP message, in step 211, taking into account the availability of the dedicated radio bearer, the UE may determine how to record and report the requested data (e.g., measurement results), for example, through the LPP layer.

[0082] Although a dedicated radio bearer is available at the UE when receiving LPP messages for configuring LPP data collection and reporting under Scheme 1-1, the UE can further determine whether an LPP message for reporting collected data has a lower priority (or importance) than other LPP messages based on a configured or predefined priority for reporting collected data. For example, an LPP message for reporting collected data with lenient latency requirements may be considered to have low priority, and the UE can transmit it via a dedicated radio bearer. Otherwise, the UE can transmit the LPP message for reporting collected data via SRB2 or SRB1 as specified in the legacy 3GPP specification.

[0083] In some embodiments of this disclosure, the relevant priority of LPP messages can be configured by the LMF. For example, in an LPP message from the LMF configuring LPP data collection and reporting (e.g., a RequestLocationInformation message), the IE can be used to indicate the priority level (or importance level) of the corresponding LPP message used to transmit LLP data reports (e.g., a ProvideLocationInformation message corresponding to the RequestLocationInformation message). In some embodiments of this disclosure, the relevant priority or importance of LPP messages used to report collected data can be specified or predefined in 3GPP standards or specifications. For example, an LPP message from the UE to the LMF containing data for offline AI / ML training (e.g., measurement results) is considered to have a lower priority than other LPP messages (e.g., LPP messages used for capability exchange, auxiliary data exchange, location information exchange).

[0084] Figure 3 This describes another example of a data collection and reporting procedure under scheme 1, based on aspects of this disclosure.

[0085] refer to Figure 3In some embodiments of this disclosure (Sessions 1-2), the LMF may transmit information indicating the need for a dedicated radio bearer to the gNB during the LPP procedure. For example, when the LMF initiates the LPP procedure and sends an LPP message to configure the UE to perform data collection and report the collected data via the LPP message, the LPP message is expected to be transmitted via a dedicated radio bearer. In step 301, the LMF may include an LPP message configuring LPP data collection and reporting via a dedicated radio bearer in a message transmitted from the LMF to the AMF. The LPP message configuring the UE to perform LPP data collection and reporting, along with the information indicating the need for a dedicated radio bearer, will first be transmitted from the LMF to the AMF in step 301a, then from the AMF to the gNB in ​​step 301b, and then from the gNB to the UE in step 301c. In step 301, the LMF may include the information indicating the need for a dedicated radio bearer in the same message from the LMF to the AMF.

[0086] For example, in some embodiments of this disclosure, the LMF may generate an LPP message (e.g., RequestLocationInformation) to configure the UE to perform data collection and reporting via LPP. The LPP message may be further included as an LPP PDU in a message from the LMF to the AMF (e.g., Namf_Communication_N1N2MessageTransfer). In the same message from the LMF to the AMF that transmits the LPP message configuring the UE to perform LPP data collection and reporting as an LPP PDU (e.g., Namf_Communication_N1N2MessageTransfer), the LMF may also include information indicating the need for a dedicated radio bearer, which may be in various ways as described in embodiments 1-1 and is used to indicate that the transmitted LPP message or PDU is associated with an LPP procedure expected to be transmitted via the dedicated radio bearer through the air interface. Similarly, the LMF may also transmit information related to QoS requirements associated with the required dedicated radio bearer to the gNB, for example, in the same message from the LMF to the AMF that transmits the LPP message as an LPP PDU (e.g., Namf_Communication_N1N2MessageTransfer). The AMF will then forward the LPP message, along with information indicating the need for a dedicated radio bearer and QoS requirements (if provided), to the gNB via NGAP procedures or messages (e.g., via NGAP DL NAS).

[0087] After receiving a message (e.g., NGAP DL NAS Transport) from the AMF, the gNB will deliver or forward an LPP message to the UE configuring the UE to perform LPP data collection and reporting. For received information indicating the need for a dedicated radio bearer and QoS requirement information (if provided), the gNB may determine in step 303 whether to configure the dedicated radio bearer, similar to step 203 described above, and therefore will repeat the process.

[0088] If the gNB determines that a dedicated radio bearer needs to be configured, the gNB may configure the dedicated radio bearer for the UE in step 305, for example, via an air interface through an RRC reconfiguration procedure or similar. However, in some cases, the gNB may refuse to configure the required dedicated radio bearer, for example, due to a lack of radio resources.

[0089] On the UE side, after receiving an LPP message configuring the UE to perform LPP data collection expected to be reported via a dedicated radio bearer, the UE can determine how to record and report the requested data (e.g., measurement results), for example, through the LPP layer, considering the availability of the dedicated radio bearer. For example, in step 307, the UE can first check whether the dedicated radio bearer is available (or configured by the gNB). If the dedicated radio bearer is unavailable (or not configured by the gNB), then the UE can start a timer and wait for the gNB to configure the dedicated radio bearer, for example, as expected in step 305.

[0090] The timer and its value can be configured by the gNB and run at the RRC layer, or configured by the LPP layer and run at the LPP layer. The UE can start the timer in response to receiving an LPP message configuring LPP data collection and reporting (which is expected to be transmitted via a dedicated radio bearer) that is unavailable or not configured at the UE, for example, as determined in step 307.

[0091] In step 309, the UE may further determine whether the collected data is reported via an LPP message through a dedicated radio bearer as configured, and in step 311, transmit information related to data collection to the LMF. This information may be an LPP data report via a dedicated radio bearer, or an LPP message report via another radio bearer (non-dedicated radio bearer), or information indicating the start of an LPP data report via a dedicated radio bearer, or information indicating the failure or cessation of an LPP data report via a dedicated radio bearer, etc. For example, the UE may generate an LPP message or PDU containing information related to data collection, which is included in a message from the UE to the gNB (e.g., RRC UL information transmission) in step 311a, and then the LPP message or PDU is included in a message from the gNB to the AMF (e.g., NGAP UL NAS Transport) in step 311b, and then forwarded by the AMF to the LMF in a message such as Namf Communication_N1MessageNotify in step 331c.

[0092] For example, if the dedicated radio bearer is already available at the UE in step 307 (e.g., the gNB has configured the dedicated radio bearer in advance for other reasons) or if the dedicated radio bearer is configured at the UE in step 305 before the timer expires, the UE may further determine whether to perform LPP data reporting via the dedicated radio bearer based on priority, etc., as described in scheme 1-1, and therefore will not be repeated.

[0093] If the dedicated radio bearer is not configured until the timer expires (or the UE determines that the dedicated radio bearer will not be configured by the gNB in ​​any other way), that is, even after the timer expires, the dedicated radio bearer is not available at the UE, the UE will assume that no LPP data reporting will occur via the dedicated radio bearer.

[0094] According to some aspects of this disclosure, the UE cannot perform measurements for data collection due to the unavailability of a dedicated radio bearer. In other words, the UE will only begin performing measurements for data collection if the dedicated radio bearer is available. The UE may generate an LPP message containing information related to LPP data collection and transmit an LPP message to notify the LMF of configured LPP data collection and reporting failure, for example, via an explicit indicator IE or a cause value. Exemplary LPP messages carrying information indicating failure of configured LPP data collection and reporting may be LPP ProvideLocationInformation messages, error messages, or abort messages. The indicator IE or cause value may indicate that the failure is due to the absence of a dedicated radio bearer or other reasons.

[0095] According to some other aspects of this disclosure, even when a dedicated radio bearer is unavailable, the UE can begin performing data collection as configured (e.g., performing measurements and recording measurement results), for example, when it is determined in step 307 or step 309 that no dedicated radio bearer is available (e.g., a timer expires). Various schemes exist for the UE to further process the collected data.

[0096] For example, in some embodiments of this disclosure, the UE may buffer LPP data reports in its memory until a dedicated radio bearer becomes available at the UE. If the UE memory is full, the UE may discard the collected data in memory in the following order: from older data to newer data, or from lower priority (or importance) data types to higher priority data types, or both. Exemplary data types may be measurement types, such as PRS measurements or SSB measurements, or measurements of a specific cell. The priority (or importance) of data types may be configured by the LMF. In some cases, if the UE memory is full, the UE may switch to another radio bearer (a backup radio bearer, such as SRB2, SRB1, or SRB3) for transmitting buffered LPP data reports. Whether a backup radio bearer is used to transmit buffered LPP data reports and which backup radio bearer is used for transmitting buffered LPP data reports may be configured by the gNB or specified (or predefined) in 3GPP standards or specifications.

[0097] In some embodiments of this disclosure, the UE may not buffer the LPP data report for the collected data, but instead transmit the LPP data report directly via another configured or predefined radio bearer (e.g., SRB2 or SRB1).

[0098] According to some other aspects of this disclosure, when it is determined in step 307 that no dedicated radio bearer is available, the UE may also begin performing data collection as configured (e.g., performing measurements and recording measurement results). The UE may also start a timer and wait for the gNB to configure the dedicated radio bearer. If the UE determines that an LPP data collection report will not occur, for example, if no dedicated radio bearer configuration is received before the timer expires, or if the UE determines that the dedicated radio bearer will not be configured by the gNB, then the UE will stop any ongoing data collection (e.g., measurements). The UE may discard all collected data. Similarly, the UE may generate an LPP message to notify the LMF of the failure to configure LPP data collection and report, for example, via an explicit indicator IE or a cause value.

[0099] Figure 4 This document describes an example of a data collection and reporting procedure under scheme 2, based on aspects of this disclosure.

[0100] refer to Figure 4 Scheme 2 is similar to Schemes 1-2. The main difference between them is that in Scheme 2, the LMF will not transmit information to the gNB indicating the need for a dedicated radio bearer. Instead, if the UE determines that there is no available dedicated radio bearer for configured LPP data collection and reporting that is expected to be transmitted via a dedicated radio bearer, then the UE will transmit information to the gNB indicating the need for a dedicated radio bearer.

[0101] For example, in step 401, the LMF may initiate an LPP procedure and send an LPP message to configure the UE to perform data collection and report the collected data via the LPP message. The LPP message configuring the UE to perform LPP data collection and reporting will first be transmitted from the LMF to the AMF in step 401a, then from the AMF to the gNB in ​​step 401b, and then from the gNB to the UE in step 401c.

[0102] After the UE receives an LPP message configuring the UE to perform LPP data collection that is expected to be reported via a dedicated radio bearer, the UE can determine whether to report the collected data via the LPP message through the configured dedicated radio bearer, for example, through the LPP layer. For example, in step 403, the UE will first check whether the dedicated radio bearer is available (or configured by the gNB). If the dedicated radio bearer is unavailable, the UE can indicate to the gNB, for example via an RRC UEAssistanceInformation message in step 404, that a dedicated radio bearer is required. The UE can also include information related to the QoS requirements for the configured LPP data collection and reporting in the same message, similar to the information described in schemes 1-1 and 1-2. Similarly, the UE can also start a timer and wait for the gNB to configure the dedicated radio bearer.

[0103] For information received from the UE indicating the need for a dedicated radio bearer, the gNB may determine in step 405, for example, based on configured or predefined QoS requirements, whether to configure a dedicated radio bearer, which is similar to step 203 above and will therefore be repeated.

[0104] In step 409, the UE may further determine whether to report the collected data via an LPP message through a dedicated radio bearer as configured, and in step 411 transmit information related to data collection to the LMF. For example, the UE may generate an LPP message or PDU containing information related to data collection, which is included, for example, in a message transmitted from the UE to the gNB in ​​step 411a, and then the LPP message or PDU is included, for example, in a message transmitted from the gNB to the AMF in step 411b, and then forwarded by the AMF to the LMF in step 411c, for example, in a message called Namf Communication_N1MessageNotify. More detailed operations within the UE are similar to those described in respect of schemes 1-2, and therefore will not be repeated.

[0105] Furthermore, regarding LPP data collection and reporting within the UE, as explained above, the UE LPP layer can determine whether a UL LPP message will be transmitted via a dedicated radio bearer. In some embodiments of this disclosure, the UE LPP layer can directly deliver UL LPP messages to the corresponding radio bearer. In some embodiments of this disclosure, the UE LPP layer can deliver UL LPP messages as NAS PDUs to the RRC layer and indicate to the UE RRC layer whether the NAS PDU will be transmitted via a dedicated radio bearer.

[0106] When the UE initiates LPP data collection and reporting via a dedicated radio bearer, the UE may have to prioritize other transmissions and maintain buffered LPP data reports in its memory because the dedicated radio bearer has a lower priority than SRB1, SRB2, and SRB3. If the UE memory is full, the UE may discard LPP data reports in memory in the following order: from old data to new data, or from low-priority (or importance) data types to high-priority data types, or both; this is similar to those described in Schemes 1-2, where the memory is full when the dedicated radio bearer is unavailable. Similarly, the UE may switch to another radio bearer (a backup radio bearer, such as SRB2, SRB1, or SRB3) for transmitting LPP data reports if the UE memory is full due to the low priority of the dedicated radio bearer.

[0107] In addition, considering the mobility of the UE, handover may occur during the LPP data collection and reporting process.

[0108] Figure 5 Examples of data collection and reporting procedures during the handover period are provided in accordance with aspects of this disclosure.

[0109] refer to Figure 5UEs that perform LPP data collection and reporting via the source gNB can switch to the target gNB via intra-gNB or inter-gNB mobility procedures.

[0110] For example, during an inter-gNB mobility procedure, when the source gNB wants to hand over the UE to the target cell at the target gNB, in step 501, the source gNB may, for example, explicitly indicate in an XnAP HANDOVER REQUEST message that a dedicated radio bearer has been configured at the UE in the source cell, or provide the configuration of the dedicated radio bearer in the source gNB in ​​an inter-node RRC message. In some embodiments of this disclosure, in step 501, the source gNB may transmit information to the target gNB indicating the dedicated radio bearer that needs to be received from the LMF or gNB.

[0111] Correspondingly, in step 503, the target gNB is expected to provide, for example, a dedicated radio bearer configuration and target gNB configuration in a HANDOVER REQUEST ACKNOWLEDGE message, which will be forwarded to the UE in step 505, for example, via an RRC reconfiguration message.

[0112] In step 507, the UE will dispose of the LPP data reports buffered in memory. In some embodiments of this disclosure, during intra-gNB or inter-gNB mobility procedures, when the UE receives the RRC reconfiguration message for handover in step 505, the UE may discard LPP data reports (or segments) that have been delivered to memory and are awaiting transmission in memory. The UE may retransmit the discarded LPP data reports (or segments) to the target gNB after the handover is complete (e.g., after transmitting the RRC reconfiguration completion message in step 509). In some embodiments of this disclosure, during intra-gNB or inter-gNB mobility procedures, when the UE receives the RRC reconfiguration message for handover in step 505, the UE may not discard LPP data reports (or segments) that have been delivered to memory and are awaiting transmission in memory. After the handover is complete, for example, after transmitting the RRC reconfiguration completion message in step 509, the UE may resume transmitting LPP data reports (or segments) that have been delivered to memory on the target cell or are in said memory. For example, during handover within a gNB, resetting the RLC radio bearer or PDCP may not always be necessary.

[0113] Figure 6An example of a UE 600 according to aspects of this disclosure is described. UE 600 may include a processor 602, a memory 604, a controller 606, and a transceiver 608. The processor 602, memory 604, controller 606, and transceiver 608, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0114] Processor 602, memory 604, controller 606, or transceiver 608, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), or other programmable logic devices, or any combination thereof, configured to or otherwise support components for performing the functions described in this disclosure.

[0115] Processor 602 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some embodiments, processor 602 may be configured to operate memory 604. In some other embodiments, memory 604 may be integrated into processor 602. Processor 602 may be configured to execute computer-readable instructions stored in memory 604 to cause UE 600 to perform various functions of this disclosure.

[0116] Memory 604 may include volatile or non-volatile memory. Memory 604 may store computer-readable, computer-executable code containing instructions that, when executed by processor 602, cause UE 600 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 604 or another type of memory. Computer-readable medium includes both non-transitory computer storage media and communication media, which includes any media that facilitates the transfer of a computer program from one location to another. Non-transitory storage media may be any available media accessible by a general-purpose or special-purpose computer.

[0117] In some implementations, processor 602 and memory 604 coupled to processor 602 may be configured to cause UE 600 to perform one or more of the functions described herein (e.g., processor 602 executing instructions stored in memory 604). For example, processor 602 may support wireless communication at UE 600 according to the examples disclosed herein. UE 600 may be configured to support means for receiving a first LPP message that configures the UE to perform data collection and report collected data via a dedicated radio bearer via an LPP message; means for determining whether to report collected data via a dedicated radio bearer; and means for reporting collected data via a dedicated radio bearer via an LPP message in response to determining that collected data should be reported via a dedicated radio bearer.

[0118] Controller 606 manages the input and output signals of UE 600. Controller 606 can also manage peripheral devices not integrated into UE 600. In some embodiments, controller 606 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some embodiments, controller 606 may be implemented as part of processor 602.

[0119] In some embodiments, UE 600 may include at least one transceiver 608. In other embodiments, UE 600 may have more than one transceiver 608. Transceiver 608 may represent a wireless transceiver. Transceiver 608 may include one or more receiver chains 610, one or more transmitter chains 612, or a combination thereof.

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

[0121] Transmitter chain 612 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 612 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 like phase shift keying (PSK) or quadrature amplitude modulation (QAM). Transmitter chain 612 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. Transmitter chain 612 may also include one or more antennas for transmitting the amplified signal over the air or into the wireless medium.

[0122] Figure 7 An example of a processor 700 according to aspects of this disclosure is described. Processor 700 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 700 may include a controller 702 configured to perform various operations according to the examples described herein. Processor 700 may optionally include at least one memory 704, which may be, for example, an L1 / L2 / L3 cache. Additionally or alternatively, processor 700 may optionally include one or more arithmetic logic units (ALUs) 706. One or more of these components may be electronically communicateable or otherwise coupled via one or more interfaces (e.g., buses) (e.g., operatively, communicatively, functionally, electronically, electrically).

[0123] Processor 700 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 local to the processor chipset (e.g., processor 700) or contained within 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.).

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

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

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

[0127] Memory 704 may store computer-readable, computer-executable code containing instructions that, when executed by processor 700, cause processor 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. Controller 702 and / or processor 700 may be configured to execute the computer-readable instructions stored in memory 704 to cause processor 700 to perform various functions. For example, processor 700 and / or controller 702 may be coupled to memory 704, and processor 700, controller 702, and memory 704 may be configured to perform the various functions described herein. In some instances, processor 700 may include multiple processors and memory 704 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, and the multiple processors may be individually or collectively configured to perform the various functions described herein.

[0128] According to the examples described herein, one or more ALU 706s can be configured to support various operations. In some embodiments, one or more ALU 706s may reside within or on a processor chipset (e.g., processor 700). In some other embodiments, one or more ALU 706s may reside outside the processor chipset (e.g., processor 700). One or more ALU 706s can perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 706s can receive input operands and operation codes, which determine the operation to be performed. One or more ALU 706s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Alternatively, one or more ALU 706s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 706s to handle conditional operations, comparisons, and bitwise operations.

[0129] Processor 700 may support wireless communication according to the examples disclosed herein. Processor 700 may be configured or operable to support means for receiving a first LPP message, the first LPP message configuring the UE to perform data collection and report the collected data via a dedicated radio bearer through the LPP message; means for determining whether to report the collected data via the dedicated radio bearer; and means for reporting the collected data via the dedicated radio bearer through the LPP message in response to determining that the collected data should be reported via the dedicated radio bearer.

[0130] Figure 8This describes an example of NE 800 according to aspects of this disclosure. NE 800 may include a processor 802, a memory 804, a controller 806, and a transceiver 808. The processor 802, memory 804, controller 806, and transceiver 808, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0131] Processor 802, memory 804, controller 806, or transceiver 808, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), or other programmable logic devices, or any combination thereof, configured to or otherwise support elements for performing the functions described in this disclosure.

[0132] Processor 802 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some embodiments, processor 802 may be configured to operate memory 804. In some other embodiments, memory 804 may be integrated into processor 802. Processor 802 may be configured to execute computer-readable instructions stored in memory 804 to cause NE 800 to perform various functions of this disclosure.

[0133] Memory 804 may include volatile or non-volatile memory. Memory 804 may store computer-readable, computer-executable code containing instructions that, when executed by processor 802, cause NE 800 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 804 or another type of memory. Computer-readable medium includes both non-transitory computer storage media and communication media, which includes any media that facilitates the transfer of a computer program from one location to another. Non-transitory storage media may be any available media accessible by a general-purpose or special-purpose computer.

[0134] In some implementations, processor 802 and memory 804 coupled to processor 802 may be configured to cause NE 800 to perform one or more of the functions described herein (e.g., processor 802 executing instructions stored in memory 804). For example, processor 802 may support wireless communication at NE 800 according to the examples disclosed herein. NE 800 may be configured to support means for receiving information indicating the need for a dedicated radio bearer associated with a UE, wherein the UE is expected to report collected data via an LPP message through the dedicated radio bearer; means for determining whether to configure the dedicated radio bearer; and means for transmitting the dedicated radio bearer to the UE in response to determining that the dedicated radio bearer is configured.

[0135] Controller 806 manages the input and output signals of NE 800. Controller 806 can also manage peripheral devices not integrated into NE 800. In some embodiments, controller 806 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some embodiments, controller 806 may be implemented as part of processor 802.

[0136] In some embodiments, NE 800 may include at least one transceiver 808. In other embodiments, NE 800 may have more than one transceiver 808. Transceiver 808 may represent a wireless transceiver. Transceiver 808 may include one or more receiver chains 810, one or more transmitter chains 812, or a combination thereof.

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

[0138] Transmitter chain 812 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 812 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 like phase shift keying (PSK) or quadrature amplitude modulation (QAM). Transmitter chain 812 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. Transmitter chain 812 may also include one or more antennas for transmitting the amplified signal over the air or into the wireless medium.

[0139] Figure 9 An example of an LMF 900 according to aspects of this disclosure is described. The LMF 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908. The processor 902, memory 904, controller 906, and transceiver 908, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0140] Processor 902, memory 904, controller 906, or transceiver 908, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), or other programmable logic devices, or any combination thereof, configured to or otherwise support components for performing the functions described in this disclosure.

[0141] Processor 902 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some embodiments, processor 902 may be configured to operate memory 904. In some other embodiments, memory 904 may be integrated into processor 902. Processor 902 may be configured to execute computer-readable instructions stored in memory 904 to cause LMF 900 to perform various functions of this disclosure.

[0142] Memory 904 may comprise volatile or non-volatile memory. Memory 904 may store computer-readable, computer-executable code containing instructions that, when executed by processor 902, cause LMF 900 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 904 or another type of memory. Computer-readable medium includes both non-transitory computer storage media and communication media, which includes any media that facilitates the transfer of a computer program from one location to another. Non-transitory storage media may be any available media accessible by a general-purpose or special-purpose computer.

[0143] In some implementations, processor 902 and memory 904 coupled to processor 902 may be configured to cause LMF 900 to perform one or more of the functions described herein (e.g., processor 902 executing instructions stored in memory 904). For example, processor 902 may support wireless communication at LMF 900 according to the examples disclosed herein. LMF 900 may be configured to support means for transmitting LPP messages that configure the UE to perform data collection and report collected data via dedicated radio bearers; and means for receiving information from the UE via dedicated radio bearers or another radio bearer related to data collection via LPP messages.

[0144] Controller 906 manages the input and output signals of LMF 900. Controller 906 can also manage peripheral devices not integrated into LMF 900. In some embodiments, controller 906 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some embodiments, controller 906 may be implemented as part of processor 902.

[0145] In some embodiments, the LMF 900 may include at least one transceiver 908. In other embodiments, the LMF 900 may have more than one transceiver 908. The transceiver 908 may represent a wireless transceiver. The transceiver 908 may include one or more receiver chains 910, one or more transmitter chains 912, or a combination thereof.

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

[0147] Transmitter chain 912 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 912 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 like phase shift keying (PSK) or quadrature amplitude modulation (QAM). Transmitter chain 912 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. Transmitter chain 912 may also include one or more antennas for transmitting the amplified signal over the air or into the wireless medium.

[0148] Figure 10 A flowchart illustrating a method according to an aspect of this disclosure is provided. The operation of the method can be implemented by a UE as described herein. In some embodiments, the UE can execute a set of instructions to control functional elements of the UE to perform the described functions.

[0149] At step 1001, the method may include receiving a first LPP message that configures the UE to perform data collection and report the collected data via a dedicated radio bearer through the LPP message. Step 1001 may be performed according to examples as described herein. In some embodiments, it may be performed by, as referenced... Figure 6 The described aspect of the UE to perform the operation of 1001.

[0150] At step 1003, the method may include determining whether to report the collected data via a dedicated radio bearer. Step 1003 may be performed according to examples as described herein. In some embodiments, it may be performed by, as referenced... Figure 6 The described aspect of the UE performing the operation of step 1003.

[0151] At step 1005, the method may include reporting the collected data via a dedicated radio bearer via an LPP message in response to determining that the collected data should be reported via a dedicated radio bearer. Step 1005 may be performed according to examples as described herein. In some embodiments, it may be performed by, as referenced... Figure 6 The described aspect of the UE performing the operation of step 1005.

[0152] It should be noted that the method described herein describes one possible implementation, and the operation and steps may be rearranged or otherwise modified, and other implementations are possible.

[0153] Figure 11 A flowchart illustrating a method according to an aspect of this disclosure is provided. The operation of the method can be implemented by an NE as described herein. In some embodiments, the NE can execute a set of instructions to control the functional elements of the NE to perform the described functions.

[0154] At step 1101, the method may include receiving information indicating the need for a dedicated radio bearer associated with the UE, wherein the UE is expected to report the collected data via an LPP message through the dedicated radio bearer. Step 1101 may be performed according to examples as described herein. In some embodiments, it may be performed by reference to... Figure 8 The NE described herein is the aspect of performing the operation of step 1101.

[0155] At step 1103, the method may include determining whether to configure a dedicated radio bearer. Step 1103 may be performed according to examples as described herein. In some embodiments, it may be performed by, as referenced... Figure 8 The described NE is used to perform the operation of step 1103.

[0156] At step 1105, the method may include transmitting a dedicated radio bearer to the UE in response to determining a configuration for the dedicated radio bearer. Step 1105 may be performed according to examples as described herein. In some embodiments, it may be performed by, as referenced... Figure 8 The NE described herein is the aspect of performing the operation of step 1105.

[0157] Figure 12 A flowchart illustrating a method according to an aspect of this disclosure is provided. The operation of the method may be implemented by an LMF as described herein. In some embodiments, the LMF may execute a set of instructions to control the functional elements of the LMF to perform the described functions.

[0158] At step 1201, the method may include transmitting an LPP message that configures the UE to perform data collection and report the collected data bearer via a dedicated radio through the LPP message. Step 1201 may be performed according to examples as described herein. In some embodiments, it may be performed by, as referenced... Figure 9 The LMF described herein is used to perform the operation of step 1201.

[0159] At step 1203, the method may include receiving information from the UE via a dedicated radio bearer or another radio bearer related to data collection via LPP messages. Step 1203 may be performed according to examples as described herein. In some embodiments, it may be performed by, as referenced... Figure 9 The LMF described herein is used to perform the operation of step 1203.

[0160] It should be noted that the method described herein describes one possible implementation, and the operation and steps may be rearranged or otherwise modified, and other implementations are possible.

[0161] It should be noted that the method described herein describes one possible implementation, and the operation and steps may be rearranged or otherwise modified, and other implementations are possible.

[0162] The description herein is provided to enable those skilled in the art to make or use this disclosure. Those skilled in the art will understand that various modifications to this disclosure are possible, and that other variations can be applied to the general principles defined herein without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but is consistent with the widest scope of the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) for wireless communication, comprising: At least one memory; and At least one processor, coupled to and configured to enable the UE to: The UE receives a first Long Term Evolution (LTE) Positioning Protocol (LPP) message, which configures the UE to perform data collection and report the collected data via a dedicated radio bearer through the LPP message. Determine whether to report the collected data via the dedicated radio bearer; and In response to determining that the collected data should be reported via the dedicated radio bearer, the collected data is reported via the dedicated radio bearer through an LPP message.

2. The UE according to claim 1, wherein the first LPP message configures the UE to report the collected data periodically, once, or in an event-triggered manner.

3. The UE according to claim 1, wherein the dedicated radio bearer is a radio bearer different from the signaling radio bearers SRB1, SRB2 and SRB3.

4. The UE of claim 1, wherein determining whether to report the collected data via the dedicated radio bearer comprises: In response to receiving the first LPP message, it is determined whether the dedicated radio bearer is available.

5. The UE of claim 4, wherein the at least one processor is configured to cause the UE to: If the dedicated radio bearer is unavailable, transmit information to the NE indicating that a dedicated radio bearer is required.

6. The UE of claim 4, wherein the at least one processor is configured to cause the UE to: If the dedicated radio bearer is unavailable, a timer is started to wait for the dedicated radio bearer to be configured.

7. The UE of claim 6, wherein in response to a configuration where the timer period has expired and no dedicated radio bearer has been received, the at least one processor is configured to cause the UE to: A second LPP message is transmitted to notify that the collected data, as configured by the first LPP message, has failed to be reported.

8. The UE of claim 4, wherein, if the dedicated radio bearer is available, determining whether to report the collected data via the dedicated radio bearer further comprises: Whether a second LPP message used to report the collected data has a low priority is determined based on a configured or predefined priority used to report the collected data; and When the second LPP message has a low priority, the second LPP message is transmitted via the dedicated radio bearer.

9. The UE of claim 8, wherein the at least one processor is configured to cause the UE to: If the second LPP message has a high priority, the second LPP message is transmitted via SRB2 or SRB1.

10. The UE of claim 4, wherein, if the dedicated radio bearer is available, determining whether to report the collected data via the dedicated radio bearer further comprises: Determine whether to report the collected data via the dedicated radio bearer through the UE's LPP layer.

11. The UE of claim 1, wherein, in the event that the memory of the UE buffering the collected data is full, performing the reporting of the collected data via the dedicated radio bearer comprises: The collected data in the memory shall be discarded in one or more of the following orders: from old data to new data, or from low-priority data types to high-priority data types; or Switch the dedicated radio bearer used to report the collected data to a different radio bearer that is configured or predefined.

12. The UE of claim 4, wherein, in the event that the dedicated radio bearer is unavailable, the at least one processor is configured to cause the UE to: Begin collecting data as configured by the first LPP message and buffer the collected data until the dedicated radio bearer becomes available; or Begin collecting data as configured by the first LPP message and transmit the collected data report via a configured or predefined radio bearer.

13. The UE of claim 1, wherein in response to a handover being initiated, the at least one processor is configured to cause the UE to: Discard or retain the collected data that has been delivered to memory and is awaiting transmission and will be reported.

14. The UE of claim 13, wherein, if the dedicated radio bearer configured by the target NE after the handover is completed is available for reporting the collected data, the at least one processor is configured to cause the UE to: If the buffered collected data to be reported is discarded, the collected data is retransmitted to the target NE; or While retaining the collected data to be reported, resume reporting the collected data to the target NE.

15. A processor for wireless communication, comprising: At least one controller, coupled to at least one memory and configured to enable the processor to: The UE receives a first Long Term Evolution (LTE) Positioning Protocol (LPP) message, which configures the UE to perform data collection and report the collected data via a dedicated radio bearer through the LPP message. Determine whether to report the collected data via the dedicated radio bearer; and In response to determining that the collected data should be reported via the dedicated radio bearer, the collected data is reported via the dedicated radio bearer through an LPP message.

16. A network device NE for wireless communication, comprising: At least one memory; and At least one processor, coupled to the at least one memory and configured to enable the NE: Receive information indicating that a dedicated radio bearer associated with a user equipment (UE) is required, wherein the UE is expected to report the collected data via the dedicated radio bearer through a Long Term Evolution (LTE) Positioning Protocol (LPP) message. Determine whether to configure the dedicated radio bearer; and In response to determining the configuration of the dedicated radio bearer, the dedicated radio bearer is transmitted to the UE.

17. The NE of claim 16, wherein the information indicating the need for a dedicated radio bearer is carried in the New Radio NR Positioning Protocol A NRPPa message.

18. The NE of claim 16, wherein the information indicating the need for a dedicated radio bearer is received from the UE.

19. The NE of claim 16, wherein the NE is the source NE of the UE in handover, and the at least one processor is configured to cause the NE to: Transmit to the target NE information indicating the need for the dedicated radio bearer associated with the UE.

20. A location management function (LMF) for wireless communication, comprising: At least one memory; and At least one processor, coupled to the at least one memory and configured to enable the NE: The first Long Term Evolution (LTE) Positioning Protocol (LPP) message is transmitted, which configures the User Equipment (UE) to perform data collection and report the collected data via a dedicated radio bearer through the LPP message; and Information related to the data collection via LPP messages is received from the UE via the dedicated radio bearer or another radio bearer.

Images