WiWavelength
-
Posts
18,133 -
Joined
-
Last visited
-
Days Won
429
Content Type
Profiles
Blogs
Articles
Media Demo
Gallery
Downloads
Events
Forums
Everything posted by WiWavelength
-
Some of it should be sent to the Prehistoric iDENite Museum. AJ
-
It is even easier and faster if you do it at gunpoint. AJ
-
No, it is not quite that straightforward. The decision to go single radio path e/CSFB with the transition to tri band is almost certainly an agreement between Sprint and the OEMs. AJ
-
It is a hardware design. No ROM, baseband, setting, etc., is going to change that. AJ
-
Again, you are off base. This has nothing to do with the network, everything to do with the handsets. So, stop with the "advanced network" nonsense. Very few operators in the world are as far along as Sprint is in a comprehensive three band LTE deployment. AJ
-
Like I stated, AT&T and T-Mobile use e/CSFB. They fall back to W-CDMA, which supports simultaneous circuit switched voice and packet data. Though if in T-Mobile GSM only coverage, that no longer applies. If you must have simultaneous voice and data, the Sprint network supports it. Just stick with your Galaxy S3 or get another single band handset until VoLTE becomes available in the next few years. Otherwise, find another provider. AJ
-
Quit the hyperbole. AT&T and T-Mobile handsets do not do SVLTE either. They use e/CSFB, too. And the long term plan for all is VoLTE. AJ
-
Where have you read that? VZW currently does dual band LTE handsets with SVLTE. That puts VZW on an island for handset design. Sprint handsets, on the other hand, can now use the same 3GPP designs as AT&T and T-Mobile with few, if any modifications. AJ
-
Single radio path e/CSFB devices are simpler and better performers. This is not a "huge mistake." AJ
-
All current and reportedly future tri band LTE handsets will be single radio path e/CSFB devices. They will not support SVLTE. AJ
-
That is nothing new. Because it helps reduce the variable bit rate, ambient noise cancelation has been built in since at least the original EVRC, which has been around for 15 years. AJ
-
I would like to see the wording of that slide because it is patently not true that T-Mobile has 40 MHz of AWS, let alone contiguous AWS in all top 25 markets. In fact, I have a VZW-T-Mobile top 25 market AWS spectrum spreadsheet that I put together about 18 months ago following the major spectrum swap. https://docs.google.com/spreadsheet/ccc?key=0ArY31Mr219-ydFVpWGJJNlFtQlk4M3h5R1c4eklJamc&usp=drive_web#gid=0 Now, some of that data is no longer current due to subsequent transactions, such as the MetroPCS merger. But the thrust of it is still accurate. T-Mobile has anywhere from 10 MHz to 50 MHz of accumulated AWS in the top 25 markets. Additionally, keep in mind that T-Mobile will have to continue to run at least one W-CDMA carrier in AWS for the next few years, so that takes up at least 10 MHz of spectrum. In other words, not all of that spectrum will be available for LTE. And 20 MHz FDD requires contiguous spectrum, so that further limits the pool of possible markets. AJ
-
Samsung Galaxy S5 Announced - Launch Date 4/11/14
WiWavelength replied to illest_ios's topic in Samsung
I heard there will not be a Galaxy S5 this year. Instead, it will be the Galaxy S4S. AJ -
Pretty much. That these little handheld devices can effectively decode digital messages received at power levels around one billionth of a watt is almost magic. AJ
-
Hey, I am still trying fully to wrap my brain around e/CSFB because it is a 3GPP technique, not 3GPP2, which is more my specialty. But on that note, do know that when a CDMA1X mobile receives a call, the paging channel message for the incoming call does not go out to a specific site closest to the mobile. No, the MSC broadcasts the page across all CDMA1X sites within the zone where the mobile is registered. I will have to do more digging to confirm, but I expect e/CSFB to do the same. Once the LTE mobile gets the command to fall back to CDMA1X for an incoming call, it picks up the page coming from all CDMA1X sites within that zone. Then, the mobile responds to the page over CDMA1X, and a traffic channel is set up on the nearest (well, technically, best Ec/Io) site. AJ
-
With those speeds, you did just tire it out. AJ
-
No, they should be affected the same as Sprint LTE sites in that regard. AJ
-
Yup. But that command comes from the MSC via the DDC. AJ
-
As Robert has reported, Clearwire base stations are backhauled to the Sprint DDCs, which then communicate with the MSCs. AJ
-
The band 41 site does not need to know anything about routing voice calls. That is the job of e/CSFB through the MSC (i.e. "switch") and DDC (i.e. "4G core"). AJ
-
AJ
-
Non-G-Block PCS LTE Carriers
WiWavelength replied to dmchssc's topic in Network, Network Vision/LTE Deployment
For Sprint branded postpaid, the LTE handset penetration is already significant. I seem to recall a stat of 40 percent, and that was from a number of months ago. Remember, we are almost two years into LTE handset availability. I would bet that penetration is over 50 percent by now. So, that would alleviate considerable pressure on EV-DO in well deployed LTE markets. Additionally, voice traffic is not likely at the levels it was years ago when Sprint determined how many CDMA1X carriers to deploy on a site by site basis. Throw in the new CDMA1X 800 carrier, and Sprint probably has excess voice capacity. AJ -
That depends on the downlink:uplink ratio chosen. AJ
-
...especially the HPV LTE variant. It is worse than the eHERPIES. AJ
-
I think NII Holdings aka Nextel International might be the only hope. AJ
