I Introduction
A key feature of the upcoming 5G technology is the support for UltraReliable and Low Latency Communication (URLLC) [carvalho2016random]. URLLC may be supported both through the 5G new air interface [ji2017introduction] or through the integration of different existing communication technologies [andrews2014will] [monserrat2015metis]
. URLLC will enable the support of new use cases with required packet delivery success probability as high as 5nines (
) to 9nines (), while at the same time the acceptable latency may be at the subsecond level or even down to a few milliseconds [ratasuk2015recent]. There are proposals for how to decrease the latency in future cellular systems, e.g., by reducing the Transmission Time Interval (TTI) [lahetkangas2014achieving, tullberg2014towards], fast uplink access [3GPPTR36881], or by puncturing URLLC resources on top of eMBB [ji2017introduction]. While 5G with URLLC support (rel. 16) is still several years from deployment, URLLC can already be achieved through integration of multiple communication technologies.The use of multiple communication technologies is conceptually very similar to many existing multipath protocols that increase endtoend reliability [qadir2015exploiting]. However, low latency requirements exclude reactive protocols that rely on, e.g. retransmission or backup paths. For low latency, we consider interface diversity which is in fact a type of path diversity [apostolopoulos2000reliable], where each path must use a different communication interface. The closest examples of related work that we have identified are the following. In [yap2012making, yap2013scheduling], the authors demonstrate the use of Software Defined Networking to distribute application packets across multiple available interfaces to increase application throughput. In [singh2016optimal], the authors consider fairness optimized multilink aggregation in heterogeneous wireless systems. Candidate architectures for enabling multiconnectivity and high reliability in 3GPP cellular systems are studied in [michalopoulos2016user] and [ravanshid2016multi]. Most recently, in [wolf2017diversity], the authors present a physical layer analysis of outage probability in multiconnectivity scenarios.
While the use of multiple interfaces, based on different technologies and potentially using independent paths, clearly improves reliability, we are in this work studying how also latency can be reduced using this technique. If the payload is split in parts and different parts are sent over each interface, it is possible to tradeoff latency and reliability according to the targeted application. We demonstrated this principle very simply in previous work [nielsen2016latency] and for the present paper we explore the principle in more details. Specifically, we extend our previous analyses as follows: 1) we demonstrate how coding can be exploited to enable flexible splitting of payload across interfaces; 2) we focus the analysis on independent wireless interfaces, whereas the previous work focused on a specific scenario with only two wireless interfaces; 3) we formulate the optimization problem of the optimal payload splitting problem as well as the generic evaluation method and present corresponding numerical results; and 4) we provide an analytic solution for the optimal split of data between two interfaces that minimizes the expected latency. 5) Finally, we use experimental latency data to validate the proposed methodology.
We initially present the system model and transmission strategies in sec. II. The methodology for calculating reliability of the considered strategies is presented together with the optimization problem in sec. III. In the following sec. IV we provide an analytical solution to the sub problem of splitting between two interfaces. Numerical results are given and discussed in sec. V, after which an experimental validation is presented in sec. VI. Conclusions are given in sec. VII.
Ii System model
We consider a MachinetoMachine (M2M) device, equipped with wireless communication interfaces that communicates critical information, e.g. sensor measurements or alarms messages, to a remote host. The model is depicted in Fig. 1. In this work we assume that interface failures occur independently and that measurements of endtoend delay and packet loss are available for the considered interfaces, e.g. through continual network monitoring.
Iia Transmission Strategies
For transmitting the stream of messages from M2M device to endhost, we consider the following strategies (see Fig. 2):
IiA1 Cloning
In this simple approach, the source device sends a full copy of each message through each of the available interfaces. Since only one copy is needed at the receiver to decode the message, cloning makes the communication robust at the expense of fold redundancy.
IiA2 Splitting
Instead of sending a full copy on each interface, only a fraction of the message is sent on each interface with this strategy. This allows to tradeoff reliability and latency through the selection of the fraction sizes. We assume that the payload is encoded, such that we can generate a desired number of coded fragments to be sent through different interfaces. This can be achieved using for example rateless codes [mackay2005fountain] or Reed Solomon codes [wicker1999reed]. The receiver will be able to decode the encoded message with very high probability as long as it receives coded fragments corresponding to approximately of the initial message size. A typical value is [mackay2005fountain] and we denote this threshold as . The coded fragments of a message that are to be sent over the same interface, are grouped together in a single packet to avoid excess protocol overhead. We assume that for a specific payload message, we let the used code (e.g. rateless or Reed Solomon based) generate coded fragments of a relatively small size, e.g. 10 bytes. When nonuniform, weighted splitting is used, the challenge is to determine how many fragments to assign to each interface. Depending on whether identical or different types of interfaces are used, splitting can be realized through either outof splitting or weighted splitting, respectively:
 outof

