S4GRU

Adjacent spectrum uses are taken into account. All the time. No new licenses or changes are made that negatively harm the adjacent license holder. In the instances that they do, it was because the FCC decided the new purpose was so much more important and beneficial to citizens. The difference between FDD and TDD are not likely to ever meet this level of scrutiny. If you paid $4BN for spectrum, that was the market rate with these current FCC restrictions. If you could use it any way you wanted without regard to any other license holder, then the spectrum would be worth far more. There are advantages and disadvantages to both. TDD, if used solely for data, works pretty well. Flexibility in the time ratio between uplink and downlink can be advantageous. However, most other aspects either are better for FDD or neutral. Each spectrum block is currently licensed to be a symmetrical block (FDD) or single block (which would require TDD to be used two-way). A symmetrical dual linked block cannot be used for TDD without authorization from the FCC. It would also require testing and possibly larger guard bands to protect adjacent license holders. You cannot place uplink and downlink side by side in most instances. It will cause interference problems. You would have to spend a lot of money testing and convincing the FCC that you are harming no other license holders. The other license holders would still likely file complaints. The FCC would need to justify that allowing the provider to do this is the greatest common good for the taxpayers. It is a high burden. Lightsquared could tell you all about this. Robert

There really isn't anything between two TDD sites handing to each other that would cause a problem with VoLTE. But a change of bands creates a hard handoff which could be problematic for VoLTE. However, Band 41 doesn't need to run VoLTE at all. All Band 41 LTE will be redundantly overlaid with both Band 25 & 26. Therefore, if VoLTE was only used on one band, preferably Band 26, then you wouldn't have problems. And even Band 25 and Band 26 used together probably could be done pretty seamlessly too. Robert

Also, these are not stupid questions. These are the kind of questions we like. What we dislike is when people don't ask these questions and then talk to us like we are stupid when they're willing to fight with us about things they do not know. This is a great question. Robert

As far as I know, it is technically possible. However, the problem isn't so much technical, as it is licensing. All FDD spectrum has a downlink and an uplink block that are linked together. So a 10MHz section of AWS spectrum has a downlink block in 2100MHz and an equal sized uplink block in 1700MHz. Since there is an equal sized block of downlink and uplink for all current FCC sanctioned FDD wireless spectrum, there is no need for a decreased sized uplink block for any FDD spectrum. That being said, there are some downlink only blocks that are out there. These aren't designed for 2-way mobile broadband communication. AT&T owns some. They are currently not in use. I can see how someone may in the future try to link some of these downlink only spectrum pieces to an existing underburdened uplink FDD section somewhere. But I believe this would require a rule change and a new device ecosystem to allow that. The reason why you get a slower download than upload is one of two reasons. Either the airlink from the site to your device is overloaded, or the backhaul connection from the site to the MSC is overloaded. Either of these can cause this to occur. Also, to clarify regarding TDD-LTE. It does not split a 20MHz piece of spectrum into smaller uplink and downlink sections in MHz. Rather it uses time to split them. The downlink and uplink occur on the same frequency, just changing back and forth extremely quickly. A piece of time is allocated to uplink, and then a 3x longer piece of time is used for downlink, then switched back and forth. That's what TDD is. Time Division Duplexing. You may understand this, but it was not clear to me with what you typed. Robert

Hell No

Well played. That's my move. Robert

I hardly consider California plus Clark County, Nevada the West Coast. We didn't have Lucky in Northern Nevada. Closest they ever got was Truckee, CA. Robert via Samsung Note 8.0 using Tapatalk Pro

Happy New Years to you all! May 2014 be a year full of Triband LTE! Robert via Samsung Note 8.0 using Tapatalk Pro

Eric is on the right track. But adding an LTE carrier card and configuring routers is an easy thing to do. It would take 1-2 hours per site, if things went without a hitch. Robert via Samsung Note 8.0 using Tapatalk Pro

Time is up. The sale is over. If you missed it by a day or two, PM me. I may be able to help you still. Robert

