SOUNDING REFERENCE SIGNAL SUBBAND-LEVEL SOUNDING

TECHNICAL FIELD

Particular embodiments relate to wireless communication, and more specifically to a sounding reference signal (SRS) subband-level sounding.

BACKGROUND

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

Third Generation Partnership Project (3 GPP) long term evolution (LTE) and new radio (NR) wireless networks use a sounding reference signal (SRS) to estimate the uplink channel. The SRS provides a reference signal to evaluate the channel quality to, e.g., derive the appropriate transmission/reception beams or to perform link adaptation (i.e., setting the rank, the modulation and coding scheme (MCS), and the multiple-input multiple-output (MIMO) precoder) for physical uplink shared channel (PUSCH) transmission. The signal is functionally similar to the downlink (DL) channel-state information reference signal (CSI-RS), which provides similar beam management and link adaptation functions in the downlink. SRS may be used instead of (or in combination with) CSI-RS to acquire downlink CSI (by means of uplink-downlink channel reciprocity) for enabling physical downlink shared channel (PDSCH) link adaptation.

In LTE and NR, the SRS is configured via radio resource control (RRC) and some parts of the configuration can be updated (for reduced latency) by medium access control (MAC) control element (CE) signaling. The configuration includes the SRS resource allocation (the physical mapping and sequence to use) as well as the time (aperiodic/semi-persistent/periodic) behavior. For aperiodic SRS transmission, the RRC configuration does not activate an SRS transmission from the user equipment (UE), but instead a dynamic activation trigger is transmitted via the physical downlink control channel (PDCCH) downlink control information (DCI) in the downlink from the gNodeB (gNB) to instruct the UE to transmit the SRS once, at a predetermined time.

The SRS configuration includes an SRS transmission pattern based on an SRS resource configuration grouped into SRS resource sets. Each SRS resource is configured with the following abstract syntax notation (ASN) code in RRC (see 3GPP 38.331 version 16.1.0).

To create the SRS resource on the time-frequency grid with the current RRC configuration, each SRS resource is thus configurable with respect to transmission comb, time domain, and frequency domain.

The transmission comb (i.e., mapping to every n ^th subcarrier, where n = 2 orn = 4) is configured by the RRC parameter transmissionComb . For each SRS resource, a comb offset, configured by the RRC parameter combOffset, is specified (i.e., which of the n combs to use). A cyclic shift, configured by the RRC parameter cyclicShift, that maps the SRS sequence to the assigned comb, is also specified. The cyclic shift increases the number of SRS resources that can be mapped to a comb, but there is a limit on how many cyclic shifts that can be used that depends on the transmission comb being used.

The time-domain position of an SRS resource within a given slot is configured with the RRC parameter resourceMapping. A time-domain start position for the SRS resource, which is limited to be one of the last 6 symbols in a slot, is configured by the RRC parameter startPosition. A number of orthogonal frequency-division multiplexing (OFDM) symbols for the SRS resource (that can be set to 1, 2 or 4) is configured by the RRC parameter nrofSymbols. A repetition factor (that can be set to 1, 2 or 4) is configured by the RRC parameter repetitionFactor. When this parameter is larger than 1, the same frequency resources are used multiple times across OFDM symbols, used to improve the coverage as more energy is collected by the receiver. It can also be used for beam-management functionality, where the gNB can probe different receive beams for each repetition.

The frequency-domain sounding bandwidth and position of an SRS resource in a given OFDM symbol (i.e., which part of the system bandwidth is occupied by the SRS resource) is configured with the RRC parameters freqDomainPosition, freqDomainShift and the freqHopping parameters: c-SRS, b-SRS and b-hop. The smallest possible sounding bandwidth in a given OFDM symbol is 4 resource blocks (RBs).

FIGURE 1 is a schematic illustration of how an SRS resource is allocated in time and frequency in a given OFDM symbol within a slot. Note that c-SRS controls the maximum sounding bandwidth, which can be smaller than the maximum transmission bandwidth the UE supports. For example, the UE may have capability to transmit over 40 MHz bandwidth, but c- SRS is set to a smaller value corresponding to 5 MHz, thereby focusing the available transmit power to a narrowband transmission which improves the SRS coverage.

NR release 16 includes an additional RRC parameter referred to as resour ceMapping- rl6. If resourceMapping-rl6 is signaled, the UE shall ignore the RRC parameter resourceMapping. The difference between resourceMapping-rl6 and resourceMapping is that the SRS resource (for which the number of OFDM symbols and repetition factor is still limited to 4) can start in any of the 14 OFDM symbols (see FIGURE 2) within a slot, configured by the RRC parameter startPosition-r16.

The RRC parameter resourceType configures whether the resource is transmitted as periodic, aperiodic (single transmission triggered by DCI), or semi persistent (same as periodic but the start and stop of the periodic transmission is controlled by MAC CE signaling instead of RRC signaling). The RRC parameter sequenceld specifies how the SRS sequence is initialized and the RRC parameter spatialRelationlnfo configures the spatial relation for the SRS beam with respect to a reference signal (RS), which may be either another SRS, synchronization signal block (SSB) or CSI-RS. Thus, if the SRS has a spatial relation to another SRS, then this SRS should be transmitted with the same beam (i.e., spatial transmit filter) as the indicated SRS.

The SRS resource is configured as part of an SRS resource set. Within a set, the following parameters (common to all resources in the set) are configured in RRC. The associated CSI-RS resource (this configuration is only applicable for non-codebook-based uplink transmission) for each of the possible resource types (aperiodic, periodic and semi persistent). For aperiodic SRS, the associated CSI-RS resource is set by the RRC parameter csi-RS. For periodic and semi-persistent SRS, the associated CSI-RS resource is set by the RRC parameter associatedCSI-RS. Note that all resources in a resource set must share the same resourcetype.

Foraperiodicresources,theslotoffsetisconfiguredbytheRRC parameterslotOffset and setsthedelay from thePDCCH triggerreceptionto startofthetransmission oftheSRS resourcesmeasuredinslots.

The configuration includes the resource usage,which is configured by the RRC parameterusage setsthe constraintsand assumption on theresource properties(see 3GPP

38.214).

The configuration includes power-control RRC parameters alpha, p0, pathlossReferenceRS (indicatingthedownlinkreferencesignal(RS)thatcanbeusedforpat h- loss estimation),srs-PowerControlAdjustmentStates,andpathlossRefe renceRSList-r16 (for NR release16),whichareusedfordeterminingtheSRStransmitpower.

Each SRSresourcesetisconfiguredwiththefollowingASN codeinRRC (see3GPP 38.331version 16.1.0):

Thus, in terms of resource allocation, the SRS resource set configures usage, power control, aperiodic transmission timing, and downlink resource association. The SRS resource configuration controls the time-and-frequency allocation, the periodicity and offset of each resource, the sequence ID for each resource and the spatial-relation information.

