Positioning method

Abstract

A system and method for positioning by a user equipment (UE) may include: the UE receiving a radio resource control (RCC) signal including a measurement request; the UE receiving at least two positioning reference signals (PRS), each of the at least two PRS corresponding to a different portion of an operating frequency range; determining that the at least two positioning reference signals are capable of being coherently combined; the UE aggregating the at least two PRS during a measurement interval; and the UE reporting the measurement based on the aggregation of the at least two PRS.

Description

Technical Field

[0001] This disclosure generally relates to user equipment positioning. More specifically, the subject matter disclosed herein relates to an improvement in a method for positioning in a user equipment with low power reduction capability. [Cross - reference to Related Applications]

[0002] This application claims the benefit of priority of U.S. Provisional Application No. 63 / 419,636, filed on October 26, 2022, and U.S. Provisional Application No. 63 / 331,014, filed on April 14, 2022, under 35 U.S.C. § 119(e). The entire disclosures of both of the said U.S. Provisional Applications are incorporated herein by reference in their entireties as if fully set forth herein. Prior Art

[0003] In the 3rd Generation Partnership Project (3GPP) New Radio (NR) Release-16 and Release-17, various positioning technology standards are standardized. Release-18 continues these positioning standards by adding areas for supporting Reduced Capability (RedCap) User Equipment (UE) and Low Power High Accuracy Positioning (LPHAP). Therefore, there has been a continuous desire to improve accuracy, integrity, and power efficiency. The Service & System Aspects Working Group 1 (SA1) has studied the requirements for LPHAP (such as the requirements defined in European Telecommunications Standards Institute (ETSI) Technical Specification (TS) 22.104, which include enhancements to the RRC_INACTIVE state and / or the RRC_IDLE state) to evaluate the Radio Access Network (RAN) functions that support such power consumption requirements and positioning requirements. Therefore, there has been a continuous desire to improve the technology that supports such low power requirements and positioning requirements for RedCap UEs. Therefore, the angle-based positioning technology and time-based positioning technology described throughout this disclosure can be utilized to perform positioning under these lower power conditions and reduced capability conditions. Summary of the Invention

[0004] According to an embodiment, a positioning method may include: receiving, by a User Equipment (UE), a Radio Resource Control (RCC) signal including a measurement request; receiving, by the UE, at least two Positioning Reference Signals (PRSs), each of the at least two PRSs corresponding to a different division of an operating frequency range; determining that the at least PRSs are co-phasable; aggregating, by the UE, the at least two PRSs in one measurement gap; and reporting, by the UE, measurements based on the aggregation of the at least two PRSs.

[0005] The method may include determining that the at least two PRSs are co-phasable is at least based on channel coherence time.

[0006] The method may include determining that the at least two PRSs can be coherently combined based on at least one of clock drift and timing offset between different sub-bands of the operating frequency range.

[0007] The measurements based on the aggregation may be reported to a Location Management Function (LMF).

[0008] Each of the at least two PRSs may be a narrowband PRS.

[0009] The UE may be a Reduced Capability (RedCap) UE or a Low Power High Accuracy Positioning (LPHAP) UE.

[0010] The at least two PRSs may be configured by an LMF.

[0011] The method may further include a Transmission and Reception Point (TRP) measuring uplink sounding reference signal-reference signal received power (UL SRS-RSRP), uplink sounding reference signal-reference signal path power (UL SRS-RSRPP), and uplink relative time of arrival (UL RTOA) and reporting the UL SRS-RSRP, the UL SRS-RSRPP, and the UL RTOA to the LMF.

[0012] The method may further include the TRP reporting a difference report, the difference report including differences between previously measured UL SRS-RSRP, UL SRS-RSRPP, and UL RTOA and subsequently measured UL SRS-RSRP, UL SRS-RSRPP, and UL RTOA.

[0013] The method may further include the UE reporting downlink positioning reference signal-reference signal received power (DL PRS-RSRP) and downlink positioning reference signal-reference signal path power (DL PRS-RSRPP) to the LMF.

[0014] The reporting of the measurements may be carried out using a Configuration Grant (CG).

[0015] According to another embodiment, a positioning method may include: receiving, by a user equipment (UE), a radio resource control (RCC) signal including a measurement request; receiving, by the UE, a configuration from a location management function (LMF) to report an aggregated bandwidth by the UE; receiving, by the UE, a plurality of positioning reference signals (PRSs), each of the plurality of PRSs corresponding to a different division of an operating frequency range; determining that the plurality of PRSs can be coherently combined; performing, by the UE, measurements in one measurement gap based on determining a maximum aggregated bandwidth of the received plurality of PRSs; and reporting, by the UE, the determined maximum aggregated bandwidth to the LMF.

[0016] The method may further include reporting the measurements to the LMF.

[0017] The maximum aggregated bandwidth may be further determined based on channel coherence time.

[0018] The maximum aggregated bandwidth is further determined based on at least one of clock drift and timing offset between the different divisions of the operating frequency range.

[0019] The UE may be a reduced-capability (RedCap) UE or a low-power high-accuracy positioning (LPHAP) UE.

[0020] The PRS may be received from a network server.

[0021] The maximum aggregated bandwidth may be reported as the number of hopping frequencies.

[0022] The method may further include measuring, by a transmission and reception point (TRP), uplink sounding reference signal-reference signal received power (UL SRS-RSRP), uplink sounding reference signal-reference signal path power (UL SRS-RSRPP), and uplink relative time of arrival (UL RTOA), and reporting the UL SRS-RSRP, the UL SRS-RSRPP, and the UL RTOA to the LMF.

[0023] The method may further include the TRP reporting a difference report, the difference report including differences between previously measured UL SRS-RSRP, UL SRS-RSRPP, and UL RTOA and subsequently measured UL SRS-RSRP, UL SRS-RSRPP, and UL RTOA.

[0024] It may further include the UE reporting a downlink positioning reference signal - reference signal received power (DL PRS - RSRP) and a downlink positioning reference signal - reference signal path power (DL PRS - RSRPP) to the LMF.

[0025] The reporting of the measurement may be implemented using a configured grant (CG).

[0026] According to another embodiment, a positioning method may include: a user equipment (UE) receiving a downlink (DL) positioning reference signal (PRS); the UE measuring at least one of a DL reference signal received power (RSRP) and a DL reference signal path power (RSRPP) for a plurality of transmit - receive points (TRPs) based on the received DL PRS; the UE transmitting an uplink (UL) sounding reference signal (SRS) including at least one of the RSRP and the RSRPP to the TRP.

[0027] The DL PRS includes DL RSRP and / or DL RSRPP.

[0028] Measuring the DL RSRP and / or DL RSRPP per beam for each of the plurality of TRPs.

[0029] The method may further include reporting the measured DL RSRP and / or DL RSRPP to a location management function (LMF).

[0030] The reporting of the measured DL RSRP and / or DL RSRPP may include a differential report of the measured DL RSRP and / or DL RSRPP in response to determining that a previous report includes a complete report.

[0031] The method may further include determining the direction of a network server based on the measured DL RSRP and / or DL RSRPP.

[0032] The transmitting of the UL SRS includes transmitting in the direction of the determined network server.

[0033] The transmitting of the UL SRS includes an omnidirectional transmission to the network server.

[0034] The method may further include the UE sending, to the LMF, capability information corresponding to the UE.

[0035] The capability information indicates that the UE is a Reduced Capability (RedCap) UE configured to perform low-overhead angle-based positioning via the Long-Term Evolution (LTE) Positioning Protocol (LPP).

