EP4666512A1

EP4666512A1 - Ul srs frequency hopping indication and procedure enhancements for positioning

Info

Publication number: EP4666512A1
Application number: EP24707294.5A
Authority: EP
Inventors: Zhilan XIONG; Florent Munier; Chunhui Zhang; Ritesh SHREEVASTAV
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2023-02-17
Filing date: 2024-02-19
Publication date: 2025-12-24
Also published as: CN120937290A; WO2024171167A1

Abstract

A method, system and apparatus are disclosed. In at least one embodiment, a network node is configured to communicate with a wireless device. The network node is configured to, and/or includes a radio interface, and/or includes processing circuitry configured to: configure the wireless device for a sounding reference signal, SRS, frequency hopping scheme. The scheme includes a configuration for at least one of partial intra-slot SRS frequency hopping, partial inter-slot SRS frequency hopping, and inter-slot SRS frequency hopping within continuous slots. The network node is configured to communicate with the wireless device according to the configured SRS frequency hopping scheme.

Description

UL SRS FREQUENCY HOPPING INDICATION AND PROCEDURE ENHANCEMENTS FOR POSITIONING

RELATED APPLICATIONS

[0001] This application claims the benefit of provisional patent application serial number 63/446744, filed February 17, 2023, the disclosure of which is hereby incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] The present disclosure relates to wireless communications, and in particular, to sounding reference signal (SRS) frequency hopping.

BACKGROUND

[0003] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0004] 3GPP is discussing NR positioning Release (Rel) 18 with the potential enhancements for RedCap positioning in which the maximum bandwidth of RedCap wireless device is 20MHz in frequency range 1 (FR1) and 100MHz in frequency range 2 (FR2). One of potential approaches is introducing sounding reference signal (SRS) frequency hopping for the positioning accuracy improvement of uplink-related RedCap positioning.

[0005] Existing approaches in NR

[0006] In existing SRS configurations, one wireless device can be configured with repetition factor RG{ 1,2,4} or RG{ 1, 2, 3, 4, 5, 6, 7, 8, 10, 12, 14} by network where R<Ns, and Ns is the number of adjacent symbols in one slot for SRS transmission.

[0007] If SRS frequency hopping is not configured, each of the antenna ports of the SRS resource in each slot is mapped in all the Ns symbols to the same set of subcarriers in the same set of physical resource blocks (PRBs).

[0008] FIG. 1A illustrates intra-slot SRS frequency hopping where m_{SRS 3} = 4 and /V₃ = 2 and FIG. IB illustrates intra-slot SRS frequency hopping where m_{SRS 3} = 8 and N₂ = 2 [0009] If frequency hopping within an SRS resource in each slot is configured without repetition (i.e. R=l), according to the SRS hopping parameters B_SRS, C_SRS, b_hop, each of the antenna ports of the SRS resource in each slot is mapped to different sets of subcarriers in each orthogonal frequency division multiplexing (OFDM) symbol, where the same transmission comb value is assumed for different sets of subcarriers. In this case, for example, if B_SRS = 3, C_SRS = 9, b_hop = 1, and N_s = 4, then m_{SRS 3} = 4 and /V₃ = 2, the SRS frequency hopping is within one time slot and one hop has 4 RBs as shown in FIG. 1A; if ^BSRS = 2, ^CSRS = 9, ^bho_P = 1, and N_s = 4, then m_{SRS 3} = 8 and N₃ = 2, the SRS frequency hopping is within one time slot and one hop has 8 RBs as shown in FIG. lb.

[0010] If both frequency hopping and repetition within an SRS resource in each slot are configured (Ns > 4, R > 2), each of the antenna ports of the SRS resource in each slot is mapped to the same set of subcarriers within each set of R adjacent OFDM symbols, and frequency hopping across the sets is according to the SRS hopping parameters B_SRS, C_SRS, and b_hop, where N_s should be divisible by R. For example, if B _R — 3, C _R — 9, bh_Op — 1, N_s = 4 and R = 2, then m_{SRS 3} = 4 and N₃ = 2, the SRS frequency hopping is within multiple time slots and one hop has 4 RBs and 2 symbols as shown in FIG. 2, which illustrates inter-slot SRS frequency hopping

[0011] A wireless device may be configured with N_s = 2,4,8,10,12 or 14 adjacent symbol aperiodic SRS resource with intra-slot frequency hopping within a bandwidth part, where the full hopping bandwidth is sounded with an equal-size subband across N_s symbols when frequency hopping is configured with R=l. A wireless device may be configured N_s > 4 adjacent symbols aperiodic SRS resource with intra-slot frequency hopping within a bandwidth part, where the full hopping bandwidth is sounded with an equal-size subband across — R sets of R adjacent OFDM symbols, when frequency hopping is configured with R >

2, N_s > R and Ns may be divisible by R. Each of the antenna ports of the SRS resource is mapped to the same set of subcarriers within each set of R adjacent OFDM symbols of the resource.

