Jump to content

Network Vision and Spark EARFCN logging thread


Recommended Posts

Revol-ting!  Revol-ting!

 

Yeah, I guess Ting, too, would get some of that second band 25 carrier.

 

;)

 

AJ

  • Like 1
Link to comment
Share on other sites

Also second PCS LTE carrier confirmed in Cleveland earfcn 26465/8645 (PCS F Block) and Columbus earfcn 26565 / 8565 PCS C block.

This is awesome. Tim, where did this spectrum come from? Was it refarmed Sprint spectrum? Or, was it through a regional acquisition.

 

Edit: AJ answered this as I was typing. Revol?

 

 

Sent from my iPhone 6

Link to comment
Share on other sites

B41 in mid Michigan is on channel 58978. I don't see that listed on the OP. I've got a screenshot if needed.

 

Carefully read the top post, please.

 

egg-on-face.jpg

 

AJ

  • Like 1
Link to comment
Share on other sites

I have again updated the top post and spreadsheet.  They do not, however, include the reported second band 25 carriers in Revol spectrum yet.  Those await screenshot confirmation.

 

AJ

  • Like 2
Link to comment
Share on other sites

I have again updated the top post and spreadsheet. They do not, however, include the reported second band 25 carriers in Revol spectrum yet. Those await screenshot confirmation.

 

AJ

uploadfromtaptalk1414803694540.jpg

 

 

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

  • 3 weeks later...

I was requested to post my B25 second carrier finds for the Cleveland market, so here's the screenshots. Both of these were found October 29thattachicon.gif Screenshot_2014-10-29-15-51-27.pngattachicon.gif Screenshot_2014-10-29-17-58-39.png

Cleveland is now running 3 5x5mhz band 25 carriers? That's nice.

 

 

Sent from my iPhone 6

Link to comment
Share on other sites

I was requested to post my B25 second carrier finds for the Cleveland market, so here's the screenshots. Both of these were found October 29thattachicon.gifScreenshot_2014-10-29-15-51-27.pngattachicon.gifScreenshot_2014-10-29-17-58-39.png

 

Were both of those screenshots taken in the Cleveland-Akron market?  The second appears to be an anomaly, as that LTE carrier is centered in the PCS E block, which is licensed to T-Mobile.

 

AJ

Link to comment
Share on other sites

Yes, both were taken in the Cleveland market, though in different regions. The 8415/26415 pair was grabbed from a site near Warren, OH. I'll reevaluate the result the next time I'm in that area and let you know if anything's different.

Link to comment
Share on other sites

Yes, both were taken in the Cleveland market, though in different regions. The 8415/26415 pair was grabbed from a site near Warren, OH. I'll reevaluate the result the next time I'm in that area and let you know if anything's different.

 

Ah, that is not the Cleveland-Akron market.  It is the Youngstown-Warren market, where Sprint did acquire a different Revol license -- the PCS E block license.  So, your screenshot is accurate.

 

Apparently, Sprint is not screwing around with this Revol spectrum.  Youngstown is basically an armpit, a heavily depressed area that is losing population like crazy.  But, regardless of market prospects, Sprint is rolling this acquired spectrum right into band 25 LTE.

 

AJ

  • Like 3
Link to comment
Share on other sites

These were taken in and around Eaton Ohio in the Cincinnati market. There are three sites that always give me an invalid UL Channel. I took a screen shot so we know it is not software. Is this a site configuration error? Also the uploads either fail or they are extremely slow. dkyeager helped me figure out it was an invalid UL channel.18421d434ec0b772ea18144f4e858221.jpg38db66189bea6a745b6885593852602e.jpgc821ab31c4e742336e8f03b52228895a.jpg

Also found a second band 25 carrier but was unable to get a engineering screenshot.

Link to comment
Share on other sites

  • 1 month later...

New B41 sites coming online in the Metro Detroit area. I saw EARFCN 41374 coming from sites in the Madison Heights and Troy area. There was a B41 site that just came online in the Warren area but  I wasn't able to determine the EARFCN. Any other B41 site I've seen in outstate Michigan is on the common 40978 EARFCN thus far. 

 

Screenshot_2015-01-02-16-51-07.png

 

 

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

Over 90 b25 second carrier sites have been found in the Cleveland Market so far. Maybe they can be moved up to the big league on the first page of this thread.  Columbus continues to have just one B25 second carrier site.

  • Like 1
Link to comment
Share on other sites

  • 2 months later...

Top post has been updated.

 

AJ

  • Like 1
Link to comment
Share on other sites

Earfcn 26315 is pretty widespread throughout Ft Wayne and points south, Southern Illinois and St Louis.

That's Chicago's second PCS carrier, too.

 

 

Sent from my iPhone 6+

Link to comment
Share on other sites

Earfcn 26315 is pretty widespread throughout Ft Wayne and points south, Southern Illinois and St Louis. 

 

A few thoughts...

 

EARFCN 26315 is the uplink.  Focus on the downlink EARFCN, which would be EARFCN 8315.  Generally, logging either is fine.  But TD-LTE throws a wrench into the mix -- with invalid uplink EARFCNs.

 

The PCS B block spectrum acquired from USCC is in the Chicago MTA.  Parts of Northern Indiana, such as Ft. Wayne, and much of Southern Illinois are still in the Chicago MTA.  So, reports of a second carrier in those areas with the same EARFCN as in Chicago are not exactly new info.  Those areas are all part of the Chicago MTA.

 

Now, St. Louis is a whole new ballgame -- to the cheers of insufferable Cardinals fans.  The USCC spectrum acquired there is from the St. Louis MTA PCS A block license.  It is not the same spectrum as in the Chicago MTA, so it cannot contain the same EARFCN.  But Sprint itself has long held the PCS B block license for the St. Louis MTA.  Thus, a second band 25 carrier in St. Louis with the same EARFCN as in Chicago would have to come from Sprint's own spectrum.

 