[0036] According to another embodiment, a system may include a User Equipment (UE), the UE including a memory and a processor, the processor being configured to execute instructions stored in the memory to perform operations including: receiving, by the UE, a Downlink (DL) Positioning Reference Signal (PRS); measuring, by the UE, at least one of DL Reference Signal Received Power (RSRP) and DL Reference Signal Path Power (RSRPP) for a plurality of Transmission and Reception Points (TRPs) based on the received DL PRS; transmitting, by the UE, an Uplink (UL) Sounding Reference Signal (SRS) including at least one of RSRP and RSRPP to the TRP.

[0037] The DL PRS may include DL RSRP and / or DL RSRPP.

[0038] The DL RSRP and / or DL RSRPP per beam may be measured for each of the plurality of TRPs.

[0039] The operations may further include reporting the measured DL RSRP and / or DL RSRPP to a Location Management Function (LMF).

[0040] The reporting of the measured DL RSRP and / or DL RSRPP may include reporting a difference report of the measured DL RSRP and / or DL RSRPP in response to determining that a previous report includes a complete report.

[0041] The operations may further include determining a direction of a network server based on the measured DL RSRP and / or DL RSRPP.

[0042] The transmitting the UL SRS may include transmitting in the determined direction of the network server.

[0043] The transmitting the UL SRS may include transmitting omnidirectionally to the network server.

[0044] The operation may further include the UE sending, to the LMF, capability information corresponding to the UE.

[0045] The capability information may indicate that the UE is a Reduced Capability (RedCap) UE configured to perform low-overhead angle-based positioning via the Long-Term Evolution (LTE) Positioning Protocol (LPP). Brief Description of the Drawings

[0046] In the following sections, aspects of the subject matter disclosed herein will be described with reference to exemplary embodiments shown in the figures, in which: FIG. 1 shows an overall system diagram of a downlink angle of departure (DL-AoD) method. FIG. 2 shows an overall system diagram of an uplink angle of arrival (UL-AoA) method. FIG. 3 is a flowchart of an angle-based positioning protocol according to various embodiments of the present disclosure. FIG. 4 is a flowchart of a method for UE operation according to various embodiments of the present disclosure, in which frequency hopping is performed by a network server and the UE determines whether to perform aggregation with frequency hopping. FIG. 5 is a flowchart of a method for UE operation according to various embodiments of the present disclosure, in which the UE performs frequency hopping and the UE determines the number of frequency hops to perform. FIGS. 6 to 7 are block diagrams of an electronic device in a network environment according to various embodiments of the present disclosure. Embodiments

[0047] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the present disclosure. However, those skilled in the art will understand that the disclosed aspects may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to obscure the subject matter disclosed herein.

[0048] As used throughout this specification, the phrase "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment disclosed herein. Thus, the appearances of the phrases "in one embodiment", "in an embodiment", or "according to one embodiment" (or other phrases with similar meanings) throughout this specification are not necessarily all referring to the same embodiment. In addition, in one or more embodiments, the particular features, structures, or characteristics can be combined in any suitable manner. In this regard, the term "exemplary" as used herein means "serving as an example, instance, or illustration". Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. Additionally, in one or more embodiments, the particular features, structures, or characteristics can be combined in any suitable manner. Also, depending on the context of the discussion herein, singular terms can include the corresponding plural forms and plural terms can include the corresponding singular forms. Similarly, hyphenated terms (e.g., "two-dimensional", "pre-determined", "pixel-specific", etc.) can occasionally be used interchangeably with their corresponding non-hyphenated versions (e.g., "two dimensional", "predetermined", "pixel specific", etc.), and capitalized terms (e.g., "Counter Clock", "Row Select", "PIXOUT", etc.) can be used interchangeably with their corresponding non-capitalized versions (e.g., "counter clock", "row select", "pixout", etc.). Such occasional interchangeability should not be construed as inconsistent with each other.

[0049] Also, depending on the context of the discussion herein, singular terms can include the corresponding plural forms and plural terms can include the corresponding singular forms. It should be further noted that the various figures (including component diagrams) shown and discussed herein are for illustrative purposes only and are not drawn to scale. For example, some elements in the figures can be exaggerated in size relative to other elements for clarity. Additionally, where appropriate, reference numerals are reused in the various figures to indicate corresponding and / or similar elements.

[0050] The terms used herein are for the purpose of describing some exemplary embodiments only and are not intended to limit the claimed subject matter. Unless the context clearly dictates otherwise, the singular forms "a", "an", and "the" used herein are also intended to include the plural forms. It should be further understood that when the terms "comprises" and / or "comprising" are used in this specification, they specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0051] It should be understood that when an element or layer is referred to as being "on", "connected to", or "coupled to" another element or layer, the element or layer can be directly on, directly connected to, or directly coupled to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being "directly on", "directly connected to", or "directly coupled to" another element or layer, no intervening elements or layers are present. Throughout, like numerals refer to like elements. The term "and / or" used herein includes any and all combinations of one or more of the associated listed items.

[0052] The terms "first", "second", etc. used herein are used as labels for the nouns following the terms and do not imply any type of order (e.g., spatial order, temporal order, logical order, etc.) unless explicitly defined as such. Additionally, the same reference numerals may be used in two or more figures to refer to components, elements, blocks, circuits, units, or modules having the same or similar functions. However, such usage is for the sake of brevity and ease of discussion only; it does not imply that the construction details or architectural details of these components or units are the same in all embodiments or that the commonly mentioned components / modules are the only way to implement some of the exemplary embodiments disclosed herein.

[0053] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this subject matter belongs. It should be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and should not be interpreted as having an idealized or overly formal meaning unless so defined herein.

[0054] As used herein, the term "module" refers to any combination of software, firmware, and / or hardware configured to provide the functions described herein in combination with the module. For example, the software may be implemented as a software package, code, and / or instruction set or instructions, and the term "hardware" as used in any of the embodiments described herein may include, for example, a unit in isolation or in any combination, hardwired circuitry, programmable circuitry, state machine circuitry, and / or firmware storing instructions executed by the programmable circuitry. Each module may be implemented jointly or separately as circuitry forming part of a larger system (such as, but not limited to, an integrated circuit (IC), a system on-a-chip (SoC), a unit, etc.).

[0055] Embodiments of the present disclosure relate to positioning techniques for supporting low-power and / or reduced-capability devices. According to one technique, angle-based positioning can be utilized since it can be used in systems with lower bandwidths. Some embodiments include an angle-based positioning protocol that meets the low-power requirements of both RedCap and LPHAP.

[0056] Another technique for supporting RedCap UEs with smaller bandwidths (i.e., 20 megahertz (MHz) or 5 MHz) is to utilize frequency hopping for positioning reference signals (PRSs) / sounding reference signals (SRSs) and coherent processing across the hops such that a larger signal bandwidth can be utilized due to the frequency hopping, thereby improving positioning accuracy. However, frequency hopping may also require the UE to determine whether coherent combining can be performed and then aggregate the measurement results for multiple hops based on this determination. In some embodiments, aggregation can still be performed over multiple hops even if coherent combining cannot be achieved. However, if it is determined that coherent combining can be achieved, the quality of the aggregation can be improved.

[0057] Returning to angle-based positioning, FIG. 1 shows an overall system diagram of a downlink angle of departure (DL-AoD) method. The system includes a user equipment (UE) 100, multiple next-generation Node B (g Node B, gNB) servers 102, and a location server 104 (e.g., Location Management Function (LMF)). In some embodiments, the UE 100 may be configured to measure the reference signal received power (RSRP) and the reference signal received path power (RSRPP) of the first detected path on the DL PRS resource and report the RSRP measurement and the RSRPP. In other embodiments, the UE 100 may use NR PRS to perform the RSRP measurement. Additionally, a hybrid method may be utilized, which makes full use of the DL-time difference of arrival (TDOA) and DL-AoD of the same transmission using PRS. Therefore, these methods may be referred to as UE-assisted positioning techniques.

