Jump to content

PCS H Block Spectrum discussion (was "Draft Rules for H Block Auction Set by FCC"


marioc21

Recommended Posts

Once sprint deploys the H block does that mean their existing 5x5 on 1900 goes to 10x10 on 1900 and will that double the data speeds?

With the current gear, that is not possible. The only way for Sprint to go to 10 MHz FDD with G+H is to upgrade the radio hardware (or get brand new radio hardware) to support the "multiple frequency band indicator" (otherwise known as MFBI) feature that allows Sprint to declare 5 MHz FDD for Band 25 and 10 MHz FDD for a newly defined extended PCS A-H band.

 

Existing devices with Band 25 will only see 5 MHz FDD until the end of their days. Devices with the new band will support 10 MHz FDD with G+H.

Link to comment
Share on other sites

With the current gear, that is not possible. The only way for Sprint to go to 10 MHz FDD with G+H is to upgrade the radio hardware (or get brand new radio hardware) to support the "multiple frequency band indicator" (otherwise known as MFBI) feature that allows Sprint to declare 5 MHz FDD for Band 25 and 10 MHz FDD for a newly defined extended PCS A-H band.

 

Existing devices with Band 25 will only see 5 MHz FDD until the end of their days. Devices with the new band will support 10 MHz FDD with G+H.

What is the 3GPP going to do after band 31 and 32? They're be out of FDD bands unless they start again at 50 or something.

Link to comment
Share on other sites

What is the 3GPP going to do after band 31 and 32? They're be out of FDD bands unless they start again at 50 or something.

There are a few reserved band numbers in place already, such as 15 and 16. However, devices don't strictly use band numbers. They rely on {U,E}ARFCNs, which band numbers are merely a construct of {U,E}ARFCN groups for frequencies. Renumbering is certainly possible, and increasingly likely, too.

Link to comment
Share on other sites

There are a few reserved band numbers in place already, such as 15 and 16. However, devices don't strictly use band numbers. They rely on {U,E}ARFCNs, which band numbers are merely a construct of {U,E}ARFCN groups for frequencies. Renumbering is certainly possible, and increasingly likely, too.

Renumbering seems like it would be a huge mess, not for the people trying to figure out what bands their phones support.

Link to comment
Share on other sites

Supplemental downlink for just about anything -- PCS, AWS, Cellular, etc.  But the PCS/AWS-2 H block holder would have the most interesting opportunity, since it could potentially lease or license, say, the lower 10 MHz of the AWS-4 2000-2020 MHz segment for an asymmetric carrier aggregated 5 MHz x 15 MHz LTE carrier.

 

AJ

 

Or take all 25 (20MHz of 2000-2020MHz +5MHz of PCS H) for an assymetric contiguous aggregated band.

Link to comment
Share on other sites

Renumbering seems like it would be a huge mess, not for the people trying to figure out what bands their phones support.

The renumbering would likely only affect LTE TDD bands, as they would probably get pushed down to the 60s.

Link to comment
Share on other sites

Dish is interested in getting its AWS-4 2000-2020 MHz uplink converted to downlink.  If so, then the conflicts with the PCS/AWS-2 H block downlink go away.  That could make the H block more valuable, as it would be part of a 25 MHz swath of contiguous spectrum that could be used for supplemental downlink.

 

AJ

 

According to Tim Farrar's post, the FCC's decision on converting that segment of AWS-4 from uplink to downlink will occur in December, before the PCS H auction. Either way, they should know by January whether or not they want to bid.

 

Yeah, that's true. I bet since Dish has relented a little bit the H block gets tacked on to PCS, which means yet another new band. Sigh.

 

I wish that the FCC would just mandate that handset makers always use the newer superset bands in place of the more limited ones (i.e. EPCS Band 25 instead of PCS Band 2, 700 MHz Band 12 instead of Band 17), so that whatever band number they assign for PCS A-H is all anybody has to worry about going forward.

 

Once sprint deploys the H block does that mean their existing 5x5 on 1900 goes to 10x10 on 1900 and will that double the data speeds?

 

It would be possible, but the high cost of doing so makes it highly unlikely. All existing LTE handsets (and apparently some upcoming ones as well...) only use Band 25, which is PCS A-G. Furthermore, many (mostly Samsung's handsets), are only approved for 5 MHz wide FDD rather than also supporting 10 MHz channels. So assuming Sprint doesn't want to pay to replace everybody's LTE handsets with newer ones a la Wi-Max, in order to combine G+H into a 10x10 they would have to: 1.) Make sure Samsung and other phone OEM's include support for 10 MHz channels in addition to switching over from Band 25 to the new EPCS A-H band, 2.) Refarm a 5x5 slice of existing PCS A-F spectrum from 1x/Ev-DO to LTE, which may not be possible to do in every market, and 3.) Replace whatever site equipment can't be retrofitted to support PCS H (I've heard the new NV RRUs may support it, but not the antennas).

 

