Jump to content

Network Vision and Spark EARFCN logging thread


Recommended Posts

We are starting to encounter more and more distinct band 41 TD-LTE 2600 EARFCNs.  Unfortunately, these pop up sporadically in various market threads and do not always come to my attention.  Additionally, we are waiting on the first report of a band 25 LTE 1900 EARFCN outside of the PCS G block.
 
At present -- and periodically updated -- the EARFCNs that have been documented are as follows:
 
Band 25 LTE 1900:

  • EARFCNs 8665/26665 [nationwide; PCS G block]
  • EARFCNs 8315/26315 [Chicago MTA; former USCC PCS B block; second carrier]
  • EARFCNs 8158/26158 [shentel; Washington-Baltimore MTA; PCS A block; second carrier]
  • EARFCNs 8565/26565 [Columbus BTA; former Revol PCS C4 block; second carrier]
  • EARFCNs 8465/26465 [Cleveland-Akron BTA; former Revol PCS F block; second carrier]
  • EARFCNs 8415/26415 [Youngstown-Warren BTA; former Revol PCS E block; second carrier]
  • EARFCNs 8321/26321 [Phoenix MTA; PCS B block; second carrier]
  • EARFCNs 8308/26308 [Flint; Detroit MTA; PCS B block; second carrier]
  • EARFCNs 8159/26159 [Lee's Summit; Kansas City MTA; PCS A block; second carrier]

Band 26 LTE 800:

  • EARFCNs 8763/26763 [nationwide; SMR X block]

Band 41 TD-LTE 2600:

  • EARFCN 39826
  • EARFCN 39858
  • EARFCN 39926
  • EARFCN 39956
  • EARFCN 39991
  • EARFCN 40056
  • EARFCN 40124
  • EARFCN 40254 [multiple markets; second carrier]
  • EARFCN 40521
  • EARFCN 40719
  • EARFCN 40978 [multiple markets; first carrier]
  • EARFCN 41078
  • EARFCN 41176 [multiple markets; was Kansas City BTA; Kauffman Stadium -- World Series; second carrier]
  • EARFCN 41276
  • EARFCN 41374

Since there is strength in numbers, if any member encounters an undocumented EARFCN -- whether on an owned device or in someone else's engineering screenshot -- please report it in this thread.  Just please do not report EARFCNs 65535 or 58978.  Those are invalid values.
 
Finally, remember that the S4GRU DL Center contains a spreadsheet that is periodically updated with all known WiMAX and TD-LTE carriers.
 
http://s4gru.com/index.php?/files/file/29-clearwire-wimaxtd-lte-carrier-band-plan/
 
AJ

  • Like 21
Link to comment
Share on other sites

Great idea for a thread, AJ.  Thanks for this.  I'm looking forward to seeing other PCS entries, and possibly some varieties on the SMR with different size carriers in different positions.   :tu:

 

Robert

  • Like 1
Link to comment
Share on other sites

The third engineering screen article, this time focused on band 41, is now up on The Wall.

 

http://s4gru.com/index.php?/blog/1/entry-360-whats-the-frequency-kenneth-interpreting-your-engineering-screen-part-three/

 

AJ

  • Like 11
Link to comment
Share on other sites

Not sure if these can count. I have been having some thing weird happen as of late. My phone connects just on the DL on LTE. It shows LTE Signal sometimes, sometimes not, either way the engineering screens are the same both ways.

 

https://www.dropbox.com/s/fkqgr6j2w9ql0m0/Screenshot_2014-02-01-14-22-34.png

 

https://www.dropbox.com/s/8gjfe4dtgtqzifw/Screenshot_2014-02-06-00-43-09.png

 

 

The 8222 I know was just a scan, 8569 was on there for a bit.

Link to comment
Share on other sites

The 8222 I know was just a scan, 8569 was on there for a bit.

 

Did these occur in Tyler?  Unfortunately, I do not think that either was an actual connection.  And even if EARFCN 8569 was, it was not in spectrum that is licensed to Sprint in the Tyler BTA.

 

AJ

Link to comment
Share on other sites

Did these occur in Tyler?  Unfortunately, I do not think that either was an actual connection.  And even if EARFCN 8569 was, it was not in spectrum that is licensed to Sprint in the Tyler BTA.

 

AJ

Yeah pretty sure it was in Tyler. I did the math just now and it is T-Mobile spectrum. Hmm not sure what happened. But it might be a value to look for in other markets
Link to comment
Share on other sites

  • 3 weeks later...

AJ, I do not know if this counts.

 

My stock Nexus 5 has been scanning all LTE Bands about every 3 minutes.

This is the video.

Band 17 - 5760, 5799
Band 4 - 2325
Band 26 - 8883, 8949, 8973, 8922, 8856
Band 41 - 41501, 41417, 39753, 39823, 39826
Band 25 - 8443, 8277, 8365, 8477, 8328
Band 1 - 422, 410, 447, 366, 357
Band 2 - 974, 835, 689, 1083, 865
Band 4 - 2350, 2331, 2322, 2174
Band 5 - 2580, 2564, 2511, 2577, 2515
Band 19 - 6101, 6049
 

  • Like 1
Link to comment
Share on other sites

AJ, I do not know if this counts.

 

My stock Nexus 5 has been scanning all LTE Bands about every 3 minutes.

This is the video.

Band 17 - 5760, 5799

Band 4 - 2325

Band 26 - 8883, 8949, 8973, 8922, 8856

Band 41 - 41501, 41417, 39753, 39823, 39826

Band 25 - 8443, 8277, 8365, 8477, 8328

Band 1 - 422, 410, 447, 366, 357

Band 2 - 974, 835, 689, 1083, 865

Band 4 - 2350, 2331, 2322, 2174

Band 5 - 2580, 2564, 2511, 2577, 2515

Band 19 - 6101, 6049

 

Where is the band 25 EARFCN of 8665? I haven't seen an EARFCN that sprint uses, and the nexus 5 scans for. ( except b41 39826)
Link to comment
Share on other sites

  • 3 months later...

The EARFCN of Sprint Band 41 in Columbus is 40521, same as the Clear (Clearwire) Band 41  EARFCN, source: http://s4gru.com/index.php?/topic/4825-columbus-market-mapspreadsheet-premier-edition/page-19&do=findComment&comment=321397

Link to comment
Share on other sites

Aj, I was traveling through the southern suburbs of Chicago, when I noticed I was connected to band 41 with this frequency. I checked post #1 to see if it was on your "do not post, these are null values" list, and it wasn't. It never changed, and stayed even while using data, so I don't think it was null.

yjugydap.jpgpuzade7a.jpg

 

Sent from my HTC One M8

Link to comment
Share on other sites

Aj, I was traveling through the southern suburbs of Chicago, when I noticed I was connected to band 41 with this frequency. I checked post #1 to see if it was on your "do not post, these are null values" list, and it wasn't. It never changed, and stayed even while using data, so I don't think it was null.

 

 

Sent from my HTC One M8

 

Still invalid. The valid EARFCN in the screenshots are 40056. Anything above 46589 is an invalid EARFCN. 

Link to comment
Share on other sites

Still invalid. The valid EARFCN in the screenshots are 40056. Anything above 46589 is an invalid EARFCN.

So it's an error on the phone's engineering screen?

 

Sent from my HTC One M8

Link to comment
Share on other sites

So it's an error on the phone's engineering screen?

 

Hi Vince...

 

Yes, the uplink EARFCN for TDD appears to be an error.  Why it is even there, I cannot explain it.  So, I should probably edit my instructions to indicate that you should report only the downlink EARFCN.  If it is TDD, the downlink EARFCN is accurate.  If it is FDD, I can calculate the uplink EARFCN from the reported downlink EARFCN.

 

Also, I did not have a chance yet to thank you for supplying the official documentation of the secondary band 25 LTE 1900 carrier in Chicago.  But I added the new EARFCNs shortly after your post and PM.  The secondary band 25 LTE 1900 carrier is just as I expected at the high end of the former USCC license.  That is wise spectrum management.

 

AJ

Link to comment
Share on other sites

Hi Vince...

 

Yes, the uplink EARFCN for TDD appears to be an error.  Why it is even there, I cannot explain it.  So, I should probably edit my instructions to indicate that you should report only the downlink EARFCN.  If it is TDD, the downlink EARFCN is accurate.  If it is FDD, I can calculate the uplink EARFCN from the reported downlink EARFCN.

 

Also, I did not have a chance yet to thank you for supplying the official documentation of the secondary band 25 LTE 1900 carrier in Chicago.  But I added the new EARFCNs shortly after your post and PM.  The secondary band 25 LTE 1900 carrier is just as I expected at the high end of the former USCC license.  That is wise spectrum management.

 

AJ

Do you think Sprint might eventually sell its E block PCS license in Chicago?

Link to comment
Share on other sites

Do you think Sprint might eventually sell its E block PCS license in Chicago?

 

It is a possibility.  To the PCS E block 10 MHz license, the adjacent license holders are VZW with the PCS B5 block 10 MHz disaggregation and AT&T with the PCS F block 10 MHz license.  VZW holds no other PCS spectrum in Chicago, while AT&T also has the PCS A block 30 MHz license.  So, VZW might be interested, while I think AT&T is already full up.

 

On the other hand, Sprint might want to send its PCS D block 10 MHz license to AT&T in exchange for the PCS F block.  That would give Sprint two separate 20 MHz contiguous swaths, while AT&T would end up with one 40 MHz contiguous segment.

 

The third option is that Sprint keeps it all.  And CDMA2000 operations are eventually shunted to just the PCS E block so that the adjacent combo of the PCS D block and PCS B3/B4 block 20 MHz disaggregation can run LTE at 15 MHz FDD.

 

The band plan graphic that I created for the Sprint-USCC transaction article can be a helpful reference:

 

2qi8ier.png

 

AJ

  • Like 2
Link to comment
Share on other sites

It is a possibility.  To the PCS E block 10 MHz license, the adjacent license holders are VZW with the PCS B5 block 10 MHz disaggregation and AT&T with the PCS F block 10 MHz license.  VZW holds no other PCS spectrum in Chicago, while AT&T also has the PCS A block 30 MHz license.  So, VZW might be interested, while I think AT&T is already full up.

 

On the other hand, Sprint might want to send its PCS D block 10 MHz license to AT&T in exchange for the PCS F block.  That would give Sprint two separate 20 MHz contiguous swaths, while AT&T would end up with one 40 MHz contiguous segment.

 

The third option is that Sprint keeps it all.  And CDMA2000 operations are eventually shunted to just the PCS E block so that the adjacent combo of the PCS D block and PCS B3/B4 block 20 MHz disaggregation can run LTE at 15 MHz FDD.

 

AJ

 

I am assuming that eventually all of the USCC Spectrum would be used for LTE incrementally, and that as CDMA traffic declined they would simply sell off block E. Continuity is good though. Frankly, if Sprint needed money for low band spectrum, I could see them pairing down to about 30Mhz of PCS  across the country (10Mhz for CDMA and a pair of 5x5 LTE channels), once they get a solid band 41 LTE network built up. With the new gear, the band 41 coverage is almost as good as the Band 25 coverage. Band 25 will mostly be for non-spark devices (old Sprint devices or roaming traffic).

Link to comment
Share on other sites

  • 2 weeks later...

AJ, I know this is in your list, but I was wondering why there would be two different b41 channels in a market. I found this 40 minutes outside of Chicago last night. It strays from our usual 40056veruve7e.jpg

Link to comment
Share on other sites

AJ, I know this is in your list, but I was wondering why there would be two different b41 channels in a market. I found this 40 minutes outside of Chicago last night. It strays from our usual 40056

 

One carrier is deployed in EBS spectrum, the other in BRS spectrum.  And "40 minutes outside of Chicago" is not necessarily still in the same licensed market -- especially for EBS. 

 

AJ

Link to comment
Share on other sites

One carrier is deployed in EBS spectrum, the other in BRS spectrum. And "40 minutes outside of Chicago" is not necessarily still in the same licensed market -- especially for EBS.

 

AJ

30-40 minutes. It was in Joliet. That's still our market.

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

    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
    • "The company’s unique multi-layer approach to 5G, with dedicated standalone 5G deployed nationwide across 600MHz, 1.9GHz, and 2.5GHz delivers customers a consistently strong experience, with 85% of 5G traffic on sites with all three spectrum bands deployed." Meanwhile they are very close to a construction deadline June 1 for 850Mhz of mmWave in most of Ohio covering 27500-28350Mhz expiring 6/8/2028. No reported sightings.  Buildout notice issue sent by FCC in March 5, 2024 https://wireless2.fcc.gov/UlsApp/letterPdf/LetterPdfController?licId=4019733&letterVersionId=178&autoLetterId=13060705&letterCode=CR&radioServiceCode=UU&op=LetterPdf&licSide=Y&archive=null&letterTo=L  No specific permits seen in a quick check of Columbus. They also have an additional 200Mhz covering at 24350-25450 Mhz and 24950-25050Mhz with no buildout date expiring 12/11/2029.
  • Recently Browsing

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