Jump to content

Number of EVDO carriers per sector in the Chicago market?


briank101

Recommended Posts

 

With LTE, the network can tell your phone to move to a different carrier so it can balance the load that way. In this way adding another carrier will improve network speeds. Simply moving users from a very congested carrier to a less congested one will improve the speeds for the users. Their THEORHETICAL top speed won't improve, but simply dividing up the load (not through aggregation, just moving some users to the other 5x5 carrier) will improve their real life performance.

That's LTE multi-carrier technology. Not all vendors have support for it. Maybe all Network Vision vendors do, but I've only confirmed NSN and Samsung gear to have it.

 

That seems anti factual, Neal.  If that were true, then a 10 MHz FDD carrier would be able to provide disproportionately greater peak speeds than could a 5 MHz FDD carrier.  However, that is not the case.  So, I would like to see some evidence to support your assertion.

 

AJ

I believe the problem is substantially more evident with 1.4MHz/3MHz to 5MHz carriers. If I remember correctly, the overhead subcarrier set size does not change based on the total carrier size. This means that the ratio of data subcarriers to overhead subcarriers becomes a problem at small carrier sizes.

 

And note that I was comparing a wide carriers against aggregated carriers, which it will beat on downlink performance because carrier aggregation necessarily cannot offer the same performance that a wide LTE carrier can. This is because each carrier being aggregated has its own set of overhead subcarriers, which subtracts from the overall available data subcarriers. 

Link to comment
Share on other sites

That's LTE multi-carrier technology. Not all vendors have support for it. Maybe all Network Vision vendors do, but I've only confirmed NSN and Samsung gear to have it.

 

I have seen lots of Sprint docs that reference network initiated load balancing with Network Vision equipment.  I have not seen any caveats due to OEM.  Which there are often when one of the vendors cannot provide the noted feature.

 

Robert

  • Like 1
Link to comment
Share on other sites

I believe the problem is substantially more evident with 1.4MHz/3MHz to 5MHz carriers. If I remember correctly, the overhead subcarrier set size does not change based on the total carrier size. This means that the ratio of data subcarriers to overhead subcarriers becomes a problem at small carrier sizes.

 

In terms of subcarriers to spectrum bandwidth, all FDD configurations are the same -- with one exception.  The 1.4 MHz FDD configuration is the outlier.  Otherwise, all others scale linearly with spectrum bandwidth:  5 MHz FDD contains 300 subcarriers, 10 MHz FDD contains 600 subcarriers, 15 MHz FDD contains 900 subcarriers, etc.

 

Additionally, I am not seeing the overhead issue that you state because the peak carrier speeds -- assuming a Category 4 UE -- also scale linearly with those bandwidths and subcarriers.

 

AJ

Link to comment
Share on other sites

In terms of subcarriers to spectrum bandwidth, all FDD configurations are the same -- with one exception.  The 1.4 MHz FDD configuration is the outlier.  Otherwise, all others scale linearly with spectrum bandwidth:  5 MHz FDD contains 300 subcarriers, 10 MHz FDD contains 600 subcarriers, 15 MHz FDD contains 900 subcarriers, etc.

 

Additionally, I am not seeing the overhead issue that you state because the peak carrier speeds -- assuming a Category 4 UE -- also scale linearly with those bandwidths and subcarriers.

 

AJ

Category 4 UE won't have carrier aggregation. All LTE CA devices are Category 6 UE. And all UE categories are done with the assumption you are using a single carrier channel. Carrier aggregation throughput differs from the maximum defined throughput for a UE category.

Link to comment
Share on other sites

  • 3 weeks later...

Category 4 UE won't have carrier aggregation. All LTE CA devices are Category 6 UE. And all UE categories are done with the assumption you are using a single carrier channel. Carrier aggregation throughput differs from the maximum defined throughput for a UE category.

 

I just caught up with this discussion.  I am not sure why carrier aggregation entered the equation.  I was referencing the total capacity of standalone carriers.  In such case, two 5 MHz FDD carriers equal one 10 MHz FDD carrier, for example.

 

AJ

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

    • My hope is they can spot something in the data that was exported. I am going after all 4 carriers on a multitude of phones and Android versions. My S24 did work.  I have not checked another S24 or S22.  S21s failed which are on Android 14 as well. It should be noted I did not reboot after updates and some of the data was captured on the prior update. Data from some new Boost Mobile Dish (Echostar) sites in the Wheeling area did make it in. Was hoping for more SA data from the duo. Many of the phones are just LTE.
    • I was traveling for a couple of days.   Sunday evening, I upload from 3 phones.  A S-22 and two Moto 5G phones.  Everything looked ok.    How do we explain that?   One person has issues and another person does not.  All my phones have the latest update.
    • 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.
  • Recently Browsing

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