If none of the other spectrum covered by Band 25 is refarmed, then, as Neal mentioned, Sprint would need to modify their site equipment to support MFBI.  Incidentally, that is something AT&T is currently having to do, since they were stubborn and refused to use Band 12 for their LTE from the start.

 

Since carrier aggregation's high power draw is likely to eventually be improved, it probably makes more sense to deploy another 5x5 carrier on PCS H, and when the time comes aggregate G and H together to form a pseudo-10x10 channel, which would have nearly the same performance as a true 10x10 channel. That way all current handsets will continue to happily use the 5x5 G they're using now, and new handsets will have access to G+H in addition to 800 and 2600.

 

Since all new phones that support PCS H will also presumably be tri-band, whichever path Sprint decides to take (two CA 5x5's vs a true 10x10) wouldn't do anything to help the speeds for existing LTE devices beyond the benefit of off-loading that will already be helped along by 800/2600 LTE. Average (but not peak) speeds for current devices will only improve if Sprint adds a second 5x5 carrier in PCS A-F in addition to the existing G block carrier.

Link to comment
Share on other sites

Since carrier aggregation's high power draw is likely to eventually be improved...

 

The power draw of a 10Mhz channel (assuming of cource nobody else is using the channel) will always be a problem. So will a 20MHz channel or a 40Mhz channel. That's why on the handset side, it makes no sense to have carrier aggregation.

Link to comment
Share on other sites

I wonder what would happen if Sprint decides it's not worth it to spend over $1.5B on this spectrum (sinking that money into NV instead), and Dish doesn't change it's mind about not participating. Smaller carriers probably wouldn't have that much to spend either. So if no one's willing to fork over that much for the spectrum, they would have to hold another auction with a lower reserve price, right? The FCC would have to give in at a lower price some point since they're mandated by Congress to license it by February 2015.

 

The power draw of a 10Mhz channel (assuming of cource nobody else is using the channel) will always be a problem. So will a 20MHz channel or a 40Mhz channel. That's why on the handset side, it makes no sense to have carrier aggregation.

 

I take it you mean 2 aggregated 5x5's will draw more power than a single 10x10? Because all the other carriers are getting by just fine with channels wider than 5 MHz, as will Sprint soon with 20 MHz TDD.

Link to comment
Share on other sites

I wonder what would happen if Sprint decides it's not worth it to spend over $1.5B on this spectrum (sinking that money into NV instead), and Dish doesn't change it's mind about not participating. Smaller carriers probably wouldn't have that much to spend either. So if no one's willing to fork over that much for the spectrum, they would have to hold another auction with a lower reserve price, right? The FCC would have to give in at a lower price some point since they're mandated by Congress to license it by February 2015.

 

 

I take it you mean 2 aggregated 5x5's will draw more power than a single 10x10? Because all the other carriers are getting by just fine with channels wider than 5 MHz, as will Sprint soon with 20 MHz TDD.

 

Try downloading a really big file on a 10MHz empty channel and get back to me with your battery draw.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.

  • 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 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. 
    • 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.
    • Looks like a great place for for FWA. Many apartment dwellers only have one overpriced choice.
  • Recently Browsing

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