Patent Description:
Uplink transmissions from different wireless devices served by a base station in a wireless communication network should arrive at the base station time-aligned, e.g., within a defined misalignment tolerance. Time-alignment of the uplink transmissions, among other things, mitigates interference between the uplink transmissions, e.g., inter-subcarrier interference.

In order to ensure that uplink transmissions from wireless devices are received time-aligned, the base station controls the timing of the wireless devices' uplink transmissions. For example, the base station commands a wireless device that is far away from the base station to perform an uplink transmission relatively early in time, so that the uplink transmission will arrive time-aligned with the uplink transmission of a different wireless device that is closer to the base station. A command that controls the amount by which a wireless device is to advance the timing of its uplink transmissions is referred to as a timing advance command.

Challenges exist, though, in controlling the uplink transmission timing for time-aligned reception while also exploiting so-called joint channel estimation. In joint channel estimation, the base station jointly estimates the uplink channel based on measurement of multiple uplink reference signals, e.g., that are bundled together and/or that are received in a bundle of time slots. Such joint channel estimation over a set of multiple uplink transmissions can improve the channel estimation quality, and thereby improve overall link and system performance. Problematically, however, uplink transmission timing adjustment between bundled slots or reference signals jeopardizes the ability of the base station to perform joint channel estimation across those slots or reference signals. An example of prior art is the document: "<NPL>.

<FIG> shows a wireless communication network <NUM> that serves a wireless device <NUM> according to some embodiments. The wireless device <NUM> in this regard is configured to perform uplink transmissions on a carrier or bandwidth part provided by a radio network node <NUM>. Here, a bandwidth part refers to a part of the total cell bandwidth of a cell provided by the radio network node <NUM>.

As shown, the wireless device <NUM> obtains a timing advance adjustment <NUM>. The timing advance adjustment comprises an adjustment to the uplink transmission timing of uplink transmissions on the carrier or bandwidth part, e.g., for purposes of uplink transmission time alignment at the radio network node <NUM>. In some embodiments, for example, the wireless device <NUM> receives, from the radio network node <NUM>, a timing advance command (TAC) <NUM> that commands the wireless device <NUM> to perform this adjustment to the uplink transmission timing of the uplink transmissions on the carrier or bandwidth part.

As shown, the adjustment to the uplink transmission timing is to be applied at a nominal start time T0. The nominal start time T0 may for example be a beginning of an uplink slot that is a certain number of uplink slots after an uplink slot on which a TAC <NUM> was received. For instance, if the TAC <NUM> was received on uplink slot n, the nominal start time T0 may be the beginning of uplink slot n+k+<NUM>.

However, the nominal start time T0 occurs during a window of time W spanned by a certain set <NUM> of uplink transmissions, e.g., Physical Uplink Shared Channel (PUSCH) transmissions. Some of the uplink transmissions in this certain set <NUM> may for instance have been performed before the nominal start time T0 whereas others of the uplink transmissions in the certain set <NUM> may be scheduled to occur after the nominal start time T0. Regardless, the uplink transmissions in the set <NUM> are restricted to having one or more of the same transmission parameters on the carrier or bandwidth part. Such one or more transmissions parameters may for instance comprise parameters that impact phase consistency of the uplink transmissions in the set <NUM>. Indeed, the restriction may be in place so that there is phase consistency among the uplink transmissions in the set <NUM>. In these and other embodiments, for example, the transmission parameter(s) may include one or more of: a modulation order, a resource block (RB) allocation in terms of length and frequency position, transmission power level, and an uplink beam.

In some embodiments, the transmission parameter restriction and resulting phase consistency facilitates joint channel estimation across the uplink transmissions in the set <NUM>. In fact, in one or more embodiments, the uplink transmissions in the set <NUM> are associated with demodulation reference signals (DMRS) in a bundle and/or are transmitted during time slots in a bundle. In one embodiment, for example, the window of time W spanned by the set of uplink transmissions <NUM> includes a bundle of time slots, where the uplink transmissions in the set <NUM> are to be performed during respective ones of the time slots in the bundle. Such slot bundling and/or DMRS bundling for joint channel estimation provides improved channel estimation for reception of the uplink transmissions in the set <NUM>.

In this context, the wireless device <NUM> is to perform an uplink transmission <NUM> on the carrier or bandwidth part at or after the nominal start time T0 as part of, or during the window of time W spanned by, the set of uplink transmissions <NUM>. In some embodiments, the uplink transmission <NUM> is one of the uplink transmissions in the set <NUM>, whereas in other embodiments the uplink transmission <NUM> is not one of the uplink transmissions in the set <NUM>.

The wireless device <NUM> according to embodiments herein correspondingly determines an uplink transmission timing of the uplink transmission <NUM> that is to be performed. Notably, the wireless device <NUM> determines this uplink transmission timing based on one or more rules that specify (i) the uplink transmission timing of the uplink transmission <NUM> is to be adjusted according to the timing advance adjustment <NUM> if one or more first conditions are met; and (ii) the uplink transmission timing of the uplink transmission <NUM> is not to be adjusted according to the timing advance adjustment <NUM> if one or more second conditions are met. Accordingly, rather than unconditionally applying the timing advance (TA) adjustment <NUM> at the nominal start time T0 despite the nominal start time T0 being during the window of time W spanned by the set of uplink transmission <NUM>, and rather than unconditionally avoiding application of the timing advance (TA) adjustment <NUM> at the nominal start time T0 because the nominal start time T0 occurs during the window of time W spanned by the set of uplink transmission <NUM>, the wireless device <NUM> may selectively apply the timing advance adjustment <NUM> to at least some transmissions (e.g., uplink transmission <NUM>) that are to occur during the window of time W under at least some conditions. In doing so, some embodiments facilitate time-aligned reception of at least some uplink transmissions while at the same time preserving the ability of the radio network node <NUM> to perform joint channel estimation despite uplink transmission timing adjustment.

For example, in some embodiments, the one or more first conditions include a first condition that is met if the uplink transmission <NUM> is to be performed during the window of time W spanned by the set of uplink transmissions <NUM> but is not performed as part of the set of uplink transmissions <NUM>, and the one or more second conditions include a second condition that is met if the uplink transmission <NUM> is to be performed as part of the set of uplink transmissions <NUM>.

Alternatively or additionally, where the window of time W spanned by the set of uplink transmissions <NUM> includes a bundle of time slots, the one or more first conditions may include a first condition that is met if the uplink transmission <NUM> is to be performed during the window of time W spanned by the set of uplink transmissions <NUM> but not during a time slot in the bundle, and the one or more second conditions include a second condition that is met if the uplink transmission <NUM> is to be performed during a time slot in the bundle.

