Jump to content

CDMA vs EDGE vs HSPA vs LTE range


RAvirani

Recommended Posts

Infinity.  To Alpha Centauri and beyond.

 

AJ

  • Like 1
Link to comment
Share on other sites

A slightly more serious answer: the more advanced technologies tend to be more susceptible to interference, so the effective usable range for the same power is higher with simpler signals like those in GSM and CDMA 1X.

 

GSM, due to its use of TDMA, also has a hard limitation on its range of 35 km.

Link to comment
Share on other sites

GSM, due to its use of TDMA, also has a hard limitation on its range of 35 km.

 

...if timing advance is limited to one time slot.

 

AJ

Link to comment
Share on other sites

A slightly more serious answer: the more advanced technologies tend to be more susceptible to interference, so the effective usable range for the same power is higher with simpler signals like those in GSM and CDMA 1X.

 

GSM, due to its use of TDMA, also has a hard limitation on its range of 35 km.

So something like CDMA>GSM>HSPA>LTE

Link to comment
Share on other sites

So something like CDMA>GSM>HSPA>LTE

And yet, in real life, I can get CDMA 1x on 800 much further distances than EDGE on 850.

 

Using Tapatalk on Note 8.0

  • Like 3
Link to comment
Share on other sites

I would guess HSPA goes farther than EDGE because of the fact that HSPA is highly (and I mean highly) derivative of CDMA. On 850 it is probably fairly close to CDMA 1x. Not exactly there due to higher channel bandwidth, but close.

 

Sent from my SM-N920V using Tapatalk

Link to comment
Share on other sites

I think in reality, what goes farther is gonna be largely network dependant. On paper 1X is probably king, followed by GSM, and then UMTS/WCDMA, and lastly LTE.

 

In reality I've seen it all over the place, though one thing that holds true almost all of the time is that 1x is king for distance. Locally, EDGE on 850 outcovers UMTS on 850, and UMTS on 850 outdoes B17 LTE, though I often see B17 LTE and UMTS 850 being a close tie.

 

On T-Mobile I have seen band 4 LTE outperform UMTS on PCS in several odd instances as far as signal goes.

 

I do believe it's been claimed that the 35 km distance on GSM is no longer true and that it can reach almost as far as CDMA 1x now. I've personally never picked up an EDGE signal from further than maybe 20 miles away, that I know of anyway.

  • Like 1
Link to comment
Share on other sites

I think in reality, what goes farther is gonna be largely network dependant. On paper 1X is probably king, followed by GSM, and then UMTS/WCDMA, and lastly LTE.

 

In reality I've seen it all over the place, though one thing that holds true almost all of the time is that 1x is king for distance. 

...

 

...

On T-Mobile I have seen band 4 LTE outperform UMTS on PCS in several odd instances as far as signal goes.

 

Wider LTE signal is usable for a greater distance than a narrower one.

Link to comment
Share on other sites

Wider LTE signal is usable for a greater distance than a narrower one.

Yes that is one of the things to factor in. Just today I was in a place where I could barely hold a signal on WCDMA 850 but had little problem hanging onto B17 LTE. That's a 5mhz WCDMA channel vs a 10 MHz LTE channel.

Link to comment
Share on other sites

Yes that is one of the things to factor in. Just today I was in a place where I could barely hold a signal on WCDMA 850 but had little problem hanging onto B17 LTE. That's a 5mhz WCDMA channel vs a 10 MHz LTE channel.

I notice that on AT&T too all the time considering I spend a lot of time in an area with -114 to -118 LTE/HSPA. Phone holds on to LTE a lot better. How would they compare if they were both 5mhz tho?

Link to comment
Share on other sites

I notice that on AT&T too all the time considering I spend a lot of time in an area with -114 to -118 LTE/HSPA. Phone holds on to LTE a lot better. How would they compare if they were both 5mhz tho?

UMTS would have somewhat better fringe performance.

 

CDMA2000 would be much better still. Just because WCDMA has some CDMA style features, it is a totally different type of signal.

Link to comment
Share on other sites

UMTS would have somewhat better fringe performance.

 