[0012] A wireless device may be configured N_s = 1 symbol periodic or semi-persistent SRS resource with inter-slot hopping within a bandwidth part, where the SRS resource occupies the same symbol location in each slot. A wireless device may be configured N_s = 2,4,8,10,12 or 14 symbol periodic or semi-persistent SRS resource with intra-slot and interslot hopping within a bandwidth part, where the N-symbol SRS resource occupies the same symbol location(s) in each slot. For N_s > 4, when frequency hopping is configured with R >

2, intra-slot and inter-slot hopping is supported with each of the antenna ports of the SRS resource mapped to different sets of subcarriers across — R sets of R adjacent OFDM symbol(s) of the resource in each slot, where N_s may be divisible by R. Each of the antenna ports of the SRS resource is mapped to the same set of subcarriers within each set of R adjacent OFDM symbols of the resource in each slot. For N_s= R, when frequency hopping is configured, interslot frequency hopping is supported with each of the antenna ports of the SRS resource mapped to the same set of subcarriers in R adjacent OFDM symbol(s) of the resource in each slot.

[0013] For bandwidth part, one wireless device can be configured with up to 4 bandwidth parts in uplink (UL) and up to 4 bandwidth parts in downlink (DL).

SUMMARY

[0014] Some embodiments advantageously provide methods, systems, and apparatuses for SRS frequency hopping.

[0015] Problem(s) of the existing approaches in NR

[0016] For intra-slot SRS frequency hopping, existing solutions do not support partial SRS frequency hopping.

[0017] For inter-slot SRS frequency hopping, the existing solutions do not support partial SRS frequency hopping and SRS frequency hopping within continuous slots and across full wider bandwidth in one period.

[0018] Disclosed herein are embodiments relating to SRS frequency hopping configuration and indication as well as repetition indication, e.g., as shown in FIGS. 12 - 14, discussed below.

• Example 1: Virtual wider bandwidth

• Example 2: Multiple bandwidth parts

• Example 3: Multiple RF carrier frequencies

[0019] At least one embodiment supports re-synchronization during SRS frequency hopping.

[0020] At least one embodiment relates to signaling exchange among wireless device, network node and LMF to realize the UL SRS FH.

[0021] At least one embodiment can be used to support SRS frequency hopping configuration and indication as well as repetition indication. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0023] FIG. 1A illustrates an example of intra-slot SRS frequency hopping;

[0024] FIG. IB illustrates another example of intra-slot SRS frequency hopping;

[0025] FIG. 2 illustrates another example of intra-slot SRS frequency hopping;

[0026] FIG. 3 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

[0027] FIG. 4 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;

[0028] FIG. 5 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure;

[0029] FIG. 6 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;

[0030] FIG. 7 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;

[0031] FIG. 8 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure;

[0032] FIG. 9 is a flowchart of an example process in a network node for according to some embodiments of the present disclosure; [0033] FIG. 10 is a flowchart of an example process in a wireless device according to some embodiments of the present disclosure;

[0034] FIG. 11A illustrates an example of intra-slot SRS frequency hopping according to some embodiments of the present disclosure;

[0035] FIG. 11B, illustrates an example of intra-slot SRS frequency hopping according to some embodiments of the present disclosure;

[0036] FIG. 12 illustrates an example of intra-slot SRS frequency hopping resource allocation according to some embodiments of the present disclosure;

[0037] FIG. 13 illustrates an example of intra-slot plus inter-slot SRS frequency hopping resource allocation according to some embodiments of the present disclosure;

[0038] FIG. 14 illustrates an example of intra-slot plus inter-slot SRS frequency hopping resource allocation according to some embodiments of the present disclosure;

[0039] FIG. 15 illustrates an example of one bandwidth part per hop according to some embodiments of the present disclosure;

[0040] FIG. 16 is an example of a FrequencylnfoUL information element according to some embodiments of the present disclosure; and

[0041] FIG. 17 is an example signaling procedure according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

[0042] Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to SRS frequency hopping. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0043] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

[0044] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0045] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.

[0046] The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

[0047] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc. [0048] Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0049] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0050] In some embodiments, the general description elements in the form of “one of A and B” corresponds to A or B. In some embodiments, at least one of A and B corresponds to A, B or AB, or to one or more of A and B, or one or both of A and B . In some embodiments, at least one of A, B and C corresponds to one or more of A, B and C, and/or A, B, C or a combination thereof.

[0051] Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

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

[0053] Some embodiments provide for SRS frequency hopping.

[0054] Referring again to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 3 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.

[0055] Also, it is contemplated that a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.

[0056] The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

[0057] The communication system of FIG. 3 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.

[0058] A network node 16 is configured to include a configuration unit 32 which is configured to perform one or more network node 16 functions described herein, including functions related to SRS frequency hopping. A wireless device 22 is configured to include an implementation unit 34 which is configured to perform one or more wireless device 22 functions described herein, including functions related to SRS frequency hopping.

[0059] Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 4. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

[0060] Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24.

[0061] The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22. The processing circuitry 42 of the host computer 24 may include a control unit 54 configured to enable the service provider to observe/monitor/ control/transmit to/receive from the network node 16 and or the wireless device 22.

[0062] The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10. [0063] In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