Alternatively or additionally, the one or more first conditions may include a first condition that is met if the uplink transmission <NUM> is to be performed on a first physical channel of the carrier or bandwidth part, and the one or more second conditions may include a second condition that is met if the uplink transmission <NUM> is to be performed on a second physical channel of the carrier or bandwidth part. In one such embodiment, uplink transmissions performed on the first physical channel are performed as part of the set of uplink transmissions <NUM>, and uplink transmissions performed on the second physical channel are not performed as part of the set of uplink transmissions <NUM>.

Alternatively or additionally, in some embodiments, the one or more first conditions include a first condition that is met if the uplink transmission <NUM> is to be performed on a first transmit chain of the wireless device <NUM>, and the one or more second conditions include a second condition that is met if the uplink transmission <NUM> is to be performed on a second transmit chain of the wireless device <NUM>.

Alternatively or additionally, in some embodiments, the one or more first conditions include a first condition that is met if an amount by which the wireless device <NUM> is to adjust the uplink transmission timing according to the timing advance adjustment <NUM> is smaller than a threshold amount, and the one or more second conditions include a second condition that is met if the amount by which the wireless device <NUM> is to adjust the uplink transmission timing according to the timing advance adjustment <NUM> is larger than the threshold amount.

Alternatively or additionally, in some embodiments, the one or more first conditions include a first condition that is met if an amount by which the wireless device <NUM> is to adjust the uplink transmission timing according to the timing advance adjustment <NUM> is larger than a threshold amount, and wherein the one or more second conditions include a second condition that is met if the amount by which the wireless device <NUM> is to adjust the uplink transmission timing according to the timing advance adjustment <NUM> is smaller than the threshold amount.

Alternatively or additionally, in some embodiments, the one or more first conditions include a first condition that is met if the wireless device <NUM> is to increase advancement of the uplink transmission timing of uplink transmissions on the carrier or bandwidth, and the one or more second conditions include a second condition that is met if the wireless device is to decrease advancement of the uplink transmission timing of uplink transmissions on the carrier or bandwidth.

Alternatively or additionally, in some embodiments, the one or more first conditions include a first condition that is met if the timing advance adjustment <NUM> is obtained by receiving a timing advance command <NUM> that indicates the timing advance adjustment, and the one or more second conditions include a second condition that is met if the timing advance adjustment is not obtained by receiving a timing advance command that indicates the timing advance adjustment.

Alternatively or additionally, in some embodiments, the one or more first conditions include a first condition that is met if signaling from a wireless communication network <NUM> indicates the uplink transmission timing of the uplink transmission <NUM> is to be adjusted according to the timing advance adjustment, and the one or more second conditions include a second condition that is met if no signaling from the wireless communication network indicates the uplink transmission timing of the uplink transmission is to be adjusted according to the timing advance adjustment.

In view of the embodiments herein, <FIG> depicts a method performed by a wireless device <NUM> in accordance with particular embodiments. The method includes obtaining a timing advance adjustment <NUM> that comprises an adjustment to an uplink transmission timing of uplink transmissions on a carrier or bandwidth part (Block <NUM>). The adjustment to the uplink transmission timing is to apply beginning at a nominal start time T0.

The method also includes determining an uplink transmission timing of an uplink transmission <NUM> that is to be performed on the carrier or bandwidth part at or after the nominal start time T0 as part of, or during a window of time W spanned by, a set of uplink transmissions <NUM> that are restricted to having one or more of the same transmission parameters on the carrier or bandwidth part (Block <NUM>). The uplink transmission timing is determined based on one or more rules. In some embodiments, the one or more rules specify (i) the uplink transmission timing of the uplink transmission <NUM> is to be adjusted according to the timing advance adjustment <NUM> if one or more first conditions are met; and (ii) the uplink transmission timing of the uplink transmission <NUM> is not to be adjusted according to the timing advance adjustment <NUM> if one or more second conditions are met.

The method further comprises performing the uplink transmission <NUM> on the carrier or bandwidth part with the determined uplink transmission timing (Block <NUM>).

Other aspects of the method in <FIG> are enumerated in Group A Embodiments herein.

<FIG> depicts a method performed by a radio network node <NUM> in accordance with other particular embodiments. The method includes transmitting, to a wireless device <NUM>, signaling that configures the wireless device <NUM> to determine, based on one or more rules, an uplink transmission timing of an uplink transmission <NUM> to be performed on a carrier or bandwidth part at or after a nominal start time T0 as part of, or during a window of time W spanned by, a set of uplink transmissions <NUM> that are restricted to having one or more of the same transmission parameters on the carrier or bandwidth part (Block <NUM>). In some embodiments, the one or more rules specify (i) the uplink transmission timing of the uplink transmission <NUM> is to be adjusted according to the timing advance adjustment <NUM> if one or more first conditions are met; and (ii) the uplink transmission timing of the uplink transmission <NUM> is not to be adjusted according to the timing advance adjustment <NUM> if one or more second conditions are met.

The method may also include receiving the uplink transmission <NUM>, e.g., with the determined uplink transmission timing (Block <NUM>).

Other aspects of the method in <FIG> are enumerated in Group B Embodiments herein.

Still other embodiments herein include other methods enumerated in the Group A Embodiments and Group B Embodiments herein. The methods in the Group A Embodiments and Group B Embodiments herein may be implemented separately from or in conjunction with one another.

Embodiments herein also include corresponding apparatuses. Embodiments herein for instance include a wireless device configured to perform any of the steps of any of the embodiments described above for the wireless device.

Embodiments also include a wireless device comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the wireless device. The power supply circuitry is configured to supply power to the wireless device.

Embodiments further include a wireless device comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the wireless device. In some embodiments, the wireless device further comprises communication circuitry.

Embodiments further include a wireless device comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the wireless device is configured to perform any of the steps of any of the embodiments described above for the wireless device.

Embodiments moreover include a user equipment (UE). The UE comprises an antenna configured to send and receive wireless signals. The UE also comprises radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the wireless device. In some embodiments, the UE also comprises an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry. The UE may comprise an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry. The UE may also comprise a battery connected to the processing circuitry and configured to supply power to the UE.

Embodiments herein also include a radio network node configured to perform any of the steps of any of the embodiments described above for the radio network node.

Embodiments also include a radio network node comprising processing circuitry and power supply circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the radio network node. The power supply circuitry is configured to supply power to the radio network node.