[0058] FIG. 2 shows an overall system diagram of an uplink angle of arrival (AoA) (UL-AoA) method. In some embodiments, uplink signals may be used to estimate the AoA at the transmission reference point (TRP) or gNB. For example, in Long Term Evolution (LTE), the AoA measurement is specified as part of the enhanced cell ID (E-CID) and is defined for the serving cell. In NR, a complete positioning solution using multiple AoAs may be specified. To this end, the AoA measurement may be defined at both the serving cell and neighboring cells. In some embodiments, the AoA is defined as the estimated angle of the UE 100 relative to a reference direction, which is geographically north and positive in the counterclockwise direction, as shown in FIG. 2.

[0059] To estimate the AoA of an incident signal, a directional antenna can be used, such as an adaptive phased array formed by two or more antenna elements. AoA estimation techniques can be used to electronically steer the beam in all possible directions and search for peaks in the output power. However, in this method, the angular resolution may be limited by the beamwidth of the array. Therefore, a large number of antenna elements may be required to achieve a higher resolution. The Multiple Signal Classification (MUSIC) method can also be used to perform AoA measurement, which employs the eigen-structure of the input data when organizing the input data in the form of a time-space matrix. For example, in NR Release 16, UL SRS is used as a reference signal for measuring UL AoA.

[0060] Low-power high-accuracy positioning is an integral part of a significant number of industrial applications. The total energy required for the optimal operation time of such low-power high-accuracy positioning IoT devices is a combination of: the energy for performing positioning (which varies depending on the positioning method used), the energy for communication / synchronization, and other factors that may be difficult to predict to withstand additional losses, such as security, power management, the microcontroller, and the self-discharge of the battery. Exemplary target applications for low-power high-accuracy positioning include, but are not limited to, asset tracking, vehicle tracking, and tool tracking in process automation. Other use cases can include: 1) Process automation: Trolley tracking (outdoor); 2) Process automation: Asset tracking; 3) Flexible modular assembly area: Tool tracking in the flexible modular assembly area in a smart factory; 4) Process automation: Sequence container (intralogistics); 5) Process automation: Palette tracking (e.g., in turbine construction); 6) Flexible modular assembly area: Workpiece tracking in assembly areas and warehouses (indoor and outdoor); 7) Flexible modular assembly area: Tool assignment in the flexible modular assembly area in a smart factory (assigning tools to vehicles (left / right) in the production line); 8) Flexible modular assembly area: Positioning of autonomous vehicles for monitoring purposes (vehicles lined up, distance 1.5 meters); 9) (Internal) logistics: Asset tracking.

[0061] By way of example, Table 1 provides the operation time and duty cycle of updated location information for 5G-enabled IoT devices for different use cases. [Use case] [#] [Horizontal accuracy] [Corresponding service level (] [22.261] [)] [Positioning interval] [ / ] [Duty cycle] [Battery life] [ / ] [Minimum operation time] 1 10 m Service level 1 As required 24 months 2 2 m to 3 m Service level 2 <4 s >6 months 3 <1 m Service level 3 No indication 1 shift - 8 hours (up to 3 days, standby 1 month) 4 <1 m Service level 3 1 s 6 years to 8 years 5 <1 m Service level 3 5 s to 15 minutes 18 months 6 <1 m Service level 3 15 s to 30 s 6 months to 12 months 7 30 cm Service level 5 250 ms 18 months 8 30 cm Service level 5 1 second 6 to 8 years (no strict limit on battery size) 9 10 m Service level 1 20 minutes 12 years (@20 mJ / position fixed) Table 1

[0062] In Release - 17, positioning in the RRC_INACTIVE mode is supported to reduce UE power consumption and signaling overhead. For PRS reception, it is expected that a UE in the RRC_INACTIVE mode will prioritize the reception of any other DL signals and DL channels over the reception of DL PRS. Therefore, a UE in the RRC_INACTIVE mode processes DL PRS outside and within the initial downlink bandwidth part (DL BWP) according to the UE capabilities. For the processing of DL PRS outside the initial DL BWP, the UE can be configured with a numerology and Cyclic Prefix (CP) that are the same as or different from those of the initial DL BWP for PRS resources. For the processing of DL PRS within the initial DL BWP, the UE can be configured with a numerology and CP that are the same as those of the initial DL BWP for PRS resources.

[0063] For SRS transmission, the UE may be configured with SRS resources for positioning associated with the initial UL BWP according to the UE capabilities, and transmit the SRS resources within the initial uplink bandwidth part (UL BWP) during the RRC_INACTIVE mode, where the UL BWP has the same cyclic prefix (CP) and numerology as those configured for the initial UL BWP. The UE may be configured with SRS resources for positioning according to the UE capabilities, and the SRS resources include the frequency position and bandwidth, numerology, and CP length for transmitting the SRS in the RRC_INACTIVE mode. If the transmission of the SRS for positioning in the RRC_INACTIVE mode (the handover time is in the unpaired spectrum according to the UE capabilities) collides with other DL signals or DL channels or UL signals or UL channels in the time domain, the SRS for positioning transmission is discarded in the symbols where the collision occurs. The SRS resources for positioning in the RRC_INACTIVE mode are configured in the same frequency band and component carrier as the initial UL BWP.

[0064] In some embodiments, fingerprint positioning technology uses signal fingerprints and uses the received signal strength at each location (e.g., as a fingerprint stored in a fingerprint database) to match the signal strength measured by the device location to achieve positioning. Therefore, the signal fingerprint positioning method can support and enhance the positioning of RedCap UEs with low power and small channel bandwidths.

[0065] In some embodiments, the fingerprint positioning method for RedCap UEs may be configured such that the UE uses an omnidirectional antenna to transmit UL SRS for positioning. Each transmission reception point (TRP) measures the following: the UL angle of arrival (AoA) of the received UL SRS configured for measurement, the UL reference signal received power (RSRP) of the received UL SRS configured for measurement, the UL SRS-reference signal received path power (RSRPP) for the i-th path (where i = 1, 2,..., N (N ≥ 1)), and the UL relative time of arrival (UL-RTOA) of the received UL SRS signal configured for measurement. Finally, the TRP can then report the measurement vector including UL SRS-RSRP, UL SRS-RSRPP, and UL-RTOA to the LMF via the NR Positioning Protocol A (NRPPa).

[0066] In some embodiments, UL AoA measurement, UL SRS-RSRP measurement, UL SRS-RSRPP measurement, and UL-RTOA measurement can be considered as "signal fingerprint vectors", and location calculation can be performed using pattern matching methods. It should be noted that θ is the measurement of the azimuth angle of arrival (A-AoA), φ is the measurement of the zenith angle of arrival (Z-AoA), is the measurement of UL SRS-RSRP, in the case where i = 1, 2, …, N (N≥2) is the measurement of UL SRS-RSRPP for the i-th path, and is the measurement of UL-RTOA. Therefore, the signal fingerprint vector of the UE can be expressed as:

[0067] Then the positioning engine can compare the received signal fingerprint vector with the expected "database" of the vector and determine the UE location. Therefore, the described signal fingerprint method can be applied to RedCap UEs operating on both FR1 frequency and FR2 frequency. In some embodiments, the RedCap UE has more than one antenna (e.g., two antennas). In such a case, the UE can form a transmit (Tx) beam for SRS transmission. When transmitting UL SRS using multiple Tx beams, the TRP first measures SRS-RSRP for each Tx beam and selects the strongest Tx beam with the maximum SRS-RSRP. Then, the TRP can measure AoA, SRS-RSPP, and UL-RTOA for beam k and report the measurements to the LMF.

[0068] In some embodiments, a UE in an inactive state uses a Small Data Transmission (SDT) method to transmit data. Thus, SDT is the transmission of short data bursts in a connectionless state, where when a small amount of data is to be transmitted, the UE does not have to establish and tear down a connection. Since the network pre-configures radio resources for data transmission in the inactive state, the principle of SDT is relatively simple. For example, if the condition of using the pre-configured radio resources is met, the device transmits data and an RRC request message via the pre-configured radio resources. In the 3GPP standard, depending on the way the radio resources are configured, there are two types of SDT: 1) SDT using random access (RA); and 2) SDT using pre-configured radio resources.

