Jump to content

Verizon LTE, I'm impressed


illest_ios

Recommended Posts

I'm suggesting they deploy WCS as TD-LTE, and perhaps adding 700 Lower D and E into that depending on testing.

 

That WCS spectrum harmonizes with China Mobile's 2.4 GHz TD-LTE spectrum.

WCS is paired spectrum though.

 

Sent from my Motorola Photon 4G using Tapatalk 2

 

 

Link to comment
Share on other sites

Yes, use the paired spectrum for FD, and the unpaired for TD.

 

Don't know how that affects Sirius radio, however. That's the hitch.

Neal's article says that AT&T is using the C and D blocks (which, of course, are the unpaired blocks) as guard bands.

 

http://www.extremetech.com/electronics/131316-att-and-sirius-xm-propose-rules-to-allow-lte-on-wcs

Link to comment
Share on other sites

Yes, use the paired spectrum for FD, and the unpaired for TD.

 

Don't know how that affects Sirius radio, however. That's the hitch.

Will not fly. The unpaired WCS C and D blocks are being used as de facto guard bands to protect SDARS. Plus, those blocks are only 5 MHz TDD.

 

AJ

Link to comment
Share on other sites

Will not fly. The unpaired WCS C and D blocks are being used as de facto guard bands to protect SDARS. Plus, those blocks are only 5 MHz TDD.

 

AJ

 

Yes, I figured that out as soon as I started reading Neal's article. 

 

Oh well... 

Link to comment
Share on other sites

Sprint should just sell its WCS A and B blocks in the southeast US to AT&T so it makes great use of the spectrum so that AT&T can get a full 10x10 LTE carrier on WCS spectrum.  Sprint is just sitting on it.  I would much rather have them swap some WCS spectrum for PCS spectrum in areas where they need help.

Link to comment
Share on other sites

I am lying in bed, typing on a tablet. I got "scooped" while I was still writing.

 

AJ

Link to comment
Share on other sites

I am lying in bed, typing on a tablet. I got "scooped" while I was still writing.

 

AJ

I figured you probably were, I just had to point it out.

 

Sprint should just sell its WCS A and B blocks in the southeast US to AT&T so it makes great use of the spectrum so that AT&T can get a full 10x10 LTE carrier on WCS spectrum.  Sprint is just sitting on it.  I would much rather have them swap some WCS spectrum for PCS spectrum in areas where they need help.

I don't see any way where AT&T gives Sprint any PCS in exchange for the WCS it has, I'd rather AT&T just buy it from them because Sprint is never going to use it and AT&T would.

Link to comment
Share on other sites

Anyone chime in here?  Is Phase 1 Wimax converted sites able to pull these speeds or is it Phase 2 and on?

 

No. A 20mhz TDD-LTE carrier running in Clearwires setup will top out at ~90 / ~40 due to the continuous blocked split up in a 3:2 fashion. Going for 18 mhz of usable spectrum as very simple estimates for guard bands.. that gives us 11-12 mhz for DL and 5-7 mhz fo UL. 

 

A 20mhz TDD carrier is slightly superior to a 10x10 FDD carrier on the downlink and somewhat inferior on the uplink. To match a 20x20 FDD setup you need 40mhz TDD carriers or 20+20 CA'd TDD carriers. 

 

But that's no issue as Sprint has at least 40-50 mhz of BRS spectrum and a hodgepodge of EBS spectrum meaning Sprint can deploy additional 20 mhz TD carriers as needed in the future to keep speeds stable. T-Mobile, Verizon, and ATT will need to refarm other spectrum if their 20mhz carriers start bogging down. 

 

  • Like 2
Link to comment
Share on other sites

No. A 20mhz TDD-LTE carrier running in Clearwires setup will top out at ~90 / ~40 due to the continuous blocked split up in a 3:2 fashion. Going for 18 mhz of usable spectrum as very simple estimates for guard bands.. that gives us 11-12 mhz for DL and 5-7 mhz fo UL. 

 

A 20mhz TDD carrier is slightly superior to a 10x10 FDD carrier on the downlink and somewhat inferior on the uplink. To match a 20x20 FDD setup you need 40mhz TDD carriers or 20+20 CA'd TDD carriers. 

 

But that's no issue as Sprint has at least 40-50 mhz of BRS spectrum and a hodgepodge of EBS spectrum meaning Sprint can deploy additional 20 mhz TD carriers as needed in the future to keep speeds stable. T-Mobile, Verizon, and ATT will need to refarm other spectrum if their 20mhz carriers start bogging down. 

