Location of user equipment (UE) using reference signals

Abstract

The application relates to devices and components, including apparatuses, systems, and methods for UE positioning. In one example, a UE transmits a sounding reference signal (SRSp) for positioning to a base station. The SRSp transmission can use frequency hopping and can depend on windows and / or conflict rules associated with the entire frequency hopping sequence or only frequency hopping in such sequences. This window and / or conflict rule can reduce the likelihood of signal conflicts with non-SRSp signals. In addition, the UE can implement a low power high accuracy positioning (LPHAP) technique. In this technique, if the UE cannot accurately measure "N" configured reference signals, the fallback behavior or SRSp transmission can be stopped, where "N" can be based on a positioning method.

Description

Cross-reference to related applications

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 501,642, filed May 11, 2023, the entire disclosure of which is incorporated herein by reference for all purposes. Background Technology

[0002] Cellular communication can be defined in various standards to enable communication between user equipment and cellular networks. For example, fifth-generation mobile networks (5G) are wireless standards designed to improve data transmission speed, reliability, availability, and the location of user equipment. Attached Figure Description

[0003] Figure 1 Examples of network environments based on some implementation schemes are shown.

[0004] Figure 2 Examples of transmit bandwidth and effective positioning bandwidth for user equipment (UE) according to some implementation schemes are shown.

[0005] Figure 3 Examples of using partial location bandwidth according to some implementation schemes are shown.

[0006] Figure 4 Another example of using partial location bandwidth according to some implementation schemes is shown.

[0007] Figure 5 Another example of using partial location bandwidth according to some implementation schemes is shown.

[0008] Figure 6 Examples of operational flow / algorithm structures for feedback positioning measurements implemented by receivers according to some implementation schemes are illustrated.

[0009] Figure 7 An example of a window for transmitting a probe reference signal (SRSp) for positioning, according to some implementation schemes, is shown.

[0010] Figure 8 An example of a window for SRSp transmission according to some implementation schemes is shown.

[0011] Figure 9 Examples of parameters for the window used for SRSp transmission are shown, according to the definitions of some implementation schemes.

[0012] Figure 10 Examples of conflict rules for SRP transmissions according to some implementation schemes are shown.

[0013] Figure 11Another example of a conflict rule for SRSp transmission according to some implementation schemes is shown.

[0014] Figure 12 Examples of operational flow / algorithm structures for user equipment positioning based on some implementation schemes are illustrated.

[0015] Figure 13 Examples are illustrated of possible use of one or more spatial domain transmission filters for user equipment according to some implementation schemes.

[0016] Figure 14 Another example of an operational flow / algorithm structure for user equipment positioning, based on some implementation schemes, is illustrated.

[0017] Figure 15 Examples of receiving components according to some implementation schemes are shown.

[0018] Figure 16 Examples of UEs according to some implementation schemes are shown.

[0019] Figure 17 Examples of base stations based on some implementation schemes are shown. Detailed Implementation

[0020] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).

[0021] Generally, a User Equipment (UE) communicates with a network's base stations via one or more communication channels. These base stations may also be referred to as network nodes, such as Evolved Node B (eNB), Next Generation Node B (gNB), or other base stations. The network may include fifth-generation (5G) systems, new radio (NR) systems, long-term evolution (LTE) systems, combinations thereof, or other wireless systems. Reference signals (such as Positioning Reference Signals (PRS) on downlink channels and Detection Reference Signals (SRSp) on uplink channels) may be transmitted between the UE and the network (e.g., one or more base stations or one or more cells provided by a set of base stations) to estimate the UE's location, which may be a geographic location with a specific accuracy.

[0022] In one example, the UE may have a specific bandwidth capability (e.g., 20 MHz capability) for transmitting and / or receiving such reference signals. To improve positioning accuracy, a larger positioning bandwidth (e.g., 100 MHz) may be used, thereby enabling the UE to implement frequency hopping to support the larger positioning bandwidth. In this example, several challenges may arise, including, for example, measurement reporting when only a larger positioning bandwidth is used partially (e.g., using 80 MHz instead of 100 MHz, corresponding to four frequency hopping instead of five), on-demand positioning and associated signaling, and the reception and / or transmission of other signals using frequency hopping (e.g., in the case of signal collisions, etc.). Various solutions to such challenges are described in this disclosure.

[0023] In another example, the UE may be configured with one or more spatial domain transmission filters. Various challenges may also arise associated with using such filters. For example, the UE may determine that its positioning using such filters may not be accurate enough. Various solutions to these challenges are also described in this disclosure.

[0024] The following is a glossary of terms that may be used in this disclosure.

[0025] As used herein, the term "circuit" refers to, is part of, or includes the following: hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-chips (SoCs)), digital signal processors (DSPs), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functionalities. The term "circuit" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) and program code for executing the functionality of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0026] As used herein, the term "processor circuit" means, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may also refer to an application processor, baseband processor, central processing unit (CPU), graphics processing unit, single-core processor, dual-core processor, triple-core processor, quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions such as program code, software modules, and / or functional processes.

[0027] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, or network interface cards.

[0028] As used herein, the term "user equipment" or "UE" refers to a device with radio communication capabilities and can describe network resources in a communication network. Furthermore, the term "user equipment" or "UE" can be considered synonymous and can refer to a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

[0029] As used herein, the term "base station" refers to a device with radio communication capabilities, which is a network node in a communication network and can be configured as an access node in the communication network. The UE's access to the communication network can be managed at least partially by the base station, thereby connecting the UE to the base station to access the communication network. According to Radio Access Technology (RAT), a base station may be referred to as a gNodeB (gNB), eNodeB (eNB), access point, etc.

[0030] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" can refer to various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" can refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0031] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, databases and applications, units of workload, etc. "Hardware resource" can refer to computing, storage, or networking resources provided by physical hardware components. "Virtualized resource" can refer to computing, storage, or networking resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resource" or "communication resource" can refer to resources that a computer device / system can access via a communication network. The term "system resource" can refer to any kind of shared entity providing services and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0032] As used herein, the term "channel" refers to any tangible or intangible transmission medium used to transmit data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a means or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices used for transmitting and receiving information.

[0033] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0034] The term "connection" can refer to an established signaling relationship between two or more elements at a common communication protocol layer through a communication channel, link, interface, or reference point.

[0035] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as networked computers, network hardware, network equipment, network nodes, virtualized network functions, etc.

[0036] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element, or the data element that contains that content. An information element may include one or more additional information elements.

[0037] Figure 1 A network environment 100 according to some implementation schemes is illustrated. Network environment 100 may include UE 104 and gNB 108. gNB 108 may be a base station providing a radio access cell, for example, UE 104 may communicate with gNB 108 through a 3GPP New Radio (NR) cell. UE 104 and gNB 108 may communicate through an air interface compatible with 3GPP technical specifications, such as those defining the fifth-generation (5G) NR system standard.

[0038] The gNB 108 transmits information (e.g., data and control signaling) in the downlink direction by mapping logical channels to transport channels and transport channels to physical channels. Logical channels can transmit data between the Radio Link Control (RLC) layer and the Media Access Control (MAC) layer; transport channels can transmit data between the MAC and PHY layers; and physical channels can transmit information across the air interface. Physical channels may include the Physical Broadcast Channel (PBCH), the Physical Downlink Control Channel (PDCCH), and the Physical Downlink Shared Channel (PDSCH).

[0039] The PBCH can be used to broadcast system information that UE 104 can use for initial access to the serving cell. The PBCH can be transmitted together with the Physical Synchronization Signal (PSS) and the Secondary Synchronization Signal (SSS) in the Synchronization Signal (SS) / PBCH block. During the cell search process (including cell selection and reselection) and for beam selection, UE 104 can use the SS / PBCH block (SSB).

[0040] PDSCH can be used to transmit end-user application data, signaling radio bearer (SRB) messages, system information messages (except for MIBs), and paging messages.

[0041] The PDCCH can transmit downlink control information (DCI), which the gNB 108 scheduler uses to allocate both uplink and downlink resources. DCI can also be used to provide uplink power control commands, configure time slot formats, or indicate when preemption has occurred.

[0042] gNB 108 can also transmit various reference signals to UE 104. These reference signals may include demodulation reference signals (DMRS) for PBCH, PDCCH, and PDSCH. UE 104 can compare the received version of the DMRS with the transmitted known DMRS sequence to estimate the impact of the propagation channel. UE 104 can then apply the inverse channel of the propagation channel during the demodulation process transmitted on the corresponding physical channel.

[0043] The reference signal may also include a CSI reference signal (CSI-RS). The CSI-RS can be a multipurpose downlink transmitter that can be used for CSI reporting, beam management, connection mode mobility, radio link failure detection, beam failure detection and recovery, and fine-tuning of time and frequency synchronization.

[0044] Reference signals and information from the physical channel can be mapped to resources in the resource grid. For a given antenna port, subcarrier spacing configuration, and transmission direction (e.g., downlink or uplink), there exists a resource grid. The basic unit of the NR downlink resource grid can be a resource element, which can be defined by a subcarrier in the frequency domain and an orthogonal frequency division multiplexing (OFDM) symbol in the time domain. Twelve consecutive subcarriers in the frequency domain can constitute a physical resource block (PRB). A resource element group (REG) can include a PRB in the frequency domain and an OFDM symbol in the time domain, for example, twelve resource elements. A control channel element (CCE) can represent a resource group used to transmit the PDCCH. One CCE can be mapped to multiple REGs, for example, six REGs.

[0045] Transmissions using different antenna ports may traverse different radio channels. However, in some cases, different antenna ports may share common radio channel characteristics. For example, different antenna ports may have similar Doppler drift, Doppler spread, average delay, delay spread, or spatial receiver parameters (e.g., characteristics associated with the downlink received signal angle of arrival at the UE). Antenna ports sharing one or more of these large-scale radio channel characteristics can be considered quasi-co-located (QCL) with each other. 3GPP has specified four types of QCL to indicate which specific channel characteristics are shared. In QCL type A, antenna ports share Doppler drift, Doppler spread, average delay, and delay spread. In QCL type B, antenna ports share Doppler drift and Doppler spread. In QCL type C, antenna ports share Doppler drift and average delay. In QCL type D, antenna ports share spatial receiver parameters.

[0046] The gNB 108 can provide Transmission Configuration Indicator (TCI) status information to the UE 104 to indicate the QCL relationship between antenna ports used for reference signals (e.g., synchronization signals / PBCH or CSI-RS) and downlink data or control signaling (e.g., PDSCH or PDCCH). The gNB 108 can use a combination of RRC signaling, MAC control element signaling, and DCI to inform the UE 104 of these QCL relationships.

[0047] UE 104 can use physical uplink channels to send data and control information to gNB 108. Different types of physical uplink channels are possible, including, for example, the Physical Uplink Control Channel (PUCCH) and the Physical Uplink Shared Channel (PUSCH). The PUCCH carries control information from UE 104 to gNB 108, such as uplink control information (UCI), while the PUSCH carries data traffic (e.g., end-user application data) and may carry UCI.

[0048] UE 104 and gNB 108 can perform beam management operations to identify and maintain the desired beams for transmission in both the uplink and downlink directions. Beam management can be applied to both PDSCH and PDCCH in the downlink direction and both PUSCH and PUCCH in the uplink direction.

[0049] In one example, communication with the gNB 108 and / or the base station may utilize channels in the Frequency Range 1 (FR1) band (between 40 MHz and 7,125 MHz) and / or the Frequency Range 2 (FR2) band (between 24,250 MHz and 52,600 MHz). The FR1 band includes both licensed and unlicensed bands. The NR unlicensed band (NR-U) includes spectrum shared with other types of Radio Access Technologies (RATs) (e.g., LTE-LAA, WiFi, etc.). A Listen-Before-Speak (LBT) process can be used to avoid or minimize conflicts between different RATs in the NR-U, whereby the device should apply a Clear Channel Assessment (CCA) check before using the channel.

