Positioning scheme in wireless communication

By using jump technology in 5G-NR systems to expand effective bandwidth, the problem of insufficient positioning accuracy of RedCap UE in harsh environments is solved, and higher positioning accuracy and more efficient resource utilization are achieved.

CN119072987APending Publication Date: 2024-12-03ZTE CORP

Patent Information

Application Number
CN202380035185.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-01-17
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

The existing 5G-NR positioning scheme lacks positioning accuracy for RedCap UE in harsh environments, especially in dense urban areas and underground parking lots, which are difficult to meet the one-meter commercial requirements, and the existing technology uses network resource utilization and systems. Spectral efficiency and operational efficiency have adverse effects.

Method used

By adopting the jump technology in the wireless communication system, the jump transmission is performed using the positioning reference signals (PRS and SRS) between the user equipment and the base station, expanding the effective bandwidth and improving the positioning accuracy. Specific measures include configuring multi-segment jumps, optimizing measurement intervals and processing windows, prioritizing the processing of positioning reference signals, and using technologies such as carrier switching and antenna switching to ensure positioning performance.

Benefits of technology

It improves the positioning accuracy of RedCap UE, meets one meter of commercial requirements, reduces the adverse impact on network resources, and improves the system spectrum efficiency and operation efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119072987A_ABST
    Figure CN119072987A_ABST
Patent Text Reader

Abstract

A method of wireless communication is provided. The method comprises: receiving, by a user equipment, configuration information for configuring a positioning reference signal from a network device; performing a measurement on the positioning reference signal; and reporting a measurement result of the measurement.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This document relates to systems, devices, and techniques for wireless communications. Background Art

[0002] There are currently efforts underway to define the next generation of wireless communication networks that provide greater deployment flexibility, support a large number of devices and multiple services as well as different technologies for efficient system evolution. Summary of the invention

[0003] Various methods and apparatuses are provided for providing a positioning solution in a wireless communication system.

[0004] In one example aspect, a method of wireless communication is disclosed. The method includes receiving, by a user equipment, configuration information for configuring a positioning reference signal from a network equipment; performing measurement on the positioning reference signal; and reporting a measurement result of the measurement.

[0005] In another example aspect, a method of wireless communication is disclosed. The method includes configuring, by a base station, a reference signal for positioning; performing measurement on the reference signal for positioning; and reporting a measurement result of the measurement.

[0006] In yet another example aspect, a wireless communication apparatus including a processor is disclosed. The processor is configured to implement the method described herein.

[0007] In another example aspect, the various techniques described herein may be embodied as processor-executable code and stored on a computer-readable program medium.

[0008] The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features will be apparent from the description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 An example diagram illustrating a downlink (DL) positioning scheme is shown.

[0010] Figure 2 An example diagram illustrating an uplink (UL) positioning scheme is shown.

[0011] Figure 3 Illustration of a diagram indicating positioning accuracy for a UE supporting hopping.

[0012] Figure 4 An example of SRS transmission based on some implementations of the disclosed technology is described, including the first to fifth partial transmissions.

[0013] Figure 5 An example of a hopping pattern with two allocated symbols based on some implementations of the disclosed technology is described.

[0014] Figure 6 Examples of resources based on some implementations of the disclosed technology are described, which are transmitted with two symbols on a first antenna and a second (virtual) antenna.

[0015] Figure 7 is a block diagram of an example of a wireless communication device.

[0016] Figure 8 An example wireless communication network is shown.

[0017] Fig. 9 and Fig.10 is an example flow chart of a wireless communication method based on some implementations of the disclosed technology. DETAILED DESCRIPTION

[0018] The disclosed technology provides implementations and examples of positioning solutions with improved positioning accuracy for RedCap UEs.

[0019] The section headings used in this document are intended only to improve readability and do not limit the scope of the embodiments and techniques disclosed in each section to only that section. In addition, for ease of understanding, some embodiments are described with reference to the 3rd Generation Partnership Project (3GPP) New Radio (NR) standard ("5G"), and the described techniques may be implemented in different wireless systems that implement protocols other than the 5G protocol.

[0020] At present, there are some requirements for positioning. For example, in a parking lot (especially an underground parking lot), it is not easy to find a car (especially during peak hours). The fifth generation mobile communication system (5G, new radio access technology, 5G-NR) provides a positioning method including a positioning reference signal (PRS, from a base station gNB) and a sounding reference signal (SRS, from a user equipment UE) on the radio side.

[0021] Some implementations of the disclosed technology may be used to support a class of NR UEs with lower complexity and power consumption levels than Rel-15 NR UEs. It is expected that a class of reduced capability (RedCap) NR user equipment (UE) will be defined that can be served using the currently specified 5G NR framework together with necessary adaptations and enhancements to limit the complexity and power consumption of the device while minimizing any adverse impact on network resource utilization, system spectrum efficiency, and operational efficiency.

[0022] For UEs with reduced capabilities (RedCap), there are restrictions on the receive / transmit bandwidth, such as 20MHz in frequency range 1 (FR1). In some examples, the receive / transmit bandwidth in the 700MHz band can even be limited to 5MHz. Positioning accuracy is highly related to the bandwidth of the reference signal used for positioning. In some cases, a RedCap UE has only one receive / transmit antenna (e.g. in frequency range 1 FR1), which also reduces positioning accuracy.

[0023] The positioning accuracy of the existing 5G-NR based positioning solution for RedCap UE may not be high enough (e.g., 3 meters or less). In some harsh environments (e.g., dense urban areas), the positioning accuracy of the existing 5G-NR based positioning solution for RedCap UE may be lower. In some business situations, a positioning accuracy of one meter is required. In some cases, it is difficult to achieve some business requirements (e.g., one meter) through the existing 5G-NR based positioning solution for RedCap UE. In this regard, some implementations of the disclosed technology are related to technologies for improving positioning accuracy based on 5G-NR positioning, particularly for RedCap UE.

[0024] Figure 1 An example diagram illustrating a downlink (DL) positioning scheme is shown. Figure 1 In the downlink (DL) positioning shown, the PRS is transmitted by one or more gNBs. In some examples, multiple gNBs are involved to achieve "good" positioning accuracy. In some examples, three base stations are used. The number of multiple gNBs is not limited to three, and other implementations are also possible. The UE measures the PRS (positioning reference signal) and reports the measurement results to the network (e.g., the location management function LMF in the core network CN, 5G CN, 5GC). It should be noted that the network elements include gNB, CN and UE. In some implementations, the UE can connect the segments (hops) of the PRS and perform measurements on the connected PRS.

[0025] Figure 2 An example diagram illustrating an uplink (UL) positioning scheme is shown. Figure 2 In the uplink (UL) positioning shown, SRS is transmitted by a UE. One or more gNBs measure the SRS and report the measurement results to the network (e.g. LMF).

[0026] The transmission of PRS and SRS for positioning purposes is easily affected by the wireless propagation environment (eg, attenuation, distortion), which may reduce the positioning accuracy.

[0027] Various implementations of the disclosed technology provide positioning solutions with improved positioning accuracy compared to those available in conventional technologies. Since RedCap UE can only support limited bandwidth (e.g., 20 MHz or 5 MHz in FR1), multiple segments (hops) can be applied to RedCap UE. A segment (hop) may refer to the transmission of a reference signal over a specified frequency range at a specified time. The following is an example of two segments (two hops): when the first segment (hop) is transmitted at 2000 MHz to 2020 MHz (with a 20 MHz bandwidth) at the first millisecond, then after a period of time, the second segment (hop) is transmitted at 2020 MHz to 2040 MHz (with a 20 MHz bandwidth) at the second millisecond. RedCap UE can receive / transmit multiple hops at different frequencies and different times to form an equivalent high bandwidth. For frequency hopping (including transmission hopping and reception hopping), some unexpected problems may occur, such as random phases of each hop, large delays, etc. Some implementations of the disclosed technology provide techniques for avoiding and / or overcoming the unexpected problems.

[0028] Implementation Example 1: UL-SRS Hopping / DL-PRS Hopping

[0029] In the following description, SRS transmission is used as an example, but the proposed implementation can also be applied to PRS transmission. When the implementation is applied to SRS transmission, it can be called UL-SRS hopping. When the implementation is applied to PRS transmission, it can be called DL-PRS hopping.

[0030] For RedCap UE, SRS transmission (or PRS transmission) can be hopping or non-hopping in frequency within the activated bandwidth part (BWP). Hopping may refer to an event when a transmission is transferred from one bandwidth or frequency range to another bandwidth or frequency range. Since the SRS transmission (or PRS transmission) is hopping within the activated BWP, the bandwidth range (or frequency range) after the hopping is within the activated BWP.

[0031] For each SRS transmission (or PRS reception), there is downlink control information (DCI) to trigger the SRS transmission (or PRS reception). In some implementations, there is only one DCI to trigger all SRS transmissions with hopping (or all PRS receptions with hopping, that is, one DCI is used for all hopping). In some implementations, the bitmap on the DCI will indicate which hop of the SRS transmission (or PRS reception) is triggered. In some implementations, the code point on the DCI (e.g., the possible code points "0", "1", "2", "3" of two bits) will indicate which hop of the SRS transmission (or PRS reception) is triggered. In some implementations, the media access control (MAC) control element (CE) will indicate which hop of the SRS transmission (or PRS reception) is triggered.

