From: Robert McMahon <rjmcmahon@rjmcmahon.com>
To: Mike Puchol <mike@starlink.sx>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
Rpm <rpm@lists.bufferbloat.net>,
libreqos <libreqos@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Rpm] [Starlink] On FiWi
Date: Tue, 14 Mar 2023 10:06:29 -0700 [thread overview]
Message-ID: <89c55d67-86f0-494d-a09e-c9aeebe46dc0@rjmcmahon.com> (raw)
In-Reply-To: <f0cde647-0295-4dbd-9e0a-e39177e7338f@rjmcmahon.com>
[-- Attachment #1: Type: text/plain, Size: 9523 bytes --]
The ISP could charge per radio head and manage the system from a FiWi head end which they own. Virtualize the APs. Get rid of SoC complexity and costly O&M via simplicity. Eliminate all the incremental engineering that has gone astray, e.g. bloat and over powered APs.
Bob
On Mar 14, 2023, 9:49 AM, at 9:49 AM, Robert McMahon <rjmcmahon@rjmcmahon.com> wrote:
>Hi Mike,
>
>I'm thinking more of fiber to the room. The last few meters are wifi
>everything else is fiber.. Those radios would be a max of 20' from the
>associated STA. Then at phy rates of 2.8Gb/s per spatial stream. The
>common MIMO is 2x2 so each radio head or wifi transceiver supports
>5.6G, no queueing delay. Wholesale is $5 and retail $19.95 per
>pluggable transceiver. Sold at Home Depot next to the irrigation aisle.
>10 per house is $199 and each room gets a dedicated 5.8G phy rate. Need
>more devices in a space? Pick an RRH with more cmos radios. Also, the
>antennas would be patch antenna and fill the room properly. Then plug
>in an optional sensor for fire alerting.
>
>
>A digression. A lot of signal processing engineers have been working on
>TX beam forming. The best beam is fiber. Just do that. It even can turn
>corners and goes exactly to where it's needed at very low energies.
>This is similar to pvc pipes in irrigation systems. They're designed to
>take water to spray heads.
>
>The cost is the cable plant. That's labor more than materials. Similar
>for irrigation, pvc is inexpensive and lasts decades. A return labor
>means use future proof materials, e.g. fiber.
>
>Bob
>
>
>
>On Mar 14, 2023, 4:10 AM, at 4:10 AM, Mike Puchol via Rpm
><rpm@lists.bufferbloat.net> wrote:
>>Hi Bob,
>>
>>You hit on a set of very valid points, which I'll complement with my
>>views on where the industry (the bit of it that affects WISPs) is
>>heading, and what I saw at the MWC in Barcelona. Love the FiWi term
>:-)
>>
>>I have seen the vendors that supply WISPs, such as Ubiquiti, Cambium,
>>and Mimosa, but also newer entrants such as Tarana, increase the
>>performance and on-paper specs of their equipment. My examples below
>>are centered on the African market, if you operate in Europe or the
>US,
>>where you can charge customers a higher install fee, or even charge
>>them a break-up fee if they don't return equipment, the economics
>work.
>>
>>Where currently a ~$500 sector radio could serve ~60 endpoints, at a
>>cost of ~$50 per endpoint (I use this term in place of ODU/CPE, the
>>antenna that you mount on the roof), and supply ~2.5 Mbps CIR per
>>endpoint, the evolution is now a ~$2,000+ sector radio, a $200
>>endpoint, capability for ~150 endpoints per sector, and ~25 Mbps CIR
>>per endpoint.
>>
>>If every customer a WISP installs represents, say, $100 CAPEX at
>>install time ($50 for the antenna + cabling, router, etc), and you
>>charge a $30 install fee, you have $70 to recover, and you recover
>from
>>the monthly contribution the customer makes. If the contribution after
>>OPEX is, say, $10, it takes you 7 months to recover the full install
>>cost. Not bad, doable even in low-income markets.
>>
>>Fast-forward to the next-generation version. Now, the CAPEX at install
>>is $250, you need to recover $220, and it will take you 22 months,
>>which is above the usual 18 months that investors look for.
>>
>>The focus, thereby, has to be the lever that has the largest effect on
>>the unit economics - which is the per-customer cost. I have drawn what
>>my ideal FiWi network would look like:
>>
>>
>>
>>Taking you through this - we start with a 1-port, low-cost EPON OLT
>(or
>>you could go for 2, 4, 8 ports as you add capacity). This OLT has
>>capacity for 64 ONUs on its single port. Instead of connecting the
>>typical fiber infrastructure with kilometers of cables which break,
>>require maintenance, etc. we insert an EPON to Ethernet converter (I
>>added "magic" because these don't exist AFAIK).
>>
>>This converter allows us to connect our $2k sector radio, and serve
>the
>>$200 endpoints (ODUs) over wireless point-to-multipoint up to 10km
>>away. Each ODU then has a reverse converter, which gives us EPON
>again.
>>
>>Once we are back on EPON, we can insert splitters, for example,
>>pre-connectorized outdoor 1:16 boxes. Every customer install now
>>involves a 100 meter roll of pre-connectorized 2-core drop cable, and
>a
>>$20 EPON ONU.
>>
>>Using this deployment method, we could connect up to 16 customers to a
>>single $200 endpoint, so the enpoint CAPEX per customer is now $12.5.
>>Add the ONU, cable, etc. and we have a per-install CAPEX of $82.5
>>(assuming the same $50 of extras we had before), and an even shorter
>>break-even. In addition, as the endpoints support higher capacity, we
>>can provision at least the same, if not more, capacity per customer.
>>
>>Other advantages: the $200 ODU is no longer customer equipment and
>>CAPEX, but network equipment, and as such, can operate under a longer
>>break-even timeline, and be financed by infrastructure PE funds, for
>>example. As a result, churn has a much lower financial impact on the
>>operator.
>>
>>The main reason why this wouldn't work today is that EPON, as we know,
>>is synchronous, and requires the OLT to orchestrate the amount of time
>>each ONU can transmit, and when. Having wireless hops and media
>>conversions will introduce latencies which can break down the
>>communications (e.g. one ONU may transmit, get delayed on the radio
>>link, and end up overlapping another ONU that transmitted on the next
>>slot). Thus, either the "magic" box needs to account for this, or an
>>new hybrid EPON-wireless protocol developed.
>>
>>My main point here: the industry is moving away from the unconnected.
>>All the claims I heard and saw at MWC about "connecting the
>>unconnected" had zero resonance with the financial drivers that the
>>unconnected really operate under, on top of IT literacy, digital
>>skills, devices, power...
>>
>>Best,
>>
>>Mike
>>On Mar 14, 2023 at 05:27 +0100, rjmcmahon via Starlink
>><starlink@lists.bufferbloat.net>, wrote:
>>> To change the topic - curious to thoughts on FiWi.
>>>
>>> Imagine a world with no copper cable called FiWi (Fiber,VCSEL/CMOS
>>> Radios, Antennas) and which is point to point inside a building
>>> connected to virtualized APs fiber hops away. Each remote radio head
>>> (RRH) would consume 5W or less and only when active. No need for
>>things
>>> like zigbee, or meshes, or threads as each radio has a fiber
>>connection
>>> via Corning's actifi or equivalent. Eliminate the AP/Client power
>>> imbalance. Plastics also can house smoke or other sensors.
>>>
>>> Some reminders from Paul Baran in 1994 (and from David Reed)
>>>
>>> o) Shorter range rf transceivers connected to fiber could produce a
>>> significant improvement - - tremendous improvement, really.
>>> o) a mixture of terrestrial links plus shorter range radio links has
>>the
>>> effect of increasing by orders and orders of magnitude the amount of
>>> frequency spectrum that can be made available.
>>> o) By authorizing high power to support a few users to reach
>slightly
>>> longer distances we deprive ourselves of the opportunity to serve
>the
>>> many.
>>> o) Communications systems can be built with 10dB ratio
>>> o) Digital transmission when properly done allows a small signal to
>>> noise ratio to be used successfully to retrieve an error free
>signal.
>>> o) And, never forget, any transmission capacity not used is wasted
>>> forever, like water over the dam. Not using such techniques
>represent
>>> lost opportunity.
>>>
>>> And on waveguides:
>>>
>>> o) "Fiber transmission loss is ~0.5dB/km for single mode fiber,
>>> independent of modulation"
>>> o) “Copper cables and PCB traces are very frequency dependent. At
>>> 100Gb/s, the loss is in dB/inch."
>>> o) "Free space: the power density of the radio waves decreases with
>>the
>>> square of distance from the transmitting antenna due to spreading of
>>the
>>> electromagnetic energy in space according to the inverse square law"
>>>
>>> The sunk costs & long-lived parts of FiWi are the fiber and the CPE
>>> plastics & antennas, as CMOS radios+ & fiber/laser, e.g. VCSEL could
>>be
>>> pluggable, allowing for field upgrades. Just like swapping out SFP
>in
>>a
>>> data center.
>>>
>>> This approach basically drives out WiFi latency by eliminating
>shared
>>> queues and increases capacity by orders of magnitude by leveraging
>>10dB
>>> in the spatial dimension, all of which is achieved by a physical
>>design.
>>> Just place enough RRHs as needed (similar to a pop up sprinkler in
>an
>>> irrigation system.)
>>>
>>> Start and build this for an MDU and the value of the building
>>improves.
>>> Sadly, there seems no way to capture that value other than over long
>>> term use. It doesn't matter whether the leader of the HOA tries to
>>> capture the value or if a last mile provider tries. The value
>remains
>>> sunk or hidden with nothing on the asset side of the balance sheet.
>>> We've got a CAPEX spend that has to be made up via "OPEX returns"
>>over
>>> years.
>>>
>>> But the asset is there.
>>>
>>> How do we do this?
>>>
>>> Bob
>>> _______________________________________________
>>> Starlink mailing list
>>> Starlink@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/starlink
[-- Attachment #2: Type: text/html, Size: 10771 bytes --]
next prev parent reply other threads:[~2023-03-14 17:06 UTC|newest]
Thread overview: 148+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2651.1672779463.1281.starlink@lists.bufferbloat.net>
[not found] ` <1672786712.106922180@apps.rackspace.com>
[not found] ` <F4CA66DA-516C-438A-8D8A-5F172E5DFA75@cable.comcast.com>
2023-01-09 15:26 ` [Rpm] [Starlink] Researchers Seeking Probe Volunteers in USA Dave Taht
2023-01-09 17:00 ` Sebastian Moeller
2023-01-09 17:04 ` [Rpm] [LibreQoS] " Jeremy Austin
2023-01-09 18:33 ` Dave Taht
2023-01-09 18:54 ` [Rpm] [EXTERNAL] " Livingood, Jason
2023-01-09 19:19 ` rjmcmahon
2023-01-09 19:56 ` [Rpm] [LibreQoS] " dan
2023-01-09 21:00 ` rjmcmahon
2023-03-13 10:02 ` Sebastian Moeller
2023-03-13 15:08 ` [Rpm] [Starlink] [LibreQoS] [EXTERNAL] " Jeremy Austin
2023-03-13 15:50 ` Sebastian Moeller
2023-03-13 16:06 ` [Rpm] [Bloat] " Dave Taht
2023-03-13 16:19 ` Sebastian Moeller
2023-03-13 16:12 ` [Rpm] " dan
2023-03-13 16:36 ` Sebastian Moeller
2023-03-13 17:26 ` dan
2023-03-13 17:37 ` Jeremy Austin
2023-03-13 18:34 ` Sebastian Moeller
2023-03-13 18:14 ` Sebastian Moeller
2023-03-13 18:42 ` rjmcmahon
2023-03-13 18:51 ` Sebastian Moeller
2023-03-13 19:32 ` rjmcmahon
2023-03-13 20:00 ` Sebastian Moeller
2023-03-13 20:28 ` rjmcmahon
2023-03-14 4:27 ` [Rpm] On FiWi rjmcmahon
2023-03-14 11:10 ` [Rpm] [Starlink] " Mike Puchol
2023-03-14 16:54 ` Robert McMahon
2023-03-14 17:06 ` Robert McMahon [this message]
2023-03-14 17:11 ` [Rpm] [Bloat] " Sebastian Moeller
2023-03-14 17:35 ` Robert McMahon
2023-03-14 17:54 ` [Rpm] [LibreQoS] " dan
2023-03-14 18:14 ` Robert McMahon
2023-03-14 19:18 ` dan
2023-03-14 19:30 ` [Rpm] [Bloat] [LibreQoS] " Dave Taht
2023-03-14 20:06 ` rjmcmahon
2023-03-14 19:30 ` [Rpm] [LibreQoS] [Bloat] " rjmcmahon
2023-03-14 23:30 ` [Rpm] [Starlink] [LibreQoS] [Bloat] " Bruce Perens
2023-03-15 0:11 ` Robert McMahon
2023-03-15 5:20 ` Bruce Perens
2023-03-15 16:17 ` Aaron Wood
2023-03-15 17:05 ` Bruce Perens
2023-03-15 17:44 ` rjmcmahon
2023-03-15 19:22 ` [Rpm] [Bloat] [Starlink] [LibreQoS] " David Lang
2023-03-15 17:32 ` [Rpm] [Starlink] [LibreQoS] [Bloat] " rjmcmahon
2023-03-15 17:42 ` dan
2023-03-15 19:33 ` [Rpm] [Bloat] [Starlink] [LibreQoS] " David Lang
2023-03-15 19:39 ` Dave Taht
2023-03-15 21:52 ` David Lang
2023-03-15 22:04 ` Dave Taht
2023-03-15 22:08 ` dan
2023-03-15 17:43 ` Sebastian Moeller
2023-03-15 17:49 ` rjmcmahon
2023-03-15 17:53 ` Dave Taht
2023-03-15 17:59 ` dan
2023-03-15 19:39 ` rjmcmahon
2023-03-17 16:38 ` [Rpm] [Starlink] " Dave Taht
2023-03-17 18:21 ` Mike Puchol
2023-03-17 19:01 ` Sebastian Moeller
2023-03-17 19:19 ` rjmcmahon
2023-03-17 20:37 ` Bruce Perens
2023-03-17 20:57 ` rjmcmahon
2023-03-17 22:50 ` Bruce Perens
2023-03-18 18:18 ` rjmcmahon
2023-03-18 19:57 ` [Rpm] [LibreQoS] " dan
2023-03-18 20:40 ` rjmcmahon
2023-03-19 10:26 ` [Rpm] [Starlink] [LibreQoS] " Michael Richardson
2023-03-19 21:00 ` [Rpm] On metrics rjmcmahon
2023-03-20 0:26 ` dan
2023-03-20 3:03 ` [Rpm] [Starlink] " David Lang
2023-03-20 20:46 ` [Rpm] [Starlink] [LibreQoS] On FiWi Frantisek Borsik
2023-03-20 21:28 ` dan
2023-03-20 21:38 ` Frantisek Borsik
2023-03-20 22:02 ` [Rpm] On FiWi power envelope rjmcmahon
2023-03-20 23:47 ` [Rpm] [Starlink] " Bruce Perens
2023-03-21 0:10 ` [Rpm] [Starlink] [LibreQoS] On FiWi Brandon Butterworth
2023-03-21 5:21 ` Frantisek Borsik
2023-03-21 11:26 ` [Rpm] Annoyed at 5/1 Mbps Rich Brown
2023-03-21 12:29 ` [Rpm] [Starlink] [LibreQoS] On FiWi Brandon Butterworth
2023-03-21 12:30 ` Sebastian Moeller
2023-03-21 17:42 ` rjmcmahon
2023-03-21 18:08 ` rjmcmahon
2023-03-21 18:51 ` Frantisek Borsik
2023-03-21 19:58 ` rjmcmahon
2023-03-21 20:06 ` [Rpm] [Bloat] " David Lang
2023-03-25 19:39 ` [Rpm] On fiber as critical infrastructure w/Comcast chat rjmcmahon
2023-03-25 20:09 ` [Rpm] [Starlink] " Bruce Perens
2023-03-25 20:47 ` rjmcmahon
2023-03-25 20:15 ` [Rpm] [Bloat] " Sebastian Moeller
2023-03-25 20:43 ` rjmcmahon
2023-03-25 21:08 ` [Rpm] [Starlink] " Bruce Perens
2023-03-25 22:04 ` Robert McMahon
2023-03-25 22:50 ` dan
2023-03-25 23:21 ` Robert McMahon
2023-03-25 23:35 ` [Rpm] [Bloat] [Starlink] " David Lang
2023-03-26 0:04 ` Robert McMahon
2023-03-26 0:07 ` Nathan Owens
2023-03-26 0:50 ` Robert McMahon
2023-03-26 8:45 ` Livingood, Jason
2023-03-26 18:54 ` rjmcmahon
2023-03-26 0:28 ` David Lang
2023-03-26 0:57 ` Robert McMahon
2023-03-25 22:57 ` [Rpm] [Starlink] [Bloat] " Bruce Perens
2023-03-25 23:33 ` [Rpm] [Bloat] [Starlink] " David Lang
2023-03-25 23:38 ` [Rpm] [Starlink] [Bloat] " Robert McMahon
2023-03-25 23:20 ` [Rpm] [Bloat] [Starlink] " David Lang
2023-03-26 18:29 ` rjmcmahon
2023-03-26 10:34 ` [Rpm] [Bloat] " Sebastian Moeller
2023-03-26 18:12 ` rjmcmahon
2023-03-26 20:57 ` David Lang
2023-03-25 20:27 ` [Rpm] " rjmcmahon
2023-03-17 23:15 ` [Rpm] [Bloat] [Starlink] On FiWi David Lang
2023-03-13 19:33 ` [Rpm] [Starlink] [LibreQoS] [EXTERNAL] Re: Researchers Seeking Probe Volunteers in USA dan
2023-03-13 19:52 ` Jeremy Austin
2023-03-13 21:00 ` Sebastian Moeller
2023-03-13 21:27 ` dan
2023-03-14 9:11 ` Sebastian Moeller
2023-03-13 20:45 ` Sebastian Moeller
2023-03-13 21:02 ` [Rpm] When do you drop? Always! Dave Taht
2023-03-13 16:04 ` [Rpm] UnderBloat on fiber and wisps Dave Taht
2023-03-13 16:09 ` Sebastian Moeller
2023-01-09 20:49 ` [Rpm] [EXTERNAL] Re: [Starlink] Researchers Seeking Probe Volunteers in USA Dave Taht
2023-01-09 19:13 ` [Rpm] " rjmcmahon
2023-01-09 19:47 ` Sebastian Moeller
2023-01-11 18:32 ` Rodney W. Grimes
2023-01-11 20:01 ` Sebastian Moeller
2023-01-11 21:46 ` Dick Roy
2023-01-12 8:22 ` Sebastian Moeller
2023-01-12 18:02 ` rjmcmahon
2023-01-12 21:34 ` Dick Roy
2023-01-12 20:39 ` Dick Roy
2023-01-13 7:33 ` Sebastian Moeller
2023-01-13 8:26 ` Dick Roy
2023-01-13 7:40 ` rjmcmahon
2023-01-13 8:10 ` Dick Roy
2023-01-15 23:09 ` rjmcmahon
2023-01-11 20:09 ` rjmcmahon
2023-01-12 8:14 ` Sebastian Moeller
2023-01-12 17:49 ` Robert McMahon
2023-01-12 21:57 ` Dick Roy
2023-01-13 7:44 ` Sebastian Moeller
2023-01-13 8:01 ` Dick Roy
2023-01-09 20:20 ` Dave Taht
2023-01-09 20:46 ` rjmcmahon
2023-01-09 20:59 ` Dave Taht
2023-01-09 21:06 ` rjmcmahon
2023-01-09 21:18 ` rjmcmahon
2023-01-09 21:02 ` Dick Roy
2023-01-10 17:36 ` David P. Reed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=89c55d67-86f0-494d-a09e-c9aeebe46dc0@rjmcmahon.com \
--to=rjmcmahon@rjmcmahon.com \
--cc=bloat@lists.bufferbloat.net \
--cc=libreqos@lists.bufferbloat.net \
--cc=mike@starlink.sx \
--cc=rpm@lists.bufferbloat.net \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox