Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] ongo legalized
Date: Mon, 27 Jan 2020 20:21:32 -0800	[thread overview]
Message-ID: <CAA93jw5Si3JqoRF5Mn8=y4fNqh4Rvw-67nQUHYTHtRHexu9-gg@mail.gmail.com> (raw)

comes with centralized off-switch. from.

https://venturebeat.com/2020/01/27/fcc-unlocks-3-5ghz-cbrs-band-enables-ongo-in-apple-and-android-phones/

Led by the 159-member CBRS Alliance and Wireless Innovation Forum,
efforts to open 3.5GHz spectrum for public access required development
of a sharing arrangement between existing users — most notably the
U.S. Department of Defense (DoD) for naval purposes near the country’s
coasts — and the broader public, including millions of potential users
in both landlocked and coastal areas. Using special “spectrum access
systems” operated by CommScope, Federated Wireless, Google, and Sony,
radio frequencies from 3.55GHz to 3.7GHz can now be used by members of
the public, subject to whatever priority access the government may
demand on an as-needed basis.

In the event that the DoD needs access to the spectrum in a specific
coastal area, a protection zone is activated, dynamically reassigning
access system users within the zone to other frequencies. This lets
prior government users immediately access the 3.5GHz band as needed,
while making the previously locked-up spectrum generally available for
consumer devices and future private networks. Supported phones will
enjoy faster speeds and/or stronger signals on the 3.5GHz band,
falling back to other spectrum in the event of DoD use.


-- 
Make Music, Not War

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729

                 reply	other threads:[~2020-01-28  4:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw5Si3JqoRF5Mn8=y4fNqh4Rvw-67nQUHYTHtRHexu9-gg@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@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