SRS resources may be mapped to antenna ports. SRS resources can be configured with four different usages: ‘beamManagement’, ‘codebook’, ‘nonCodebook’ or ‘antennaSwitching’ .

SRS resources in an SRS resource set configured with usage ‘beamManagement’ are mainly applicable for frequency bands above 6 GHz (i.e., for frequency range 2 (FR2)) and the purpose is to enable the UE to evaluate different UE transmit beams for wideband (e.g., analog) beamforming arrays. The UE transmits one SRS resource per wideband beam, and the gNB performs reference signal received power (RSRP) measurement on each of the transmitted SRS resources and in this way determines a suitable UE transmit beam. The gNB can then inform the UE which transmit beam to use by updating the spatial relation for different uplink RSs. It is expected that the gNB will configure the UE with one SRS resource set with usage ‘beamManagement’ for each analog array (panel) that the UE has.

SRS resources in an SRS resource set configured with usage ‘codebook’ are used to sound the different UE antennas and let the gNB determine suitable precoders, rank and MCS for PUSCH transmission. How each SRS port is mapped to each UE antenna is up to UE implementation, but it is expected that one SRS port will be transmitted per UE antenna, i.e. the SRS port to antenna-port mapping will be an identity matrix.

SRS resources in an SRS resource set configured with usage ‘nonCodebook’ are used to sound different potential precoders, autonomously determined by the UE. The UE determines a set of precoder candidates based on reciprocity, transmits one SRS resource per candidate precoder, and the gNB can then, by indicating a subset of these SRS resources, select which precoder(s) the UE should use for PUSCH transmission. One uplink layer will be transmitted per indicated SRS, hence candidate precoder. How the UE maps the SRS resources to the antenna ports is up to UE implementation and depends on the channel realization. SRS resources in an SRS resource set configured with usage ‘antennaSwitching’ are used to sound the channel in the uplink so that the gNB can use reciprocity to determine suitable downlink precoders. If the UE has the same number of transmit and receive chains, the UE is expected to transmit one SRS port per UE antenna. The mapping from SRS ports to antenna ports is, however, up to the UE to decide and is transparent to the gNB.

Uplink coverage for SRS is identified as a bottleneck for NR and a limiting factor for downlink reciprocity-based operation. Some measures to improve the coverage of SRS have been adopted in NR, for example repetition of an SRS resource and/or frequency hopping. One example of frequency hopping is illustrated in FIGURE 3, where different parts of the frequency band are sounded in different OFDM symbols, which means that the power spectral density (PSD) for the SRS will improve. Here, the illustrated frequency-hopping pattern is set according to Section 6.4 of 3GPP 38.211. FIGURE 4 illustrates an example of repetition, where one SRS resource is transmitted in four consecutive OFDM symbols, which will increase the processing gain of the SRS.

SRS transmission includes power scaling. SRS has its own uplink power control (PC) scheme in NR, which can be found in Section 7.3 of 3GPP 38.213. Section 7.3 in 38.213 additionally specifies how the UE should split the above output power between two or more SRS ports during one SRS transmit occasion (an SRS transmit occasion is a time window within a slot where SRS transmission is performed). Specifically, the UE splits the transmit power equally across the configured antenna ports for SRS.

SRS transmission may include antenna switching. Because it is desirable for the gNB to sound all UE antennas (where sounding an antenna means transmitting an SRS from that antenna, which, in turn, enables the gNB to estimate the channel between said UE antenna and the antennas at the gNB) but costly to equip the UE with many transmit ports, SRS antenna switching was introduced in NR Rel-15, for several different UE architectures for which the number of receive chains is larger than the number of transmit chains. If a UE support antenna switching, it will report so by means of UE-capability signaling.

The left column of FIGURE 5 (from 3GPP 38.306) lists SRS antenna-switching capabilities that can be reported from a UE in NR Rel-15. For example, if a UE reports tlr2 in the UE-capability signaling, it means that it has two receive antennas (i.e., two receive chains) but only has the possibility of transmitting from one of those antennas at a time (i.e., one transmission chain) with support for antenna switching. In this case, two single-port SRS resources can be configured to the UE such that it can sound both receive ports using a single transmit port with an antenna switch in between.

Additional UE capabilities were further introduced in NR Rel-16, see right column of FIGURE 5, which indicates support for the UE to be configured with SRS resource set(s) with usage ‘ antennaSw itching ’ but where only a subset of all UE antennas is sounded. For example, the UE capability tlrl-tlr2 means that the gNB can configure one single-port SRS resource (same as no antenna-switching capability) or two single-port SRS resources (same as for the capability “lt2r” described above) with usage ‘ antennaSw itching" per SRS resource set. In this case, if the UE is configured with a single SRS resource (no antenna switching) it will only sound only one of its two antennas, which will save UE power consumption at the cost of reduced channel knowledge at the gNB (because the gNB can only estimate the channel between itself and the UE based on one of the two UE antennas).

Each entry of the table in FIGURE 5 is here referred to as an antenna switching configuration. Each antenna switching configuration is associated with one or several possible SRS configurations (where each SRS configuration includes a number of SRS resource sets, a number of SRS resources per SRS resource set, a number of SRS ports per SRS resource, etc.). Thus, if a UE signals the UE capability tlrl-tlr2, it means that the UE supports to be configured both with the antenna switching configuration tlrl and the antenna switching configuration tlr2.

There currently exist certain challenges. For example, as described above, uplink coverage for SRS can be improved by SRS repetition and/or SRS frequency hopping. SRS repetition, however, suffers from the drawback that SRS multiplexing capacity is reduced (more time/frequency resources are consumed by SRS compared to the no-repetition case). To enhance coverage without sacrificing multiplexing capacity, SRS frequency hopping may be used (in fact, frequency hopping can improve multiplexing capacity if the number of frequency hops per slot times the bandwidth per hop is less than the transmission bandwidth).

As used herein, not sounding the entire transmission bandwidth in a slot is referred to as partial frequency sounding. In particular, the schemes considered herein, i.e., not sounding the entire transmission bandwidth in a slot by using a minimum of four RBs of contiguous bandwidth per frequency hop, is referred to as subband-level partial frequency sounding. Note that with subband-level partial frequency sounding, SRS coverage as well as SRS multiplexing capacity is, in theory, enhanced compared to transmitting SRS over the entire transmission bandwidth in a single OFDM symbol. However, in practice, existing SRS frequency-hopping schemes suffer from some drawbacks, as described next.

The limitations of existing frequency-hopping solutions are best illustrated by example. Consider an uplink sounding in which the network desires to estimate the channel over 24 physical RBs (PRBs) (which corresponds, e.g., to FR1 transmission for when the transmission bandwidth is set to 10 MHz and the subcarrier spacing is 30 kHz, see Clause 5.3.2 of 3GPP TS 38.101-1). As described above, to enhance coverage without sacrificing multiplexing capacity, the UE wants to concentrate the UE power onto a subset of the 24 PRBs in each OFDM symbol. Specifically, to maximize the power per frequency unit per OFDM symbol, the network only wants to sound four PRBs (which is the smallest number of PRBs that can be sounded by SRS in NR Rel-16) in each OFDM symbol.

