Jump to content

3GPP approves LTE band 70 for Dish Spectrum


bigsnake49

Recommended Posts

Band 70 comprises Dish's current AWS-4 spectrum (2000 MHz to 2020 MHz), its H Block downlink spectrum (1995 MHz to 2000 MHz), and unpaired AWS-3 uplink spectrum (1695 MHz to 1710 MHz). The 3GPP agreed to the specifications three weeks ago; formal approval will enable the development of devices and infrastructure supporting Band 70.

 

http://www.fiercewireless.com/story/3gpp-approves-band-70-allowing-dish-combine-three-spectrum-blocks/2016-06-16

 

I know that I am asking you to speculate, but what do you think of the possibility that Dish invests in Sprint or T-Mobile in return for getting their spectrum hosted? Is Dish just a spectrum speculator or are they interested in being a wireless operator?

Edited by bigsnake49
Link to comment
Share on other sites

And as I have said, I look for 5/10/15 MHz FDD carrier bandwidths standardized, perhaps only in the 1695-1710 MHz x 1995-2010 MHz pairing.  The other 10 MHz, possibly limited to 2010-2020 MHz will be for supplemental downlink carrier aggregation.

 

Also, note that the PCS H block uplink at 1915-1920 MHz gets orphaned.  But that is just as well.  It may have been getting too close for comfort to the PCS A block downlink at 1930-1945 MHz.  And Sprint owns a lot of PCS A block spectrum.

 

AJ

  • Like 1
Link to comment
Share on other sites

So is Dish getting B70 to make the spectrum more valuable, or to actually deploy it? From what I've read, they've done nothing in terms of actually utilizing the spectrum for broadband or fixed wireless.

Only thing Dish has done was the fixed wireless trials with Ntelos and Sprint but that was Sprint's and Ntelos's own spectrum.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Uploaded data without issues on Friday. Now with the latest update I am getting "Cluster #1 skipped: invalid file format detected. File exported for inspection." Doing same with all other clusters. Did this on 4 phones in a row.  Seems to work on s24 ultra just fine. On s21 ultra it says "web data upload failed. No data to send" although 8800 records were displayed. Now gives same error as above. I have not sent the data from 3 other phones.  All should have latest update.
    • After several months of testing, an update to SignalCheck Pro is rolling out on Google Play. It may take up to 48 hours to become available for download. Notable changes include: Added option to display site notes for NSA 5G-NR cells. Enabling this new option (Preferences > Display Settings > Show NSA 5G-NR Site Notes) will cause the app to make an "educated guess" as to what the most appropriate site note is linked to the connected NSA 5G cell, using the PCI and the device location. If it finds an existing entry that is likely to be relevant, it will display the note along with the distance from where the strongest signal from that cell was logged. While connected to NSA 5G, these notes cannot be edited; a valid NCI is required to add/edit notes and that information is not available on NSA connections.   Added option to log cells with missing/invalid PLMN (such as NSA 5G-NR cells). Users asked for the ability to log data for NSA 5G, so a new option (Preferences > Logger Settings > Log Cells with Missing PLMN) will permit this.   Added option to display LTE info above 5G-NR info. Enabling this new option (Preferences > Display Settings > Show LTE Cells Above 5G-NR Cells) shows the same information that is currently displayed, but moves the LTE information above the 5G-NR information. Other changes: Code optimizations and enhancements. Improved Android 15 compatibility. Overhauled Purchases module. Resolved force closes impacting some GSM/LTE connections. Resolved issue with improper 5G-NR PLMN display when NR/LTE PLMNs did not match. Resolved issue with improper PLMN display with single-digit MNCs. Resolved issue with incorrect 5G-NR bands displayed on some devices due to Android bug. Resolved issue with incorrect number of neighbor cells displayed when some cells were unknown. Resolved issue with missing 5G-NR data when sector display is enabled. Resolved issue with saving 5G-NR site notes when NR/LTE PLMNs did not match. Resolved issue with settings to log missing GCI/NCI/TAC/PLMN being ignored. Resolved issues with web data export function. Updated internal libraries. Updated provider database. Updated target API to Android 15. I appreciate all of your support, and a big thank you to the members of the Beta Crew that help with testing and feedback!
    • Oct security update is out.
    • Stopped by again today and the antennas are up but it isn't live just yet. If other Sprint conversions are anything to go by it'll likely take about a month for the site to go live.
    • It is an Android bug that was reportedly fixed in August 2023 but definitely has not been. I have implemented numerous workarounds in SCP to correct the NR bands the app displays. The OS ignores the possibility that many NR-ARFCNs are valid across multiple bands.. it reports the lowest NR band that is valid for the current ARFCN. In your example, channel 432530 can be n1, n65, or n66.. so the OS just (lazily) reports n1.   Awesome, thanks! I will add an n65 override also.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...