Device data for Mobile Operators

DeviceAtlas partners with the GSMA to provide an authoritative device capabilities database for mobile network operators and service providers in the operators space, called Device Map.

Device Map provides up-to-minute, high-quality, and high-accuracy device data combined with TAC (Type Allocation Code) for the telecommunications environment.

How is it used?

Device Map has many potential applications for mobile network operators and service providers working in the GSM ecosystem.

Device-related insight for sales and marketing

Device-related insight for sales and marketing

Identify specific devices to make compelling targeted marketing offers. For example, identify older devices that are due an upgrade or find out which devices drive higher ARPU.

Troubleshooting and customer support

Troubleshooting and customer support

Reduce churn and improve customer retention. Help customer service representatives or subscribers troubleshoot support issues according to their devices’ unique features.

Network optimization and planning

Network optimization and planning

Make business decisions that are driven by mobile traffic analysis. For example, track device-based network usage patterns to make decisions on network optimization, plan the roll out of network infrastructure such as LTE, or the retirement of obsolete capacity.

Enhanced analytics

Enhanced analytics

React quickly to specific events or traffic patterns. Get real-time or offline analytics on CDR or on-network traffic data. Read more

Device Map makes these and more use cases possible in any scenario where TAC is available.

Device analytics for operators

See how Device Map's fine grained device data can be used by BI and analytics teams in the operator environment.

Launch Demo

How it works

Device Map gives you an in-depth understanding of all network traffic.

TAC code

Device Map maps detailed device data to each TAC

TAC maps to ID

Import it into your BI or analytics tools

Analyze traffic

Analyze traffic using over 100 data points

Detailed TAC-based device data

Mobile device database for TAC

TAC is the 8-digit part of the IMEI code used to identify mobile devices on GSM or IMEI-based networks. They are issued to device manufacturers by the GSMA, the global representative body for mobile operators.

Each TAC is mapped to a device record from DeviceAtlas with over 100 detailed data points, such as operating system, browser, multimedia capabilities, screen size, and much more. This additional layer of detailed and accurate device data opens up a range of powerful analytics and BI use cases.

