Jump to content

Recommended Posts

Posted

 

I agree that WiMax is less than ideal. But that being said, Puerto Rico only had WiMax Protection Sites. Protection sites are deployed with zero downtilt to maximize coverage. This only made the penetration problem worse. In fully deployed and appropriately dense network conditions, WiMax performed OK. But Sprint LTE is superior in every way.

 

Robert via Samsung Note II via Tapatalk

 

I had no idea that protection sites had no downtilt. I learn something everyday :D

 

I also wanted to add that if you were to go on a roadtrip or something similar when you are constantly moving from one site to another the handoff is incredibly slow. Very ineficient for a cell phone in my opinion.

 

Sent from my SPH-L710 using Tapatalk 2

 

 

Posted

OT, I drove from Springfield MA to Cleveland OH, on the 22nd on I-84 and I-80. What amazed me is how much Edge AT&T had. Granted Sprint roamed on 3G, but it was 3G.

Posted

Sprint has some WCS, and in the near future, it will hopefully become more valuable because at&t is going to utilize the band.

 

Sent from my Galaxy Nexus running Paradigm 3.0 using Forum Runner

 

Maybe they can exchange it for some PCS in Florida :) .

Posted

Yes, VZW should use the spectrum or give it back. There needs to be a timeline. What VZW is doing is anti-competitive and they are trying to create a duopoly with AT&T.

 

I am not sure what makes you think that there is no timeline. See Title 47 Parts 27.13 and 27.14.

 

http://www.ecfr.gov/....0.1.1.5.2.49.4

 

The timeline is long for AWS 2100+1700 MHz licenses because the spectrum is not ideal. Government incumbents have to be relocated from the 1700 MHz uplink. No AWS licensee has hit its first buildout deadline yet, so no AWS spectrum should be revoked yet.

 

And lest you think that I am soft on the duopoly, I suggest that you read almost anything that I have written here at S4GRU. Try a search on "anti competitive asshats." That should bring up some of my scathing criticisms of both VZW and AT&T. Moreover, if you want my perspective on carriers using protection sites to retain licenses, read the very first piece that I wrote for S4GRU.

 

http://s4gru.com/ind...t-of-hypocrisy/

 

For basically a decade, I have hammered away at the use of protection sites. But there is a big difference between fat and happy AT&T sitting on prime PCS 1900 MHz spectrum in smaller markets and cash strapped Clearwire grinding to a halt with marginal BRS/EBS 2600 MHz spectrum in several already well served major markets.

 

Regardless, your protests, Richard, strike me less as concerned altruism about use of public spectrum, more as sour grapes over the dearth of WiMAX in San Diego County.

 

AJ

  • Like 4
Posted

 

 

Regardless, your protests, Richard, strike me less as concerned altruism about use of public spectrum, more as sour grapes over the dearth of WiMAX in San Diego County.

This is true. I really do HATE HATE HATE Clearwire. With that being said, it really has opened my eyes to the practices of all the cell phone companies. They basically can hold a community hostage. They milk every last dime they can out of the consumer and don't give a damn about fairly using the public airwaves. Not providing adequate cell coverage can give an entire region an economic disadvantage. What business would want to operate in an area without proper 4G coverage? I doubt I will be any less bitter until Sprint 4G is widespread in San Diego.

Posted

This is true. I really do HATE HATE HATE Clearwire. With that being said, it really has opened my eyes to the practices of all the cell phone companies. They basically can hold a community hostage. They milk every last dime they can out of the consumer and don't give a damn about fairly using the public airwaves. Not providing adequate cell coverage can give an entire region an economic disadvantage. What business would want to operate in an area without proper 4G coverage? I doubt I will be any less bitter until Sprint 4G is widespread in San Diego.

 

Dude calm down man....sprint has bought clearwire and now has the rights to the 2.5 ghz spectrum. Once the deal is finalizes...i expect to see huge ramp up of 2.5 ghz TDD LTE in 2014. I expect sprint to focus on the 1900 mhz and 800 mhz LTE build out in 2013

 