Embodiments further include a radio network node comprising processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the radio network node. In some embodiments, the radio network node further comprises communication circuitry.

Embodiments further include a radio network node comprising processing circuitry and memory. The memory contains instructions executable by the processing circuitry whereby the radio network node is configured to perform any of the steps of any of the embodiments described above for the radio network node.

More particularly, the apparatuses described above may perform the methods herein and any other processing by implementing any functional means, modules, units, or circuitry. In one embodiment, for example, the apparatuses comprise respective circuits or circuitry configured to perform the steps shown in the method figures. The circuits or circuitry in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory. For instance, the circuitry 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 may include 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 embodiments that employ memory, the memory stores program code that, when executed by the one or more processors, carries out the techniques described herein.

<FIG> for example illustrates a wireless device <NUM>, e.g., wireless device <NUM>, as implemented in accordance with one or more embodiments. As shown, the wireless device <NUM> includes processing circuitry <NUM> and communication circuitry <NUM>. The communication circuitry <NUM> (e.g., radio circuitry) is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. Such communication may occur via one or more antennas that are either internal or external to the wireless device <NUM>. The processing circuitry <NUM> is configured to perform processing described above, e.g., in <FIG>, such as by executing instructions stored in memory <NUM>. The processing circuitry <NUM> in this regard may implement certain functional means, units, or modules.

<FIG> illustrates a radio network node <NUM>, e.g., radio network node <NUM>, as implemented in accordance with one or more embodiments. As shown, the radio network node <NUM> includes processing circuitry <NUM> and communication circuitry <NUM>. The communication circuitry <NUM> is configured to transmit and/or receive information to and/or from one or more other nodes, e.g., via any communication technology. The processing circuitry <NUM> is configured to perform processing described above, e.g., in <FIG>, such as by executing instructions stored in memory <NUM>. The processing circuitry <NUM> in this regard may implement certain functional means, units, or modules.

A computer program comprises instructions which, when executed on at least one processor of an apparatus, cause the apparatus to carry out any of the respective processing described above. A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

Some embodiments herein are applicable in the context described below.

It is important that signals from different UEs are time-aligned when received by the base station (BS). For example, received PUSCH OFDM symbols from different UEs should start and end simultaneously within a misalignment tolerance that is (significantly) less than the duration of the OFDM cyclic prefix (CP).

One reason for this being important is that if the misalignment is larger than the CP, there will typically be inter-subcarrier interference, i.e., nominally frequency-separated signals can interfere with each other. Also, misalignment could lead to an interference level that varies throughout the duration of an OFDM symbol. Such variation is challenging from a receiver algorithm perspective and could require increased receiver computational complexity as well as ultimately degrade performance. Furthermore, even without interference, the timing misalignment would mean that the BS would not be able to use the same DFT for all users in the cell, which would again lead to increased receiver computational complexity.

In order to ensure that signals are received time-aligned, it is not enough that UEs transmit at the same time; due to differences in propagation delays between different UEs depending on how far from the BS they are located, adjustments are necessary. This is illustrated in parts a) and b) of <FIG> schematically shows a) exemplary Tx and Rx times for UEs with different distance to the BS for the case of b) no timing advance or c) appropriate timing advance. "Packet A" and "Packet B" could e.g., represent one transmitted slot. A UE that is far from the BS must be instructed to transmit a certain time in advance in order for the signal to reach the BS at the right time. This functionality is in NR referred to as timing advance (TA) and is described for example in 3GPP TS <NUM> and 3GPP TS <NUM>, and is illustrated in part c) of <FIG>.

According to 3GPP TS <NUM> rev <NUM>. <NUM>, the TA can be adjusted in multiples of <NUM>·<NUM>·Tc/<NUM>µ , where Tc = <NUM>/(Δfmax ·Nf), Δfmax = <NUM> · <NUM><NUM> Hz and Nf = <NUM>. In other cases than random access response, a timing advance command (3GPP TS <NUM>), TA , for a timing advance group (TAG) indicates adjustment of a current NTA value, NTA_old , to the new NTA value, NTA_new , by index values of TA = <NUM>, <NUM>, <NUM>,. , <NUM>, where for a SCS of <NUM>µ ·<NUM>, NTA_new=NTA_old+(TA -<NUM>)·<NUM>·<NUM>/<NUM>µ. Adjustment of an NTA value by a positive or a negative amount indicates advancing or delaying the uplink (UL) transmission timing for the TAG by a corresponding amount, respectively.

The TA granularity for <NUM> subcarrier spacing is about <NUM> and for higher subcarrier spacings scales inversely with the subcarrier spacing. In the present disclosure, we for brevity define ΔT<NUM> = <NUM> · <NUM> · Tc/<NUM>µ. In the case of random access response, the TA can be set to any value in the range <NUM>×ΔT<NUM>, <NUM>×ΔT<NUM>, <NUM>×ΔT<NUM>,. , <NUM>×ΔT<NUM>. In other situations, relative TA adjustments in the range -<NUM>×ΔT<NUM>, -<NUM>×ΔT<NUM>,. <NUM>×ΔT<NUM>,. +<NUM>×ΔT<NUM>, +<NUM>×ΔT<NUM> can be set. The maximum TA adjustment is <NUM>, about one fourth of an OFDM symbol length.

According to the following table from 3GPP TS <NUM> rev <NUM>. <NUM>, different cyclic prefixes are supported.

Cyclic prefix (CP) length is denoted by <MAT>, where <MAT> <MAT>.

The constant κ = Ts/Tc = <NUM>. We denote x · ΔT<NUM> as relative TA adjustment. x = TA - <NUM>, where TA= <NUM>, <NUM>, <NUM>,. , <NUM> is index value in TAC. The UE applies TA adjustment before its UL transmission, which may happen at any symbol in a slot. In order for the relative TA adjustment x · ΔT<NUM> to be within CP range, x should meet below requirement: <MAT> where |x| is the absolute value of x. That means the maximum absolute value of relative TA adjustment <NUM>×ΔT<NUM> doesn't exceed an extended CP. But for normal CP, take the example of <NUM>, i.e. µ =<NUM>. If the value x derived from the TA command is between [-<NUM>, +<NUM>], the TA adjustment is within CP length for the first symbol of the slot. If the value is in the range [-<NUM>, -<NUM>] or [<NUM>, <NUM>], the TA is larger than the CP.

