Patent Description:
For example, the invention refers to enhancements for URLLC SPS or CGs (configured grants) to cope with timing drifts between a wireless network and a UE-side application.

<CIT> relates to a technique for position determination in a wireless communication system with detection and compensation. Repeaters are not user equipments and are not associated to any local device. There is no definition of first and second active configurations and of any possibility of switching to a particular active configuration.

<CIT> discloses a technique to obtain channel state information measurements.

Examples below refer, inter alia, to enhancements for URLLC semi-presentence scheduling (SPS) and/or configured grants (CG), e.g., to cope with timing drifts between a wireless network and a UE-side application.

The SPS is defined as a configured resources configured in Time (including time offset and periodicity) and frequency (including frequency resources); the SPS mainly consider UL/DL transmission for LTE and only DL for NR.

The Configured grants (CG) as a configured resources configured in Time (including time offset and periodicity) and frequency (including frequency resources); the CG mainly consider UL transmission. In this document, we used both terms interchangeably.

Examples and aspects herein below relate to strategies and techniques for wireless networks, devices and/or communications (e.g., LTE, <NUM>, etc.), e.g., in radio frequencies or ultrasounds, etc..

Wireless communications permit the exchange of transmissions between transmitters and receivers without interposition of electrical wires.

Wireless communications suffer of several impairments, such as a reduced reliability as it is not possible to always guarantee that transmissions are properly received by the receiver. Further, there is the necessity of establishing rules (e.g., protocols) for coordinating the transmissions and the receptions.

For example, it is necessary to establish rules for avoiding that two nodes of the network transmit simultaneously or, in case of this occurrence, to develop techniques for solving collisions. Scheduling operations are known for these purposes (e.g., to distribute granted resources to different UEs).

Examples below and above may also refer to methods, which may be obtained, for example, by replacing functional elements with method steps, e.g. at least in some cases obtained with the equipment below.

Examples below may refer to computer programs and instructions which, when executer by a processor, may perform at least some of the methods below or implement at least some of the functions below.

The claims also define examples of the invention, which may cover or supplement examples described in the description. The text in squared or round brackets also create examples which supplement and/or integrate the examples not defined in squared brackets.

Examples below may relate, for example, to wireless communications (e.g., with electromagnetic waves, e.g., in radiofrequency).

In general terms, a UE (or a couple of UEs) may serve an internet of things, IOT, application (or another application in which the control is explicated via a wireless network). A first UE may be associated to and receive data from a sensor, while a second (remote) UE may be associated to and send data to an actuator. In another example, a first UE may be associated to a physical system (e.g., including sensor and actuator), while a second UE (or physical control system) may be associated to a controller of the physical system. Here, the second UE (or physical control system) may obtain sensed data from the first UE and may transmit command data to the first UE, so as to control the physical system. According to another example, the first UE is associated to a physical system, and the second UE (or monitoring system) may simply monitor the functioning of the physical system and receive data for monitoring the operations at the physical system. For these applications, URLLC may be used, e.g., with SPS scheduling or with CGs. In general terms, it is here mostly referred to the operations of the first UE, e.g., the UE which is at the side of the physical system or that collects data and send them in UL (e.g., to the BS, which may be a gNB). Subsequently, it is intended that the data is to be transmitted to the BS and that the BS will retransmit to any other system according to the specific communication. Further, it is her imagined that the UE is associated to (in proximity with) an external device, which is the device which obtains data packets from the physical system and provides the data packets to the UE, so that the UE retransmit the data packets to the BS.

Hence, several data may be sequentially obtained by the UE from the external device. These packets are to be periodically sent in UL according to the scheduling. However, it has been noted that the external device and the UE are not always synchronized with each other. The time periods of the transmissions from the UE are not necessarily the same of the time period for the periodic reception (arrival) of the data packets from the external device. For example, this may occur because of the UE having a timing (clock) module different from the timing (clock) module of the external device, so that the timings of the UE and of the external device drift. Therefore, there may occur the undesired situation in which the external device provides a data packet too late, so that the UE cannot respect the scheduling (the UE loses the "transmission occasion", TO). In cases like this, even if the scheduling grants a resource to a particular data packet, the data packet is not prepared in time and cannot be transmitted at the granted resource. Therefore, an unwanted "hole" in the communication could be generated.

It is also noted that the UE may serve, in real time, multiple services (e.g., for the same external device). An example may be a first service for providing a first measurement (e.g., voltage, or any other data measurement provided by a first sensor) and a second service for providing a second measurement (e.g., current, or any other data measurement provided by a second sensor). Further, while a first service may refer to measurement data, a second service may provide control data for controlling the physical system (these control data are not to be understood as signalling for the communication, but data providing information on the status of the controlled or measured physical system). Even in this case, there may happen that, because of internal functioning of the external device (e.g., internal queues, operating system, bugs, malfunctions, etc.), some packets are provided to the UE too late with respect to the foreseen scheduling. Even in this case, an unwanted "hole" in the communication could be generated. Multiple, subsequent holes may also be generated.

Techniques are requested to cope with these inconveniences.

The invention made is disclosed in the embodiment referring to <FIG>.

<FIG> shows a general example <NUM> of a UE according to the invention. The UE may be, for example, a mobile phone, a smartphone, a tablet, a personal computer, a portable computer, etc. The UE <NUM> may comprise a transmission unit <NUM> which may operate communications with a BS (not shown, but which may be a gNB) through an antenna <NUM> (here represented as external to the transmission unit <NUM>).

The UE <NUM> may comprise a communication controller <NUM> (e.g., a transceiver), which may control the antenna <NUM> for transmitting (and, in some cases, also receiving) data packets <NUM>, <NUM>.

The UE <NUM> may comprise and/or be associated to a buffer <NUM> (e.g., a memory, a storage, etc.). The buffer <NUM> may be input with data packets <NUM>, <NUM> from an external device <NUM>. The external device <NUM> may be a local device. The external device <NUM> may be connected to the buffer <NUM> through electric connections and/or non-wireless connections. The external device <NUM> may have some capacities of obtaining data from a physical system, and task of the UE <NUM> is to send the data packet to the BS (and to another computer device, such as another UE, for example, for performing a distributed control on the physical system or on a distributed physical system). The data packets <NUM>, <NUM> may be understood as information to be sent to a remote device, and may be processed and/or manipulated by the external device <NUM> and/or by the UE <NUM> and/or by any intermediate device which could be inserted.

The buffer <NUM> is here represented as having a plurality (e.g. two) columns, a first column for carrying data (e.g., measurements) 102a (which may therefore correspond to the packets <NUM>, <NUM>), and a second column for carrying time stamps 102b. The time stamps 102b may be associated, for example, to the time instant in which a data packet <NUM>, <NUM> has arrived at the buffer <NUM>. The buffer <NUM> may also comprise other information, such as an identifier field for identifying the particular data packet arrive from the external device <NUM>.

The buffer <NUM> may provide the data packets <NUM>, <NUM> (e.g., stored as 102a) to the communication controller <NUM>, so that the letter may transmit the data packets, according to the scheduling, to the BS.

The UE <NUM> may comprise a timing module <NUM> (e.g., clock), which may comprise, for example, a phase locked loop, PLL, device. The timing module <NUM> may synchronize (e.g. through synchronization signal <NUM>) the elements of the UE <NUM>, but may be seen as being in general incapable of synchronizing the UE <NUM> with the external device <NUM>.

The UE <NUM> may comprise a scheduling/reallocation unit <NUM>, which may define the scheduling <NUM> (and redefine it on the fly). The scheduling/reallocation unit <NUM> may define the scheduling <NUM> on the basis of a handshaking with the BS (the signalling from the BS being indicated with <NUM>) and/or on the basis of other information. The scheduling may be associated to a scheduling period, a subdivision among grants (e.g., time slots), frequencies, etc., each resource (frequency, time slot, etc.) being associated to a particular information to be provided (e.g., data packet <NUM>, <NUM>, etc., control signalling, DL data, etc.) and, in some cases, may define resources also for different UEs (e.g., mobile phones which happen to be in the neighbourhood of the UE <NUM>). The scheduling <NUM> may be synchronized with the synchronization signal <NUM> provided by the timing module <NUM>, and is in general non-synchronized with the external device <NUM> providing the data packets <NUM>, <NUM>. Each scheduling period of the scheduling <NUM> may be associated to a particular offset and to a particular time granularity.

The UE <NUM> may comprise a lookup table, LUT, <NUM> which is accessible from at least the scheduling/reallocation unit <NUM>. In the LUT <NUM>, scheduling data and/or other information may be stored.