[0032] In some implementations, there is a transmission window (or transmission interval, e.g., duration / period, e.g., 20 ms, 40 slots) for hopping SRS transmissions. The gNB (or LMF) may configure the transmission window. If the transmission window is not configured, the RedCap UE will not perform hopping SRS transmissions outside its operating bandwidth (e.g., 20 MHz, e.g., within its operating bandwidth with normal non-hopping SRS transmissions). In some implementations, the MAC CE may enable / disable the transmission window. In some implementations, the UE may request the MAC CE to enable / disable the transmission window. In some implementations, the UE may request a MAC CE on hopping SRS transmissions.

[0033] For the case of subcarrier spacing (SCS) = 15kHz and 50MHz bandwidth, there are N RB = 270 RBs (RB#0, 1, 2, ... 268, 269). RB#0 can be a common RB, a CRB, or CRB0. For the case of SCS = 15 kHz and 100 MHz bandwidth, there are N RB =2*270=540RB (RB#0, 1, 2, ... 268, 269, 270, 271, ... 539). For the case of SCS=15kHz and 20MHz bandwidth supporting RedCap UE, in order to support an aggregate bandwidth of 100MHz after hopping, there will be N with one or more overlapping RBs between two consecutive hops. Hopping =5 hops. The RBs of the first hop (of RedCap UE) may be RB#0, 1, 2, ... 103 (with respect to CRB, or CRB0, a total of 104 RBs for PRS / SRS). A BWP, or a virtual BWP, or a first BWP or a first virtual BWP may be configured with these RBs.

[0034] In addition, the bandwidth of PRS / SRS is not greater than the bandwidth of BWP. In some implementations, the hop is transmitted / received within the BWP or virtual BWP. The RBs of the second hop (of RedCap UE) can be RB#103, 104, 105...206 (with respect to CRB or CRB0, with one overlapping RB on RB#103 on the previous hop, and one overlapping RB on RB#206 on the next hop). BWP, or virtual BWP, or second BWP, or second virtual BWP can be configured with these RBs.

[0035] The RB of the third hop (of RedCap UE) may be RB#206, 207, 208...309 (with respect to CRB or CRB0, having an overlapping RB on RB#206 on the previous hop. A BWP or a virtual BWP or a third BWP or a third virtual BWP may be configured with these RBs). The RB of the fourth hop (of RedCap UE) may be RB#309, 310, 311...412 (with respect to CRB or CRB0 or ​​a virtual CRB or a virtual CRB0, having an overlapping RB on RB#309 on the previous hop. A BWP or a virtual BWP or a fourth BWP or a fourth virtual BWP may be configured with these RBs). The RB of the fifth hop (of RedCap UE) may be RB#412, 413, 414...515 (with respect to CRB or CRB0, having an overlapping RB on RB#412 on the previous hop. A BWP or a virtual BWP or a fifth BWP or a fifth virtual BWP may be configured with these RBs).

[0036] In some implementations, the subcarriers of the hopped SRS transmission (or hopped PRS reception) start from the lowest subcarrier of the BWP to which it belongs.

[0037] For SCS = 30kHz and 100MHz bandwidth, there is N RB = 273 RBs (RB#0, 1, 2, ... 271, 272. RB#0 can be a common RB, CRB, or CRB0). For the case of SCS=30kHz and 20MHz bandwidth supporting RedCap UE, in order to support an aggregate bandwidth of 100MHz after hopping, there will be N with one or more overlapping RBs between two consecutive hops. Hopping=5. The RB of the first hop (of RedCap UE) can be RB#0, 1, 2...54 (relative to CRB or CRB0, there are 55 RBs in total. BWP or virtual BWP or first BWP or first virtual BWP can be configured with these RBs). The RB of the second hop (of RedCap UE) can be RB#54, 55, 56...108 (relative to CRB or CRB0, there is an overlapping RB on RB#54 on the previous hop, and there is an overlapping RB on RB#108 on the next hop. BWP or virtual BWP or second BWP or second virtual BWP can be configured with these RBs). The RB of the third hop (of RedCap UE) can be RB#108, 109, 110...162 (relative to CRB or CRB0, there is an overlapping RB on RB#108 on the previous hop. BWP or virtual BWP or third BWP or third virtual BWP can be configured with these RBs). The RBs of the fourth hop (of RedCap UE) may be RB#162, 163, 164...216 (with respect to CRB or CRB0, having one overlapping RB on RB#162 on the previous hop. The BWP or virtual BWP or fourth BWP or fourth virtual BWP may be configured with these RBs). The RBs of the fifth hop (of RedCap UE) may be RB#216, 217, 218...270 (with respect to CRB or CRB0, having one overlapping RB on RB#216 on the previous hop. The BWP or virtual BWP or fifth BWP or fifth virtual BWP may be configured with these RBs).

[0038] In some implementations, the starting RB ID of the first hop may be moved to 1 (i.e., RB#1). In some implementations, the RBs of the first hop (of RedCap UE) may be RB#1, 2, 3, ...55 (a total of 55 RBs relative to CRB or CRB0). The RBs of the second hop (of RedCap UE) may be RB#55, 56, 57, ...109 (with one overlapping RB on RB#55 on the previous hop relative to CRB or CRB0). The RBs of the third hop (of RedCap UE) may be RB#109, 110, 111, ...163 (with one overlapping RB on RB#109 on the previous hop relative to CRB or CRB0). The RBs of the fourth hop (of RedCap UE) may be RB#163, 164, 165, ...217 (with one overlapping RB on RB#163 on the previous hop relative to CRB or CRB0). The RB of the fifth hop (of RedCap UE) may be RB#217, 218, 219, ... 271 (with respect to CRB or CRB0, having one overlapping RB on RB#217 on the previous hop).

[0039] In some implementations, the starting RB ID of the first hop may be moved to 2 (i.e., RB#2). In some implementations, the RBs of the first hop (of RedCap UE) may be RB#2, 3, 4, ...56 (a total of 55 RBs relative to CRB or CRB0). The RBs of the second hop (of RedCap UE) may be RB#56, 57, 58, ...110 (with an overlapping RB on RB#56 on the previous hop relative to CRB or CRB0). The RBs of the third hop (of RedCap UE) may be RB#110, 111, 112, ...164 (with an overlapping RB on RB#110 on the previous hop relative to CRB or CRB0). The RBs of the fourth hop (of RedCap UE) may be RB#164, 165, 166, ...218 (with an overlapping RB on RB#164 on the previous hop relative to CRB or CRB0). The RBs of the fifth hop (of RedCap UE) may be RB#218, 219, 220, ... 272 ​​(with respect to CRB or CRB0, having one overlapping RB on RB#218 on the previous hop).

[0040] In some implementations, the bandwidth (number of RBs) of a hop needs to be a multiple of 4 (e.g., 48 RBs). In some implementations, the number of RBs may be indicated as 4*(n-1)+24 (e.g., at least 24 RBs, where n is an integer, e.g., n=7, for a total of 48 RBs). In some implementations, the RBs of the first hop (of a RedCap UE) may be RB#0, 1, 2, ...47 (for a total of 48 RBs relative to CRB or CRB0). The RBs of the second hop (of a RedCap UE) may be RB#47, 48, 49, ...94 (with one overlapping RB on RB#47 on the previous hop, relative to CRB or CRB0). The RBs of the third hop (of a RedCap UE) may be RB#94, 95, 96, ...141 (with one overlapping RB on RB#94 on the previous hop, relative to CRB or CRB0). The RB of the fourth hop (of RedCap UE) may be RB#141, 142, 143, ... 188 (with respect to CRB or CRB0, having one overlapping RB on RB#141 on the previous hop). The RB of the fifth hop (of RedCap UE) may be RB#188, 189, 190, ... 235 (with respect to CRB or CRB0, having one overlapping RB on RB#188 on the previous hop).

[0041] In some implementations, the RBs of the first hop (of the RedCap UE) may be RB#0, 1, 2, ... 51 (with respect to CRB or CRB0, a total of 52 RBs). The RBs of the second hop (of the RedCap UE) may be RB#51, 52, 53, ... 102 (with respect to CRB or CRB0, having an overlapping RB on RB#51 on the previous hop). The RBs of the third hop (of the RedCap UE) may be RB#102, 103, 104, ... 153 (with respect to CRB or CRB0, having an overlapping RB on RB#102 on the previous hop). The RBs of the fourth hop (of the RedCap UE) may be RB#153, ​​154, 155, ... 204 (with respect to CRB or CRB0, having an overlapping RB on RB#153 on the previous hop). The RB of the fifth hop (of RedCap UE) may be RB#204, 205, 206, ... 255 (with respect to CRB or CRB0, having one overlapping RB on RB#204 on the previous hop).

[0042] In some implementations, a mixed number of RBs (i.e., different numbers of RBs) may be applied to different hops (e.g., 48 RBs for the first hop and 56 RBs for other hops). In some implementations, the RBs for the first hop (of a RedCap UE) may be RB#0, 1, 2, ...47 (for a total of 48 RBs relative to CRB or CRB0). The RBs for the second hop (of a RedCap UE) may be RB#47, 48, 49, ...102 (with one overlapping RB on RB#47 on the previous hop, for a total of 56 RBs relative to CRB or CRB0). The RBs for the third hop (of a RedCap UE) may be RB#102, 103, 104, ...157 (with one overlapping RB on RB#102 on the previous hop, for a total of 56 RBs relative to CRB or CRB0). The RBs of the fourth hop (of RedCap UE) may be RB#157, 158, 159, ... 212 (with respect to CRB or CRB0, having one overlapping RB on RB#157 on the previous hop, for a total of 56 RBs). The RBs of the fifth hop (of RedCap UE) may be RB#212, 213, 214, ... 267 (with respect to CRB or CRB0, having one overlapping RB on RB#212 on the previous hop, for a total of 56 RBs).

[0043] In some implementations, a mixed number of RBs (i.e., different numbers of RBs) may be applied to different hops (e.g., 52 RBs for the first hop and 56 RBs for other hops). In some implementations, the RBs for the first hop (of a RedCap UE) may be RB#0, 1, 2, ...51 (52 RBs in total relative to CRB or CRB0). The RBs for the second hop (of a RedCap UE) may be RB#51, 52, 53 ...106 (with one overlapping RB on RB#51 on the previous hop, with a total of 56 RBs relative to CRB or CRB0). The RBs for the third hop (of a RedCap UE) may be RB#106, 107, 108, ...161 (with one overlapping RB on RB#106 on the previous hop, with a total of 56 RBs relative to CRB or CRB0). The RBs of the fourth hop (of RedCap UE) may be RB#161, 162, 163, ... 216 (with respect to CRB or CRB0, having one overlapping RB on RB#161 on the previous hop, for a total of 56 RBs). The RBs of the fifth hop (of RedCap UE) may be RB#216, 217, 218, ... 271 (with respect to CRB or CRB0, having one overlapping RB on RB#212 on the previous hop, for a total of 56 RBs).

[0044] In some implementations, the number of overlapping RBs may be 0, or 1, or 2, or 3, or 4, or a number configured by the network. In some implementations, the RBs of the first hop (of the RedCap UE) may be RB#0, 1, 2...51 (52 RBs in total relative to CRB or CRB0). The RBs of the second hop (of the RedCap UE) may be RB#50, 51, 52,...101 (with one overlapping RB on RB#50 and RB#51 on the previous hop relative to CRB or CRB0). The RBs of the third hop (of the RedCap UE) may be RB#101, 102, 103,...152 (with one overlapping RB on RB#101 and RB#102 on the previous hop relative to CRB or CRB0). The RB of the fourth hop (of RedCap UE) may be RB#152, 153, 154, ... 203 (with respect to CRB or CRB0, having one overlapping RB on RB#152 and RB#153 on the previous hop). The RB of the fifth hop (of RedCap UE) may be RB#203, 204, 205, ... 254 (with respect to CRB or CRB0, having one overlapping RB on RB#203 and RB#204 on the previous hop).

[0045] For the case where SCS=60kHz and 20MHz bandwidth support RedCap UE, in some implementations, the RBs of the first hop (of the RedCap UE) may be RB#0, 1, 2, ...23 (a total of 24 RBs relative to CRB or CRB0). The RBs of the second hop (of the RedCap UE) may be RB#23, 24, 25, ...46 (with an overlapping RB on RB#23 on the previous hop relative to CRB or CRB0). The RBs of the third hop (of the RedCap UE) may be RB#46, 47, 48, ...69 (with an overlapping RB on RB#46 on the previous hop relative to CRB or CRB0). The RBs of the fourth hop (of the RedCap UE) may be RB#69, 70, 71, ...92 (with an overlapping RB on RB#92 on the previous hop relative to CRB or CRB0). The RBs of the fifth hop (of RedCap UE) may be RB#92, 93, 94, ... 115 (with respect to CRB or CRB0, having one overlapping RB on RB#92 on the previous hop).

[0046] For the case of supporting RedCap UE with 20MHz bandwidth, at SCS of 15, 30, and 60kHz, the maximum number of RBs in a hop is 104, 48, and 24, respectively. Therefore, floor(Number_of_RB_at_20MHz / 4)*4, where Number_of_RB_at_20MHz is the number of RBs at 20MHz.

[0047] For the case of SCS=15kHz and 5MHz bandwidth supporting RedCap UE, there will be Number_of_RB_at_100MHz / (floor(Number_of_RB_at_5MHz / 4)*4-1)=2*Number_of_RB_at_50MHz / (floor(Number_of_RB_at_5MHz / 4)*4-1)=2*270 / (24-1)=23 hops, where there are 24 RBs in each hop and there is one overlapping RB between two adjacent hops.

[0048] In some implementations, for the case of SCS=15kHz and 5MHz bandwidth supporting RedCap UE, there will be Number_of_RB_at_100MHz / (floor(Number_of_RB_at_5MHz / 4)*4-2)=2*Number_of_RB_at_50MHz / (floor(Number_of_RB_at_5MHz / 4)*4-2)=2*270 / (24-2)=24 hops, where there are 24 RBs in each hop and there are two overlapping RBs between two adjacent hops.

[0049] In some implementations, when SCS=15kHz and 5MHz bandwidth supports RedCap UE, there are at most 32 hops. In some implementations, when SCS=15kHz and 5MHz bandwidth supports RedCap UE, there are at most 24 hops, and there are two overlapping RBs between two adjacent hops.

[0050] For SCS=30kHz and 5MHz bandwidth supporting RedCap UE, there will be Number_of_RB_at_100MHz / (ceil(Number_of_RB_at_5MHz / 4)*4-1)=273 / (12-1)=24 hops, with 12 RBs in each hop and one overlapping RB between two adjacent hops.

[0051] Support for RedCap UE for SCS=60kHz and 5MHz bandwidth, this configuration is not supported.

[0052] For SCS=60kHz and 10MHz bandwidth supporting RedCap UE, there will be Number_of_RB_at_100MHz / (ceil(Number_of_RB_at_10MHz / 4)*4-1)=135 / (12-1)=12 hops, where there are 12 RBs in each hop and there is one overlapping RB between two adjacent hops.

[0053] For SCS=60kHz and 50MHz bandwidth supporting RedCap UE (on, frequency range 2, FR2), there will be 2 hops, with 64 RBs for PRS / SRS in each hop, and one overlapping RB (eg, RB#63) between two adjacent hops.

[0054] For SCS=120kHz and 50MHz bandwidth supporting RedCap UE (on, frequency range 2, FR2), there will be 2 hops, with 32 RBs for PRS / SRS in each hop, and there is one overlapping RB (eg, RB#31) between two adjacent hops.

[0055] Support for RedCap UE (ON, frequency range 2, FR2) for SCS=60kHz and 100MHz bandwidth, this configuration is not supported. In some implementations, there will be 2 hops with 132 RBs in each hop and one overlapping RB (on RB#131) between two adjacent hops.

[0056] Support for RedCap UE (ON, frequency range 2, FR2) for SCS=120kHz and 100MHz bandwidth, this configuration is not supported. In some implementations, there will be 2 hops with 64 RBs in each hop and one overlapping RB (on RB#63) between two adjacent hops.

[0057] In some implementations, the hops may start from a higher frequency to a lower frequency. For example, for SCS=60kHz and 50MHz bandwidth supporting RedCap UE (ON, frequency range 2, FR2), there will be 2 hops, with 64 RBs for PRS / SRS in each hop, and one overlapping RB between two adjacent hops (e.g., on RB#63). The first hop (of PRS / SRS) is on RB#63, 64, 65, ... 126 (relative to CRB or CRB0), and the second hop (of PRS / SRS) is on RB#0, 1, 2, ... 63 (relative to CRB or CRB0). In some implementations, the hops may start from a lower frequency (e.g., a small RB index) to a higher frequency (e.g., a large RB index).

[0058] In some implementations, the BWP ID in the DCI may be a hop ID (eg, 0, 1, 2, 3).

[0059] In some implementations, a receiver (e.g., a gNB) may receive each segment (or BWP or hop), adjust the phase of each segment, and connect the segments together. Afterwards, the receiver (e.g., a gNB) may measure / report positioning-related results on the connected segments. For example, the receiver configures the SRS for the UE. Then, the UE transmits the SRS (e.g., two hops, i.e., two transmissions on different frequencies). When the receiver receives the SRS of the two hops at different times, the receiver connects the SRS of the two hops. Then, the receiver measures the connected SRS.

[0060] In some implementations, for sidelink positioning, the UE may not transmit the sidelink PRS / SRS (regardless of hopping) even if requested by another UE (or the network, or an anchor UE, or a roadside unit RSU). In some implementations, the UE may stop transmitting the sidelink PRS / SRS even if the UE indicates that it has the ability to transmit the sidelink PRS / SRS. This can reduce the chance of a surge in the UE's own position.

[0061] According to the implementation, the hopping of SRS / PRS can be achieved by overlapping between hops (to adjust the coherent phase of the channel). Thus, the effective bandwidth can be expanded. Therefore, the positioning performance can be improved (eg, higher positioning accuracy).

[0062] Implementation Example 2: Jumping to a specific MG / PPW

[0063] For PRS reception, at least one of a measurement gap (MG) or a PRS processing window (PPW) may be configured for a RedCap UE. In an implementation, a hopping-specific MG / PPW (or referred to as a RedCap-specific MG / PPW) is configured for PRS reception (or PRS transmission). In such a hopping-specific MG / PPW, only hopping PRS may be received (or transmitted). Non-hopping PRS is received (or transmitted) only in a normal MG / PPW.

[0064] In some implementations, the first hop of the PRS hop is outside the MG / PPW (or hop-specific MG / PPW, or RedCap-specific MG / PPW), and the remaining hops of the PRS hop are inside the MG / PPW (or hop-specific MG / PPW, or RedCap-specific MG / PPW). In some implementations, the time interval between the first hop of the PRS hop and the MG / PPW is the hop interval (or radio frequency RF retuning time). In some implementations, the time interval between the first hop of the PRS hop and the MG / PPW is longer than the RF retuning time. In some implementations, the time interval between the first hop of the PRS hop and the MG / PPW is longer than the RF retuning time, but shorter than twice the RF retuning time.

[0065] In some implementations, the minimum duration of a MG / PPW (or a hop-specific MG / PPW, or a RedCap-specific MG / PPW) is: (floor(BW_PRS / BW_UE)-1)*RF_Re_tuning_Time, or (Hop_Number-1)*RF_Re_tuning_Time. In some implementations, the minimum duration of a MG / PPW (or a hop-specific MG / PPW, or a RedCap-specific MG / PPW) is: floor(BW_PRS / BW_UE)*RF_Re_tuning_Time, or Hop_Number*RF_Re_tuning_Time. BW_PRS is the bandwidth of PRS (e.g., expressed in number of RBs, such as 273RB@SCS=30kHz in 100MHz), BW_UE is the maximum bandwidth supported by RedCap UE (e.g., expressed in number of RBs, such as 51RB@SCS=30kHz in 20MHz), RF_Re_tuning_Time is the duration of RedCap UE switching from one frequency to another (or from one virtual BWP to another virtual BWP, such as one time slot), and Hop_Number is the hop number configured by higher layers. In some implementations, the minimum duration of MG / PPW (or hop-specific MG / PPW, or RedCap-specific MG / PPW) is: floor(BW_PRS / BW_UE)*(RF_Re_tuning_Time+PRS_Duration), or Hop_Number*(RF_Re_tuning_Time+PRS_Duration), where PRS_Duration is the duration of PRS transmission (or reception, or PRS measurement). In some implementations, PRS_Duration may be Number_of_Symbol*Duration_of_Symbol, where Number_of_Symbol is the number of symbols configured for PRS transmission (eg, two symbols), and Duration_of_Symbol is the duration of the symbol (eg, 35.7 μs@SCS=30 kHz).

[0066] In some implementations, for a hopping PRS, the minimum repetition period is the hopping interval (or RF retuning time). In some implementations, for a hopping PRS, the minimum repetition period is the sum of the hopping interval (or RF retuning time) and the PRS transmission (or reception) duration.

[0067] In some implementations, for a hopping PRS, the minimum repetition is: floor(BW_PRS / BW_UE) or Hop_Number.

[0068] In some implementations, for a MG (or a hop-specific MG, or a RedCap-specific MG), the PRS has the highest priority (i.e., the PRS takes precedence over all other DL signals / channels). In some implementations, for a MG (or a hop-specific MG, or a RedCap-specific MG), the PRS takes precedence over all other DL signals / channels except a synchronization signal block (SSB).

[0069] In some implementations, for PPW (or hopping specific PPW, or RedCap specific PPW), PRS has the highest priority (i.e., PRS takes precedence over all other DL signals / channels). In some implementations, for PPW (or hopping specific PPW, or RedCap specific PPW), PRS takes precedence over all other DL signals / channels except SSB. In some implementations, for PPW (or hopping specific PPW, or RedCap specific PPW), PRS takes precedence over all other DL signals / channels except SSB and physical downlink control channel (PDCCH) for ultra-reliable and low-latency communication (URLLC). In some implementations, within PPW (or hopping specific PPW, or RedCap specific PPW), PRS symbols for URLLC that overlap with SSB / PDCCH are discarded. In some implementations, within PPW (or hopping specific PPW, or RedCap specific PPW), time slots for URLLC that overlap with SSB / PDCCH are discarded. In some implementations, within a PPW (or a hopping-specific PPW, or a RedCap-specific PPW), PRS hopping for URLLC that overlaps with SSB / PDCCH is discarded.

[0070] In some implementations, both MG and PPW are configured for RedCap UE. In some implementations, some hops of PRS (e.g., the first two hops out of five hops) are performed in MG, while other hops of PRS (e.g., the last three hops out of five hops) are performed in PPW. In some implementations, if PRS takes precedence over all other DL signals / channels in MG, some hops of PRS are performed in MG, while other hops of PRS are performed in PPW. Using this approach, positioning performance is high enough, while the priority of other signals / channels can be maintained (in PPW).

[0071] In some implementations, within a PPW, a RedCap UE may handle one (virtual) carrier / positioning frequency layer (PFL). In some implementations, within a PPW, a RedCap UE may handle one (virtual) carrier / PEL at a time.

[0072] In some implementations, for a UE supporting carrier / PFL aggregation, multiple PPWs may be configured (eg, one PPW per carrier / PFL. These PPWs may have the same start / end time or duration).

[0073] In some implementations, the priority of the PRS for each (virtual) carrier / PFL may be different relative to other signals / channels within the PPW. For example, for a first carrier, the priority of the PRS may be higher than other signals / channels in the PPW, while for a second carrier, the priority of the PRS may be lower than other signals / channels in the PPW. In this case, the final priority of the PRS may depend on the highest priority of the PRS in each PPW (for each carrier). In some implementations, the final priority of the PRS may depend on the lowest priority of the PRS in each PPW (e.g., the lowest priority to be applied). In some implementations, the final priority of the PRS may depend on the priority of the PRS in the PPW of the first (virtual) carrier / PFL / hop / BWP / sub-BWP. In some implementations, the final priority of the PRS may depend on the priority of the PRS in the PPW of the last (virtual) carrier / PFL / hop / BWP / sub-BWP. In some implementations, the final priority of the PRS may depend on the priority of the PRS in the PPW of the first transmission / reception of the PRS. In some implementations, the final priority of the PRS may depend on the priority of the PRS in the PPW in which the PRS was last transmitted / received.

[0074] In some implementations, for a UE supporting carrier / PFL aggregation (e.g., four PFLs), multiple PPWs (e.g., two PPWs, each with two PFLs) may be configured. In some implementations, each PPW has a list of carriers / PFLs that the UE can handle at one time.

[0075] In some implementations, for a UE supporting carrier / PFL aggregation (e.g., five carriers), only one PPW is configured, wherein the PPW has a list of carriers / PFLs that the UE can handle at one time. In some implementations, the carrier / PFL list has a carrier ID (or cell ID).

[0076] In some implementations, the UE may report its PPW capabilities to the network.

[0077] In some implementations, a UE's PRS configuration may be shared by other UEs (even UEs in other cells, or UEs in inactive / idle states).

[0078] In some implementations, during a MG (or hop-specific MG, or RedCap-specific MG), there are one or more activated (virtual) BWP switches (or sub-BWP switches) for PRS reception. In some implementations, activated (virtual) BWP switches (or sub-BWP switches) are used to handle different hops of PRS.

[0079] In some implementations, multiple (concurrent) MGs may be configured for a UE. In some implementations, multiple (concurrent) MGs may be configured for a UE with multiple carriers / PFLs. In some implementations, each carrier / PFL may be associated with a specific MG. In some implementations, one carrier / PFL may be associated with a different MG from another MG for the carrier / PFL.

[0080] In some implementations, during a PPW (or a hop-specific PPW, or a RedCap-specific PPW), there are one or more active BWP switches for receiving PRS. In some implementations, active (virtual) BWP switches (or sub-BWP switches) are used to handle different hops of PRS within a PPW.

[0081] In this implementation, by utilizing hopping-specific MG / PPW (or RedCap-specific MG / PPW), DL signals / channels may be processed preferentially, and positioning performance (eg, higher positioning accuracy) may be improved compared to a non-hopping case.

[0082] Implementation Example 3: Component Carrier Level SRS

[0083] Currently, SRS is configured under BWP. SRS on the currently activated BWP can be transmitted, while SRS on the inactive BWP cannot be transmitted.

[0084] In some implementations, SRS may be configured under a carrier (equivalent to a cell or serving cell). In some implementations, the configuration of SRS on a carrier (component carrier CC, CC-level SRS) includes frequency information (e.g., absolute radio frequency channel number ARFCN, start / end frequency in RB relative to CRB / CRB0, bandwidth expressed in number of RBs). It should be noted that a carrier may be a virtual carrier (e.g., its bandwidth may be greater than the physical carrier associated with it).

[0085] In some implementations, if CC-level SRS is configured, the UE needs to apply CC-level SRS (e.g., transmit CC-level SRS). In some implementations, if CC-level SRS is configured, the UE needs to apply CC-level SRS (e.g., transmit CC-level SRS) instead of applying BWP-level SRS (i.e., SRS configured under BWP). Therefore, if CC-level SRS is configured, the UE transmits CC-level SRS instead of BWP-level SRS. In some implementations, if CC-level SRS is configured, even if BWP-level SRS is configured, the UE needs to apply CC-level SRS (e.g., transmit CC-level SRS) instead of BWP-level SRS.

[0086] In some implementations, an SRS sequence generator for an SRS sequence for SRS transmission needs to be initialized using a carrier ID (or a serving cell index, or a value related to a serving cell, or a value configured by a higher layer).

[0087] For CC-level SRS, a BWP (or virtual BWP) is configured to have the same bandwidth as the bandwidth of the CC (or virtual carrier) to which it belongs. In some implementations, a virtual BWP may have a larger bandwidth than a physical BWP. In some implementations, a virtual BWP may have a larger bandwidth than the physical BWP associated with it. In some implementations, the bandwidth of an SRS configured on a BWP (or virtual BWP) may be wider than the bandwidth of the BWP.

[0088] A RedCap UE may be configured with one SRS resource, which may be distributed across multiple BWPs (or virtual BWPs), for example including Hop_Number virtual BWPs, a physical BWP, and Hop_Number-1 virtual BWPs. In some implementations, a list of start / end frequencies (e.g., RB indices) and bandwidths (e.g., number of RBs) of SRS resources will be configured for each BWP (or virtual BWP). In some implementations, a list of start / end frequencies (e.g., RB indices, such as ARFCN) and bandwidths (e.g., number of RBs) of SRS resources will be configured for a carrier (or virtual carrier). In the case of a BWP switch (or virtual BWP switch), a RedCap UE may hop a segment of the SRS (or SRS bandwidth) to another.

[0089] In some implementations, in case of carrier switching (or virtual carrier switching), a RedCap UE may hop a segment of the SRS (or SRS bandwidth) to another one.

[0090] In some implementations, a RedCap UE may be configured with multiple SRS resources (e.g., Hop_Number SRS resources), and each SRS resource is associated with a corresponding BWP (or virtual BWP). In the case of BWP switching (or virtual BWP switching), the RedCap UE may hop from one SRS resource to another SRS resource to cover a large bandwidth.

[0091] According to the implementation, CC-level SRS can use hopping to expand the bandwidth of SRS. Thus, the effective bandwidth can be expanded. Therefore, the positioning performance can be improved (eg, higher positioning accuracy).

[0092] Implementation Example 4: BWP Handover with More Than 4 Hops

[0093] Currently, (up to) 4 BWPs can be dynamically switched via DCI (carried on PDCCH, i.e., bits 0, 1, 2 for the target BWP index). If PRS / SRS hopping is based on BWP switching (i.e., there is one PRS / SRS hop on each BWP or virtual BWP), there are up to 4 hops. These 4 hops can be triggered by DCI, MAC CE, or pre-configuration. Figure 3 A diagram indicating the position accuracy of a UE for a hopping technique with frequency overlap is illustrated. Figure 3 As shown, for RedCap UE supporting 20MHz bandwidth, in the case of indoor factory sparse high (InF-SH), four hops (4x20MHz in total, 20MHz per hop) are sufficient to meet the requirements of the Industrial Internet of Things (IIOT) scenario (i.e., one meter @CDF=90% requirement). However, in some cases, four hops are not enough (for example, for RedCap UE supporting 5MHz or 10MHz bandwidth), and more than 4 hops are required.

[0094] To support more than four hops (e.g., 24 hops for RedCap UE supporting 5 MHz bandwidth in the previous example), more bits are needed in the DCI for BWP indication on BWP switching (e.g., 5 bits for 32 hops, or 32 BWPs, or 32 virtual BWPs). In some implementations, a DCI with multiple indication bits (e.g., 32 bits) may indicate one or more hops (e.g., application bitmaps or code points) for PRS / SRS.

[0095] In some implementations, a MAC CE having multiple indication bits (e.g., one or more 8-bit bytes, e.g., 4 8-bit bytes, one 8-bit byte having 8 bits, in addition to the logical channel ID) may indicate one or more hops of PRS / SRS (e.g., using a bitmap or code points, e.g., 32 hops).

[0096] In some implementations, a BWP may have multiple sub-BWPs (or virtual sub-BWPs). In this example, a higher layer may configure 0-8 sub-BWPs (or virtual sub-BWPs). In some implementations, one or more sub-BWPs (or virtual sub-BWPs) may be associated with a BWP. In some implementations, the bandwidth of a sub-BWP (or virtual sub-BWP) may exceed the range of the BWP associated with it. In some implementations, except for one sub-BWP (or virtual sub-BWP, such as the first sub-BWP, such as the sub-BWP with ID=0), the bandwidth of a sub-BWP (or virtual sub-BWP) may exceed the range of the BWP associated with it. In some implementations, the RedCap UE switches the sub-BWP in the order of the sub-BWP ID. In some implementations, the RedCap UE switches the sub-BWP in the order of the sub-BWP ID after receiving a PRS / SRS hopping indication or a sub-BWP switching indication. With this implementation, the RedCap UE first switches the BWP and then switches the sub-BWP associated with the same BWP. In some implementations, BWP switching may be indicated by a DCI / MAC CE, and sub-BWP switching may be automatic (eg, switching from a low index to a high index based on the sub-BWP ID upon receiving a BWP switching indication from the BWP associated with it).

[0097] In some implementations, the first sub-BWP (or virtual sub-BWP, or virtual BWP, for example, ID=0) is mapped to the physical BWP. In some implementations, the first sub-BWP (or virtual sub-BWP) is for the first hop (for example, hop ID=0).

[0098] In some implementations, one sub-BWP (or virtual sub-BWP) is configured with PRS / SRS resources. After receiving / transmitting PRS / SRS in each BWP / sub-BWP (e.g., 2 with BWP / sub-BWP switching), the UE can cover a larger bandwidth (e.g., 5 hops / BWP / sub-BWP for 100MHz bandwidth). Thus, positioning accuracy can be improved.

[0099] In some implementations, the sub-BWP ID (or virtual sub-BWP ID, or BWP ID, or virtual BWP ID) is equal to the PRS / SRS resource ID.

[0100] In some implementations, one PRS / SRS resource is configured for all sub-BWPs (or virtual sub-BWPs, or BWPs, or virtual BWPs). Each sub-BWP (or virtual sub-BWP, or BWP, or virtual BWP) includes a segment of the PRS / SRS resource (e.g., equal segments between hops, e.g., hops with segments).

[0101] In some implementations, a sub-BWP (or virtual sub-BWP, or BWP, or virtual BWP) has a frequency starting point (e.g., RB ID, ARFCN relative to CRB / CRB0), RB length / number (or frequency range or frequency end point (e.g., RB ID, ARFCN relative to CRB / CRB0)).

[0102] In some implementations, the same transmit power is applied for PRS / SRS transmission on each sub-BWP (or virtual sub-BWP, or BWP, or virtual BWP). In some implementations, the same transmit power spectral density (PSD, power divided by bandwidth) is applied for PRS / SRS transmission on a sub-BWP (or virtual sub-BWP, or BWP, or virtual BWP, or hop).

[0103] In some implementations, the same SCS is applied for PRS / SRS transmission on each sub-BWP (or virtual sub-BWP, or BWP, or virtual BWP, or hop).

[0104] In some implementations, for PRS transmission on a sub-BWP (or virtual sub-BWP, or BWP, or virtual BWP, or hop), a PRS-specific sub-BWP (or virtual sub-BWP, or BWP, or virtual BWP, or hop) is applied. In some implementations, for a PRS-specific sub-BWP, there is no data channel, no PDCCH, and no other reference signal. In some implementations, for a PRS-specific sub-BWP, there is no data channel, no PDCCH, and no other reference signal except for SSB.

[0105] In some implementations, for SRS transmission on a sub-BWP (or virtual sub-BWP, or BWP, or virtual BWP, or hop), an SRS specific sub-BWP (or virtual sub-BWP, or BWP, or virtual BWP, or hop) is applied. In some implementations, for an SRS specific sub-BWP, there is no data channel, no physical uplink control channel (PUCCH), no physical random access channel (PRACH), and no other reference signals. In some implementations, for an SRS specific sub-BWP, there is no data channel, no PUCCH, and no other reference signals except PRACH.

[0106] In some implementations, one or more BWPs (or one or more virtual BWPs, a virtual BWP may be a BWP outside a carrier / cell, such as a BWP outside a 20MHz carrier) may be grouped into a BWP group (e.g., a BWP group has 1-8 BWPs) with a group ID (e.g., 0-3 for 4 BWP groups). With this implementation, a BWP group switching will be performed first (e.g., based on a DCI / MACCE indication). Then, a BWP switching within a BWP group will be performed (e.g., automatically based on a BWP ID).

[0107] In some implementations, if less than or equal to 4 hops, only BWP switching is performed. In this case, no BWP group switching is performed or only one BWP group switching is performed. In some implementations, if more than 4 hops, both BWP group switching and BWP switching are performed.

[0108] In some implementations, a first BWP group (eg, group ID=0) includes a physical BWP (eg, BWP ID=0).

[0109] According to the implementation, the hopping of SRS / PRS can be realized by (sub)BWP switching (virtual BWP switching) between hops. Thus, the effective bandwidth can be extended. Therefore, the positioning performance can be improved (eg, higher positioning accuracy).

[0110] Implementation Example 5: Positioning based on partial transmission

[0111] like Figure 4 As shown, the SRS may be configured with partial transmission (partial sounding) on ​​a BWP (or virtual BWP, or carrier, or virtual carrier). Figure 4 An example of SRS transmission is described, including the first to fifth partial transmissions. Figure 4 In , blocks with a fill pattern are transmitted, while blocks without any fill pattern are not transmitted. Figure 4 Each partial transmission has a fill pattern indicating a 20 MHz jump. Figure 5 , the block structure of the fifth partial transmission is shown as an example. Although each transmission has a different frequency, the first to fourth partial transmissions have the same block structure as the fifth partial transmission.

[0112] For this partial transmission based positioning, the higher layer (or gNB) will configure a (virtual) BWP (or carrier or virtual carrier) with a relatively large bandwidth (e.g. 100MHz, or 273RB@SCS=30kHz) for the RedCap UE. For this relatively large bandwidth, the UE will only transmit a portion of it (e.g. the first transmission is on the lowest frequency with 20MHz bandwidth, or 48RB@SCS=30kHz. For example, the second transmission is on the second lowest frequency with 20MHz bandwidth and one or more overlapping RBs.)

[0113] In some implementations, for such partial transmission based positioning, the transmission number (i.e., ID) is associated with a symbol ID or a timeslot number or a system frame number. For example, the first partial transmission occurs at SFN mod SRS_Period = 0, where the timeslot number is zero and the symbol ID is a symbol of the first configuration (e.g., 12). In the example, SFN is the system frame number (0 to 1023) and SRS_Period is the SRS period (e.g., 10 milliseconds).

[0114] In some implementations, for such partial transmission based positioning, the size of Comb is 1 (all subcarriers in RB). In some implementations, for such partial transmission based positioning, the size of Comb can only be configured as 1.

[0115] In some implementations, for such partial transmission based positioning, there is an indication of an extended bandwidth for the SRS resources. The SRS resources may be outside the currently activated BWP (or carrier). In some implementations, the bandwidth of the reference signal used for positioning may be outside the currently activated (virtual) BWP (or sub-BWP). In some implementations, the reference signal used for positioning may span outside the currently activated (virtual) BWP (or sub-BWP).

[0116] In some implementations, a partial transmission factor (PTF) may be configured for such partial transmission based positioning. For example, the PTF may be configured as the transmission bandwidth in time divided by the total transmission bandwidth, such as 20 MHz / 100 MHz=1 / 5, where the total transmission bandwidth is the sum of all transmission bandwidths in time. The PTF may be configured as other values, not limited to the transmission bandwidth in time divided by the total transmission bandwidth. In some other implementations, if the partial transmission factor (PTF) is not configured, the partial transmission factor will be set to, for example, the transmission bandwidth in time divided by the total bandwidth.

[0117] In some implementations, for such positioning based on partial transmission, the starting RB of the partial transmission can be configured. For example, the starting RB (Starting_RB_First) of the first transmission of the partial transmission is configured to 0. According to this configuration, the starting RB (Starting_RB_Second) of the second / third / fourth / fifth transmission of the partial transmission is: Starting_RB_First+PTF*Total_Bandwidth*(Transmission_ID-1)+Overlap_RB. In the example, Total_Bandwidth is the total bandwidth of the SRS based on the partial transmission, and Transmission_ID is the transmission ID of each partial transmission (for example, 2 / 3 / 4 / 5 for the second / third / fourth / fifth transmission). If it is not configured, the starting RB of the first transmission of the partial transmission will be 0.

[0118] In some implementations, for this partial transmission based positioning, there is a sequence ID (eg, 0-65535) for generating the sequence of the SRS.

[0119] In some implementations, for such positioning based on partial transmission, a spatial relationship with other signals (e.g., quasi-co-located QCL) may be configured (e.g., QCL-Type-C or QCL-Type-D). For example, the first transmission of the partial transmission may have a spatial relationship with an SSB (including a cell-defined SSB (CD-SB), a non-cell-defined SSB (NCD-SB)), a channel state information reference signal (CSI-RS). For example, the remaining transmissions of the partial transmission (e.g., the second / third / fourth / fifth transmission) may have a spatial relationship with the first transmission of the SRS in the partial transmission.

[0120] In some implementations, if an initial downlink BWP for all UEs and an initial downlink BWP for RedCap UEs are configured, the QCL source may be SSB on the initial downlink BWP for RedCap UEs.

[0121] In some implementations, for such partial transmission based positioning, one SRS resource (with a large bandwidth, such as 100 MHz) may be configured. In some implementations, for such partial transmission based positioning, Number_of_Transmission SRS resources (with a small bandwidth, such as 20 MHz) may be configured. In the example, Number_of_Transmission is the total number of transmissions with a relatively small bandwidth. In some implementations, for such partial transmission based positioning, a 1 / PTF SRS resource (with a relatively small bandwidth, such as 20 MHz) may be configured. In some implementations, for such partial transmission based positioning, floor(1 / PTF) SRS resources (with a relatively small bandwidth, such as 20 MHz) may be configured.

[0122] In some implementations, the SRS resources for such partial transmission based positioning are semi-periodic resources (eg, resources that can be activated by a MAC CE) or aperiodic resources (eg, resources that can be activated by a DCI).

[0123] In some implementations, such as Figure 5 As shown, the size of Comb can be larger than the number of allocated symbols (eg Comb=4, Symbol=2). Figure 5 Two examples of assigning symbols are shown. Figure 5 In , since there are 12 resource elements (REs) in a resource block, the size of the Comb is obtained by dividing 12 by the number of REs transmitted in a symbol. Figure 5 In , there are three shaded blocks indicating three transmitted REs, and therefore the size of Comb is 4. In RB, the first symbol ( Figure 5 The first / third / fifth subcarrier on the left column) (see Figure 5 ), and the second symbol ( Figure 5 The eighth / tenth / twelfth subcarrier on the right column) (see Figure 5 The shaded box in the figure) is assigned to RedCap UE.

[0124] In some implementations, the UE may report its positioning capability based on the partial transmission. For example, the capability on a single transmission bandwidth, the capability on the total bandwidth, and / or the capability on the PTF may be reported.

[0125] According to some implementations, a relatively large SRS / PRS bandwidth may be enabled, with overlap between different parts of partial transmissions (to adjust the coherence phase of the channel). Thus, the effective bandwidth may be extended, which improves positioning performance (eg, higher positioning accuracy).

[0126] Implementation Example 6: PRS / SRS Transmission / Reception Based on Carrier Switching

[0127] A RedCap UE may be configured with multiple carriers (or virtual carriers) that may overlap in frequency with some resources (eg, one RB) between two adjacent carriers. In an implementation, the carriers also include virtual carriers. PRS / SRS transmission / reception may be based on carrier switching.

[0128] In some implementations, each (virtual) carrier is configured with a carrier ID (or serving cell ID, or hop ID, e.g. 0, 1, 2, ... 30, 31, 32, ... 63). DCI / MAC CE / higher layer signaling may indicate that one or more (virtual) carriers are triggered. Upon receiving DCI / MAC CE / higher layer signaling, a RedCap UE may switch from one (virtual) carrier to another. If the switch is triggered by DCI, 0-5 bits (or 0-32 bits) may be configured for the indication. In some implementations, there is a one-bit difference between a normal UE and a RedCap UE. In some implementations, a (virtual) carrier switching order list is configured to indicate a carrier switching sequence (e.g. 0, 1, 2, 3, 4 of carrier ID). In some implementations, the (virtual) carrier with the first carrier ID in the list will be used for the first transmission / reception (or first hop, or reference transmission / reception, or reference hop, or reference carrier, or reference resource).

[0129] In some implementations, the UE should report its capabilities regarding carrier switching (e.g., RF re-tuning time between two carriers, number of carriers / virtual carriers it supports).

[0130] In some implementations, there is a sequence ID (eg, 0-8191) that is used to generate the sequence for PRS / SRS, with one sequence ID per (virtual) carrier.

[0131] In some implementations, special time slots and flexible symbols or uplink symbols are configured for (virtual) carrier switching. In some implementations, there are no other signals / channels on the special time slot except PRS / SRS. In some implementations, if there are other signals / channels on the special time slot, PRS / SRS has a higher priority than other signals / channels. In some implementations, there is a priority list for PRS / SRS and other signals / channels.

[0132] In some implementations, the (virtual) carrier transmission / reception order is the (virtual) carrier ID (or hop ID, or the above sequence ID).

[0133] In some implementations, the sequence generation of the PRS / SRS is associated with the previous (virtual) carrier / hop.

[0134] Depending on the implementation, hopping of SRS / PRS may be enabled with overlap between (virtual) carriers / hops (to adjust the coherence phase of the channel). Thus, the effective bandwidth may be extended, which improves positioning performance (eg, higher positioning accuracy).

[0135] Implementation Example 7 (Antenna Switching Based Solution)

[0136] For RedCap UE on FR1, it may have a single physical antenna. For such UE, it may be configured with one or more virtual antennas, where the virtual antennas are actually mapped to the same physical antenna. In some implementations, both the physical antenna and the virtual antenna have antenna IDs (or antenna port IDs). In some implementations, such as Figure 6 As shown, each antenna (or antenna ID) is associated with a (virtual) carrier (or cell, e.g. 20 MHz) or a segment of a (virtual) carrier (or cell). Figure 6 , a first antenna and a second (virtual) antenna are configured for the UE. The first antenna used to transmit a resource with 2 symbols is associated with a 20 MHz carrier. The second (virtual) antenna used to transmit a resource with 2 symbols is associated with another 20 MHz carrier.

[0137] In some implementations, there is a frequency overlap (eg, one RB) between two consecutive transmissions of two (virtual) carriers, or between two segments of a (virtual) carrier.

[0138] In some implementations, there is a time interval between two consecutive transmissions of the two virtual antennas. In some implementations, the UE may report this time interval as its capability. It should be noted that during this time interval, another UE may have SRS / PRS transmission.

[0139] In some implementations, the DCI / MAC CE / higher layer signaling may indicate that one or more (virtual) antennas are triggered. In some implementations, the DCI / MAC CE / higher layer signaling may indicate the transmission order of the (virtual) antennas.

[0140] For RedCap UE on FR2, it may have two physical antennas. In this case, zero or more virtual antennas may be configured to use the above solution.

[0141] In some implementations, the (virtual) antenna ID of the transmitting (virtual) antenna is associated with the slot number, for example, ID = Slot_Number mod Number_of_Virtual_Antenna. In the example, Slot_Number is the slot number (0, 1, 2, ... 9) in the radio frame (10ms), and Number_of_Virtual_Antenna is the total number of virtual antennas (e.g. 5).

[0142] In some implementations, one PRS / SRS resource is mapped to a virtual antenna, where one PRS / SRS resource is associated with a transmission order (e.g., in the order of virtual antenna ID, carrier ID). The transmission order indicates the order in which transmissions are performed. In one example, the transmission order may be indicated by a sequence of antenna IDs, such that the transmission with the smallest antenna ID may occur first. In another example, the transmission order may be indicated by a sequence of carrier IDs, such that the transmission with the smallest carrier ID may occur first. These transmission orders are just examples, and other implementations are possible. In some implementations, the transmission order is indicated in a system information broadcast (SIB). In some implementations, there is only one PRS / SRS resource with multiple segments (overlapping at different frequencies), and one segment is mapped to a virtual antenna.

[0143] Depending on the implementation, SRS / PRS hopping may be enabled with virtual antenna switching, with overlap between hops (to adjust the coherence phase of the channel). Thus, the effective bandwidth may be extended, which improves positioning performance (eg, higher positioning accuracy).

[0144] Implementation Example 8: Improving Channel Estimation on Overlapping RB / RE / SC

[0145] The positioning performance of PRS / SRS hopping is highly dependent on the channel estimation on overlapping resource blocks (RBs) / resource elements (REs) / subcarriers (SCs). It is necessary to study how to improve its channel estimation.

[0146] The power boost is applied on the overlapped RB / RE / SC. For example, 3dB more power is applied relative to other non-overlapped RB / RE.

[0147] In some implementations, the gNB / UE calculates the path loss (PL) of SRS / PRS. The gNB indicates the number of overlapping RBs / REs / SCs based on the PL. In some implementations, the network may increase the number of overlapping RBs / REs / SCs.

[0148] In some implementations, if the reference signal received power (RSRP) is below a threshold, the gNB / UE may select a path before the path with the highest RSRP, where the gNB / UE uses the selected path for channel estimation / phase estimation.

[0149] In some implementations, the gNB / UE may provide line-of-sight (LOS) / non-line-of-sight (NLOS) probabilities to the network.

[0150] According to some implementations, channel estimation on overlapping RB / RE / SC may be improved, and positioning performance may be improved (eg, higher positioning accuracy).

[0151] Implementation Example 9: Dropping of SRS transmissions for power saving

[0152] If the UE detects that its position has not changed since the last position fix, the UE may discard the SRS transmission to save power. For example, the UE may have an internal sensor and detect its position. The gNB may detect the energy on the SRS symbol to check whether the UE transmits SRS. If the detected energy is below a threshold, the gNB may declare "not detected" and transmit this declaration to the network.

[0153] In some implementations, when the battery of the UE is below a threshold, the UE may drop the SRS transmission to save power.

[0154] In some implementations, the UE may transmit a PRACH / PUCCH / PUSCH (eg, a single symbol) to indicate that the SRS transmission is dropped.

[0155] Depending on the implementation, it may be possible to save power without affecting positioning performance.

[0156] Figure 7 1 is a block diagram of an example implementation of a wireless communication device 1200. The methods described herein may be implemented by the device 1200. In some embodiments, the device 1200 may be a base station or network device of a wireless network. In some embodiments, the device 1200 may be a user equipment (e.g., a wireless device or a user equipment UE). The device 1200 includes one or more processors, such as a processor electronic device 1210, a transceiver circuit 1215, and one or more antennas 1220 for transmitting and receiving wireless signals. The device 1200 may include a memory 1205, which may be used to store data and instructions used by the processor electronic device 1210. The device 1200 may also include an additional network interface connected to additional equipment of one or more core networks or network operators. The additional network interface not explicitly shown in the figure may be wired (e.g., optical fiber or Ethernet) or wireless.

[0157] Figure 8An example of a wireless communication system 1300 is depicted in which various techniques described herein can be implemented. System 1300 includes a base station 1302 that can have a communication connection with a core network (1312) and a wireless communication medium 1304 to communicate with one or more user devices 1306. User device 1306 can be a smartphone, a tablet, a machine-to-machine communication device, an Internet of Things (IoT) device, etc.

[0158] Some preferred embodiments may include the following solutions.

[0159] 1. A method of wireless communication (e.g., Fig. 9 The method 900 shown in the figure comprises: receiving 910, by a user equipment, configuration information for configuring a positioning reference signal from a network device; performing 920 measurement on the positioning reference signal; and reporting 930 a measurement result of the measurement.

[0160] 2. A method according to solution 1, wherein the configuration information includes a downlink control information that triggers the transmission or reception of a positioning reference signal, the transmission or reception of the positioning reference signal having a jump between two segments of the positioning reference signal having different frequency ranges.

[0161] 3. The method according to solution 1, wherein the configuration information includes a medium access control (MAC) control element (CE) indicating transmission or reception of a positioning reference signal.

[0162] 4. The method according to solution 1, wherein the configuration information configures a transmission window for positioning reference signal transmission with hopping.

[0163] 5. The method according to solution 1, wherein the configuration information configures a carrier list to a positioning reference signal processing window (PPW), and the carrier list is associated with a cell ID.

[0164] 6. The method according to solution 1, wherein the configuration information configures the measurement interval, the RedCap specific MG, and for the RedCap specific MG, the positioning reference signal takes precedence over other downlink signals and channels for the RedCap specific MG.

[0165] 7. The method according to solution 1, wherein the configuration information configures a processing window for a positioning reference signal, a RedCap specific PPW, and for the RedCap specific PPW, the positioning reference signal takes precedence over all other downlink signals and channels except synchronization signal blocks.

[0166] 8. A method according to solution 1, wherein the configuration information configures multiple processing windows for positioning frequency layers, and multiple processing windows with different priorities applied to positioning reference signals, and the final priority depends on the lowest priority among the different priorities of the multiple processing windows.

[0167] 9. A method according to solution 1, wherein the configuration information configures multiple processing windows for the positioning frequency layer, and multiple processing windows with different priorities applied to the positioning reference signal, and the final priority depends on the priority of the PRS transmitted first in the multiple processing windows.

[0168] 10. The method according to solution 1 further comprises: in case that a component carrier level SRS is configured, applying, by the user equipment, a component carrier level SRS (sounding reference signal) to replace a BWP (bandwidth part) level SRS.

[0169] 11. The method according to solution 10, wherein an SRS sequence generator for generating an SRS sequence of the component carrier level SRS is initialized using a carrier ID.

[0170] 12. The method according to solution 10, wherein the configuration information configures a plurality of SRS resources, and each SRS resource is associated with a corresponding BWP.

[0171] 13. The method according to solution 1, wherein the configuration information triggers a BWP group switch for a BWP group including one or more BWPs, the BWP group switch being followed by a BWP switch for one of the one or more BWPs within the BWP group.

[0172] 14. The method according to solution 1, wherein the configuration information triggers a BWP group switch for a BWP group including one or more BWPs, the BWP group switch value is followed by a sub-BWP switch, and the sub-BWP switch is for a sub-BWP of one of the one or more BWPs.

[0173] 15. The method according to solution 1, wherein the configuration information configures a partial transmission factor (PTF), wherein the PTF is the transmission bandwidth in time divided by the total transmission bandwidth.

[0174] 16. The method according to solution 15 further includes: reporting by the user equipment a capability regarding a partial transmission factor (PTF), the PTF being the transmission bandwidth in time divided by the total transmission bandwidth.

[0175] 17. A method according to solution 15, wherein the configuration information configures the spatial relationship between the first part transmission and the synchronization signal block.

[0176] 18. The method according to solution 1, wherein the configuration information configures a carrier list indicating a carrier switching sequence so that a carrier with a first carrier ID in the list is used for a first transmission or reception of a positioning reference signal.

[0177] 19. The method according to solution 1, wherein the configuration information includes a system information broadcast (SIB) indicating: a transmission order of antennas with antenna IDs and an association of reference signal resources.

[0178] 20. The method according to solution 1, wherein the configuration information indicates the number of overlapping resource blocks, resource elements, or subcarriers.

[0179] 21. The method according to solution 1 further comprises: concatenating multiple segments of a reference signal to obtain a concatenated reference signal, wherein performing measurements comprises performing positioning-related measurements on the concatenated reference signal.

[0180] 22. A method of wireless communication (e.g., Fig.10 The method 1000 shown in the figure comprises: configuring 1010, by a base station, a reference signal for positioning; performing 1020 measurement on the reference signal for positioning; and reporting 1030 a measurement result of the measurement.

[0181] 23. The method according to solution 22 also includes: receiving multiple segments of reference signals with different frequency ranges from a user device; and connecting the multiple segments of the reference signal to obtain a connected reference signal, wherein the measurement results include positioning-related measurements on the connected reference signal.

[0182] 24. A wireless communication device, comprising a processor, wherein the processor is configured to implement the method of any one of the above solutions.

[0183] 25. A computer storage medium having codes stored thereon, which, when executed by a processor, enable the processor to implement the method of any one of the above solutions.

[0184] The disclosed and other embodiments, modules and functional operations described in this document may be implemented in digital electronic circuits or computer software, firmware or hardware, including the structures disclosed in this document and their structural equivalents, or a combination of one or more of them. The disclosed and other embodiments may be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution or control of the operation of a data processing device. The computer-readable medium may be a machine-readable storage device, a machine-readable storage substrate, a storage device, a material combination that affects a machine-readable propagation signal, or a combination of one or more of them. The term "data processing device" includes all devices, equipment and machines for processing data, including, for example, a programmable processor, a computer, or multiple processors or multiple computers. In addition to hardware, the device may include code that creates an execution environment for the computer program in question, such as code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, such as a machine-generated electrical signal, an optical signal, or an electromagnetic signal, which is generated to encode information for transmission to a suitable receiving device.

[0185] A computer program (also referred to as a program, software, software application, script, or code) may be written in any form of programming language, including compiled or interpreted languages, and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored as part of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files storing one or more modules, subroutines, or portions of code). A computer program may be deployed to execute on one or more computers, located at one site, or distributed across multiple sites and interconnected by a communications network.

[0186] The processes and logic flows described in this document can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and the apparatus can also be implemented as, special purpose logic circuitry, such as an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

[0187] For example, processors suitable for executing computer programs include both general-purpose and special-purpose microprocessors, and any one or more processors of any kind of digital computer. In general, the processor receives instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more storage devices for storing instructions and data. In general, a computer also includes one or more mass storage devices (such as magnetic disks, magneto-optical disks, or optical disks) for storing data, or is operatively coupled thereto to receive data from it or to transfer data to it or both. However, a computer does not necessarily need to have such a device. Computer-readable media suitable for storing computer program instructions and data include various forms of non-volatile memory, media, and storage devices, including, for example, semiconductor storage devices such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and memory may be supplemented by or incorporated into a dedicated logic circuit.

[0188] Although this document contains many details, these details should not be understood as limitations on the scope of the invention claimed or the scope of the invention that may be claimed, but should be understood as descriptions of features specific to specific embodiments. Certain features described in this document in the context of separate embodiments may also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments, respectively, or in any suitable sub-combination. In addition, although features may be described as working in certain combinations, even initially required, in some cases, one or more features in the combination may be deleted from the required combination, and the required combination may be for a sub-combination or a variant of a sub-combination. Similarly, although operations are described in a specific order in the accompanying drawings, this should not be understood as requiring that these operations be performed in the specific order shown or in a sequential order, or that all illustrated operations be performed to achieve the desired result.

[0189] Only a few examples and implementations are disclosed. Based on what is disclosed, changes, modifications and enhancements may be made to the described examples and implementations and other implementations.

Claims

1. A method of wireless communication, comprising: The user equipment receives configuration information for configuring a positioning reference signal from the network equipment; performing measurements on the positioning reference signal; as well as The measurement results of the measurements are reported.

2. The method according to claim 1, wherein the configuration information includes a downlink control information, the downlink control information triggers the transmission or reception of the positioning reference signal, and the transmission or the reception of the positioning reference signal has a jump between two segments of the positioning reference signal with different frequency ranges. 3 . The method according to claim 1 , wherein the configuration information comprises a medium access control (MAC) control element (CE), the MAC CE indicating transmission or reception of the positioning reference signal. The method according to claim 1 , wherein the configuration information configures a transmission window for transmission of the positioning reference signal with hopping. 5 . The method according to claim 1 , wherein the configuration information configures a carrier list to a positioning reference signal processing window (PPW), and the carrier list is associated with a cell ID.

6. The method of claim 1, wherein the configuration information configures a measurement interval, a RedCap specific MG, and for the RedCap specific MG, the positioning reference signal takes precedence over other downlink signals and channels for the RedCap specific MG.

7. The method of claim 1, wherein the configuration information configures a processing window for the positioning reference signal, a RedCap-specific PPW, and for the RedCap-specific PPW, the positioning reference signal takes precedence over all other downlink signals and channels except synchronization signal blocks.

8. The method according to claim 1, wherein the configuration information configures multiple processing windows for positioning frequency layers, and for the multiple processing windows with different priorities applied to the positioning reference signal, a final priority depends on the lowest priority among the different priorities of the multiple processing windows.

9. The method according to claim 1, wherein the configuration information configures multiple processing windows for positioning frequency layers, and for the multiple processing windows with different priorities applied to the positioning reference signal, a final priority depends on the priority of the PRS that is first transmitted in the multiple processing windows.

10. The method according to claim 1, further comprising: In case that a component carrier level SRS is configured, the component carrier level SRS (sounding reference signal) is applied by the user equipment to replace the BWP (bandwidth part) level SRS.

11. The method according to claim 10, wherein an SRS sequence generator for generating an SRS sequence of the component carrier level SRS is initialized using a carrier ID. 12 . The method according to claim 10 , wherein the configuration information configures a plurality of SRS resources, and each SRS resource is associated with a corresponding BWP.

13. The method of claim 1, wherein the configuration information triggers a BWP group switch for a BWP group including one or more BWPs, the BWP group switch being followed by a BWP switch for one of the one or more BWPs within the BWP group.

14. The method of claim 1, wherein the configuration information triggers a BWP group switch for a BWP group including one or more BWPs, the BWP group switch being followed by a sub-BWP switch for a sub-BWP of one of the one or more BWPs.

15. The method of claim 1, wherein the configuration information configures a partial transmission factor (PTF), the PTF being the transmission bandwidth in time divided by the total transmission bandwidth.

16. The method according to claim 15, further comprising: The capability regarding the partial transmission factor (PTF) is reported by the user equipment, the PTF being the transmission bandwidth in time divided by the total transmission bandwidth.

17. The method according to claim 15, wherein the configuration information configures: the spatial relationship between the first part transmission and the synchronization signal block.

18. The method according to claim 1, wherein the configuration information configures a carrier list indicating a carrier switching sequence so that a carrier having a first carrier ID in the list is used for the first transmission or reception of the positioning reference signal.

19. The method of claim 1, wherein the configuration information comprises a system information broadcast (SIB) indicating an association of a transmission order of antennas with antenna IDs and reference signal resources.

20. The method of claim 1, wherein the configuration information indicates: a number of overlapping resource blocks, resource elements, or subcarriers.

21. The method according to claim 1, further comprising: A plurality of segments of the reference signal are concatenated to obtain a concatenated reference signal, wherein performing the measurements comprises performing positioning related measurements on the concatenated reference signal.

22. A method of wireless communication, comprising: A reference signal configured by the base station for positioning; performing measurements on the reference signal used for positioning; as well as The measurement results of the measurements are reported.

23. The method according to claim 22, further comprising: receiving, from a user equipment, a plurality of segments of the reference signal having different frequency ranges; as well as concatenating the plurality of segments of the reference signal to obtain a concatenated reference signal, The measurement result includes: positioning-related measurement of the reference signal of the connection.

24. A wireless communication device, comprising a processor, wherein the processor is configured to implement the method according to any one of the above claims.

25. A computer storage medium having codes stored thereon, which, when executed by a processor, cause the processor to implement the method of any one of the above claims.

Citation Information

Patent Citations

  • Determination of capability of user equipment to measure a downlink positioning reference signal across a plurality of frequency hops

    US20220109466A1

  • Signaling between the serving base station and the location server for partial frequency sounding patterns

    WO2022266561A1

Cited By

  • Wireless sensing processing method, electronic device, and computer program product

    WO2026218783A1