I thought the most you could use was 20+20 with CA?

Link to comment
Share on other sites

I thought the most you could use was 20+20 with CA?

 

According to Qualcomm, LTE-A with CA can combine multiple LTE carriers of up to 100 MHz (ex: 20+20+20+20+20) to create one big fat huge pipe.  However no wireless carrier has that much free spectrum to spare nor has the power output needed to do this though.  Going past 20+20 with CA shouldn't be an issue.

Link to comment
Share on other sites

According to Qualcomm, LTE-A with CA can combine multiple LTE carriers of up to 100 MHz (ex: 20+20+20+20+20) to create one big fat huge pipe.  However no wireless carrier has that much free spectrum to spare nor has the power output needed to do this though.  Going past 20+20 with CA shouldn't be an issue.

 

I think he was referring to the new RRUs. They can be configured for 20, 40, or 20+20 MHz.

Link to comment
Share on other sites

According to Qualcomm, LTE-A with CA can combine multiple LTE carriers of up to 100 MHz (ex: 20+20+20+20+20) to create one big fat huge pipe.  However no wireless carrier has that much free spectrum to spare nor has the power output needed to do this though.  Going past 20+20 with CA shouldn't be an issue.

Oh, Neat.

 

I think he was referring to the new RRUs. They can be configured for 20, 40, or 20+20 MHz.

That wasn't directly what I was talking about that but maybe that's what I was thinking of.

Link to comment
Share on other sites

So that's Verizon's AWS 20x20 FDD, to supplement their 700mhz 10x10 FDD, impressive. Very impressive. 

 

Not so impressive if they're deploying on every third site like they did with 700Mhz. Hopefully, this time around they'll actually densely deploy.

Link to comment
Share on other sites

Not so impressive if they're deploying on every third site like they did with 700Mhz. Hopefully, this time around they'll actually densely deploy.

 

Considering Verizon's original spacing was for 1900, deploying 700mhz on every third site is fine for overlay. AWS will require using the same dense PCS spacing they have in effect now. So that should be fine, in fact, should be pretty seamless.

 

I gotta hand it to them, very good business and service.

Link to comment
Share on other sites

Verizon needs AWS in Rapid City. 1/3 of their LTE 750 sites drop to 1-2Mbps in the evenings. Another third drop to 2-4Mbps, and the final third are over 4. I do get between 30-40Mbps from Midnight to 5 AM though. ;)

 

Robert via Samsung Note 8.0 using Tapatalk Pro

  • Like 2
Link to comment
Share on other sites

11/01/2012 is my first documented ticket on the current issue for the site.  It's still broke as of today.  Between me and another member we've probably opened about 30-40 tickets this year on the site.  They let my co-worker out of his contract with his brand new 5 lines and phones scott free over the site.  I've gotten probably $300+ in credits over the site.  Opened another ticket today to start the process for more credits and cover my butt for going over my 300meg roaming due to this site.  Seems like it would be easier to fix and provide the customers in the downtown area with a working data connection.  :wall:

Since last year on my tower I use to be constant 4 bars now one bar.  I called for 3 months straight due to roaming to find out they upgraded the the tower to a gmo site now I get one bar -109db.   I'm tired of hearing theirs a ticket opened and we will call you they never do.  I only had one person that called me back.

Link to comment
Share on other sites

Verizon needs AWS in Rapid City. 1/3 of their LTE 750 sites drop to 1-2Mbps in the evenings. Another third drop to 2-4Mbps, and the final third are over 4. I do get between 30-40Mbps from Midnight to 5 AM though. ;)

 

Have you gone spotting yet and made a tally of how many VZW sites are in the city limits and then how many of those have been overlaid with LTE?

 

AJ

Link to comment
Share on other sites

Next month my Verizon contract is up so it's decision time.

I was hopeful of ditching dual service and going only with Sprint to save money.

Unfortunately Sprint just isn't good enough yet, an LTE/800MHz voice tower (SE 44th & Sooner Rd. in Del City) just a mile away from my gym is unusable inside.  Verizon works well. 

Since the mobile isn't allowed in the office it's real important to me that I catch up on things while in the gym during lunch.

Maybe 800 MHz LTE (which we should get in a couple of years?) will help and I can kick the Verizon habit. 

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