Jump to content

Everything 800mhz (1xA, LTE, coverage, timeline, etc)


Recommended Posts

Given the size of Sprint's 800 Mhz spectrum holdings (they can't fit MORE than a 5x5 LTE carrier there, even if they got rid of the 1xA carrier), I don't know why they'd be in any hurry to get rid of the 1xA carrier on 800Mhz.

Why would they get rid of that 1xA carrier?

Link to comment
Share on other sites

Keep in mind that if it is a SID boundary -- hence, a transition between MSCs -- then the call may still drop.

 

AJ

 

is the SID reported by CDMA field test accurate? (right now it says 4124) If so next time i'm connected to the tower they would be switching too i'll see if the SID is the same or not.

Link to comment
Share on other sites

is the SID reported by CDMA field test accurate? (right now it says 4124) If so next time i'm connected to the tower they would be switching too i'll see if the SID is the same or not.

 

It is probably not a SID boundary, but what is the location?

 

AJ

Link to comment
Share on other sites

It is probably not a SID boundary, but what is the location?

 

AJ

 

here is a post i made about it awhile back, its got a map with the tower locations and approximate location of the call dropping.

Link to comment
Share on other sites

here is a post i made about it awhile back, its got a map with the tower locations and approximate location of the call dropping.

 

No, that is not a SID boundary.  Your closest SID boundaries along I-35 and I-80 are halfway to Council Bluffs for the Omaha MTA, the Missouri state line for the Kansas City MTA, and the Minnesota state line for the Minneapolis MTA.  But it may be an old NID boundary between Sprint corporate and iPCS affiliate.

 

I am not familiar with the coverage north of Des Moines, but south of Des Moines, the old NID boundary between Sprint and iPCS along I-35 was, if I recall correctly, the Polk County line -- surprisingly close to the southern edge of the suburbs.  For technical and billing reasons, corporate and affiliate typically did not hand off to each other.  And to prevent overlap, site spacing at corporate/affiliate market boundaries was often significant.

 

Now, the only sticking point is that I am not sure the location in question is the former corporate/affiliate NID boundary north on I-35.  If so, then Ames was affiliate.  Does anyone remember if Sprint let iPCS have Ames?

 

AJ

Link to comment
Share on other sites

No, that is not a SID boundary.  Your closest SID boundaries along I-35 and I-80 are halfway to Council Bluffs for the Omaha MTA, the Missouri state line for the Kansas City MTA, and the Minnesota state line for the Minneapolis MTA.  But it may be an old NID boundary between Sprint corporate and iPCS affiliate.

 

I am not familiar with the coverage north of Des Moines, but south of Des Moines, the old NID boundary between Sprint and iPCS along I-35 was, if I recall correctly, the Polk County line -- surprisingly close to the southern edge of the suburbs.  For technical and billing reasons, corporate and affiliate typically did not hand off to each other.  And to prevent overlap, site spacing at corporate/affiliate market boundaries was often significant.

 

Now, the only sticking point is that I am not sure the location in question is the former corporate/affiliate NID boundary north on I-35.  If so, then Ames was affiliate.  Does anyone remember if Sprint let iPCS have Ames?

 

AJ

 

interesting info..... the place the call drops is almost exactly the county border between polk and story counties. so assuming this is some kind of NID boundary and that is what is causing the call drop will that change with NV getting installed?

 

i always just assumed it was tower spacing at that location and 1900 not being able to reach far enough to handoff from tower to tower.

Link to comment
Share on other sites

Why would they get rid of that 1xA carrier?

I don't think they would, that's exactly my point. Even in 10 years when all the new phones are doing VoLTE, dropping the 1xA carrier on ESMR won't give them enough additional spectrum to enlarge their 5x5 LTE carrier on ESMR. My guess is that this would be the very last CDMA carrier that Sprint will get rid of.

  • Like 1
Link to comment
Share on other sites