The timing advance is in NR Rel-<NUM>/<NUM> signaled using a TA Medium Access Control (MAC) Control Element (CE) as described in section <NUM>. <NUM> of 3GPP TS <NUM>. One octet is used for signaling as shown in <FIG> schematically shows an exemplary Timing Advance Command MAC CE, which is a figure from 3GPP TS <NUM> V16. Six bits are used to indicate one of the above-mentioned <NUM> possible relative TA adjustments. Two bits are used to indicate a timing advance group (TAG) identity (ID). TAGs can be useful to specify the same TA for multiple cells, e.g., for a multi-carrier system where the same UE is served by the same BS in multiple cells operating on the different carrier frequencies.

When the UE receives a TA adjustment command (TAC), it should in Rel-<NUM>/<NUM> of NR update the TA essentially immediately, with just a short delay to allow for processing time, etc. More precisely, according to 3GPP TS <NUM> rev <NUM>. <NUM>, if the UE receives a TA command in slot n, the new TA should apply from the beginning of the uplink slot n + k + <NUM>, where <MAT>, NT,<NUM> is a time duration in msec of N<NUM> symbols corresponding to a PDSCH processing time for UE processing capability <NUM> when additional PDSCH DM-RS is configured, NT,<NUM> is a time duration in msec of N<NUM> symbols corresponding to a PUSCH preparation time for UE processing capability <NUM>, NTA,max is the maximum timing advance value in msec that can be provided by a TA command field of <NUM> bits, <MAT> is the number of slots per subframe, and Tsf is the subframe duration of <NUM> msec. N<NUM> and N<NUM> are determined with respect to the minimum SCS among the SCSs of all configured UL BWPs for all uplink carriers in the TAG and of all configured downlink (DL) BWPs for the corresponding downlink carriers.

If the received downlink timing changes and is not compensated or is only partly compensated by the uplink timing adjustment without timing advance command as described in TS <NUM>, the UE changes NTA accordingly.

In 3GPP TS <NUM> rev <NUM>. <NUM>, the downlink timing is defined as the time when the first detected path (in time) of the corresponding downlink frame is received from the reference cell.

UE transmission timing is adjusted using gradual timing adjustments described in section <NUM>. <NUM> of 3GPP TS <NUM>. When it is not the first transmission in a DRX cycle or there is no DRX cycle, and when it is the transmission for PUCCH, PUSCH and SRS transmission, the UE shall be capable of changing the transmission timing according to the received downlink frame of the reference cell except when the timing advance in section <NUM> of 3GPP TS <NUM> is applied.

According to section <NUM>. <NUM> of 3GPP TS <NUM>, requirements in this section apply regardless of whether the reference cell is on a carrier frequency subject to Clear Channel Assessment (CCA) or not.

When the transmission timing error between the UE and the reference timing exceeds ±Te then the UE is required to adjust its timing to within ±Te.

The reference timing shall be (NTA + NTA offset)×Tc before the downlink timing of the reference cell. All adjustments made to the UE uplink timing shall follow these rules:.

where the maximum autonomous time adjustment step Tq and the aggregate adjustment rate Tp are specified in Table <NUM>. <NUM>-<NUM>.

UE shall adjust the timing of its uplink transmission timing at time slot n+ k+<NUM> for a timing advance command received in time slot n, and the value of k is defined in clause <NUM> in 3GPP TS <NUM>. The same requirement applies also when the UE is not able to transmit a configured uplink transmission due to the channel assessment procedure.

3GPP TS <NUM> rev <NUM>. <NUM> specifies that uplink frame number i for transmission from the UE shall start TTA = (NTA + NTA,offset)Tc before the start of the corresponding downlink frame at the UE where NTA,offset is given by 3GPP TS <NUM>. <FIG> reproduces <FIG>. <NUM>-<NUM> from 3GPP TS <NUM> rev <NUM>. <NUM>, which schematically shows an exemplary Uplink-downlink timing relation.

The N_TA-Offset to be applied for all uplink transmissions on this serving cell. If the field is absent, the UE applies the value defined for the duplex mode and frequency range of this serving cell. See TS <NUM>, table <NUM>. <NUM>-<NUM>.

-- ASN1START
-- TAG-TAG-CONFIG-START
TAG-Config ::= SEQUENCE {
tag-ToReleaseList SEQUENCE (SIZE (<NUM>. maxNrofTAGs)) OF TAG-Id
OPTIONAL, -- Need N
tag-ToAddModList SEQUENCE (SIZE (<NUM>. maxNrofTAGs)) OF TAG
OPTIONAL -- Need N
}
TAG ::= SEQUENCE {
tag-Id TAG-Id,
timeAlignmentTimer TimeAlignmentTimer,. }
TAG-Id ::= INTEGER (<NUM>. maxNrofTAGs-<NUM>)
TimeAlignmentTimer ::= ENUMERATED {ms500, ms750, ms1280, ms1920,
ms2560, ms5120, ms10240, infinity}
-- TAG-TAG-CONFIG-STOP
-- ASN1STOP
timeAlignmentTimer
Value in ms of the timeAlignmentTimer for TAG with ID tag-Id, as specified in
TS <NUM>.

In 3GPP TS <NUM> rev. <NUM>, it is specified that RRC configures the following parameters for the maintenance of UL time alignment:.

According to 3GPP TS <NUM> rev. <NUM>, a Timing Advance Group (TAG) is a group of Serving Cells that is configured by RRC and that, for the cells with a UL configured, uses the same timing reference cell and the same Timing Advance value. A Timing Advance Group containing the SpCell of a MAC entity is referred to as Primary Timing Advance Group (PTAG), whereas the term Secondary Timing Advance Group (STAG) refers to other TAGs.

Slot aggregation for the Physical Uplink Shared Channel (PUSCH) is supported in Rel-<NUM> and was renamed to PUSCH Repetition Type A in Rel-<NUM>. The name PUSCH repetition Type A is used even if there is only a single repetition, i.e., no slot aggregation. <NUM>, a PUSCH transmission that would overlap with DL symbols is not transmitted.

<NUM>, the number of repetitions is semi-statically configured by RRC parameter pusch-AggregationFactor. At most <NUM> repetitions are supported.

A new repetition format PUSCH repetition Type B is supported in Rel-<NUM>, which allows back-to-back repetition of PUSCH transmissions. The biggest difference of Type B from Type A is that repetition Type A only allows a single repetition in each slot, with each repetition occupying the same symbols. Using this format with a PUSCH length shorter than <NUM> introduces gaps between repetitions, increasing the overall latency. The other change compared to Rel. <NUM> is how the number of repetitions is signaled. <NUM>, the number of repetitions is semi-statically configured, while in Rel. <NUM> the number of repetitions can be indicated dynamically in DCI. This applies both to dynamic grants and configured grants type <NUM>.

