Jump to content

Network Vision and Spark EARFCN logging thread


Recommended Posts

I've been looking for a repeater and some of the things I've read suggest that G-block is not covered by most of them, or worse, the filter rolls off right in the middle of G-block.

 

- Trip

Link to comment
Share on other sites

Nice.

 

What is curious is that I'm now getting a consistent LTE signal now with this carrier throughout my entire building where before I would have to get close to a window to get a LTE signal.

 

We do have cellular repeaters throughout the building so maybe that has something to do with it.

 

Are the repeaters official Sprint ones or just off-the shelf ones? I would wager that they support A-F block out of the box.

Link to comment
Share on other sites

Are the repeaters official Sprint ones or just off-the shelf ones? I would wager that they support A-F block out of the box.

They are not off the shelf but am not sure if they are Sprint only either.

 

The cones distributed in the ceilings looks like what is shone in this picture:

 

https://cdn.shopify.com/s/files/1/0358/5537/products/2014041414374150_f4c7d284-d74f-4398-b9c1-f87ab6e034fd_1024x1024.jpeg?v=1419883401

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

They are not off the shelf but am not sure if they are Sprint only either.

 

The cones distributed in the ceilings looks like what is shone in this picture:

 

https://cdn.shopify.com/s/files/1/0358/5537/products/2014041414374150_f4c7d284-d74f-4398-b9c1-f87ab6e034fd_1024x1024.jpeg?v=1419883401

 

 

Sent from my iPhone using Tapatalk

 

Makes sense, I've seen something similar before.

Link to comment
Share on other sites

I was going by the summary on the first page. It obviously needs to to be updated. I wasn't trying to step on your toes, sorry.

Link to comment
Share on other sites

I was going by the summary on the first page. It obviously needs to to be updated. I wasn't trying to step on your toes, sorry.

 

The top post will be updated only periodically now.  Additional LTE carriers are no longer big news.

 

AJ

Link to comment
Share on other sites

The top post will be updated only periodically now. Additional LTE carriers are no longer big news.

 

AJ

Additional LTE carriers are quite important to those who benefit and do encourage member participation. Point taken that they not as unique. However just the process of looking for them may result in finding items like 3x3 b26 LTE or 15x15 or 20x20 b25 LTE, or even third carrier b41 and beyond.

 

Sent from my LGLS991 using Tapatalk

  • Like 2
Link to comment
Share on other sites

However just the process if looking for them may result in finding items like 3x3 b26 LTE or 15x15 or 20x20 b25 LTE, or even third carrier b41 and beyond.

 

That is fine.  If the carrier is of unusual bandwidth, it is newsworthy.  We will sound the clarion call.  However, a 5 MHz FDD band 25 second carrier does not require a rapid thread update any longer.

 

AJ

Link to comment
Share on other sites

Looks like I found a new one: 8071/26071. Site near my parents' place (outside Fredericksburg, TX). Which puts it as close to the bottom of PCS A as we've seen so far.

 

As I recall, the actual transmission path on 5x5 LTE is 4.5 MHz wide, so with a center frequency 3.1 MHz above the bottom of the band you end up with 0.85 MHz of guard band going on, or 0.6 MHz if you do your guard band based on a 5 MHz channel width. Conservative, maybe, but they've got 15x15 here to play with on a rural site so aggressive spacing doesn't really need to happen.

 

Service is plenty speedy, though it looks like that's partially because PCS-G takes priority when its signal is good...was hard for me to grab PCS-A outdoors as my phone would go to G or B41 (!!!). This is by all indications a 5x5 deployment.

Link to comment
Share on other sites

Looks like I found a new one: 8071/26071. Site near my parents' place (outside Fredericksburg, TX). Which puts it as close to the bottom of PCS A as we've seen so far.

 

As I recall, the actual transmission path on 5x5 LTE is 4.5 MHz wide, so with a center frequency 3.1 MHz above the bottom of the band you end up with 0.85 MHz of guard band going on, or 0.6 MHz if you do your guard band based on a 5 MHz channel width. Conservative, maybe, but they've got 15x15 here to play with on a rural site so aggressive spacing doesn't really need to happen.

 

Service is plenty speedy, though it looks like that's partially because PCS-G takes priority when its signal is good...was hard for me to grab PCS-A outdoors as my phone would go to G or B41 (!!!). This is by all indications a 5x5 deployment.

Samsung phones and, iPhone will show Bandwidth. *#0011# on samsung and, fieldtest for phone. You can Google the code for that.

 

Sent from my SM-G900P using Tapatalk

Link to comment
Share on other sites

Samsung phones and, iPhone will show Bandwidth. *#0011# on samsung and, fieldtest for phone. You can Google the code for that.

 

Sent from my SM-G900P using Tapatalk

 

My N5X won't show bandwidth though. Will see if the A9, M8, S III or Galaxy Victory phone(s) other family members have will...

Link to comment
Share on other sites

Looks like I found a new one: 8071/26071. Site near my parents' place (outside Fredericksburg, TX). Which puts it as close to the bottom of PCS A as we've seen so far.

 