The UE <NUM> may include a jitter determiner <NUM>. The jitter determiner <NUM> may check whether the timing of the data packets <NUM>, <NUM> arrived to the buffer <NUM> is compliant with the scheduling <NUM>. For example, the jitter determiner <NUM> may check the time stamps 102b of the arrived data packets <NUM>, <NUM> and may determine whether the latter have arrived in time for being transmitted according to the current scheduling.

Accordingly, the jitter determiner <NUM> may obtain jitter information <NUM>, <NUM>. Jitter information may be understood as delay information, regarding the delay of the arrival of the data packets <NUM>, <NUM> with respect to the expected times of arrival.

In some examples, the jitter determiner <NUM> may provide jitter information <NUM> to the scheduling/reallocation unit <NUM>. This operation may be carried out, for example, for causing the scheduling/reallocation unit <NUM> to perform a reallocation operation, for example.

In addition or in alternative, the jitter determiner <NUM> may provide jitter information <NUM> to the communication controller <NUM>. This operation may be carried out, for example, for informing the BS of the delay in the arrival of the data packet <NUM>, <NUM>, and/or to request, in some cases, modifications to the scheduling.

In general terms, the UE <NUM> may, on the basis of the jitter information <NUM>, <NUM> obtained by the jitter determiner, modify or request the modification of the transmission configuration (e.g., associated to the scheduling). For example, the UE's transmissions may be moved from a first active configuration (e.g., associated to a first scheduling) to a second active configuration (e.g., associated to a second scheduling). The first and second active configurations may differ from each other by any of the scheduling properties (e.g., at least one of allocated time slots, frequencies, length of the scheduling period, offset and granularity of the scheduling, etc.).

It is not strictly necessary for the UE to comprise the buffer, the transmission unit, and the delay or jitter determiner, or any other of the hardware and functional components discussed above and/or below. Notwithstanding, reference is made to these components for the sake of simplicity.

It will be shown that the UE may modify the transmission configuration to switch from a first active configuration to a second active configuration.

It will be also shown that the UE may transmit at least one of the delay information (<NUM>) or jitter information (<NUM>) and a request (<NUM>), the request being at least one of a scheduling modification request, a configuration modification request, a feedback information, and an additional configuration request, so as to modify the transmission configuration and/or the scheduling.

The time diagram of <FIG> shows a plurality of consecutive scheduling time periods P (<NUM>, <NUM>, <NUM>, etc.), each of which may be associated to a particular data packet <NUM>, <NUM> to be transmitted in UL. Packets <NUM> are first data packets <NUM> associated to a first service (e.g., measurements on physical magnitudes) and packets <NUM> are second data packets <NUM> associated to a second service (e.g., other measurements on other physical magnitudes or control data for governing the distributed physical system). The packets <NUM>, <NUM>, are respectively instantiated by periodically arriving packets <NUM>', <NUM>", <NUM>‴, and <NUM>', <NUM>", <NUM>"', etc. The arriving time of each packet <NUM>, <NUM> as received by the buffer <NUM> is indicated with 122t, <NUM> (e.g., the arriving time of packet <NUM>' is t122', the arriving time of packet <NUM>" is t122", and the arriving time of packet <NUM>" is t122"). The arriving packets <NUM>, <NUM> are respectively retransmitted, by the communication controller <NUM> and the antenna <NUM>, as wireless transmissions 122t, 126t (e.g., the arriving packet <NUM>' is retransmitted as 122t', the arriving packet <NUM>" is retransmitted as 122t", and the arriving packet <NUM>" is retransmitted as 122t"). the time necessary for retransmitting one packet is indicated with K.

In this case, a first instantiation <NUM>' of the first data packet (packet <NUM>/service <NUM>) arrives at the buffer <NUM> at time instant t122'. According to the scheduling, at the subsequent instant TO122' there is a possibility (transmissions occasion) for transmitting the data packet <NUM>': the transmission 122t' is therefore performed by the communication controller <NUM> and the antenna <NUM> starting from instant TO122'.

During the transmission of the data packet <NUM>', at instant t126' the buffer <NUM> receives a first instantiation <NUM>' of the second data packet (packet <NUM>/service <NUM>). According to the scheduling, at the subsequent instant TO126' there is a possibility (transmissions occasion) for transmitting the data packet <NUM>': the transmission 126t' is therefore performed by the communication controller <NUM> and the antenna <NUM> starting from instant TO126'. A delay <NUM>' is therefore caused.

During the transmission of the data packet <NUM>', at instant t122" the buffer <NUM> receives a second instantiation <NUM>" of the first data packet (packet <NUM>/service <NUM>). According to the scheduling, at the subsequent instant TO122" there is a possibility (transmissions occasion) for transmitting the data packet <NUM>": the transmission 122t" is therefore performed by the communication controller <NUM> and the antenna <NUM> starting from instant TO122". A delay D122" is therefore caused.

It is noted that, according to version of known protocols, there is a possibility for transmitting a plurality of redundancy versions (RVs) of each data packet. RVs, which may be either self-decodable or non-self-decodable, and are where indicated with RV0, RV1, RV2, RV3 (it is here imagined that RV0 and RV3 are self-decodable, while RV1 and RV2 are not, while other configurations are possible). The RVs may be associated to different forward error correction (FEC) schemes and/or may be encoded differently (e.g., to increase diversity). Therefore, the transmission of data packets <NUM>, <NUM> may be understood as transmissions of RVs (e.g., repetitions of multiple RVs). Here, four RVs are used, even if different numbers of repetitions may be possible. Here, the imagined sequence for the RVs is RV0, RV2, RV3, RV1 (other sequences may be possible). Therefore, the transmission 122t, 126t of the packets may be understood as the transmission of multiple data RVs (within the slot time P and which take the time K).

The RVs may be understood as data structures which are associated by the communication controller <NUM> and are transmitted in subsequent slots within the timing slot in which each transmission 122t, 126t is to be performed. In some examples, there is provided an initial transmission and one or more RVs. In some examples, the transmission of one single RV of the packet is sufficient. In some examples, the transmission of multiple RVs is preferable, for the sake of redundancy.

Hence, the transmission of the packets <NUM>', <NUM>', <NUM>" (in any possible RV), etc. could, in principle, only be performed at some particular timing occasions TO126', TO126', TO122", which are in general too few for permitting a reliable transmission of the packets. If a packet arrives too late (e.g., after the transmit occasion), its transmission needs to be delayed. Further, multiple services at the external device <NUM> may compete for the transmission at a particular time slot (it is notwithstanding not necessary to have multiple services, in some examples).

Since Rel-<NUM>, the reliability and latency have been taken into account for satisfying the defined requirement between 10E-<NUM> in <NUM> to 10E-<NUM> in <NUM>. This latency-reliability constraint to be used to satisfy ultra-reliable and low latency (URLLC) applications which can be used for different applications such as:.

Grant-free (GF)/Configured-Grants (CG) in UL transmission and semi-presentence scheduling (SPS) in UL have been considered a major feature suitable for URLLC application. As the UE uses configured resources for physical uplink shared channel (PUSCH) and physical uplink control channel (PUCCH) transmission, the Transmission Opportunities (TO) cannot be allocated arbitrary depending on data arrival time. This will also have drawbacks when different services (i.e., with different traffic requirements) exist at the UE, where the UE need to have:.

Hence, a strict occurrence of TOs of a single active configuration may result in a delay (also referred to as a jitter). It has been understood, however, that this delay can be further reduced if the allowed transmission opportunities are increased. It can be even enhanced if the transmission opportunity can be dynamically set by the UE (per request) or by the gNB (per signaling). <FIG> highlights the delay due to single-strict CG. (<FIG> shows a possible delay due to late packet arrivals, with no cross boundaries or soft starts).

P is the SPS/CG period, K is the number and the window size of repetition, e.g., K=<NUM> in <FIG>, and the Delay (or Jitter) may be computed from when the data of the said service arrives until when the first part of the data run over the air. One can observe the following use cases that may exhibit 'racing up' of services at the UE, requiring access to configured grants.

A UE is handling different services with different URLLC requirements, i.e., latency, reliability, and traffic types. In this case, the different services may require different time accessing the air-interface. With different reliability requirements, it may mandate different number of K-repetitions.

In a factory automation scenario (e.g., physical or distributed system), if the data arriving time is subject to a varying jitter, e.g., due to different time alignment of the different clocks resulting in a hyper-period phenomenon, then, a jittered data may arrive slightly after the TO and may lead to a delay until the next TO. Hence, in case of multiple configured active grant, the newly arriving data will be deferred to the next possible TO in another active configuration.

Applications on UE side (e.g. camera pictures which are taken for industrial quality assurance along a fast-moving production line) are not necessarily all synchronized to the timing of industrial wireless networks (at the side of the external device <NUM>).