[0069] The SDT using random access in the NR standard can be referred to as Random Access based SDT (RA-SDT). For RA-SDT, the UE can use the shared radio resources of the random access procedure to perform data transmission. Thus, competition with other devices may occur on access to the shared radio resources. The shared radio resources for SDT are broadcast by the system information and can be configured to be isolated from the radio resources for non-SDT RA procedures (i.e., legacy RA procedures provided in, for example, Release-16 / Release-17). On the other hand, Configured Grant based SDT (CG-SDT) uses pre-configured radio resources dedicated to the UE. Thus, the NR standard refers to the SDT using pre-configured radio resources as CG-SDT. When the UE transitions from a connected state to an inactive state, the network can configure the configuration parameters of the pre-configured resources. For example, the RRC release message for connection release transmitted from the network contains the configuration parameters of CG-SDT. In this case, since the configuration parameters are dedicated to the device, it is expected that the SDT using pre-configured radio resources does not have competition.

[0070] In some embodiments, a RedCap UE operates with a smaller bandwidth compared to legacy UEs that operate with full bandwidth (larger bandwidth). In Release-18, the RedCap bandwidth can be as small as 5 megahertz, while legacy UEs can have a bandwidth of up to 100 megahertz or 200 megahertz depending on the frequency range (e.g., FR1 or FR2). This smaller bandwidth of the RedCap UE can be a concern for positioning since traditional time-based techniques may require a bandwidth reference signal larger than that used to provide accurate measurements. Thus, various techniques such as angle-based positioning and frequency hopping methods are attractive for such low-bandwidth UEs.

[0071] Additionally, both RedCap UEs and LPHAP UEs operate at reduced power and are power-constrained, and thus limit the signaling overhead transmissions of RedCap UEs and LPHAP UEs to save power as much as possible. On the other hand, some angle-based method protocols are relatively power-consuming and may require a large amount of reporting, and thus require the UE to transmit. Therefore, there is a desire for an angle-based positioning method with lower power and lower overhead.

[0072] Another solution may include a signal fingerprint method, where the GNB performs positioning measurements based on the received UL SRS and generates a fingerprint vector for pattern matching with a database. Thus, embodiments of the present disclosure include techniques for reducing the overhead that such a signal fingerprint method may incur.

[0073] Accordingly, protocols for angle-based RedCap positioning and positioning using signal fingerprints will be described. According to some embodiments, DL-AoD positioning is based on per-beam RSRP measurements of DL-PRS performed at UE DL-PRS RSRP measurements and / or UE DL-PRS DL-PRS RSRPP measurements. Thus, it is expected that the TRP will transmit beamformed DL-PRS in a beam scanning manner that can be measured by the UE. In some embodiments, the UE may report up to multiple RSRP / RSRPP measurements that are derived on different DL-PRS resources (e.g., derived on different Tx beams of the same TRP). It should be noted that the described angle-based method can be applicable to FR2, but can also be applicable to FR1 (e.g., when a relatively large number of TRPs are involved).

[0074] In some embodiments, when using a downlink angle-based method for RedCap UE, since the UE can send feedback from multiple TRPs, the signaling overhead may be relatively large, especially in FR1. Additionally, such feedback may be sent relatively frequently to maintain positioning accuracy. Therefore, another solution may utilize an uplink angle-based method, where the UE transmits a reference signal (RS) (e.g., SRS in Release-16 / Release-17 specifications), and the TRP performs angle measurements. However, since the UE transmits the RS for a long enough duration for the TRP to perform beam scanning, this method may also involve a large amount of UE transmissions.

[0075] According to some embodiments of the present disclosure, another protocol is described that combines UL SRS-RSRP / SRS-RSRPP measurements with DL-AoD measurements to achieve higher improved positioning accuracy for RedCap UE. The protocol for angle-based RedCap UE positioning may include the UE first measuring the RSRP and / or RSRPP per beam transmitted for multiple TRPs. Then the UE may report the RSRP and / or RSRPP to the LMF via the Long-Term Evolution (LTE) positioning protocol (LPP). At this stage, approximate positioning of the UE may be performed. Next, the UE may transmit UL SRS, and the transmission may be, but not necessarily, an omnidirectional transmission for a single slot. Each TRP may perform UL SRS-RSRP / SRS-RSRPP measurements and determine a more accurate or exact UE location. Therefore, by using channel reciprocity, even with highly directional beams, the TRP can still set its beam to receive the UL SRS. Thus, the UL SRS transmission may be short and omnidirectional to save power. Although this high-level procedure may be enabled in Release-17, the signaling overhead may be relatively high. However, this overhead can be reduced by restricting the per-beam RSRP report from the UE to be sent only when needed (e.g., when there is a beam change) and adapting the UL SRS transmission period from the UE conditionally.

[0076] In addition, in some embodiments, the RF signal fingerprint method described earlier may be used for the positioning of RedCap UEs and low-power UEs (LPHAPs). To reduce the signaling overhead for measurement reporting in the signal fingerprint method, the TRP may report the difference between the current measurement and the previous measurement. More specifically, when positioning is initiated, the TRP may report a measurement vector including UL SRS-RSRP, UL SRS-RSRPP, and UL-RTOA to the LMF. If a full report has been sent previously, the TRP may send only a difference report, which is a vector including the difference between the SRS-RSRP of the current measurement and the previously reported SRS-RSRP for all paths configured to perform measurements, the difference between the SRS-RSRPP of the current measurement and the previously reported SRS-RSRPP, and the difference between the UL-RTOA of the current measurement and the previously reported UL-RTOA.

[0077] Figure 3 is a flowchart of an angle-based positioning protocol according to various embodiments of the present disclosure. For example, since there are no changes or only small changes, the protocol relies on the UE to send limited reports or not to send reports when not required. The UE then sends an uplink signal of short duration so that the TRP can refine the position and compensate for small position changes.

[0078] First, if the UE is a RedCap UE, the fact that the UE is a RedCap UE needs to be reported. Thus, at step 302, the RedCap UE reports, via LPP, information that enables the RedCap UE to support RedCap positioning to the LMF. In essence, the UE needs to indicate that the UE can send limited feedback on its measurements from the PRS. Additionally, the UE can indicate that the UE can transmit SRS only when needed. For example, if the UE is not moving, the UE does not have to send SRS, and if the UE has a low speed, the UE can (in a timely manner) send low-density SRS.

[0079] In the RRC connected mode, at step 304, the PRS for RedCap positioning can be transmitted periodically within the active BWP of the RedCap UE. If the PRS is outside the active BWP of the RedCap UE, a measurement gap can be utilized for positioning measurements. If the PRS is designed to be within the active BWP (the active BWP for the RedCap UE is 20 MHz), a new PRS configuration can be proposed for RedCap positioning. More specifically, for different subcarrier spacings (SCS), the information element (IE) dl-PRS-ResourceBandwidth can have different maximum numbers. It should be noted that in the case where legacy UEs (i.e., non-RedCap UEs) coexist with RedCap UEs in the same system, the TRP can transmit the broadband PRS used in Release-16 / Release-17 positioning. Then the RedCap UE can perform PRS-RSRP measurements and / or PRS-RSRPP measurements on the received PRS within its supported active BWP.