splitting generates equally sized coded fragments from the payload and the receiver needs to receive at least of them in order to decode the message. This strategy allows to trade off reliability and latency, since large redundancy leads to higher reliability but longer transmission times, whereas small redundancy offers a lower error protection but shorter transmission times.
 Weighted

the payload is split across interfaces so that the size of the perinterface packet is optimized according to a specific objective. That objective could be to minimize the expected overall transmission latency or to maximize the reliability for a given latency constraint. The optimal solution is, however not trivial, as our analysis shows.
IiB Latencyreliability Function
Typically, the duration of a packet transmission is depending on the packet size . As a result, we specify the latencyreliability function of interface as . This gives the probability of being able to transmit a data packet of bytes from a source to a destination via interface within a latency deadline . In other words, the value of is the achievable reliability for a latency and payload size . In the following, let specify the fraction of coded payload assigned to interface , where . Also, let refer to the longterm error or packet loss probability of an interface, as defined in references [strom20155g, nielsen2016latency].
Iii Reliability of interface diversity
This section presents the proposed methodologies for achieving reliability through interface diversity. Generally, we assume that the interfaces fail independently, i.e. that the interfaces do not have common error causes.
Iiia Evaluating reliability for weight assignment
The general approach to evaluating the latencyreliability function for a specific transmission strategy, is that we consider for each possible outcome (in terms of packet losses) if enough payload has been received to decode the message and then sum up the success probability according to the law of total probability. The steps to do this are explained in the following.
Note that payload assignments where should be avoided, as in such cases, the coded packets can never be decoded. For enumeration of all possible events, let be a matrix listing all possible outcomes for the interfaces, where a 0 or 1 denotes the successful or failed reception of a packet from the interface of that column:
(1) 
The element in the th row and th column of , refers to the th interface in the th outcome.
For a specific choice of , we use the law of total probability to evaluate the resulting latencyreliability function by summing the probability of all successful events. The successful events are the outcomes where the received coded packets can be decoded. The resulting latencyreliability function is:
(2) 
where
(3) 
ensures that we only include outcomes where at least the minimal number of payload fragments are received that allow to decode the payload. Further, is defined as:
(4) 
IiiB Cloning
For transmissions using packet cloning over interfaces that can justifiably be considered independent, e.g. cellular connecting to different eNBs or cellular from different operators, we can either use the method presented above or we can use the easier traditional parallel systems [rausand2004system] method to combine the latencyreliability functions as:
(5) 
In either case for .
IiiC outof splitting
While the outof splitting strategy is only optimal for the case of identical interfaces, it can in principle be used in any case, but with best results in situations where the properties of the available interfaces are comparable. Generally, we can evaluate the latencyreliability function using the method in sec. IIIA, with for . In the special case of identical interfaces, the resulting latencyreliability function can be calculated as:
(6) 
where and is the latencyreliability function that represents the identical interfaces.
IiiD Weighted splitting
The challenge of the weighted splitting scheme is to determine how many coded fragments to send on each interface to optimize a given utility function. This problem has degrees of freedom in the form of the payload allocation vector . Formally, this optimization problem can be phrased in the following way:
(7) 
where is evaluated using eq. (2) and the vectors and specify the targeted latency values to be maximized and their corresponding importance, respectively. For example, and would mean that reliability at 0.5 s is 10x more important than reliability at 0.2 s.
Assuming that the optimization is solved using a bruteforce search, the search space grows as , where is the step size between values. In practice, the computational tractability of a bruteforce search is therefore limited by the number of interfaces and choice of step size . The problem in eq. (7) does not immediately have an analytical solution, since the payload assignment weights in do not translate linearly into specific reliability values. Specifically, when increasing the value for an interface and thereby increasing the amount of coded payload, the reliability for a specific latency is going to decrease at some point due to the increasing packet size. However, at the same time a combination of two or more interfaces’ increasing values can add up to and thereby improve the overall reliability, even if the reliability of the individual interfaces is decreasing as goes up. This behavior, that the overall reliability decreases before it suddenly jumps up, combined with the fact that the value should be adjusted for each interface individually, narrows the possibilities for analytical solutions.
Therefore, for the numerical results, we include results from a bruteforce search that tries out all combinations of values on the different interfaces, with a step size that is coarse enough to make the search computationally tractable. While we have not managed to solve the whole optimization problem in eq. (7) analytically, we present in the following section an analytical solution to a subproblem of eq. (7). specifically, we consider how to optimally split coded payload between two interfaces A and B, so that the latency is minimized.
Iv Analysis of splitting between two interfaces
In the optimization problem, we assume the latency of each interface is represented by two Gaussian random variables
and . In the following we assume that and are constant and independent of and .When splitting the payload between two interfaces, the latency is defined by the time at which the last fragment is received. The expected latency is thus the expectation of
, which is also the first moment of the random variable
. By using the approximation of the expectation of the maximum of two normal random variables from [clark1961greatest], we obtain(8) 
where , , , and .
To find the minimum of the expected latency, we differentiate with respect to :
(9) 
In order to get the optimal solution, must hold. So we have the solution as follows:
which is equivalent to:
(10) 
V Numerical results
For the numerical results we will consider the different scenarios specified in Table II. The considered technologies are using the reliability specifications shown in Table I.
GPRS  EDGE  UMTS  HSDPA  LTE  
0.70  0.46  0.43  0.35  0.0067  
400  230  200  178  41  
0.984  0.983  0.982  0.981  0.980 
IF1  IF2  IF3  IF4  IF5  