Site acceptance reports from Friday (12/27), Saturday (12/28), Sunday (12/29), Monday (12/30) and Tuesday (12/31): Alabama - 2 updates (LTE) Albuquerque - 3 updates (LTE) Atlanta/Athens - 2 updates (1 LTE) Austin - 10 updates (3 LTE) Baltimore - 16 updates (1 LTE, 11 CDMA 800) Buffalo - 11 updates (3G) Boston - 38 updates (2 LTE, 34 CDMA 800) Central Jersey - 3 updates (3G) Charlotte - 2 updates (1 LTE) Chicago - 3 updates (LTE) Cincinnati - 54 updates (4 LTE, 4 CDMA 800) Cleveland - 7 updates (LTE) Colorado - 45 updates (2 LTE, 18 CDMA 800) Columbus - 26 updates (3G, 19 CDMA 800) Delaware - 1 update (3G) DFW - 1 update (3G) East Kentucky - 2 updates (3G) East Texas - 1 update (LTE) Ft. Wayne/South Bend - 1 update (LTE) GA/SC Coast - 6 updates (2 LTE) Georgia - 1 update (LTE) Gulf Coast - 2 updates (3G) Houston - 14 updates (13 CDMA 800) Jacksonville - 3 updates (LTE) Kansas - 29 updates (1 LTE, 27 CDMA 800) LA Metro - 31 updates (7 LTE, 21 CDMA 800) Las Vegas - 7 updates (5 LTE) Long Island - 9 updates (3 LTE) Memphis - 3 updates (LTE) Minnesota - 40 updates (6 CDMA 800) Mississippi - 3 updates (2 LTE) Missouri - 10 updates (6 LTE) Myrtle Beach - 4 updates (2 LTE) Nashville - 12 updates (11 LTE) New York City - 10 updates (4 LTE) Northern Connecticut - 5 updates (3G) Northern Jersey - 10 updates (4 LTE) North LA - 2 updates (1 LTE) Oklahoma - 2 updates (3G) Orange County - 3 updates (2 LTE) Oregon/SW Washington - 17 updates (CDMA 800) Orlando - 10 updates (5 LTE) Philadelphia Metro - 8 updates (3 LTE) Phoenix - 11 updates (9 LTE) Pittsburgh - 3 updates (3G) Raleigh Durham - 9 updates (8 LTE) Riverside/San Bernardino - 10 updates (6 LTE) Rochester - 3 updates (3G) San Antonio - 1 update (3G) San Diego - 10 updates (1 LTE) SF Bay - 31 updates (5 LTE, 26 CDMA 800) South Bay - 18 updates (2 LTE, 16 CDMA 800) South Carolina - 4 updates (3G) Southern Connecticut - 25 updates (1 LTE, 15 CDMA 800) Southern Jersey - 8 updates (1 LTE) South Texas - 4 updates (LTE) Southwest Florida - 3 updates (3G) Tampa - 1 update (LTE) The Panhandle - 4 updates (2 LTE) Toledo - 7 updates (3G) Tucson/Yuma - 2 updates (1 LTE) Upper Central Valley - 1 update (LTE) Upstate NY East - 2 updates (LTE) Utah - 9 updates (CDMA 800) VT/NH/ME - 4 updates (3G) Washington DC - 20 updates (7 LTE, 10 CDMA 800) West Iowa/Nebraska - 15 updates (CDMA 800) West Kentucky - 9 updates (3 LTE) West Michigan - 3 updates (CDMA 800) West Texas - 5 updates (4 LTE) West Washington - 8 updates (7 LTE) Winston/Salem - 24 updates (LTE) Maps are updated. Robert Links: Comments regarding this thread, NV Sites Complete Map

Just a few more hours left!!! Upgrade to Premier Sponsor today! Robert

Yes. Robert

OK. Looks like I have been looking incorrectly all along. Doesn't appear any have remote RRU's around here. I checked out about half a dozen sites around here today. Robert

Could be. But I thought the AWS deployments had RRU's up at the panels. None of them around here have any visible RRU's Robert via Nexus 5 using Tapatalk

I've said it before, and I'll say it again...I don't think Sprint will ever bring back unlimited for hotspots or home ISP. It would fill up it's airways in no time. Sprint still has finite spectrum resources. I think Sprint could offer unlimited home solutions in rural areas. But I don't think they want to make a distinction with unlimited rural service and tiered service with urban/suburban. That's why this team up with DISH kind of makes that work. The joint venture could just only offer service in areas that are ISP underserved and not spectrum starved. Allowing for a robust LTE experience without throttling or data caps. That way Sprint does not starve it's long term growth high speed/capacity spectrum, and it uses the joint venture as a differentiator to allow unlimited hotspot/home ISP in areas it can do so without impact to their network. Quite brilliant, actually. But I hope they brought adequate "protection" before getting into bed with Charlie Ergen. I hear he has VD...corporate VD. Can be fatal without the proper remedies. Robert via Samsung Note 8.0 using Tapatalk Pro

What a decidedly California-centric post. As if anyone outside of California remembers Lucky stores. Robert via Samsung Note 8.0 using Tapatalk Pro

Island Paradise Robert via Samsung Note 8.0 using Tapatalk Pro

Did you try a few servers? It could have actually just been a server problem causing slower throughput. Robert via Samsung Note 8.0 using Tapatalk Pro

We have extended the promotion through tonight at Midnight, due to a few requests today. This is your last chance to get a $25 discount on Premier Sponsor status. Remember, Premier Sponsorships do not expire, and you get access to much more content!! If you are unsure, ask a Premier Sponsor yourself if it is worth it! Robert via Samsung Note 8.0 using Tapatalk Pro

With that kind of ping, things that only use small amounts of data will feel very fast. That could just be a provisioning problem at the switch. I don't recall ever seeing a ping that low with a speed that low before. Robert via Samsung Note 8.0 using Tapatalk Pro

Novatel MiFi 5510L Robert via Samsung Note 8.0 using Tapatalk Pro

Yes. My hotspot. But there are no engineering screens in the web browser interface to confirm what I'm connected to. The diagnostic screens provide lots of CDMA info, but only provide RSRP and MCC ID for LTE. Unless VZW uses a different ID for Band 4. Novatel Mifi 5510L. Robert via Samsung Note 8.0 using Tapatalk Pro

Well, it turns out Verizon has deployed AWS all over Rapid City. It seems to be on every site. I drove around all over the city and never lost the signal. I discussed this with AJ last night, and it turns out the channel is parked on Tmo spectrum. Strange. I first discovered it on my ATT SIM when in LTE only mode. Only ATT showed as a provider when I searched for mobile networks. But after searching the carrier ID, it came as Verizon. Slap in a Verizon SIM and it appeared and the signal filled up on the status bar. I used my VZW SIM from my hotspot in my Nexus 5. No matter what I did, it would not authenticate. It would say it successfully registered with the network. And the signal would vary as I drove around. And the serving cells would change. But the info would not ever populate in SignalCheck Pro. I think they only allow devices to authenticate to their LTE network where the MEID is in their database. And we know that Verizon does not have the N5 in their system. AT&T does the same thing. My N5 would not work on ATT LTE initially, I had to call them and they added the MEID to the system to allow it. At least ATT does that much. Robert via Nexus 5 using Tapatalk

I went back to the site in better light today during my lunch hour. They actually changed one of the other sectors to narrow beam too. So the two lower burdened sectors are unchanged, but the high burdened sector is now split into two narrow beam antennas. Works like a charm! Robert via Nexus 5 using Tapatalk