[0080] In the RRC inactive / idle mode, the PRS can be transmitted outside or within the initial DL BWP of the RedCap UE. In the case of transmitting the PRS outside the initial DL BWP of the RedCap UE, the SCS and CP type of the DL PRS can be the same as or different from those of the initial DL BWP of the RedCap UE. In the case of transmitting the DL PRS within the initial DL BWP of the RedCap UE, the SCS and CP type of the DL PRS can be the same as those of the initial DL BWP of the RedCap UE. The UE can receive the PRS in a similar manner to legacy UEs (e.g., according to Release-17). However, the reporting of measurements can be quite different. For example, the UE reports the best beam received by the UE from each TRP. If the best beam does not change between two measurements, the UE may not have to report the best beam. Therefore, the network can assume that the previously indicated best beam can still be valid in the case where a new best beam is not reported.

[0081] In one solution, the UE may have moved slightly. By receiving the SRS and monitoring the signal quality, the TRP can notice that the beam reported as the best beam may no longer be valid. In this case, at step 306, the network can request the UE to report only the best beams of a subset of TRPs, and at step 314, an update for the requested TRPs can be sent.

[0082] When positioning is initiated, all TRPs need to know the best beam of the said TRP for a specific UE. If such determination has not been made, at step 308, the UE may send a complete beam report for all TRPs transmitting PRS. At step 316, the UE may be probed by the network to send this complete report. As an alternative, the TRP can determine this by itself. For example, the TRP can determine the beam direction on its own based on previous downlink transmissions. Since the UE may have more autonomy in operation in the RRC_CONNECTED mode, this is particularly beneficial for LPHAP UEs operating in the RRC_IDLE mode. In some embodiments, the complete report includes the maximum measured RSRP value and the associated PRS index for each TRP. The network may request the UE to send the complete report via Downlink Control Information (DCI) or MAC Control Element (MAC CE), or the UE can decide on its own whether the UE has determined that the best Tx beam has changed relative to the previous report.

[0083] If a complete report has been sent previously, the UE only needs to send a differential report. Therefore, if the best beam has not changed, the UE does not report anything. If the best beam has changed, the UE reports the new best beams of those TRPs. Therefore, at step 310, the UE determines whether the UE needs to send a new update. If a new update needs to be sent, an update is sent at step 318. In this case, the UE may report an indication that the best Tx beam has changed for each TRP. The indicator can be 0 (the best beam has not changed) or 1 (the best beam has changed). If the indicator is 0, the UE reports the difference between the current RSRP and the previous RSRP; if the indicator is 1, the UE reports the current RSRP and the associated PRS index for RSRP measurement.

[0084] For angle-based RedCap positioning, the same spatial filter as the Rx beam will be used to transmit UL SRS. The UE measures the maximum DL-PRS RSRP using the said Rx beam at step 312. The UL SRS can be configured as non-periodic (triggered by DCI) or semi-persistent (triggered by MAC CE). If the DCI configures the SRS as non-periodic, the time offset between the SRS transmission and the last PRS reception can be configured by the gNB.

[0085] In some embodiments, if there is a significant change (e.g., a substantial change), then an SRS is sent. For example, if the UE can determine that the UE is not moving (e.g., based on an accelerometer, Doppler measurements, etc.), then the UE may not report anything. Additionally, the UE can determine that its position has not changed significantly since its last SRS transmission, and thus can skip sending the SRS. In essence, the rate of sending SRS is adaptive based on speed and / or other parameters.

[0086] To enable this operation, the network can provide the UE with a "CG-like" configuration of the SRS. In such a scenario, the UE can transmit or not transmit the SRS according to the condition change. For a UE not in the RRC_CONNECTED mode, the UE can use the SDT procedure for SRS transmission described earlier. More specifically, for RA-SDT, the UE can send the SRS after receiving a Random Access Response (RAR) from the gNB, and the UE obtains TA information. For Configuration Grant-based SDT (CG-SDT), the UE can send the SRS in the pre-configured UL resources.

[0087] In some embodiments, the RedCap UE only reports the measurements for UE-assisted positioning, where the UE position is calculated at the UE side. To reduce the reporting overhead, if an angle-based RedCap positioning method is used, the RedCap UE can only report the PRS index corresponding to the measured maximum DL PRS-RSRP to each TRP. The content of the measurement can include an indication that the best Tx beam for each TRP changes, where the indication can be a binary value 0 or 1; if the best Tx beam changes relative to the previous report, the PRS index is associated with the measured maximum RSRP for each TRP.

[0088] For RedCap UEs in RRC connected mode and LPHAPs in active RRC using small data transfer (SDT), some embodiments may use configured grant (CG) uplink transmission, which enables UL transmission without the need for dynamic grants for measurement reporting. There are two types of configured grants: 1) configured grant type 1, where the grant configuration is provided by RRC; and 2) configured grant type 2, where the grant is provided by the physical downlink control channel (PDCCH) and is also enabled or disabled by the physical uplink shared channel (PUSCH). The CG PUSCH for reporting measurements for RedCap positioning can be configured with the same periodicity as the PRS and can be scheduled at a certain time distance after the PRS so that the UE can take into account measurement processing latency and signal generation.

[0089] For LPHAPs in RRC inactive / idle and using RACH, the measurements can be directly included in the PUSCH transmission (i.e., Msg3) in the random access procedure.

[0090] In some embodiments, using frequency hopping enables UEs operating with a smaller bandwidth to utilize a larger bandwidth. For example, a RedCap UE operates with a smaller bandwidth (e.g., 20 megahertz or 5 megahertz). By enabling frequency hopping and coherent processing across the hops for the PRS / SRS, the RedCap UE will be able to effectively utilize a larger signal bandwidth (e.g., 100 megahertz), thereby improving positioning accuracy. However, frequency hopping also relies on the UE to perform coherent combining and aggregate the measurement results of multiple hops of the frequency hopping. Therefore, in some embodiments, the UE may first determine the coherently combinable PRS / SRS, which may indicate the quality of the aggregation or whether the aggregation is actually beneficial. Thus, if coherent combining cannot be achieved, then even though aggregation over multiple hops may be possible, the aggregation may not be beneficial.

[0091] Therefore, according to embodiments of the present disclosure, to achieve a gain from coherent combining, the total transmission time of multiple hops should be within the channel coherence time. The coherence time is inversely related to the Doppler spread such that:

[0092] Table 2 provides values of Doppler spread and associated channel coherence time for two frequency bands for RedCap UE positioning. Carrier frequency UE speed Maximum Doppler spread Channel coherence time 3.5 GHz 3 km / h 9.72 Hz 25.7 ms 3.5 GHz 30 km / h 97.2 Hz 2.57 ms 3.5 GHz 60 km / h 194.4 Hz 1.285 ms 28 GHz 3 km / h 77.8 Hz 3.21 ms 28 GHz 30 km / h 777.8 Hz 0.321 ms 28 GHz 60 km / h 1555.6 Hz 0.161 ms Table 2

[0093] As shown in Table 2, the feasibility of frequency hopping for positioning a RedCap UE depends on the time gap between two consecutive hops reported by the RedCap UE, the operating carrier frequency, and the UE speed (e.g., the speed at which the UE moves or travels). The said shows that in some cases, applying frequency hopping to RedCap UE positioning may be infeasible. For example, if the time gap between two consecutive hops reported by the UE is 1 millisecond, then in the case where the RedCap UE operates at a carrier frequency of 28 GHz and a UE speed greater than 30 km / h, frequency hopping is infeasible. In FR1, the coherence time is generally longer, thus providing more opportunities to implement channel aggregation of PRS. It should be noted that to cover a bandwidth of 100 MHz, six hops (each hop having a bandwidth of 20 MHz) may be required, taking into account the overlap between the hops. Therefore, if the gap is 1 millisecond, it may take more than 6 milliseconds. Therefore, coherent combination can be applied for very low UE speeds.

