No. But at a certain point, with the high speed modulations we have today, it is totally feasible to broadcast these passively to a multi-state region encompassing a radius of hundreds of miles.
There's not a legitimate engineering reason that the network needs to maintain constant fine-grained location data for each registered device at this point. The scope of the registration can be far more widely cast.
This would even have upsides for the devices and users. As check-ins to the network in which the device must transmit to the network would be far reduced, battery life improvements can be had.
Yes, this increases the amount of "broadcast" traffic, but honestly, even for some of the busiest telco switches in New York or LA, those data streams don't even approach the throughput requirements of a single HD Youtube stream...
/napkin overestimate using US 6B/calls/day with a nationwide 256B packet each, that's roughly a 100Mbps broadcast channel, which is ~5 digital TV channels, or one geostationary satellite's half-duplex bandwidth if it could see the entire US. As mdhardeman points out, it's easier than that, and there is plenty of room for re-transmission.
What is the passive bitrate of a tower->cell connection? LTE/GSM whatever.
Pagers parse every single page. They only alert you when it's to your address. /napkin is just that, if you designed the protocol this would be very doable. The receiver can passively listen quite cheaply energy wise. This is nothing like decoding a video stream.
No. But at a certain point, with the high speed modulations we have today, it is totally feasible to broadcast these passively to a multi-state region encompassing a radius of hundreds of miles.
There's not a legitimate engineering reason that the network needs to maintain constant fine-grained location data for each registered device at this point. The scope of the registration can be far more widely cast.
This would even have upsides for the devices and users. As check-ins to the network in which the device must transmit to the network would be far reduced, battery life improvements can be had.
Yes, this increases the amount of "broadcast" traffic, but honestly, even for some of the busiest telco switches in New York or LA, those data streams don't even approach the throughput requirements of a single HD Youtube stream...
/napkin overestimate using US 6B/calls/day with a nationwide 256B packet each, that's roughly a 100Mbps broadcast channel, which is ~5 digital TV channels, or one geostationary satellite's half-duplex bandwidth if it could see the entire US. As mdhardeman points out, it's easier than that, and there is plenty of room for re-transmission.
What is the passive bitrate of a tower->cell connection? LTE/GSM whatever.
With everyone's phones receiving and parsing that, batteries would die very quickly.
Pagers parse every single page. They only alert you when it's to your address. /napkin is just that, if you designed the protocol this would be very doable. The receiver can passively listen quite cheaply energy wise. This is nothing like decoding a video stream.
1 reply →