[0050] In one example, UE 104 and gNB 108 may transmit reference signals to locate UE 104 (e.g., to determine its geographic location, where the location can be absolute or relative to gNB 108). Various positioning methods are possible, including triangulation techniques, time-of-arrival techniques, time-of-flight techniques, angle-of-arrival techniques, received signal strength techniques, etc. At least some of these positioning methods rely on reference signals transmitted between UE 104 and gNB 108, and more specifically, on measurements performed on such reference signals. Example reference signals may include a PRS on the downlink and an SRS (SRSp) for positioning on the uplink. The use of PRS and SRSp is further described in the following figures. However, embodiments of this disclosure are not limited to only these two types of reference signals.

[0051] Figure 2Example 200 illustrates a UE's transmit bandwidth 210 and effective positioning bandwidth 220 according to some implementation schemes. For clarity, only transmit bandwidth 210 is described. However, the UE may also have a receive bandwidth that is the same as or different from transmit bandwidth 210. The description of transmit bandwidth 210 and its use in the context of UE positioning applies similarly and equivalently to receive bandwidth. In the transmit bandwidth case, the transmitted signal is an SRSp from the UE, and the receiving device is a gNB. The gNB receives the SRSp, performs measurements, and reports to the Location Management Function (LMF). In the receive bandwidth case, the transmitted signal is a PRS from the gNB, and the receiving device is the UE. The UE receives the PRS, performs measurements, and then reports to the LMF. For downlink, the gNB can transmit across the entire bandwidth, and the UE receives what it can receive. For uplink, the UE can only transmit and hop across its entire bandwidth. This difference in behavior is because the UE is bandwidth-limited, and when transmitting, it transmits to one gNB, while others listen to it. When a gNB transmits, it typically sends to multiple UEs, some of which are bandwidth-limited while others are not.

[0052] In one example, the transmit bandwidth 210 depends on the capabilities of the UE (such as the physical configuration of its transmit radio frequency (RF) chain). The UE can be a reduced-capability (RedCap) UE with reduced capabilities relative to a non-RedCap UE. Reduced capabilities involve the RedCap UE's communication bandwidth (Tx and / or Rx bandwidth), receive branch, multiple-input multiple-output (MIMO) layer, modulation order, and / or duplex operation. The expected traffic volume of a RedCap UE is expected to be relatively lower than that of a non-RedCap UE, and a RedCap UE can be expected to have lower battery consumption than a non-RedCap UE. Therefore, RedCap UEs typically have smaller transmit bandwidths than non-RedCap UEs.