In current releases of NR, as described above, there exists mechanisms for configuring the SRS bandwidth configuration and the frequency-hopping configuration. The shortcomings of existing mechanisms are demonstrated using two examples. Specifically, when nrofSymbols = 2 and startPosition = 1 (two SRS symbols in the last two symbols of a slot), the following two SRS configurations may be used:

Case 1 : c-SRS = 7, b-hop = 0, b-SRS = 2,freqDomainPosition = 0, and freqDomainShift = 0, which results in a total of m _SRS,0 = 24 PRBs (starting from PRB 0) beings sounded with m _SRS,2 ⁼ 4 PRBs per hop (i.e., per SRS symbol).

Case 2: c-SRS = 1, b-hop = 0, b-SRS = 1, freq o ain Position = 0, and freqDomainShift = 8, which results in a total of m _SRS,0 = 8 PRBs (starting from PRB 8) beings sounded with m _SRS,1 = 4 PRBs per hop (i.e., per SRS symbol).

The transmitted SRS over 3 slots (6 SRS symbols) for a periodic SRS resource configured as in Case 1 is illustrated in FIGURE 6. As illustrated, all 24 PRBs are sounded over the 3 slots (6 OFDM symbols) with 4 PRBs being sounded in each hop. The cross hatch pattern area illustrates OFDM symbols used for SRS. PRBs where SRS is being transmitted are highlighted as solid black.