Device Name
TAC Type Allocation Code
DeviceAtlas ID DeviceAtlas Device reference (Multiple TACs can reference one Device ID)
Standardised Full Name Market recognised name (composite of Vendor + Marketing Name or Model)
Standardised Device Vendor The name of the maker (OEM) of a device, browser or some other component
Standardised Device Model The model name of a device, browser or some other component.
Standardised Marketing Name The marketing name for a device
Manufacturer Primary organisation creating (not necessarily assembling) the device.
Year Released This is the year that the device was released (or announced)
Hardware
Mobile Device True if the device is meant for use on the move.
Primary Hardware Type Primary hardware type, e.g. Tablet, Mobile Phone, etc. Major device types are also available as Boolean fields.
Touch Screen User may touch the screen to interact with the device.
Screen Width The total number of addressable pixels in the horizontal direction of a rectangular display when held in its default orientation. The Property does not apply to displays that are not rectangular or square.
Screen Height The total number of addressable pixels in the vertical direction of a rectangular display when held in its default orientation. The Property does not apply to displays that are not rectangular or square.
Diagonal Screen Size The diagonal dimension of the screen in inches.
Display PPI The pixel density of the Device's screen. Pixels Per Inch.
Device Pixel Ratio Ratio between physical pixels and device-independent pixels (dips) on the browser.
Screen Color Depth The color depth of a display.
NFC The device has NFC (Near Field Communication) hardware.
Camera Megapixels of the camera if the device has one.
Is Mobile Phone The device is a mobile phone.
Is Tablet The device is a tablet device.
Is EReader The device is a reading device.
Is Games Console The device is a games console.
Is TV The device is a television.
Is Set Top Box The device is a set-top box.
Is Media Player The device is a media player.
Chipset Vendor The company/organisation that provides the chipset to the market.
Chipset Name The marketing name for a chipset. Alternatives separated by '/'.
Chipset Model The model number of a chipset.
CPU Name The marketing name for the CPU. If a device is equipped with more than one CPU, values are separated by '&'.
CPU Cores The Number of physical cores in the CPU. If a device is equipped with more than one CPU, values are separated by '+'.
CPU Maximum Frequency The maximum clock frequency of a single core expressed in MHz. If a device is equipped with more than one CPU, values are separated by '&'.
GPU Name The model name for the GPU.
SIM Slots Number of SIM card slots with which the device is equipped.
SIM Size Size of a SIM card supported by the device. It may support multiple values, separated by '&'.
Internal Storage Capacity The capacity of the device storage. The value is expressed in GB and the metric system is used for unit conversion (e.g. 1 GB = 1000 MB).
Expandable Storage The device supports physical storage expansion.
Total RAM The amount of memory allocated to RAM as reported by manufacturer. The value is expressed in MiB, with binary conversion (1GiB = 1024MiB)
OS
OS Name The name of the Operating System installed on the device. This can be used as a substitute for the Boolean OS properties. Please see the complete list of predefined property values.
OS Version The Operating System minimum version installed on the device.
OS Android The device is distributed with Android OS pre-installed.
OS Bada The device is distributed with Bada OS pre-installed.
OS iOS The device is distributed with iOS pre-installed.
OS Rim The device is distributed with RIM OS pre-installed.
OS Symbian The device is distributed with Symbian OS pre-installed.
OS Windows Mobile The device is distributed with Windows Mobile pre-installed.
OS Windows Phone The device is distributed with Windows Phone pre-installed.
OS Windows RT The device is distributed with Windows RT OS pre-installed.
OS Web OS The device is distributed with WebOS pre-installed.
Browser
Browser Name The name or type of the default browser on the device. Please see the complete list of predefined property values.
Browser Version The default browser version on the device.
Browser Rendering Engine The name or type of the browser rendering engine used by the browser. Please see the complete list of predefined property values.
Markup XHTML Basic 1.0 The ability of the web browser to render a page using XHTML Basic 1.0.
Markup XHTML MP 1.0 The ability of the web browser to render a page using XHTML-MP 1.0.
Markup XHTML MP 1.1 The ability of the web browser to render a page using XHTML-MP 1.1.
Markup XHTML MP 1.2 The ability of the web browser to render a page using XHTML-MP 1.2.
Markup WML1 The ability of the web browser to render a page using WML.
vCard Download The ability of the web browser to download and open the device's address book when a vCard URI is used.
Image Gif87 The ability to display a GIF87 image embedded in a mobile web page, using a tag such as img or object.
Image GIF89A The ability to display a GIF89a image embedded in a mobile web page, using a tag such as img or object.
Image JPG The ability to display a JPG image embedded in a mobile web page, using a tag such as img or object.
Image PNG The ability to display a PNG image embedded in a mobile web page, using a tag such as img or object.
URI Scheme Tel The ability of the web browser to start a telephone call when a URI is defined with the protocol 'tel' followed by a telephone number (e.g. tel:+35312345678). Verify that the browser behaves as expected.
URI Scheme SMS The ability of the web browser to start a new SMS message when a URI is defined with the protocol sms followed by a telephone number (e.g. sms:+35312345678). Verify that the browser behaves as expected.
URI Scheme SMS To The ability of the web browser to start a new SMS message when a URI is defined with the protocol smsto followed by a telephone number (e.g. smsto:+35312345678). Verify that the browser behaves as expected.
Cookie The ability of a client to store cookies and send them when appropriate.
HTTPS The web browser supports the SSL protocol. Support of different certificate authorities is independent from the ability of supporting SSL. Verify that a page protected with SSL is displayed properly.
Memory Limit Markup Describes the maximum size in bytes for markup in a web page. Media is treated separately. Some browsers might have a variable memory limit based on the memory used by other applications, in that case 0 will be used.
Memory Limit Embedded Media Describes the maximum size in bytes for media files embedded in a web page. Media is treated separately. Some browsers might have a variable memory limit based on the memory used by other applications, in that case 0 will be used.
Memory Limit Download Describes the maximum size in bytes for downloaded from a web page and stored locally (e.g. a ringtone or an image). Media is treated separately. Some browsers might have a variable memory limit based on the memory used by other applications, in that case 0 will be used.
Flash Capable The browser is Flash-Capable.
JavaScript Capabilities
JS Support Basic Java Script The browser has some level of JavaScript support, typically Alert, Confirm, setInterval, setTimeout.
JS Modify Dom The browser's JavaScript engine supports modifying DOM elements.
JS Modify CSS The browser's JavaScript engine supports modifying CSS elements.
JS Support Events The browser's JavaScript engine supports Events.
JS Support Event Listener The browser's JavaScript engine supports Event Listeners.
JS XHR The browser's JavaScript engine supports XMLHttpRequest.
JS Support Console Log The browser's JavaScript engine supports console.log().
JS Json The browser's JavaScript engine supports JSON objects.
Supports Client Side Indicates whether the device supports the DeviceAtlas ClientSide component.
Network Protocols
CSD The device is capable of connecting to CSD (Circuit Switched Data) networks.
HSCSD The device is capable of connecting to HS CSD (High Speed Circuit Switched Data) networks.
GPRS The device is capable of connecting to GPRS (General Packet Radio Service) networks.
EDGE The device is capable of connecting to EDGE (Enhanced Data rates for GSM Evolution) networks.
HSDPA The device is capable of connecting to HSDPA (High-Speed Downlink Packet Access) networks.
UMTS The device is capable of connecting to UMTS (Universal Mobile Telecommunications System) networks.
HSPA+ The device is capable of connecting to HSPA+ (Evolved High-Speed Packet Access) networks.
LTE The device is capable of connecting to LTE (Long Term Evolution) networks.
LTE Category The UE Category which the device is capable of using. The device will also be able to use all preceding Categories.
LTE Advanced The device is capable of connecting to LTE Advanced (Long Term Evolution Advanced) networks.
VoLTE The device is capable of making VoLTE calls. When True, this implies LTE, HD Voice, and AMR-WB are True.
WiFi The device is capable of connecting to WiFi networks.
VoWiFi The device is capable of seamless call handover between Wi-Fi and VoLTE connections.
HTML5 Capabilities
HTML Audio The browser supports the audio HTML tag.
HTML Canvas The browser supports the canvas element.
HTML Inlinesvg The browser supports inline SVG.
HTML SVG The browser supports SVG.
HTML Video The browser supports the video HTML tag.
CSS Animations The browser supports CSS animations.
CSS Columns The browser supports CSS columns.
CSS Transforms The browser supports CSS transforms.
CSS Transitions The browser supports CSS transitions.
JS Application Cache The browser's JavaScript engine supports Application Cache.
JS Geo Location The browser's JavaScript engine supports Geo Location.
JS Indexeddb The browser's JavaScript engine supports indexedDB.
JS Local Storage The browser's JavaScript engine supports Local Storage.
JS Session Storage The browser's JavaScript engine supports Session Storage.
JS Web GL The browser's JavaScript engine supports Web GL.
JS Web Sockets The browser's JavaScript engine supports the Web Sockets API.
JS Web SQL Database The browser's JavaScript engine supports the Web SQL Database API.
JS Web Workers The browser's JavaScript engine supports the Web Workers API.
JS Device Orientation The browser's JavaScript engine supports Device Orientation.
JS Device Motion The browser's JavaScript engine supports Device Motion event.
JS Touch Events The browser's JavaScript engine supports Touch events.
JS Query Selector The browser's JavaScript engine supports the Query Selector.
Media Playback Capabilities
WMV The ability to play WMV files.
MIDI Monophonic The ability to play MIDI files with not more than 1 note at a time, normally Type 0. The device is able to play the MIDI file as expected.
MIDI Polyphonic The ability to play MIDI files, can be Type 0 or Type 1, may have more than 1 note at a time. The device is able to play the MIDI file as expected.
AMR The ability to play AMR (Adaptive Multi-Rate) files as defined by 3GPP. The device is able to play the AMR file as expected.
MP3 The ability to play MP3 (MPEG-1 Audio Layer 3) files. The device is able to play the MP3 file as expected.
AAC The ability to play AAC (Advanced Audio Coding) as defined as part of the MPEG-4 specifications. The device is able to play the AAC file as expected.

Why operators use Device Map?

Building your very own consistent, accurate, and up-to-date TAC-based device database requires costly and time consuming research, and manual updates. Inconsistent naming conventions and standards can often be a challenge in the mobile operator environment.

Device Map addresses all these problems by providing operators with an organization-wide device database. Our solution ensures that consistent naming conventions and accurate, automatically updated data are used within the entire organization removing additional workload required in data management, and manual updates.

Why operators use Device Map?

Get a Device Map data sample

A data sample is available to allow mobile operators to evaluate the real-life applications of Device Map. To get a bespoke data sample, please complete the form providing us with as much detail as possible. Your request will be processed by our partners at the GSMA.

We communicate via email to process your request in line with our privacy policy. Please check the box to give us your permission to do this.