[0053] UEs (including RedCap UEs) may support frequency hopping, enabling a larger effective bandwidth. For example, assume a transmit bandwidth of 20 MHz. Also assume the UE supports five frequency hoppings. In this case, an effective bandwidth of 100 MHz can be achieved by using five frequency hoppings. Frequency hopping can be used in the context of UE positioning, thereby extending PRS and / or SRSp transmissions across multiple frequency hoppings to achieve an effective positioning bandwidth 220. This effective positioning bandwidth 220 is typically greater than the transmit bandwidth 210 (and / or the UE's receive bandwidth). Typically, signal processing requires overlap to ensure phase coherence between hoppings. Therefore, up to six hoppings may be required.

[0054] Frequency hopping can be configured for a UE (including RedCap UEs) by, for example, a network (e.g., its base station). This configuration can indicate the frequency hopping pattern and associated parameters, such as the number of hopping subcarriers, the duration of each hop, and the hopping sequence.

[0055] For clarity, the transmission of SRSp using frequency hopping is further described below. In this case, positioning measurements are generated by the network (e.g., the base station receiving the SRSp, or the location management function providing the measurement to the base station). The positioning measurements are fed back or reported to the LMF. …For SRSp, the report is sent from the gNB to the LMF via NR Positioning Protocol a (NRPPa). Therefore, there are different challenges when using frequency hopping, including whether to feed back a single measurement for the effective positioning bandwidth 220 and / or measurements per frequency hop. Similar challenges exist on the downlink using PRS, where feedback is sent from the UE to the LMF via the LTE Positioning Protocol (LPP). Furthermore, there are cases where the full effective positioning bandwidth 220 is not used (e.g., instead of all five frequency hoppings, four frequency hoppings are used by the UE for SRSp transmission, or only SRSp transmissions on four frequency hoppings are received at the base station). Such cases also present challenges regarding measurement feedback. Solutions and related methods for such challenges are further described in the following figures.

[0056] The challenges and solutions described above apply similarly and equivalently to PRS reception. Specifically, the base station can frequency hopping or transmit the full PRS bandwidth because it has a full-bandwidth radio. The UE needs to frequency hopping during reception. On the receiving side, the UE can use frequency hopping for PRS reception, perform positioning measurements, and feed those measurements back to the LMF. Therefore, challenges exist and involve feeding back a single measurement for the full effective positioning bandwidth, feeding back measurements per frequency hop, or feeding back when only a portion of the effective positioning bandwidth is used. The solutions described in the context of SRSp transmission apply similarly and equivalently to PRS reception.

[0057] Figure 3An example of using a portion of the positioning bandwidth according to some implementation schemes is illustrated. Here, the UE (such as a RedCap UE) has a transmit bandwidth of 310 and is configured for frequency hopping. Frequency hopping is used for UE positioning, thereby transmitting PRS and / or SRS to and / or from the UE using the configured frequency hopping. As explained above, the SRSp transmission use case is described, whereby the UE transmits SRSp, the gNB receives the SRSp, and subsequently reports the positioning measurement feedback to the LMF. However, these techniques are equivalently applied to the PRS reception use case, whereby the UE feeds back the positioning measurement to the LMF. Generally, the process for PRS is as follows: (1) The LMF configures the gNB to transmit the PRS (e.g., by using NRPPa), (2) The LMF configures the UE to receive the PRS (e.g., by using LPP), (3) The LMF configures sufficient PRS signals (e.g., on a large bandwidth) for the UE to hop across the entire bandwidth with some overlap, (4) The gNB configures the UE to receive the PRS (e.g., by using RRC), (5) The gNB transmits the PRS, (6) The UE hops across the bandwidth, receives and measures the PRS, and (7) The UE feeds back the measurement to the LMF (e.g., by using LPP). In contrast, the procedure for SRSp is as follows: (1) The LMF configures the gNB to receive SRSp (e.g., by using NRPPa), (2) The LMF configures the UE to transmit SRSp (e.g., by using LPP), (3) The LMF configures sufficient SRSp signals for the UE to hop across the entire bandwidth with some overlap, (4) The gNB configures the UE to transmit signals for the actual SRSp (e.g., by using RRC), (5) The UE transmits SRSp and hops across the bandwidth, (6) The gNB receives and measures SRSp over a larger bandwidth, and (7) The gNB feeds back / reports the measurement to the LMF (e.g., by using NRPPa).

[0058] Specifically, in the SRP (Survey Service Spread) use case, the UE is the transmitter of the reference signal (e.g., SRP), and the base station is the receiver of the reference signal. Subsequently, the base station is the transmitter of the positioning measurement feedback, and the LMF (Location Measurement Filter) is the receiver of the positioning measurement feedback. In contrast, in the PRS (Purvey Service Responsibility) use case, the base station is the transmitter of the reference signal (e.g., PRS), and the UE is the receiver of the reference signal. Subsequently, the UE is the transmitter of the positioning measurement feedback, and the LMF is the receiver of the positioning measurement feedback. In both use cases, the techniques described herein involve transmitting positioning measurement feedback (by the base station in the SRP use case or the UE in the PRS case) based on the frequency hopping used in the transmission of the reference signal (by the UE in the SRP use case or the base station in the PRS case).

[0059] Generally, the UE has a transmission bandwidth of 310 and can be configured with frequency hopping parameters to achieve an effective positioning bandwidth greater than the transmission bandwidth of 310. In one example, the effective positioning bandwidth is used entirely for SRSp transmission. In this example, the LMF receives positioning measurement feedback from the base station, where the feedback is based on the full effective positioning bandwidth. Different methods exist for positioning measurement feedback. In one example method, the feedback includes only a single measurement corresponding to the full effective positioning bandwidth. In another example method, the feedback includes a single measurement corresponding to the full effective positioning bandwidth and per-hop measurements for all frequency hopping. In yet another example, a hybrid method can be used. For example, the feedback includes a single measurement corresponding to the full effective positioning bandwidth, per-hop measurements for some but not all frequency hopping, and / or a combination of measurements corresponding to two or more but not all frequency hopping.

[0060] In one example and as Figure 3 As shown, the effective positioning bandwidth is not fully utilized. For example, at least one frequency hopping frequency is unused (in...). Figure 3 The unused bandwidth 330 is exemplified here. There could be various reasons for this. For example, the UE might have used all frequency hopping for SRSp transmissions, but the base station might have already received SRP transmissions on a subset of the frequency hopping frequencies. In another example, the UE might actually only use a subset of the frequency hopping frequencies for SRSp transmissions. In either case, only a portion of the positioning bandwidth 320 is used. This bandwidth 320 corresponds to the frequency hopping subset, is less than the full effective positioning bandwidth (corresponding to the full set of frequency hopping frequencies), and may even be equal to the transmission bandwidth 310.

[0061] exist Figure 3 In the example shown, the feedback (e.g., transmitted by the base station in an SRP use case, or equivalently by the UE in a PRS use case) includes an indication 340 of unused effective positioning bandwidth. This indication 340 can notify the UE (or the base station in the PRS case) that the full effective positioning bandwidth is not being used. For example, the indication can be a single bit, where a bit value can be set to indicate that the full effective positioning bandwidth is not being used. It can also be a higher-layer signal flag indicating success or failure. Furthermore, the feedback can include a single measurement 350 of the maximum consecutive SRP transmissions (or equivalently, the maximum consecutive PRS transmissions), and a bitmap 360 indicating the combination to generate the frequency hopping (e.g., the frequency hopping corresponding to the maximum consecutive transmissions) of the single measurement 350.

[0062] Figure 4 Another example 400 illustrating the use of partial positioning bandwidth according to some implementation schemes is shown. The UE (such as a RedCap UE) has a transmit bandwidth 410 and is configured for frequency hopping to achieve effective positioning bandwidth. However, and with... Figure 3Similarly, the effective positioning bandwidth is not fully utilized. For example, at least one frequency hopping in a frequency hopping pattern is unused (in...). Figure 4 The unused bandwidth 430 is exemplified here. Therefore, only a portion of the positioning bandwidth is used (exemplified as including the first portion of positioning bandwidth 420A corresponding to the first two frequency hoppings and the second portion of positioning bandwidth 420B corresponding to the next two other frequency hoppings).

[0063] exist Figure 4 In the example shown, the feedback (e.g., transmitted by the base station in an SRS use case, or equivalently by the UE in a PRS use case) includes an indication 440 of unused effective positioning bandwidth. This indication 440 can be... Figure 3 Similar to indication 340, this notifies the UE (or the base station in the case of PRS) that the full effective positioning bandwidth is not being used. Furthermore, the feedback may include multiple measurements 350. Each of these measurements 350 may correspond to a different consecutive SRSp transmission (or equivalently, a different consecutive PRS transmission). Figure 4 In the example, two measurements are fed back, each corresponding to two consecutive frequency hopping intervals (e.g., the first measurement corresponds to a first portion of the positioning bandwidth 420A, and the second measurement corresponds to a second portion of the positioning bandwidth 420B). Furthermore, the feedback includes signaling, such as a bitmap 460 instructing the combination of frequency hopping intervals to generate measurement 450 (e.g., instructing the first two frequency hopping intervals to be used to generate the first measurement, and the next two frequency hopping intervals to be used to generate the second measurement).

[0064] Figure 5 Another example 500 illustrating the use of partial positioning bandwidth according to some implementation schemes is shown. The UE (such as a RedCap UE) has a transmission bandwidth 510 and is configured for frequency hopping to achieve effective positioning bandwidth. However, and with... Figures 3 to 4 Similarly, the effective positioning bandwidth is not fully utilized. For example, at least one frequency hopping in a frequency hopping pattern is unused (in...). Figure 5 The unused bandwidth 530 is exemplified here. Therefore, only a portion of the positioning bandwidth is used (exemplified as including five partial positioning bandwidths 520A, 520B, 520C and 520D, each of which may be the same as the transmission bandwidth 510 and correspond to a separate frequency hopping).

[0065] exist Figure 5 In the example shown, the feedback (e.g., transmitted by the base station in an SRS use case, or equivalently by the UE in a PRS use case) includes an indication 540 of unused effective positioning bandwidth. This indication 540 can be... Figure 3Similar to indication 340, this notifies the UE (or base station in the case of PRS) that the full effective positioning bandwidth is not being used. Furthermore, the feedback may include per-hop measurements and an indication 550 thereof. Specifically, positioning measurements may be generated per frequency hopping and may be included in the feedback. Additionally, an index of the measured location (e.g., an identifier of the frequency hopping) may be included in the feedback. Therefore, upon receiving feedback, the UE can determine the positioning measurements for each frequency hopping.

[0066] See again Figures 3 to 5 In cases where the effective positioning bandwidth is partially used, different types of measurements that can be included in the positioning measurement feedback are described. Additional or alternative methods are also possible. For example, a backoff mode is defined and used only when a portion of the positioning bandwidth is available. For instance, a backoff mode is used if a measurement with the full effective positioning bandwidth fails. In one example, every hop measurement is fed back in backoff mode, with the option to signal that the full effective positioning bandwidth was not used. Other possibilities exist, such as feeding back in backoff mode. Figures 3 to 5 The combination or all of the measurements described herein.

[0067] In one example, a single measurement across multiple frequency hopping is used in the positioning measurement feedback (e.g., by the base station in the SRS use case, or by the UE in the PRS use case). If a disconnection exists (e.g., only partial positioning bandwidth is available, or only discontinuous frequency hopping is available), the feedback may not be transmitted. Alternatively, if a disconnection exists, the feedback may be transmitted but may include an indication of whether the single measurement is a value (e.g., an indication of invalidity in the case of a disconnection).

[0068] For example, a single measurement across multiple frequency hopping is used in positioning measurement feedback (e.g., by the base station in an SRS use case, or by the UE in a PRS use case). Here, the single measurement may be based on a combination of frequency hopping. In this example, the feedback includes an indication of the combined frequency hopping. This indication may be in the form of a bitmap. Specifically, each frequency hopping may be represented by bits in the bitmap. The value of the bit representing the frequency hopping (e.g., "1") can be used to indicate that the frequency hopping is part of a combination.

[0069] In one example, multiple measurements are included in the location measurement feedback (e.g., by the base station in an SRS use case, or by the UE in a PRS use case), each corresponding to a combination of frequency hopping. Here, the feedback also includes an indication of the frequency hopping for each combination of measurements. This indication may be in the form of a bitmap. Specifically, each frequency hopping may be represented by bits in the bitmap. The value of the bit representing the frequency hopping (e.g., "1") can be used to indicate that the frequency hopping is part of a combination. Alternatively, each frequency hopping may be represented by multiple bits in the bitmap. A default value for the bit representation of the frequency hopping (e.g., "0 0" in a two-bit representation) can be used to indicate that the frequency hopping is not part of any combination. Another value may indicate the combination to which the frequency hopping belongs (e.g., a "0 1" value indicates a first combination corresponding to a first measurement, while a "1 0" value indicates a second, different combination corresponding to a second measurement).

[0070] In one example, per-hop measurements are included in the location measurement feedback (e.g., by the base station in the SRP use case, or by the UE in the PRS use case) and correspond to a single frequency hop. Per-hop measurements may be included in the feedback along with a single measurement across multiple frequency hops. Alternatively or in addition, per-hop measurements may be fed back in fallback mode and / or by themselves (e.g., based on an explicit measurement request from the UE in the SRP use case or the base station in the PRS use case). To facilitate per-hop measurements, an indication of which hops were measured and transmitted may be reported. Different options exist for this type of indication. In a first option, an indicator is transmitted per measurement report (e.g., {M1, [1 0 0], M2 [0 1 0], M3, [0 0 1]}, where “Mi” corresponds to the per-hop measurement, and [ijk] is a three-bit map for the three frequency hops, where a “1” value indicates that the measurement is for the corresponding frequency hop). In another option, the indicator is a bitmap transmitted as a group, identifying all measured transitions {M1, M3, [1 0 1]}. In yet another example, the indicator is implicit and no bitmap is used. Instead, a "0" value is reported for the measurement to indicate that no per-hop measurement was generated for the corresponding transition (e.g., {M1, 0, M3} indicates a per-hop measurement for each of the first and third hop frequencies, but no per-hop measurement was generated for the second hop frequency).

[0071] Figure 6An example of an operational flow / algorithm structure 600 for feedback positioning measurements implemented by a receiver according to some embodiments is illustrated. The receiver may be a component of a base station (e.g., in the use case of an SRSP) or a UE (e.g., in the use case of a UE). The reference signal used for positioning is described in conjunction with the operational flow / algorithm structure 600 and may refer to an SRSP, PRS, or any other type of reference signal that can be transmitted between the base station and the UE and can be used for UE positioning. The operational flow / algorithm structure 600 includes multiple operations. Some of these operations may be implemented, while the remaining operations may be omitted depending on whether the full bandwidth is used, whether a single measurement is desired, etc. Alternatively, all operations may be implemented, and specific operations may be used depending on a particular situation (e.g., depending on whether the full bandwidth is received).

[0072] In one example, the operation flow / algorithm structure 600 includes: at 610, receiving a reference signal for positioning. For example, the reference signal may be received based on a reference signal transmission using frequency hopping. In a specific SRSp use case, the UE (e.g., a RedCap UE) may use frequency hopping for SRSp transmission to achieve an effective positioning bandwidth greater than its transmission bandwidth. In a specific PRS use case, the base station may use UE frequency hopping to transmit multiple PRS transmissions to achieve an effective positioning bandwidth greater than the UE's reception bandwidth. If a request 601 for per-hop measurement is also received, the operation flow / algorithm structure 600 may proceed to operation 650. Otherwise, operations 620, 630, or 640 may be performed after operation 610. If all frequency hopping 602 is received (e.g., the effective positioning bandwidth is fully utilized), operation 620 may be performed after operation 610. Otherwise, some (but not all) of the frequency hopping 603 is received. In this case, either there is no single measurement feedback 604 to send, and therefore operation 630 can be performed after operation 610; or a best-effort service 605 is performed on the feedback measurement related to the received frequency hopping, and operation 640 can be performed after operation 610.

[0073] In one example, the operation flow / algorithm structure 600 includes, at 620, estimating a single measurement and indicating that all hops have been received. The single measurement may correspond to a combination of all frequency hopping, such that it is derived from an extension of the reference signal across the full effective positioning bandwidth. This indication may be a single bit having a value set to indicate the use of the full effective positioning bandwidth (e.g., "1"). If the receiver is configured (or requested) for both joint measurements and per-hop measurements 606, operation 650 may be performed after operation 620. Specifically, in addition to the single measurement, the receiver may also feed back one or more joint measurements and / or one or more per-hop measurements corresponding to a subset of combined frequency hopping. In such cases, operation 650 may be performed to also feed back the one or more joint measurements and / or the one or more per-hop measurements along with an indication (e.g., a bitmap) of the corresponding frequency hopping.

[0074] In one example, the operation flow / algorithm structure 600 includes: at 630, abandoning the generation of a single measurement because only a portion of the positioning bandwidth is available. Instead, an indication can be generated to indicate that not all frequency hopping is received (e.g., not the full effective bandwidth is being used). Operation 650 can be performed after operation 630. In this case, operation 650 may include sending an indication (but not a single measurement) in the positioning measurement feedback.

[0075] In one example, the operational flow / algorithm structure 600 includes: at 640, estimating a single measurement. For example, a single measurement based on the maximum consecutive transmissions can be generated. Furthermore, an indication can be generated to indicate that not all frequency hopping was received (e.g., not the full effective bandwidth was used). Additionally, the receiver can generate one or more joint measurements and / or possibly one or more per-hop measurements corresponding to the combined subset of frequency hopping. In this case, the indication can indicate the corresponding frequency hopping.

[0076] In one example, the operation flow / algorithm structure 600 includes, at 650, transmitting per-hop measurements and an indication identifying the corresponding hop frequency. Depending on the outputs of operations 620, 630, and 640, operation 650 may also include transmitting such outputs in the positioning measurement feedback.

[0077] See again Figures 2 to 6 And as explained above, PRS is an example of a downlink reference signal used for positioning. An on-demand PRS transmission procedure can be used. Specifically, this procedure allows the network's Location Management Function (LMF) to control and decide whether to transmit a PRS and to modify the characteristics of an ongoing PRS transmission. The on-demand PRS transmission procedure can be initiated by the UE or the LMF. The actual PRS change is requested by the LMF, regardless of whether the on-demand PRS transmission procedure is initiated by the UE or the LMF.

[0078] Generally, the on-demand PRS transmission process involves several steps. For example, information is exchanged via the LTE Location Protocol (LPP) between the LMF and the UE, and via the NR Location Protocol A (NRPPa) between the LMF and the base station (e.g., a gNB, or a gNB's Transmit / Receive Point (TRP)). This information exchange allows for the exchange of PRS configurations and on-demand PRS requests. UE-initiated requests may indicate predefined PRS configuration identifiers or explicit PRS configuration parameters, requests for PRS transmission, and / or changes to PRS transmission characteristics. LMF-initiated requests may involve obtaining UE measurements and / or changing PRS transmission characteristics.

[0079] As explained above, frequency hopping can be used in conjunction with UE positioning (e.g., in the use case of RedCap UEs, but not limited to this type of UE). Therefore, the PRS configuration that can be used as part of the on-demand PRS transmission process can be updated to accommodate the need for frequency hopping.

[0080] In an example of updating the PRS configuration for frequency hopping, it can be initially determined that the effective positioning bandwidth is greater than the UE's receive bandwidth. This determination can be made by the network (e.g., LMF) and / or the UE. Therefore, the PRS configuration can be linked to the desired effective positioning bandwidth. Using a one-to-one mapping, this link can be implicit. In other words, because frequency hopping is required to achieve the desired effective positioning bandwidth, it can be implicitly determined that the PRS configuration needs to support frequency hopping. Alternatively, an explicit link can be used instead of an implicit link. Here, an explicit mapping can be defined, where the required number of frequency hoppings can be based on both the PRS configuration and the desired effective positioning bandwidth. The PRS configuration can be updated accordingly. For example, information elements (IEs), such as the NR-On-Demand-DL-PRS-Configurations IE, can be updated. The NR-On-Demand-DL-PRS-Configurations IE provides a set of possible downlink PRS configurations that the target device can request on demand. The updates here can indicate identifiers for the downlink PRS configuration (as the desired configuration), whether to use frequency hopping for the PRS (e.g., as a flag), and bandwidth (e.g., an indication of effective positioning bandwidth), etc. For example, the NR-On-Demand-DL-PRS-Configurations IE can be defined as:

[0081]

[0082] In the IE above, "Dl-prs-configuration-id-r18" signals the desired configuration, "PRS_hopping" indicates whether frequency hopping is not used (e.g., with a value of "0") or frequency hopping is used (e.g., with a value of "1"), and "BW" indicates the desired effective positioning bandwidth.

[0083] Additionally, the IE used in on-demand PRS requests can be updated. An example IE is the NR-On-Demand-DL-PRS-Information IE. The NR-On-Demand-DL-PRS-Information IE defines the requested on-demand DL-PRS. This IE can contain the "PRS_hopping" and "BW" parameters.

[0084] Generally, various parameters can be indicated by requests initiated by the LMF (Local Frequency Frame) for on-demand PRS and / or by requests initiated by the UE. For the resource set of each positioning frequency layer in each frequency range (FR), parameters may include downlink PRS periodicity, downlink PRS resource bandwidth, downlink resource repetition factor, the number of downlink PRS resource symbols for each downlink PRS resource, and downlink PRS comb size. In the case of UE-initiated requests, parameters may also include the number of downlink frequency layers per FR and the start / end time of downlink PRS transmission for each UE. Additional parameters related to frequency hopping may also be included in both types of requests. These parameters include, for example, the overall expected effective positioning bandwidth, frequency hopping overlap between hopping frequencies, the number of hopping frequencies, whether intra-slot hopping is allowed, and / or whether inter-slot hopping is allowed.

[0085] In one example, frequency hopping is used by the UE for SRSp transmission. Because multiple frequency hoppings are used, there is a possibility of signal collisions between SRSp and non-SRSp signals (on the uplink and / or downlink). To mitigate this possibility, an uplink time window (shown as a window in the figures below and referred to as a window for SRSp transmission) and / or a collision rule (shown as a collision rule in the figures below and referred to as a collision rule for resolving signal collisions) can be used. The window can be an uplink time window, where the UE is not expected to receive and / or transmit other signals and / or channels, and is only expected to use frequency hopping to transmit SRSp. The collision rule can be associated with an uplink SRSp with frequency hopping and other uplink and / or downlink channels, and can specify, for example, the relative priority between such signals. The collision rule can allow the transmission of a first signal (whether SRSp or other signal) and prohibit the transmission of a second signal (whether SRSp or other signal) that would collide with the first signal (where at least one of the two signals is an SRSp), based on the relative priority between such signals. Windows and collision rules can be combined with each other or used alternately.

[0086] Figure 7 An example of a window 730 for SRSp transmission according to some embodiments is illustrated. As shown, the UE (e.g., a RedCap UE) may have a transmission bandwidth 710. SRSp transmission may use frequency hopping, such that SRSp is transmitted using an effective positioning bandwidth 720 greater than the transmission bandwidth 710 (or, conversely, possibly using a portion of the positioning bandwidth as described in the previous figures). The window 730 for SRSp transmission may be defined (e.g., configured via signaling from the network) to span the entire use (or at least a portion of the entire positioning bandwidth) of the frequency hopping sequence that causes the effective positioning bandwidth in the time domain.

[0087] In one example, window 730 represents the duration during which transmission and / or reception of signals other than SRSp are not expected. During this duration, the UE is only expected to use frequency hopping to transmit SRSp. In another example, the UE may be permitted to use frequency hopping to transmit SRSp only during window 730, thus prohibiting the UE from using frequency hopping to transmit SRSp outside of window 730. In yet another example, the UE may be permitted to use frequency hopping to transmit SRSp during window 730 (while other signals are not expected to be received or transmitted), and may also be permitted to use frequency hopping to transmit SRSp outside of window 730 (while other signals are expected to be received or transmitted; in this case, some signal priority ordering may be used).

[0088] Figure 8An example of a window for SRSp transmission according to some implementation schemes is illustrated. As shown, the UE (e.g., a RedCap UE) may have a transmission bandwidth 810. SRSp transmission may use frequency hopping, such that SRSp is transmitted using an effective positioning bandwidth 820 greater than the transmission bandwidth 810 (or, conversely, possibly using a partial positioning bandwidth as described in the previous figures). Individual windows can be defined (e.g., configured via signaling from the network), where each window corresponds to a frequency hop in a plurality of frequency hopping schemes. The window corresponding to the frequency hop can span the use of frequency hopping in the time domain. Figure 8 In the example, five frequency hopping frequencies are shown (e.g., as blank rectangles). Therefore, five windows 830A, 830B, 830C, 830D, and 830E are defined, each corresponding to a different frequency hopping frequency (e.g., window 830A corresponds to the first frequency hopping, window 830B to the second frequency hopping, window 830C to the third frequency hopping, window 830D to the fourth frequency hopping, and window 830E to the fifth frequency hopping). For simplicity, any of these windows 830A, 830B, 830C, 830D, and 830E may be referred to as window 830.

[0089] In one example, window 830 represents the duration during which no signal other than SRSp is expected to be transmitted and / or received. During this duration, the UE is only expected to use frequency hopping to transmit SRSp. In another example, the UE may be permitted to use frequency hopping to transmit SRSp only during window 830, such that the UE is prohibited from using frequency hopping outside window 830 to transmit SRSp (until the next frequency hopping configured for SRSp transmission). In yet another example, the UE may be permitted to use frequency hopping to transmit SRSp during window 830 (while no other signal is expected to be received or transmitted, or to utilize a signal of higher priority), and may also be permitted to use frequency hopping to transmit SRSp outside window 830 (while other signals are expected to be received or transmitted).

[0090] although Figure 7 A window for full effective bandwidth is described, and although Figure 8 A window for each frequency hopping is described, but embodiments of this disclosure are not limited thereto. For example, the window may be defined for multiple frequency hoppings (e.g., two or more) rather than the entire frequency hopping sequence. If multiple windows are defined across frequency hopping patterns, the durations of these windows may, but do not have to, be the same.

[0091] See again Figure 7 and Figure 8The window (e.g., window 730, or any of windows 830A through 830E) can be a configured window within which the UE is only expected to transmit FH SRS for positioning. The window can be configured via higher-layer parameters, such as UL-SRS-FH-Window-Preconfig. This parameter may indicate an identifier (e.g., ul-SRS-FH-Window-ID: a pre-configured identifier (ID) configured for the uplink SRS hopping window), and / or may indicate periodicity and the offset of the start slot (e.g., ul-SRS-FH-PeriodicityandStartSlot: the periodicity and the offset of the start slot relative to the system frame number (SFN) zero and slot number zero of the reference serving cell to which the uplink SRS (e.g., SRSp) is to be transmitted). The window can be valid for other cells that can be the receiver of the SRS (e.g., SRSp). The reference serving cell can be a primary cell or a reference cell (e.g., a secondary cell) configured for positioning. The periodicity and / or offset values ​​can be related to the subcarrier spacing. The length of the window can also be indicated in this parameter. The length can be a time slot. In this case, the probability of dropping SRS is minimized (e.g., because the window spans at least the entire time slot). The length can be a sub-time slot. In this case, the UE has the opportunity to transmit other signals outside the window and within the time slot containing the window. In yet another example, the length can be in symbols. Here, the UE also has the opportunity to transmit other signals outside the window and within the time slot containing the window. The length can be defined in a specific time base (such as gNSS, UTC time, etc.).

[0092] Once the window is configured, different usage types are possible. In one example, uplink frequency-hopping SRS can be configured to be transmitted only within the window. In other words, the UE can only use frequency hopping to transmit SRSp during the window period. Alternatively, uplink frequency-hopping SRS can be configured to be transmitted both within and outside the window. In other words, the UE is not expected to use frequency hopping to transmit and / or receive other signals during the window period, but is permitted to use frequency hopping to transmit SRSp both during and outside the window.

[0093] Generally, when using frequency hopping and time windows, signal collisions can be avoided because the UE is not expected to transmit and / or receive non-SRS signals during the window period. To fine-tune this collision avoidance without reducing throughput (e.g., by defining the duration of the time window as longer than the desired duration), the length of the time window can be set to the number of symbols, where the start and end can depend on several parameters, such as bandwidth partial switching, RF retuning, receive-to-transmit switching, and / or send-to-receive switching, etc. Figure 9 The example is also shown in the text.

[0094] Figure 9 Examples of parameters for the window used for SRSp transmission, defined according to some implementation schemes, are shown. Figure 9 The upper part illustrates a first example 900, in which the UE switches from receiving to transmitting to send SRS, and then subsequently switches back to receiving. Figure 9 The second example 950 is illustrated in the lower half, where the UE does not perform a downlink-to-uplink handover, and vice versa. Of course, other examples also exist, such as when the UE switches from downlink to uplink but then does not immediately switch back to downlink, or when the UE sends an SRS while in uplink transmission and subsequently switches to downlink reception.

[0095] As shown in the first example 900, the UE receives a signal on downlink 902. The UE then switches to transmitting SRS 904 for positioning, where this transmission uses frequency hopping. Immediately following SRS transmission 904, the UE switches back to receiving a signal on downlink 906. For this purpose, the first handover involves a bandwidth portion switch, RF retuning, and a received transmission chain switch. The length of the first handover is X * [missing information] before SRS transmission 904 (e.g., before the start of transmission 904, where it may begin at a specific symbol). DL 910 symbols (e.g., the first duration defined by the number of symbols), where X DL The second handover is a positive integer. It involves bandwidth portion switching, RF retuning, and transmission-to-reception chain switching. The length of the second handover is Y * [value missing] after SRS transmission 904 (e.g., after the end of transmission 904, where it may end at a specific symbol). DL 920 symbols (e.g., the second duration defined by the number of symbols), where Y DL It is a positive integer. Therefore, if any part of another downlink signal or channel is affected by X before SRS 904 is transmitted... DL The symbol 910 begins and Y is enabled after SRS sends 904. DL If the time intervals ending with symbol 920 overlap, then the uplink frequency-hopping SRS instance will conflict with another downlink signal or channel. Therefore, in this example, the window can be defined as X before SRS 904 is transmitted. DL The Y symbol begins at position 910 and is transmitted after SRS 904. DL The sequence ends at point 920.

[0096] As shown in the second example 950, the UE transmits a signal on uplink 952. The UE then uses a different bandwidth portion to transmit SRS 954 for positioning, where this transmission uses frequency hopping. And immediately following the SRS transmission 954, the UE uses another bandwidth portion on uplink 956. For this purpose, the UE also performs two handovers. The first handover involves bandwidth portion switching and RF retuning. The length of the first handover is X before the SRS transmission 954 (e.g., before the start of the transmission 954, where it may begin at a specific symbol). UL 960 symbols (e.g., the first duration defined by the number of symbols), where X UL The second handover is a positive integer. It involves a bandwidth portion switch and RF retuning. The length of the second handover is Y * [value missing] after SRS transmission 954 (e.g., after the end of transmission 954, where it may end at a specific symbol). UL 970 symbols (e.g., the second duration defined by the number of symbols), where Y UL It is a positive integer. Therefore, if any part of another uplink signal or channel is related to X before SRS 954 is transmitted... UL The symbol 960 begins and Y is made after SRS transmission 954. UL If the time intervals ending with symbol 970 overlap, then the uplink frequency-hopping SRS instance will conflict with another uplink signal or channel. Therefore, in this example, the window can be defined as X before SRS 954 is transmitted. UL Y starts at symbol 960 and is sent after SRS 954. UL The symbol ends at point 970.

[0097] In one example, X and Y (representing the number of first symbols before frequency-hopping SRS transmission and the number of second symbols after frequency-hopping SRS transmission, respectively, and related to the aforementioned X) DL and / or X UL and Y DL and / or Y UL Correspondingly, X and Y can depend on the subcarrier. Furthermore, X and Y can differ for downlink symbols / channels and uplink symbols / channels (e.g., X...). DL Can be with X UL Different, and / or Y DL Can be with Y UL (Different). X and Y can also be different from each other (or equal), and each can be based on the UE capabilities associated with the required handover. In one example, the window configuration may include definitions (e.g., values) for X and Y (e.g., these two parameters can be configured via higher-layer signaling).

[0098] Therefore, for X symbols prior to the start of SRSp transmission using frequency hopping, the UE is not expected to receive and / or process downlink symbols and / or transmit and / or process uplink symbols. Therefore, the reception, processing, and / or transmission of such symbols can be abandoned. Similarly, for Y symbols after the end of SRSp transmission using frequency hopping, the UE is not expected to receive and / or process downlink symbols and / or transmit and / or process uplink symbols. Therefore, the reception, processing, and / or transmission of such symbols can be abandoned.

[0099] Figure 10 Examples of conflict rules for SRSp transmission according to some implementation schemes are illustrated. As shown, a UE (e.g., a RedCap UE) may have a transmission bandwidth 1010. SRSp transmission may use frequency hopping, such that an effective positioning bandwidth 1020 greater than the transmission bandwidth 1010 is used to transmit SRSp (or, conversely, a partial positioning bandwidth as described in previous figures may be used). When multiple frequency hoppings are used, a conflict rule 1040 may be associated with SRSp transmission. Specifically, conflict rule 1040 may indicate the priority of SRSp and other signals, such that a relative priority between signals can be determined (e.g., the relative priority of SRSp relative to any other signal among the other signals). When SRSp transmission is performed using frequency hopping, in the event of a conflict between SRSp transmission and the reception and / or transmission of any other signal using frequency hopping, conflict rule 1040 allows certain transmissions and / or receptions based on relative priority. For example, SRSp transmission may have the highest priority, such that SRSp transmission is allowed.

[0100] In another example, and as shown by the dashed line, conflict rule 1040 can be used as a standalone rule (e.g., independent of window 1030 for SRSp transmission) or in combination with window 1030 for SRSp transmission. As a standalone rule, window 1030 is not configured, or if configured, it does not need to be used. If combined, conflict rule 1040 applies only to SRSp transmissions during window 1030 and cannot be applied to SRSp transmissions outside window 1030 (if any).

[0101] exist Figure 10 In the diagram, conflict rule 1040 applies to the entire frequency hopping sequence. That is, if a signal conflict exists in any frequency hopping, conflict rule 1040 can prioritize SRSp transmissions across the entire frequency hopping sequence. For example, suppose a signal conflict occurs in one frequency hopping, such as... Figure 10The image is shown as a diagonally dashed rectangle. When a signal collision exists, collision rule 1040 only allows SRSp to be transmitted. Therefore, because a signal collision exists in one of the frequency hopping sequences, the frequency hopping sequence cannot be used to transmit (or receive) signals other than SRSp.

[0102] Figure 11 Another example of a conflict rule for SRSp transmission according to some implementation schemes is illustrated. Here, the UE (e.g., a RedCap UE) may also have a transmission bandwidth 1110. SRSp transmission may use frequency hopping, such that an effective positioning bandwidth 1120 greater than the transmission bandwidth 1110 is used to transmit the SRSp (or, conversely, a partial positioning bandwidth as described in the previous figures may be used). When multiple frequency hopping is used, conflict rules may be associated with SRSp transmission. Specifically, conflict rules may indicate the priority of SRSp and other signals, such that the relative priority between signals can be determined (e.g., the relative priority of SRSp relative to any other signal among the other signals). When SRSp transmission is performed using frequency hopping, if a conflict occurs between the SRSp transmission and the reception and / or transmission of any other signal using frequency hopping in the frequency hopping sequence, the conflict rule is only appended to the frequency hopping where the signal conflict occurs. The appended conflict rule allows certain transmissions and / or receptions using frequency hopping based on relative priority, but such constraints do not apply to other frequency hopping in the frequency hopping sequence where there is no signal conflict.

[0103] exist Figure 11 In the example, it is assumed that a signal collision occurs in one of the frequency hopping frequencies, as shown by the diagonal dashed rectangle. If a signal collision exists when using frequency hopping, the collision rule only allows SRSp transmission during that frequency hopping period and is only appended to that frequency hopping. Therefore, because a signal collision exists in a particular frequency hopping, that frequency hopping is only allowed for SRSp transmission (assuming the SRSp has the highest relative priority 1140). However, due to this signal collision, no constraints are imposed on the use of any other frequency hopping in the other frequency hopping sequence (e.g., ...). Figure 11 As shown, because the relative priority of SRSp is not considered in these other frequency hopping (1150).

[0104] In another example, and as shown by the dashed lines, the conflict rule can be used as a standalone rule (e.g., independent of the window used for SRSp transmission) or in combination with individual windows 1130A, 1130B, 1130C, 1130D, and 1130E, each corresponding to a specific frequency hopping frequency. As standalone rules, windows 1130A through 1130E are not configured, or if configured, they do not need to be used. When combined, the conflict rule is applied to SRSp transmission only during a specific window 1130A, 1130B, 1130C, 1130D, or 1130E.

[0105] Despite Figure 11 The example illustrates separate windows corresponding to different frequency hopping frequencies, but such windows can be combined with... Figure 10 The conflict rule 1040 is used in conjunction with it. Conversely, the window 1030 spanning the entire frequency hopping sequence can be used with... Figure 11 Use them together with conflict rules.

[0106] See again Figures 10 to 11 A signal collision occurs when an uplink frequency-hopping SRS instance conflicts with a downlink signal / channel and / or uplink signal / channel if any part of other downlink signals / channels and / or uplink signals / channels overlaps with a time interval that starts with X symbols before SRSp transmission and ends with Y symbols after that transmission. X symbols and Y symbols can be defined as described above. Here, similarly, Figure 9 X DL and X UL It is an example of X, and Figure 9 Y DL and Y UL This is an example of Y. Specifically, X and Y can depend on retuning of the active bandwidth portion, rapid retuning of the RF frequency, and switching of transmit and receive channels, such as... Figure 9 As described above. Regarding retuning of the active bandwidth portion, X and Y may depend on whether the uplink and / or downlink signals are transmitted via frequency hopping or at the frequency of the active bandwidth portion. This depends on whether the active bandwidth portion used for communication remains the same on frequency hopping, or whether the active bandwidth portion changes with frequency hopping. Regarding rapid retuning of the RF frequency, if the active bandwidth portion used for communication remains the same or different, X and Y may depend on rapid retuning of the RF to the active communication bandwidth portion. Regarding transmit and receive channel switching, for the downlink channel, X and Y may depend on the transmit and receive switching time to enable the UE to switch from receive (downlink channel receive) to transmit (uplink channel transmit), and vice versa. This may be specified in the UE's compatible technical specifications and / or may depend on the UE's capabilities, assuming the UE may have varying complexities. For the uplink channel, the effects of receive and transmit switching can be ignored.

[0107] Uplink frequency-hopping SRS transmission can depend on the relative priority of the colliding signals and the channel. For example... Figure 11 As shown, in the event of a signal collision, if the collision occurs on a specific frequency hopping frequency, the uplink frequency hopping SRS can be transmitted (when it has a higher priority than other colliding signals and the other signals are dropped) or dropped (when it has a relatively lower priority and the other signals are transmitted). In contrast, as Figure 10As shown, the collision rule is a total bandwidth collision rule. Specifically, if a collision occurs on any frequency hop in the frequency hopping process, all uplink hop frequency SRSs are either dropped (when the uplink hop frequency SRS has a higher priority than other colliding signals and the other signals are dropped during the frequency hopping sequence) or transmitted (when the uplink hop frequency SRS has a higher priority than other colliding signals and the other signals are transmitted during the frequency hopping sequence).

[0108] Conflict rules can be priority-based. Specifically, the rule can indicate the relative priority of the uplink frequency-hopping SRS compared to other downlink and uplink signals. In one example, there is no distinction between uplink and downlink, and the same set of priorities is defined. Alternatively, a distinction can be made between uplink and downlink, with one set of priorities defined for the uplink and a different set for the downlink. Table 1 below illustrates the use of two different priority sets.

[0109]

[0110] Table 1

[0111] In Table 1 above, any one of the indicators Pd1 to Pd4 can be set for the uplink frequency hopping SRS to define its relative priority to the downlink. Similarly, any one of the indicators Pu1 to Pu4 in Table 1 can be set for the uplink frequency hopping SRS to define its relative priority to the uplink.

[0112] In one example, the relative priority of the uplink frequency hopping SRS compared to other downlink and uplink signals can be configured based on higher-layer signaling. For example, higher-layer signaling (such as RRC signaling) can set the relative priority of the uplink frequency hopping SRS relative to all downlink signals (e.g., PDCCH / PDSCH / CSI-RS) and / or relative to all other uplink signals (e.g., PRACH / PUCCH / PUSCH). Other signaling can be possible, such as LPP.

[0113] For example, relative priorities can be predefined instead of being configured via higher-layer signaling. This is similar to priorities defined for carrier aggregation. Predefinition can be specified in the UE's compatible technical specifications and / or can be a UE-specific implementation. In one example, for the uplink, PRACH and PUCCH / PUSCH have higher priority values, PUCCH / PUSCH have the same priority index, and SRS transmissions with aperiodic SRS have higher priority than SPS or periodic SRS. The uplink frequency-hopping SRS can be positioned at a specific location within this hierarchy. On the downlink, SSB has higher priority than PDCCH, which has higher priority than PSDCH, which has higher priority than CSI-RS. The uplink frequency-hopping SRS can be positioned at a specific location within this hierarchy.

[0114] In one example of a process for using conflict rules, the UE determines uplink frequency hopping conflict parameters. These parameters include X, Y, and / or priority (e.g., relative priority indicators as shown in Table 1) and can be predefined or configured via higher-layer signaling. If conflict parameters are determined for frequency hopping (e.g., as shown in Table 1),... Figure 11 In the conflict rules, X symbols prior to transmission (e.g., during the first duration before the start of SRSp transmission using frequency hopping), the UE performs a priority analysis of all signals / channels for a single frequency hopping. The UE can then transmit the signal with the highest priority (in the event of signal collisions that would occur with frequency hopping, if the uplink frequency-hopping SRS does not have the highest priority, the UE can discard it, or it can otherwise transmit it and discard other conflicting lower-priority signals). If conflict parameters are determined for the entire frequency hopping sequence (e.g., as in...), Figure 10 In the conflict rules, the UE performs a priority analysis of all signals / channels for all frequency hopping at X symbols prior to transmission (e.g., during the first duration before the start of SRSp transmission using frequency hopping sequences). Here, if the uplink frequency hopping SRS has the highest priority, the UE can transmit that SRS for all frequency hopping.

[0115] Figure 12 An example of an operational flow / algorithm structure 1200 for user equipment positioning according to some implementation schemes is illustrated. The operational flow / algorithm structure 1200 can be implemented by a UE (such as any of the UEs described herein) to transmit SRS for positioning, wherein the transmission uses frequency hopping.

[0116] In one example, the operation flow / algorithm structure 1200 includes: at 1202, receiving configuration information from the network associated with the transmission of a probe reference signal (SRSp) for positioning, the SRSp transmission using frequency hopping to achieve an effective positioning bandwidth for the SRSp transmission, wherein the UE is a UE with reduced transmission bandwidth capability (RedCap), and the effective positioning bandwidth is greater than the transmission bandwidth of a RedCap UE.

[0117] In one example, the operation flow / algorithm structure 1200 includes, at 1204, determining a configuration associated with frequency hopping for transmitting SRSp, wherein the configuration is specific to multiple frequency hopping frequencies or frequency hopping among the multiple frequency hopping frequencies, and includes at least one of a window for SRSp transmission or a conflict rule for resolving signal conflicts between SRSp and non-SRSp signals. This configuration may be specified in configuration information (e.g., signaled by higher-layer signaling) or predefined. The configuration information may configure SRSp transmission and may include, for example, indications of X, Y, priority, etc.

[0118] Based on this configuration, at least one of operation 1206 or operation 1208 will be executed. Specifically, if the configuration includes only windows, only operation 1206 will be executed. Conversely, if the configuration includes only conflict rules, only operation 1208 will be executed. However, if the configuration includes only both windows and conflict rules, both operation 1206 and operation 1208 will be executed.

[0119] In one example, the operation flow / algorithm structure 1200 includes: at 1206, when the configuration includes a window, transmitting an SRSp during the window period, wherein the RedCap UE abandons signal transmission or reception for a first duration before the start of the window and for a second duration after the end of the window. The first duration may begin X symbols before the SRSp transmission. The second duration may end Y symbols after the SRSp transmission.

[0120] In one example, the operation flow / algorithm structure 1200 includes: at 1208, when the configuration includes conflict rules, sending SRSp based on signal priority, wherein the signal priority is determined at or within a first duration before the start of SRSp transmission.

[0121] Figure 13Examples of using one or more spatial domain transmission filters for user equipment, according to some implementation schemes, are illustrated. UE 1304 (such as an Industrial Internet of Things (IoT) device or any other type of device) can implement Low Power High Accuracy Positioning (LPHAP) technology. UE 1304 can be configured with spatial relation information that indicates one or more spatial domain filters (e.g., for beamforming) for transmitting SRS to support UE positioning using the positioning method. The spatial relation information can be configuration information specified by higher-level parameters (such as spatialRelationInfoPos).

[0122] When UE 1304 is in the RRC_CONNECTED state, the following UE behaviors can be specified. If the UE is not configured with the higher-layer parameter spatialRelationInfoPos, UE 1304 can use a fixed spatial domain transmission filter across multiple SRS resources to transmit SRS configured by the higher-layer parameter SRSPosResource, or UE 1304 can use different spatial domain transmission filters across multiple SRS resources.

[0123] When UE 1304 is in the RRC_INACTIVE state, spatial validity criteria for SRS transmission can be specified and the following UE behavior can be observed. If UE 1304 is in the RRC_INACTIVE state and it is determined that UE 1304 cannot accurately measure the configured downlink reference signal (where the downlink reference signal is semi-persistent or periodic) in the SRS-SpatialRelationInfoPos for SRS resources used for positioning, then UE 1304 stops transmitting SRS resources for positioning.

[0124] Additionally, when UE 1304 is in the RRC_INACTIVE state, the following UE behaviors are possible for the spatial relationships of SRS configured for positioning in multiple cells. When spatial relationship information is not present in the configuration, UE 1304 can use a fixed spatial domain transmission filter across multiple SRS resources to transmit the SRS configured by the higher-layer parameter SRS-PosResource, or UE 1034 can use different spatial domain transmission filters across multiple SRS resources. When spatial relationship information is provided in the configuration, it can be applied across cells within the effective area. In this case, a validity criterion for the spatial relationship information can be defined, and it can also be defined whether / how to determine UE fallback behavior if the validity criterion for the spatial relationship of the configured RS is not met. Such definitions (e.g., validity criteria and fallback behavior when spatial relationship information is provided in the configuration) are also described in this disclosure.

[0125] like Figure 13 As shown, UE 1304 communicates with multiple base stations (e.g., gNB 1308A, gNB 1308B, gNB 1308C, and gNB 1308C) that each provide a cell. However, it is possible for UE 1304 to communicate with base stations providing multiple cells. In this example, UE 1304 is configured with a set of one or more SpatialRelationInfoPos for SRS resources used for positioning. SpatialRelationInfoPos may be specific to a cell identifier (e.g., configured for a corresponding cell). Additionally or alternatively, SpatialRelationInfoPos may be specific to a set of cell identifiers (e.g., configured for a corresponding group of cells).

[0126] In one example, the number of SpatialRelationInfoPos configurable per region may depend on UE capabilities. In one example, one SpatialRelationInfoPos is configured per cell identifier and / or per group of cell identifiers (e.g., the size of the configured SpatialRelationInfoPos set is one). A single configured SpatialRelationInfoPos may correspond to a single spatial domain transmission filter available for both FR1 and FR2. Alternatively, more than one SpatialRelationInfoPos may be configured per cell identifier and / or per group of cell identifiers (e.g., the size of the configured SpatialRelationInfoPos set is greater than one). For example, each configured SpatialRelationInfoPos may correspond to a different spatial domain transmission filter available for FR2.

[0127] The spatial relationship validity criterion for SRS transmission and UE behavior can be defined as follows. If UE 1304 is in the RRC_INACTIVE or RRC_IDLE state, and it is determined that UE 1304 cannot accurately measure the number of “N” configured downlink reference signals (where the downlink reference signals are semi-persistent or periodic) in the SRS-SpatialRelationInfoPos for SRS resources used for positioning for each cell identifier and / or each group of cell identifiers, then UE 1304 may fall back to the behavior assuming the SRS information does not exist or stop transmitting SRS resources for positioning. Fallback behaviors include: UE 1304 using a fixed spatial domain transmission filter to transmit SRS configured by the higher-layer parameter SRS-PosResource across multiple SRS resources, or UE 1304 using different spatial domain transmission filters across multiple SRS resources. The number “N” may depend on the positioning method and the number of SRS-SpatialRelationInfoPos parameters supported by the UE's capabilities. For example, “N” may be set to “…”. .

[0128] In one example, if only one SRS-SpatialRelationInfoPos is configured, then "N" is one. Similarly, if multiple SRS-SpatialRelationInfoPos are configured and three anchor points are required for positioning (e.g., in the case of triangulation positioning), then "N" is three. In yet another example, "N" can be configured at a higher level. For example, if the positioning method requires a different number of anchor points, "N" can be set in the SRS-SpatialRelationInfoPos configuration. Generally, in these examples, if UE positioning cannot be measured with the target accuracy (or minimum accuracy) using "N" configured downlink reference signals, then fallback behavior can be followed.

[0129] See again Figure 13 Assume that positioning method 1310 requires “M” anchor locations. For example, in the case of triangulation, “M” can be three, allowing the use of triangulation involving at least three of the four cells provided by gNBs 1308A to 1308D. Assume that UE 1304 can accurately measure fewer than “N” configured downlink reference signals. Here, if “N” is less than “M”, the UE can use a fixed or different spatial domain transmission filter 1330 depending on the backoff behavior, or it can stop SRS transmission 1340.

[0130] Figure 14Another example of an operational flow / algorithm structure 1400 for user equipment positioning, according to some implementation schemes, is illustrated. Operational flow / algorithm structure 1400 can be implemented by a UE (such as any of the UEs described herein) to transmit SRS for positioning, wherein this transmission uses frequency hopping.

[0131] In one example, the operation flow / algorithm structure 1400 includes: at 1402, receiving configuration information from the network, which includes a set of SRS-SpatialRelationInfoPos parameters for probe reference signal (SRS) resources used for positioning, wherein the SRS-SpatialRelationInfoPos parameters indicate the spatial domain transmission filter used for SRS transmission.

[0132] In one example, the operation flow / algorithm structure 1400 includes: at 1404, when the UE is in the RRC_INACTIVE state or the RRC_IDLE state, determining that the UE is unable to measure the number of “N” configured downlink reference signals in the SRS-SpatialRelationInfoPos parameter for SRS resources for each cell identifier or each group of cell identifiers with predefined accuracy.

[0133] In one example, the operation flow / algorithm structure 1400 includes: at 1406, based on the lack of capability, abandoning the transmission of SRS resources or transmitting SRS resources based on one or more spatial domain transmission filters that do not exist in the configuration information.

[0134] Figure 15 A receiver assembly 1500 for a UE 104 or gNB 108 according to some embodiments is illustrated. The receiver assembly 1500 may include an antenna panel 1504 that includes a plurality of antenna elements. The panel 1504 is shown as having four antenna elements, but other embodiments may include a different number of antenna elements.

[0135] Antenna panel 1504 may be coupled to an analog beamforming (BF) assembly comprising multiple phase shifters 1508(1) to 1508(4). Phase shifters 1508(1) to 1508(4) may be coupled to radio frequency (RF) chain 1512. RF chain 1512 may amplify received analog RF signals, downconvert RF signals to baseband, and convert analog baseband signals into digital baseband signals that can be provided to a baseband processor for further processing.

[0136] In various implementations, control circuitry residing in the baseband processor may provide phase shifters 1508(1) to 1508(4) with BF weights (e.g., W1 to W4) that represent phase shift values ​​to provide a receive beam at antenna panel 1504. These BF weights may be determined based on channel-based beamforming.

[0137] Figure 16 An example of UE 1600 according to some implementation schemes is shown. UE 1600 may be similar to Figure 1 The UE 104 is basically interchangeable with it.

[0138] Similar to the description of UE 104 above, UE 1600 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, computer, tablet, industrial wireless sensors (e.g., microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, inventory sensors, voltmeters / ammeters, and actuators), video surveillance / monitoring devices (e.g., cameras and camcorders), wearable devices, or relaxed IoT devices. In some implementations, the UE can be a reduced-capacity UE or an NR lightweight UE.

[0139] UE 1600 may include a processor 1604, RF interface circuitry 1608, memory / storage device 1612, user interface 1616, sensor 1620, drive circuitry 1622, power management integrated circuit (PMIC) 1624, and battery 1628. The components of UE 1600 may be implemented as integrated circuits (ICs), portions of such integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 16 The block diagram is intended to show a high-level view of some of the components of the UE 1600. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0140] The components of UE 1600 can be coupled to a variety of other components via one or more interconnects 1632, which can represent any type of interface, input / output, bus (local, system, or extended), transmit line, trace, optical connector, etc., allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0141] Processor 1604 may include processor circuitry, such as, for example, baseband processor circuitry (BB) 1604A, central processing unit circuitry (CPU) 1604B, and graphics processing unit circuitry (GPU) 1604C. Processor 1604 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional procedures from memory / storage device 1612) to cause UE 1600 to perform the operations described herein.