A downside of the configuration in Case 1 is that noncontiguous bandwidth is being sounded in each slot, which, in general, results in degraded channel-estimate quality (which, in turn, leads to, e.g., suboptimal choice of downlink precoder and/or suboptimal choice of uplink precoder) compared to the case when a contiguous bandwidth is sounded (in particular if the gap between the two frequency hops is large (e.g., if it exceeds the coherence bandwidth of the channel).

A contiguous bandwidth of 8 PRBs is sounded in each slot by instead transmitting a periodic SRS resource according to the configuration in Case 2, as illustrated in FIGURE 7. The cross hatch pattern area illustrates OFDM symbols used for SRS. PRBs where SRS is being transmitted are highlighted as solid black.

A downside of this approach is that only 8 of the 24 PRBs are sounded over the 3 slots (6 OFDM symbols). Thus, the channel estimate needs to be extrapolated to the nonsounded PRBs (i.e., to PRB 0 — 7 and 16 — 23), which, reduces the quality of the channel estimate for those PRBs (whereas the channel estimate for the sounded PRBs, i.e., PRB 8 — 15, is improved).

The current release of NR does not include a mechanism for sounding with periodic/semi-persistent SRS the entire transmission bandwidth using contiguous frequency hops in a slot except for the special case in which the bandwidth per hop (the actual sounding bandwidth in FIGURES 1 and 2 is equal to the full transmission bandwidth (the maximum sounding bandwidth in FIGURES 1 ad 2) divided by the number of SRS symbols per slot.

For large sounding bandwidths (in NR, up to 272 PRBs can be sounded by as few as 4 PRBs per hop), the gap between frequency hops can be very large (up to 132 PRBs), and thus it becomes increasingly important to have mechanisms for reducing the gap if narrowband SRS transmissions are desired (e.g., for narrowband transmitters or in coverage-limited scenarios).

SUMMARY

As described above, certain challenges currently exist with sounding reference signal (SRS) subband-level sounding. Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments include an SRS enhancement that facilitates sounding a wide bandwidth using one or more frequency hops per slot that together span, over all slots, either (1) a contiguous bandwidth or (2) a bandwidth for which the gap between the frequency hops is smaller than what is possible in the current release of new radio (NR).

Some embodiments facilitate time-varying subband-level frequency hopping for periodic/semi-persistent SRS resources according to a predefined rule.

In general, particular embodiments configure a “subband” whose bandwidth equals the SRS hopping bandwidth that varies over time (e.g., over slots or after all frequency hops within that bandwidth has been sounded) and spans the maximum sounding bandwidth over all sounded slots. Within each subband, normal frequency-hopping schemes apply.

According to some embodiments, a method performed by a wireless device comprises: receiving a SRS configuration comprising a frequency hopping pattern over a plurality of slots wherein a frequency domain starting position varies per slot; and transmitting SRS according to the received SRS configuration.

In particular embodiments, the SRS configuration comprises a frequency hopping pattern over a plurality of slots and a frequency domain starting position for each slot such that one or more frequency hops per slot together span, over the plurality of slots, a contiguous bandwidth.

In particular embodiments, the SRS configuration comprises a frequency hopping pattern over a plurality of slots and a frequency domain starting position for each slot such that one or more frequency hops per slot together span, over the plurality of slots, a bandwidth for which any gap between the frequency hops is smaller than current new radio (NR) configurations.

In particular embodiments, each frequency hop comprises a frequency hop bandwidth and the frequency domain starting position is incremented by the frequency hop bandwidth for each slot of the plurality of slots.

In particular embodiments, the frequency domain starting position is incremented after a fixed number of slots of the plurality of slots.

In particular embodiments, the frequency domain starting position is incremented according to a pre-defined hopping pattern. According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the wireless device methods described above.

Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless device described above.

According to some embodiments, a method performed by a network node comprises: transmitting, to a wireless device, a SRS configuration comprising a frequency hopping pattern over a plurality of slots wherein a frequency domain starting position varies per slot; and receiving SRS from the wireless device according to the transmitted SRS configuration.

The SRS configuration may comprise any of the configurations described above with respect to the wireless device.

According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.

Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network node described above.

Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments include a flexible SRS resource configuration for which sounding a contiguous bandwidth within a slot is enabled for a large range of bandwidth configurations compared to current releases of NR.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

FIGURE 1 is a schematic illustration of how an SRS resource is allocated in time and frequency within a slot if resourceMapping-r16 is not signaled; FIGURE 2 is a schematic description of how an SRS resource is allocated in time and frequency within a slot if resourceMapping-rl6 is signaled;

FIGURE 3 is a time/frequency diagram illustrating SRS transmission using frequency hopping;

FIGURE 4 is a time/frequency diagram illustrating SRS transmission using repetition;

FIGURE 5 is a table illustrating example SRS antenna-switching capabilities supported by a UE;

FIGURE 6 is a time/frequency diagram illustrating SRS transmission over three slots according to the configuration in Case 1;

FIGURE 7 is a time/frequency diagram illustrating SRS transmission over three slots according to the configuration in Case 2;

FIGURE 8 is a time/frequency diagram illustrating SRS transmission over 3 slots, according to particular embodiments;

FIGURE 9 is a time/frequency diagram illustrating frequency-domain starting position for subband-level partial sounding that is incremented after each slot;

FIGURE 10 is a time/frequency diagram illustrating frequency-domain starting position for subband-level partial sounding that is incremented as soon as the entire hopping bandwidth has been sounded;

FIGURE 11 is a time/frequency diagram illustrating legacy (NR Rel-16) sounding over 96 RBs (with b-hop = 0, to sound over the maximum sounding bandwidth according to predefined frequency -hopping pattern);

FIGURE 12 is a time/frequency diagram illustrating enhanced sounding over 96 RBs (with b-hop = 1, to sound over a third of the maximum sounding bandwidth in each slot according to predefined frequency -hopping pattern);

FIGURE 13 is a time/frequency diagram illustrating a frequency-hopping pattern within each subband that is the same as for legacy NR;

FIGURE 14 is a time/frequency diagram illustrating another frequency-hopping pattern within each subband is the same as for legacy NR, and the same frequency pattern is applied to each subband over slots;

FIGURE 15 is a block diagram illustrating an example wireless network; FIGURE 16 illustrates an example user equipment, according to certain embodiments;

FIGURE 17A is flowchart illustrating an example method in a wireless device, according to certain embodiments;

FIGURE 17B is flowchart illustrating an example method in a network node, according to certain embodiments;

FIGURE 18 illustrates a schematic block diagram of a wireless device and network node in a wireless network, according to certain embodiments;

FIGURE 19 illustrates an example virtualization environment, according to certain embodiments;

FIGURE 20 illustrates an example telecommunication network connected via an intermediate network to a host computer, according to certain embodiments;

FIGURE 21 illustrates an example host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments;

FIGURE 22 is a flowchart illustrating a method implemented, according to certain embodiments;

FIGURE 23 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments;

FIGURE 24 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments; and

FIGURE 25 is a flowchart illustrating a method implemented in a communication system, according to certain embodiments.

DETAILED DESCRIPTION

As described above, certain challenges currently exist with sounding reference signal (SRS) subband-level sounding. Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges.

For example, particular embodiments include an SRS enhancement that facilitates sounding a wide bandwidth using one or more frequency hops per slot that together span, over all slots, either (1) a contiguous bandwidth or (2) a bandwidth for which the gap between the frequency hops is smaller than what is possible in the current release of new radio (NR). Some embodiments facilitate time-varying subband-level frequency hopping for periodic/semi- persistent SRS resources according to a predefined rule.

Particular embodiments are described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

Particular embodiments include solutions for configuring, e.g., the sounding patterns illustrated in FIGURE 8Error! Reference source not found.. The illustrated pattern cannot be configured with a single SRS resource in current release of NR.

Comparing the pattern in Error! Reference source not found.FIGURE 8 to the pattern in FIGURE 6Error! Reference source not found, reveals that the transmission bandwidth of 24 RBs are now sounded using a contiguous set of 8 RBs per slot but with a varying frequency- domain start position (which is in contrast to the pattern in FIGURE 7). Thus, particular embodiments may sound the entire transmission bandwidth with SRS transmissions of 4 PRBs per OFDM symbol and in a contiguous bandwidth per slot (which enables improved channel- estimate quality).

Due to a plethora of available SRS bandwidth configurations (see Table 6.4.1.4.3-1 in 3GPP TS 38.211), particular embodiments may configure a large variation of subband-level partial (or full) sounding patterns (without altering the existing frequency-hopping pattern in Clause 6.4.1.4.3 in 3GPP TS 28.211).

As used herein, the terms entire bandwidth, transmission bandwidth, and maximum sounding bandwidth are used interchangeably. The terms “hopping bandwidth”, “subband bandwidth”, and “actual sounding bandwidth” are also used interchangeably.

As used herein, n _start (measured in RBs) denotes the frequency-domain starting position for an SRS transmission. In current specification, this value depends on c-SRS, h-hop, b-SRS, freqDomainPosition, freqDomainShift, and on the number of SRS transmissions (not including repeated SRS transmission) as exemplified in FIGURES 6 and 7 above. For example, in FIGURE 6Error! Reference source not found., n _start = 0 in OFDM symbol 12, n _start = 12 in OFDM symbol 13, n _start = 4 in OFDM symbol 26, and so on. Inafirstgroupofembodiments,theSRSfrequency-domainstartingpos itionmay,via radioresourcecontrol(RRC),beconfiguredtovarybetween SRStransmissionsaccordingto apredefined rulethatfacilitatesenhanced channel-estimateacquisition compared to legacy NR.Specifically,an additionalfieldreferredtoas,e.g.,subbandLevelHopping-p/sp-r1 7may beincludedin SRS ConfigIE (see3GPP TS 38.211)asshown inASN foran SRS resource below. p

In some embodiments, when subbandLevelHopping-p/sp-r17 is activated (i.e., when it is set to true) for a periodic/semi-persistent SRS resource, the frequency-domain start position nstart is incremented by m _SRS,b-hop RBs (where m _SRS,b-hop is the hopping bandwidth, which depends on c-SRS and b-hop as specified in Clause of 3GPP TS 38.211) after each slot in which SRS has been transmitted.

In some embodiments, if n _start 4- m _{SRS b-hop} exceeds m _SRS,0 RBs (where m _SRS,0 denotes the entire bandwidth and depends on c-SRS as specified in 3GPP TS 38.211) in any symbol, the frequency-domain starting position for SRS transmission is set to n _start = 0 and is thereafter incremented as described above. This ensures that the procedure restarts after the entire bandwidth has been sounded.

In some embodiments, the frequency-domain starting position is not incremented after each slot but instead after frequency hops (where N _t depends on c-SRS in 3GPP TS 38.211). When subbandLevelHopping-p/sp-r17 is activated, the pattern illustrated in FIGURE 7 can be configured according to this rule, e.g., by setting c-SRS = 6, b-hop = 2, b- SRS = 2, freqDomainPosition = 0, and freqDomainShift = 0.

FIGURES 9 and 10 illustrate the case when the frequency-domain start position is incremented for each slot and the case when it is incremented after the entire hopping bandwidth has been sounded, respectively. Here, subbandLevelHopping-p/sp-r17= true, c-SRS = 4, b-hop = 1, b-SRS = 2, freqDomainPosition = 0, freqDomainShift = 0, nrofSymbols = 4 and startPosition = 3. According to this configuration, the entire bandwidth is 16 RBs, the hopping bandwidth is 8 RBs, and there are 4 SRS symbols per slot.

In some embodiments, the frequency-domain starting position is incremented after frequency hops if is smaller than the number of SRS symbols per slot (i.e., if the entire hopping bandwidth is sounded within a slot), otherwise (i.e., if the entire hopping bandwidth is not sounded within a slot) it is incremented after each slot.

In some embodiments, when subbandLevelHopping-p/sp-r17 is activated, the frequency-domain start position n _start is changed according to some predefined hopping pattern (e.g., similar to the frequency hopping pattern in Clause 6.4.1.4.3 in 3GPP TS 38.211). The bandwidth in each slot need not necessarily be contiguous for all embodiments. In fact, for some (wideband) bandwidth configurations it is not possible to sound contiguous spectrum in each slot (with or without particular embodiments). Nevertheless, particular embodiments facilitate SRS enhancements for these cases also.

As an example, FIGURES 11 and 12 include sounding patterns with subbandLevelHopping-p/sp-r17 being deactivated (with b-hop = 0) and activated (with b-hop = 1 and with the frequency-domain position being incremented after each slot), respectively. Each square represents a chunk of 4 RBs Thus, c-SRS = 23 (such that the maximum sounding bandwidth is 96 RBs), and b-SRS = 3 (such that 4 RBs are sounded in each SRS symbol). Comparing FIGURES 11 and 12 reveals that the same RBs are sounded in both cases. However, with particular embodiments the gap between frequency hops in a slot is significantly smaller than in legacy NR (fixed to 12 RBs with particular embodiments compared to varying between 28 and 44 RBs without). This decreases the risk of the channel being significantly different between frequency hops, which improves, in general, the channel-estimate quality.

In particular embodiments, the configured frequency-hopping pattern (as in legacy NR) is used within each subband, but the subband is changing over time. FIGURE 13 illustrates particular embodiments when there are 4 SRS symbols within each slot. The frequency- hopping pattern within each subband (i.e., within the hopping bandwidth) is unchanged from current NR.

In a second group of embodiments, a new field referred to as, e.g., freqHopping-rl7 is included in SRS Config IE (see 3GPP TS 38.211) as shown in ASN for an SRS resource below.

In some embodiments, when freqHopping-r17 is configured, c-SRS-2 replaces the value of c-SRS in freqHopping, and c-SRS-1 > c-SRS-2 configures a bandwidth that should be sounded by SRS in increments (or according to a predefined hopping pattern) of the bandwidth configured c-SRS-1. Furthermore, b-SRS and b-hop in freqHopping-r17 replaces the corresponding parameters in freqHopping.

The second group of embodiments need not necessarily be limited to periodic/semi- persistent SRS, freqHopping-r17 could be used for aperiodic SRS as well (however, for particular embodiments to have an impact on aperiodic SRS sounding, the limit in the standard that aperiodic SRS should be contiguous in frequency in a slot should be revised).

For example, the sounding pattern in FIGURE 13 can be configured by setting, in freqHopping-r17, c-SRS-1 = 23 (96 RBs), c-SRS-2 = 9 (32 RBs), b-hop = 0 (32 RBs), and b- SRS = 3 (4 RBs). Furthermore,freqDomainPosition = freqDomainShift = 0, the number of SRS symbols per slot is 4, and the SRS sounding pattern is incremented by the bandwidth configured by c-SRS-2 after each slot (i.e., no hopping).

Another example of a sounding pattern that can be configured, according to the second group of embodiments, is the pattern in FIGURE 14. Here, c-SRS-1 = 23 (96 RBs), c-SRS-2 = 9 (32 RBs), b-hop = 2 (16 RBs), and b-SRS = 3 (4 RBs). Furthermore, freqDomainPosition = freqDomainShift = 0, the number of SRS symbols per slot is 4, and the SRS sounding pattern hops between subbands over slots according to a hopping pattern similar to the one in in Clause 6.4.1.4.3 in 3GPP TS 38.211.

FIGURE 15 illustrates an example wireless network, according to certain embodiments. The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node 160 and WD 110 comprise various components described in more detail below. These components work together to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.

Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.

A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.

As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In FIGURE 15, network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162. Although network node 160 illustrated in the example wireless network of FIGURE 15 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components.

It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 160 may be composed of multiple physically separate components (e.g., aNodeB component and aRNC component, or aBTS component and aBSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node.

In some embodiments, network node 160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 180 for the different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 160.

Processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry 170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 160 components, such as device readable medium 180, network node 160 functionality.

For example, processing circuitry 170 may execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 170 may include a system on a chip (SOC).

In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 170 alone or to other components of network node 160 but are enjoyed by network node 160 as a whole, and/or by end users and the wireless network generally.

Device readable medium 180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 170. Device readable medium 180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 170 and, utilized by network node 160. Device readable medium 180 may be used to store any calculations made by processing circuitry 170 and/or any data received via interface 190. In some embodiments, processing circuitry 170 and device readable medium 180 may be considered to be integrated.

Interface 190 is used in the wired or wireless communication of signaling and/or data between network node 160, network 106, and/or WDs 110. As illustrated, interface 190 comprises port(s)/terminal(s) 194 to send and receive data, for example to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that may be coupled to, or in certain embodiments a part of, antenna 162.

Radio front end circuitry 192 comprises filters 198 and amplifiers 196. Radio front end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front end circuitry may be configured to condition signals communicated between antenna 162 and processing circuitry 170. Radio front end circuitry 192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and/or amplifiers 196. The radio signal may then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals which are then converted into digital data by radio front end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 160 may not include separate radio front end circuitry 192, instead, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192. Similarly, in some embodiments, all or some of RF transceiver circuitry 172 may be considered a part of interface 190. In still other embodiments, interface 190 may include one or more ports or terminals 194, radio front end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).

Antenna 162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 162 may be coupled to radio front end circuitry 190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 162 may be separate from network node 160 and may be connectable to network node 160 through an interface or port.

Antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment. Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein. Power circuitry 187 may receive power from power source 186. Power source 186 and/or power circuitry 187 may be configured to provide power to the various components of network node 160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 186 may either be included in, or external to, power circuitry 187 and/or network node 160.

For example, network node 160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187. As a further example, power source 186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node 160 may include additional components beyond those shown in FIGURE 15 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 160 may include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.

In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.

Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.

As yet another specific example, in an Internet of Things (loT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).

In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136 and power circuitry 137. WD 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 110.

Antenna 111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from WD 110 and be connectable to WD 110 through an interface or port. Antenna 111, interface 114, and/or processing circuitry 120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 111 may be considered an interface.

As illustrated, interface 114 comprises radio front end circuitry 112 and antenna 111. Radio front end circuitry 112 comprise one or more filters 118 and amplifiers 116. Radio front end circuitry 114 is connected to antenna 111 and processing circuitry 120 and is configured to condition signals communicated between antenna 111 and processing circuitry 120. Radio front end circuitry 112 may be coupled to or a part of antenna 111. In some embodiments, WD 110 may not include separate radio front end circuitry 112; rather, processing circuitry 120 may comprise radio front end circuitry and may be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 may be considered a part of interface 114.

Radio front end circuitry 112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 118 and/or amplifiers 116. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals which are then converted into digital data by radio front end circuitry 112. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may comprise different components and/or different combinations of components. Processing circuitry 120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 110 components, such as device readable medium 130, WD 110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.

As illustrated, processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 120 of WD 110 may comprise a SOC. In some embodiments, RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips.

In alternative embodiments, part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and RF transceiver circuitry 122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and application processing circuitry 126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 122 may be a part of interface 114. RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.

In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 120 alone or to other components of WD 110, but are enjoyed by WD 110, and/or by end users and the wireless network generally.

Processing circuitry 120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 120, may include processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium 130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 120. Device readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non- transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 120. In some embodiments, processing circuitry 120 and device readable medium 130 may be integrated.

User interface equipment 132 may provide components that allow for a human user to interact with WD 110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to WD 110. The type of interaction may vary depending on the type of user interface equipment 132 installed in WD 110. For example, if WD 110 is a smart phone, the interaction may be via a touch screen; if WD 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).

User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 132 is configured to allow input of information into WD 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from WD 110, and to allow processing circuitry 120 to output information from WD 110. User interface equipment 132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 132, WD 110 may communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein.

Auxiliary equipment 134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 134 may vary depending on the embodiment and/or scenario.

Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 110 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of WD 110 which need power from power source 136 to carry out any functionality described or indicated herein. Power circuitry 137 may in certain embodiments comprise power management circuitry.

Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in which case WD 110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 137 may also in certain embodiments be operable to deliver power from an external power source to power source 136. This may be, for example, for the charging of power source 136. Power circuitry 137 may perform any formatting, converting, or other modification to the power from power source 136 to make the power suitable for the respective components of WD 110 to which power is supplied.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIGURE 15. For simplicity, the wireless network of FIGURE 15 only depicts network 106, network nodes 160 and 160b, and WDs 110, 110b, and 110c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 160 and wireless device (WD) 110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

FIGURE 16 illustrates an example user equipment, according to certain embodiments. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 200 may be any UE identified by the 3 ^rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 200, as illustrated in FIGURE 16, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3 ^rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although FIGURE 16 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In FIGURE 16, UE 200 includes processing circuitry 201 that is operatively coupled to input/output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, communication subsystem 231, power source 233, and/or any other component, or any combination thereof. Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Certain UEs may use all the components shown in FIGURE 16, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

In FIGURE 16, processing circuitry 201 may be configured to process computer instructions and data. Processing circuitry 201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 200 may be configured to use an output device via input/output interface 205.

An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 200 may be configured to use an input device via input/output interface 205 to allow a user to capture information into UE 200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In FIGURE 16, RF interface 209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 211 may be configured to provide a communication interface to network 243a. Network 243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243a may comprise a Wi-Fi network. Network connection interface 211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM 217 may be configured to interface via bus 202 to processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 219 may be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.

Storage medium 221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 221 may be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227. Storage medium 221 may store, for use by UE 200, any of a variety of various operating systems or combinations of operating systems.

Storage medium 221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro- DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 221 may allow UE 200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 221, which may comprise a device readable medium.

In FIGURE 16, processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231. Network 243a and network 243b may be the same network or networks or different network or networks. Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b. For example, communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 233 and/or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 233 and receiver 235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200.

The features, benefits and/or functions described herein may be implemented in one of the components of UE 200 or partitioned across multiple components of UE 200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 231 may be configured to include any of the components described herein. Further, processing circuitry 201 may be configured to communicate with any of such components over bus 202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 201 and communication subsystem 231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware. FIGURE 17A is a flowchart illustrating an example method in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 17A may be performed by wireless device 110 described with respect to FIGURE 15.

The method begins at step 1712, where the wireless device (e.g., wireless device 110) receiving a SRS configuration comprising a frequency hopping pattern over a plurality of slots wherein a frequency domain starting position varies per slot.

In particular embodiments, the SRS configuration comprises a frequency hopping pattern over a plurality of slots and a frequency domain starting position for each slot such that one or more frequency hops per slot together span, over the plurality of slots, a contiguous bandwidth.

In particular embodiments, the SRS configuration comprises a frequency hopping pattern over a plurality of slots and a frequency domain starting position for each slot such that one or more frequency hops per slot together span, over the plurality of slots, a bandwidth for which any gap between the frequency hops is smaller than current new radio (NR) configurations.

In particular embodiments, each frequency hop comprises a frequency hop bandwidth and the frequency domain starting position is incremented by the frequency hop bandwidth for each slot of the plurality of slots.

In particular embodiments, the frequency domain starting position is incremented after a fixed number of slots of the plurality of slots.

In particular embodiments, the frequency domain starting position is incremented according to a pre-defined hopping pattern.

In particular embodiments, the SRS configuration comprises any of the configurations described herein, such as those described with respect to FIGURES 8-14.

A step 1714, the wireless device transmits SRS according to the received SRS configuration.

Modifications, additions, or omissions may be made to method 1700 of FIGURE 17A. Additionally, one or more steps in the method of FIGURE 17A may be performed in parallel or in any suitable order. FIGURE 17B is a flowchart illustrating an example method in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 17B may be performed by network node 160 described with respect to FIGURE 15.

The method begins at step 1732, where the network node (e.g., network node 160) transmits, to a wireless device, a SRS configuration comprising a frequency hopping pattern over a plurality of slots wherein a frequency domain starting position varies per slot.

At step 1734, the network node receives SRS from the wireless device according to the transmitted SRS configuration.

The SRS configurations are described above with respect to FIGURE 17 A.

Modifications, additions, or omissions may be made to method 1730 of FIGURE 17B. Additionally, one or more steps in the method of FIGURE 17B may be performed in parallel or in any suitable order.

FIGURE 18 illustrates a schematic block diagram of two apparatuses in a wireless network (for example, the wireless network illustrated in FIGURE 15). The apparatuses include a wireless device and a network node (e.g., wireless device 110 and network node 160 illustrated in FIGURE 15). Apparatuses 1600 and 1700 are operable to carry out the example methods described with reference to FIGURE 17A and FIGURE 17B, respectively, and possibly any other processes or methods disclosed herein. It is also to be understood that the methods of FIGURE 17A and FIGURE 17B are not necessarily carried out solely by apparatuses 1600 and/or 1700. At least some operations of the methods can be performed by one or more other entities.

Virtual apparatuses 1600 and 1700 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving module 1602, determining module 1604, transmitting module 1606, and any other suitable units of apparatus 1600 to perform corresponding functions according one or more embodiments of the present disclosure. Similarly, the processing circuitry described above may be used to cause receiving module 1702, determining module 1704, transmitting module 1706, and any other suitable units of apparatus 1700 to perform corresponding functions according one or more embodiments of the present disclosure.

As illustrated in FIGURE 18, apparatus 1600 includes receiving module 1602 configured to receive SRS configuration according to any of the embodiments and examples described herein. Determining module 1604 is configured to determine SRS configurations according to any of the embodiments and examples described herein. Transmitting module 1606 is configured to transmit SRS according to any of the embodiments and examples described herein.

As illustrated in FIGURE 18, apparatus 1700 includes receiving module 1702 configured to a receive SRS according to any of the embodiments and examples described herein. Determining module 1704 is configured to determine SRS configuration according to any of the embodiments and examples described herein. Transmitting module 1706 is configured to transmit SRS configurations according to any of the embodiments and examples described herein.

FIGURE 19 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks). In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of hardware nodes 330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications 320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 320 are run in virtualization environment 300 which provides hardware 330 comprising processing circuitry 360 and memory 390. Memory 390 contains instructions 395 executable by processing circuitry 360 whereby application 320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment 300, comprises general-purpose or special-purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 390-1 which may be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360. Each hardware device may comprise one or more network interface controllers (NICs) 370, also known as network interface cards, which include physical network interface 380. Each hardware device may also include non-transitory, persistent, machine-readable storage media 390-2 having stored therein software 395 and/or instructions executable by processing circuitry 360. Software 395 may include any type of software including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software to execute virtual machines 340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines 340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the instance of virtual appliance 320 may be implemented on one or more of virtual machines 340, and the implementations may be made in different ways.

