GSMA TAC Allocation and IMEI
`Programming Rules
`for
`Device Brand Owners and Manufacturers
`Training Guide
`February 2018 v1.0
`
`Copyright © 2018 GSMA
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 1
`
`
`Programming Rules
`for
`Device Brand Owners and Manufacturers
`Training Guide
`February 2018 v1.0
`
`Copyright © 2018 GSMA
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 1
`
`
`
`Introduction
`
`About this document
`This is a practical training guide to help
`understand TAC allocations and IMEI
`production as specified in GSMA TS.06
`IMEI Allocation and Approval Process
`and TS.30 TAC IMEI Application Forms
`which can be found on the GSMA IMEI
`db homepage, together with the GSMA
`IMEI Security Technical Design
`Principles document.
`
`Who should read this document?
`This document has been compiled for
`device brand owners and their associates
`who are required to program a unique
`IMEI in each mobile device they produce.
`
`About GSMA
`The GSMA is the global industry administrator of
`the TAC and IMEI allocation system, essential to
`the correct functioning of 3GPP devices and the
`mobile ecosystem.
`
`2
`
`TAC (Type Allocation Code)
`
`IMEI (International Mobile Equipment Identity)
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 2
`
`
`
`14, 15
`
`16
`
`17, 18
`
`19, 20
`
`21, 22
`
`23, 24
`
`25
`
`26
`
`What if I have multiple SIM devices?
`
`What if I have multiple transceivers?
`
`5 6 7
`
`8, 9
`
`How secure should IMEI be?
`
`8
`
`10
`
`11
`
`What if I outsource device production?
`
`What if buy or licence a device brand?
`
`What if I co-brand a device?
`
`Content
`
`Who uses TAC and IMEI?
`
`What are TAC and IMEI?
`
`What devices need an IMEI?
`
`Who applies for TAC?
`
`How do I apply for TAC?
`
`Where do I apply for TAC?
`
`How do I form an IMEI?
`
`When do I need new TAC?
`
`12, 13, 14
`
`What if I repair a device?
`
`3
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 3
`
`
`
`Rules at a Glance
`
`TAC identifies the device model, brand owner and OEM
`A TAC is allocated to a specific device model and brand owner
`Only one device model may be allocated to a TAC
`A new TAC is required for each unique device model
`TAC is the first 8 digits of an IMEI
`One million devices or units / IMEI per TAC
`After one million units allocate a new TAC
`Only use GSMA allocated TAC
`
`TAC Applications
`GSMA allocates TAC via appointed Reporting Bodies
`Reporting Bodies are TÜV SÜD BABT, CTIA, MSAI, TAF and TIA
`Device brand owners apply for TAC, even if outsourcing manufacture
`Modem producers apply for TAC not the end device brand owner
`Brand owner HQ location determines which Reporting Body is used
`Co-branding: The brand responsible for sales applies for TAC
`Brand licencing: The licensee applies for TAC
`
`4
`
`IMEI (International Mobile Equipment Identity)
`3GPP devices must contain an IMEI
`IMEI identifies individual unit and device model, brand owner, & OEM
`Every IMEI must be globally unique
`IMEI implantation shall be secure and tamperproof
`The first 8 digits of the IMEI are the TAC
`Incremental IMEI serial number for each device unit produced
`Multi-SIM devices with one transceiver need one IMEI
`Devices which are 3GPP and 3GPP2 compliant require one IMEI
`Multi-transceiver devices require multiple IMEI
`Do not duplicate IMEI
`Spare IMEI capacity is prohibited for use in other models
`Secure IMEI implementation prevents the IMEI being changed
`Repairs involving replacing peripheral components do not impact
`IMEI
`Repairs that replace components that contain a securely stored IMEI
`result in new IMEI
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 4
`
`
`
`How are TAC / IMEI serial numbers used?
`
`Consumers
`
`Operators
`
`Law
`Enforcement
`
`Insurers
`
`Customs
`& Excise
`
`IoT Service
`Providers
`
`Manufacturers
`& OS providers
`
`Government
`& regulators
`
`Recyclers
`
`Retailers
`& traders
`
`Theft
`checking
`Lawful
`interception/
`location
`Compliance
`checking
`
`Authenticity
`False claim
`detection
`
`Taxation
`Certification
`Authenticity
`Counterfeit
`detection
`
`Identification
`SW updates
`Remote
`control
`Support
`Blocking
`Fraud
`detection
`
`Updates
`App mgmt
`Service
`delivery
`Support
`Warranty
`Compliance
`Theft
`reporting
`Testing
`
`Certification
`Type approval
`Taxation
`Crime
`management
`
`Authenticity
`Warranty
`Theft
`checking
`
`Authenticity
`Compliance
`Warranty
`Theft
`checking
`
`Support
`Warranty
`Authentication
`Theft reporting
`Theft checking
`
`Identification
`Support
`Device blocking
`Lawful
`interception
`/location
`Updates
`Configuration
`Analytics
`Sales &
`marketing
`Service delivery
`Whitelisting
`Fraud detection
`
`5
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 5
`
`
`
`What is an IMEI?
`
`Every device must
`have a unique IMEI
`number identifying
`brand owner & model.
`The Brand Owner must
`apply to the GSMA for
`the TAC code.
`
`Rule:
`
`TAC: Type Allocation Code
`
`Serial Number
`
`Check Digit
`
`86
`
`Reporting
`Body identifier
`
`916102
`
`Type Identifier
`Indicating brand owner and
`device model allocated by
`Reporting Body
`
`991292
`
`Unique Number assigned
`to individual devices
`by the manufacturer
`
`0
`
`A function
`of the other digits
`[calculated by
`the manufacturer]
`
`6
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 6
`
`
`
`What devices need an IMEI?
`
`3GPP devices require
`an IMEI.
`
`Rule:
`
`Mobile / Feature
`Phone
`
`Smartphone
`
`Tablet
`
`IoT Device
`
`Wearable
`
`Dongle
`
`Modem
`
`WLAN Router
`
`7
`
`Key: 3GPP transceiver
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 7
`
`
`
`Process of applying for TAC
`
`The brand owner is the
`TAC holder and the
`manufacturer is named
`as OEM on the TAC
`application form.
`
`Rule:
`
`Brand owner
`plans product
`
`Select external
`design house if
`required
`
`Select external
`manufacturer if
`required
`
`Brand owner
`confirms
`device model
`specification
`
`Brand owner
`applies
`for TAC
`for model
`
`Brand owner
`provides
`TAC to
`manufacturer
`
`Manufacturer
`produces device
`model and
`forms unique
`IMEI from
`the TAC
`
`End products
`include
`unique IMEIs
`
`8
`
`Brand owner action
`
`Manufacturer action
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 8
`
`
`
`Who applies for TAC when IoT modems are
`installed in other equipment?
`
`Modem
`
`When modems are
`installed in other
`machines, the original
`modem producer
`applies for TAC.
`
`Rule:
`
`Fridge manufacturer
`
`Smart meter manufacturer
`
`Automaker
`
`9
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 9
`
`
`
`Who issues the TAC code?
`
`Global Decimal
`Administrator
`
`GSMA appointed Reporting
`Bodies issue TAC codes.
`The HQ location of the brand
`owner determines which
`Reporting Body manages
`an application.
`
`China
`
`86
`
`India
`
`91
`
`Rest of World
`
`35
`
`Specialist
`identifier:
`
`Specialist:
`
`USA
`
`01
`CTIA
`
`Rest of World
`
`99
`TIA
`
`All device types
`
`All device types
`
`All device types
`
`Coverage:
`
`Optional
`source when
`applying for
`PTCRB
`certification
`
`Optional source
`for 3GPP /
`3GPP2
`multi-mode
`devices
`
`Reporting
`Body identifier:
`
`Reporting
`Body:
`
`Coverage:
`
`10
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 10
`
`
`
`How do you form an IMEI?
`
`TAC: Type Allocation Code
`
`Serial Number
`
`Check Digit
`
`35
`
`123451
`
`000000
`
`X
`
`35 123451 000001 X
`35 123451 000002 X
`35 123451 000003 X
`
`Model A
`Model A
`Model A
`
`11
`
`The TAC identifies the
`device model. Only
`one model per TAC.
`Each device must have
`a unique IMEI.
`
`Rule:
`
`35 123451 000001 X
`35 123451 000001 X
`35 123451 000001 X
`
`Do not
`duplicate IMEI
`
`Model A
`Model A
`Model A
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 11
`
`
`
`When do you need a new TAC for a device model?
`
`The following are considered
`variations to a specification
`which do require a new TAC
`
`Model A
`Model B
`Model C
`
`The following are considered
`variations to a specification
`which do not require a new TAC
`
`Model A
`Model A
`Model A
`
`Brand owner
`
`External
`manufacturer
`
`Model Name
`
`Components
`Casing
`Motherboard
`Chipset
`Number of cameras
`
`Connectivity
`Transceiver
`capabilities
`Frequency bands
`
`Operating system
`e.g. Android, Tizen
`
`Different version
`of same OS
`e.g. Android 7,
`Android 8
`
`User interface
`differences
`
`Marketing Name
`
`Devices
`configurations
`subset of
`transceiver
`frequency bands
`
`Manufacturer
`producing same
`model in different
`locations
`
`Minor variations
`Camera pixel count
`Colour of device
`Memory size
`Minor components
`
`12
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 12
`
`
`
`TAC and multiple device models
`
`TAC: Type Allocation Code
`
`Serial Number
`
`Check Digit
`
`35
`
`123451
`
`X
`
`35 123451 000000 X
`35 123452 000000 X
`35 123453 000000 X
`
`Each device model
`must be allocated a
`unique TAC.
`
`Rule:
`
`35 123451 000000 X
`35 123451 000000 X
`35 123451 000000 X
`
`Model A
`Model B
`Model C
`
`Model A
`Model B
`Model C
`
`13
`
`Use a different
`TAC for each model
`
`Do not use the same
`TAC for each model
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 13
`
`
`
`TAC and high
`volume production
`
`TAC: Type Allocation Code
`
`Serial Number
`
`Check Digit
`
`35
`
`123451
`
`999999
`
`A new TAC is
`required for every
`1 million units
`produced.
`
`Rule:
`
`From: 35 123451 000000 X
`35 123451 999999 X
`To:
`
`From: 35 123451 000000 X
`35 123451 999999 X
`To:
`
`From: 35 123451 000000 X
`35 123451 999999 X
`To:
`
`From: 35 123452 000000 X
`35 123452 999999 X
`To:
`
`Model A
`
`000,000
`to
`999,999
`
`Model A
`
`Over:
`1,000,000
`
`Use another TAC
`after 1 million units
`
`Do not use the same
`TAC for the next million units
`
`Model A
`
`000,000
`to
`999,999
`
`Model A
`
`Over:
`1,000,000
`
`14
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 14
`
`
`
`Unused TAC capacity
`
`TAC: Type Allocation Code
`
`Serial Number
`
`Check Digit
`
`35
`
`123451
`
`999999
`
`35 123451 000000 X
`
`35 123451 175000 X
`
`Model B
`
`000,000
`to
`175,000
`
`Spare capacity in
`one TAC cannot be
`transferred to another
`device model.
`
`Rule:
`
`35 123451 175001 X
`
`35 123451 350000 X
`
`Model A
`
`000,000
`to
`175,000
`
`15
`
`Unused capacity can only be
`used for future production
`of the same model
`
`Do not use spare capacity
`for a different model
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 15
`
`
`
`When one network
`connection is
`present, only one
`IMEI is required.
`
`Rule:
`
`1 TAC / 1 IMEI
`
`Multiple SIM, UICC and eUICC
`
`1 TAC / 1 IMEI
`
`16
`
`Single SIM
`
`1
`
`2
`
`Multi SIM
`One transceiver
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 16
`
`
`
`Multiple transceivers
`
`1 TAC / 2 IMEI
`
`1 TAC
`
`Serial
`
`Check
`
`86123451
`86123451
`
`000001 X
`000002 X
`
`17
`
`Parallel
`connections
`
`Multiple different
`transceivers
`
`Each parallel connection
`requires a unique IMEI.
`Different separate
`transceivers
`require unique TACs.
`
`Rule:
`
`2 TAC / 2 IMEI
`
`2 TAC
`
`Serial
`
`Check
`
`86123451
`86123452
`
`000001 X
`000001 X
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 17
`
`
`
`Multiple Radio
`Access Technology
`
`3GPP + 3GPP2
`IMEI
`
`3GPP
`IMEI
`
`3GPP2
`MEID
`
`Independent
`platforms
`
`1 TAC + 1 IMEI
`
`Integrated
`3GPP and 3GPP2
`transceiver requires
`one IMEI
`
`18
`
`Integrated 3GPP and
`3GPP2 devices require
`only one IMEI.
`
`Rule:
`
`1 IMEI + 1 MEID
`
`Separate parallel
`3GPP and 3GPP2
`transceivers require
`one IMEI and one MEID
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 18
`
`
`
`How secure should an IMEI be?
`
`I M E I
`
`IMEI implementation
`shall be resistant to
`hacking, spoofing or
`change by any means.
`
`Rule:
`
`19
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 19
`
`
`
`IMEI secure implementation principles
`
`Here are the recommended GSMA IMEI security technical
`design principles to help device brand owners develop a
`comprehensive security architecture to protect the
`IMEI implementation.
`
`1: Software Integrity
`
`2: No Modification
`
`3: No Cloning
`
`4: No External Access
`
`5: No fallback
`
`Detect, prohibit and
`record attempts to
`alter data or software
`
`Protect component
`code against
`manipulation
`
`Prevent IMEI copying
`between different
`devices
`
`6: No tampering
`
`7: Software Quality
`
`8: No Hidden Menus
`
`Make IMEI implemen-
`tation inaccessible
`from outside the
`device
`9: No Substitution
`
`Stop unauthorised
`reversion to old
`software versions
`
`Prevent, detect and
`respond to attempts
`to change IMEIs
`
`Develop software in
`accordance with best
`process & techniques
`
`No means to access
`or modify areas that
`store the IMEI
`
`Prevent substitution
`of components that
`contain memory
`
`20
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 20
`
`
`
`Who applies for TAC when
`production is out sourced?
`
`The brand owner must
`apply for TAC.
`
`Rule:
`
`TAC
`Holder
`
`TAC
`Holder
`
`TAC
`Holder
`
`21
`
`Brand owner
`
`Design house
`
`Manufacturer
`
`Internal
`
`Outsourced 01
`
`Outsourced 02
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 21
`
`
`
`Multiple production facilities and TAC
`
`TAC
`Holder
`
`TAC
`Holder
`
`TAC
`Holder
`
`PRODUCTION
`Including
`secure IMEI
`
`PRODUCTION
`Including
`secure IMEI
`
`PRODUCTION
`Including
`secure IMEI
`
`PRODUCTION
`Including
`secure IMEI
`
`The same model, produced by different
`outsourced manufacturers requires two TAC.
`Each outsourced OEM must be named on the
`TAC application form.
`
`The same model, designed and produced by
`different outsourced manufacturers requires two
`TAC. The outsourced OEMs must be named on
`the TAC application form.
`
`22
`
`Brand owner
`
`Design house
`
`Manufacturer
`
`Internal
`
`Outsourced 01
`
`Outsourced 02
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 22
`
`
`
`Original brand owner
`must confirm transfer of
`brand ownership before
`TAC allocation can be
`managed by new
`brand owner.
`
`Rule:
`
`Sale of Brands and TAC
`
`Confirmation of
`brand transfer
`
`Confirmation of
`brand transfer
`
`Brand Seller
`
`GSMA
`IMEI Db
`
`Reporting
`Bodies
`
`Brand sale
`agreement
`
`Register and
`apply for TAC
`
`Buyer/New
`Brand Owner
`
`23
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 23
`
`
`
`Original brand owner
`must confirm licencing
`of brand before TAC
`allocation can be
`managed by the
`licensee.
`
`Rule:
`
`Brand Licencing and TAC
`
`Confirmation of
`brand licence
`
`Confirmation of
`brand licencing
`
`Brand Owner
`
`GSMA
`IMEI Db
`
`Reporting
`Bodies
`
`Brand licence
`agreement
`
`Brand licence
`agreement
`
`Brand Licensee
`
`Brand Licensee
`
`Register and
`apply for TAC
`
`Register and
`apply for TAC
`
`24
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 24
`
`
`
`Who applies for TAC when multiple brands
`are present?
`Example:
`Mobile network operator, Brand 1, provides
`devices in association with manufacturer, Brand 2
`
`Where multiple brands
`are involved the brand
`responsible for sales
`must apply for TAC.
`
`Rule:
`
`Brand 1 logo
`
`Brand 1
`(Sales responsibility )
`
`Brand 1
`applies for TAC
`
`Brand 2 is secondary brand
`
`Produced by
`Brand 2
`
`Produced by Brand 2
`
`35 123451 000001 X
`
`25
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 25
`
`
`
`When does a repair
`require an IMEI to change?
`
`TAC: Type Allocation Code
`
`Serial Number
`
`Check Digit
`
`35
`
`123451
`
`000000
`
`X
`
`Changing the
`component that
`securely stores the IMEI
`results in a change of
`IMEI value.
`
`Rule:
`
`35 123451 000001 X
`
`35 123451 000001 X
`
`Peripheral components
`can be replaced provided
`the model specification
`is not changed
`
`Keep IMEI
`
`Model A
`
`Broken
`mother-
`board
`
`Model A
`
`Replace-
`ment
`mother-
`board
`
`35 123451 000001 X
`
`35 123451 634535 X
`
`Changing out the
`motherboard, requires
`changing the IMEI keeping the
`appropriate TAC
`
`Change IMEI
`
`Model A
`
`Broken
`screen
`
`26
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 26
`
`
`
`A well-functioning IMEI ecosystem benefits all
`
`Recyclers
`
`Retailers &
`traders
`
`Government &
`regulators
`
`Manufacturers &
`OS providers
`
`IoT Service
`Providers
`Customs &
`Excise
`
`GSMA
`IMEI Db
`
`Operators
`
`Insurers
`
`Consumers
`
`27
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 27
`
`
`
`To register for TAC
`allocations or to clarify
`any of this material,
`please contact:
`
`imeihelpdesk@gsma.com
`
`DivX Exhibit 2015
`Netflix & Hulu v. DivX, IPR2020-00648
`Page 2015 - 28
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
