更新时间:2023-08-30 16:27:40
除非找到了一个私有API解决方案 - 我们的组织正在推进将IMEI和phone#作为受保护的应用程序设置放入我们的企业应用程序中。
Unless there is a private API solution found - our organization is moving forward with placing the IMEI and phone# into our Enterprise Applications as a guarded Application Settings.
使用基于相机的iOS7条形码识别功能 - 甚至可以在初始配套和部署期间从电话盒扫描IMEI,而不是手动输入。
With the new camera based barcode recognition of iOS7 - the IMEI can even be scanned from the phone box during initial kitting and deployment rather than entered by hand.
我们还考虑跟踪链接到IMEI / Phone#的数据库等中的identifierForVendor UUID,但因为它可以改变,因为我们的历史数据都是基于IMEI的 - 没有'有意义的是将这一跟踪复杂性层添加到半无用的标识符中,该标识符不会追溯到像Phone / IMEI这样的通用有意义的跟踪机制。
We also considered tracking the identifierForVendor UUID in a database etc. linking to IMEI/Phone# but since it can change and since our historical data is all IMEI based - didn't make sense to add that layer of tracking complexity to a semi-useless identifier that doesn't trace back to a universal meaningful tracking mechanism like Phone/IMEI.