During operation, processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 350 may present a virtual operating platform that appears like networking hardware to virtual machine 340.

As shown in FIGURE 19, hardware 330 may be a standalone network node with generic or specific components. Hardware 330 may comprise antenna 3225 and may implement some functions via virtualization. Alternatively, hardware 330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which, among others, oversees lifecycle management of applications 320.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine 340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 340, and that part of hardware 330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 340, forms a separate virtual network elements (VNE).

Still in the context of NF V, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 340 on top of hardware networking infrastructure 330 and corresponds to application 320 in FIGURE 20.

In some embodiments, one or more radio units 3200 that each include one or more transmitters 3220 and one or more receivers 3210 may be coupled to one or more antennas 3225. Radio units 3200 may communicate directly with hardware nodes 330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signaling can be effected with the use of control system 3230 which may alternatively be used for communication between the hardware nodes 330 and radio units 3200.

With reference to FIGURE 20, in accordance with an embodiment, a communication system includes telecommunication network 410, such as a 3 GPP -type cellular network, which comprises access network 411, such as a radio access network, and core network 414. Access network 411 comprises a plurality of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c is connectable to core network 414 over a wired or wireless connection 415. A first UE 491 located in coverage area 413c is configured to wirelessly connect to, or be paged by, the corresponding base station 412c. A second UE 492 in coverage area 413a is wirelessly connectable to the corresponding base station 412a. While a plurality of UEs 491, 492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 412.

