Jump to content

Everything 800mhz (1xA, LTE, coverage, timeline, etc)


Recommended Posts

Hopefully there is not also Public Safety Agencies in Canada that need clearing.

 

If Canada has not finished 800 MHz rebanding, then Public Safety still will be in the way at the top of the band where the band 26 LTE carrier is located.  The band class 10 CDMA1X carrier has been deployed in some IBEZ areas because it is located below 821 MHz x 866 MHz and is in a contiguous 3 MHz FDD block that has been used for commercial operations, not Public Safety.  So, once Telus Mike goes dark, band class 10 CDMA1X at the very least should be possible.

800bandplan1X_3.png

 

http://s4gru.com/index.php?/blog/1/entry-90-fcc-ready-to-give-sprint-official-go-ahead-on-smr-800-mhz-wideband-operation/

 

AJ

Link to comment
Share on other sites

I think it may be somewhat market dependant as far as 800 installation in IBEZ areas are concerned. Most of the sites in the Cleveland market already have at least the dualband antenna installed, and 1x800 lit up rather quickly in the secondary IBEZ once Sprint decided to activate it about 3 or 4 months ago.

 

I know we have confirmed that the East Michigan and Washington had PCS only antennas deployed. I don't know about the other IBEZ Samsung markets. I'm not sure, but I don't think the other vendors deployed a PCS only antenna. Just did not install an 800 RRU initially. 

Link to comment
Share on other sites

I think it may be somewhat market dependant as far as 800 installation in IBEZ areas are concerned. Most of the sites in the Cleveland market already have at least the dualband antenna installed, and 1x800 lit up rather quickly in the secondary IBEZ once Sprint decided to activate it about 3 or 4 months ago.

Yea we don't have 800mjz equipment up at all here so the deployment probably won't be as quick.

Link to comment
Share on other sites

  • 4 months later...

Sprint isn't very happy with Maricopa county.  

 

 

 

Improving Public Safety Communications in the 800 MHz Band - EDOCS
May 18, 2016 - ORDER

Granted in part and denied in part a request by Sprint for Bureau intervention in Maricopa's rebanding proces

 

 

http://transition.fcc.gov/Daily_Releases/Daily_Business/2016/db0518/DA-16-553A1.pdf

  • Like 5
Link to comment
Share on other sites

Sprint isn't very happy with Maricopa county.

 

 

Improving Public Safety Communications in the 800 MHz Band - EDOCS

May 18, 2016 - ORDER

Granted in part and denied in part a request by Sprint for Bureau intervention in Maricopa's rebanding proces

 

 

http://transition.fcc.gov/Daily_Releases/Daily_Business/2016/db0518/DA-16-553A1.pdf

 

 

Jesus. Sounds like it's going to be awhile before this is settled. I hate Arizona. I use to live there for 6 years lol. My kids still live there now.

Link to comment
Share on other sites

Sprint isn't very happy with Maricopa county.  

 

 

 

Improving Public Safety Communications in the 800 MHz Band - EDOCS
May 18, 2016 - ORDER

Granted in part and denied in part a request by Sprint for Bureau intervention in Maricopa's rebanding proces

 

 

http://transition.fcc.gov/Daily_Releases/Daily_Business/2016/db0518/DA-16-553A1.pdf

Well at least now they've got the FCC breathing down their necks. Probably better for all involved parties to ensure more transparency.

  • Like 1
Link to comment
Share on other sites

  • 3 weeks later...

This should be faster now especially since Telus as killed of Mike (iDen Network in Canada) last January.

Telus MiKE has no effect on the situation in Arizona, only the situation in western Washington.

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

  • Similar Content

  • Posts

    • 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.
    • Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
  • Recently Browsing

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