Hmm, I would have thought Fredericksburg to be in the Austin BTA, hence the Dallas-Ft. Worth MTA.  But if this is PCS A block, then it is not Dallas-Ft. Worth MTA, as that is PCS B block for Sprint.  You could cross reference the county in the FCC ULS database, but it looks like Fredericksburg must be in the San Antonio MTA, which is PCS A block for Sprint.

 

AJ

  • Like 2
Link to comment
Share on other sites

Hmm, I would have thought Fredericksburg to be in the Austin BTA, hence the Dallas-Ft. Worth MTA.  But if this is PCS A block, then it is not Dallas-Ft. Worth MTA, as that is PCS B block for Sprint.  You could cross reference the county in the FCC ULS database, but it looks like Fredericksburg must be in the San Antonio MTA, which is PCS A block for Sprint.

 

AJ

Checked before posting, hence the 15x15 PCS A reference. That block is San Antonio MTA. SA is geographically closer, though for TV and network classifications it's a toss up between SAT and AUS.

Link to comment
Share on other sites

As I recall, the actual transmission path on 5x5 LTE is 4.5 MHz wide, so with a center frequency 3.1 MHz above the bottom of the band you end up with 0.85 MHz of guard band going on, or 0.6 MHz if you do your guard band based on a 5 MHz channel width. Conservative, maybe, but they've got 15x15 here to play with on a rural site so aggressive spacing doesn't really need to happen.

 

In 5/10/15 MHz FDD spectrum block allocations, CDMA2000 long has used 0.625 MHz FDD guard bands at the top and bottom of each block.  CDMA2000 did not require 0.625 MHz FDD guard bands, but there was no way around them.  If you do the math in 5/10/15 MHz FDD spectrum blocks with 1.25 MHz FDD CDMA2000 carriers, guard bands must be 0.625 MHz FDD.  The only alternative is zero -- not feasible. 

 

So, that is what you are seeing with the 0.6 MHz FDD guard band at the bottom of the PCS A block.  That spectrum always has been reserved as a CDMA2000 guard band.  Now, keeping the same guard band, a 5 MHz FDD LTE carrier has replaced up to four 1.25 MHz FDD CDMA2000 carriers or filled fallow spectrum.

 

AJ

Link to comment
Share on other sites

Checked before posting, hence the 15x15 PCS A reference. That block is San Antonio MTA. SA is geographically closer, though for TV and network classifications it's a toss up between SAT and AUS.

 

And, yikes, for band class 1 CDMA1X, that would mean a lot of inter license, inter frequency hard handoffs around Fredericksburg.  For that area, band class 10 CDMA1X should be a godsend, since it not only is low band but also uses the same SMR 476 carrier channel assignment across nearly all license boundaries.

 

AJ

  • Like 4
Link to comment
Share on other sites

  • 3 weeks later...
  • 4 weeks later...

Tucson's has no B26 or B41 active, so we finally got our first 10x10 B25 to atleast ease up some congestion finally!

 

I can't get the LTE Engineering page up on my N6P, if you know of a way, let me know!

 

Ninja Edit:

 

 

_id first_time first_time_offset last_time last_time_offset last_device_latitude last_device_longitude last_device_loc_accuracy user_note provider plmn gci pci tac dl_chan strongest_rsrp strongest_latitude strongest_longitude 1 2/9/16 10:03 -7 2/9/16 10:04 -7 32.287514 -110.960024 21.78   Sprint B25 310120 06E02B02 358 14082 0 -77 32.287514 -110.960024   2 2/9/16 10:04 -7 2/9/16 10:06 -7 32.287514 -110.960024 21.78   Sprint B25² 310120 06E02B0A 358 14082 0 -75 32.287514 -110.960024  

 

 

Screenshot_20160209-072159.png

Screen Shot 2016-02-09 at 11.19.22 AM.png

  • Like 1
Link to comment
Share on other sites

 

 

Tucson's has no B26 or B41 active, so we finally got our first 10x10 B25 to atleast ease up some congestion finally!

 

I can't get the LTE Engineering page up on my N6P, if you know of a way, let me know!

 

Ninja Edit:

The 6P technically has engineering screens.... They're just useless. They don't display anything other than the PLMN and Serving Cell, which for some reason is always 0. I have my fingers crossed it'll get fixed in the March or April update (the Nexus 6 got them in the mid-March update last year).

 

Sent from my Nexus 6P

  • Like 1
Link to comment
Share on other sites

 

 

Tucson's has no B26 or B41 active, so we finally got our first 10x10 B25 to atleast ease up some congestion finally!

 

I can't get the LTE Engineering page up on my N6P, if you know of a way, let me know!

 

Ninja Edit:

It may just be a second 5x5 B25 carrier. Need more info to confirm. But good news all the same. Even a second 5x5 carrier will double capacity and speeds.

 

Using Tapatalk on Note 8.0

  • Like 1
Link to comment
Share on other sites

Tucson's has no B26 or B41 active, so we finally got our first 10x10 B25 to atleast ease up some congestion finally!

 

I can't get the LTE Engineering page up on my N6P, if you know of a way, let me know!

 

Ninja Edit:

Not 10x10.

 

That's the second 5 mhz b25 carrier on the PCS B block since sprint is licensed the entire 30 MHz portion there.

  • Like 1
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

    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • 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.
  • Recently Browsing

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