Telecommunication network 410 is itself connected to host computer 430, 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. Host computer 430 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. Connections 421 and 422 between telecommunication network 410 and host computer 430 may extend directly from core network 414 to host computer 430 or may go via an optional intermediate network 420. Intermediate network 420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 420, if any, may be a backbone network or the Internet; in particular, intermediate network 420 may comprise two or more sub-networks (not shown).

The communication system of FIGURE 20 as a whole enables connectivity between the connected UEs 491, 492 and host computer 430. The connectivity may be described as an over-the-top (OTT) connection 450. Host computer 430 and the connected UEs 491, 492 are configured to communicate data and/or signaling via OTT connection 450, using access network 411, core network 414, any intermediate network 420 and possible further infrastructure (not shown) as intermediaries. OTT connection 450 may be transparent in the sense that the participating communication devices through which OTT connection 450 passes are unaware of routing of uplink and downlink communications. For example, base station 412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 430 to be forwarded (e.g., handed over) to a connected UE 491. Similarly, base station 412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 491 towards the host computer 430.

FIGURE 21 illustrates an example host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments. Example implementations, in accordance with an embodiment of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIGURE 21. In communication system 500, host computer 510 comprises hardware 515 including communication interface 516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 500. Host computer 510 further comprises processing circuitry 518, which may have storage and/or processing capabilities. In particular, processing circuitry 518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 510 further comprises software 511, which is stored in or accessible by host computer 510 and executable by processing circuitry 518. Software 511 includes host application 512. Host application 512 may be operable to provide a service to a remote user, such as UE 530 connecting via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the remote user, host application 512 may provide user data which is transmitted using OTT connection 550.