[0094] In some embodiments, when coherent combination cannot be achieved and thus cannot be applied, each hop can be processed individually. Thus, by way of example, then the individual measurements can be averaged. Additionally, the number of hops that can be combined together depends on the channel coherence time. For example, aggregating two hops of 20 MHz each will achieve a bandwidth of 40 MHz, so aggregating two hops according to the above example can achieve a considerable gain. However, since the coherence time may be too small, it may be difficult to perform larger aggregations. Therefore, when reporting measurements, the UE can also report the bandwidth it uses for the combined PRS.

[0095] Therefore, in some embodiments, the UE can decide whether to perform frequency hopping depending on whether frequency hopping is actually beneficial. Additionally, the UE can be configured to indicate the number of aggregated frequency hops in the measurement report.

[0096] In some embodiments, the UE can perform measurements during a time window period, which can be referred to as a measurement gap. The measurement gap can be determined and / or set by a higher-level network such as a gNB, and during this measurement gap, the UE determines the priority of the measurement and performs the measurement. During the time period outside this measurement gap, the UE can perform other functions, such as data communication (e.g., transmitting data and / or receiving data). Therefore, the UE may prioritize these other functions and thus may not be able to perform the measurement function requested by the RRC. In such a case, it may be necessary for the UE to determine the function it wishes to prioritize. Therefore, to ensure that the UE performs the measurement function, aggregation should be performed in one measurement gap.

[0097] FIG. 4 is a flowchart of a method for UE operation according to an embodiment of the present disclosure, where frequency hopping is performed by a network server (e.g., gNB) and the UE determines whether to perform aggregation with frequency hopping. According to this technique, at step 402, the UE may receive a measurement request via RRC signaling. In other words, the transmitter is configured to perform frequency hopping or not perform frequency hopping depending on whether the UE indicates to the transmitter that the UE is capable of performing aggregation or desires to perform aggregation. The measurement request may generally be in an existing format, but a field may be added to the measurement request information element (IE) to indicate that aggregated PRS can be used. For example, a binary 1 in this field may indicate that the UE is capable of performing aggregation, while a binary 0 may indicate that the UE is not capable of performing aggregation.

[0098] If the UE is capable of performing aggregation, the UE sends a signal back to the transmitter, and then the UE receives the aggregated PRS at step 404. That is, the UE receives a set of narrowband PRS on different sub-bands of the frequency band at different times. The UE may determine at step 406 whether coherent combining can be performed based on channel parameters (e.g., coherent time) and other parameters (e.g., clock drift, time interval between frequency hops, etc.). If coherent combining can be performed, the UE reports the measurement based on the aggregated PRS at step 408. If coherent combining cannot be performed, the UE reports the measurement based on the quantity calculated on the non-aggregated PRS (e.g., individual TDOA values per hop or the average of the hops, etc.) at step 410. It should be noted that in some embodiments, aggregation may still be performed even if coherent combining is not achievable. Additionally, in its measurement report, the UE may include information on whether aggregated PRS or non-aggregated PRS is used to perform the measurement. Therefore, this technique is particularly useful when up to two hops can be aggregated together.

[0099] However, in some cases, aggregating more than two hops may be beneficial for further improving positioning. For example, a 20 MHz UE may aggregate six hops to fully utilize a 100 MHz bandwidth. Therefore, the UE (e.g., RedCap UE) may perform frequency hopping to achieve this further aggregation. FIG. 5 is a flowchart of a method for UE operation according to various embodiments of the present disclosure, where the UE performs frequency hopping and the UE determines the number of hops to perform.

[0100] According to this technique, at step 502, the UE reports the aggregated bandwidth for which it has performed measurements. More specifically, the UE receives a measurement request via RRC signaling, and the measurement request can have an existing format. A field can be added to the measurement request to indicate that the aggregated PRS can be used. Then, at step 504, the UE receives the aggregated PRS. In the case of Tx hopping, the UE receives a set of narrowband PRSs on different sub-bands of the frequency band at different times. In other embodiments, the UE performs frequency hopping, and thus can receive broadband PRS (e.g., legacy PRS), and the UE can perform Rx hopping. At step 506, the UE determines the number of hopping synchronization combinations that can be performed based on channel parameters (e.g., synchronization time) and other parameters (e.g., clock drift, time interval between frequency hops, etc.). Then, at step 508, the UE performs measurements on the highest amount (e.g., maximum amount) of aggregated bandwidth that the UE can support. Then, the UE reports the measurements and the aggregated bandwidth to the transmitter (e.g., gNB). In some embodiments, the aggregated bandwidth can be reported as the number of hops. Additionally, it should be noted that the UE can autonomously determine the number of hops or the aggregated bandwidth.

[0101] Therefore, the UE can autonomously determine whether to perform frequency hopping, and if frequency hopping is performed, determine the number of frequency hops to be aggregated. Additionally, the frequency hopping can be performed by the UE or by the network server to improve positioning measurements, especially in UEs with reduced capabilities and low power constraints.

[0102] FIG. 6 is a block diagram of an electronic device in a network environment 600 according to an embodiment.

[0103] Referring to FIG. 6, the electronic device 601 in the network environment 600 may communicate with an external electronic device 602 via a first network 698 (e.g., a short-range wireless communication network), or communicate with an external electronic device 604 or a server 608 via a second network 699 (e.g., a long-range wireless communication network). The electronic device 6601 may communicate with the external electronic device 604 via the server 608. The electronic device 601 may include a processor 620, a memory 630, an input device 650, a sound output device 655, a display device 660, an audio module 670, a sensor module 676, an interface 677, a haptic module 679, a camera module 680, a power management module 688, a battery 689, a communication module 690, a subscriber identification module (SIM) card 696, or an antenna module 697. In one embodiment, at least one of the components (e.g., the display device 660 or the camera module 680) may be omitted from the electronic device 601, or one or more other components may be added to the electronic device 601. Some of the components may be implemented as a single integrated circuit (IC). For example, the sensor module 676 (e.g., a fingerprint sensor, an iris sensor, or an illuminance sensor) may be embedded in the display device 660 (e.g., a display).

[0104] The processor 620 may execute software (e.g., a program 640) to control at least one other component (e.g., a hardware component or a software component) of the electronic device 601 coupled to the processor 620 and may perform various data processing or calculations.

