Jump to content

Potential Sprint rural buildout by 2016


Recommended Posts

Did you try using LTE only mode. Maybe it's not letting devices authenticate since there's no CSFB fallback.

Or data centric mode. Could also be a question of backhaul.

 

Sent from my LGLS991 using Tapatalk

Link to comment
Share on other sites

 

 

 

 

 

Still cannot authenticate to the PCS G Block LTE Carrier on B25 here in Rapid City, SD. Not on a Sprint SIM it Google Fi SIM.

 

It is still broadcasting on PLMN ID 311 530 only. I don't know if Sprint will push an update to allow that PLMNID or if they will soon start broadcasting Sprint's 310 120 ID also. Or if Sprint customers will never be allowed to use it.

 

Sent from my Nexus 5 using Tapatalk

Provide me an address of this site, i'll ask what they up to.

Link to comment
Share on other sites

Did you try using LTE only mode. Maybe it's not letting devices authenticate since there's no CSFB fallback.

Yeah, I was in LTE Only mode. Otherwise I don't see it at all.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Provide me an address of this site, i'll ask what they up to.

There are three in Rapid City doing the same thing. This specific one is:

 

- 3850 Tower Road, Rapid City, SD 57701

 

The other two are:

 

- 2727 N. Plaza Drive, Rapid City, SD 57702

- 909 St. Joseph St., Rapid City, SD 57701

 

All three of these are Golden West Telecommunications sites broadcasting on Sprint's PCS G Block channels.

 

Sent from my Nexus 5 using Tapatalk

  • Like 1
Link to comment
Share on other sites

Link to comment
Share on other sites

Another possible repeat, but good verification (Grand Forks, ND):

 

Map

https://wireless2.fcc.gov/UlsEntry/attachments/attachmentViewRD.jsp?applType=search&fileKey=1718171375&attachmentKey=19885565&attachmentInd=applAttach

 

paperwork:

http://wireless2.fcc.gov/UlsApp/ApplicationSearch/applMain.jsp?applID=9525071

 

I have 173 of these, skipping the ones I figure we know or not interested in.

  • Like 1
Link to comment
Share on other sites

 

Yes, those all are Required Notification filings -- the standard type of FCC filing licensees use to indicate satisfaction of certain construction requirement benchmarks.

 

AJ

  • Like 3
Link to comment
Share on other sites

 

So that you do not knock yourself out with too much searching, Sprint has filed these Required Notifications for all of its PCS G block BEAs across the country.  Not just the previously unconstructed, largely rural BEAs.  The filings were due for all BEAs.  You can view the filings for the likes of New York and Los Angeles, too.

 

But good find.  I did not think to look this week at pending applications for the PCS G block licenses -- even though I created this thread almost three years ago.

 

AJ

  • Like 2
Link to comment
Share on other sites

So that you do not knock yourself out with too much searching, Sprint has filed these Required Notifications for all of its PCS G block BEAs across the country.  Not just the previously unconstructed, largely rural BEAs.  The filings were due for all BEAs.  You can view the filings for the likes of New York and Los Angeles, too.

 

But good find.  I did not think to look this week at pending applications for the PCS G block licenses -- even though I created this thread almost three years ago.

 

AJ

 

These were all filed on March 9th.  I have read just a few and they indicate these are for all LTE at greater than -119.8 RSRP.  They provide a wealth of information for sparsely covered markets.  Maps for markets such as Columbus are of quite limited use.  Any idea as to what stage of construction these sites would need to met for the substantial service requirement?

 

( I hope to make it through all 173 filings tonight, posting those that I feel are relevant.)

Link to comment
Share on other sites

These were all filed on March 9th.  I have read just a few and they indicate these are for all LTE at greater than -119.8 RSRP.  They provide a wealth of information for sparsely covered markets.  Maps for markets such as Columbus are of quite limited use.  Any idea as to what stage of construction these sites would need to met for the substantial service requirement?

 

( I hope to make it through all 173 filings tonight, posting those that I feel are relevant.)

 

Yes, you are correct.  Sprint filed all of them as a batch.  The posting date was yesterday, but they may not have appeared in the FCC ULS until today.

 

And as I already commented to an on the road Robert, Sprint is using a -119.8 dBm RSRP figure of merit to define the extent of coverage footprint.  It is not conservative, but it is about what we have long experienced with the 5 MHz FDD carrier -- that -120 dBm RSRP is more or less the bottom limit.

 

AJ

  • Like 1
Link to comment
Share on other sites

Done.  I did not see the following BEAs: Northern Mariana Islands, American Samoa, Gulf of Mexico, thus all are accounted.  

 

All say required notification received (3/9) then offlined for expired license review (3/10).  There is no date on the attachments.

 

the following search was used:

 

Specified Search Radio Service Code=CW, CY
Applicant City=reston
Applicant State=Virginia
Receipt Date=02/25/2016 to 3/10/2016

 

from here: http://wireless2.fcc.gov/UlsApp/ApplicationSearch/searchAdvanced.jsp

 

I use City and State to get all of the Sprint subsidiaries.  Occasionally I pickup someone else. 

Link to comment
Share on other sites

Excuse the newbie question but do these filings mean that Sprint is going to start a LTE build out in these areas (shown map in link)pending FCC approval? Because it would be nice if Sprint had LTE service extending all the way from Pueblo down through Trinidad into Northern New Mexico Raton area!? But not sure if that's what these mean?

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...