Jump to content

Questions about how to obtain 20X20Mhz.


Exzir

Recommended Posts

Hey,

 

I know you have to have consecutive block access to obtain a 20X20 LTE but could does it have to be like Block A and block D. Here is the info I have ATM.

 

Block A: 1850 - 1865 and 1930 - 1945 (30 MHz) - issued by MTAs

Block B: 1870 - 1885 and 1950 - 1965 (30 MHz) - issued by MTAs

Block C: 1895 - 1910 and 1975 - 1990 (30 MHz, 15 MHz or 10 MHz) - issued by BTAs

Block D: 1865 - 1870 and 1945 - 1950 (10 MHz) - issued by BTAs

Block E: 1885 - 1890 and 1965 - 1970 (10 MHz) - issued by BTAs

Block F: 1890 - 1895 and 1970 - 1975 (10 MHz) - issued by BTAs

Block G: 1910 - 1915 and 1990 - 1995 (10 MHz) - issued by EAs

 

Block A and Block D would be 1845-1870 and 1930- 1950 or would you need consecutive letters like D,E,F and G.

 

I know you need 40 Mhz total spectrum so you would need a 30 and a 10; or 4 10's.

Link to comment
Share on other sites

You'd need LTE-Advanced to do what you are suggesting. The best Sprint could do in its existing would be a 15x15, but i don't think any of the current phones (expect the iPhone) support more than a 5x5 or 10x10 channel.

 

Sprint will be just fine doing multiple 5x5 channels as they fully utilize their A-F spectrum to compliment the G block and SMR.

Link to comment
Share on other sites

I can certainly appreciate your interest in this question if it is academic. I think much the same way. That said, your question is of little practical significance. In PCS 1900 MHz spectrum, LTE 20 MHz FDD (i.e. 20 MHz x 20 MHz) will be exceedingly rare, possibly even nonexistent.

 

First, you have to understand the PCS band plan. For various licensing reasons, it does not follow alphabetical order. See below:

 

PCS A block (30 MHz)

PCS D block (10 MHz)

PCS B block (30 MHz)

PCS E block (10 MHz)

PCS F block (10 MHz)

PCS C block (30 MHz)

PCS G block (10 MHz)

 

To deploy LTE 20 MHz FDD would require 40 MHz contiguous spectrum -- for example, a PCS A+D, D+B, B+E, F+C, or C+G block combo. A 20 MHz disaggregation from a 30 MHz license plus two adjacent 10 MHz licenses would be another possibility, but that is so uncommon as to be almost irrelevant. Even the 30 MHz plus 10 MHz adjacent license combo is relatively rare. Sure, VZW, AT&T, and T-Mobile have some markets in which they hold 40 MHz total PCS spectrum, but only coincidentally is that 40 MHz contiguous. The PCS band was not designed nor auctioned in the 1990s for huge swaths of contiguous spectrum.

 

So, in this decade at least, LTE 20 MHz FDD is not likely to be found outside the AWS 2100+1700 MHz band. Both VZW and T-Mobile have opportunities to deploy 20 MHz x 20 MHz in AWS. A year or two earlier, though, Clearwire will be deploying LTE 20 MHz TDD in its BRS/EBS 2600 MHz spectrum. That is likely to be the first taste of LTE 20 MHz carriers.

 

AJ

  • Like 3
Link to comment
Share on other sites

Interesting post AJ.

 

Another question:

Three scenarios

5x5 + 5x5 + 5x5 + 5x5 = 4 channels, 1 RRU, 4 line cards needed?

10x10 + 10x10 = 2 channels, 1 RRU, 2 line card needed?

20x20 = 1 channel, 1 RRU, 1 line card needed?

 

Is this the right way of looking at it? Is this why there is a desire to create such wide channels? A lot cheaper (in terms of hardware needed to deploy)?

Link to comment
Share on other sites

Interesting post AJ.

 

Another question:

Three scenarios

5x5 + 5x5 + 5x5 + 5x5 = 4 channels' date=' 1 RRU, 4 line cards needed?

10x10 + 10x10 = 2 channels, 1 RRU, 2 line card needed?

20x20 = 1 channel, 1 RRU, 1 line card needed?

 

