Jump to content

T-Mobile LTE & Network Discussion V2


lilotimz

Recommended Posts

For GSM, here's what I saw this morning:

 

687

688

689

709

711

712

713

714

734

735

 

- Trip

So are they making room for a GSM and lte channel or are they doing 2G refarming?

 

Sent from my SAMSUNG-SM-G891A using Tapatalk

Link to comment
Share on other sites

For GSM, here's what I saw this morning:

 

687

688

689

709

711

712

713

714

734

735

 

- Trip

 

With EARFCN of 1025, you have a 5 MHz carrier, centered at 1972.5, extending from 1970-1975.

 

GSM channels, being 200 kHz wide, ARFCN 711 is centered at 1970 exactly, with 712 at 1970.2, 713 at 1970.4, 714 at 1970.6, 734 at 1974.6, and 735 at 1974.8. So we clearly have overlapping GSM with LTE, likely by way of selective resource block shutdown.

 

Oddly, UARFCN of 587 is centered at 1967.5, and Ericsson generally can reduce UMTS bandwidth to 4.2 MHz wide, which would be 1965.4-1969.6, though I have heard that Ericsson has recently matched Nokia in being able to achieve stable 3.8 MHz wide UMTS carriers. The reason this must be a 3.8 MHz carrier is because at both bookends, you have GSM carriers, at 688 (and 689) and 709 and 1965.4 and 1969.6 precisely.

 

So assuming 3.8 MHz wide U1900 carrier, 689 is still right at the end of the carrier, so something strange is definitely going on.

 

Either way, they're stuffing GSM into the LTE carrier (it looks like), which is pretty crazy and exciting.

  • Like 2
Link to comment
Share on other sites

That's really odd. Head scratcher.

 

T-Mobile has a TON of spectrum in Jacksonville, with 50 MHz of AWS-1 and 20 MHz of A block and 30 MHz of C block.

 

This 10 MHz carrier is using up the full A block.

 

In my mind it makes far more sense to deploy in the C block, even if just at 10 MHz, because you have the runway to get to 15 MHz wide.

 

They could easily have 1c U2100, at least 1c U1900, 5 MHz of GSM, 20 MHz L2100, 15 MHz L1900, and 5 MHz L700.

 

That's a conservative approach. Considering that they've been moving quickly to 1 UMTS carrier in lots of markets.

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

That's really odd. Head scratcher.

 

T-Mobile has a TON of spectrum in Jacksonville, with 50 MHz of AWS-1 and 20 MHz of A block and 30 MHz of C block.

 

This 10 MHz carrier is using up the full A block.

 

In my mind it makes far more sense to deploy in the C block, even if just at 10 MHz, because you have the runway to get to 15 MHz wide.

 

They could easily have 1c U2100, at least 1c U1900, 5 MHz of GSM, 20 MHz L2100, 15 MHz L1900, and 5 MHz L700.

 

That's a conservative approach. Considering that they've been moving quickly to 1 UMTS carrier in lots of markets.

 

 

Sent from my iPhone using Tapatalk

Aren't they preparing to swap the C block with Sprint in the PCS swaps?
  • Like 1
Link to comment
Share on other sites

ba11dee0af1f1077980d5cd1acc3126e.jpg a lot of spectrum

 

Sent from my SM-G928P using Tapatalk

Oh wow they make T-Mobile new Jersey market look spectrum starved we have only 43 MHz of spectrum here...no AWS-3 spectrum purchased here

 

Sent from my XT1575 using Tapatalk

Link to comment
Share on other sites

ba11dee0af1f1077980d5cd1acc3126e.jpg a lot of spectrum

 

Sent from my SM-G928P using Tapatalk

Is that a public information source showing in that screenshot?
Link to comment
Share on other sites

Wow - are there maps like these for other carriers?

San Francisco has a map with every RF antenna in the city. You can filter by carrier. https://fusiontables.google.com/DataSource?docid=1jgD0NwaO_dLNhIkjaANj_2fzV9WFwLDGgb8uM57x#map:id=3

 

Was last updated April 2015 though.

 

Sent from my Nexus 6P

Link to comment
Share on other sites

San Francisco has a map with every RF antenna in the city. You can filter by carrier. https://fusiontables.google.com/DataSource?docid=1jgD0NwaO_dLNhIkjaANj_2fzV9WFwLDGgb8uM57x#map:id=3

 

Was last updated April 2015 though.

 

Sent from my Nexus 6P

How many antennas are in San Diego

 

Sent from my XT1575 using Tapatalk

Link to comment
Share on other sites

How many antennas are in San Diego

 

How would he know?  He mentioned San Francisco, not San Diego.  Go ask Carmen.

 

AJ

Link to comment
Share on other sites

OK :) lol I like your sense of humor and what market are you from AJ

 

The home office in Butte, MT.

 

AJ

Link to comment
Share on other sites

San Francisco has a map with every RF antenna in the city. You can filter by carrier. https://fusiontables.google.com/DataSource?docid=1jgD0NwaO_dLNhIkjaANj_2fzV9WFwLDGgb8uM57x#map:id=3

 

Was last updated April 2015 though.

 

Sent from my Nexus 6P

 

I wonder why they have not decommissioned the Nextel sites? Well they show they are decommissioned but why are they still listing them. Has sprint decommissioned them but have not removed the equipment?

Edited by bigsnake49
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

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