[0064] Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include configuration unit 32 configured to perform one or more network node 16 functions described herein, including functions related to SRS frequency hopping.

[0065] The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.

[0066] The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).

[0067] Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

[0068] The processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 84 of the wireless device 22 may include an implementation unit 34 configured to perform one or more wireless device 22 functions described herein, including functions related to SRS frequency hopping.

[0069] In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 4 and independently, the surrounding network topology may be that of FIG. 3. [0070] In FIG. 4, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[0071] The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

[0072] In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.

[0073] Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the WD 22, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the WD 22.

[0074] In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the network node 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the network node 16.

[0075] Although FIGS. 3 and 4 show various “units” such as configuration unit 32, and implementation unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0076] FIG. 5 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIGS. 3 and 4, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 4. In a first step of the method, the host computer 24 provides user data (Block S100). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block S102). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block s 108).

[0077] FIG. 6 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 3 and 4. In a first step of the method, the host computer 24 provides user data (Block SI 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block SI 14).

[0078] FIG. 7 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 3 and 4. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block SI 16). In an optional substep of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block s 126).

[0079] FIG. 8 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 3, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 3 and 4. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (Block S128). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block SI 30). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block SI 32).

[0080] FIG. 9 is a flowchart of an example process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the configuration unit 32), processor 70, radio interface 62 and/or communication interface 60. Network node 16 is configured to configure the wireless device for a sounding reference signal, SRS, frequency hopping scheme, the scheme including a configuration for at least one of partial intra-slot SRS frequency hopping, partial inter-slot SRS frequency hopping, and inter-slot SRS frequency hopping within continuous slots (Block S134). Network node 16 is configured to communicate with the wireless device according to the configured SRS frequency hopping scheme (Block SI 36).

[0081] In at least one embodiment, the configured SRS frequency hopping scheme includes a configuration for one radio frequency (RF) carrier for each of a plurality of SRS frequency hops.