Communication system 500 further includes base station 520 provided in a telecommunication system and comprising hardware 525 enabling it to communicate with host computer 510 and with UE 530. Hardware 525 may include communication interface 526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 500, as well as radio interface 527 for setting up and maintaining at least wireless connection 570 with UE 530 located in a coverage area (not shown in FIGURE 21) served by base station 520. Communication interface 526 may be configured to facilitate connection 560 to host computer 510. Connection 560 may be direct, or it may pass through a core network (not shown in FIGURE 21) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 525 of base station 520 further includes processing circuitry 528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 520 further has software 521 stored internally or accessible via an external connection.

Communication system 500 further includes UE 530 already referred to. Its hardware 535 may include radio interface 537 configured to set up and maintain wireless connection 570 with a base station serving a coverage area in which UE 530 is currently located. Hardware 535 of UE 530 further includes processing circuitry 538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 530 further comprises software 531, which is stored in or accessible by UE 530 and executable by processing circuitry 538. Software 531 includes client application 532. Client application 532 may be operable to provide a service to a human or non-human user via UE 530, with the support of host computer 510. In host computer 510, an executing host application 512 may communicate with the executing client application 532 via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the user, client application 532 may receive request data from host application 512 and provide user data in response to the request data. OTT connection 550 may transfer both the request data and the user data. Client application 532 may interact with the user to generate the user data that it provides.

It is noted that host computer 510, base station 520 and UE 530 illustrated in FIGURE 21 may be similar or identical to host computer 430, one of base stations 412a, 412b, 412c and one of UEs 491, 492 of FIGURE 20, respectively. This is to say, the inner workings of these entities may be as shown in FIGURE 21 and independently, the surrounding network topology may be that of FIGURE 20.

In FIGURE 21, OTT connection 550 has been drawn abstractly to illustrate the communication between host computer 510 and UE 530 via base station 520, 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 UE 530 or from the service provider operating host computer 510, or both. While OTT connection 550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., based on load balancing consideration or reconfiguration of the network).

Wireless connection 570 between UE 530 and base station 520 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 UE 530 using OTT connection 550, in which wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments may improve the signaling overhead and reduce latency, and thereby provide benefits such as reduced user waiting time, better responsiveness and extended battery life.

A measurement procedure may be provided for 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 OTT connection 550 between host computer 510 and UE 530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 550 may be implemented in software 511 and hardware 515 of host computer 510 or in software 531 and hardware 535 of UE 530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 550 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 511, 531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 520, and it may be unknown or imperceptible to base station 520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 510’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 511 and 531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 550 while it monitors propagation times, errors etc.

FIGURE 22 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 20 and 21. For simplicity of the present disclosure, only drawing references to FIGURE 22 will be included in this section.