[0142] In some implementations, the baseband processor circuit 1604A can access the communication protocol stack 1636 in the memory / storage device 1612 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 1604A can access the communication protocol stack to perform user plane functions at the PHY, MAC, RLC, PDCP, SDAP, and PDU layers; and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and non-accessible (NAS) layers. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuit 1608.

[0143] The baseband processor circuit 1604A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.

[0144] The baseband processor circuit 1604A can also access group information 1624 from memory / storage device 1612 to determine multiple repeating search space groups in which PDCCH can be sent.

[0145] The memory / storage device 1612 may include any type of volatile or non-volatile memory that can be distributed throughout the UE 1600. In some embodiments, some of the memory / storage devices 1612 may be located on the processor 1604 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 1612 may be located outside the processor 1604 but accessible via a memory interface. The memory / storage device 1612 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0146] The RF interface circuitry 1608 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows the UE 1600 to communicate with other devices via a radio access network. The RF interface circuitry 1608 may include various components arranged in the transmit or receive path. These components may include switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0147] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna 1624, and further filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which downconverts the RF signal into a baseband signal that is provided to the baseband processor of processor 1604.

[0148] In the transmission path, the transceiver's transmitter up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM can then amplify the RF signal using a power amplifier before it is radiated across the air interface via antenna 1624.

