Mobile networks
Enhance a device’s TAC (taken from the IMEI) with additional device specific information, such as price band, model, and hardware.
Use 51Degrees for telecoms and handsetsIMEI and TAC
TAC information is a powerful tool for mobile network operators. Derived from the first eight digits of an IMEI number, the TAC identifies wireless mobile devices on the GSM network.
Keeping track of all the TACs can be time-consuming and costly. You may also be missing out on enhanced device-specific insight.
The 51Degrees TAC service matches the TAC to other device information such as hardware, operating system, or multimedia technologies. We can easily navigate different naming conventions between vendors and identify duplicate TACs for an accurate, up-to-date database.
With this additional device insight, you can be confident in your business decisions.
What data points can you detect?
We map TAC data across multiple data properties, including 4G, 5G, NFC connections, and radio frequencies. We have many other properties related to the hardware or physical device attributes such as screen size or processors.
Other non-tangible properties we can detect are the device’s price at launch or age.
You could use TAC for:
Your customer service team can troubleshoot specific device features with ease, thanks to comprehensive device data. Create quicker resolutions, better customer experiences, and more upselling opportunities.
Handset recyclers and resellers can save time researching information on the wireless device by using 51Degrees. Identify device specifications from a TAC such as the price at launch or the age of the device.
Understand customer behavior in real-time with device insight, improving results through sharper targeting and analysis. Optimize content by screen size, troubleshoot device-specific performance issues, or tailor promotions by device price and age. In-depth device data drives smarter business decisions.
Network operators and vendors, insurers, and recycling companies are increasingly using TAC to enhance cybersecurity. Validate that the device characteristics match the TAC information to help authenticate devices and prevent fraud.
2 ways to use device data in your network
Check the hardware behind an IMEI
The TAC is the first eight digits of the IMEI. Look up the full hardware specification behind it, check the insured or traded device is the model the paperwork claims, then price policies, payouts, and plans on what the device is really worth.
Who it serves. Mobile networks, device insurers, and trade-in platforms.
Pairs well with Spot the fake, to verify a device, then see what it is worth.
Integration time. 30 minutes with TAC lookup.
Ingredients, 10
- TAC
- HardwareVendor
- HardwareModel
- HardwareName
- NativeBrand
- NativeModel
- ReleaseYear
- ReleaseAge
- HardwareRank
- PriceBand
Hero ingredient. TAC The TAC identifies the model behind the IMEI, even where software detection can't tell models apart.
- Take the TAC, the first eight digits of the IMEI
- Look up the full hardware specification behind it
- Check the device is what the paperwork claims
- Price policies, payouts, and plans on real device value
Chef's tip. Check the price band and release year against what the paperwork claims.
Send each device only the bytes it needs
Classify each device where the traffic lands. Match image and video variants to its real screen and the codecs it decodes, then trim what you send to fit the connection type.
What changes. You send fewer bytes, so pages load faster and delivery costs less.
Who it serves. Telcos, CDNs, and hardware platforms optimizing delivery.
Pairs well with The perfect stream, to choose the stream for each device. Light menu for low-end devices does the same for pages.
Integration time. One sprint at the edge.
Ingredients, 11
- DeviceType
- ScreenPixelsWidth
- ScreenPixelsHeight
- PixelRatio
- DeviceRAM
- CPU
- CPUCores
- HardwareVideoCodecsDecode
- BrowserVideoCodecsDecode
- WebP
- ConnectionType
Hero ingredient. HardwareVideoCodecsDecode Send video in a codec the device's chipset decodes in hardware.
- Classify each device where the traffic lands
- Match image and video variants to the real screen and codecs
- Trim what you send to fit the connection type
- Send fewer bytes to every device
Chef's tip. Start with the screen and the codecs, then trim what you send to fit the connection type.
Start with the network problem you want to solve
Each recipe explains the business use, followed by the properties and steps your developers need. It also includes a link to create a Resource Key.