Jump to content

LTE Fragmentation(any "hopefully" a solution)


Recommended Posts

There are currently a total of 43 different LTE band classes in the world. Very likely, more bands classes will come into fruition in the future. However, many of these band classes are somewhat redundant. Here's one such example.


Band Class 2 covers the U.S. PCS Spectrum bands(at least most of them). Band 2 covers frequencies 1930-1990MHz on downlink and 1850-1910MHz on uplink. This is the FCC’s PCS A-F blocks.

Around the time Sprint announced the EVO 4G(April 2010), Sprint requested a band extension from the 3GPP for Band 2. They asked for this so that it can also cover the G block(has you might know, is what Sprint’s LTE network will operate on at launch). The extension was eventually approved, but it ended up creating a new Band #(in this case, Band 25). This is not a true extension of Band 2, but pretty much covered what Sprint requested.

Band Class 25 covers the frequencies 1930-1995MHz for downlink and 1850-1915MHz for uplink.



As you can probably forumate from above, Band 25= Band 2 + G Block.


I can understand that creating a new band class does help prevent confusion on if a device supports a certain frequency, or that manufacturers can just create new devices using the newer bands instead of the older ones that covers less possible networks.

The thing is that LTE is young, new, and still adapting to the world's different frequency blocks across the globe. Band classes will continue to grow for at least the next few years. Some carriers may opt to buy new spectrum and deploy LTE there. Other(like Sprint & T-Mobile USA) would refarm and use spectrum they already own.

This makes building a multi-carrier device a bit of a pain at this time since most devices are incompatible with other networks, even one within a close MHz range. One example is the 700MHz spectrum in the U.S.(which will be discussed in another article)


One solution I see for this is the true extension of band classes to include new bands. For this, I would opt for all band classes to be given “draft” status, along with a revision label be given to every time a new request for an extension of a band class is approved instead of a new band class number. For example, Band 2 & 25.

With the addition of a spectrum block to band 2, instead of creating Band 25(or 26 or etc.), use a revision marker for the same band class.

So if in 2010, PCS bands(without G block) for LTE was called Band 2, PCS w/G Block would become the new Band 2. A revision number would be associated with each small change to the band along with “draft” status to the class number, but all future devices w/ this band number will include the updated frequency range. After a few years, the band class would be finalized and no additional changes can or will be made. This will prevent redundant band classes, intentional use of older bands(anticompetitive practices), and excessive phone revisions of the same phone(no more “one size fits one” and more “one size fits many”).


I’ll end this write-up with the growing possibility of LTE roaming in the near future. South Korea carrier’s SK Telecom & LG Telecom(LG U+) currently operate their LTE networks at 800MHz(Band 5). Sprint has just received approval for Band Class 26(an extended Band 5 to support ESMR).



If both the Korean carriers decided to sell new devices with Band 26 support along with Sprint, could this be the beginning of internationality compatible LTE devices?



Sources: Niviuk(http://niviuk.free.fr/lte_band.php), 3GPP(Band 25[http://www.3gpp.org/.../RP-110804.zip ]

Band 26[http://www.3gpp.org/.../RP-120305.zip] ), Engadget, LG U+ (Korean[http://www.uplus.co.kr/])

  • Like 5
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.

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

    • https://www.fiercewireless.com/wireless/t-mobile-gets-little-closer-accessing-its-25-ghz-spectrum-auction-108 Senator Kennedy's bill to grant the FCC temporary auction authority to finish processing the Auction 108 licenses it has sold to their proper licensees. This would greatly benefit T-Mobile.  This delayed process took what would have been a strategic advantage for T-Mobile (1 one year plus head start)  and turned into catch-up, since AT&T and Verizon haven been busy installing their c-band n77 in rural areas.
    • I configured -44/-3 scenarios on an Edge 2022 to be an invalid connection, so yes, it would show no service.. I didn't realize it was a frequent issue though. How certain are you about the other values? Perhaps they are just unchanged from the previous array of signal information that was reported? If that is the case, I can try to have the app discard -44/-3 datapoints and leave the screen unchanged. I worry about the slippery slope of having it display as -140, because that leads users to believe there is a -140 signal present, when in reality we don't know what the actual reading is.   Haha me and you both wish this!!!
    • Following up, I've gone into the office in person today and took my Edge with me. It looks like it now shows "No service" instead of the -44/-3 value.  I saw a lot of "no service" because it apparently does it a lot.  I'll check again on the train ride home later. Assuming I'm correct, is it possible to have some kind of middle ground on this?  I think it was showing other legitimate values, like the TA, even when it was showing -44/-3.  I'd prefer it show the data it has but at -140 dBm in those cases.  I recognize this could be a pain to implement, and if it is, then no worries, mostly curious. EDIT:  But now I'm sitting here thinking "what if the PCI is bad and I don't know it?"  But that can just as easily be the case on other phones that aren't caught.  I do regularly see bad PCI entries on my other devices, so maybe this isn't the best option.  Bleh, I wish this stuff just worked properly! - Trip
    • Forgot to follow up on this. The service was once again abysmal .
  • Recently Browsing

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