[0149] In various implementations, the RF interface circuit 1608 can be configured to transmit / receive signals in a manner compatible with NR access technologies.

[0150] Antenna 1624 may include multiple antenna elements, each of which converts an electrical signal into a radio wave to travel through the air and converts received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 1624 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input multiple-output communication. Antenna 1624 may include a microstrip antenna, a printed antenna fabricated on the surface of one or more printed circuit boards, a patch antenna, a phased array antenna, etc. Antenna 1624 may have one or more panels designed for a specific frequency band including the frequency bands in FR1 or FR2.

[0151] User interface circuitry 1616 includes various input / output (I / O) devices designed to enable a user to interact with UE 1600. User interface 1616 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual components for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphone, scanner, or headset, etc. Output device circuitry includes any physical or virtual components for displaying information or otherwise conveying information such as sensor readings, actuator positions, or other similar information. Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators such as light-emitting diodes (LEDs) and multi-character visual outputs), or more complex outputs (e.g., display devices or touchscreens such as liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.)), wherein the output of characters, graphics, and multimedia objects, etc., is generated or produced by the operation of UE 1600.

[0152] Sensor 1620 may include a device, module, or subsystem intended to detect events or changes in its environment and transmit information (sensor data) about the detected events to another device, module, subsystem, etc. Examples of such sensors include, in particular, inertial measurement units, which include accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems including: triaxial accelerometers, triaxial gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; etc.

