https://tmfassociates.com/blog/2011/06/27/brattle-prattle/ Satellites, spectrum and other stuff Tue, 03 Feb 2026 21:36:32 +0000 hourly 1 http://wordpress.org/?v=3.3.1 https://tmfassociates.com/blog/2011/06/27/brattle-prattle/comment-page-1/#comment-582 krbarker Tue, 28 Jun 2011 00:33:31 +0000 http://tmfassociates.com/blog/?p=2130#comment-582 The latest CMRS Competitive Report from the FCC (http://wireless.fcc.gov/index.htm?job=cmrs_reports) seems to confirm your numbers. They indicate LS will have 260 POPs by 2015, and they also used the AWS-1 auction numbers. By my math (with 40 MHz) of spectrum that's around $5.6B worth of spectrum. However, as we have both discussed, this is highly subject to interference. What I don't understand is how can LS keep dropping their power and amount of spectrum, and not change their valuation. In fact, I'm not sure I understand the whole base station power issue. Dropping power of a base station simply means I need more to cover the same area at the same user QoS. More base stations means more cumulative power in the spectrum creating the same issue. We're still updating our interference analysis (www.questinygroup.com/qgi-blog), and maybe that will resolve the issue in my mind. The latest CMRS Competitive Report from the FCC (http://wireless.fcc.gov/index.htm?job=cmrs_reports) seems to confirm your numbers. They indicate LS will have 260 POPs by 2015, and they also used the AWS-1 auction numbers. By my math (with 40 MHz) of spectrum that’s around $5.6B worth of spectrum. However, as we have both discussed, this is highly subject to interference. What I don’t understand is how can LS keep dropping their power and amount of spectrum, and not change their valuation. In fact, I’m not sure I understand the whole base station power issue. Dropping power of a base station simply means I need more to cover the same area at the same user QoS. More base stations means more cumulative power in the spectrum creating the same issue. We’re still updating our interference analysis (www.questinygroup.com/qgi-blog), and maybe that will resolve the issue in my mind.

]]>