In NR Rel-<NUM>/<NUM>, one UL TB is confined to the UL symbols in a slot. To support high data rate, multiple Physical Resource Blocks (PRBs) in a slot can be used for the transmission of a large TB and the multiple PRBs share UE transmission power. Transport block (TB) processing over multiple slots may be possible for coverage enhancement of PUSCH in NR Rel-<NUM>. Multi-slot TB extends the time domain resource for the transmission of a TB across slot border to increase total power for transmission of a TB compared to TB transmission in a single slot. Multi-slot TB also reduces cyclic redundancy check (CRC) overhead by reducing the number of CRCs in a given number of slots compared to the PUSCH transmissions at the same data rate with separate TBs.

In an NR gNB, the reception of the Physical Uplink Shared Channel (PUSCH) on a high level typically consists of two steps: (i) estimation of the physical channel based on measurements of reference symbols (e.g., DMRS) and (ii) equalize, demodulate, and decode the signal based on the so estimated channel.

In existing releases of NR (Rel-<NUM>/<NUM>), the gNB performs the channel estimation (or at least the channel filtering part of it) on each slot individually, since different slots may have different random phase offsets, timing differences, and/or other differences that may make cross-slot channel filtering impossible.

In the NR coverage enhancements work item (WI) for Rel-<NUM>, it has been agreed to support PUSCH cross-slot channel estimation, or joint channel estimation as it is called in 3GPP; the two terms will mostly be treated as synonyms herein. Joint channel estimation imposes some constraints on the UE regarding phase changes etc., between slots in order to allow the gNB to estimate the channel jointly for multiple slots. Such joint processing over multiple slots can improve the channel estimation quality, and thereby improve overall link and system performance.

The description herein refers to a set of slots intended for joint channel estimation as a set of bundled slots or a slot bundle. A set of bundled slots would typically be a few consecutive slots in which the UE transmits a physical channel, e.g., all slots of a repetitions set (see section <NUM> of 3GPP TS <NUM> for more information on repetition), all slots of a single transport block (TB) transmission, or a predetermined set of slots identified by their location in time during which the UE must maintain relative phase among transmissions in the slots. In more general cases, a slot bundle comprises those slots over which a UE is to maintain the relative phase between transmissions in the different slots. Such cases may for example include where the UE does not transmit, but also does not receive a downlink transmission, and so may keep its Tx chain active without degrading its downlink reception with self-interference.

Mechanism(s) are desired to enable joint channel estimation over multiple PUSCH transmissions, based on conditions to keep power consistency and phase continuity. As noted above, cross-slot channel estimation would involve certain constraints on timing changes in the UE's transmissions between slots that are jointly processed.

One approach to constraining timing changes between slots that are jointly processed would be to avoid, cancel, or postpone changes during a set of slots with joint channel estimation, so as to favor joint channel estimation over timing adjustment. Another approach would be to proceed with the timing changes at the expense of joint channel estimation, i.e., to effectively terminate joint channel estimation.

More particularly in this regard, the UE heretofore applies a timing advance (TA) update at the start of slot n+k+<NUM> after receiving a timing advance command in slot n. In NR Rel-<NUM> such a TA change may occur in the middle of a set of bundled slots, which are configured by a gNB or predetermined for joint channel estimation. As illustrated in <FIG> which schematically shows exemplary TA changes in the midst of PUSCH transmission in bundled slots, bundled slots from a UE can be used for transmission of PUSCH repetitions and/or a TB over multiple slots. A change of TA in the middle of the bundled slots can degrade cross-slot channel estimation.

In order to preserve cross-slot channel estimation, then, one approach would be to have the UE avoid TA updates during a set of bundled slots. The UE in this approach, for example, could apply the update after the set of bundled slots (e.g., either immediately after the transmission finished, or just before the UL transmissions in any slot following the last bundled slot, which might be different if the change in TA would cause the two slots to overlap in principle). An example of application after the bundled slots is illustrated in <FIG> schematically shows that a TA command received during a set of bundled slots is applied once the set of bundled slots is ended.

However, such avoidance may cause issues of inter-subcarrier interference and UE-UE interference. Indeed, as described above, for normal CP case, if the TA adjustment x*ΔT<NUM> derived from TA command doesn't meet the requirement below, not adjusting TA accordingly will cause inter-subcarrier interference, i.e., nominally frequency-separated signals can interfere with each other.

In the configuration of DDSUUDDSUU, for example, if the UE moves around a street corner, it could suddenly have a strong line-of-sight (LOS) path to the BS with much shorter propagation delay than it previously had, and the TA should be enlarged. Keeping a smaller TA will make the UL transmission extend into the next DL slot (if UE uses the last symbol in the UL slot) and gNB will not be able to receive the last several symbols of the UL slot, since the gNB has started DL transmission. The UE also causes UE-UE interference, as illustrated in <FIG> schematically shows exemplary interference caused by no TA adjustment. If the UE then avoids updating the TA to compensate for that, it could for a period of time cause severe interference to other users, who are receiving DL data, due to the timing misalignment at the receiver. When the TA adjustment error exceeds CP length, not updating TA causes inter-subcarrier interference unless there is no other UE scheduled in the slot.

Note that if the number of bundled slots exceeds the number of HARQ re-transmissions used in the system (and the HARQ feedback delay is less than the time interval between consecutive UL slots, which may be the case in TDD), the interference from the wrong TA setting could affect all transmission attempts of another user and hence potentially lead to need for re-transmissions by higher layers, which is costly.

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, some embodiments define certain rules for when the UE should or should not update its TA setting in order to avoid that the UE unnecessarily disrupts cross-slot channel estimation or causes other issues. Generally, in certain situations, the UE should update the TA only after the set of bundled slots. However, in other situations, it is more beneficial to update the TA already before the end of a set of bundled slots and to have the gNB take this TA change into account when receiving the bundled slots.

Certain embodiments may provide one or more of the following technical advantage(s). The network can signal TA to the UE at any time without risking that joint channel estimation over multiple slots fails and without risking issues from delayed application of an updated TA.

More specifically, the description herein for brevity refers to a set of slots intended or usable for joint channel estimation as a set of bundled slots or a slot bundle. The bundle could be formally specified as a "bundle" (or similar, e.g., as a time window, slot group, etc.), but need not necessarily be so. For example, "intended" could mean that the gNB plans to use the slots for joint estimation without the UE being aware of that, and "usable" could more generally mean that the system is configured in such a way (e.g., by signaling to a UE) that the slots will be usable for joint estimation by the gNB (again possibly without the UE being aware of this), or usable with less receiver computational complexity than would otherwise be needed.