[0153] The driving circuitry 1622 may include software and hardware elements that operate to control a specific device embedded in, attached to, or otherwise communicatively coupled to the UE 1600. The driving circuitry 1622 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 1600. For example, the driving circuitry 1622 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for obtaining sensor readings from the sensor circuitry 1620 and controlling and allowing access to the sensor circuitry 1620; a driver for obtaining actuator positioning of an electromechanical component or controlling and allowing access to an electromechanical component; a camera driver for controlling and allowing access to an embedded image capture device; or an audio driver for controlling and allowing access to one or more audio devices.

[0154] The PMIC 1624 manages the power supplied to various components of the UE 1600. Specifically, relative to the processor 1604, the PMIC 1624 controls power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0155] In some implementations, the PMIC 1624 can control or otherwise become part of various power-saving mechanisms of the UE 1600. For example, if the platform UE is in the RRC_Connected state, where it remains connected to the RAN node as it anticipates receiving traffic soon, then after a period of inactivity, the platform UE can enter a state known as Discontinuous Receive Mode (DRX). During this state, the UE 1600 can power down for short intervals, thus saving power. If there is no data traffic activity during an extended period, the UE 1600 can transition to the RRC_Idle state, where the UE disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The UE 1600 enters a very low-power state, and the UE performs paging, where it periodically wakes up again to listen to the network, and then power down again. The UE 1600 may not receive data in this state; to receive data, the UE must transition back to the RRC_Connected state. An additional power-saving mode renders the device unusable for a period exceeding the paging interval (from seconds to hours). During this time, the device is completely unconnected to the network and may be completely powered off. Any data transmitted during this period will incur significant latency, which is assumed to be acceptable.

