Average Per-Bit Delivery Cost, or APBDC, is the cost accounting method by which Internet Service Providers (ISPs) calculate their cost of goods sold. [1]
Average Per-Bit Delivery Cost divides the cost of however many bits were actually modulated across a network or component of a network over a period of time by the total operational and amortized capital expenses associated with the network or component over the same time-period, to produce an average cost for the delivery of each transmitted bit of data.[2] This is contrasted principally with flat-rate and 95th percentile functions, which are typically used for billing customers rather than cost accounting. In typical use, APBDCs of individual links or components of an operating network are compared with the APBDC of the whole, in order to evaluate the efficiency of the components and to track improvements in efficiency.[3][4]
High APBDC may reflect either a high cost or a low utilization, either of which is detrimental to the price/performance of the network as a whole, and indicates an area that needs attention and improvement. Besides reduction in costs of existing network components, use of already-amortized or less expensive components, and transmission of greater volumes of traffic, fundamental or "revolutionary" changes to the topology of a network, such as the substitution of peering-derived bandwidth for purchased transit, often have substantial impacts on a network's APBDC.[5]
The use of Internet Exchange Points (IXes or IXPs) to disintermediate ISP networks from sources of Internet bandwidth is a typical mechanism by which ISPs reduce their APBDC. Properly-sourced, bandwidth procured directly from its point of production in an IXP has a lower APBDC than bandwidth procured indirectly through an intermediary transit provider.[6][7][8][9][10]
Average Per-Bit Delivery Cost was first described under that name by Bill Woodcock in 2004, but built upon his previous work on Internet cost calculation, some of which was in collaboration with Andrew Odlyzko in the 1990s and with Zhi-Li Zhang and others in the early 2000s.[11][12][13][14][15]
In ISP-economic terms, the greater the portion of their bandwidth has an Average Per-Bit Delivery Cost (APBDC) lower than their current overall average, the more they've succeeded in driving down their APBDC over time. To succeed, they need to drive APBDC down faster than their competitors.
What SDx Applications Need from the Infrastructure: Efficiency: get more bandwidth, compute, and storage with fewer inputs (monetary or human); reduce average per-bit delivery cost.
An IXP reduces your average per-bit delivery cost by reducing a portion of your upstream traffic.
When two local networks are exchanging traffic, an IXP can reduce the portion of a network's traffic that must be delivered via upstream transit providers, thereby reducing the average per-bit delivery cost of service and latency as well as improving routing efficiency and fault-tolerance.
The Mwanza IXP is operated by TISPA in order to provide a neutral peering point for IP networks in Mwanza, Tanzania. This allows for local routing of Internet traffic in Mwanza, between network operators, via peering connections, reducing the average per-bit delivery cost for Internet traffic, reduce latencies, increase available bandwidth and improve quality of service.
The new exchange points will significantly reduce the average per-bit delivery cost of Internet services. This means that the price of the Internet for end-users will decrease significantly in the next few years.
IXPs enable local peering, which creates, in essence, a local network of networks and reduces the amount of an ISP's traffic that must be delivered via its upstream transit providers. And because traffic between local peers generally travels free, this can also help to reduce the average per-bit delivery cost while increasing efficiency and network resiliency.
