Jump to content

Tmobile looking at Verizon's 700mhz spectrum


IamMrFamous07

Recommended Posts

Remapped channels are a headache for us RF guys.

 

At the family's vacation home over the weekend, we had one inexplicably broken LNB that prevented reception of the 103° W orbital satellite, which transmits the local affiliate feeds. I had to jury rig a solution with a UHF antenna so that we could try to pick up the Chiefs-Broncos game OTA. But I had to go online to double check that the Albuquerque NBC affiliate, KOB, which has long been known for its position on low VHF channel 4, had moved to UHF with the ATSC transition. Indeed, it had moved its physical channel to UHF channel 26, remapped to virtual channel 4. And my UHF antenna solution worked. But the antenna did not pick up the local CBS affiliate, which had moved back to its high VHF channel 13 position, hence my need to confirm the NBC affiliate physical channel had gone UHF.

 

AJ

Where is your vacation home here in nm?

Link to comment
Share on other sites

  • 2 weeks later...

Looks like AT&T wants to cause some disruption in Tmobile's plan to bid on the 700 MHz A block spectrum from Verizon.  I really hope AT&T is not allowed to buy the 700 MHz A block spectrum from Verizon.  If ATT does win this 700 MHz A block spectrum, they should be barred from participating in the 600 MHz auction.

 

http://www.fiercewireless.com/story/report-att-vying-t-mobile-verizons-700-mhz-block-spectrum/2013-12-05

  • Like 1
Link to comment
Share on other sites

Where is your vacation home here in nm?

 

About five miles west of Santa Fe.

 

AJ

Link to comment
Share on other sites

Pojoaque? Tesuque?

 

Pojoaque and Tesuque are too far north.  Pojoaque is basically where Robert lived.  No, this is a few miles off the Relief Route due west of Santa Fe.

 

AJ

  • Like 1
Link to comment
Share on other sites

Pojoaque and Tesuque are too far north.  Pojoaque is basically where Robert lived.  No, this is a few miles off the Relief Route due west of Santa Fe.

 

AJ

Surprisingly when i lived in Santa Fe, I lived close to what is the relief route and airport road.  It used to be way out there.  Now it is just a thought. 

Link to comment
Share on other sites

Surprisingly when i lived in Santa Fe, I lived close to what is the relief route and airport road.  It used to be way out there.  Now it is just a thought. 

 

Yep, we drive through the arroyo on Paseo de River and hit the Relief Route at Airport Road whenever coming and going from Albuquerque.

 

AJ

Link to comment
Share on other sites

Yep, we drive through the arroyo on Paseo de River and hit the Relief Route at Airport Road whenever coming and going from Albuquerque.

 

AJ

 

So I wonder what they meant by/or why they called it Relief Route? 

 

HMMMMM....

 

sweet-jesus-have-mercy.jpg

Link to comment
Share on other sites

So I wonder what they meant by/or why they called it Relief Route? 

 

Two things: relief from traffic and radioactive waste transit through the heart of Santa Fe.

 

AJ

Link to comment
Share on other sites

If the FCC is committed to 4 nation wide carriers it cannot do a half arsed job, it has to give the two 'smaller' carriers a shot at sub gig spectrum (I know sprint have 800mhz, but I mean a significant chunk like 20-40MHz). The big two are not exactly innovating, their pricing usually all but matches each other, they roll out service pretty much as it suits their marketing department unlike Sprint who seems to be rolling it out as fast as it can or tmo who seems to be doing it as quickly as they can afford. Sprint and tmo cannot be 'token competitors'. Whilst Sprint is doing a good job these days they still need a decent chunk of low dial spectrum and to have a chance at expanding coverage. It would be nice to see them both get some assistance to level they playing field. 

  • Like 1
Link to comment
Share on other sites

Two things: relief from traffic and radioactive waste transit through the heart of Santa Fe.

 

AJ

If there is anything people need relief from, it's Santa Fe traffic. Driving down Cerrillos or St. Francis at rush hour is enough to make someone batty. I actually preferred driving in ABQ.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

Link to comment
Share on other sites

New report that Verizon is open to swapping spectrum for 700 MHz A block.  I see this as an opportunity for Verizon to dominate the AWS spectrum as well by asking Tmobile to swap some of its AWS spectrum in exchange for some 700 MHz A blocks.  I wonder if Tmobile will bite on this.

 

http://www.fiercewireless.com/story/verizon-open-swapping-spectrum-700-mhz-block/2013-12-11

Link to comment
Share on other sites

New report that Verizon is open to swapping spectrum for 700 MHz A block.  I see this as an opportunity for Verizon to dominate the AWS spectrum as well by asking Tmobile to swap some of its AWS spectrum in exchange for some 700 MHz A blocks.  I wonder if Tmobile will bite on this.

 

http://www.fiercewireless.com/story/verizon-open-swapping-spectrum-700-mhz-block/2013-12-11

I don't see how swap could be a solution for T-Mobile since their AWS is all deployed. I can only think of AWS rich market like Dallas where they could shut down their A block and divest to Verizon, but they'll still pay a lot of money for 700Mhz A so not sure if that'd make much sense...

Link to comment
Share on other sites

I don't see how swap could be a solution for T-Mobile since their AWS is all deployed. I can only think of AWS rich market like Dallas where they could shut down their A block and divest to Verizon, but they'll still pay a lot of money for 700Mhz A so not sure if that'd make much sense...

 

Tmobile's goal is still to eventually move HSPA+ off of AWS and onto PCS correct?  However in the time frame that Verizon needs to sell its 700 MHz A block spectrum, I don't see how this can happen.

 

Honestly I don't really want to see Verizon get any stronger with more AWS spectrum.  I would rather just see Verizon cash out on the 700 MHz A block spectrum and move on.  They have a 20x20 LTE AWS block in the eastern half of the US already and I don't think they need anymore.  Perhaps the goal for Verizon in the 700 MHz A block swap would be to fill in the gaps on the western half of the US so that it holds more than just a 10x10 LTE block of AWS spectrum.

 

Link to comment
Share on other sites

I don't see how swap could be a solution for T-Mobile since their AWS is all deployed. I can only think of AWS rich market like Dallas where they could shut down their A block and divest to Verizon, but they'll still pay a lot of money for 700Mhz A so not sure if that'd make much sense...

 

VZW seems ready to divest its Lower 700 MHz A block licenses in as many markets as possible.  Meanwhile, in exchange, T-Mobile might be willing to shed some AWS spectrum across numerous secondary and tertiary markets.  After all, let us be honest -- T-Mobile for years has shown tepid interest in updating those markets.  It seems more than content to be the new "MetroPCS."  And VZW has a much higher proportion of its subs outside of the top 100 markets, so it may need the smaller market AWS spectrum far more than T-Mobile does.

 

AJ

Link to comment
Share on other sites

VZW seems ready to divest its Lower 700 MHz A block licenses in as many markets as possible.  Meanwhile, in exchange, T-Mobile might be willing to shed some AWS spectrum across numerous secondary and tertiary markets.  After all, let us be honest -- T-Mobile for years has shown tepid interest in updating those markets.  It seems more than content to be the new "MetroPCS."  And VZW has a much higher proportion of its subs outside of the top 100 markets, so it may need the smaller market AWS spectrum far more than T-Mobile does.

 

AJ

That actually make pretty good sense, assuming those markets still have sufficient amount of left over AWS and PCS so that voice remains uninterrupted and HSPA/LTE service could be deployed. I'd much rather see T-Mobile acquiring 700Mhz A from smaller smaller providers or spectrum holders in those secondary markets for rural deployment, but oh well.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • 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...