If the UE <NUM> sends data 122t, 126t on the UL with Semi-Persistent-Scheduling (SPS) with an application specific period of the scheduled resources (which are synchronous to the network), it may result in a systematic jitter of the data reception timing, because the relative timing of the application drifts relative to the scheduled SPS resources. The jitter is up to the granularity of the SPS periodicity, which can be up to several TTI's or sTTI's.

This jitter (e.g., D126', D122") may lead to problems in the overall industrial application, e.g. camera pictures for quality monitoring are jittering too much and cannot be used any more for quality assurance.

As shown in <FIG>, a hyper-period may be understood as the least common multiple (LCM) of all related clock periods, e.g., various application timers (CPU based), UE's clock <NUM>, network clock error, and the machines internal clocks (embedded clocks). After that time, the complete schedule repeats itself. (<FIG> may be understood as showing the Hyper-period due to SPS and periodic arrival mismatch; <FIG> may be understood as showing the Hyper-period for arbitrary (fractional) clock mismatch).

The example showing this on the whiteboard was this:.

sps period = <NUM>
event_period = <NUM> % arrival of physical message.

And here an example with two SPS active configurations.

sps period = <NUM> (offset = <NUM> (SPS_ticks = <NUM>, <NUM>, <NUM>,. ), offset = <NUM> (SPS_ticks = <NUM>, <NUM>, <NUM>,. ))
event period = <NUM>.

As can be understood, the minimum jitter is increasing (and this is undesired).

From the examples above, we can see that the SPS/CG period and the number of SPS/CG active configurations are the only parameters bounding the jitter. The formulas to compute the maximum jitter and the required number of SPS active configurations to reduce or have no jitter is as follows:.

The maximum admitted jitter (maximum_allowedjitter) cannot be larger than the duration of a time slot (otherwise, a packet arriving at the buffer <NUM> soon after the transmission occasion would automatically be invalid). The maximum admitted jitter (maximum_allowedjitter) shall notwithstanding be lower than a scheduling period P (SPS/CG_period).

It has been understood that it is possible to make use of different active configurations (e.g., SPS configurations, CG configurations). Each active configuration may be understood as a data structure indicating some granted resources (e.g., time slot, frequency, etc.), e.g., for redundancy versions of the transmissions of the data packets. Accordingly, in some examples, in case of late arrival of the data packets <NUM>, <NUM> at the buffer <NUM>, they may be routed to different active configurations, for example.

According to formula <NUM>, the maximum allowed delay or jitter may be defined between the length of a time slot and the length of the time period.

According to formula <NUM>, the number of active configurations may be associated to the length of the period and the maximum allowed delay or jitter. For example, the number of active configurations is associated to the fraction, or the ceiling of the fraction, between the length of the period and the maximum allowed jitter.

Therefore, on the basis of formulas <NUM> and <NUM> (and/or on the basis of the maximum jitter, which may be based on requirements on the physical system), it is possible to define how many active configurations may be defined necessary.

In examples, the active configurations are such that, for each time slot, only one active configuration transmits a data packet including the transmit block of all the redundancy versions of the data packet.

Different active configurations may have an offset with each other, with respect to each other of one symbol or a discrete number of symbols (e.g., one slot may take a discrete number of symbols such as <NUM> symbols). A time slot comprises an integer number of time symbols. , in LTE and New Radio a symbol duration is the duration of one OFDM symbol. Additionally, a slot may be, for example in normal cyclic prefix length, composed of <NUM> symbols. In some examples, the offset between different active configurations may be one time slot or an integer number of time slots.

Hereinbelow, reference is made to several "embodiments" (e.g., E1, E2, E2*, E3). It is to understand that the "embodiments" are only for the sake of explanation and are to be construed broadly, without limiting the solutions to them. The features of the different embodiments may be combined with the features of other embodiments.

This solution is based, inter alia, on modifying on the fly some features associated to the scheduling. This may be obtained, for example, by relying on the jitter information <NUM> provided to the scheduling/reallocation unit <NUM>. For example, the UE may jump (e.g. when the UE determines that the jitter or delay of a packet arrival is too high) from a first active configuration to a second active configuration, the second configuration permitting the transmission of the late-arrived data packet. The active configurations may be more than one, and the UE may switch (e.g., without necessity of requesting to the BS) to the active configuration which permits the transmission of the late-arrived packet.

An idea is to apply a switching mechanism to alternate between multiple configured and multiple active SPS/CG active configurations and/or preconfigured resources defined by either the network via RRC messages or the base-station (L1-Signaling/DCI), i.e., allowing multiple reservations. For example, at least one of the following assertions may result to be valid:.

With reference to the active configurations, this concept may be understood as referring the concept of "configuration configured for the UE" and/or "configuration ready to be used after being activated by the BS (gNB) or RRC". Hence, the active configuration may be configured by the UE and/or by the BS.

The present solution may work both for UL and DL. Hereinafter, reference is prevalently made to UL solutions.

With examples according to the present solution, there is provided the possibility of changing the transmission configuration (e.g., the scheduling, timing parameters associated to the scheduling timing period, the particular instantiation of the data packet as transmitted, etc.) on the basis of jitter information (e.g., <NUM> and/or <NUM>).

It is also possible to reduce the possible jitter time that might be induced due to the existence of periodic events, where their periods are not integer multiples. The least common multiple of all these periods is called "hyper-period". This hyper-period may exist due to the presence of multiple (different) clocks in a controlled system, e.g., the radio chipset clock, the motor clock, the electronic controller clock etc..

The proposed solutions as described in the Embodiments above reduce the transmission timing jitter from the SPS scheduling period (which might be a multiple of a TTI/sTTI) down to the granularity of the wireless communication system TTI/sTTI.

Points in the specifications of LTE and NR, where extensions or changes are required, are explained later in the document.

Reference may be made to <FIG>, showing a timing diagram with configurations at the abscissa and time and the ordinate. According to the scheduling there is provided a first active configuration conf1 and a second active configuration conf2. The first and second active configurations conf1, conf2 are scheduled to transmit different RVs of the same data packet <NUM>.

At an instant t122', a data packet <NUM>' arrives at the buffer <NUM>. As foreseen by the scheduling and in particular by the first active configuration conf1, a timing occasion occurs at instant TO122'<NUM>, in which a redundancy version RV0 of the data packet <NUM>' is transmitted by the communication controller <NUM> and the antenna <NUM>. As foreseen by the scheduling and in particular by the second active configuration conf2, a subsequent timing occasion occurs at instant TO122'<NUM>, in which a redundancy version RV3 of the data packet <NUM>' is transmitted by the communication controller <NUM> and the antenna <NUM>.

A subsequent data packet <NUM> (<NUM>") undesirably happens to arrive at the buffer <NUM> at instant t122", which is after the transmission occasion TO122"<NUM> (this is how to say that the data packet <NUM> arrives in the buffer <NUM> after a first delay or jitter threshold, which, when expires, permits to conclude that the data packet <NUM> has not arrived in time). This means that an unwanted "hole" is caused in the transmission (as the first redundancy version RV0 of the packet <NUM>", which should be transmitted, cannot transmitted because of the absence of the packet <NUM>" in the buffer <NUM>). Theoretically, also the subsequent transmission occasion TO122"<NUM> (which, according to the scheduling, should be assigned to a second redundancy version RV3 of the packet <NUM>") should not be used.

However, it has been understood that it is possible to reconfigure the transmission configuration, e.g., by reallocating, on the fly, the first redundancy version RV0 of the packet <NUM>" to the second active configuration conf2, so as to quickly transmit the first redundancy version RV0 of the packet <NUM>" at the next transmission occasion TO122"<NUM> which was originally assigned to the second active configuration conf2, and in particular to the second redundancy version RV3 of the packet <NUM>". Basically, the resource (time slot, frequency) starting at instant TO123"<NUM>, which according to the scheduling was allocated to the second redundancy version RV3, has been reallocated on the fly to the first redundancy version RV0. (This may be carried out when the packet <NUM> arrives in the buffer <NUM> after a first delay or jitter threshold, but before a second delay or jitter threshold, which permits to conclude that the packet <NUM> has arrive in time for the second configuration. The second jitter threshold may be associated, e.g., be equal or almost equal, to the shifting of the second configuration with respect to the first configuration. Therefore, if a second configuration is delayed of a certain time with respect to the first configuration, it is possible to switch to the second configuration when the packet <NUM> arrives within the second threshold, i.e. in time for being transmitted at the second configuration, e.g. within a delay which is less than the shift between the first and second configurations).

Notably, this possibility may be obtained by relying on the jitter information <NUM> as provided by the jitter determiner <NUM> to the scheduling/reallocation unit <NUM>. The scheduling/reallocation unit <NUM> may reallocate, on the fly, the scheduled resources (e.g., a time slot, a frequency, etc.) and provide the modified scheduling <NUM> to the communication controller <NUM>, so that the communication controller <NUM> transmits the data packets in accordance to the modified scheduling.

Subsequently, if the third packet <NUM>"' arrives in time before the next scheduled time slot, the communication may be performed according to the predefined scheduling, without the necessity of reallocating resources. In that case, no resource reallocation is performed on the basis of the jitter information <NUM>.

In examples, the scheduling/reallocation unit may check whether the jitter <NUM> (as measured by the jitter determiner <NUM>) is larger than a predetermined jitter threshold (as based on the transmission occasions as defined by the predefined scheduling): if the jitter <NUM> is larger than the predetermined jitter threshold, then a reallocation is performed; otherwise, no reallocation is performed.

At least one of the following statements may be valid:.

<FIG>) shows a timing diagram with time at the abscissa and resource configurations at the ordinate. A first active configuration conf1 is assigned, by the scheduling, with a slot S122 (instantiated by multiple slots S122', S122", S122‴) for the transmission of a first redundancy version RV0 and a second redundancy version RV3 of a cyclical data packet <NUM> (instantiated by packets <NUM>', <NUM>", <NUM>"', periodically arriving at the buffer <NUM>).

At first, reference is made to timing period <NUM>. At an instant t122', a first packet <NUM>' (packet <NUM>) arrives at the buffer <NUM>. The instant t122' is before the timing occasion TO122'<NUM> (start of the slot <NUM>'), and the packet <NUM> may be transmitted by the communication controller <NUM> and the antenna <NUM> as packet 122t'. According to the scheduling, the transmitted first packet 122t' is transmitted using the first active configuration conf1. According to the first active configuration conf1, a first redundancy version RV0 of the received packet <NUM>' is transmitted at a first part of the slot <NUM>', starting from time instant TO122'<NUM>. According to the first active configuration conf1, a second redundancy version RV0 of the received packet <NUM>' is transmitted at a second part of the slot <NUM>', starting from time instant TO122'<NUM>. As both the first and the second RVs are transmitted in time through the first active configuration conf1, there is here no need for invoking the second active configuration conf2.

For the subsequent timing period <NUM>, the data packet <NUM> (<NUM>") arrives (undesirably) at the buffer <NUM> at the unwanted time instant t122", which is after the first timing occasion TO122"<NUM> defined by the scheduling (this is hot to say that the packet <NUM>" arrives at the buffer <NUM> when the scheduled slot S122" has already started). Hence, an unwanted transmission hole may be generated, in the sense that the communication controller <NUM> and the antenna <NUM> do not transmit a valuable data.

One could imply that, following the scheduling and the first active configuration conf1, the transmission 122t" of the data packet would be delayed at least to the further subsequent timing period <NUM>.

Notwithstanding, it has been understood that it is possible to make use of the second active configuration conf2, and replenish at least a part of the slot S122" with a valuable packet to be transmitted. Hence, while a first slot S122"<NUM> of the slot S122" hosts a transmission hole, the second slot S122"<NUM> of the slot S122" may actually be used for transmitting, as transmitted data packet 122t", at least one redundancy version (e.g., RV0) of the arrive data packet <NUM>".

Notably, we do not need to modify the first active configuration conf1, but we may simply reconfigure the second active configuration conf2.

<FIG>) shows a variant according to which, instead of transmitting the first redundancy version RV0 of the data packet 122t", the second active configuration conf2 transmits the second redundancy version RV3.

Subsequently, if the third packet <NUM>"' arrives in time before the next scheduled time slot, the communication may be performed according to the predefined scheduling, without reallocating resources. In that case, no resource reallocation is performed on the basis of the jitter information <NUM>.

In examples, the scheduling/reallocation unit <NUM> may check whether the jitter <NUM> (as measured by the jitter determiner <NUM>) is larger than a predetermined jitter threshold (as based on the transmission occasions as defined by the predefined scheduling): if the jitter <NUM> is larger than the predetermined jitter threshold, then a reallocation is performed; otherwise, no reallocation is performed.

At least one of the following statements may be valid in some examples:.

<FIG> may therefore be understood as showing multiple active configuration with variable RV-ID shift.

Another example is provided by <FIG>, where the ordinate is the time, and the abscissa is the frequency. Here, a first active configuration conf1 and a second active configuration conf2 are both used (e.g., at the same frequency), even conf1 and conf2 do not overlap (they use time slots which are not the same). According to the scheduling, for each arriving data packet <NUM>, the first active configuration conf1 provides the transmission of a first redundancy version RV0 at a first time slot, and the second active configuration conf2 provides the transmission of a second redundancy version RV3 at a second time slot (non-overlapping with the first time slot).

For period <NUM>, a packet <NUM>' correctly arrives at the buffer <NUM> at an instant t122', which is before the timing occasion TO122'<NUM>. Hence, the packet <NUM>' is transmitted as packet 122t" by the communication controller <NUM> and the antenna <NUM> at the time slots defined by the first and second active configurations conf1, conf2, according to the scheduling.

For period <NUM>, a small jitter impairs the arrival of a packet <NUM>", as the packet <NUM>" incorrectly arrives at the buffer <NUM> after the scheduled timing occasion TO122"<NUM>. Accordingly, the slot S122"<NUM>, which, according to the scheduling and the first active configuration conf1 should host a redundancy version of a packet 122t" to be transmitted, actually contains an undesired transmission hole.

One could imagine that the same fate would impair the subsequent slot S122"<NUM> (foreseen by the second active configuration conf2 for hosting the second redundancy version RV3 of a packet 122t" to be transmitted).

However, it has been understood that it is possible to avoid the occurrence of a further transmission hole, and use the slot S122"<NUM> for hosting a valuable data and to reduce the jitter. In fact, it has been understood that it is simply possible to modify the second active configuration conf2 on the fly, to host at least one redundancy version (e.g., RV3) of the data packet <NUM>" (transmitted as the transmission 122t").

Accordingly, at least one redundancy version of the data packet may be transmitted in time. This is possible at least when the delayed arrival of the data packet <NUM>" is at a delayed time instant t122", which is after the transmit occasion TO126"<NUM> of the first active configuration conf1, but before the transmit occasion TO126"<NUM> of the second active configuration conf2.

At the subsequent period <NUM>, an increased jitter impairs the arrival of the packet <NUM>"', which is received in the buffer at the time instant t122"', which is after the timing occasion TO122"<NUM> which, according to the scheduling and the first active configuration conf1, is foreseen as the start of the slot S122‴ for the transmission of a first redundancy version RV0 of the packet <NUM>"'.

It has been understood that, instead of suffering of another transmission hole, it is possible to transmit a second version RV3 of the previous data packet <NUM>": accordingly, the slot S122"' is not wasted, and a second redundancy version RV3 of the previously transmitted data packet <NUM>" may be transmitted. Notably, this possibility may be obtained by relying on the jitter information <NUM> as provided by the jitter determiner <NUM> to the scheduling/reallocation unit <NUM>. The scheduling/reallocation unit <NUM> may reallocate, on the fly, the scheduled resources (e.g., a time slot, a frequency, etc.) and provide the modified scheduling <NUM> to the communication controller <NUM>, so that the communication controller <NUM> and the antenna transmit the data packets in accordance to the modified scheduling.

At least one of the following statements may be valid in some examples:
For <FIG>: apply a switching on mechanism to alternate between SPS active configurations (e.g., conf1, conf2) allowing different repetition sequences.

<FIG> may be understood as showing multiple active configuration with variable RV-ID shift.

It is to be noted that <FIG> shows an example in which the frequencies of the first and second active configurations conf1, conf2 are different (e.g., non-overlapping).

Same operation as <FIG>, <FIG> shows the case when two active configurations share the same frequency resources but have different frequency offset.

In case the buffer <NUM> receives, at the delayed instant t122"", the packet <NUM> (<NUM>"") (for which the first active configuration conf1 would prescribe the transmission at the slot S122""<NUM>) is transmitted at the slot S122ʺ‴<NUM>, while the subsequent slot S122ʺ‴<NUM> may be used for transmitting the packet In the examples above, reference has prevalently been made to a data packet <NUM> periodically received by the buffer <NUM>. However, multiple data packet (e.g., <NUM>, <NUM>) may arrive, e.g. from different services (e.g., associated to different measurements or different applications or different uses) expected by the external device <NUM> from the UE <NUM>.

An example is provided by <FIG>, in which different services <NUM> and <NUM> are served at different periods.

Different frequency bands are used: a first active configuration conf1 is associated to a first band F0, and the second active configuration conf2 is associated to a second band F0+F1. In this case, the first and second band may be at least partially overlap. The second band F0+F1 may be broader than the first band F0.

In examples, the first (narrower) band F0 may be used for transmitting data packets <NUM> for servicing the service <NUM>. The second (broader) band F0+F1 may be used for transmitting data packets <NUM> for servicing the service <NUM>. It is here hypothesized that the service <NUM> needs more band (e.g., more information to be transmitted in the one slot, even though the transmission rate may be lower).

A first data packet <NUM>' arrives (from service <NUM>) at the instant t122' before the transmit occasion TO122'<NUM>, while no second data packet for service <NUM> arrives. Hence, the first data packet <NUM>' is transmitted by the communication controller <NUM> and the antenna <NUM> as transmission <NUM>' in the slots S122'<NUM> and S122'<NUM>,.

At the subsequent instant t122", another first data packet <NUM>" arrives at the buffer <NUM> before the timing occasion TO122"<NUM>. Therefore, at least one redundancy version RV0 of the second data packet may be transmitted as transmission 122t" in at least one first slot S122"<NUM>.

However, at instant t126', before the subsequent timing occasion TO122"<NUM> (which is scheduled for either transmitting a second redundancy version RV3 of the second data packet 122t" or transmitting a packet 126t servicing service <NUM>), a data packet <NUM>' for service <NUM> arrives at the buffer <NUM>.

One could imagine that, at this point, a second version RV3 of the first packet 122t" should necessarily be transmitted, while the transmission of the data packet 126t' for service <NUM> should be delayed to the subsequent timing occasion.

However, it has been understood that this implication can be avoided by intelligently operating on the active configurations conf1 and conf2. For example, it may be possible to avoid the transmission, in the slot S122"<NUM>, of the second redundancy version RV3 of the data packet 122t", while it may be possible to transmit, instead, a redundancy version RV0 of the data packet <NUM>' associated to service <NUM>.

At instant t122‴ a packet <NUM>"' (for service <NUM>) is received by the buffer <NUM>, and at instant t126" a packet <NUM>" (for service <NUM>) is received by the buffer <NUM>. Both instants t122‴ and t126" are after the timing occasion TO122‴<NUM> for transmitting at a first slot S122‴<NUM>, but before the timing occasion TO <NUM>"'<NUM> for transmitting at a second (immediately subsequent) slot S122"<NUM>.

Hence, the slot S122‴<NUM> undesirably hosts a transmission hole.

However, a transmission hole in the subsequent slot S122‴<NUM> is avoided: this is because it is possible to modify on the fly the second active configuration conf2, and insert a redundancy version RV3 of the packet 122t‴. As the packet 122t‴ is services service <NUM> (which requires less band than service <NUM>), only a part of the band S122"'<NUM>-<NUM> in the slot S122‴<NUM> may be used, while the remaining band S122"'<NUM>-<NUM> the slot S122‴<NUM> may be void or filled by zero values.

Basically, a prioritization may be defined: some packets may be defined as having higher priority than other ones. The priority may be fixed (e.g., defined a priori) or variable, as in <FIG>: while the competition for the slot S122"<NUM> has been wonby service <NUM>, the competition for the slot <NUM>‴<NUM> has been won by service <NUM>. The priority may be therefore variable: for example, the priority may be changed alternatively for different services. In alternative, other strategies may be adopted: for example, a first-in-first-out, FIFO, or last-in-first-out, LIFO strategy may be adopted. In examples, the prioritization may follow the quality of service, QoS, as experienced by the UE <NUM> and/or by the external device <NUM>.

In examples, there may be the possibility for the UE to choose, among different packets arriving from different services, the preferred data packet to be sent. For example, it is possible for the UE to decide the preferred data packet to be transmitted on the basis of a predetermined required maximum jitter, so as to give precedence to data packets whose required maximum jitter is closest to expire.

Also this example relies on the jitter information <NUM> as provided by the jitter determiner <NUM> to the scheduling/reallocation unit <NUM>. The scheduling/reallocation unit <NUM> may reallocate, on the fly, the scheduled resources (e.g., a time slot, a frequency, etc.) and provide the modified scheduling <NUM> to the communication controller <NUM>, so that the communication controller <NUM> and the antenna <NUM> transmit the data packets in accordance to the modified scheduling.

The UE <NUM> may be configured with two or more active configurations share part of the frequency domain so that at least one of the following assumptions may be valid:.

The UE <NUM> may be configured with two or more active configurations (e.g., conf1, conf2) may have different time offset: e.g., the time offset can be one or multiple slots/mini-slots/subframes/ OFDM symbols or multiple OFDM symbols.

The UE <NUM> may be configured to use one active configuration (e.g., conf1) for a service (e.g., service <NUM>) and another active configuration (e.g., conf2) for another service (e.g., service <NUM>) for UL transmission.

The UE <NUM> may be configured to prioritize any of the services based on the QoS or the jitter or the cumulative delay.

If the UE <NUM> may select (e.g., due to a jitter/delay and or QoS prioritization) to transmit one service that requires less resources (say F0 only), the UE <NUM> may still use the active configuration with more resources (F0 +F1):.

<FIG> may be understood as showing multiple active configuration with variable RV-ID shift using same frequency and different time. Hint; every CG/SPS starts with RV0.

<FIG> therefore disclose a scheme with multiple active configuration with variable RV-ID shift.

For <FIG>: Apply a switching on mechanism to alternate between SPS/CG active configurations allowing different repetition sequences. Now, with more SPS/CG-configs, at least one of the following assertions may be valid:.

<FIG>: similar to <FIG>; however, at least one of the following assertions may be valid:.

There is a set of SPS/CG active configurations reserved for the UE. The UE can switch to the active configuration that is closer to the received data transmission. Depending on the used SPS active configuration, the set of reserved SPS active configurations can change.

In general terms, when multiple redundancy versions (RVs) compete for the transmission, priority may be awarded to the self-decodable RVs. Other priority strategies may be adopted.

<FIG> shows an example of a method <NUM> according to an example, which may be combined with features above. At step <NUM>, data packets <NUM>, <NUM> are received, e.g., by the buffer <NUM> from an external device <NUM>. At step <NUM>, a jitter <NUM> is measured (e.g., by the jitter determiner <NUM>). At step <NUM>, a reallocation is performed (e.g., by modifying the scheduling on the fly), e.g., by the scheduling/reallocation unit <NUM>. At step <NUM>, the transmissions are performed according to the reallocations (e.g., new scheduling), e.g., by the communication controller <NUM>.

As explained, the transmission configuration (i.e., the general transmission configuration between the UE and the BS) is a general concept including all the rules, protocols, etc. which permit the communication. There are included, for example, the frequencies, the scheduling, etc..

There is the possibility of using "first and/or second active configurations (conf1, conf2)", which may be understood as different schemes at disposal of the UE for transmitting its packets. The active configurations may be scheduled, and it is not necessary that each active configuration is always chosen.

When an active configuration is chosen (e.g., because of a late arrival of a data packet <NUM> or <NUM> at the buffer <NUM>), in some examples the UE may continue using the chosen active configuration up to the next late arrival of a subsequent data packet.

The "transmission configuration" is therefore a general concept which may also encompass the concept of "(different) active configuration(s)" (e.g., SPS configurations), but is not necessarily the same.

The active configurations may be in a plural number (e.g., more than two), and, in some cases, only one active configuration transmits. When a transmitting active configuration does not permit to transmit a data packet anymore (e.g., because of the data packet having arrived at the buffer <NUM> too late), the UE may switch to a second active configuration (e.g., offset of one slot or of a discrete number of slots) which permits to transmit the late-arrived data packet as soon as possible.

Summarizing, at least one of the following assertions may be valid:.

The active configurations may be such that, for each time slot, only one active configuration transmits a data packet.

The active configurations may be such that, for each time slot, only one active configuration transmits a data packet including an initial transmission and all the possible redundancy versions of the data packet.

The UE may be to choose between the first and second active configurations so as to switch from one configuration to the chosen configuration without transmitting a request to a BS, hence increasing speed.

When operating at the first active configuration and in case of late arrival of a data packet, the UE may switch to the second active configuration for transmitting the late arrived data packet.

When switching to the second active configuration, to reallocate a data packet or a RV of the data packet, to a resource of the second active configuration.

The scheduling may provide for a configuration time offset (e.g., indicated with <NUM> in <FIG>) of the second active configuration with respect to the first active configuration, so that, if a data packet <NUM>" (<FIG>) arrives too late for being transmitted in the first active configuration but before the configuration time offset <NUM> elapses, the UE reallocates the late-arrived data packet <NUM>", or at least a redundancy version thereof, to a resource of the second active configuration, and switches to the second active configuration (and in fact in <FIG> the transmitted packet 122t" is transmitted in one single RV, but is transmitted within only the time offset <NUM>).

After switching to the second active configuration, the UE may continue transmitting with the second active configuration up to a new necessity for switching to the first active configuration or to a different active configuration based on a subsequent late arrival of a data packet.

The UE may, when choosing to switch to another active configuration, choose the active configuration (among a plurality of active configurations different from the first active configuration) which permits the transmission of the delayed data packet.

The UE may receive BS's signalling defining the active configurations (e.g., by RRC).

In some examples above, different active configurations have different resources for transmitting different RVs in different time slots. Another coverage may be to have either only time and/or time+frequency shift between the configurations. Different active configurations have different resources for transmitting different redundancy versions, RVs, in different frequencies.

This solution is based, inter alia, on measuring or obtaining the jitter in the arrival of the data packets <NUM>, <NUM>, and, in case of necessity, in the request of modifying the timing of the scheduling. For example, the UE <NUM> (which may be as in <FIG>) may request to increase or reduce the length of the scheduling period. In addition or alternative, the UE <NUM> may request to modify the offset of the scheduling period (e.g. by shifting the scheduling period). In some cases, this solution may be understood a distributed PLL, in which the BS synchronizes with the clock of the external device <NUM>.

Hence, in order to modify transmission configuration, the UE <NUM> is configured to transmit the delay or jitter information (<NUM>) and/or a scheduling and/or configuration modification request, so as to modify the transmission configuration and/or the scheduling. In examples, the UE may be configured to request to the BS some adjustments and/or some modifications. For example, the UE may provide some information which will force the BS to modify the timing parameters of the scheduling, hence operating as a distributed PLL, in which the timing of the scheduling is synchronized by the BS to the clocks of the external device <NUM>.

<FIG> shows an example of a method <NUM> in which a UE (e.g., the UE <NUM> above) measures jitter information <NUM> at step <NUM>. The jitter information <NUM> may refer to the jitter between:.

In addition or alternative, the UE <NUM> may define a scheduling modification request and/or configuration modification request, to request a modification of the scheduling to the BS (e.g., based on the jitter measurement <NUM>).

At step <NUM>, the UE <NUM> may send the jitter information and/or the modification request and/or the configuration modification request to the BS. An updated of the scheduling may therefore be requested by the UE.

At step <NUM>, the BS may receive the jitter information and/or the modification request and/or the configuration modification request. This information is collectively referred to as information <NUM>.

At step <NUM>, the BS may modify the scheduling according to the jitter information and/or the modification request and/or the configuration modification request (information <NUM>). Hence, an update is carried out.

At step <NUM>, the BS may signal the modified scheduling (or scheduling parameters, such as the timing parameters of the time period <NUM>) to the UE.

In general terms, the information <NUM> sent by the UE <NUM> to the BS may include a determination on parameters associated to the jitter. These parameters (which may include, for example, parameters k1 and/or k2 as discussed below) may cause a reconfiguration of the scheduling (and in particular of the scheduling parameters of the communication).

For example, the UE <NUM>, when periodically receiving at the buffer <NUM> the data packet <NUM>, <NUM> from the external device, may determine that the period of provision of the data packets is different from the UE's expected period (this may be due to the non-synchronization of the timing module of the external device <NUM> with respect to the timing module <NUM> of the UE <NUM>). Therefore, the UE (e.g., at the jitter determiner <NUM>) may determine a scaling parameter k1 which would permit to resynchronize the scheduling period to the provision period of the arriving the data packet <NUM>, <NUM> at the buffer <NUM>.

Similarly, the UE <NUM> (e.g., at the jitter determiner <NUM>) may determine a shifting parameter k2 for shifting the scheduling period, so as to align the scheduling period with the period of provision of the data packet <NUM>, <NUM> as provided by the external device <NUM> to the buffer <NUM>.

Accordingly, the BS ay update the parameters of the scheduling on the basis of the delay or jitter information.

It is to be noted that, in some examples, the parameters k1 and k2 are calculated by the BS on the basis of the feedback information <NUM> (e.g., delay or jitter information) provided by the UE <NUM>. In that case, k1 and/or k2 may be modified at step <NUM>.

In some examples, the delay or jitter information may include a jitter trend information. The jitter trend information may include information on the evolution of the jitter during subsequent scheduling periods. The jitter trend information may provide information on the increasing or decreasing jitter, for example. For example, there may be provided the ratio Ratio_1 = (ΔT<NUM> - ΔT<NUM>)/period , where ΔT<NUM> is a first difference between the arrival of a first data packet (e.g., <NUM>") in the buffer (e.g., <NUM>) and the subsequent timing occasion (e.g., TO122"<NUM>); ΔT<NUM> is a second difference between the arrival of a second, subsequent data packet (e.g., <NUM>‴) in the buffer (e.g., <NUM>) and the subsequent timing occasion (e.g., TO122‴<NUM>) for transmitting the second data packet (e.g., <NUM>"'); and "period" is the length of the current determined period (e.g., <NUM>), to provide a value of the jitter trend. The jitter trend may be updated at each period. The jitter trend may be signalled to the Bs with the information <NUM>. An example of trend information may be (with reference to <FIG>):.

By analyzing the trend on the jitters, it is possible to provide jitter trend information to the BS.

In examples, a lookup table, LUT, <NUM> may be provided, for providing a quantized version of the delay or jitter information. The LUT <NUM> may have a plurality of values which may be associated to different ratio values obtained in different time periods. Therefore, the values of the jitters may be encoded by using codes stored in the LUT <NUM>: hence, the code associated to a particular jitter may be provided to the BS as delay or jitter information. In other examples, the trend delay information or trend jitter information may be directly analyzed at the jitter determiner <NUM>, which may therefore provide jitter trend information after having directly analysed the evolution of the jitter.

On the basis of the jitter trend information it may be possible (e.g., by the BS and/or by the jitter determiner <NUM> and/or the scheduling/reallocation unit <NUM>) to foresee the future jitter, and, in case, to adopt a strategy to compensate it.

On the basis of the jitter trend information (e.g., in information <NUM>) as provided by the UE <NUM>, the BS may modify the length of the scheduling period and/or shift the scheduling period. The BS may, for example, calculate k1 and k2.

Even though reference is here made to SPS, it is possible to also refer to different techniques (the SPS_period may be the scheduling time period). It is here important to understand that the transmission configuration may be modified by the BS, on UE's demand, on the basis of the delay or jitter information <NUM> obtained by the jitter determiner <NUM>. The features of the embodiment E2 may be combined with those of the embodiment E1.

In some examples, there is the possibility of updating the SPS_period_1 by ± k * (s)TTIs, where k can be any arbitrary values based on the observed jitter; i.e., see the equation above in E2, equations (<NUM>) and (<NUM>).

where sym2 is <NUM> OFDM symbols, sym7 is <NUM>-OFDM symbols, etc.. ms stands for millisecond and ms0dot5 is <NUM> where, e.g., ms32 is <NUM>.

In some examples, there is the possibility of performing at least one of:.

Hence, in view of the above, it is possible to state that the UE may:.

In some examples, there may apply one of the following considerations:.

Different granularities may be used (e.g., it may be measured in sTTls, slots, mini-slots, durations of OFDM symbols, etc.). In some examples, k1 and k2 may be used for scaling time durations which may be one of sTTIs, slots, mini-slots, durations of OFDM symbols, etc..

This embodiment may also be illustrated as a variant of E2 and can be also shown in <FIG>. The UE <NUM> may be as in <FIG>.

In this embodiment, the UE <NUM> may send a feedback (step <NUM>) to the BS (e.g., gNB) with some information <NUM> (e.g., codified in a control data field) regarding the delay or jitter (delay or jitter information <NUM>) for adapting the CG/SPS accordingly. This may be via uplink (UL) control information (UCI) feedback and/or in Data control feedback and/or UE assisting information (all this information may be resumed with the concept of delay or jitter information). This UE assisting information may include information about the traffic arrival, delays, and data periodicity; this may be sent periodically or on-demand, according to the examples.

In addition or alternative, the BS (e.g., gNB) may sense or predict the jitter or decode the jitter from a UE assisting information. Herewith, the BS (e.g., gNB) may update the existing configuration period (with k1) or update the CG/SPS offset (with k2). Hence, the BS may send an SPS/Configured-Grant update message, e.g., RRC ConfiguredGrantConfigUpdate, with any of the following:.

Another example: any or all of the following can be sent via an update downlink control information (DCI) message, i.e., via L1-signaling (wherein L1 means physical layer):.

The features of the embodiment E2* may be combined with those of the embodiment E1 and/or E2.

In general terms, the UE <NUM> may be configured to receive, from the base station, BS, signalling regarding the transmission configuration. The signalling may be at least partially based on the at least one of the delay or jitter information (e.g., <NUM>), scheduling modification request, configuration modification request, and feedback information, so as to modify the transmission configuration and/or the scheduling. In addition or alternative, the UE may be configured to receive, from the BS, signalling regarding the transmission configuration, the signalling being at least partially based on measurements performed by the BS or by another device associate to the BS.

Hence, with the present embodiment, the UE may:.

In some examples, the BS may operate autonomously.

In some examples, at least one of the following may apply:.

In this embodiment, the UE <NUM> may send to the BS additional information (which may also be understood as delay or jitter information). In some examples, the UE may be as in <FIG>. The embodiment is also shown in <FIG>.

In order to minimize the observed jitter on application side, the UE <NUM> may request additional new SPS/CG configuration(s) by sending a jitter-correction report or extend one existing measurement REPORTS (e.g., CSI reports, SPS reports, or new reports). This report or feedback information can be conveyed via UCI message or in UL Data control information. At least one of the following assertions may be valid:.

Even though reference is here made to SPS, it is possible to also refer to different techniques (the SPS_period may be the scheduling time period). It is here important to understand that the transmission configuration may be modified by the BS, on the basis of the UE's feedback report demand, on the basis of the delay or jitter information <NUM> obtained by the jitter determiner <NUM>.

At least one of the following assertions may be valid, according to the examples:.

The following table describes a problem the embodiments solve:.

The request <NUM> may be a request including at least one of:.

The additional configuration request (<NUM>) may include a request of changed time length of the determined time period. In response, the BS may provide a changed time length of the determined time period. The UE may therefore change time length of the determined time period.

The additional configuration request (<NUM>) may include a request of changed time index or time offset of the determined time period. In response, the BS may provide a changed time index or time offset of the determined time period. The UE may therefore change the time index or time offset of the determined time period.

The UE may expect an additional configuration update message in the RRC including the updated time period. When received, the UE may update the time period.

The UE may expect an additional configuration update message in the L1 signalling, e.g., DCI, including the updated time period. When received, the UE may update the time period.

The additional configuration request (<NUM>) may include a request of both changed time index or time offset and changed time length of the determine time period. In response, the BS may provide both a changed time length of the determined time period a changed time index or time offset of the determined time period. The UE may therefore change the time length and the time index or time offset of the determined time period.

The UE may expect an additional configuration update message in the RRC including the updated time index or time offset. When received, the UE may update the time index or time offset.

The UE may expect an additional configuration update message in the L1 signalling, e.g., DCI, including the updated time index or time offset. When received, the UE may update the time index or time offset.

The may receive, from the base station, BS, signalling regarding the transmission configuration, the signalling being at least partially based on the at least one of the delay information (<NUM>) or jitter information (<NUM>) (<NUM>), scheduling modification request, configuration modification request, feedback information, and additional configuration request, so as to modify the transmission configuration and/or the scheduling.

The LUT <NUM> may provide a quantized version of at least some of the delay information or jitter information, so as to provide the quantized version or jitter information.

An example of active configuration is provided for TS <NUM>. The IE ConfiguredGrantConfig may be used to configure uplink transmission without dynamic grant according to two possible schemes. The actual uplink grant may either be configured via RRC (type1) or provided via the PDCCH (addressed to CS-RNTI) (type2).

The base station may be a gNB, an eNB, a coordinator, etc. A simplified example of BS <NUM> is shown in <FIG>. The BS <NUM> may always communicate in uplink (UL) or downlink (DL) with the UE <NUM> (and, in case, with other UEs), e.g., according to a communication standard (e.g., LTE, <NUM>, <NUM>, etc.).

The base station, BS <NUM> may comprise at least one of:.

In example, the scheduler <NUM> may be configured to define and/or adapt the scheduling on the basis of at least feedback information, from the UE, regarding the delay or jitter information and/or a scheduling modification request, from the UE, based on delay or jitter information [e.g., according to the UE measurements]. All this information may be indicated with <NUM>.

The scheduler <NUM> may be configured to update the length of the time period, e.g., on the basis of a feedback from the UE and/or on the basis of a request from the UE and/or on the basis of delay or jitter information from the UE. The scheduler <NUM> may be configured to update the index of the time period and/or to shift the time period, e.g., on the basis of a feedback from the UE and/or on the basis of a request from the UE and/or on the basis of delay or jitter information from the UE.

The scheduler <NUM> nay be configured to define and/or modify the scheduling period and/or the scheduling on the basis of at least one of:.

Other aspects of the scheduler <NUM> and/or BS <NUM> may be understood from the explanations above regarding the UE <NUM> (as the UL and/or DL and/or signalling transmissions may be performed with the BS <NUM> and/or on the basis of the scheduling defined by the scheduler <NUM>.

In some examples (e.g., embodiment E2* discussed above), the BS <NUM> may be configured to transmit signalling regarding the transmission configuration. The signalling may be at least partially based on the at least one of the delay or delay or jitter information (e.g., <NUM>), scheduling modification request, configuration modification request, and feedback information as transmitted from the UE to the BS. Accordingly, the BS may modify the transmission configuration and/or the scheduling.

In addition or alternative, the BS may transmit signalling regarding the transmission configuration, the signalling being at least partially based on measurements performed by the BS or by another device associate to the BS (e.g., another device at the network side).

In addition or alternative, the BS <NUM> may update the scheduling (e.g., by signalling values k1 and/or k2) to the UE.

<FIG> shows a unit <NUM> including the UE <NUM> (some elements not being shown) and the local external device <NUM>. The external device <NUM> may include a sensor <NUM> acquiring physical measurements on the environment (e.g., any of electrical, mechanical, chemical magnitude(s), etc.). The external device <NUM> may include a processor <NUM>. The external device <NUM> may include a timing (clock) module <NUM>, which is in principle different from the timing (clock) module <NUM> of the UE <NUM>. The external device <NUM> may (e.g., periodically) send (e.g., through electrical connections, e.g., without wireless connections) data packets <NUM>, <NUM> to the buffer <NUM> of the UE <NUM>.

The unit <NUM> may receive the data packets <NUM>, <NUM> from the external device <NUM> and retransmit them (as data packets 121t, 126t) to a remote unit <NUM> through the BS <NUM> (in <FIG> only one BS <NUM> is shown, but it is clear that a plurality of BSs may be involved, as a common network may be used). Techniques for transmitting the data packets 122t, 126t are discussed above.

The remote unit <NUM> may retransmit data packets (e.g., as packets 122tt, 126tt) to the unit <NUM> through the BS <NUM> and/or more in general through the network.

In some cases, the unit <NUM> may be a remote controller. In this case, the data packets <NUM>, <NUM> may refer to commands input by a user (e.g., through a joystick, an input/output, I/O, unit, an haptic interface, etc.), while the remote unit <NUM> may be a controlled system (e.g., an actuator which is moved according to the user's commands). In some cases, it is the opposite: the unit <NUM>, in this case, may obtain, at the device <NUM>, data packets <NUM>, <NUM> associated to feed ack measurements of the controlled physical system.

Hence, the units <NUM> and <NUM> form a remote system <NUM>. The remote system <NUM> may be, for example, an internet-of-things, loT, system.

Generally, examples may be implemented as a computer program product with program instructions, the program instructions being operative for performing one of the methods when the computer program product runs on a computer. The program instructions may for example be stored on a machine readable medium. Other examples comprise the computer program for performing one of the methods described herein, stored on a machine-readable carrier. In other words, an example of method is, therefore, a computer program having a program-instructions for performing one of the methods described herein, when the computer program runs on a computer. A further example of the methods is, therefore, a data carrier medium (or a digital storage medium, or a computer-readable medium) comprising, recorded thereon, the computer program for performing one of the methods described herein. The data carrier medium, the digital storage medium or the recorded medium are tangible and/or non-transitionary, rather than signals which are intangible and transitory. A further example of the method is, therefore, a data stream or a sequence of signals representing the computer program for performing one of the methods described herein. The data stream or the sequence of signals may for example be transferred via a data communication connection, for example via the Internet. A further example comprises a processing means, for example a computer, or a programmable logic device performing one of the methods described herein. A further example comprises a computer having installed thereon the computer program for performing one of the methods described herein. A further example comprises an apparatus or a system transferring (for example, electronically or optically) a computer program for performing one of the methods described herein to a receiver. In some examples, a programmable logic device (for example, a field programmable gate array) may be used to perform some or all of the functionalities of the methods described herein. In some examples, a field programmable gate array may cooperate with a microprocessor in order to perform one of the methods described herein. Generally, the methods may be performed by any appropriate hardware apparatus. The above described examples are merely illustrative for the principles discussed above. It is understood that modifications and variations of the arrangements and the details described herein will be apparent. It is the intent, therefore, to be limited by the scope of the claims and not by the specific details presented by way of description and explanation of the examples herein.

Examples discusses above and further examples of the present technique are here identified.

In examples above, some aspects relate to a user equipment, UE, including.

In examples above, some aspects relate to a unit comprising the UE as above and/or below and an external device configured to insert in the buffer data packet to be transmitted by the transmission unit of the UE, wherein the UE has a first timing (clock) module and the external device has a second timing (clock) module which is different from the first timing (clock) module [the timing of the insertion in the buffer may be theoretically the same as the time for transmitting by the UE, but at least by virtue of the drifts between the timings of the UE and the external device the timings actually do not coincide].

In examples above, some aspects relate to a base station, BS (e.g., gNB, e.g., for receiving data [e.g., in UL] from a UE) or a network coordinator [e.g., for vehicle to vehicle communications and/or user to user communications, comprising:.

The BS as above, wherein the scheduler may be configured to update the length of the time period, e.g., on the basis of a feedback from the UE and/or on the basis of a request from the UE and/or on the basis of jitter information from the UE. The BS as above, wherein the scheduler may be configured to update the index of the time period and/or to shift the time period, e.g., on the basis of a feedback from the UE and/or on the basis of a request from the UE and/or on the basis of jitter information from the UE.

In examples above, some aspects relate to a system comprising a BS and at least one UE, wherein:.

[Another possibility is to substitute the BS with a network coordinator, which may be another UE].

In examples above, some aspects relate to a UE [e.g., as any of the above] for the transmission [e.g., in UL to a BS and/or to a network coordinator], configured to:.

In examples above, some aspects relate to a UE [e.g., as any of the above] for the transmission [e.g., in UL to a BS and/or a network coordinator], configured to:.

In examples above, some aspects relate to a UE [e.g., as any of the above] for the transmission in[e.g., in UL to a BS and/or a network coordinator], configured to:.

measure [e.g., by the jitter determiner] a jitter trend information [e.g., the modification of the jitter between the current period and the previous period or an average, e.g., a weighted average, of the previous jitters][e.g., the jitter being between the arrival in the buffer and the transmission in UL and/or to a network coordinator], and/or
provide, as a feedback information [e.g., based on the jitter trend information] , information associated to at least one of the following scenarios:.

The UE may be further configured to:
request a particular scheduling period [e.g., SPS period] [e.g., to the BS and/or the network coordinator].

The UE may be further configured to:
request a particular shifting [e.g., by providing new_SPS_Index] [e.g., to the BS and/or the network coordinator].

The UE may be further configured to:
request a particular updating [e.g., by providing new_SPS_Period] of the length of the period [e.g., to the BS and/or the network coordinator].

The UE may be further configured to
provide a value of the jitter trend [e.g., to the BS and/or the network coordinator] [the jitter trend may be the increment on the jitter from the previous period to the current period and/or the increment on the jitter from an average regarding previous periods and the current period].

The UE may be further configured to
provide ratio_1 [which may be as in the description above] [e.g., to the BS and/or the network coordinator].

The UE may further comprise a lookup table, LUT, for providing a quantized version of the jitter information [e.g., of the jitter trend information][the LUT may have the values p1, p2, p3. stored so as to associate, to each range of the possible jitter information or jitter trend information, a quantized version thereof ], so as to provide the quantized version of the jitter information and/or jitter trend information [e.g., to provide the quantized version to the BS and to the network coordinator].

The UE may be further configured so as to, in case of determination of failure of the scheduling/modification, to perform a redundancy strategy.

The UE may be further configured, wherein a failure of the scheduling/modification is determined when no quantized version of the jitter information or jitter trend information is found (e.g., is not in the LUT).

The UE may be further configured, wherein a failure of the scheduling/modification is determined when the BS fails to modify the scheduling/modification [e.g., within a predetermined threshold].

The UE may be further configured, wherein a failure of the scheduling/modification is determined when the UE fails to obtain the jitter information or jitter trend information [e.g., within a predetermined threshold].

The UE may be further configured to estimate a hyper-period [e.g., as the least common multiple, LCM between the period as for the timing (clock) module of the UE and the period as for the timing (clock) module of the external device inserting the data packets onto the buffer]
The UE may be further configured to define the maximum allowed jitter between the length (e.g., sTTI) of the time slot for the first RV [and/or for a resource] and the length of the time period.

The UE may be further configured so that the number of configurations [and/or different allocations of resources] is associated to the length of the period and the maximum allowed jitter (e.g. the fraction between these values and/or the ceiling of the fraction, wherein the fraction may be, for example, the value of the hyper-period; other methods for calculating the hyper period may be carried out)
The UE may be further configured so that the number of configurations is associated to the hyper period.

The UE may be further configured so thatdifferent configurations have different resources for transmitting different RVs in different time slots.

The UE may be further configured so that the configurations are such that, for each time slot (e.g., sTTI), only one configuration transmits a data packet [e.g., a RV].

In examples above, some aspects relate to a BS, [e.g., as above] or a network coordinator comprising a scheduler configured to define and/or modify the scheduling period [e.g., SPS period] on the basis of at least one of:.

The BS or network coordinator may be further configured to receive the transmission from a UE.

In examples above, some aspects relate to a UE configured to carry out, as redundancy strategy [the redundancy strategy may be triggered by the determination of failure of the scheduling/modification and/or autonomously, e.g., by default]:.

The UE may be further configured to perform, as redundancy strategy:
in case the subsequent data packet arrives in the buffer before the first maximum jitter threshold, transmit the first RV of the subsequent data packet in the first resource of the subsequent period instead of the first RV of the first data packet.

The UE may be further configured to perform, as a redundancy strategy:
in case the first data packet arrives in the buffer after the first maximum jitter threshold [e.g., in time for transmitting the second RV but not in time for the first RV] but before a second maximum jitter threshold [e.g., in time for transmitting the second RV], to actually transmit the second RV of the first data packet.

In examples above, some aspects relate to a UE configured to perform, as a redundancy strategy:
perform transmissions [e.g., of first and/or second RVs] according to a periodic scheduling so that at least one first and second RVs of a first data packet are scheduled to be transmitted in the first and second scheduled resources of a first period and at least one first and second RVs of a subsequent data packet are to be transmitted in the first and second scheduled resources of a subsequent period; and/or
in case a first data packet arrives in the buffer after a first maximum jitter threshold [e.g., in time for transmitting the second RV but not in time for transmitting the first RV], reallocating the transmission of the first RV in the second resource in the same first period [e.g., without transmitting the second RV in the first period].

The UE may be further configured to perform, as redundancy strategy:
reallocate the transmission of the second RV in the first resource in the subsequent period.

The UE may be further configured to perform, as a redundancy strategy:
in case the subsequent data packet arrives in the buffer before the first maximum jitter threshold [e.g., in time for transmitting the first RV], avoid the transmission of the first RV of the first data packet and actually transmit the first RV of the subsequent data packet in the first resource.

In examples above, some aspects relate to a UE [e.g., as any of the UEs above] configured to perform, as redundancy strategy, transmit a plurality of RVs of the same data packet periodically arrived in a buffer, wherein at least one RV is a self-decodable RV and at least one RV is a non-self-decodable RV, configured to:
in case of late reception of a data packet after a first maximum jitter threshold for transmitting a first decodable RV but before a second maximum jitter threshold for transmitting a second non-decodable RV, to reallocate the transmission of the RVs so that:
at least one self-decodable RV is transmitted before at least one non-self-decodable RV.

The UE may be further configured to perform, as redundancy strategy:
reallocate a resource previously allocated to a non-self-decodable RV to a self-decodable RV in the same period [e.g., postponing or avoiding the transmission of the non-self-decodable RV].

The UE may be further configured to perform, as redundancy strategy:
in case in the subsequent period the subsequent data packet arrives in the buffer in time [e.g., before the first maximum jitter], transmit the first RV of the subsequent data packet instead of reallocating the resources for the non-self-decodable RV of the previous data packet.

[The UE above may send feedback information regarding the jitter, for example].

A storage unit may be configured to store instructions which, when executed by a processor, cause the processor to perform a method and/or to implement any of the functions above.

Claim 1:
A user equipment, UE, (<NUM>) for transmitting wireless transmissions, wherein the UE is adapted to:
receive data packets (<NUM>, <NUM>) from an external device (<NUM>) which is a local device;
transmit the data packets (<NUM>) according to a scheduling which allocates transmission resources in a determined time period (P);
determine a delay information (<NUM>) between the reception of a data packet (<NUM>, <NUM>) in the buffer (<NUM>) and the transmission of the data packet (<NUM>, <NUM>); and
modify the transmission configuration to switch from a first active configuration to a second active configuration,
wherein the active configurations are such that, for each time slot, only one active configuration transmits a data packet including an initial transmission and all the possible redundancy versions, RVs, of the data packet, wherein the UE is to receive a definition of the first active configuration (conf1) and second active configuration (conf2) in a BS's signalling,
wherein the UE is configured, when operating at the first active configuration and in case of late arrival of a data packet, to switch to the second active configuration for transmitting the late arrived data packet.