[0082] In at least one embodiment, the configured SRS frequency hopping scheme includes a hopping pattern, the hopping pattern being based on a band configuration, the band configuration being at least one of frequency division duplex (FDD), time division duplex (TDD and half duplex FDD (HD-FDD).

[0083] FIG. 10 is a flowchart of an example process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of wireless device 22 such as by one or more of processing circuitry 84 (including the implementation unit 34), processor 86, radio interface 82 and/or communication interface 60. Wireless device 22 is configured to receive a sounding reference signal, SRS, frequency hopping scheme, the scheme including a configuration for at least one of partial intra-slot SRS frequency hopping, partial inter-slot SRS frequency hopping, and inter-slot SRS frequency hopping within continuous slots (Block S 138). Wireless device 22 is configured to communicate with the network node according to the configured SRS frequency hopping scheme (Block S140).

[0084] In at least one embodiment, the configured SRS frequency hopping scheme includes a configuration for one radio frequency (RF) carrier for each of a plurality of SRS frequency hops.

[0085] In at least one embodiment, the configured SRS frequency hopping scheme includes a hopping pattern, the hopping pattern being based on a band configuration, the band configuration being at least one of frequency division duplex (FDD), time division duplex (TDD and half duplex FDD (HD-FDD).

[0086] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for SRS frequency hopping. One or more wireless device 22 functions described below may be performed by one or more of processing circuitry 84, processor 86, implementation unit 34, etc. One or more network node 16 functions described below may be performed by one or more of processing circuitry 68, processor 70, configuration unit 32, etc. [0087] The time-frequency resource configuration for SRS frequency hopping may be, by way of non-limiting examples, the configuration from network node 16 to wireless device 22, may be the indication from network node 16 to location server, may be the indication from location server to network node 16, and may be the configuration from location server to wireless device 22.

[0088] One virtual bandwidth (or one virtual bandwidth part)

[0089] Intra-Slot SRS frequency hopping

[0090] The information related to the time-frequency resources used for SRS frequency hopping in some embodiments is associated with a virtual bandwidth. The start index of the resource block (RB) in this virtual bandwidth is same as the start index of one given bandwidth part (e.g., initial bandwidth part, active bandwidth part, current bandwidth part, indicated bandwidth part for this SRS configuration). For example, in FIGS. 11A and 11B, which illustrate examples of intra-slot SRS frequency hopping resource allocation, the virtual bandwidth is 273 RBs.

[0091] The information related to the time-frequency resources used for SRS frequency hopping may be associated with a list of number of RBs, or the information related to this list of number of RBs. Each number of RBs in this list indicates the number of RBs of partial overlapped frequency in two adjacent hops, the first number indicates the number of RBs of partial overlapped frequency of hop 0 and hop 1 , the second number indicates the number of RBs of partial overlapped frequency of hop 1 and hop 2, and so on. For example, in FIG. 11 A, this list is (7, 7, 7, 6, 6).

[0092] The information related to the time-frequency resources used for SRS frequency hopping may be associated with one overlap factor. This overlap factor indicates the number of RBs of partial overlapped frequency in two adjacent hops as shown in FIG. 1 IB. Additionally, if a partial subcarrier location of one hop is not within the given wide band, then only the resources of this hop in the wide band may be transmitted as shown in solution 1 in FIG. 11B. In at least one embodiment, if a partial subcarrier location of one hop is not within the given wide band, then the frequency location of this hop is moved to adapt for the wide band as shown in solution 2 in FIG. 1 IB.

[0093] The information related to the time-frequency resources used for SRS frequency hopping may be associated with the bandwidth of one hop. Each hop in one whole SRS frequency hopping has common bandwidth. For example, in FIGS. 11 A and 1 IB, the bandwidth of one hop is 51 RBs.

[0094] The information related to the time-frequency resources used for SRS frequency hopping may be associated with the time gap between two adjacent hops. There is a common time gap between any two adjacent hops within same time slot. For example, in FIGS. 11A and 1 IB, the time gap between two adjacent hops is 1 OFDM symbol.

[0095] The information related to the time-frequency resources used for SRS frequency hopping may be associated with the number of OFDM symbols of each hop (i.e., repetition number#l). Each hop in one whole SRS frequency hopping has common number of OFDM symbols. For example, FIGS. 11A and 1 IB, the number of OFDM symbols of one hop is 1. [0096] The information related to the time-frequency resources used for SRS frequency hopping may be associated with one start offset, which is equal to the total number of symbols in one time slot minus the index of the start symbol of the first hop in the same time slot. For example, in the FIGS. 11A and 1 IB, the value of the start offset is 14-3 = 11. In another embodiment, the start offset is equal to the index of the start symbol of the first hop in one time slot.

[0097] The information related to the time-frequency resources used for SRS frequency hopping may be associated with the number of hops in one whole SRS frequency hopping. For example, in FIGS. 11 A and 1 IB, the number of hops is 6.

[0098] The information related to the time-frequency resources used for SRS frequency hopping may be associated with (e.g., may be defined by or determined from) the number of the symbols which is equal to the total number of symbols used for SRS transmission plus the total number of symbols used for the time gaps above in a whole SRS frequency hopping. For example, in FIGS. 11A and 1 IB, the number of the symbols of one whole SRS frequency hopping is 11.

[0099] The information related to the time-frequency resources used for SRS frequency hopping may be associated with the periodicity which is the difference of the start times of two adjacent whole SRS frequency hopping.

[0100] The information related to the time-frequency resources used for SRS frequency hopping may be associated with repetition number#2 which indicates the number of continuous whole SRS frequency hopping in one period. For example, in FIG. 12, which illustrates an example of intra-slot SRS frequency hopping resource allocation, repetition number#2 is equal to 2. In at least one embodiment, the start offset in each whole SRS frequency hopping is same, as shown in FIG. 12.

[0101] In at least one embodiment, supporting partially overlapped SRS frequency hopping configuration is accomplished via one virtual wide bandwidth, one overlap offset, one time gap besides the existing parameter configuration, in which the virtual wide bandwidth indicates the target wide bandwidth for SRS frequency hopping, the overlap offset indicates the number of overlapped RBs of two adjacent hops, and the time gap indicates the number of symbols between two adjacent hops for RF retuning. This solution uses fewer bits to indicate the SRS frequency hopping pattern, but the bandwidth of last hop may be smaller than the bandwidths of other hops or the overlap offset of the last hop may be changed if hoping to keep same bandwidth. At least one embodiment uses one virtual wide bandwidth, one list of overlap offsets and one time gap as well as the existing parameter configuration, where the value in the list of overlap offsets indicates the overlap offset of the hop. The newly introduced parameters could be common parameters shared by all (positioning) SRS resources in one (positioning) SRS resource set.

[0102] Intra-Slot plus Inter-Slot SRS frequency hopping

[0103] In at least one embodiment, if the number of OFDM symbols of each hop (i.e. repetition number) is set to more than 1 , then the SRS frequency hopping pattern become (may become) intra-slot plus inter-slot SRS frequency hopping depending on the detailed parameters. For example, in FIG. 13, which illustrates an example of intra-slot plus inter-slot SRS frequency hopping resource allocation, the repetition number#3 is set to 3 and one whole SRS frequency hopping cover two time slots. [0104] In at least one embodiment, the definition of the start offset in each related time slot is same as that shown in FIG. 13. In another embodiment, the definition of the start offset of the first time slot is same as other embodiments described herein, while the resource allocation of SRS in the following time slot(s) in the same SRS frequency hopping follows other parameter configuration as shown in FIG. 14, which illustrates an example of intra-slot plus inter-slot SRS frequency hopping resource allocation.

[0105] Inter-Slot SRS frequency hopping

[0106] In at least one embodiment, the information related to the time-frequency resources used for SRS frequency hopping may be associated with the number of the time slots for one hop, and each hop has same value of the start offset, which is also provided in this information.

[0107] In at least one embodiment, the information related to the time-frequency resources used for SRS frequency hopping may be associated with the number of continuous whole SRS frequency hopping in one period.

[0108] One bandwidth part per hop

[0109] The SRS frequency hopping information in some embodiments relating to one bandwidth part per hop is associated with more bandwidth parts, and each bandwidth part is associated with one start RB index of one hop.

[0110] The SRS frequency hopping information may be associated with the time gap as described herein.

[0111] The SRS frequency hopping information may be associated with the start offset as described herein.

[0112] The SRS frequency hopping information may be associated with the number of OFDM symbols for SRS transmission in one bandwidth part, and each bandwidth part has same number of OFDM symbols for SRS transmission. In at least one embodiment, one bandwidth part is associated with one number of OFDM symbols for SRS transmission, which means that the number may be different in each bandwidth part.

[0113] The SRS frequency hopping information may be associated with the number of continuous whole SRS frequency hopping in one period, as described herein, for intra-slot SRS frequency hopping, inter-slot SRS frequency hopping, and/or intra-slot plus inter-slot SRS frequency hopping.

[0114] FIG. 15 illustrates an example of one bandwidth part per hop.

[0115] One RF carrier frequency for each hop [0116] The SRS frequency hopping information in some embodiments using one radio frequency (RF) carrier frequency for each hop is associated with more RF carrier frequencies, and each RF carrier frequency indicates the start RB of one hop. At least one embodiment does not require the change of other bandwidth part (BWP) parameters.

[0117] In existing approaches, the carrier frequency for the active BWP is configured in ServingCellConfigCommon, in SIB1, as follows:

— ServingCellConfig

— UplinkConfig

— BWP-Uplink

— BWP-UplinkDedicated

— SRS-config

[0118] In at least one embodiment, FrequencylnfoUL configures the carrier for UL, the configuration of a list of absolute radio frequency channel number (ARFCN) frequencies (i.e., carrier values) enables the configuration of RF carrier hopping, and other parameters in FrequencylnfoUL may not need to be changed. The first value of the list corresponds the first hop, and the second value of the list corresponds the second hop, and so on.

[0119] FIG. 16 is an example of a FrequencylnfoUL information element according to some embodiments of the present disclosure.

— RF Frequency hopping could be supported in at least three ways:

— Option 1: At least one embodiment includes configuring multiple resources, and hopping across resources. Each resource is then associated with a “RF frequency shift,” which the original UL carrier.

— However, some such embodiments may not provide for a way to link SRS resources to keep them consistent in the current SRS configuration.

— Option 2: At least one embodiment includes configuring multiple repetitions, with each repetition instance associated with the RF frequency shift

— However, in some such embodiments, repetition may not be supported by SRS pos,

— Option 3: At least one embodiment includes specifying additional staggering patterns, which may be achieved in, e.g., the following ways:

— configure the SRS with partial staggering (high comb value with repeated com offsets or — configure the SRS with low comb value (for example comb 1) and gap symbols according to wireless device 22 capability.

— However, some such embodiments may pose challenges to hop within a slot except with 1 -symbol per hops. However, that may be sufficient, considering uses case where InF has good coverage.

— Note, in some instances, embodiments relating to Option 2 may be preferred.

— Additionally, it may be preferable to have the entire hopping sequence in one slot, to avoid consuming UL resources.

[0120] Frequency hopping pattern including the wireless device 22 re-sync time [0121] In at least one embodiment, the frequency hopping pattern may be configured differently for a frequency division duplex (FDD) band and a time division duplex (TDD) band or a RedCap wireless device 22 operating half duplex FDD (HD-FDD) mode in a FDD band.

[0122] For FDD band and RedCap wireless device 22 operating in full-duplex mode, wireless device 22 can monitor the DL synchronization signals at the same time wireless device 22 transmits the different frequency hop in UL, and both PLLs are synchronized to the DL synchronization signals, e.g., SSB signals. Thus, the Redcap wireless device 22 can be equipped with two phase-locked loops (PLL), one for mixer input for downlink receiving and one for mixer input for uplink transmission. In this way, the frequency hopping pattern for a RedCap wireless device 22 could be configured without additional time gap for Redcap wireless device 22 keeping track of the DL synchronization signals.

[0123] For TDD band, in at least one embodiment, Redcap wireless device 22 may be equipped only one PLL, which is shared by both DL and UL. When wireless device 22 is configured to be transmitted in multiple time slots across DL time slots according to one TDD pattern, RedCap wireless device 22 may need to track the DL synchronization signals so the PLL will be in lock to network node 16 timing, and wireless device 22 can successfully tune its UL PLL to different frequency for a frequency hop. However, wireless device 22 needs to be tuned to the frequency where SSB signal is transmitted and wireless device 22 needs time gap between frequency hops for this purpose. To reduce the hop duration, BS could also configure a CSLRS to this wireless device 22 with the same RB range configured for UL SRS transmission for a frequency hop.

[0124] In at least one embodiment, a RedCap wireless device 22 with HD-FDD operation in a FDD band, includes the same solution described above with TDD band. For example, if the hop duration is across several slots and a Redcap wireless device 22 operating in HD- FDD mode needs to keep track of the DL timing, it is allowed to do so by allocating a time gap between two frequency hops. Such time gap configuration may depend on the duration of the hops, how many SSB occasions wireless device 22 needs to resync, and the time relating to retune to the SSB frequency and back to another frequency hop occasion. In at least one embodiment, a channel state information reference signal (CSI-RS) can be transmitted within the same RB range for some frequency hop where the RedCap wireless device 22 needs to resync. This then reduces the hoping duration at the expense of more network (e.g., as part of a network node 16) resources.

[0125] Signaling and Procedure

[0126] FIG. 17 is an example signaling procedure according to some embodiments of the present disclosure.

[0127] Example methods implemented in a network node 16 and/or wireless device 22 according to some embodiments of the present disclosure (note that the frequency hopping (FH) here can be replaced by partial SRS FH): One or more blocks described herein may be performed by one or more elements of network node 16 and/or wireless device 22 such as by one or more of processing circuitry 68 (including the configuration unit 32 and/or implementation unit 34.

[0128] In at least one embodiment, the network node 16(s) provides a list of supported FH configurations that network node 16 can perform measurements on (Block S200). This may include measurements on UL-SRS FH configuration that network node 16 can perform: o Measurement when SRS is configured with Frequency Hopping with Intra-Slot Measurement; o Measurement when SRS is configured with Frequency Hopping with Inter-Slot Measurement; o Measurement when SRS is configured with Frequency Hopping on slot level Repetition; o Measurement when SRS is configured with Frequency Hopping after certain periodicity; o Measurement when SRS is configured with Frequency Hopping on multiple BWP; o Measurement when SRS is configured with Frequency Hopping on wider virtual bandwidth part; o Measurement when SRS is configured with Frequency Hopping on multiple RF carrier Frequency; and o Measurement when SRS is configured with Frequency Hopping on certain band such as FDD band, TDD band.

[0129] In at least one embodiment, a wireless device 22 provides the FH capabilities for the support of UL-SRS FH pattern. The wireless device 22 can support to network node 16 via radio resource control (RRC) (Block S202) and optionally to location management function (LMF) via LTE positioning protocol (LPP) (Block S204). Alternatively, wireless device 22 may include a full detailed granular capability report to network node 16, but just a subset to LMF indicating that wireless device 22 is capable of FH but not indicating which one. The capabilities include, e.g.: o UL-SRS Transmission with FH with Intra-Slot; o UL-SRS Transmission with FH with Inter-Slot; o UL-SRS Transmission with FH on slot level Repetition; o UL-SRS Transmission with FH after certain periodicity; o UL-SRS Transmission with FH on multiple BWPs; o UL-SRS Transmission with FH on wider virtual bandwidth part; o UL-SRS Transmission with FH on multiple RF carrier Frequency; and o UL-SRS Transmission with FH on certain band (TDD, FDD, HD-FDD).

[0130] In at least one embodiment, LMF provides a recommendation to network node 16 to configure UL-SRS with FH (Block S206) and the recommendation of certain characteristics can be based upon: o Wireless device’s 22 current positioning accuracy (LMF may decide to vary FH pattern if currently configured FH pattern does not yield good accuracy. o Historical information, such as FH pattern applied by another wireless device 22 in the same area/vicinity or cell/beam, and if that provided better result, the LMF may recommend such to network node 16.

[0131] Network node 16 makes the final decision (Block S208) and determines UL-SRS with FH based upon: o recommendation from LMF, o capability of wireless device 22, and/or o Channel condition (if fast fading exist or slow fading exist).

[0132] If several fast fading occurs in certain frequency region, network node 16 decides to perform intra-slot (within same slot) FH; else for the case of slow fading; inter-slot or after certain periodicity is configured. [0133] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0134] Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0135] These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

[0136] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0137] It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0138] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0139] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0140] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings. The following enumerated embodiments are included within the scope of the disclosure. [0141] Embodiment Al. A network node configured to communicate with a wireless device (WD), the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to: configure the wireless device for a sounding reference signal, SRS, frequency hopping scheme, the scheme including a configuration for at least one of partial intra-slot SRS frequency hopping, partial inter-slot SRS frequency hopping, and inter-slot SRS frequency hopping within continuous slots; and communicate with the wireless device according to the configured SRS frequency hopping scheme.