Is this the right way of looking at it? Is this why there is a desire to create such wide channels? A lot cheaper (in terms of hardware needed to deploy)?[/quote']

 

Cards are not prohibitively expensive. But there is some hardware and even a small operational savings. But the savings from having lower frequency spectrum and reduced site count is far better than reducing carriers at existing sites.

 

Robert via Moto Photon Q using Forum Runner

Link to comment
Share on other sites

Is this why there is a desire to create such wide channels? A lot cheaper (in terms of hardware needed to deploy)?

 

I doubt it. The desire for greater bandwidth LTE carriers is driven by the lack of disadvantages (pardon the double negative) of greater bandwidth LTE carriers. In other words, if a provider has the contiguous and available spectrum to do 20 MHz FDD, then it probably will do 20 MHz FDD. The one downside that comes to mind is sometimes a handset ERP/EIRP reduction on the uplink due to the greater bandwidth, but even that is somewhat dependent on the number of Resource Blocks assigned to the mobile.

 

AJ

Link to comment
Share on other sites

I doubt it. The desire for greater bandwidth LTE carriers is driven by the lack of disadvantages (pardon the double negative) of greater bandwidth LTE carriers. In other words, if a provider has the contiguous and available spectrum to do 20 MHz FDD, then it probably will do 20 MHz FDD. The one downside that comes to mind is sometimes a handset ERP/EIRP reduction on the uplink due to the greater bandwidth, but even that is somewhat dependent on the number of Resource Blocks assigned to the mobile.

 

AJ

 

I just tend to think that by creating smaller carriers, you are creating a more consistent experience for end users (ie, one user can't suck an entire 20x20 channel). If it's not a cost issue, you are only creating more variability in the user experience, which makes no sense.

 

But if you have less hardware, less energy, less capital costs, then the wide channels start to make a lot of sense.

 

Thx for explaining (thx to robert as well)

Link to comment
Share on other sites

I just tend to think that by creating smaller carriers, you are creating a more consistent experience for end users (ie, one user can't suck an entire 20x20 channel). If it's not a cost issue, you are only creating more variability in the user experience, which makes no sense.

 

But if you have less hardware, less energy, less capital costs, then the wide channels start to make a lot of sense.

 

Thx for explaining (thx to robert as well)

 

I dunno about consistency. There's a reason that DOCSIS 3 has channel bonding...more capacity, more consistency. Then again cable companies have speed tiers.

 

The pro to 20x20 LTE is you have tons of capacity in one place, without the need for Carrier Aggregation. The con is that most phones don't support that bandwidth. Heck, most Sprint phones only support 5x5.

  • Like 1
Link to comment
Share on other sites

I dunno about consistency. There's a reason that DOCSIS 3 has channel bonding...more capacity, more consistency. Then again cable companies have speed tiers.

 

The pro to 20x20 LTE is you have tons of capacity in one place, without the need for Carrier Aggregation. The con is that most phones don't support that bandwidth. Heck, most Sprint phones only support 5x5.

 

I think given that cable companies are stuck with 6MHz channels, they have no choice but to either go to a higher QAM (more dense) or bond channels.

 

Wireless operators seem to have the flexibility to deploy whatever channel width the standard they are deploying supports.

Link to comment
Share on other sites

I think given that cable companies are stuck with 6MHz channels, they have no choice but to either go to a higher QAM (more dense) or bond channels.

 

Wireless operators seem to have the flexibility to deploy whatever channel width the standard they are deploying supports.

 

The implementation is different (4x6 MHz channels or 8x6 MHz channels vs. on a 5x5, 10x10, 15x15 or 20x20 channel) but the reasoning is the same: carriers want a larger pipe for their users if it can be done relatively inexpensively using available resources. D3 channel bonding these days is seamless enough that it might as well be one big 24MHz (or however many DOCSIS channels get bonded, multiplied by 6) downstream channel. Says the person who has had D3 in some form or fashion for maybe three years now.

Link to comment
Share on other sites

I think given that cable companies are stuck with 6MHz channels, they have no choice but to either go to a higher QAM (more dense) or bond channels.

 

I have not heard of a move to greater than 256-QAM, even over wired connections. For example, 512-QAM increases modulation complexity 100 percent but increases potential throughput only 12.5 percent. I call that the point of diminishing returns.

 

AJ

Link to comment
Share on other sites

I have not heard of a move to greater than 256-QAM, even over wired connections. For example, 512-QAM increases modulation complexity 100 percent but increases potential throughput only 12.5 percent. I call that the point of diminishing returns.

 

AJ

 

 

Thought this was interesting:

 

OFDM will be matched up with low density parity-check (LDPC), a Forward Error Correction (FEC) scheme that takes up less bandwidth than the current Reed-Solomon approach. LDPC will let cable pump out more bits per hertz by utilizing higher orders of QAM modulation, including 1024 QAM and 4096 QAM in both the downstream and the upstream, Schmitt said. (256 QAM is typically used in today's cable downstream.)

To point out how much more efficient the new approach will be, Schmitt noted that it would take 780MHz of spectrum to get 5 Gbit/s using Docsis 3.0, but only 500MHz with Docsis 3.1.

 

http://www.lightreading.com/document.asp?doc_id=226144&site=lr_cable

Link to comment
Share on other sites

There are couple of cons to wider channels. If that wider channel card goes out, the whole sector goes out unless you have a standby spare you can automatically provision remotely. if one of your 4 5x5 goes out, you have 3 left. On the handset side, transmission over a wider channel, if allocated the maximum number of subcarriers sucks the battery up.

  • Like 1
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

  • Posts

    • So, in summary, here are the options I tested: T-Mobile intl roaming - LTE on SoftBank, routes back to the US (~220ms to 4.2.2.4) IIJ physical SIM - LTE on NTT, local routing Airalo - LTE on SoftBank and KDDI (seems to prefer SoftBank), routed through Singapore (SingTel) Ubigi - 5G on NTT, routed through Singapore (Transatel) US Mobile East Asia roaming - 5G on SoftBank, routed through Singapore (Club SIM) Saily - 5G on NTT, routed through Hong Kong (Truphone)...seems to be poorer routing my1010 - LTE on SoftBank and KDDI (seems to prefer KDDI), routed through Taiwan (Chunghwa Telecom) I wouldn't buy up on the T-Mobile international roaming, but it's a solid fallback. If you have the US Mobile roaming eSIM that's a great option. Otherwise Ubigi, Airalo, or my1010 are all solid options, so get whatever's cheapest. I wouldn't bother trying to find a physical SIM from IIJ...the Japanese IP is nice but there's enough WiFi that you can get a Japanese IP enough for whatever you need, and eSIM flexibility is great (IIJ as eSIM but seems a bit more involved to get it to work).
    • So, the rural part of the journey still has cell service for nearly all the way, usually on B18/19/8 (depending on whether we're talking about KDDI/NTT/SoftBank). I think I saw a bit of B28 and even n28 early on in the trip, though that faded out after a bit. Once we got to where we were going though, KDDI had enough B41 to pull 150+ Mbps, while NTT and SoftBank had B1/B3 IIRC. Cell service was likewise generally fine from Kawaguchiko Station to Tokyo on the express bus to Shinjuku Station, though there were some cases where only low-band LTE was available and capacity seemed to struggle. I also figured out what I was seeing with SoftBank on 40 MHz vs. 100 MHz n77: the 40 MHz blocks are actually inside the n78 band class, but SoftBank advertises them as n77, probably to facilitate NR CA. My phone likely preferred the 40 MHz slices as they're *much* lower-frequency, ~3.4 GHz rather than ~3.9, though of course I did see the 100 MHz slice being used rather often. By contrast, when I got NR on NTT it was either n28 10x10 or, more often, 100 MHz n78. As usual, EMEA bands on my S24 don't CA, so any data speeds I saw were the result of either one LTE carrier or one LTE carrier plus one NR carrier...except for B41 LTE. KDDI seems to have more B41 bandwidth live at this point, so my1010 or Airalo works well for this, and honestly while SoftBank and NTT 5G (in descending order of availability) have 5G that's readily available it may be diminishing returns, particularly given that I still don't know how to, as someone not from Hong Kong, get an eSIM that runs on SoftBank 5G that isn't the USM "comes for free with the unlimited premium package" roaming eSIM (NTT is easy enough thanks to Ubigi). In other news, I was able to borrow someone's Rakuten eSIM and...got LTE with it. 40 Mbps down, 20 Mbps up, 40ms latency to Tokyo while in Tokyo...which isn't any worse than the Japan-based physical SIMs I had used earlier. But not getting n77 or n257 was disappointing, though I had to test the eSIM from one spot rather than bouncing around the city to find somewhere with better reception. It's currently impossible to get a SIM as a foreigner that runs on Rakuten, so that was the best I could do. Also, I know my phone doesn't have all the LTE and 5G bands needed to take full advantage of Japanese networks. My S24 is missing: B21 (1500 MHz) - NTT B11 (1500 MHz) - KDDI, SoftBank B42 (3500 MHz) - NTT, KDDI, SoftBank n79 (4900 MHz) - NTT Of the above, B42/n79 are available on the latest iPhones, though you lose n257, and I'm guessing you're not going to find B11/B21 on a phone sold outside Japan.
    • T-Mobile acquiring SoniqWave's 2.5 GHz spectrum  Another spectrum speculator down! T-Mobile is acquiring all of their BRS/EBS licenses and their leases. Details are lacking but it looks like T-Mobile might be giving them 3.45GHz in exchange in some of the markets where they're acquiring BRS/EBS to sweeten the deal and stay below the spectrum screen. Hopefully NextWave is at the negotiating table with T-Mobile so NYC can finally get access to the full BRS/EBS band as well.  — — — — — Edit: Turns out this is a spectrum swap where T-Mobile is basically giving them DoD spectrum in a bunch of markets in exchange for all of SoniqWave's BRS/EBS. SoniqWave will likely turn around and sell the DoD spectrum to AT&T whenever the FCC removes the 40MHz cap.
    • Maybe. The taller buildings on one side of the street all have Fios access and the NYCHA buildings are surrounded by Verizon macros that have mmWave. I don’t think this site will add much coverage. It’d be better off inside the complex itself.
  • Recently Browsing

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