I don't think they would, that's exactly my point. Even in 10 years when all the new phones are doing VoLTE, dropping the 1xA carrier on ESMR won't give them enough additional spectrum to enlarge their 5x5 LTE carrier on ESMR. My guess is that this would be the very last CDMA carrier that Sprint will get rid of.

 

I agree that the ESMR 1xA carrier would be the last CDMA carrier that Sprint would get rid of.  Since Sprint has 7x7 (14 MHz) of ESMR spectrum in most areas of the country, I wonder if they could at some point refarm that last CDMA carrier to deploy a 1.4 x 1.4 MHz LTE carrier.  The spectrum needed is just slightly larger than a CDMA carrier (1.25 x 1.25 MHz)

Link to comment
Share on other sites

I agree that the ESMR 1xA carrier would be the last CDMA carrier that Sprint would get rid of.  Since Sprint has 7x7 (14 MHz) of ESMR spectrum in most areas of the country, I wonder if they could at some point refarm that last CDMA carrier to deploy a 1.4 x 1.4 MHz LTE carrier.  The spectrum needed is just slightly larger than a CDMA carrier (1.25 x 1.25 MHz)

You need to factor in guard bands on each end.

Link to comment
Share on other sites

I agree that the ESMR 1xA carrier would be the last CDMA carrier that Sprint would get rid of.  Since Sprint has 7x7 (14 MHz) of ESMR spectrum in most areas of the country, I wonder if they could at some point refarm that last CDMA carrier to deploy a 1.4 x 1.4 MHz LTE carrier.  The spectrum needed is just slightly larger than a CDMA carrier (1.25 x 1.25 MHz)

 

Maybe in this case, they'd refarm the ESMR so they had a pair of 3x3 LTE carriers, instead of 5x5 LTE and a 1xA (1.25x1.25). How big do the guard bands need to be?

Link to comment
Share on other sites

You need to factor in guard bands on each end.

 

I understand.  However I believe the guard band required for CDMA are more stringent than they are for LTE.  I don't think that an extra 150 KHz is going to be a deal breaker.  I believe CDMA needs 625 KHz guard band while LTE needs about 225 KHz guard band.  I know someone will correct me if I am wrong.

Link to comment
Share on other sites

You need to factor in guard bands on each end.

How big do the guard bands need to be?

 

No, 3GPP airlinks do not require additional guard bands.  In a Eurasian spectrum centric move, they already include internal guard bands.  A 5 MHz FDD LTE carrier, for example, occupies really only 4.5 MHz.  To illustrate, see my spectrum analyzer sweep in the RSRP article:

 

http://s4gru.com/index.php?/blog/1/entry-308-rssi-vs-rsrp-a-brief-lte-signal-strength-primer/

 

AJ

  • Like 1
Link to comment
Share on other sites

No, 3GPP airlinks do not require additional guard bands.  In a Eurasian spectrum centric move, they already include internal guard bands.  A 5 MHz FDD LTE carrier, for example, occupies really only 4.5 MHz.  To illustrate, see my spectrum analyzer sweep in the RSRP article:

 

http://s4gru.com/index.php?/blog/1/entry-308-rssi-vs-rsrp-a-brief-lte-signal-strength-primer/

 

AJ

So the question becomes, with 14Mhz of spectrum, would Sprint opt to add a 1.4x1.4 LTE carrier after they drop the 1xA carrier, or would they refarm to something like a pair of 3x3 LTE carriers on ESMR? Too bad you can't do a 7x7 carrier on LTE....

Link to comment
Share on other sites

So the question becomes, with 14Mhz of spectrum, would Sprint opt to add a 1.4x1.4 LTE carrier after they drop the 1xA carrier, or would they refarm to something like a pair of 3x3 LTE carriers on ESMR? Too bad you can't do a 7x7 carrier on LTE....

 