A set of bundled slots would typically be a few consecutive slots in which the UE transmits a physical channel, e.g., all slots of a repetitions set (see section <NUM> of 3GPP TS <NUM> for more information on repetition), all slots of a single TB transmission, or a predetermined set of slots identified by their location in time during which the UE must maintain relative phase among transmissions in the slots. In more general cases, a slot bundle comprises those slots over which a UE can maintain the relative phase between transmissions in the different slots. Such cases may for example include where the UE does not transmit, but also does not receive a downlink transmission, and so may keep its Tx chain active without degrading its downlink reception with self-interference.

In this context, some embodiments herein introduce rules for when the UE should apply the TA update. That is, rather than the UE always and unconditionally avoiding TA updates during a set of bundled slots, the UE may selectively apply or not apply TA updates during such a set of bundled slots, e.g., depending on one or more conditions. Some embodiments therefore generally include methods for a UE to determine when it should or should not apply a TA, e.g., when a set of bundled slots is configured by gNB or predetermined for joint channel estimation, which can be used for transmission of PUSCH repetitions and/or a TB across multiple slots.

Embodiment <NUM>-<NUM>: Apply a new TA on slots not for a PUSCH bundle, and keep using the old TA for all slots for a PUSCH bundle. For example, for a PUCCH transmitted in a slot that is between two PUSCH slots that are in a PUSCH bundle, a new TA can be used for the PUCCH slot, but the old TA should be used for the <NUM> slots which are assumed to be bundled for PUSCH transmission.

Generally, then, according to Embodiment <NUM>-<NUM>, the UE can apply the updated TA to any transmissions that are not part of a set of bundled slots but transmitted in the same period of time (i.e., a transmission anywhere between the start of the first slot of a bundle and the end of the last slot of the bundle). For example, control channels or other PUSCH transmissions that do not use bundling, and that are transmitted in slots between the bundled slots, could be allowed to use the new TA even though the old TA persists for the slots that are part of an ongoing bundle.

The support for different TA timing could be used in UEs that have multiple transmit chains that can operate on the same carrier frequency. In such cases, the different transmit chains could transmit with different timing advances. In such UEs, it can be possible for the UE to select on which Tx chain it will transmit a given physical channel in a transparent way to the gNB. This is possible in NR because each physical channel transmitted from the UE has an associated antenna port and a corresponding DMRS that are generally independent of other physical channels. Physical channels transmitted on different antenna ports can be on different Tx chains. Therefore, in some embodiments, the UE selects a Tx chain to transmit a physical on according to whether a timing advance is to be applied to the Tx chain. If the physical channel is to be transmitted in a set of bundled slots, the channel is transmitted on a Tx chain that does not have the timing advance applied during the bundled slots, otherwise the UE transmits the physical channel on either a Tx chain that has the timing advance applied or on a Tx chain that does not have the timing advance applied.

Embodiment <NUM>-<NUM>: Apply a new TA on physical channels according to whether they are configured for bundling, where if the TA is to be updated for bundled slots, and if the channel is not configured for bundling, the TA is updated. However, if the channel is instead configured for bundling, the TA is updated after the bundled slots.

Generally, then, according to Embodiment <NUM>-<NUM>, a UE is configured to use slot bundling for a selected physical channel or cell on a bandwidth part.

Indeed, in some cases, it may not be necessary for the UE to maintain relative phase among slots (i.e., configured for slot bundling) for all physical channels transmitted on a given carrier. For example, it could be configured to maintain relative phase for its PUSCH and PUCCH transmissions independently. Such operations can be supported by the UE that has multiple Tx chains discussed above. Also, a gNB may not need the UE to maintain relative phase for a given physical channel, e.g., if it is at a high enough SINR such that the channel can estimated with sufficient accuracy, or if the gNB can estimate the relative phase between slots and to then use the multiple slots for enhanced channel estimation without the UE's assistance. Therefore, in some embodiments, a UE is configured to use slot bundling for a selected physical channel on a cell or bandwidth part. If the UE receives a TAC to apply to the carrier or bandwidth part, it will update the timing for a given physical channel according to if it is configured for slot bundling for that physical channel. If it is configured for slot bundling on the channel, it will not expect, and may choose to not adjust, a TAC that would cause it to adjust the TA of transmissions occurring within a slot bundle. If it is not configured for slot bundling on the channel, it will use the Rel-<NUM>/<NUM> procedure for adjusting TA. In a similar embodiment, if the UE is configured for slot bundling on the channel and receives a TAC that would cause it to adjust the TA on transmissions occurring within a slot bundle, it adjusts the TA in a slot after the last of the bundled slots.

When configured with bundled slots, if the relative TA adjustment signaled in TAC is small, the UE can either apply the TA causing a small phase non-consistency which the gNB can correct before joint channel estimation, or maintain relative phase by not applying TA update to assist the gNB joint channel estimation, as illustrated in <FIG> schematically shows an exemplary UE behavior on TA update according to the threshold of gNB phase correction.

In other embodiments herein, referred to as Embodiments <NUM>-x, the UE applies a new TA or not based on to what extent a TA drift is detected.

Embodiment <NUM>-<NUM>: The UE receives a TAC and the slot in which the UE is expected to apply the TA update is among the bundled slots. If the absolute value of x, based on x = TA - <NUM>, where the TA is signaled in TAC, is less than a predetermined or configured threshold, the UE applies the TA update as required.

We denote x · ΔT<NUM> as relative TA adjustment. x = TA - <NUM>, where TA= <NUM>, <NUM>, <NUM>,. , <NUM> is index value indicated in TAC. x derived from TA command is in the range of [-<NUM>, <NUM>]. The relative TA adjustment can be larger than a normal CP length and cause inter-subcarrier interference. A UE needs to determine if such interference may happen if it doesn't apply the TA update as indicated in TAC.

Embodiment <NUM>-<NUM>: With normal CP, for a timing advance command received on uplink slot n, if the UE transmits PUSCH in bundled slots, which overlap with the corresponding adjustment of the uplink transmission timing in uplink slot n+k+<NUM>, the UE can be configured/predetermined to use below method. If the value x indicated in a TA command doesn't meet the requirement, <MAT> where µ is defined in section <NUM> in 3GPP TS <NUM> and |x| is the absolute value of x, the UE adjusts the TA command in slot n+k+<NUM> accordingly and is not required to maintain relative phase among PUSCH transmissions in a bundle. The gNB may therefore be unable to do joint channel estimation for the UE across slots before and after the beginning of slot n+k+<NUM>.

