Jump to content

Sprint switches gears, backs FDD rather than TDD plan for 600 MHz auction


Recommended Posts

 

Acknowledging that an FDD allocation for the upcoming 600 MHz auction has considerably more support than the TDD approach it has been pushing, Sprint said it now supports the idea of an FDD band plan, provided it is structured to maximize "auctionable bi-directional paired spectrum."

 

Read more: Sprint switches gears, backs FDD rather than TDD plan for 600 MHz auction - FierceWirelessTech http://www.fiercewireless.com/tech/story/sprint-switches-gears-backs-fdd-rather-tdd-plan-600-mhz-auction/2014-01-09#ixzz2pvAMgtza 

Subscribe at FierceWirelessTech

 

 

Link to comment
Share on other sites

It's sad the other carriers are so dead set on FDD, it is not the most efficient mode for LTE. It if also possible that there will be isolated 6MHZ channels that become available with no possible paired channel for a discrete uplink.

 

Sent from my Nexus 7 using Tapatalk

 

 

Link to comment
Share on other sites

So from this article, it seems Sprint is set on FDD on the 600 Mhz auction? 

Sprint originally wanted TDD for 600 MHz but it's abandoned that plan because no one else wanted it. Also, I believe that TDD isn't well suited for these lower frequencies.

Link to comment
Share on other sites

Sprint originally wanted TDD for 600 MHz but it's abandoned that plan because no one else wanted it. Also, I believe that TDD isn't well suited for these lower frequencies.

 

Okay, but FDD would be more ideal than? If sprint were to snag some 600 Mhz for FDD, this would make Sprint a Quad band LTE network? 

Link to comment
Share on other sites

Okay, but FDD would be more ideal than? If sprint were to snag some 600 Mhz for FDD, this would make Sprint a Quad band LTE network? 

Ehh FDD VS. TDD is kind of a hot topic, but both have their strength and weaknesses. Also, Yes is if Sprint got some 600 MHz it would be quad band.

  • Like 1
Link to comment
Share on other sites

I'd rather have 1xA carriers on 600 unless Sprint switches to VoLTE

600 may propagate too well for something that works so well with a weak signal like CDMA. It almost couldn't be used in an urban environment at all. You will have lots of bars in your signal strength indicator, but the quality of the signal would get pretty crappy. It's almost too good on SMR.

 

LTE on 600, especially given the fragile LTE airlink, could prove to be pretty good. Especially in rural areas allowing one boomer tower to cover a lot of distance.

 

Robert via Nexus 5 using Tapatalk

 

 

  • Like 2
Link to comment
Share on other sites

Hmm Robert that's interesting. I've never heard that before (well I knew CDMA worked well on a  weak signal and LTE was pretty fragile).

 

What about capacity on 600 LTE? Good enough to fill in holes left by 800/1900/2500 I assume, but would only be used as a last ditch effort with the pretty low capacity, correct? Would that give the LTE coverage needed to get a leg up on VoLTE rollout?

Link to comment
Share on other sites

Quadband phone???? ;)

 

Sent from my Nexus 5

 

There are already quad band lte phones on the market for other carriers so this is not unrealistic :) Over the coming years I fully expect to see hexaband LTE phones, at least if we see sprint and tmo hop into the sack with each other. The PA's exist, there are issues right now with fitting too many antennas in phones but this will evolve. 

 

It would be interesting to see what SprinTmo and to an extent AT&T did with regard to band access. Do you allow pretty much all phones on all bands or restrict access to some bands to premium phones? Sprint have said triband for all, but if they suddenly find themselves with 6 or 7  bands (600, 700 , 800 , 1700\2100, 1900 , 2500), would this affect the cost of handsets enough to make it worthwhile to not include access to some of the bands? i.e. if you have access to 1900 LTE does it really matter to allow access to the (potential) 1700\2100 LTE. These are just idle musing rather than any suggestion Sprint may attempt to screw people or anything similar and it will be a little less complex should Sprint not buy tmo.

Link to comment
Share on other sites

Hmm Robert that's interesting. I've never heard that before (well I knew CDMA worked well on a weak signal and LTE was pretty fragile).

 

What about capacity on 600 LTE? Good enough to fill in holes left by 800/1900/2500 I assume, but would only be used as a last ditch effort with the pretty low capacity, correct? Would that give the LTE coverage needed to get a leg up on VoLTE rollout?

VoLTE on 600 will provide decent coverage. It will be closer to closing the VoLTE coverage gap. Put it on 450 like Africa, and maybe close it all together.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

Link to comment
Share on other sites

Question.... With 800 already in place wouldn't 600 just be redundant?

If no additional low frequency capacity was ever needed, then yes. But ideally, Sprint should have at least a 10MHz wide low frequency carrier. That can never happen on 800.

 

Sprint needs to do the best it can to be competitive. It will survive without any 600. But if and when it comes to market, it should try to get it.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

  • Like 2
Link to comment
Share on other sites

VoLTE on 600 will provide decent coverage. It will be closer to closing the VoLTE coverage gap. Put it on 450 like Africa, and maybe close it all together.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

 

I know you may just be throwing that frequency out there but isn't 450Mhz reserved for public safety in the US?  I know in my area, public safety uses 453 and 458 Mhz. 

Link to comment
Share on other sites

I know you may just be throwing that frequency out there but isn't 450Mhz reserved for public safety in the US?  I know in my area, public safety uses 453 and 458 Mhz.

 

It was used for theoretical discussion of how to close the VoLTE coverage gap. It certainly is not possible in the U.S. But I bless the rains down in Africa.

 

Robert

  • Like 1
Link to comment
Share on other sites

It was used for theoretical discussion of how to close the VoLTE coverage gap. It certainly is not possible in the U.S. But I bless the rains down in Africa.

 

Robert

 

I thought you were speaking in theory but just making sure. Thanks. 

Link to comment
Share on other sites

It was used for theoretical discussion of how to close the VoLTE coverage gap. It certainly is not possible in the U.S. But I bless the rains down in Africa.

 

Toto, I've a feeling we're not in Kansas anymore.

 

AJ

  • Like 4
Link to comment
Share on other sites

It was used for theoretical discussion of how to close the VoLTE coverage gap. It certainly is not possible in the U.S. But I bless the rains down in Africa.

 

Robert

 

No blessing of rain for california? :(

Link to comment
Share on other sites

Toto, I've a feeling we're not in Kansas anymore.

 

AJ

I was hoping someone would get it.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

Link to comment
Share on other sites

I was hoping someone would get it.

 

I meet you all the way.

 

AJ

  • 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

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