In step 610, the host computer provides user data. In substep 611 (which may be optional) of step 610, the host computer provides the user data by executing a host application. In step 620, the host computer initiates a transmission carrying the user data to the UE. In step 630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIGURE 23 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 20 and 21. For simplicity of the present disclosure, only drawing references to FIGURE 23 will be included in this section.

In step 710 of the method, the host computer provides user data. In an optional sub step (not shown) the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 730 (which may be optional), the UE receives the user data carried in the transmission. FIGURE 24 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 20 and 21. For simplicity of the present disclosure, only drawing references to FIGURE 24 will be included in this section.

In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally, or alternatively, in step 820, the UE provides user data. In substep 821 (which may be optional) of step 820, the UE provides the user data by executing a client application. In substep 811 (which may be optional) of step 810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 830 (which may be optional), transmission of the user data to the host computer. In step 840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

FIGURE 25 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 20 and 21. For simplicity of the present disclosure, only drawing references to FIGURE 25 will be included in this section.

In step 910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Modifications, additions, or omissions may be made to the systems and apparatuses disclosed herein without departing from the scope of the invention. The components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses may be performed by more, fewer, or other components. Additionally, operations of the systems and apparatuses may be performed using any suitable logic comprising software, hardware, and/or other logic. As used in this document, “each” refers to each member of a set or each member of a subset of a set.

Modifications, additions, or omissions may be made to the methods disclosed herein without departing from the scope of the invention. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.

The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s). lx RTT CDMA2000 1x Radio Transmission Technology

3GPP 3rd Generation Partnership Project

5G 5th Generation

5GC 5th Generation Core

5G-S-TMSI temporary identifier used in NR as a replacement of the S-TMSI in LTE

ABS Almost Blank Subframe

AMF Access Management Function

ARQ Automatic Repeat Request

ASN.1 Abstract Syntax Notation One

AWGN Additive White Gaussian Noise

BCCH Broadcast Control Channel

BCH Broadcast Channel

BWP Bandwidth Part

CA Carrier Aggregation

CC Carrier Component

CCCH SDU Common Control Channel SDU

CDMA Code Division Multiplexing Access

CGI Cell Global Identifier

CIR Channel Impulse Response

CMAS Commercial Mobile Alert System

CN Core Network

CORESET Control Resource Set

Cyclic Prefix

CPICH Common Pilot Channel CPICH Ec/No CPICH Received energy per chip divided by the power density in the band

CRC Cyclic Redundancy Check

CQI Channel Quality information

C-RNTI Cell RNTI

CSI Channel State Information

DCCH Dedicated Control Channel

DCI Downlink Control Information div Notation indicating integer division.

DL Downlink

DM Demodulation

DMRS Demodulation Reference Signal

DRX Discontinuous Reception

DTX Discontinuous Transmission

DTCH Dedicated Traffic Channel

DUT Device Under Test

E-CID Enhanced Cell-ID (positioning method)

E-SMLC Evolved-Serving Mobile Location Centre

ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH enhanced Physical Downlink Control Channel

EPS Evolved Packet System

E-SMLC evolved Serving Mobile Location Center

E-UTRA Evolved UTRA

E-UTRAN Evolved UTRAN

ETWS Earthquake and Tsunami Warning System

FDD Frequency Division Duplex

GERAN GSM EDGE Radio Access Network gNB Base station in NR

GNSS Global Navigation Satellite System

GSM Global System for Mobile communication

HARQ Hybrid Automatic Repeat Request HO Handover

HSPA High Speed Packet Access

HRPD High Rate Packet Data

ID Identity /Identifier

IMSI International Mobile Subscriber Identity

I-RNTI Inactive Radio Network Temporary Identifier

LOS Line of Sight

LPP LTE Positioning Protocol

LTE Long-Term Evolution

MAC Medium Access Control

MBMS Multimedia Broadcast Multicast Services

MBSFN Multimedia Broadcast multicast service Single Frequency Network

MBSFN ABS MBSFN Almost Blank Subframe

MDT Minimization of Drive Tests

MIB Master Information Block

MME Mobility Management Entity mod modulo ms millisecond

MSC Mobile Switching Center

MSI Minimum System Information

NPDCCH Narrowband Physical Downlink Control Channel

NAS Non-Access Stratum

NGC Next Generation Core

NG-RAN Next Generation RAN

NPDCCH Narrowband Physical Downlink Control Channel

NR New Radio

OCNG OFDMA Channel Noise Generator

OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access

OSS Operations Support System

OTDOA Observed Time Difference of Arrival O&M Operation and Maintenance

PBCH Physical Broadcast Channel

P-CCPCH Primary Common Control Physical Channel

PCell Primary Cell

PCFICH Physical Control Format Indicator Channel

PDCCH Physical Downlink Control Channel

PDP Profile Delay Profile

PDSCH Physical Downlink Shared Channel

PF Paging Frame

PGW Packet Gateway

PHICH Physical Hybrid- ARQ Indicator Channel

PLMN Public Land Mobile Network

PMI Precoder Matrix Indicator

PO Paging Occasion

PRACH Physical Random Access Channel

PRB Physical Resource Block

P-RNTI Paging RNTI

PRS Positioning Reference Signal

PSS Primary Synchronization Signal

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RACH Random Access Channel

QAM Quadrature Amplitude Modulation

RAN Radio Access Network

RAT Radio Access Technology

RLM Radio Link Management

RMSI Remaining Minimum System Information

RNA RAN Notification Area

RNC Radio Network Controller

RNTI Radio Network Temporary Identifier

RRC Radio Resource Control

RRM Radio Resource Management RS Reference Signal RSCP Received Signal Code Power RSRP Reference Symbol Received Power OR Reference Signal Received Power

RSRQ Reference Signal Received Quality OR Reference Symbol Received Quality

RS SI Received Signal Strength Indicator RSTD Reference Signal Time Difference SAE System Architecture Evolution SCH Synchronization Channel

SCell Secondary Cell

SDU Service Data Unit

SFN System Frame Number

SGW Serving Gateway

SI System Information

SIB System Information Block

SIB I System Information Block type 1

SNR Signal to Noise Ratio

SON Self Optimized Network ss Synchronization Signal sss Secondary Synchronization Signal S-TMSI SAE-TMSI

TDD Time Division Duplex

TMSI Temporary Mobile Subscriber Identity

TDOA Time Difference of Arrival

TOA Time of Arrival

TSS Tertiary Synchronization Signal

TS Technical Specification

TSG Technical Specification Group

TTI Transmission Time Interval

UE User Equipment

UL Uplink UMTS Universal Mobile Telecommunication System

USIM Universal Subscriber Identity Module

UTDOA Uplink Time Difference of Arrival

UTRA Universal Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access Network

WCDMA Wide CDMA

WG Working Group

WLAN Wide Local Area Network