the coverage quality experienced by users influences the amount of data they are able to upload/download, and this aspect is captured by our system model and MEC design.

Network topology
----------------

The identity and positions of base stations $b\in{\mathcal{B}}$, as well as their demand $\delta(b,k,t)$ are readily available from the trace we describe in [Sec. \[sec:traces\]]{}. However, we have no information about the topology of the backhaul cellular network. Indeed, mobile operators are extremely reluctant to disclose this information, and virtually all works in the literature resort to synthetic topologies based on current best practices. Following [@softcell], we assume a [*fat-tree*]{} topology, where:

-   base stations are grouped into [*rings*]{} of ten;

-   every ten rings, there is an aggregation-level [*pod*]{};

-   every ten pods, there is a core-level switch.

The topology has a fan-out of $2$, i.e., we connect every ring to the two closest pods, and every pod to the two closest core switches, while switches themselves are connected in a full mesh. The network topology we generate can be represented as a graph ${\mathcal{G}}=({\mathcal{N}},{\mathcal{E}})$.

We also generate a DAG ${\mathcal{D}}=({\mathcal{N}},{\mathcal{F}})$, to keep track of which nodes can serve each base station. In particular, we generate a (directed) 