[0142] Embodiment A2. The network node of Embodiment Al, wherein the configured SRS frequency hopping scheme includes a configuration for one radio frequency (RF) carrier for each of a plurality of SRS frequency hops.

[0143] Embodiment A3. The network node of Embodiment Al, wherein the configured SRS frequency hopping scheme includes a hopping pattern, the hopping pattern being based on a band configuration, the band configuration being at least one of frequency division duplex (FDD), time division duplex (TDD and half duplex FDD (HD-FDD).

[0144] Embodiment Bl. A method implemented in a network node, the method comprising: configuring a wireless device for a sounding reference signal, SRS, frequency hopping scheme, the scheme including a configuration for at least one of partial intra-slot SRS frequency hopping, partial inter-slot SRS frequency hopping, and inter-slot SRS frequency hopping within continuous slots; and communicating with the wireless device according to the configured SRS frequency hopping scheme.

[0145] Embodiment B2. The method of Embodiment B 1 , wherein the configured SRS frequency hopping scheme includes a configuration for one radio frequency (RF) carrier for each of a plurality of SRS frequency hops.

[0146] Embodiment B3. The method of Embodiment B 1 , wherein the configured SRS frequency hopping scheme includes a hopping pattern, the hopping pattern being based on a band configuration, the band configuration being at least one of frequency division duplex (FDD), time division duplex (TDD and half duplex FDD (HD-FDD).

[0147] Embodiment Cl. A wireless device (WD) configured to communicate with a network node, the WD configured to, and/or comprising a radio interface and/or processing circuitry configured to: receive a sounding reference signal, SRS, frequency hopping scheme, the scheme including a configuration for at least one of partial intra-slot SRS frequency hopping, partial inter-slot SRS frequency hopping, and inter-slot SRS frequency hopping within continuous slots; and communicate with the network node according to the configured SRS frequency hopping scheme.

[0148] Embodiment C2. The WD of Embodiment Cl, wherein the configured SRS frequency hopping scheme includes a configuration for one radio frequency (RF) carrier for each of a plurality of SRS frequency hops.

[0149] Embodiment C3. The WD of Embodiment Cl, wherein the configured SRS frequency hopping scheme includes a hopping pattern, the hopping pattern being based on a band configuration, the band configuration being at least one of frequency division duplex (FDD), time division duplex (TDD and half duplex FDD (HD-FDD).

[0150] Embodiment DI. A method implemented in a wireless device (WD), the method comprising receiving a sounding reference signal, SRS, frequency hopping scheme, the scheme including a configuration for at least one of partial intra-slot SRS frequency hopping, partial inter-slot SRS frequency hopping, and inter-slot SRS frequency hopping within continuous slots; and communicating with a network node according to the configured SRS frequency hopping scheme.

[0151] Embodiment D2. The method of Embodiment DI, wherein the configured SRS frequency hopping scheme includes a configuration for one radio frequency (RF) carrier for each of a plurality of SRS frequency hops.

[0152] Embodiment D3. The method of Embodiment DI, wherein the configured SRS frequency hopping scheme includes a hopping pattern, the hopping pattern being based on a band configuration, the band configuration being at least one of frequency division duplex (FDD), time division duplex (TDD and half duplex FDD (HD-FDD).

Claims

1. A network node configured to communicate with a user equipment (UE), the network node comprising: a radio interface; and processing circuitry configured to: configure the UE for a sounding reference signal, SRS, frequency hopping scheme, the scheme including an SRS configuration for at least one of: partial intra-slot SRS frequency hopping, partial inter-slot SRS frequency hopping, and inter-slot SRS frequency hopping within continuous slots; and communicate with the UE according to the configured SRS frequency hopping scheme.

2. The network node of claim 1, wherein the configured SRS frequency hopping scheme includes a configuration for one radio frequency (RF) carrier for each of a plurality of SRS frequency hops.

3. The network node of claim 1, wherein the configured SRS frequency hopping scheme includes a hopping pattern, the hopping pattern being based on a band configuration, the band configuration being at least one of frequency division duplex (FDD), time division duplex (TDD and half duplex FDD (HD-FDD).

4. The network node of claim 1 , wherein the SRS frequency hopping scheme is configured based on association with a virtual bandwidth or virtual bandwidth part.

5. The network node of claim 4, wherein a start index of the resource block (RB) in the virtual bandwidth or virtual bandwidth part is the same as the start index of a given bandwidth part.

6. The network node of claim 5, wherein the given bandwidth part is: an initial bandwidth part, an active bandwidth part, a current bandwidth part, or an indicated bandwidth part for the SRS configuration.

7. The network node of claim 1, wherein the SRS configuration is based on information related to time frequency resources used for SRS frequency hopping.

8. The network node of claim 7, wherein the information related to timefrequency resources comprises information: associated with a list of number of RBs, wherein each number of RBs in this list indicates the number of RBs of partial overlapped frequency in two adjacent hops, the first number indicates the number of RBs of partial overlapped frequency of hop 0 and hop 1, the second number indicates the number of RBs of partial overlapped frequency of hop 1 and hop 2.

9. The network node of claim 7, wherein the information related to timefrequency resources comprises information associated with an overlap factor.

10. The network node of claim 9, wherein the overlap factor indicates the number of RBs of partial overlapped frequency in two adjacent hops.

11. The network node of claim 7, wherein the information is associated with the bandwidth of one hop, and wherein each hop in one whole SRS frequency hopping has common bandwidth.

12. The network node of claim 7, wherein the information is associated with or with the time gap between two adjacent hops.

13. The network node of claim 7, wherein the information is associated with the number of OFDM symbols of each hop.

14. The network node of claim 7, wherein the information is associated with a start offset value, which is equal to the total number of symbols in one time slot minus the index of the start symbol of the first hop in the same time slot

15. The network node of claim 7, wherein the information

16. The network node of claim 7, wherein the information is associated with the number of hops in one whole SRS frequency hopping

17. The network node of claim 7, wherein the information is associated with a number of the symbols, which is equal to the total number of symbols used for SRS transmission plus the total number of symbols used for the time gaps above in a whole SRS frequency hopping.

18. The network node of claim 7, wherein the information is associated with the periodicity which is the difference of the start times of two adjacent whole SRS frequency hopping.

19. The network node of claim 7, wherein the information is associated with repetition number#2 which indicates the number of continuous whole SRS frequency hopping in one period.

20. A method implemented in a network node, the method comprising: configuring a wireless device for a sounding reference signal, SRS, frequency hopping scheme, the scheme including a configuration for at least one of partial intra-slot SRS frequency hopping, partial inter-slot SRS frequency hopping, and inter-slot SRS frequency hopping within continuous slots; and communicating with the wireless device according to the configured SRS frequency hopping scheme.

21. The method of claim 20, wherein the configured SRS frequency hopping scheme includes a configuration for one radio frequency (RF) carrier for each of a plurality of SRS frequency hops.

22. The method of claim 20, wherein the configured SRS frequency hopping scheme includes a hopping pattern, the hopping pattern being based on a band configuration, the band configuration being at least one of frequency division duplex (FDD), time division duplex (TDD and half duplex FDD (HD-FDD).

23. A user equipment (UE) configured to communicate with a network node, the UE comprising: a radio interface; and processing circuitry configured to: receive a sounding reference signal, SRS, frequency hopping scheme, the scheme including an SRS configuration for at least one of partial intra-slot SRS frequency hopping, partial inter-slot SRS frequency hopping, and inter-slot SRS frequency hopping within continuous slots; and communicate with the network node according to the configured SRS frequency hopping scheme.

24. The UE of claim 23, wherein the configured SRS frequency hopping scheme includes a configuration for one radio frequency (RF) carrier for each of a plurality of SRS frequency hops.

25. The UE of claim 23, wherein the configured SRS frequency hopping scheme includes a hopping pattern, the hopping pattern being based on a band configuration, the band configuration being at least one of frequency division duplex (FDD), time division duplex (TDD and half duplex FDD (HD-FDD).

26. The UE of claim 23, wherein the SRS frequency hopping scheme is configured based on association with a virtual bandwidth or virtual bandwidth part.

27. The UE of claim 26, wherein a start index of the resource block (RB) in the virtual bandwidth or virtual bandwidth part is the same as the start index of a given bandwidth part.

28. The UE of claim 27, wherein the given bandwidth part is: an initial bandwidth part, an active bandwidth part, a current bandwidth part, or an indicated bandwidth part for the SRS configuration.

29. The UE of claim 23, wherein the SRS configuration is based on information related to time frequency resources used for SRS frequency hopping.

30. The UE of claim 29, wherein the information related to time-frequency resources comprises information: associated with a list of number of RBs, wherein each number of RBs in this list indicates the number of RBs of partial overlapped frequency in two adjacent hops, the first number indicates the number of RBs of partial overlapped frequency of hop 0 and hop 1, the second number indicates the number of RBs of partial overlapped frequency of hop 1 and hop 2.

31. The UE of claim 29, wherein the information related to time-frequency resources comprises information associated with an overlap factor.

32. The UE of claim 29, wherein the overlap factor indicates the number of RBs of partial overlapped frequency in two adjacent hops.

33. The UE of claim 29, wherein the information is associated with the bandwidth of one hop, and wherein each hop in one whole SRS frequency hopping has common bandwidth.

34. The UE of claim 29, wherein the information is associated with or with the time gap between two adjacent hops.

35. The UE of claim 29, wherein the information is associated with the number of OFDM symbols of each hop.

36. The UE of claim 29, wherein the information is associated with a start offset value, which is equal to the total number of symbols in one time slot minus the index of the start symbol of the first hop in the same time slot.

37. The UE of claim 29, wherein the information is associated with the number of hops in one whole SRS frequency hopping

38. The UE of claim 29, wherein the information is associated with a number of the symbols, which is equal to the total number of symbols used for SRS transmission plus the total number of symbols used for the time gaps above in a whole SRS frequency hopping.

39. The UE of claim 29, wherein the information is associated with the periodicity which is the difference of the start times of two adjacent whole SRS frequency hopping.

40. The UE of claim 29, wherein the information is associated with repetition number#2 which indicates the number of continuous whole SRS frequency hopping in one period.

41. A method implemented in a user equipment (UE), the method comprising receiving a sounding reference signal, SRS, frequency hopping scheme, the scheme including a configuration for at least one of partial intra-slot SRS frequency hopping, partial inter-slot SRS frequency hopping, and inter-slot SRS frequency hopping within continuous slots; and communicating with a network node according to the configured SRS frequency hopping scheme.

42. The method of claim 41, wherein the configured SRS frequency hopping scheme includes a configuration for one radio frequency (RF) carrier for each of a plurality of SRS frequency hops.

43. The method of claim 41, wherein the configured SRS frequency hopping scheme includes a hopping pattern, the hopping pattern being based on a band configuration, the band configuration being at least one of frequency division duplex (FDD), time division duplex (TDD and half duplex FDD (HD-FDD).