UMTS  GPRS        1500 bytes  s  
LTE  HSDPA  UMTS  EDGE  GPRS  1500 bytes  s  
HSDPA  HSDPA  GPRS  GPRS  GPRS  1500 bytes  s 
While the distribution of latency measurements is usually longtailed [borella1997self, jacko2000effect]
, we will for simplicity use the normal probability distribution to generate latency distributions in the numerical results. While the used probability distribution of influences the specific results, the methods and general tendencies presented in this paper do not change. Specifically, we assume that the latency of transmissions of packet size
through a specific interface/path is Gaussian distributed with mean
defined as:(11) 
and due to lack of information about the distribution, we assume . The parameters and characterize the assumed linear relationship between packet size and delay for an interface. The values of and are shown in Table I. The values are derived from field measurements conducted by Telekom Slovenije within the SUNSEED project [sunseed2014web].
Initially, we study the simple scenario , for which we solved the weighted splitting between two interfaces analytically in sec. IV. That is, we used eq. (10) to determine the optimal splitting threshold . Notice that and are parametrized so that the numerical optimization calculates the expected latency as the analytical optimization. The results are shown in Fig. 3, and show a visually good correspondence between the analytical result and the bruteforce search. The bruteforce search has a slightly lower expected latency, due to the weight assignment being different. We attribute this minor difference to the use of the approximation of from [clark1961greatest].
In relation to the general idea of splitting, the most important question we seek to answer, is if it makes sense to spend the additional effort required to find the optimal values for a weighted splitting or if it suffices to use one of the simpler outof strategies. It is intuitively clear that if the used technologies are all identical, then a outof strategy will be optimal. But how much better is a weighted scheme in a heterogeneous scenario? To answer this we study three different scenarios that are specified in Table II.
The results for scenario in Fig. 4 show two examples of latencyreliability tradeoffs that are achieved by considering both when the starred and values in Table II are included and excluded. In both cases the weighted strategy achieves some reliability in the low latency region ( s) similar to the 1outof5 strategy and it has the reliability of the 2outof5 strategy around s. The difference between the 2 results is that the last one transmits more redundancy data and achieves higher reliability in the s region.
The results concerning scenario that are shown in Fig. 5 are interesting since they demonstrate a mixed data allocation. This results in the reliability at s being 0.9999, which is one decade better than any of the outof strategies that only go up to 0.999.
Vi Experimental validation
In addition to the theoretical and modelbased results presented above, we have also validated the proposed methods using traces of latency measurements for different communication technologies. Such traces were obtained by sending small (128 bytes) UDP packets every 100 ms between a pair of GPS timesynchronized devices through the considered interface (LTE, HSPA, or WiFi) during the course of a work day at Aalborg University campus. Each trace file can thus be used to playback a time sequence of oneway endtoend latencies. Our experimental results of multiinterface transmissions are obtained by playing back the three trace files at the same time time in a simulation, where for each 100 ms, the outcome of each considered strategy is recorded. When the playback simulation is done, a latencyreliability curve is calculated for each strategy as the cdf of the recorded outcomes in each 100 ms timestep. This is shown with crosses in Fig. 7. The validation consists in comparing these results to the results that are obtained by using the curves in Fig. 6 to compute the resulting latencyreliability curves using the methods described in sec. III. Those results are shown as lines in Fig. 7.
When considering the latencyreliability curves of the interfaces in Fig. 6 it is interesting that HSPA actually performs better than LTE. We believe that this is due to the fact that the majority of current mobile devices connect through LTE if it is available. Thus, the collocated HSPA network experiences a lighter load and allows for quicker access. Another interesting observation is that the WiFi network delivers very low latencies down to below 4 ms for 60% of packets. However, the 99th percentile latency of 75 ms is higher than both HSPA and LTE.
From the results in Fig. 7, we see how the 1outof3 strategy is able to outperform any individual interface, as expected. The plot does not include any result for the Weighted scheme, since the small payload size does not allow for any gain through payload splitting. The lines that represent the theoretical calculation of performance are practically coinciding with the crosses representing the experimental results. This shows that the methods for calculating the resulting performance by relying on the latencyreliability curves of the interfaces, as described in Sec. III, indeed produces accurate results when used with actual traffic traces.
Vii Conclusions and Outlook
One of the most demanding modes in the upcoming 5G systems will be UltraReliable Low Latency Communication (URLLC). In many cases it should be provided by taking advantage of the fact that multiple communication interfaces are available at the devices. In this work we have studied the concept of interface diversity, where multiple communication interfaces and paths are used simultaneously to communicate between two end devices. The use of coding allows us to assign an arbitrary amount of coded payload data to each interface, allowing to tradeoff latency and reliability. We have formulated the optimization problem to find the payload allocation weights (denoted ) that maximize the reliability at specific target latency values. We have provided and validated an analytic solution to the subproblem of splitting between two interfaces so that the expected latency is minimized. By considering different scenarios and numerically solving the full optimization problem for specific target latencies, we have found that optimized strategies can significantly outperform outof strategies, where the latter do not account for the characteristics of the different interfaces. Finally, we have experimentally validated the proposed method of computing the resulting performance, and demonstrated the practical gains of interface diversity.
Acknowledgment
This work is partially funded by EU, under Grant agreement no. 619437. The SUNSEED project is a joint undertaking of 9 partner institutions and their contributions are fully acknowledged. The work was also supported in part by the European Research Council (ERC Consolidator Grant no. 648382 WILLOW) within the Horizon 2020 Program.