GSM is the problem here. Jam the others, and the phone falls back to 2g.
2g needs to die.
GSM is the problem here. Jam the others, and the phone falls back to 2g.
2g needs to die.
https://www.business.att.com/content/other/2G-Sunset-FAQ_201...
Since LTE is the lowest common denominator technology between all carriers (and LTE is the only cellular technology with hardware that supports all cellular frequency bands in the US) the cellular market in the US is being pushed very strongly in an all-LTE direction. With the inclusion of Cat-M1 and Cat-NB1 modes in LTE release 13[0], LTE will soon be usable even for low-power IoT devices. AT&T and Verizon are already racing to support those standards on their networks.[1]
[0] https://www.qualcomm.com/invention/technologies/lte/lte-iot
[1] http://www.fiercewireless.com/tech/verizon-at-t-both-claim-l...
Damn it, Nokia had a Symbian phone you could use as a basic desktop for emails and surfing back when iPhone and Android barely did video out (and had to kill the phone screen to do so at least on Android). The mobile world basically came to a standstill, if not went backwards almost a decade, because everyone turned to the odd duck out to lead them into the future...
Typically HSPA is 5mhz+5mhz FDMA, but the carrier is only 3.6mhz+3.6mhz and can be slimmed to 4.2mhzx4.2mhz on Ericsson equipment. NSN equipment can go as low as 3.8x3.8.
In a slim HSPA situation you can run multiple 0.2x0.2 GSM channels.
LTE I've seen all over deployed in 5mhzx5mhz, but I've never seen the 3mhzx3mhz or 1.4mhzx1.4mhz configurations in the wild (they would overload easy).
Non-phone GSM devices are widely operated because of low cost and low data speed needs (most of them just ping a SMS in some direction or other).
UMTS deployments are more likely to be for bandwidth needs, and thus more likely to have moved to LTE setups already.
What I'm trying to say is that while your quip is entertaining:
a) it's impractical to scan/compromise IoT devices remotely without a stupid design (by IoT standards stupid, btw- not regular internet design- we're talking REALLY REALLY STUPID).
b) I would bet my mortgage that the logic you are presenting was never considered by the relevant carriers. They're not that smart.
[1] https://www.wirelessweek.com/news/2016/07/verizon-targeting-...
I don't think this is that insane. I doubt there are many devices that only support UMTS, but there are tons that only support GSM, including many in embedded systems that can't easily be upgraded. So by using most of your spectrum for LTE, you get spectrum efficiency, and supporting GSM you can support everything that doesn't do LTE (just not at high speeds).
Carriers have made it a policy to not whitelist imported devices for voLTE. IMEI needs to be whitelisted at carrier AND carrier file installed in phone needs to have support turned on. Either thing missing, no voLTE for you.
EDIT: Forgot to mention, non-voLTE still signals with LTE for incoming calls and SMS, it'll handover to HSPA/CDMA/GSM within about 2 seconds of the signal coming in. Unfortunately I don't have specifics of this process.
It was a funny loophole to get unlimited SMS on T-Mobile back when they just changed name from Voicestream.
I'm not American, and thus my phone is free of carrier tampering.
I even learned about the SMS over GPRS (thanks) thing because a relative of mine once owned a phone where we had to turn it off to actually get reliable SMS delivery, as it defaulted to GPRS mode.