CDMA2000 would be much better still. Just because WCDMA has some CDMA style features, it is a totally different type of signal.

 

HSPA is an issue for W-CDMA.  If the carrier were running only Release 99 W-CDMA, it would have greater range.

 

AJ

  • Like 2
Link to comment
Share on other sites

I find HSPA+/WCDMA to only have the slightest edge over LTE in the same frequency. Here in Western South Dakota, T-Mobile has both AWS WCDMA and LTE, and AT&T has both Cellular 850 WCDMA and LTE. And all four instances are 5MHz FDD carriers. In both instances, the WCDMA will peter out at the same point as the LTE, or only a few hundred feet farther. And the LTE is more usable with a fringe signal than the WCDMA.

 

I lose WCDMA between -109 and -111 RSSI. It is completely unusable at this strength. It may provide the slightest throughput between -105 and -109 RSSI. But I really need a -103 or better on WCDMA to be useful.

 

I can still use Tmo LTE on a 5MHz channel down to a -128 RSRP. Still pull 1-2Mbps DL. But upload will time out, or run a paltry 0.01Mbps. AT&T LTE won't really work past -118 RSRP here. Because they have a lot more noise from so many sites, and they have a lot more traffic, and I don't believe they run 4x MIMO.

 

Using Tapatalk on Note 8.0

Link to comment
Share on other sites

Ok so this conversation has raised a question for me. How is it that Verizon's 700 MHz LTE dies when CDMA800 is at about -98 when Sprints 800 MHz LTE cannot eclipse CDMA1900?

 

Base station power/gain may be configured for capacity, not coverage.

 

AJ

Link to comment
Share on other sites

Base station power/gain may be configured for capacity, not coverage.

 

AJ

I thought 800 was meant for coverage while 1900 and 2.5 were capacity? And also it's not like a single site in referring to - my overall experience has been that 800mhz LTE dies (-120) when 3G on 1900mhz is ~-98 to -100

Link to comment
Share on other sites

RAvirani, on 24 Dec 2015 - 4:16 PM, said:

 

I thought 800 was meant for coverage while 1900 and 2.5 were capacity? And also it's not like a single site in referring to - my overall experience has been that 800mhz LTE dies (-120) when 3G on 1900mhz is ~-98 to -100

Not surprising. Those are basically equivalent RF figures between the two airlinks. For further reference, read my article on The Wall. RSSI vs RSRP.

 

AJ

  • Like 2
Link to comment
Share on other sites

Not surprising. Those are basically equivalent RF figures between the two airlinks. For further reference, read my article on The Wall. RSSI vs RSRP.

 

AJ

So Verizon has just increased the power on their LTE to higher really? Also wouldn't it make more sense if the signals were equivalent on the same band (PCS LTE)?
Link to comment
Share on other sites

So Verizon has just increased the power on their LTE to higher really?

 

Not sure.  But VZW band 13 is 10 MHz FDD -- and often has 10-20 MHz FDD backing it on band 4.  In that situation, coverage may be more important than capacity.  Sprint does not have such luxury, since both band 25 and band 26 typically are limited to 5 MHz FDD.

 

AJ

Link to comment
Share on other sites

Not sure. But VZW band 13 is 10 MHz FDD -- and often has 10-20 MHz FDD backing it on band 4. In that situation, coverage may be more important than capacity. Sprint does not have such luxury, since both band 25 and band 26 typically are limited to 5 MHz FDD.

 

AJ

Oh that makes sense. So once sprint refarms some more PCS LTE and gets more 2.5 carriers up, they may increase power levels on B26?

Link to comment
Share on other sites

Not sure. But VZW band 13 is 10 MHz FDD -- and often has 10-20 MHz FDD backing it on band 4. In that situation, coverage may be more important than capacity. Sprint does not have such luxury, since both band 25 and band 26 typically are limited to 5 MHz FDD.

 

AJ

Do you really think that 800 MHz LTE would crash if it were optimized for coverage in a market with 2x B41, and 2x 5Mhz FDD B25 (one of them growing to 10 MHz FDD)?

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

    • 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.
    • Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
  • Recently Browsing

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