Embodiment <NUM>-<NUM>: The TA update is applied at one point in time if it is an increase in TA, and another point in time if it is a decrease in TA. For example, a rule may be that the TA is applied according to Rel-<NUM>/<NUM> specification in case it is an increase, and at a later point in time if it is a decrease, or vice versa. The time of application may also more generally depend on how large the TA change is. For example, a TA change that is larger than a certain threshold (in either direction or in some specific direction) is applied rather soon (e.g., according to Rel-<NUM>/<NUM>) while a smaller TA change is applied only after the completion of the slot bundle (or before the first slot or symbol after the slot bundle).

In the general case, there may be two different thresholds, one which determines how large a TA decrease has to be in order to trigger an early update, and one which determines how large a TA increase has to be in order to trigger an early update.

One example of why it could be beneficial to have different thresholds for increase vs decrease of TA: A transmission of an OFDM symbol consists of a CP of duration T_CP followed by the actual OFDM symbol of duration T_OFDM. The receiver DFT window, which has duration T_OFDM, could in an environment without time dispersion in theory be aligned to start at any time instance from the beginning of the CP until the beginning of the actual OFDM symbol. However, if the physical channel has time dispersion with a distance from first to last channel tap of about T_CP, the receiver should in order to avoid inter-symbol interference from the preceding OFDM symbol preferably align its DFT window so that it starts late in the CP, or right at the start of the actual OFDM symbol. Assuming such alignment of the receiver DFT window, and considering that physical channels typically have the strongest taps in the beginning of the channel profile and mostly very weak taps towards the end, it is clear that it may be more problematic if a UE transmits a little too early than if it transmits a little too late: If it transmits a little too early, the first CP of the slot will cause interference by having its first (and presumably strong) channel tap(s) being captured by the DFT window for the last symbol of the previous slot, while if it transmits a little too late, it will only cause interference by having its last (and presumably weak) channel tap(s) being captured by the DFT window for the first symbol in the following slot. Hence, application of a TA may be more important to perform urgently for small/moderate TA changes if the TA is decreased (which happens if the UE is transmitting too early) than if it is increased (which happens if the UE is transmitting too late). Therefore, it could be beneficial to have a smaller threshold for an decrease in TA.

Embodiment <NUM>: Shorten a slot on which a new TA is expected to be applied but still the old TA is applied for cross-slot channel estimation. For example, in some embodiments, a slot that should have an updated TA according to Rel-<NUM>/<NUM> is transmitted with a non-updated TA but shortened (at the beginning or the end). The shortening could be adjusted to match the TA change so that undesired interference between symbols or slots between different UEs does not risk arising at the gNB receiver, i.e., if the TA is enlarged (earlier transmission) the slots would be shortened (punctured) at the end and if the TA is reduced (later transmission) the slots would be shortened (punctured) at the beginning. Alternatively to shortening to match the TA change, an entire OFDM symbol or even an entire slot could be not transmitted by the UE. Note that if a TA command is received early in the bundle, several slots may be affected by such shortening or omissions.

Embodiment <NUM>-<NUM>: In case one TAG has multiple serving cells, apply the TA update at different points in time for the different serving cells outside of the slot bundle boundaries in the different serving cells. Or, if there are multiple carriers in a TAG, the UE may apply the TA update at different points in time for the different carriers depending on the slot bundle boundaries on the different carriers. Note that if the slot bundles on different carriers do not have boundaries coinciding in time, just requiring the UE not to apply a timing update during a slot bundle could otherwise lead to the TA application being postponed for a very long time, see <FIG> schematically shows an exemplary situation with overlapping bundles on different carriers in a TAG, implying that there is no point in time where the TA update can be applied without disrupting joint estimation in the receiver. In this case it could, for example, be specified or signaled that the UE should apply the update in between bundles on each carrier separately (thus for a period of time use different TA on different carriers), or it could be specified or signaled that the UE should apply the update in between bundles on one specific carrier and at the same time on the other carriers, thus preventing efficient joint channel estimation in one slot bundle on the other carriers.

In a sub-embodiment of embodiment <NUM>-<NUM>, when a new TA is applied at different time points on different carriers of a TAG, the TA timer of the TAG should be started/restarted in one or more of the following methods:.

In another sub-embodiment of embodiment <NUM>-<NUM>, different TA timers are introduced for different serving cells applying a new TA at different time points for one TAG.

Embodiment <NUM>-<NUM>: In an alternative embodiment where multiple carriers are configured within a TAG, a UE transmits with a single TA for all carriers within the TAG and is configured such that the slot bundle occurs in the same slots on all carriers in the TAG. Because the slot bundle is the same on all carriers of the TAG, if a TA update is outside of the slot bundle on one carrier, it will be outside on all carriers, and therefore avoid the conflict illustrated in <FIG> in embodiment <NUM>-<NUM>. Generally, then, according to this embodiment, the UE is configured such that slots to be bundled occur at the same time on all carriers that are in a TAG.

Embodiment <NUM>: It's still up to following factors to determine whether a TA should be applied for the PUSCH transmission in a set of slots, wherein the set of slots can be a set of PUSCH repetitions or a single TB transmission over multiple slots or a combination of both cases. And UEs will not expect the slots with different TA values applied are treated as a bundle for joint channel estimation.

If the UE receives a TAC to be applied in a set of bundled slots, and the timer is running, then the UE is not required to maintain relative phase among slots of the bundle, and the UE applies the TAC on a portion of the bundled slots.

Generally, then this embodiment applies the TA still based on legacy behaviors, but the UE will not expect the slots with different TA values applied can be used for joint channel estimation, and the UE is not required to maintain relative phase among bundled slots.

Embodiment <NUM>: The gNB can choose to apply (or not apply) joint channel estimation on a PUSCH bundle when a timing adjustment command (TAC) that would apply to one or more of the slots in the PUSCH bundle is not successfully decoded. For example, when a new TAC is transmitted from gNB but the UE fails to decode the PDSCH carrying the TAC, UE will not be able to apply a new TA adjusted by the new TAC not successfully received. The UE not applying the new TA can be known by the gNB as it doesn't receive ACK for PDSCH. One or more methods can be applied by the gNB:.