Sent from my MB855 using Tapatalk 2

  • Like 2

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

    • Well you officially fried my brain. Many of these topics are well beyond my very rudimentary amateur knowledge.. this has my head spinning even more than usual. When someone figures it out, just let me know what I need to do with the app! 😂
    • Confusingly, there are two different types of Cell IDs, the NR Cell ID (NCI) and the Local Cell ID, which I will call the LCID from here on out. From my understanding, @Trip is trying to get the LCID from the NCI but the same gNB is showing up for multiple sites in the app. Some background for those that don’t know about NCIs (NR Cell ID) and how they relate to gNBs and LCIDs. Just like the E/GCI which is comprised of the eNB + LCID with the eNB denoting the site, the NCI is comprised of the gNB + LCID with the gNB denoting the site. A major difference is that the eNB is a fixed number of bits in the E/GCI but the gNB can vary between 22-32 bits (out of 36) in the NCI and there is nothing transmitted which tells you what the length is. The reason for the mentioning LTE sites is that Verizon’s gNB numbering scheme in most of the USA is based upon the sites eNB (using the rules I mentioned) and a 22-bit gNB. Additionally, their LCIDs start at 25 and increment by compinations of 16 and 1. Basically, it is common to see LCID sets of 25/26/27, 41/42/43, and 57/58/59. Looking at Trip’s data and some other data from the area, they are not following the format used in the rest of the USA.  From what I can tell, they are using a 29-bit or 30-bit gNB (that gives LCIDs that follow Verizon’s standard patterning). 29-bit shares the same gNB across the two locations, while 30-bit splits the two sets: 18504107674 - gNB 144563341 + CLID 26 (29-bit) or 289126682 + CLID 26 (30-bit) 18504107690 - gNB 144563341 + CLID 42 (29-bit) or 289126682 + CLID 42 (30-bit)  18504107691 - gNB 144563341 + CLID 43 (29-bit) or 289126682 + CLID 43 (30-bit)  18504107706 - gNB 144563341 + CLID 58 (29-bit) or 289126682 + CLID 58 (30-bit)  18504107707 - gNB 144563341 + CLID 59 (29-bit) or 289126682 + CLID 59 (30-bit) 18504107738 - gNB 144563341 + CLID 90 (29-bit) or 289126683 + CLID 26 (30-bit)  18504107739 - gNB 144563341 + CLID 91 (29-bit) or 289126683 + CLID 27 (30-bit)  If true, this is a problem for SignalCheck and other mapping apps because this means they are using at least two different gNB lengths depending on the location in the USA.
    • Yeah I can confirm that the status bar is updating correctly and as often as the main app!  Great to have that back after so long. Waiting on the app to pick up the 5G data.  I'm on AT&T and I find that it only reports the 5G signal data a fraction of the time.  Once I can get it to pop back up I'll send a report with the LTE RSRP showing up in the status bar instead of the NR RSRP. I am not sure if it is new behavior with the Beta because I had it set to just show the Band since I couldn't display the band and signal at the same time. Edit:  Sent a diagnostic and here's a screenshot:
    • Yes, for various reasons the beta mapping project was limited to S4GRU sponsors at launch. It's still a work in progress but I have added a few users as it has evolved. I am inclined to leave it as-is for now -- it's not completely off-limits to discuss here (especially if there's an outage), but with so many posts I just try to keep discussions organized. RAvirani handles the map server and he monitors the other thread closer.   I might be confused, but are we talking apples and oranges here? My interpretation was Trip is talking about NR cells on different sites sharing cell IDs as far as the app is concerned, while the other comments are about LTE to NR cell ID calculations?
    • I hope this is true!! The Android development team did claim this bug was fixed several months ago, and it is typical for it to take several releases before changes are included. I was on the Android beta until I got my Pixel 9, now I am back on the public releases. With each monthly update, I have optimistically checked this icon and been disappointed. This would be fantastic to get back!   Could you send some diagnostic reports when you see this please? It is new behavior with QPR Beta 3?
  • Recently Browsing

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