AT&T and Verizon hammer Dish over spectrum interoperability proposal
Some of those rules will involve interoperability requirements with other frequency bands that have been sliced up by the industry and regulators. Right now, there is wide support from the mobile carriers to ensure downlink interoperability between AWS-1 and AWS-3 blocks of spectrum.
Dish Network, as we all know, holds licenses to large blocks of AWS-4 spectrum, for which it needs to build out over a pre-determined period of time or forfeit the licenses. Dish filed with the FCC on March 14th that the interoperability requirements should also apply to AWS-4 frequency bands.
Dish further noted that its interest in the AWS-3 auction would be “greatly enhanced” if interoperability of AWS-4 was assured to be part of that big block of frequencies from AWS-1 and AWS-3. That would presumably give Dish a better chance of success should it ever get around to building out what amounts to a nationwide footprint of spectrum it holds already.
Verizon fired a blast at Dish in a separate filing on March 19th stating that there was not enough time to evaluate Dish’s proposal given the amount of effort that 3GPP (3rd Generation Partnership Project) standards body has already put into ensuring interoperability between AWS-1 and AWS-3 blocks. Verizon also stated that Dish’s proposal was ill timed just a couple weeks before the FCC was going to publish its rules.
Dish then responded with a follow-up on March 20th saying that no such work was being done by 3GPP which on the face of it appears to be a bit of an arbitrary statement. Dish reasoned that whatever work has been done to ensure proper interoperability between AWS-1 and AWS-3 could become a natural extension to the AWS-4 spectrum it owns.
That is when AT&T stepped in, also on the 20th, and pretty much slammed Dish stating that 3GPP was the correct area to bring these proposals adding, “an 11th hour ex parte on an item headed for a vote with no notice or comment is decidedly NOT the proper approach for managing these issues.”
1. ajac09 (Posts: 1405; Member since: 30 Sep 2009)
aka Verizon and AT&T are crying. Its to bad dish didnt buy sprint they would have turned them into a super budget carrier and fired half their worthless staff and gotten rid of Dan Hesse.
4. Daftama (Posts: 587; Member since: 03 Nov 2012)
And you must proud of people losing there jobs instead of re-education... Sprint hasn't made a correct decision but you certainly have the dumbest comment on PA
5. ngo2dd (Posts: 896; Member since: 08 Jul 2011)
I think you do. If dish buy up Sprint then Sprint would be in mote debt because dish did not have the cash on hand, most of it was borrowed money. More people would have last there job because Sprint would not have a cash on hand to upgrade more of the network. Before you sound even more dumb learn how to do basic research, i.e Google the deal retard.
7. g2a5b0e (Posts: 3270; Member since: 08 Jun 2012)
Before you sound even more unintelligent or bother to call someone dumb, learn the differences between their/there/they're. Same goes to commenter #4.
8. Slammer (Posts: 1369; Member since: 03 Jun 2010)
I'm not sure correcting someone's grammatical level really enhances your argument. It doesn't change his point.
11. g2a5b0e (Posts: 3270; Member since: 08 Jun 2012)
No, it doesn't change his point, but that wasn't my point. I don't care about his argument either way. It's very ironic to call someone dumb while sounding dumb yourself. I wouldn't have bothered to correct his grammar if he hadn't been condescending to the person to whom he was responding.
13. Slammer (Posts: 1369; Member since: 03 Jun 2010)
And that's my point. This is an arena for debating. You don't like what he says in offering an opinion, so rather than offering an informational counterpoint coupled with a repremand, you just go for the grammatical error card.
You should care. We have enough adolescent, immature posters on these sites as it is. Dropping to the level of mere spell checking, doesn't interject a knowledgeable rebuttal nor does it open up the actual intellectual level that you may possess.
In short, I learned nothing on why you felt his opinion is off base in relation to the article. Only that you followed suit with needless trolling.
14. g2a5b0e (Posts: 3270; Member since: 08 Jun 2012)
Thanks for policing my post, but perhaps you still don't understand my point. I don't care so much about the grammar. It was his rudeness that prompted my post. There was no need for him to call someone dumb or a retard, especially when his own post came across that way. If you still don't understand what I'm saying, let's just put this conversation to rest.
15. ngo2dd (Posts: 896; Member since: 08 Jul 2011)
I did call him a retard because he/she does not understand what was on the tablet for the Sprint dish deal. And when you try to correct people grammar. You fail to understand that one this is an international website, one country grammar is not correct in another's person country. Two a lot of us are on mobile devices and typing on mobile devices will give you error. I know the different between their/there/they're but did not proof read it on a website because I could care less about grammar on a comment section.
17. Slammer (Posts: 1369; Member since: 03 Jun 2010)
ngo2dd, Please ascend that retard really is pretty abrasive when many individuals on this site may have relatives or friends that may be mentally challenged. My nephew is one of them. It really isn't very appropriate.
16. Slammer (Posts: 1369; Member since: 03 Jun 2010)
I don't support name calling and fully understand your point. But, if you didn't care so much about his grammar, why did you go that route? We have so many mixed individuals browsing these sites from many different countries that may not be fully educated on english spelling. Everyone can mostly understand criticism relating to misinformation on subjects and/or politcally incorrect words or sentences. They will either agree or disagree. You underscoring such rudeness with a reprimand would've been understandable. However, not everyone may be totally literate or diverse in foreign language or spelling. To me, it is pretty insulting to correct someone on their spelling when dealing with possible foreigners.
18. Daftama (Posts: 587; Member since: 03 Nov 2012)
Sorry English is not my first language and I can't tell difference between them I never called him or her dumb simply said you have the dumbest comment... Just pure hate towards sprint... It's OK to hate in your world but I would hate to see people lose their jobs.. Again read before commenting I would never call someone dumb on mistake they did the action or words were stupid or dumb
19. g2a5b0e (Posts: 3270; Member since: 08 Jun 2012)
I read your comment. The second part of my comment wasn't meant for you, but I suppose if English isn't your first language, then I can't hold you much accountable for the first either.
10. ngo2dd (Posts: 896; Member since: 08 Jul 2011)
Beside making a point, the best you have is to correct my grammar? My point still stand.
9. Slammer (Posts: 1369; Member since: 03 Jun 2010)
What's wrong with Hesse? You must certainly realize that Sprint would be in far worse shape if not for his leadership. He had a legacy of crap a mile high that he inherited from the previous CEO. He has not shot from the hip. When he took over, he admitted that the road to turn things around would not be quick nor would it be easy.
I think he has done a great job with what he has to work with. If you feel differently, please correspond with his direct team:
Dan@sprint.com. Let me know how what they say.
6. mike2959 (Posts: 368; Member since: 08 Oct 2011)
Once again the big 4 doesn't want anyone playing in their sandbox.
12. Augustine (Posts: 877; Member since: 28 Sep 2013)
AWS-1 is 1,710–1,755MHz up and 2,110–2,155MHz down. AWS-3 is 1,755–1,780MHz up and 2,155–2,180MHz down. AWS-4 is 2,000–2,020MHz up and 2,180–2,200MHz down. Only AWS-4 up frequencies are adjacent to AWS-3's, whose both up and down frequencies are adjacent to AWS-1's.
Note though that the channel width for both AWS-1 and 3 is 25MHz, whereas for AWS-4 it's 20MHz. This means that indeed there's the potential of interoperability issues of AWS-3 and 4, to Verizon's point. However, it's in the downlink, at the base-station, where things can be under better control than at the user's terminal equipment, AKA cell phone, to Dish's point. Yet, the timing and arbiter are not the best, to AT&T's point.