For example, in a FDD network a UE is scheduled to transmit PUSCH over consecutive slots, which are divided into two bundles/time-domain windows. The slots in a bundle are for joint channel estimation. Slots in different bundles are not supposed to be jointly estimated. The gNB sends TAC to indicate to the UE to apply a new TA at the beginning of the second bundle. If the UE doesn't receive/decode the TAC, the UE doesn't send ACK for PDSCH, and the UE keeps the same TA across the slots in two bundles. The gNB can do joint channel estimation over the slots in two bundles as if TAC is not sent or do joint channel estimation only over slots in one bundle.

Embodiment <NUM>: For TBoMS transmission, the same TA is applied for one TB transmission over multiple slots, but different TAs can be allowed for the repetitions of a TB transmitted over multiple slots. That is, TA can be updated on a repetition of TBoMS but not within slots of a single TBoMS transmission.

Embodiment <NUM>: Timing corrections determined by the UE from errors in downlink timing are deferred until after bundled slots. For example, the UE applies a new TA within a bundle if it was signaled by the gNB, but not allowed to apply the new TA within a bundle if it is due to detected errors in DL timing. In one sub-embodiment, if the DL timing error is sufficiently small, for example no larger than Tp or Tq defined in 3GPP TS <NUM> rev. <NUM> Table <NUM>. <NUM>-<NUM>, a prior value of timing advance is used during the bundle, and DL timing corrections are used for transmissions after the bundle. If there is both a signaled TA update and a TA update caused by detected downlink timing errors that are supposed to be (or could be) applied simultaneously, the UE should apply only the signaled part.

Embodiment <NUM>: In some embodiments, the signaling of a TA update (TA message) from the gNB to the UE includes an indication of when the TA should be applied. The indication could, e.g., be an indication of the earliest time at which the TA should be applied, or it could just be a binary indication (e.g. a single bit) that indicates whether the TA update should be applied as soon as possible (e.g. according to Rel-<NUM>/<NUM> rules) or only after the end of any bundle with ongoing transmission at the time when the update should have been made according to Rel-<NUM>/<NUM> rules. The signaling could also or alternatively be used to determine to which extent preconfigured/predetermined thresholds are to be respected or not.

Generally, then, some embodiments herein exploit rules for when a TA update should or should not be applied, in particular rules for when the update should be applied at the point in time prescribed by Rel-<NUM>/<NUM> of NR and when not.

In view of the modifications and variations above, some embodiments herein include those enumerated below.

<FIG> shows an example of a communication system <NUM> in accordance with some embodiments.

In the example, the communication system <NUM> includes a telecommunication network <NUM> that includes an access network <NUM>, such as a radio access network (RAN), and a core network <NUM>, which includes one or more core network nodes <NUM>. The access network <NUM> includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes <NUM>), or any other similar <NUM>rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes <NUM> facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs <NUM>) to the core network <NUM> over one or more wireless connections.

In some examples, the UEs <NUM> are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network <NUM> on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network <NUM>. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

In the example, the hub <NUM> communicates with the access network <NUM> to facilitate indirect communication between one or more UEs (e.g., UE 112c and/or 112d) and network nodes (e.g., network node 110b). In some examples, the hub <NUM> may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub <NUM> may be a broadband router enabling access to the core network <NUM> for the UEs. As another example, the hub <NUM> may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes <NUM>, or by executable code, script, process, or other instructions in the hub <NUM>. As another example, the hub <NUM> may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub <NUM> may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub <NUM> may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub <NUM> then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub <NUM> acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.

The hub <NUM> may have a constant/persistent or intermittent connection to the network node 110b. The hub <NUM> may also allow for a different communication scheme and/or schedule between the hub <NUM> and UEs (e.g., UE 112c and/or 112d), and between the hub <NUM> and the core network <NUM>. In other examples, the hub <NUM> is connected to the core network <NUM> and/or one or more UEs via a wired connection. Moreover, the hub <NUM> may be configured to connect to an M2M service provider over the access network <NUM> and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes <NUM> while still connected via the hub <NUM> via a wired or wireless connection. In some embodiments, the hub <NUM> may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 110b. In other embodiments, the hub <NUM> may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

<FIG> shows a UE <NUM> in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE <NUM> shown in <FIG>.

In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone's speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone's speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

<FIG> shows a network node <NUM> in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.

The host application programs <NUM> may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.

Applications <NUM> (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

Hardware <NUM> includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers <NUM> (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs <NUM>), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer <NUM> may present a virtual operating platform that appears like networking hardware to the VMs <NUM>.

Hardware <NUM> may be implemented in a standalone network node with generic or specific components. Hardware <NUM> may implement some functions via virtualization. Alternatively, hardware <NUM> may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration <NUM>, which, among others, oversees lifecycle management of applications <NUM>. In some embodiments, hardware <NUM> is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes 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 provided with the use of a control system <NUM> which may alternatively be used for communication between hardware nodes and radio units.

<FIG> shows a communication diagram of a host <NUM> communicating via a network node <NUM> with a UE <NUM> over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 112a of <FIG> and/or UE <NUM> of <FIG>), network node (such as network node 110a of <FIG> and/or network node <NUM> of <FIG>), and host (such as host <NUM> of <FIG> and/or host <NUM> of <FIG>) discussed in the preceding paragraphs will now be described with reference to <FIG>.

One or more of the various embodiments improve the performance of OTT services provided to the UE <NUM> using the OTT connection <NUM>, in which the wireless connection <NUM> forms the last segment.

In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection <NUM> between the host <NUM> and UE <NUM>, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host <NUM> and/or UE <NUM>. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection <NUM> 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 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection <NUM> may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node <NUM>. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host <NUM>. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection <NUM> while monitoring propagation times, errors, etc..

In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

Claim 1:
A method performed by a wireless device (<NUM>, <NUM>), the method comprising:
obtaining a window of time for bundling of a set of uplink transmissions (<NUM>) on a bandwidth part, wherein the bundling is for keeping power consistency and phase continuity, wherein the bundling is demodulation reference signal, DMRS, bundling;
determining whether or not to apply a timing advance adjustment (<NUM>) within the window of time, wherein the timing advance adjustment comprises an adjustment to a transmission timing of an uplink transmission in the set of uplink transmissions; and
transmitting the uplink transmission on the bandwidth part during the window of time using a transmission timing which is in accordance with said determining,
wherein said determining comprises:
determining to apply the timing advance adjustment within the window of time if the timing advance adjustment is indicated by a received timing advance command (<NUM>); and
determining to not apply the timing advance adjustment within the window of time if the timing advance adjustment is due to a detected error in downlink timing.