<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>Wireless Networks · Jared Lynskey</title>
    <link>https://jared.lynskey.co.nz/en/tags/wireless-networks/</link>
    <description>Short stories of value on software engineering and engineering leadership — performance reviews, hiring and scaling teams, CI/CD, DevOps monitoring and agentic AI. Written from Seoul.</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>© 2026 Jared Lynskey</copyright>
    <lastBuildDate>Wed, 28 Oct 2026 00:00:00 +1300</lastBuildDate>
    <atom:link href="https://jared.lynskey.co.nz/en/tags/wireless-networks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>UAV Networks: Drones in 5G and Where to Put Drone Ports</title>
      <link>https://jared.lynskey.co.nz/en/posts/2019/2019-01-26-dronesandstuff/</link>
      <guid isPermaLink="true">https://jared.lynskey.co.nz/en/posts/2019/2019-01-26-dronesandstuff/</guid>
      <pubDate>Mon, 01 Apr 2019 00:00:00 +0000</pubDate>
      <dc:creator>Jared Lynskey</dc:creator>
      <category>UAV</category>
      <category>Drones</category>
      <category>Wireless Networks</category>
      <category>5G</category>
      <category>Research</category>
      <description>What a UAV network is, how drones serve as aerial base stations or as aerial users in 5G wireless networks, two papers that shaped my thinking, and my own research on where to put drone ports.</description>
      <content:encoded><![CDATA[<p>A UAV network is a wireless network in which drones (unmanned aerial vehicles) take part in one of two ways. Either they fly as aerial base stations or relays, bringing coverage and capacity to places the ground network can&rsquo;t reach or can&rsquo;t keep up with, or they are aerial users, connected to the cellular network much like a phone, that the network has to serve in three dimensions.</p>

<h2 class="relative group">Background
    <div id="background" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#background" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>Since affordable drones arrived, the number of people using them has kept climbing, mostly because they&rsquo;re highly mobile and can do jobs in the air that are awkward to do any other way. With 5G just around the corner, researchers are looking for better ways to place drones, both in the air and on the ground between flights. Get the placement right and cellular connectivity improves, and the average latency between aerial user equipment and equipment on the ground comes down.</p>

<h2 class="relative group"><a href="https://arxiv.org/pdf/1803.00680.pdf"  target="_blank" rel="noreferrer">A Tutorial on UAVs for Wireless Networks: Applications, Challenges, and Open Problems</a>
    <div id="a-tutorial-on-uavs-for-wireless-networks-applications-challenges-and-open-problems" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#a-tutorial-on-uavs-for-wireless-networks-applications-challenges-and-open-problems" aria-label="Anchor">#</a>
    </span>
    
</h2>

<h3 class="relative group">Types of UAVs
    <div id="types-of-uavs" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#types-of-uavs" aria-label="Anchor">#</a>
    </span>
    
</h3>
<p><figure><span class="mc-img" style="--lqip:url('data:image/webp;base64,UklGRuIAAABXRUJQVlA4INYAAAAQBwCdASogAB0APwVepEeloiGb+qwAWxBE9IAECudSvd08N60CSRoeHXv6Xu9QYcR+cvqaLVDLz3lvg6Hg/0ekAAD+9+kuPYFMzi20vG4lEu61apqJSC8Os2/h0QYkk+dtMPrbkXV9WkD+FgTx1JSgsMGMPw4WNWe9xagxWykjkB/142WVKtTIoK4hQhtfeJzer9gwtp1Yg2CTcrdMTA7WBu4GQyUpuDsJLrDP7ex4mRkQgCgG/UH+BrV4eElecsZztyG1poGMId96OAPli9Ad0LNy3YAA')"><img
    class="my-0 rounded-md"
    loading="lazy"
    decoding="async"
    fetchpriority="auto"
    alt="Class of drones"
    width="674"
    height="617"
    src="https://jared.lynskey.co.nz/img/posts/drones/typesofdrones_hu_2e556dd88573eba4.webp"
    srcset="https://jared.lynskey.co.nz/img/posts/drones/typesofdrones_hu_2e556dd88573eba4.webp 800w, https://jared.lynskey.co.nz/img/posts/drones/typesofdrones_hu_2e556dd88573eba4.webp 1280w"
    sizes="(min-width: 768px) 50vw, 65vw"
    data-zoom-src="https://jared.lynskey.co.nz/img/posts/drones/typesofdrones_hu_2e556dd88573eba4.webp"></span></figure>
</p>
<p>Paper [1] sorts UAVs into a tree that branches out into sub-classes.</p>
<p><figure><span class="mc-img" style="--lqip:url('data:image/webp;base64,UklGRmoAAABXRUJQVlA4IF4AAADwAwCdASogAAgAPw1mpkemIqGYBABjEMT0gAAzNpjR8uhHQKdmZPmsAP7qpiyVkPAkZHI5rBbHE+Y9h18JFzbOOgSR+U+/qhhcnoSIKrS8Hv0Na5lcdZaMqP0lHAAA')"><img
    class="my-0 rounded-md"
    loading="lazy"
    decoding="async"
    fetchpriority="auto"
    alt="Class of drones"
    width="808"
    height="199"
    src="https://jared.lynskey.co.nz/img/posts/drones/classofdrones_hu_665185a1b98d04bf.webp"
    srcset="https://jared.lynskey.co.nz/img/posts/drones/classofdrones_hu_665185a1b98d04bf.webp 800w, https://jared.lynskey.co.nz/img/posts/drones/classofdrones_hu_b49f029e7e0c8d8e.webp 1280w"
    sizes="(min-width: 768px) 50vw, 65vw"
    data-zoom-src="https://jared.lynskey.co.nz/img/posts/drones/classofdrones_hu_b49f029e7e0c8d8e.webp"></span></figure>
</p>

<h2 class="relative group"><a href="https://arxiv.org/pdf/1805.06532.pdf"  target="_blank" rel="noreferrer">Beyond 5G with UAVs: Foundations of a 3D Wireless Cellular Network</a>
    <div id="beyond-5g-with-uavs-foundations-of-a-3d-wireless-cellular-network" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#beyond-5g-with-uavs-foundations-of-a-3d-wireless-cellular-network" aria-label="Anchor">#</a>
    </span>
    
</h2>

<h3 class="relative group">Introduction
    <div id="introduction" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#introduction" aria-label="Anchor">#</a>
    </span>
    
</h3>
<ul>
<li>Drones in large numbers will have a big effect on wireless networks.</li>
<li>Applications include thermal imaging, package delivery and aerial base stations.</li>
<li>The paper looks at low-altitude drone user equipment in a 3D space, served by access points on high-altitude platforms, which are UAVs such as blimps.</li>
</ul>

<h3 class="relative group">Background
    <div id="background-1" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#background-1" aria-label="Anchor">#</a>
    </span>
    
</h3>
<ul>
<li>Earlier work ignored drones that are themselves user equipment (UE) in flight.</li>
<li>Earlier work on user association in drone networks didn&rsquo;t consider aerial base stations.</li>
</ul>

<h3 class="relative group">System Model
    <div id="system-model" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#system-model" aria-label="Anchor">#</a>
    </span>
    
</h3>
<ul>
<li>Two kinds of drone: high-altitude drones act as access points for low-altitude drone UEs.</li>
</ul>
<a href="https://arxiv.org/pdf/1805.06532.pdf">
![System Model](/img/posts/drones/systemmodel.jpg)
</a>

<h2 class="relative group">Transport Theory
    <div id="transport-theory" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#transport-theory" aria-label="Anchor">#</a>
    </span>
    
</h2>
<a href="https://arxiv.org/pdf/1805.06532.pdf">
![System process](/img/posts/drones/model.jpg)
</a>
- The authors use optimal transport theory to decide which aerial base station each drone UE connects to. In their simulations it cut average latency by up to 46% compared with classical SINR-based association.

<h2 class="relative group">My Contribution
    <div id="my-contribution" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#my-contribution" aria-label="Anchor">#</a>
    </span>
    
</h2>

<h3 class="relative group"><a href="https://www.mdpi.com/2073-8994/11/1/118/pdf"  target="_blank" rel="noreferrer">Facility Location Problem Approach for Distributed Drones</a>
    <div id="facility-location-problem-approach-for-distributed-drones" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#facility-location-problem-approach-for-distributed-drones" aria-label="Anchor">#</a>
    </span>
    
</h3>
<p>The paper starts from two gaps: governments and aviation agencies are bound to restrict where drones can take off and land, and most drone research assumes where a drone starts without justifying it. We proposed drone ports, fixed places for drones to take off, land and charge, and an algorithm derived from the facility location problem that picks them from a set of candidate sites to minimise the average distance drones travel to the tasks in an area. It gives a near-optimal placement that reduces the drones&rsquo; overall energy use. We then applied several travelling salesman algorithms to find the shortest route for a drone to visit all its tasks.</p>
<p><figure><span class="mc-img"><img
    class="my-0 rounded-md"
    loading="lazy"
    decoding="async"
    fetchpriority="auto"
    alt="Drone port placement"
    width="960"
    height="720"
    src="https://jared.lynskey.co.nz/img/posts/drones/droneportplacement_hu_8a94891646f0e7cb.webp"
    srcset="https://jared.lynskey.co.nz/img/posts/drones/droneportplacement_hu_8a94891646f0e7cb.webp 800w, https://jared.lynskey.co.nz/img/posts/drones/droneportplacement_hu_7d7848c7ddbfb52.webp 1280w"
    sizes="(min-width: 768px) 50vw, 65vw"
    data-zoom-src="https://jared.lynskey.co.nz/img/posts/drones/droneportplacement_hu_7d7848c7ddbfb52.webp"></span></figure>
</p>
<p>The figure above shows the idea: put drone ports where demand is high. The larger coloured ports are the ones chosen as optimal, and the smaller greyed-out ones are candidate locations that didn&rsquo;t make the cut.</p>

<h3 class="relative group"><a href="https://en.wikipedia.org/wiki/Facility_location_problem"  target="_blank" rel="noreferrer">Facility Location Problem</a>
    <div id="facility-location-problem" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#facility-location-problem" aria-label="Anchor">#</a>
    </span>
    
</h3>
<p>Framing it as a facility location problem turns drone port placement into an optimisation problem: given a budget and a set of candidate locations, find the best places to put the ports.</p>

<h2 class="relative group">References
    <div id="references" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#references" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p><a href="https://arxiv.org/pdf/1803.00680.pdf"  target="_blank" rel="noreferrer">[1] Mozaffari, Mohammad, et al. &ldquo;A tutorial on UAVs for wireless networks: Applications, challenges, and open problems.&rdquo; arXiv preprint arXiv:1803.00680 (2018).</a></p>
<p><a href="https://arxiv.org/pdf/1805.06532.pdf"  target="_blank" rel="noreferrer">[2] Mozaffari, Mohammad, et al. &ldquo;Beyond 5G with UAVs: Foundations of a 3D wireless cellular network.&rdquo; IEEE Transactions on Wireless Communications 18.1 (2019): 357-372.</a></p>
<p><a href="https://www.mdpi.com/2073-8994/11/1/118/pdf"  target="_blank" rel="noreferrer">[3] Lynskey, Jared, et al. &ldquo;Facility Location Problem Approach for Distributed Drones.&rdquo; Symmetry 11.1 (2019): 118.</a></p>
]]></content:encoded>
      <media:content url="https://jared.lynskey.co.nz/en/posts/2019/2019-01-26-dronesandstuff/featured.jpeg" medium="image" type="image/jpeg" />
    </item>
    <item>
      <title>What Is Age of Information (AoI)? The Freshness Metric, Explained</title>
      <link>https://jared.lynskey.co.nz/en/posts/2019/2019-01-23-ageofinformation/</link>
      <guid isPermaLink="true">https://jared.lynskey.co.nz/en/posts/2019/2019-01-23-ageofinformation/</guid>
      <pubDate>Wed, 23 Jan 2019 00:00:00 +0000</pubDate>
      <dc:creator>Jared Lynskey</dc:creator>
      <category>Age of Information</category>
      <category>Wireless Networks</category>
      <category>5G</category>
      <category>IoT</category>
      <category>Reinforcement Learning</category>
      <category>Research</category>
      <description>Age of Information (AoI) measures how old the freshest update at a receiver is. What the metric means, how it differs from latency, why updating too often hurts, and two 5G scheduling papers.</description>
      <content:encoded><![CDATA[<p>Age of Information (AoI) measures how fresh the information at a receiver is. At any moment t, the age is Δ(t) = t − u(t), where u(t) is the generation time of the newest update the receiver has. If the latest sensor reading on a dashboard was taken four seconds ago, the age is four seconds, and it keeps growing until a newer reading arrives.</p>
<p>That makes it different from latency, which is the delay of each individual packet, and from throughput, which counts how many packets get through. You can do badly on age in two opposite ways: send updates too rarely and the receiver is left holding old information; send them so often that queues build up, and every update is already stale by the time it arrives.</p>

<h2 class="relative group">How old is your data?
    <div id="how-old-is-your-data" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#how-old-is-your-data" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>Data timeliness is one of the six criteria I identified while working at Methanex NZ, and the idea behind it is simple: new information is worth much more than old. Recently, researchers have been proposing algorithms that schedule data collection from sensors and IoT devices so as to minimise the Age of Information in next-generation (5G) wireless networks.</p>

<h2 class="relative group">Data quality
    <div id="data-quality" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#data-quality" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>I researched data quality during my time at Methanex NZ, and these were the key points I identified for judging the quality of data:</p>
<ul>
<li>Timeliness: how much value the data still has at the moment it&rsquo;s used.</li>
<li>Completeness: how much of the data is in the system, with no missing fields.</li>
<li>Consistency: how well the data is kept consistent.</li>
<li>Confidence: how far you can trust the source of the data.</li>
<li>Accuracy: how well the data represents reality.</li>
<li>Integrity: the number of sources, and how consistent the data is across them.</li>
</ul>

<h3 class="relative group">Welcome to the age of data.
    <div id="welcome-to-the-age-of-data" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#welcome-to-the-age-of-data" aria-label="Anchor">#</a>
    </span>
    
</h3>
<p><figure><span class="mc-img" style="--lqip:url('data:image/webp;base64,UklGRpQBAABXRUJQVlA4IIgBAACwBwCdASogAB8APwlqqUeloyIYDAYAWxCE9IAJAD6CMA7AgwJUD3MkkV8U8SA+m+X7qXS99SMA1snvyAv2aEd+qTBtrYYAAP7nwjjtrNNEwsmemcv8B8j0sw1DwgAMMLZNpvlHTlNZIvHjPbbFn7d21fnUQvnu2Gf8QEBAtNyh1EMozr2kjfovtNVLlGjpwzZx3IGc7ViLeIFsmk+4jR5+HGM3cGXDz3fr+QxxpDiIVQlBop3AnO47NMz4AwXzoTWr5t06i4YRx70ZdThfM4RNJ2AVLrGuQrWT+lcsOT2Zpuc1KUuLFgk29XG0ry4eZaGm9xe+it2NW9NzA5UPq/Zv+9y9Ne+/XdIuB/0t6nGs61xErlxV4T57G2qmuR/F+poVs5D1beL7QrMmOZGWz59rIvXNViK0fx+HHFdBZS+vz/uvB718v3/0cI6/aFSf0uolCJJfYtSwM1v1P2Dytj7OCjBwFQaf5XoP2a+OnbLr2TSf3Tjden//tLrXpZK/Kw/IWzgAwAAAAA==')"><img
    class="my-0 rounded-md"
    loading="lazy"
    decoding="async"
    fetchpriority="auto"
    alt="Data Timeliness"
    width="544"
    height="525"
    src="https://jared.lynskey.co.nz/img/posts/aoi/timeliness_hu_b64fe5e2aaffc525.webp"
    srcset="https://jared.lynskey.co.nz/img/posts/aoi/timeliness_hu_b64fe5e2aaffc525.webp 800w, https://jared.lynskey.co.nz/img/posts/aoi/timeliness_hu_b64fe5e2aaffc525.webp 1280w"
    sizes="(min-width: 768px) 50vw, 65vw"
    data-zoom-src="https://jared.lynskey.co.nz/img/posts/aoi/timeliness_hu_b64fe5e2aaffc525.webp"></span></figure>
</p>

<h2 class="relative group">Age of Information
    <div id="age-of-information" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#age-of-information" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>Age of Information is about the freshness of data <a href="https://arxiv.org/pdf/1811.06776.pdf"  target="_blank" rel="noreferrer">[1]</a>. Interest in it has grown with the move from 4G to 5G, which puts far more weight on wireless service for Internet of Things (IoT) devices and machine-type communication (MTC) <a href="http://vbn.aau.dk/files/208323943/Five_disruptive_technology_directions_for_5G.pdf"  target="_blank" rel="noreferrer">[2]</a>.</p>

<h2 class="relative group">The key ideas: the sawtooth, average age and peak age
    <div id="the-key-ideas-the-sawtooth-average-age-and-peak-age" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-key-ideas-the-sawtooth-average-age-and-peak-age" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>Plot the age over time and you get a sawtooth. Between updates it climbs steadily, one second of age per second. When a new update arrives the age drops, but not to zero: it drops to the time that update spent in transit, because it was already that old when it landed.</p>
<p>Two numbers summarise the curve. Average AoI is the area under the sawtooth divided by the time observed, so it&rsquo;s the age you&rsquo;d see at a random moment. Peak AoI is the average height of the teeth, the age just before each update lands, which is easier to analyse and tells you how stale things get at worst in a typical cycle.</p>
<p>The classic early result comes from Kaul, Yates and Gruteser&rsquo;s 2012 paper, &ldquo;Real-time status: How often should one update?&rdquo; <a href="https://doi.org/10.1109/INFCOM.2012.6195689"  target="_blank" rel="noreferrer">[4]</a>. They modelled updates passing through a single first-come-first-served queue (M/M/1), with service rate μ and utilisation ρ (how busy the link is), and showed that the average age is</p>
<div class="highlight-wrapper"><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">Δ = (1/μ) × (1 + 1/ρ + ρ² / (1 − ρ))</span></span></code></pre></div></div>
<p>The 1/ρ term punishes sending too rarely, and the ρ²/(1 − ρ) term punishes sending so much that a queue builds up. Age is lowest at ρ ≈ 0.53, with the link idle almost half the time. Maximising throughput would push ρ towards 1, and minimising the delay of each packet would push it towards 0; freshness wants neither. That is the whole case for the metric in one line: the best update rate for freshness is one that neither throughput nor delay would choose.</p>

<h2 class="relative group">Two papers on scheduling for AoI
    <div id="two-papers-on-scheduling-for-aoi" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#two-papers-on-scheduling-for-aoi" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p><strong><a href="https://arxiv.org/pdf/1811.06776.pdf"  target="_blank" rel="noreferrer">Reinforcement Learning Based Scheduling Algorithm for Optimizing Age of Information in Ultra Reliable Low Latency Networks [1]</a></strong></p>
<p>The authors consider a factory where a number of sensors constantly transmit data about their current state. The sensors have no on-device storage, so a sensor&rsquo;s present state is only recorded if the remote scheduler selects its signal; the scheduler&rsquo;s access point ignores the rest. That leaves the scheduler with a dilemma: how to choose among sensors with different thresholds and packet sizes so that none of their timing requirements are violated. &ldquo;The <a href="https://arxiv.org/pdf/1811.03981.pdf"  target="_blank" rel="noreferrer">URLLC</a> term minimization is represented by ensuring that the probability the AoI of each sensor exceeds a predefined threshold should be at its minimum.&rdquo; To solve this formulation, they train a reinforcement learning scheduler with an actor-critic algorithm.</p>
<p><figure><span class="mc-img" style="--lqip:url('data:image/webp;base64,UklGRpoAAABXRUJQVlA4II4AAAAQBQCdASogABIAPw1qp0emIyGYBABjEMT0gAAzjBOE/rhiujJf/o74M4IBWnms6MAAAP7oawqJ1MlHms83wrVJX6ylBf/Wnc3i/fwuz0B+7ZdulqK+oMZB7enI8U6Y5MJMUDOsa3vHMZbPtjewBzOe6ockB7UkhGkbIQQsHFZC1ys/qs+7LR160HgwAAAA')"><img
    class="my-0 rounded-md"
    loading="lazy"
    decoding="async"
    fetchpriority="auto"
    alt="Data Timeliness"
    width="864"
    height="492"
    src="https://jared.lynskey.co.nz/img/posts/aoi/fig2_hu_46672781e84592b.webp"
    srcset="https://jared.lynskey.co.nz/img/posts/aoi/fig2_hu_46672781e84592b.webp 800w, https://jared.lynskey.co.nz/img/posts/aoi/fig2_hu_5b24b8041901aba4.webp 1280w"
    sizes="(min-width: 768px) 50vw, 65vw"
    data-zoom-src="https://jared.lynskey.co.nz/img/posts/aoi/fig2_hu_5b24b8041901aba4.webp"></span></figure>
</p>
<p><strong><a href="https://arxiv.org/pdf/1811.06453.pdf"  target="_blank" rel="noreferrer">Minimizing the Age of Information from Sensors with Correlated Observations [3]</a></strong></p>
<p>This paper studies &ldquo;the average AoI in a generic setting with correlated sensor information.&rdquo; Each update from a physical source can be picked up by several sensors, so their observations overlap, and there&rsquo;s no point in the access point collecting the same update twice. The authors propose two scheduling policies: one that needs the system&rsquo;s parameters to be known in advance, and one based on contextual bandits that learns them as it goes. Both exploit the overlap between sensors to cut the age by a wide margin compared with random or round-robin schedules.</p>
<p><figure><span class="mc-img" style="--lqip:url('data:image/webp;base64,UklGRowAAABXRUJQVlA4IIAAAACwBQCdASogABEAPw10rU0mIyIhKAqoxiGJ6QAMKSCFiO+x6mfXYvXHMA1NpQu11vTeec4axgAA/u3Xs0bueEewbzk0ta/hDGufiwa6AX2Y1teqfcI0YrudzPcgk4hmv0HLnGpXgbJmOjIlVoBNPyuDEGQosWKv7fxS5yWKAAAAAA==')"><img
    class="my-0 rounded-md"
    loading="lazy"
    decoding="async"
    fetchpriority="auto"
    alt="Data Timeliness"
    width="974"
    height="525"
    src="https://jared.lynskey.co.nz/img/posts/aoi/fig1_hu_e5f6a34b048e4b89.webp"
    srcset="https://jared.lynskey.co.nz/img/posts/aoi/fig1_hu_e5f6a34b048e4b89.webp 800w, https://jared.lynskey.co.nz/img/posts/aoi/fig1_hu_ba3ea4a8d5417f99.webp 1280w"
    sizes="(min-width: 768px) 50vw, 65vw"
    data-zoom-src="https://jared.lynskey.co.nz/img/posts/aoi/fig1_hu_ba3ea4a8d5417f99.webp"></span></figure>
</p>

<h2 class="relative group">References
    <div id="references" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#references" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p><a href="https://arxiv.org/pdf/1811.06776.pdf"  target="_blank" rel="noreferrer"> [1] Elgabli, A., Khan, H., Krouka, M., &amp; Bennis, M. (2018). Reinforcement learning based scheduling algorithm for optimizing age of information in ultra reliable low latency networks. arXiv preprint arXiv:1811.06776. </a></p>
<p><a href="http://vbn.aau.dk/files/208323943/Five_disruptive_technology_directions_for_5G.pdf"  target="_blank" rel="noreferrer"> [2] Boccardi, Federico, et al. &ldquo;Five disruptive technology directions for 5G.&rdquo; IEEE Communications Magazine 52.2 (2014): 74-80.</a></p>
<p><a href="https://arxiv.org/pdf/1811.06453.pdf"  target="_blank" rel="noreferrer"> [3] Kalør, Anders E., and Petar Popovski. &ldquo;Minimizing the Age of Information from Sensors with Correlated Observations.&rdquo; arXiv preprint arXiv:1811.06453 (2018). Later versions are titled &ldquo;&hellip;with Common Observations&rdquo;.</a></p>
<p><a href="https://doi.org/10.1109/INFCOM.2012.6195689"  target="_blank" rel="noreferrer"> [4] Kaul, S., Yates, R., &amp; Gruteser, M. (2012). Real-time status: How often should one update? Proceedings of IEEE INFOCOM 2012, 2731-2735.</a></p>
<p>Further reading: the best place to start is the survey by Yates, Sun, Brown, Kaul, Modiano and Ulukus, <a href="https://arxiv.org/abs/2007.08564"  target="_blank" rel="noreferrer">&ldquo;Age of Information: An Introduction and Survey&rdquo;</a> (IEEE Journal on Selected Areas in Communications, 39(5), 2021). For a whole book on the subject, there&rsquo;s <em>Age of Information: Foundations and Applications</em>, edited by Pappas, Abd-Elmagid, Zhou, Saad and Dhillon (Cambridge University Press, 2023).</p>
]]></content:encoded>
      <media:content url="https://jared.lynskey.co.nz/en/posts/2019/2019-01-23-ageofinformation/featured.jpeg" medium="image" type="image/jpeg" />
    </item>
  </channel>
</rss>