AJ

Link to comment
Share on other sites

A few thoughts...

 

EARFCN 26315 is the uplink.  Focus on the downlink EARFCN, which would be EARFCN 8315.  Generally, logging either is fine.  But TD-LTE throws a wrench into the mix -- with invalid uplink EARFCNs.

 

The PCS B block spectrum acquired from USCC is in the Chicago MTA.  Parts of Northern Indiana, such as Ft. Wayne, and much of Southern Illinois are still in the Chicago MTA.  So, reports of a second carrier in those areas with the same EARFCN as in Chicago are not exactly new info.  Those areas are all part of the Chicago MTA.

 

I was simply replying to the post above mine that basically the 2nd LTE carrier is more widespread across this region than South Bend.

 

 

Now, St. Louis is a whole new ballgame -- to the cheers of insufferable Cardinals fans.  The USCC spectrum acquired there is from the St. Louis MTA PCS A block license.  It is not the same spectrum as in the Chicago MTA, so it cannot contain the same EARFCN.  But Sprint itself has long held the PCS B block license for the St. Louis MTA.  Thus, a second band 25 carrier in St. Louis with the same EARFCN as in Chicago would have to come from Sprint's own spectrum.

 

AJ

 

Let me see what I can do about a screen shot...

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

    • I think it is likely that T-Mobile will be forced to honor any existing US cellular roaming agreements in those areas as a condition of them taking over the spectrum.  In that case, there would be no improvement of service unless T-Mobile improves the service offering in those areas.
    • My understanding is the MNO carriers are the one who have objected to the use of cell phones in commercial planes.  I understand that it ties down too many cell phones at once, thus I can not see this changing. However this depends on how it is structured. Use of a different plmn for satellite service might make it possible for planes only to connect with satellite. Private pilots have been using cellphones in planes for many decades. Far fewer phones at a lower altitude.
    • On Reddit, someone asked (skeptically) if the US Cellular buyout would result in better service.  I'd been pondering this very issue, and decided to cross-post my response here: I've been pondering the question in the title and I've come to the conclusion that the answer is that it's possible. Hear me out. Unlike some of the small carriers that work exclusively with one larger carrier, all three major carriers roam on US Cellular today in at least some areas, so far as I know. If that network ceases to exist, then the carriers would presumably want to recover those areas of lost service by building out natively. Thus, people in those areas who may only have service from US Cellular or from US Cellular and one other may gain competition from other carriers backfilling that loss. How likely is it? I'm not sure. But it's definitely feasible. Most notably, AT&T did their big roaming deal with US Cellular in support of FirstNet in places where they lacked native coverage. They can't just lose a huge chunk of coverage whole still making FirstNet happy; I suspect they'll have to build out and recover at least some of that area, if not most of it. So it'd be indirect, but I could imagine it. - Trip
    • Historically, T-Mobile has been the only carrier contracting with Crown Castle Solutions, at least in Brooklyn. I did a quick count of the ~35 nodes currently marked as "installed" and everything mapped appears to be T-Mobile. However, they have a macro sector pointed directly at this site and seem to continue relying on the older-style DAS nodes. Additionally, there's another Crown Castle Solutions node approved for construction just around the corner, well within range of their macro. I wouldn’t be surprised to see Verizon using a new vendor for their mmWave build, especially since the macro site directly behind this node lacks mmWave/CBRS deployment (limited to LTE plus C-Band). However, opting for a multi-carrier solution here seems unlikely unless another carrier has actually joined the build. This node is equidistant (about five blocks) between two AT&T macro sites, and there are no oDAS nodes deployed nearby. Although I'm not currently mapping AT&T, based on CellMapper, it appears to be right on cell edge for both sites. Regardless, it appears that whoever is deploying is planning for a significant build. There are eight Crown Castle Solutions nodes approved for construction in a 12-block by 2-block area.
    • Starlink (1900mhz) for T-Mobile, AST SpaceMobile (700mhz and 850mhz) for AT&T, GlobalStar (unknown frequency) for Apple, Iridium (unknown frequency) for Samsung, and AST SpaceMobile (850mhz) for Verizon only work on frequency bands the carrier has licensed nationwide.  These systems broadcast and listen on multiple frequencies at the same time in areas much wider than normal cellular market license areas.  They would struggle with only broadcasting certain frequencies only in certain markets so instead they require a nationwide license.  With the antennas that are included on the satellites, they have range of cellular band frequencies they support and can have different frequencies with different providers in each supported country.  The cellular bands in use are typically 5mhz x 5mhz bands (37.5mbps total for the entire cell) or smaller so they do not have a lot of data bandwidth for the satellite band covering a very large plot of land with potentially millions of customers in a single large cellular satellite cell.  I have heard that each of Starlink's cells sharing that bandwidth will cover 75 or more miles. Satellite cellular connectivity will be set to the lowest priority connection just before SOS service on supported mobile devices and is made available nationwide in supported countries.  The mobile device rules pushed by the provider decide when and where the device is allowed to connect to the satellite service and what services can be provided over that connection.  The satellite has a weak receiving antenna and is moving very quickly so any significant obstructions above your mobile device antenna could cause it not to work.  All the cellular satellite services are starting with texting only and some of them like Apple's solution only support a predefined set of text messages.  Eventually it is expected that a limited number of simultaneous voice calls (VoLTE) will run on these per satellite cell.  Any spare data will then be available as an extremely slow LTE data connection as it could potentially be shared by millions of people.  Satellite data from the way these are currently configured will likely never work well enough to use unless you are in a very remote location.
  • Recently Browsing

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