[0156] Battery 1628 can power UE 1600, but in some examples, UE 1600 may be installed and deployed in a fixed location and may have a power source coupled to the grid. Battery 1628 may be a lithium-ion battery, a metal-air battery (such as zinc-air batteries, aluminum-air batteries, lithium-air batteries, etc.). In some specific implementations, such as in vehicle-based applications, battery 1628 may be a typical lead-acid automotive battery.

[0157] Figure 17 An example of a gNB 1700 according to some implementation schemes is shown. The gNB node 1700 may be similar to the gNB 108 and is essentially interchangeable with it. The base station may have the same or similar components as the gNB 1700.

[0158] The gNB 1700 may include a processor 1704, an RF interface circuit 1708, a core network (CN) interface circuit 1712, and a memory / storage device circuit 1716.

[0159] The gNB 1700 components can be coupled to a variety of other components via one or more interconnects 1728.

[0160] The processor 1704, RF interface circuit 1708, memory / storage device circuit 1716 (including communication protocol stack 1710), antenna 1724, and interconnect 1728 can be similar to those relative to... Figure 15 Similar named elements are shown and described.

[0161] The CN interface circuit 1712 can provide connectivity to a core network (e.g., a 5GC using a 5G core network (5GC) compatible network interface protocol, such as Carrier Ethernet, or some other suitable protocol). Network connectivity can be provided to / from the gNB 1700 via fiber optic or wireless backhaul. The CN interface circuit 1712 may include one or more dedicated processors or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1712 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0162] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0163] For one or more embodiments, at least one component shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the Embodiments section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments described below. Similarly, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments described below in the Embodiments section.

[0164] Example

[0165] Further exemplary implementations are provided in the following sections.

[0166] Example 1 includes a method implemented by a user equipment (UE), the method comprising: receiving from a network configuration information associated with the transmission of a probe reference signal (SRSp) for positioning, the SRSp transmission using frequency hopping to achieve an effective positioning bandwidth for the SRSp transmission, wherein the UE is a RedCap UE with reduced transmission bandwidth capability (RedCap), wherein the effective positioning bandwidth is greater than the transmission bandwidth of the RedCap UE; determining a configuration associated with the frequency hopping for transmitting the SRSp, wherein the configuration is specific to a plurality of frequency hopping or a frequency hopping among the plurality of frequency hopping, and includes at least one of a window for the SRSp transmission or a conflict rule for resolving signal conflicts between the SRSp and non-SRSp signals; and performing at least one of the following based on the configuration: when the configuration includes the window, transmitting the SRSp during the window, wherein the RedCap UE abandons signal transmission or reception for a first duration before the start of the window and for a second duration after the end of the window; or when the configuration includes the conflict rule, transmitting the SRSp based on signal priority, wherein the signal priority is determined at or during the first duration before the start of the SRSp transmission.

[0167] Example 2 includes a method implemented by a user equipment (UE), the method comprising: receiving configuration information from a network, the configuration information including a set of SRS-SpatialRelationInfoPos parameters for a Sounding Reference Signal (SRS) resource for positioning, wherein the SRS-SpatialRelationInfoPos parameters indicate a spatial domain transmission filter for SRS transmission; determining, when the UE is in an RRC_INACTIVE state or an RRC_IDLE state, that the UE is incapable of measuring, with predefined accuracy, a number of “N” configured downlink reference signals in the SRS-SpatialRelationInfoPos parameters for the SRS resource for each cell identifier or each group of cell identifiers; and, based on the incapacity, either abandoning the transmission of the SRS resource or transmitting the SRS resource based on one or more spatial domain transmission filters not present in the configuration information.

[0168] Example 3 includes the methods described according to Examples 1 and 2.

[0169] Example 4 includes the method according to any of the preceding examples, wherein the configuration information indicates the configuration of the window, wherein the configuration indicates the window identifier, the periodicity in the time slot, the offset of the starting time slot, and the time length.

[0170] Example 5 includes the method according to Example 4, wherein the time length includes the number of time slots, the number of sub-time slots within a time slot, or the number of symbols within a time slot.

[0171] Example 6 includes the method according to Example 5, wherein the time length includes the number of symbols, wherein one or more of the symbols are used to transmit the SRSp, and wherein other symbols of the time slot are also used to transmit non-SRSp signals.

[0172] Example 7 includes the method according to Example 4, wherein the window is valid for multiple cells and configured relative to a reference cell among the multiple cells, wherein the reference cell is a primary cell or a secondary cell configured for positioning.

[0173] Example 8 includes the method according to Example 4, wherein the RedCap UE is configured to transmit the SRSp only during the window, or to transmit the SRPp during and outside the window.

[0174] Example 9 includes the method according to any of the preceding examples, wherein the first duration corresponds to a first number of symbols, wherein the second duration corresponds to a second number of symbols, and wherein at least one of the first number or the second number is based on the subcarrier spacing transmitted by the SRSp, differs between downlink symbols or channels and uplink symbols or channels, or is based on the UE capability of the RedCap UE.

[0175] Example 10 includes the method according to any of the preceding examples, wherein the conflict rule is applied to the SRSp transmission outside the window or to the SRSp transmission during the window.

[0176] Example 11 includes the method according to any of the preceding embodiments, wherein the collision rule is specific to the frequency hopping and indicates whether to transmit or discard the SRSp when the signal collision occurs in the frequency hopping.

[0177] Example 12 includes the method according to Example 11, wherein the SRSp is transmitted based on the signal priority by at least the following operations: determining that the SRSp has a higher signal priority than the non-SRSp signal to be transmitted using the frequency hopping at a plurality of symbols prior to the transmission of the SRSp, and abandoning the transmission of the non-SRSp signal, wherein the number of symbols corresponds to the first duration.

[0178] Example 13 includes the method according to any of the preceding embodiments, wherein the collision rule is specific to the plurality of frequency hopping and indicates whether to transmit or discard the SRSp when the signal collision occurs on any of the plurality of frequency hopping frequencies.

[0179] Example 14 includes the method according to Example 13, wherein the SRSp is transmitted based on the signal priority by at least the following operations: determining at a plurality of symbols prior to the transmission of the SRSp that the SRSp has a higher signal priority than the non-SRSp signal to be transmitted using any of the plurality of frequency hopping, and abandoning the transmission of the non-SRSp signal, wherein the number of symbols corresponds to the first duration.

[0180] Example 15 includes the method according to any of the preceding embodiments, wherein the configuration information indicates relative signal priorities for the conflict rules, wherein signaling of the same priority or different priority is indicated for downlink signals and uplink signals.

[0181] Example 16 includes the method according to any of the preceding examples, wherein the conflict rules apply predefined relative signal priorities instead of those included in the configuration information.

[0182] Example 17 includes the method according to any of the preceding embodiments, wherein the configuration information indicates a first time window as the number of symbols for the SRSp transmission and the signal priority.

[0183] Example 18 includes the method according to any of the preceding embodiments, the method further comprising: receiving a positioning reference signal (PRS) on a downlink channel; determining that the reception of the PRS uses less than a desired effective positioning bandwidth; and transmitting to the network an indication of using less than the desired effective positioning bandwidth.

[0184] Example 19 includes the method according to any of the foregoing embodiments, the method further comprising: receiving a positioning reference signal (PRS) on a downlink channel; and transmitting to the network one or more measurements for continuous reference signal transmissions and an indication of frequency hopping for combinations, wherein the one or more measurements are a single measurement corresponding to a maximum continuous reference signal transmission or multiple measurements corresponding to different continuous reference signal transmissions.

[0185] Example 20 includes the method according to any of the foregoing embodiments, the method further comprising: receiving a positioning reference signal (PRS) on a downlink channel; and transmitting the per-hop reference signal measurement to the network having a location index of the per-hop reference signal measurement.

[0186] Example 21 includes the method according to Example 20, wherein the per-hop per-hop reference signal measurement is transmitted when the reference signal measurement across the desired effective positioning bandwidth fails.

[0187] Example 22 includes the method according to any of the preceding embodiments, the method further comprising: receiving a positioning reference signal (PRS) on a downlink channel; and transmitting to the network reference signal measurements associated with the plurality of frequency hopping and an indication of at least the reference signal measurements or the plurality of frequency hopping.