I guess for me, my thinking is ...why waste that 800 MHz RRU when its eventually going to be providing 1 LTE carrier (5x5) when it can easily provide 2 LTE carriers (5x5 and 1.4x1.4 or a pair of 3x3).  I think any extra capacity at 800 MHz would be welcomed. The new base stations can easily accommodate that.  

 

However I think the costs of extra LTE carrier card may end up outweighing the benefits of deploying an additional 1.4x1.4 or 3x3 LTE carrier.  I hope I am wrong and we do end up getting a pair of 3x3 LTE carriers at 800 MHz.

  • Like 1
Link to comment
Share on other sites

No, 3GPP airlinks do not require additional guard bands.  In a Eurasian spectrum centric move, they already include internal guard bands.  A 5 MHz FDD LTE carrier, for example, occupies really only 4.5 MHz.  To illustrate, see my spectrum analyzer sweep in the RSRP article:

 

http://s4gru.com/index.php?/blog/1/entry-308-rssi-vs-rsrp-a-brief-lte-signal-strength-primer/

 

AJ

 

AJ, correct me if I'm wrong, but doesn't Sprint's eSMR holdings require guardbands on each end?

Link to comment
Share on other sites

AJ, correct me if I'm wrong, but doesn't Sprint's eSMR holdings require guardbands on each end?

 

I think what AJ is saying is that a 5 MHz LTE carrier has a internal guard band already since its only has 4.5 MHz of actual signal and the remaining 0.5 MHz is the guard band.  I saw AJ's article he linked and you can see that from 1990-1995 MHz, both sides of it doesn't have signal until about 250 KHz on both sides and that is the internal guard band.  It seems to me like every LTE carrier has a internal guard band and I would think that a 10 MHz LTE carrier only has 9.5 MHz of actual signal.

 

Why would you need another guard band on both sides if the LTE carrier itself has a internal guard band?  As long as the signals on both sides don't interfere with each other it should be good.  I don't believe ESMR has any special rules about having additional guard bands just as long as it has one.  CDMA/EVDO is different and needs a 625 KHz guard band on both sides since the carrier itself does not have a guard band.

Link to comment
Share on other sites

It seems to me like every LTE carrier has a internal guard band and I would think that a 10 MHz LTE carrier only has 9.5 MHz of actual signal.

Actually, it is 9 MHz occupied bandwidth. A 10 MHz FDD LTE carrier has twice as many subcarriers as a 5 MHz FDD carrier does, so just double everything. Then, triple for 15 MHz FDD, quadruple for 20 MHz FDD.

 

CDMA/EVDO is different and needs a 625 KHz guard band on both sides since the carrier itself does not have a guard band.

CDMA2000 does not require guard bands to be 625 kHz. That is just how the math works with 1.25 MHz carrier channels in typical PCS 1900 MHz license blocks in multiples of 5 MHz.  Guard bands are either 625 kHz or zero.

 

In Cellular 850 MHz, though, 275 kHz was the typical guard band separation between CDMA1X and AMPS control channels, which were exceedingly important to be protected.

 

AJ

Link to comment
Share on other sites

When Nextel is officially shut down. When will Sprint start with the LTE800? I already know voice/3G800 here is officially live. So I am assuming every Nextel tower here has been shutdown and what not. I know the Nextel tower behind my apartment got removed last summer and Verizon added a rack below Nextels empty rack. I was hoping Sprint would sometime replace Nextel's spot :/

While I'm on 800,since it's officially live. Here are the results:

1..5 years ago:

123116718.png

Oct.2 2012:

259742027.png

Today:

486021043.png

  • Like 1
Link to comment
Share on other sites

Does sprint use a certain company for their backhaul or do they just use whoever is in the area and can meet their specs?

 

My impression was that it varied from area to area based on whoever could meet their specs.

  • Like 2
Link to comment
Share on other sites

 

 

Does sprint use a certain company for their backhaul or do they just use whoever is in the area and can meet their specs?

 

 

My impression was that it varied from area to area based on whoever could meet their specs.

Whoever also has the best price too, and can install it the soonest.

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

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

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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