(ME)ID Required
Stop Worrying
Sprint has already changed call center and front end systems for use with MEID. 😳
...
Technically, yes, but there's plenty more to be done.
They are certainly more prepared than Verizon. They have updated their back-end systems to deal with MEID, and they are ready for pESNs, unlike Verizon, who still has a lot of work to do before they can even handle pESNs, from what they told us.
But no one in the world has a network yet that can actually use MEID to identify a phone on the actual network, because the standard still hasn't been finalized, hence Sprint's quote in the article about waiting for "a place to hang their hat" so they can go ahead with the upgrades.
They are certainly more prepared than Verizon. They have updated their back-end systems to deal with MEID, and they are ready for pESNs, unlike Verizon, who still has a lot of work to do before they can even handle pESNs, from what they told us.
But no one in the world has a network yet that can actually use MEID to identify a phone on the actual network, because the standard still hasn't been finalized, hence Sprint's quote in the article about waiting for "a place to hang their hat" so they can go ahead with the upgrades.
...
Well, at least they aren't doing it the hard way. They could optionally retool the base stations to make the ESN a 56-bit code with a header of 24-null bits, or the full 56-bit MEID. It would ease the amount of headache of having two totally separate functions to have and increase the amount of backwards compatability.
The problem, of course, is running into the snag "What if the base station doesn't include the 24-bit header automatically?" and "What if nothing works?"
The problem, of course, is running into the snag "What if the base station doesn't include the 24-bit header automatically?" and "What if nothing works?"
...
This forum is closed.