[0188] Example 23 includes the method according to any of the preceding embodiments, the method further comprising: receiving a positioning reference signal (PRS) on a downlink channel; and transmitting to the network a plurality of reference signal measurements and an indication of a corresponding frequency hopping set for each of the plurality of reference signal measurements.

[0189] Example 24 includes the method according to any of the preceding embodiments, the method further comprising: receiving a positioning reference signal (PRS) on a downlink channel; and transmitting to the network a plurality of per-hop reference signal measurements and an indication of a corresponding frequency hop for each of the plurality of per-hop reference signal measurements.

[0190] Example 25 includes the method according to any of the foregoing embodiments, the method further comprising: receiving a positioning reference signal (PRS) on a downlink channel; and transmitting to the network a plurality of per-hop reference signal measurements and an indication of the correspondence between each frequency hop and each of the plurality of per-hop reference signal measurements.

[0191] Example 26 includes the method according to any of the preceding embodiments, the method further comprising: receiving a positioning reference signal (PRS) on a downlink channel; and transmitting a plurality of per-hop reference signal measurements to the network, wherein a default value for the per-hop reference signal measurements indicates that no reference signal measurement has been generated for the corresponding frequency hop.

[0192] Example 27 includes the method according to any of the preceding embodiments, the method further comprising: determining a Positioning Reference Signal (PRS) configuration for using the frequency hopping, wherein the use of frequency hopping is based on the UE being a RedCap UE or based on the PRS configuration and the effective positioning bandwidth; and receiving the PRS from the network on a downlink channel based on the PRS configuration.

[0193] Example 28 includes the method according to any of the preceding embodiments, wherein the PRS configuration is determined based on information elements including: a PRS configuration identifier, an indication of whether the frequency hopping should be used, and an indication of the effective positioning bandwidth.

[0194] Example 29 includes the method according to any of the preceding embodiments, wherein the PRS is requested based on information elements including: an indication of whether the frequency hopping should be used and an indication of the effective positioning bandwidth.

[0195] Example 30 includes the method according to any of the preceding embodiments, wherein the UE requests or the Location Management Function (LMF) requests the PRS based on PRS parameters including: an indication of the effective positioning bandwidth, frequency hopping overlap, the number of frequency hopping, an indication of whether to use intra-slot hopping, and an indication of whether to use inter-slot hopping.

[0196] Example 31 includes the method according to Example 30, wherein the SRS-SpatialRelationInfoPos parameter set is configured for the cell identifier or the set of cell identifiers.

[0197] Example 32 includes the method according to Example 30, wherein the SRS-SpatialRelationInfoPos parameter set is configured by region based on UE capabilities, wherein one SRS-SpatialRelationInfoPos parameter is configured for each cell identifier or each group of cell identifiers.

[0198] Example 33 includes the method according to Example 30, wherein the SRS-SpatialRelationInfoPos parameter set is configured by region based on UE capabilities, wherein more than one SRS-SpatialRelationInfoPos parameter is configured for each cell identifier or group of cell identifiers.

[0199] Example 34 includes the method according to Example 30, wherein the quantity "N" is based on the positioning method used and the UE capability of supporting the number of SRS-SpatialRelationInfoPos parameters for each cell identifier or each group of cell identifiers.

[0200] Example 35 includes the method according to Example 34, wherein if only one SRS-SpatialRelationInfoPos parameter is configured in the SRS-SpatialRelationInfoPos parameter set, then the quantity "N" is equal to one.

[0201] Example 36 includes the method according to Example 34, wherein if more than one SRS-SpatialRelationInfoPos parameter is configured in the SRS-SpatialRelationInfoPos parameter set and the positioning method used employs at least three anchor positioning, then the quantity "N" equals three.

[0202] Example 37 includes the method according to Example 34, wherein the quantity "N" is configured in the configuration information.

[0203] Example 38 includes a user equipment (UE) comprising: one or more processors; and one or more memories storing instructions that, when executed by the one or more processors, configure the UE to perform the method according to any of the preceding embodiments.

[0204] Example 39 includes one or more computer-readable media storing instructions that, when executed on a user equipment (UE), cause the UE to perform operations including those operations described according to any of the preceding embodiments.

[0205] Example 40 includes an apparatus comprising one or more elements for performing the methods described or associated with any of the foregoing embodiments.

[0206] Example 41 includes one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of the device, cause the device to perform one or more elements of the methods described or associated with any of the foregoing embodiments.

[0207] Example 42 includes an apparatus comprising logic, modules, or circuitry for performing one or more elements of the methods described or associated with any of the foregoing examples.

[0208] Example 43 includes an apparatus comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the methods described or associated with any of the foregoing embodiments.

[0209] Example 44 includes a system comprising components for performing one or more elements of the methods described or associated with any of the foregoing embodiments.

[0210] Unless otherwise expressly stated, any of the embodiments described above may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from the practice of various embodiments.

[0211] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

Claims

1. A method, the method comprising: The system processes configuration information associated with the transmission of a Detection Reference Signal (SRSp) for positioning, the SRSp transmission using frequency hopping to achieve an effective positioning bandwidth for the SRSp transmission, wherein the configuration information is received from the network, and wherein the effective positioning bandwidth is greater than the transmission bandwidth of a RedCap UE. Determine a configuration associated with the frequency hopping for transmitting SRSp, wherein the configuration is specific to a plurality of frequency hopping or a frequency hopping among the plurality of frequency hopping, and includes at least one of a window for transmitting the SRSp or a conflict rule for resolving signal conflicts between the SRSp and non-SRSp signals; and Based on the configuration, at least one of the following may occur: When the configuration includes the window, the SRSp is transmitted during the window, wherein signal transmission or reception is abandoned during a first duration before the window begins and during a second duration after the window ends; or When the configuration includes the conflict rule, the SRSp is transmitted based on signal priority, wherein the signal priority is determined at or within the first duration prior to the start of the SRSp transmission.

2. The method according to claim 1, further comprising: Processing Positioning Reference Signals (PRS) received on the downlink channel; It was determined that the PRS was received using less effective positioning bandwidth than expected; as well as This causes an instruction to be sent to the network to use less than the desired effective positioning bandwidth.

3. The method according to claim 1, further comprising: Processing Positioning Reference Signals (PRS) received on the downlink channel; as well as This enables the network to send one or more measurements for continuous reference signal transmissions and an indication of frequency hopping for the combination, wherein the one or more measurements are a single measurement corresponding to the maximum continuous reference signal transmission or multiple measurements corresponding to different continuous reference signal transmissions.

4. The method according to claim 1, further comprising: Processing Positioning Reference Signals (PRS) received on the downlink channel; as well as This enables the network to send the per-hop reference signal measurement, which has a position index for the per-hop reference signal measurement.

5. The method according to claim 1, further comprising: Processing Positioning Reference Signals (PRS) received on the downlink channel; as well as This enables the transmission to the network of reference signal measurements associated with the plurality of frequency hopping, as well as an indication of whether it is at least the reference signal measurement or the plurality of frequency hopping.

6. The method according to claim 1, further comprising: Processing Positioning Reference Signals (PRS) received on the downlink channel; as well as This enables the transmission of multiple reference signal measurements to the network, as well as an indication of the corresponding frequency hopping set for each of the multiple reference signal measurements.

7. The method according to claim 1, further comprising: Processing Positioning Reference Signals (PRS) received on the downlink channel; as well as This enables the transmission of multiple per-hop reference signal measurements to the network, along with an indication of the corresponding frequency hopping for each of the multiple per-hop reference signal measurements.

8. The method according to claim 1, further comprising: Processing Positioning Reference Signals (PRS) received on the downlink channel; as well as This enables the transmission of multiple per-hop reference signal measurements to the network, as well as an indication of the correspondence between each frequency hop and each of the multiple per-hop reference signal measurements.

9. The method according to claim 1, further comprising: Processing Positioning Reference Signals (PRS) received on the downlink channel; as well as This enables the transmission of multiple per-hop reference signal measurements to the network, wherein the default value of the per-hop reference signal measurement indicates that no reference signal measurement is generated for the corresponding frequency hop.

10. The method according to claim 1, further comprising: Processing a Positioning Reference Signal (PRS) configuration using the frequency hopping, wherein the frequency hopping is used based on the RedCapUE or based on the PRS configuration and the effective positioning bandwidth; and The PRS received from the network on the downlink channel is processed based on the PRS configuration.

11. An apparatus comprising: Processing circuit, the processing circuit being configured to: The system processes configuration information associated with the transmission of a Detection Reference Signal (SRSp) for positioning, the SRSp transmission using frequency hopping to achieve an effective positioning bandwidth for the SRSp transmission, wherein the configuration information is received from the network, and wherein the effective positioning bandwidth is greater than the transmission bandwidth of a RedCap UE. Determine a configuration associated with the frequency hopping for transmitting SRSp, wherein the configuration is specific to a plurality of frequency hopping or a frequency hopping among the plurality of frequency hopping, and includes at least one of a window for transmitting the SRSp or a conflict rule for resolving signal conflicts between the SRSp and non-SRSp signals; and Based on the configuration, at least one of the following may occur: When the configuration includes the window, the SRSp is transmitted during the window, wherein signal transmission or reception is abandoned during a first duration before the window begins and during a second duration after the window ends; or When the configuration includes the conflict rule, the SRSp is transmitted based on signal priority, wherein the signal priority is determined at or within the first duration prior to the start of the SRSp transmission.

12. The apparatus of claim 11, wherein the configuration information indicates the configuration of the window, wherein the configuration indicates the window identifier, the periodicity in the time slot, the offset of the starting time slot, and the time length.

13. The apparatus of claim 11, wherein the first duration corresponds to a first number of symbols, wherein the second duration corresponds to a second number of symbols, and wherein at least one of the first number or the second number is based on the subcarrier spacing transmitted by the SRSp, differs between downlink symbols or channels and uplink symbols or channels, or is based on UE capabilities.

14. The apparatus of claim 11, wherein the conflict rule is applied to the SRSp transmission outside the window or to the SRSp transmission during the window.

15. The apparatus of claim 11, wherein the collision rule is specific to the frequency hopping and indicates whether to transmit or discard the SRSp when the signal collision occurs in the frequency hopping or any of the plurality of frequency hopping frequencies.

16. A method, the method comprising: The configuration information is received from the network and includes a set of SRS-SpatialRelationInfoPos parameters for probe reference signal (SRS) resources used for positioning, wherein the SRS-SpatialRelationInfoPos parameters indicate the spatial domain transmission filter used for SRS transmission. When operating in RRC_INACTIVE or RRC_IDLE state, it is determined that there is no ability to measure the number of "N" configured downlink reference signals in the SRS-SpatialRelationInfoPos parameter for the SRS resource for each cell identifier or each group of cell identifiers with predefined accuracy. as well as Based on the aforementioned inability, the transmission of the SRS resource is abandoned, or the transmission of the SRS resource is initiated based on one or more spatial domain transmission filters that do not exist in the configuration information.

17. The method of claim 16, wherein the SRS-SpatialRelationInfoPos parameter set is configured for the cell identifier or the set of cell identifiers.

18. The method of claim 16, wherein the SRS-SpatialRelationInfoPos parameter set is configured by region based on capability information, wherein one SRS-SpatialRelationInfoPos parameter is configured for each cell identifier or each group of cell identifiers.

19. The method of claim 16, wherein the SRS-SpatialRelationInfoPos parameter set is configured by region based on capability information, wherein more than one SRS-SpatialRelationInfoPos parameter is configured for each cell identifier or group of cell identifiers.

20. The method of claim 16, wherein the quantity "N" is based on the positioning method used and the ability to support the number of SRS-SpatialRelationInfoPos parameters for each cell identifier or each group of cell identifiers.

Images