From: "David Fernández" <davidfdzp@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] On FiWi
Date: Tue, 14 Mar 2023 15:11:53 +0100 [thread overview]
Message-ID: <CAC=tZ0qL10EQkQT=wPfknOViEx6_p56n0vwjZB-Lp1chz9+gNg@mail.gmail.com> (raw)
Hi Bob,
If you want that FiWi infrastructure on buildings, I am afraid that
you only get it (in the long term) with a law that makes it mandatory
to make new buildings with that infrastructure for communications.
In Spain, it should be added to this:
https://avancedigital.mineco.gob.es/Infraestructuras/Paginas/Index.aspx
Regards,
David
> Date: Mon, 13 Mar 2023 21:27:23 -0700
> From: rjmcmahon <rjmcmahon@rjmcmahon.com>
> To: Sebastian Moeller <moeller0@gmx.de>
> Cc: dan <dandenson@gmail.com>, Jeremy Austin <jeremy@aterlo.com>, Rpm
> <rpm@lists.bufferbloat.net>, libreqos
> <libreqos@lists.bufferbloat.net>, Dave Taht via Starlink
> <starlink@lists.bufferbloat.net>, bloat <bloat@lists.bufferbloat.net>
> Subject: [Starlink] On FiWi
> Message-ID: <bc1cfdf998bb6bb246a632f0dc0fe3a8@rjmcmahon.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> 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
>
next reply other threads:[~2023-03-14 14:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 14:11 David Fernández [this message]
2023-03-14 18:37 ` David Lang
-- strict thread matches above, loose matches on Subject: below --
2023-03-15 21:48 David Fernández
2023-03-15 15:24 David Fernández
2023-03-15 16:09 ` Sebastian Moeller
2023-03-15 16:17 ` Dave Taht
2023-03-15 16:19 ` Vint Cerf
2023-03-15 21:19 ` David Fernández
2023-03-16 7:49 ` Sebastian Moeller
2023-03-15 16:26 ` Sebastian Moeller
2023-03-15 21:07 ` David Fernández
2023-03-15 21:38 ` Sebastian Moeller
2023-03-15 19:15 ` David Lang
[not found] <mailman.2651.1672779463.1281.starlink@lists.bufferbloat.net>
2023-01-03 22:58 ` [Starlink] Researchers Seeking Probe Volunteers in USA David P. Reed
2023-01-09 14:44 ` Livingood, Jason
2023-01-09 15:26 ` Dave Taht
2023-01-09 18:54 ` [Starlink] [EXTERNAL] " Livingood, Jason
2023-01-09 19:19 ` [Starlink] [Rpm] " rjmcmahon
2023-01-09 19:56 ` [Starlink] [LibreQoS] " dan
2023-03-13 10:02 ` [Starlink] [Rpm] [LibreQoS] " Sebastian Moeller
2023-03-13 15:08 ` Jeremy Austin
2023-03-13 15:50 ` Sebastian Moeller
2023-03-13 16:12 ` dan
2023-03-13 16:36 ` Sebastian Moeller
2023-03-13 17:26 ` dan
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 ` [Starlink] On FiWi rjmcmahon
2023-03-14 11:10 ` Mike Puchol
2023-03-14 18:05 ` Steve Stroh
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC=tZ0qL10EQkQT=wPfknOViEx6_p56n0vwjZB-Lp1chz9+gNg@mail.gmail.com' \
--to=davidfdzp@gmail.com \
--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