[0105] As at least a part of data processing or computing, the processor 620 may load commands or data received from another component (e.g., the sensor module 646 or the communication module 690) into the volatile memory 632, process the commands or data stored in the volatile memory 632, and store the resulting data in the non-volatile memory 634. The processor 620 may include a main processor 621 (e.g., a central processing unit (CPU) or an application processor (AP)) and an auxiliary processor 623 (e.g., a graphics processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that can operate independently of or in combination with the main processor 621. Additionally or alternatively, the auxiliary processor 623 may be adapted to consume less power than the main processor 621 or perform specific functions. The auxiliary processor 623 may be implemented separately from the main processor 621 or as a part of the main processor 621.

[0106] While the main processor 621 is in a non-active (e.g., sleep) state, the auxiliary processor 623 may control at least some of the functions or states related to at least one of the components of the electronic device 601 (e.g., the display device 660, the sensor module 676, or the communication module 690) instead of the main processor 621, or while the main processor 621 is in an active state (e.g., executing an application), the auxiliary processor 623 and the main processor 621 may perform the above control together. The auxiliary processor 623 (e.g., the image signal processor or the communication processor) may be implemented as a part of another component (e.g., the camera module 680 or the communication module 690) that is functionally related to the auxiliary processor 623.

[0107] The memory 630 may store various data used by at least one component of the electronic device 601 (e.g., the processor 620 or the sensor module 676). The various data may include, for example, software (e.g., the program 640) and input data or output data for commands related thereto. The memory 630 may include the volatile memory 632 or the non-volatile memory 634. The non-volatile memory 634 may include an internal memory 636 and an external memory 638.

[0108] The program 640 can be stored as software in the memory 630 and can include, for example, an operating system (OS) 642, middleware 644, or an application 646.

[0109] The input device 650 can receive commands or data from outside the electronic device 601 (e.g., from a user) to be used by another component of the electronic device 601 (e.g., the processor 620). The input device 650 can include, for example, a microphone, a mouse, or a keyboard.

[0110] The sound output device 655 can output a sound signal to the outside of the electronic device 601. The sound output device 655 can include, for example, a speaker or a receiver. The speaker can be used for general purposes, such as playing multimedia or making a recording, and the receiver can be used to receive an incoming call. The receiver can be implemented separately from the speaker or as part of the speaker.

[0111] The display device 660 can visually provide information to the outside of the electronic device 601 (e.g., to a user). The display device 660 can include, for example, a display, a hologram device, or a projector, as well as control circuitry for controlling the corresponding one of the display, the hologram device, and the projector. The display device 660 can include touch circuitry adapted to detect a touch or sensor circuitry (e.g., a pressure sensor) adapted to measure the intensity of a force generated by the touch.

[0112] The audio module 670 can convert sound into an electrical signal and vice versa. The audio module 670 can obtain sound via the input device 650 or output sound via the sound output device 655 or headphones of an external electronic device 602 directly (e.g., wired) or wirelessly coupled to the electronic device 601.

[0113] The sensor module 676 can detect an operating state of the electronic device 601 (e.g., power or temperature) or an environmental state outside the electronic device 601 (e.g., the state of a user), and then generate an electrical signal or data value corresponding to the detected state. The sensor module 676 can include, for example, a gesture sensor, a gyro sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0114] Interface 677 can support one or more specified protocols to be used in electronic device 601 to be coupled directly (e.g., wired) or wirelessly to external electronic device 602. Interface 677 can include, for example, a high-definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.

[0115] Connection terminal 678 can include a connector via which electronic device 601 can be physically connected to external electronic device 602. Connection terminal 678 can include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0116] Haptic module 679 can convert an electrical signal into a mechanical stimulus (e.g., vibration or movement) or an electrical stimulus that can be recognized by a user through touch or kinesthesia. Haptic module 679 can include, for example, a motor, a piezoelectric element, or an electrical stimulator.

[0117] Camera module 680 can capture still images or moving images. Camera module 680 can include one or more lenses, an image sensor, an image signal processor, or a flash. Power management module 688 can manage the power supplied to electronic device 601. Power management module 688 can be implemented as at least a part of, for example, a power management integrated circuit (PMIC).

[0118] Battery 689 can supply power to at least one component of electronic device 601. Battery 689 can include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0119] The communication module 690 can support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 601 and an external electronic device (e.g., the external electronic device 602, the external electronic device 604, or the server 608), and perform communication via the established communication channel. The communication module 690 can include one or more communication processors capable of operating independently of the processor 620 (e.g., the AP) and support direct (e.g., wired) communication or wireless communication. The communication module 690 can include a wireless communication module 692 (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 694 (e.g., a local area network (LAN) communication module or a power line communication (PLC) module). A corresponding one of these communication modules can communicate with the external electronic device via a first network 698 (e.g., a short-range communication network, such as BluetoothTM, wireless-fidelity (Wi-Fi) Direct, or the standard of the Infrared Data Association (IrDA)) or a second network 699 (e.g., a long-range communication network, such as a cellular network, the Internet, or a computer network (e.g., a LAN or a wide area network (WAN))). These various types of communication modules can be implemented as a single component (e.g., a single IC), or can be implemented as multiple components separated from each other (e.g., multiple ICs). The wireless communication module 692 can use the user information (e.g., the international mobile subscriber identity (IMSI)) stored in the user identification module 696 to identify and authenticate the electronic device 601 in a communication network (e.g., the first network 698 or the second network 699).

[0120] The antenna module 697 can transmit signals or power to the outside of the electronic device 601 (e.g., an external electronic device), or receive signals or power from the outside of the electronic device 601 (e.g., an external electronic device). The antenna module 697 can include one or more antennas, and for example, the communication module 690 (e.g., the wireless communication module 692) can select at least one antenna suitable for a communication scheme to be used in a communication network (e.g., the first network 698 or the second network 699) from the one or more antennas. Then, signals or power can be transmitted or received between the communication module 690 and the external electronic device via the selected at least one antenna.

[0121] Commands or data can be transmitted or received between the electronic device 601 and the external electronic device 604 via the server 608 coupled to the second network 699. Each of the external electronic devices 602 and 604 can be a device of the same type or a different type from the electronic device 601. All or some of the operations to be performed at the electronic device 601 can be performed at one or more of the external electronic devices 602, 604, or the server 608. For example, if the electronic device 601 should perform a function or service automatically or in response to a request from a user or another device, the electronic device 601 can request one or more of the external electronic devices to perform at least a part of the function or service instead of performing the function or service itself, or in addition to performing the function or service itself, also request one or more of the external electronic devices to perform at least a part of the function or service. The one or more external electronic devices that receive the request can perform at least a part of the requested function or service, or additional functions or additional services related to the request, and transmit the result of the performance to the electronic device 601. The electronic device 601 can provide the result as at least a part of the response to the request with or without further processing of the result. For this purpose, for example, cloud computing technology, distributed computing technology, or client-server computing technology can be used.

[0122] FIG. 7 shows a system including a UE 705 and a gNB 710 that communicate with each other. The UE can include a radio 715 and a processing circuit (or processing component) 720, and the processing circuit 720 can perform various methods disclosed herein. For example, the processing circuit 620 can receive a transmission from the network node (gNB) 710 via the radio 715, and the processing circuit 720 can transmit a signal to the gNB 710 via the radio 715.

[0123] The embodiments of the subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware (including the structures disclosed in this specification and their equivalent structures), or in combinations of one or more of them. The embodiments of the subject matter described in this specification can be implemented as one or more computer programs (i.e., one or more modules of computer program instructions) encoded on a computer storage medium for execution by, or to control the operation of, data processing apparatus. As an alternative or in addition, the program instructions can be encoded on an artificially generated propagated signal (e.g., an electrical, optical, or electromagnetic signal generated by a machine) for execution by data processing apparatus, the artificially generated propagated signal being generated to encode information for transmission to a suitable receiver apparatus. A computer storage medium can be a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination thereof, or can include within a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination thereof. Additionally, although a computer storage medium is not a propagated signal, a computer storage medium can be a source or destination for computer program instructions encoded in an artificially generated propagated signal. A computer storage medium can also be one or more separate physical components or media (e.g., multiple compact discs (CDs), disks, or other storage devices), or can include within the one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices). Additionally, the operations described in this specification can be implemented as operations performed by data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources.

[0124] Although this specification may contain many specific implementation details, these implementation details should not be construed as limiting the scope of any claimed subject matter, but rather as illustrative of the specific features of particular embodiments. Certain features described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment can also be implemented separately or in any suitable subcombination in multiple embodiments. Additionally, although the features may be described above as acting in certain combinations and even initially claimed as such, in some cases, one or more features from the claimed combination can be removed from the combination, and the claimed combination can be directed to a subcombination or a variation of a subcombination.

[0125] Similarly, although the operations are depicted in the drawings in a particular order, this should not be construed as requiring that the operations be performed in the particular order shown or in sequential order, or that all of the illustrated operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Additionally, the separation of various system components in the above-described embodiments should not be understood to be required in all embodiments, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products.

[0126] Accordingly, specific embodiments of the subject matter have been described herein. Other embodiments are within the scope of the following claims. In some instances, the actions recited in the claims can be performed in a different order and still achieve the desired result. Additionally, the processes depicted in the figures do not necessarily require the particular order shown or sequential order to achieve the desired result. In certain implementations, multitasking and parallel processing may be advantageous.

[0127] As those skilled in the art will recognize, the innovative concepts described herein can be modified and varied in a wide range of applications. Accordingly, the scope of the claimed subject matter should not be limited to any of the specific exemplary teachings discussed above, but is defined by the following claims.

[0128] Abbreviations AoA / AoD: Angle of Arrival / Angle of Departure BWP: Bandwidth Part E-CID: Enhanced Cell ID FR1 / FR2: Frequency Range 1 / Frequency Range 2 LMF: Location Management Function LPP: LTE Positioning Protocol PRS: Positioning Reference Signal PRS-RSRP: PRS Reference Signal Received Power PRS-RSRPP: PRS Reference Signal Received Path Power RedCap UE: Reduced-Capability UE SCS: Subcarrier Spacing SRS: Sounding Reference Signal SRS-RSRP: SRS Reference Signal Received Power SRS-RSRPP: SRS Reference Signal Received Path Power TRP: Transmit and Receive Point UE: User Equipment

[0129] 100, 705: UE 102: Next-generation Node B (gNB) Server 104: Location Server 302, 304, 306, 308, 310, 312, 314, 316, 318, 402, 404, 406, 408, 410, 502, 504, 506, 508: Steps 600: Network Environment 601: Electronic Device 602, 604: External Electronic Devices 608: Server 620: Processor 621: Main Processor 623: Auxiliary Processor 630: Memory 632: Volatile Memory 634: Non-volatile Memory 636: Internal Memory 638: External Memory 640: Program 642: Operating System (OS) 644: Middleware 646: Application 650: Input Device 655: Sound Output Device 660: Display Device 670: Audio Module 676: Sensor Module 677: Interface 678: Connection Terminal 679: Haptic Module 680: Camera Module 688: Power Management Module 689: Battery 690: Communication Module 692: Wireless Communication Module 694: Wired Communication Module 696: Subscriber Identity Module (SIM) 697: Antenna Module 698: First Network 699: Second Network 710: Network Node (gNB) 715: Radio 720: Processing circuit / processing component

Claims

1. A positioning method, comprising: The user equipment (UE) receives a radio resource control (RRC) signal that includes a measurement request; The user equipment receives at least two positioning reference signals (PRS), each of which corresponds to a different portion of the operating frequency range; determines that the at least two positioning reference signals can be coherently combined based on one or more channel parameters; aggregates the at least two positioning reference signals by the user equipment during a measurement interval; and reports the measurement based on the aggregation of the at least two positioning reference signals by the user equipment.

2. The positioning method as described in claim 1, wherein the one or more channel parameters include channel synchronization time.

3. The positioning method as described in claim 1, wherein the one or more channel parameters include clock drift and timing interval between the different portions of the operating frequency range.

4. The positioning method as described in claim 1, wherein the measurement based on the aggregation is reported to the Location Management Function (LMF).

5. The positioning method as described in claim 1, wherein each of the at least two positioning reference signals is a narrowband positioning reference signal.

6. The positioning method as described in claim 1, wherein the user equipment is a Reduced Capability (RedCap) user equipment or a Low Power High Accuracy Positioning (LPHAP) user equipment.

7. The positioning method as described in Request 1, wherein the at least two positioning reference signals are configured by a location management function.

8. The positioning method as described in claim 1 further includes having the Transmitter Receiver Point (TRP) measure the Uplink Detection Reference Signal-Reference Signal Received Power (UL SRS-RSRP), the Uplink Detection Reference Signal-Reference Signal Path Power (UL SRS-RSRPP), and the Uplink Relative Time of Arrival (UL RTOA) and report the Uplink Detection Reference Signal-Reference Signal Received Power, the Uplink Detection Reference Signal-Reference Signal Path Power, and the Uplink Relative Time of Arrival to the Location Management Function.

9. The positioning method as described in claim 8 further includes a difference report reported by the transmitting and receiving point, the difference report including the differences between previously measured uplink probe reference signal-reference signal received power, uplink probe reference signal-reference signal path power, and uplink relative arrival time and subsequently measured uplink probe reference signal-reference signal received power, uplink probe reference signal-reference signal path power, and uplink relative arrival time.

10. The positioning method as described in claim 8 further includes the user equipment reporting downlink positioning reference signal-reference signal received power (DL PRS-RSRP) and downlink positioning reference signal-reference signal path power (DL PRS-RSRPP) to the location management function.

11. The positioning method as described in Request 1, wherein the measurement described in the report is performed using Configuration Authorization (CG).

12. A positioning method, comprising: The user equipment (UE) receives a radio resource control (RRC) signal that includes a measurement request; The user equipment receives configuration from the location management function (LMF) to report the aggregated bandwidth; the user equipment receives multiple positioning reference signals (PRS), each of which corresponds to a different portion of the operating frequency range; it is determined that the multiple positioning reference signals can be coherently combined; the user equipment performs measurements within a measurement interval based on the determined maximum aggregated bandwidth of the received multiple positioning reference signals; And the maximum aggregate bandwidth determined by the user equipment reporting to the location management function.

13. The positioning method as described in claim 12 further includes reporting the measurement to the location management function.

14. The positioning method as described in claim 12, wherein the maximum aggregation bandwidth is determined more based on channel coherence time.

15. The positioning method as described in claim 12, wherein the maximum aggregate bandwidth is determined based on at least one of clock drift and timing interval between the different portions of the operating frequency range.

16. The positioning method as described in claim 12, wherein the user equipment is a Reduced Capability (RedCap) user equipment or a Low Power High Accuracy Positioning (LPHAP) user equipment.

17. The positioning method as described in claim 12, wherein the plurality of positioning reference signals are received from a network server.

18. The positioning method as described in claim 12, wherein the maximum aggregate bandwidth is reported as the number of frequency hopping.

19. The positioning method as described in claim 12 further includes having a transmit receiving point (TRP) measure the uplink probe reference signal-to-reference signal received power (UL SRS-RSRP), the uplink probe reference signal-to-reference signal path power (UL SRS-RSRPP), and the uplink relative time of arrival (UL RTOA) and report the uplink probe reference signal-to-reference signal received power, the uplink probe reference signal-to-reference signal path power, and the uplink relative time of arrival to the location management function.

20. The positioning method as described in claim 19 further includes a difference report reported by the transmitting and receiving point, the difference report including the differences between previously measured uplink probe reference signal-reference signal received power, uplink probe reference signal-reference signal path power, and uplink relative arrival time and subsequently measured uplink probe reference signal-reference signal received power, uplink probe reference signal-reference signal path power, and uplink relative arrival time.

21. The positioning method as described in claim 19 further includes the user equipment reporting downlink positioning reference signal-to-reference signal received power (DL PRS-RSRP) and downlink positioning reference signal-to-reference signal path power.

22. The positioning method as described in request item 12, wherein the measurement described in the report is performed using configuration authorization (CG).

Images