Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
IMEI Allocation and Approval Process
Version 7.0
31st October 2013
This is a Non-binding Permanent Reference Document of the GSMA
Security Classification: Non-confidential
Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is confidential to the Association and is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and
information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those permitted under the security classification without the prior written approval of the Association.
Copyright Notice
Copyright © 2013 GSM Association
Disclaimer
The GSM Association (“Association”) makes no representation, warranty or undertaking (express or implied) with respect to and does not accept any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document. The information contained in this document may be subject to change without prior notice.
Antitrust Notice
The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy.
V7.0 Page 1 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
Table of Contents
1 2 3 4 5
History of TAC Allocation Introduction
Definition of Acronyms
3.1 Definitions
Reference Documents
International Mobile Equipment Identity (IMEI) 5.1 IMEI Format
5.1.1 Type Allocation Code - 8 digits
5.1.2 Reporting Body Identifier (NN) – 2 digits 5.1.3 ME Model Identifier (XXXXXX) – 6 digits 5.1.4 Serial Number (ZZZZZZ) - 6 digits 5.1.5 Check Digit – 1 digit
5.2 IMEI Software Version Numbers (SVN) (2 digits) Benefits to the Industry of having an IMEI IMEI Security and Integrity Guidelines TAC (IMEI) Usage Rules Test IMEI
4 4 4 5 6 6 7 7 7 8 8 8 8 9 9 10 13 14 14 15 15 15 15 16 16 17 17 19 24 25 25 25 25 26 26 27 27 28 28 29
6 7 8 9
9.1 Format of the Test IMEI for all countries except North America 9.2 Format of the Test IMEI for North America 10 Reporting Body Identifier List 11 Test IMEI Allocating Body List
12 List of Type allocated mobile equipment and IMEI allocations by Reporting
Bodies
13 The IMEI Database / CEIR 14 GSMA Responsibilities
15 Reporting Body Responsibilities
16 Type Allocation Holder Responsibilities 17 TAC Allocation Process
Annex A – Reporting Body Identifier List Annex B Annex C
– List of Test IMEI allocating bodies: – Informative Annex - IMEISV
C.1 GSM 02.16 - MS Software Version Number (SVN)
C.2 3GPP TS 22.016 - MS Software Version Number (SVN) C.3 Structure of the IMEISV
C.4 Software Version Number Allocation Principles C.5 Security Requirements
Annex D – Informative Annex – Historical Structure of the IMEI
D.1 Historical IMEI Structure
D.1.1 Type Allocation Code - 6 digits. (Valid prior to 01/01/03)
D.1.2 Reporting Body Identifier (NN) – 2 digits (valid prior to 01/01/03) D.1.3 ME Type Identifier (XXXX) – 4 digits (valid prior to 01/01/03)
V7.0 Page 2 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
D.1.4 Final Assembly Code (FAC) - 2 digits (valid prior to 01/01/03) D.1.5 Serial Number (SNR) - 6 digits (valid prior to 01/01/03) D.1.6 Spare Digit / Check Digit – 1 digit (valid prior to 01/01/03) Document Management
V7.0 Non-confidential
29 29 30 31
Page 3 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
1 History of TAC Allocation
The IMEI number allocations were originally administered and funded by a number of
national authorities as part of the type approval of mobile devices. In 1999, the type approval regime was abolished as a European regulatory obligation and this required industry to establish an alternative device certification program and a means to allocate identifiers to mobile devices. In April 2000 the GSMA was asked by industry stakeholders to assume responsibility for allocating IMEI number ranges, and Type Allocation Codes, to mobile device manufacturers
The GSMA was formally appointed by the industry as the Global Decimal Administrator (GDA) in 2004 with responsibility for:
Appointing regional bodies to allocate TAC/IMEI ranges Maintaining lists of allocated TACs/IMEIs
Distributing lists of allocated ranges via IMEI Database Provide expertise and advice on allocations
The GSMA is the only appointed allocation authority for 3GPP and 3GPP/3GPP2 compliant devices. The TIA can also allocate TAC for 3GPP/3GPP2.
2 Introduction
This document outlines the allocation principles applicable to the International Mobile Equipment Identity (IMEI) numbers. The following areas are covered:
Allocation principles for IMEI
Allocation principles for Reporting Bodies The role of the GSM Association Security requirements for the IMEI Software Version Numbers
Single band , Multiband, Multimode and Multi RAT (Radio Access Technology) Mobile Equipment (ME) Test IMEI
The overriding principles for IMEI allocation are preservation of the available number range, the prevention of duplication and the maintenance of security.
This document also details the allocation process to be followed for obtaining TAC/IMEI numbers from the authority approved by GSMA.
3 Definition of Acronyms
Acronyms 3G 3GPP 3GPP2 V7.0
Description 3 Generation Networks 3rd Generation Partnership Project 3rd Generation Partnership Project 2 Page 4 of 32
rdGSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
Acronyms CEIR EIR NFC IMEI LTE M2M ME MEID OS PC RAT SMS TAC TIA UE UMTS (U)SIM WLAN Description Central Equipment Identity Register Equipment Identity Register Near Field Communication International Mobile Equipment Identity Long-term Evolution, also known as 4G Machine to Machine Mobile Equipment Mobile Equipment Identifier Operating System Personal Computer Radio Access Technology Short Message Service Type Allocation Code Telecommunications Industry Association User Equipment Universal Mobile Telecommunications System Universal Subscriber Identity Module Wireless Local Area Network
3.1 Definitions
The term “ME Model” SHALL be used to refer to GSM mobile equipment models and products that are differentiated in the market.
Note: the term “mobile“ is used for all devices connected to a 3GPP/3GPP2 network, it can be a M2M or fixed device
“ME Model” is defined as an ME which is different from other MEs
a) By hardware design b) By transceiver c) By control software d) By frequency bands or
e) As it is manufactured or assembled or commissioned by different ME Owners The term Type Allocation shall refer to the process by which ME Model has been allocated a TAC/IMEI. This MUST have been obtained via an organization appointed by the GSM Association, e.g. a Reporting Body.
The term Reporting Body shall refer to a Body that is recognised by the GSM Association as having authority and competence to allocate IMEIs to ME Model.. There may be more than one Reporting Body in a country.
The term Type Allocation Holder / ME Owner shall refer to the entity that has been allocated a TAC for an ME Model.
“Type Allocation Holder / ME Owner”, is either:
V7.0 Page 5 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
a mobile device manufacturer, manufacturing and marketing devices under their own
brand;
a duly approved and bona fide representative of a mobile device manufacturer
assisting the mobile device manufacturer in (a) above,
a company distributing, marketing or offering MEs for sale under their own brand. An ME Model may only be allocated to one Type Allocation holder or ME Owner.
It should be noted that, within this document, ME is used to define the equipment being identified with the IMEI. Where the term ‘GSM ME’ is used within this document it can be considered to be interchangeable with 3G UE solely for the purpose of issues connected to the IMEI.
The key words “must”, “must not”, “required”, “shall”, “shall not”, “should”, “should not”, “recommended”, “may”, and “optional” in this document are to be interpreted as described in RFC2119
4 Reference Documents
Document Number 3GPP2 SC.R4001-0 3GPP2 SC.R4002-0 3GPP TS 02.07 3GPP TS 02.09 3GPP TS 02.16 3GPP TS 02.30 3GPP TS 03.03 3GPP TS 04.08 3GPP TS 22.016 3GPP TS 23.003 CTIA PTCRB NAPRD03 ISO/IEC 7812 RFC2119 Title Global Wireless Equipment Numbering Administration Procedures document regarding Multi RAT (Radio Access Technology) GHA Global Hexadecimal Administrator Assignment Guidelines and Procedures Mobile Station (MS) Features Security aspects International Mobile Station Equipment Identities (IMEI) Man-machine Interface (MMI) of the Mobile Station (MS) Numbering, Addressing and Identification Mobile radio interface layer 3 specification International Mobile station Equipment Identities (IMEI) Numbering, addressing and identification Overview of PTCRB Mobile/User Type Certification (includes IMEI control sections) Identification of issuers http://www.ietf.org/rfc/rfc2119.txt 5 International Mobile Equipment Identity (IMEI)
The International Mobile Equipment Identity number (IMEI) uniquely identifies an individual mobile device. The IMEI is unique to every ME and thereby provides a means for controlling access to GSM networks based on ME Model or individual units.
V7.0 Page 6 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
The “IMEI” consists of a number of fields totalling 15 digits. All digits have the range of 0 to 9 coded as binary coded decimal. Values outside this range are not permitted.
Some of the fields in the IMEI are under the control of the “Reporting Body”. The remainder is under the control of the Type Allocation Holder.
For the IMEI format prior to 01/01/03 please refer to Annex D of this document. The IMEI format valid from 01/01/03 is as shown below: TAC NNXXXXXX
The meaning of the acronyms for the IMEI format is: TAC NN XXXXXX ZZZZZZ A
Type Allocation Code Reporting Body Identifier ME Model Identifier defined by the Reporting Body The range is allocated by the Reporting Body but assigned per ME by the Type Allocation Holder Check digit, defined as a function of all other digits Serial No ZZZZZZ Check Digit A 5.1 IMEI Format
5.1.1 Type Allocation Code - 8 digits
The TAC identifies the type of the ME. It consists of two parts. The first part (NN) defines the Reporting Body allocating the TAC and the second part (XXXXXX) defines the ME Model. The following allocation principles apply:
Each ME Model SHALL have a unique TAC.
More than one TAC MAY be allocated to an ME Model. This may be done for instance to
permit the production of more than 1 million units. The TAC shall uniquely identify an ME Model.
Where there is more than one Type Allocation Holder for an ME Model then the TAC
shall be different.
5.1.2 Reporting Body Identifier (NN) – 2 digits
The first two digits of the TAC are the Reporting Body Identifier. These digits indicate which Reporting Body issued the IMEI. The GSMA shall coordinate the allocation of the first 2 digits to Reporting Bodies. See Annex A for IMEI Reporting Body Identifiers that have already been allocated. Only Reporting Body Identifiers listed in Annex A are valid The following allocation principles apply:
The GSMA shall coordinate the allocation of the Reporting Body Identifier. The Reporting Body Identifier shall uniquely identify the Reporting Body.
V7.0 Page 7 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
5.1.3 ME Model Identifier (XXXXXX) – 6 digits
The following 6 digits of the TAC are under the control of the Reporting Body. These 6 digits together with the Reporting Body 2 digit identifier uniquely identify each ME Model. Valid Range: 000000 – 999999
The following allocation principles apply:
Major changes to the ME Build Level shall require a new ME Model Identifier (TAC).
Major changes to ME Build Level would normally include changes that modify the way the ME Model performs on the mobile network. The Reporting Body shall determine what constitutes a major change to the ME Build Level in line with the guidelines in section 5
Terminals designed to comply with both 3GPP and 3GPP2 specifications are
considered as multi RAT / multi-mode ME, these devices must have a decimal IMEI to register on the 3GPP network, the 3GPP2 networks will also accept the decimal IMEI. All TAC allocated by all Reporting Bodies will work in multi RAT / multi-mode ME for both 3GPP and 3GPP2 networks.
Multi RAT / Multimode ME shall only have one TAC and therefore one IMEI therefore
they do not need an additional Mobile Equipment Identifier (MEID)
5.1.4 Serial Number (ZZZZZZ) - 6 digits
The Serial Number (SNR) is used to uniquely identify each individual ME of a particular ME Model. The number range is allocated by the Reporting Body but assigned to individual mobile stations by the manufacturer. Valid Range: 000000 – 999999
The following allocation principles apply.
Each ME of each ME Model must have a unique Serial Number for a given TAC code. In special circumstances (i.e. low volume product), the Reporting Body may allocate a
partial range to be used for the SNR.
5.1.5 Check Digit – 1 digit
The Check Digit shall be calculated according to Luhn formula (ISO/IEC 7812, see GSM 02.16 / 3GPP 22.016). The Check Digit is a function of all other digits in the IMEI. The Software Version Number (SVN) of a mobile is not included in the calculation.
The purpose of the Check Digit is to help guard against the possibility of incorrect entries to the CEIR and EIR equipment or for detecting mistakes in reading or manual transcription of the IMEI.
The presentation of the Check Digit both electronically (see section 5) and in printed form on the label and packaging is very important. Logistics (using bar-code reader) and EIR/CEIR administration cannot use the Check Digit unless it is printed outside of the packaging, and on the ME IMEI/Type Accreditation label.
5.2 IMEI Software Version Numbers (SVN) (2 digits)
The network can also request the IMEISV from ME. The SVN is described in 3GPP TS 22.016 and in TS GSM 02.16. A recommendation to terminal manufacturers is detailed in Annex C.
V7.0
Page 8 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
6 Benefits to the Industry of having an IMEI
IMEIs are used by Network Operators for the following:
Identify an individual mobile terminal to a GSM, UMTS or LTE network
Enable remote loading of patches and adaptations to avoid device inter-working
issues
Support configuration management and remote updating of the customer equipment
base
Aid marketing and sales strategies by allowing operators to identify specific devices
that can support value added services
Participate to the customer management for every aspect linked to the used terminal,
support of its contract, customer care, self-care, devices after sales.
Facilitate market research of the mobile user base by identifying and cross
referencing devices and usage patterns
Determine which devices are responsible for technical faults on the network and allow
for remedial action to be taken
Detect fraud at an early stage by using the IMEI to identify returning fraudsters’
and/or debtors’ devices
Prevent a stolen phone from accessing a network and being used
IMEIs can be used by device manufacturers for the following:
Restricting network access to devices with officially allocated TAC/IMEIs
Proving the authenticity of devices by customs agencies in some countries, e.g.
Turkey, India, etc.
Facilitating the identification of grey market handsets
Taking remedial action against devices that are stolen from manufacturing sites,
storage facilities or while in transit
Allocating test IMEIs allows manufacturers to test prototype devices on live networks
prior to market launch
Allowing operators to identify devices that may require software updates to be
performed in a targeted manner to fix identified device performance problems that could otherwise necessitate a product recall
IMEIs can be used by Regulators for the following:
• Allows exclusion of non-approved terminals, which is a license obligation in some
markets
• Identifies handsets for lawful interception and criminal prosecution
7 IMEI Security and Integrity Guidelines
The management of ME identities is achieved via the use of black, white and grey lists on the Equipment Identity Register (EIR) and the Central Equipment Identity Register (CEIR). The integrity of the IMEI is the critical factor in the viability of CEIR and EIR equipment and associated processes.
V7.0
Page 9 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
There are a number of guidelines that need to be adhered to if the IMEI is to be successfully implemented allowing the use of EIR and CEIR equipment. Failure to do so will in fact make it impossible to implement EIR and CEIR equipment effectively and remove the ability to identify equipment types and to take any appropriate action if required. It is in the interests of the whole GSM industry that the integrity of the IMEI is maintained. The following guidelines are applicable.
The IMEI shall uniquely identify each individual unit of ME
As per GSM 03.03 / 3GPP 23.003, GSM 02.03 / 3GPP TS 22.016, the IMEI shall not be
changed after it is programmed into the device. It shall resist tampering, i.e. manipulation and change, by any means (e.g. physical, electrical and software).
Where repairs necessitate the replacement of the components that contain the IMEI a
new IMEI shall be used. No means should be provided to replicate the IMEI in new
hardware or components. Therefore spare parts with IMEI hardware should be allocated a unique IMEI. When the IMEI have been replaced in this manner the recycling of the now disused IMEI is not permitted.
Where a ME has variants that operate in other bands/modes then the ME should be
constructed in such a way so that it is not possible to interchange components to permit the IMEI being swapped between the variants.
GSMA launched an initiative to fight mobile theft, and has worked on IMEI security best practice. GSMA members drafted and approved 2 documents:
Technical Principles: intended to strengthen the security of the International Mobile Equipment Identity (IMEI)
GSMA Doc Reference: Security Principles Related to Handset Theft
Process in place: GSMA and DIGITAL EUROPE have agreed on a process to report alleged breaches of IMEI integrity and on the introduction of counter-measures to correct and improve IMEI security.
GSMA Doc Reference: IMEI Weakness and Correction Process
8 TAC (IMEI) Usage Rules
The following guidelines are to be adhered to:
a) Modular Equipment may use an interchangeable transceiver module to achieve
the ability to operate in alternative GSM bands. Such equipment is to treat each transceiver module as a separate ME. This will mean that each transceiver equipment module would be subject to Type Allocation and be allocated a separate IMEI/TAC. The IMEI shall not be duplicated in separate transceiver equipment.
b) The GSMA has the following policy regarding devices containing multiple
transceivers:
V7.0
Page 10 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
If a device contains two or more transceivers, each transceiver needs to be
separately identified on networks.
If two or more transceivers within the device are identical (e.g. same chipset, same
frequency bands), then each transceiver can use the same TAC, but different IMEI. If the transceivers are different (e.g. different chipset, different frequency bands), then
the transceivers have different TACs.
A single transceiver may have more than one (U) SIM. If only one (U)SIM can
connect to the network at any time then only one IMEI is required.
c) All TAC (IMEI) numbers allocated by the Reporting Bodies are stored in the
GSMA IMEI database. The database is used to populate the Central Equipment Identity Register (CEIR) which is used by the GSM Network Operators. For confidentiality reasons, access to the IMEI database is restricted. A company registered in the IMEI database can request a list of those TAC (IMEI) numbers allocated to them. Network Operators can access the IMEI data for the purposes of monitoring IMEI numbers on their networks.
d) Before applying for a TAC (IMEI) number, the applicant company must first be
registered with a reporting body. Evidence must be provided with (or in addition to) the application to ensure the following: That the applicant (i.e. Brand Owner) is a legitimate organization and is selling a
product that is to connect to the Telecoms Network,
For Modem manufacturers, it should be the manufacturer who requests the TAC as
these may go into many different devices. In all other cases it should be the Brand Owner who requests the TAC.
e) The following Equipment Types are listed on the TAC application form:- Mobile / Feature Phone:
o Description - A device supporting basic personal communication services,
e.g. voice call and SMS. (Not strictly limited to basic services, but not entering in the definition of a Smartphone).
Smartphone:
o Description – A device with large display, predominantly with touch screen
technology, fast processor and memory in the GB range. A fully-featured OS / platform that provides voice and data communications capabilities, enables personalisation of the device by the user and in addition supports installation and maintenance of mobile applications (e.g. downloadable from an Application store).
Tablet:
o Description - A device with a display minimum 5-inches, slate-type form
factor, touch screen, providing data communications and/or voice
capabilities, fully-featured OS providing connection to an Application store through which the user can personalise the device’s functionality and services
V7.0
Page 11 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
e-Book:
Description - Similar to a tablet, but prime function is digital book
storage / reading; typically outdoor-capable display, less capable OS/applications than a tablet.
Connected Computer
o Description - Laptop / Netbook / Desktop PC with integrated cellular
network connectivity module.
Dongle:
o Description - A device which can be inserted in a laptop or other computer
to provide cellular network connectivity
Modem:
o Description - A device designed for embedding in other equipment to
provide cellular connection functionality
WLAN Router:
o Description - A device that performs advanced routing functionalities and
uses the cellular network as Wide Area Network interface.
f) If the Equipment Type is listed on the TAC form as “Dongle” or “WLAN Router”
then the device will not have a relevant operating system so it is acceptable to tick the box for “Operating System” as “Other” and then put “None” in the text box.
g) If the Equipment Type is listed on the TAC form as “Modem” then the device
operating system may not be known so it acceptable to tick the box for “Operating System” as “Other” and then put “Not known” in the text box.
h) Each application is made on a per model basis. The Brand Name, Model Name &
Marketing Name need to be provided to identify the model.
i) The number of TAC numbers requested per application is enough to cover a three
month production run. One TAC number (1 million IMEI numbers) is normally more than sufficient in most applications.
j) Any amendment to an existing TAC record must be made via the GSMA IMEI
data base using the “Edit TAC” function.
k) Some manufacturers produce special test mobile equipment. This type of
equipment can harm network integrity if used in the wrong manner. Subsequently network operators need to be able to identify such equipment. The following guidelines apply.
Where the equipment is based on an existing Mobile Equipment:
A separate TAC code should be assigned to the Test ME to distinguish it from the
Type Accredited mobile equipment.
Alternatively a Test IMEI could be allocated to this type of ME if it is supplied to
operators for test purposes only and not available commercially.
V7.0
Page 12 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
Each Test ME’s IMEI shall conform to the IMEI Integrity and Security provisions in
Section 3.
l) Where GSM equipment is capable of operating in multiple modes the following
guidelines apply. The Reporting Body shall inform the GSM Association of the Multimode capability for
the ME and indicate the capable modes.
Where the standards permit the same IMEI shall be used for each mode of operation.
Where the standards do not permit the use of IMEI then an IMEI shall be allocated specifically to the GSM part and any applicable identification to the non-GSM part/s. Where physically detachable modular techniques are utilised to provide the
transceiver capability then each transceiver module shall be treated as a separate ME. Therefore separate IMEI/TAC allocations are required if an IMEI is applicable to each module.
m) Cosmetic variants of the same model. If different models of the same devices
meet all of the following criteria then the same TAC can be used for all the models:-
The same hardware design The same transceiver
The same control software having an impact on the interworking with the network, The same frequency bands
It is manufactured, assembled, commissioned by the same ME Owner
Example: a cosmetic terminal variation which is a different colour or name.
9 Test IMEI
From time to time manufacturers may wish to test prototype ME on networks before applying the regulatory procedures for placing the equipment on the market. The Test IMEI principle has been developed to allow easy allocation of IMEI to Test ME in a controllable, secure and traceable manner. The use of IMEI from Type Allocated Equipment in Test ME is strictly prohibited.
The purpose of the Test IMEI is to allow manufacturers to test prototype mobiles on a live network without having placed mobiles on the market (i.e. the mobiles are fully under the control of the manufacturer or an operator). They may be single prototype units or a limited pre-production run (e.g. to demonstrate a mobile at an exhibition or do some field trials). Test IMEIs are allocated as an 8 digit TAC code per manufacturer and uniquely identifies the manufacturer. The IMEI range implicated by the allocated Test-TAC is to be managed by the manufacturer (It is expected that the manufacturer can control the reuse of Test-IMEIs, e.g. by internal quality procedures.). It is prohibited to have identical IMEI in use in more than one piece of equipment at any given time. Test-IMEIs must not be used for samples given to operators for final product acceptance.
The total allocation of Test IMEI is one million per manufacturer. The total number of a particular model type of mobiles that can be used under this arrangement is a maximum of 1000. Old test products must be destroyed and the Test IMEI numbers must be reused.
V7.0 Page 13 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
The test IMEI allocation does not imply general permission to connect or imply approval for Test UEs. Operators are under no obligation to allow the use of test IMEI on their networks. One should normally need to seek permission from the network operator to use the Test IMEIs on their network. If a network operator queries the use of a Test IMEI issued by BABT, BABT will provide the operator with the details of the allocation, including the manufacturer's name and address. Only the Reporting Bodies listed in Annex B may allocate a Test IMEI. The use of a Test ME is subject to any applicable national legislation and regulatory requirements. In general it is subject to the agreement of the network operator and, where applicable, of the Reporting Body. A Reporting Body or operator may allow the use of a limited number of Test ME and may impose regional restrictions.
The following guidelines apply to test mobile IMEIs.
Operators are under no compulsion to allow the use of Test IMEI on their networks
and may if they wish black list all or some Test IMEI.
A Test IMEI is used for Mobile Equipment or software functionality that has not been
through the (regulatory) procedures for placing commercial equipment on the market. ME with Test IMEI cannot be supplied to the market. A Test IMEI range is available initially for a block of 1000 mobiles per model type. If more than 1000 Test IMEIs are required then more than one Test ME Model shall be allocated so that there are sequential blocks of 1000. The total Test IMEI allocation shall be a multiple of 1000. Old test products must be destroyed and the Test IMEI numbers must be reused Test IMEI shall not be duplicated.
The TAC component of the Test IMEI shall indicate the Allocating Body.
If it accepts the mobile in its country/network, a Reporting Body or operator should
accept the use of a range of Test IMEI numbers that have been allocated by another Allocating Body. The allocation of different Test IMEI ranges for the same type of ME should be avoided if at all possible.
From 01/02/2005 a new format as described in table 6.2.1 will apply to test IMEIs for
all countries except North America.
9.1 Format of the Test IMEI for all countries except North America
TAC 8 digits 00 44 MMMM To identify To Identify Manufacturer Code Test ME BABT as allocating body Notes :- MMMM - Identifies the manufacturer. Multiple codes may be allocated per manufacturer, at the discretion of the allocating body, but each code is unique to a single manufacturer. ZZZZZZ - Represents the serial number selected by the manufacturer.
SN 6 digits ZZZZZZ Serial number 9.2 Format of the Test IMEI for North America
TAC V7.0
SN Page 14 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
8 digits 001 WWW XX To identify Test ME Notes:- 6 digits YYY ZZZ Serial number Reserved for Test ME Model future use, fixed to “00” WWW - Identifies the Allocating Body using the MNC. 000 is the GSM NA XX - Is reserved for future use and fixed to “00” YYY - Represents a number chosen by the Allocating Body for the test ME Model. ZZZ - Represents the serial number selected by the manufacturer.
10 Reporting Body Identifier List
The GSMA maintains a list of all Reporting Bodies and their Reporting Body Identifier. This list is available as Annex A to this document.
11 Test IMEI Allocating Body List
The GSM Association maintains a list of contacts for the issuing of Test IMEI. This list is available as Annex B to this document.
12 List of Type allocated mobile equipment and IMEI allocations by
Reporting Bodies
The Reporting Bodies use the GSMA Web based IMEI database for allocating the TAC which in turn provides the information to the mobile network operators to allow the connection of devices to their networks.
13 The IMEI Database / CEIR
The GSMA operate the IMEI database which is also the Central Equipment Identity Register (CEIR) for use by its operator members. The CEIR contain White List Information of Mobile Equipment determined as suitable for worldwide use on mobile networks. It may also contain Black List information of the IMEI of MEs that are considered not suitable for use on mobile networks due to being stolen, duplicated, a threat to network integrity or other reasons. The GSMA shall determine valid reasons for blacklisting. The CEIR may also contain GREY list information about IMEIs of ME whose status is unclear.
The GSMA reserves the right to determine if the technical basis for Type Allocation is acceptable to permit IMEIs allocated by a Reporting Body to be included in the CEIR white list.
The GSMA reserves the right to determine if information supplied by a Reporting Body is acceptable for inclusion in the CEIR white list.
Individual members of the GSMA may choose what IMEI information to enter to their own EIR. This may include IMEI information excluded from entry to the CEIR in the White, Black or Grey lists.
V7.0 Page 15 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
The GSMA shall enter Test IMEI allocations to the CEIR. It is the responsibility of individual GSMA members to enter Test IMEI into their EIR.
14 GSMA Responsibilities
Within the context of this document the GSMA shall have the following responsibilities.
Appointment of Reporting Bodies
Coordinate the allocation of the Reporting Body Identifier.
Maintain a list of Type Allocated GSM Mobile Equipment and IMEI allocations by
Reporting Bodies containing details of TAC manufacturers, models and band/mode capability for all IMEIs allocated by Reporting Bodies.
Ensure integrity of CEIR white, black and grey list information and update white list
with new IMEI allocations according to the conditions of section 10. Ensure integrity of CEIR process.
Maintain a list of contacts for issuing Test IMEI.
Document and maintain the procedures to be followed by Reporting Bodies for
notification of allocated IMEI.
Provide expertise and advice on Allocation and IMEI issues where appropriate.
15 Reporting Body Responsibilities
Within the context of this document the Reporting Bodies shall have the following responsibilities with respect to IMEI and Type Allocation:
Ensure that the requirements for Type Allocation as outlined in section 8.0 are satisfied. Allocate IMEI TAC codes for mobile equipment within their jurisdiction as required.
Allocation of a specific Serial Number Range is optional..
Coordinate with other Reporting Bodies where the equipment requiring Type Allocation is
under the jurisdiction of more than one Reporting Body.
Reporting Bodies must allocate the TAC from within the GSMA IMEI database, however
if this is not possible then they must inform the GSMA of new Type Allocations and IMEI allocations providing the following information
TAC & Serial number range (if allocated)
Brand Name, Marketing Name and Model Name Manufacturer
Frequency Bands supported by the devices Designation Type Allocation Date Radio Interface Operating System Support for NFC (Y/N)
Support for Bluetooth (Y/N) Support for WLAN (Y/N)
Any additional information to the Type Allocation status.
V7.0
Page 16 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
If this information is not already in the GSMA IMEI database then it must be provided to the GSMA soon as possible after granting TAC to avoid delays in connecting the equipment to networks using an Excel template supplied by the GSMA by contacting imeihelpdesk@gsma.com
16 Type Allocation Holder Responsibilities
Within the context of this document Type Allocation Holders have the following responsibilities.
Comply with the relevant Type Allocation requirements.
Complete all information requested in the GSMA IMEI database with regards to company
registration and TAC requests.
Ensure IMEI are secure and have integrity.
Consider recommendations to increment SVN for new software in ME. Apply to relevant bodies for Test IMEI when required.
Gain permission from operators to use test ME where required.
17 TAC Allocation Process
To obtain the TAC the following steps should be followed:-
1. The Type Allocation Holder must be register in the GSMA IMEI Database, via the
following link: http://imeidb.gsm.org/imei/login.jsp and then click on “Manufacturers Registration Form”
2. Complete all the details & submit the registration form
Once submitted, the form is sent via the IMEI Database to the appropriate Reporting Body (RB) for processing. The RB may contact the manufacturer for more information. When the RB has completed their verification of the form, if positive, the application will be approved and the manufacturer will be sent a Manufacturer ID & Password via email. In the event of a negative review the RB will contact the Type Allocation Holder to explain the reasons for rejection of the application.
1. When the Type Allocation Holder has a Manufacturer ID & Password they are able to
enter the IMEI Database via this link:- http://imeidb.gsm.org/imei/login.jsp and click on “Application for TAC” and enter the Manufacturer ID & Password details
2. The Type Allocation Holder must pay the Fees if required, in order to obtain the TAC
Allowance. Once the payment is made the Type Allocation Holders will have a TAC Allowance available for Allocation to ME Models.
3. The TAC Allowance does not expire and can be allocated at any time.
4. In order to use the allowance and initiate the TAC Allocation complete the TAC
application form as required in the IMEI Database. This form is then sent via the IMEI Database to the RB for confirmation of the ME Model Specification and the specific TAC allocated.
5. When the TAC is allocated to a specific ME Model the Type Allocation Holder will be
sent a notification email & a TAC certificate issued by the GSMA.
6. The remaining TAC from the Allowance can be allocated to ME Models as required
by repeating from step No 5 above.
V7.0 Page 17 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
7. If more TAC than the TAC Allowance are required the Type Allocation Holder must
repeat the process from step No 4 above.
V7.0 Page 18 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
Annex A – Reporting Body Identifier List
.
Note: Global Decimal Administrator (GDA) multi RAT 3GPP2/3GPP mobile assignments are allocated from within the individual IMEI Reporting Body Identifier allocation space. Global Hexadecimal Administrator (GHA) multi RAT 3GPP2/3GPP mobiles are allocated starting from the Reporting Body Identifier 99 allocation space.
Reporting Body Identifier 00 Reporting Body or allocated Use Bands/Modes Contact Details Test ME (allocated by countries with a 1 or 2 All digit international dialling prefix) CTIA See Test IMEI Issuer List (Annex B) Mr. Will Lightfoot CTIA – The Wireless Association® 1400 16th Street, NW Suite 600 Washington, DC 20036 www.ctia.org/certification Direct: +1 202 736 3208 Main: +1 202 785 0081 Wireless: +1 202 213 5010 Fax: +1 202 736 1629 CTIA - IMEI IMEI@ctia.org 01
V7.0
Page 19 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
Reporting Body Identifier 35 Reporting Body or allocated Use Bands/Modes Contact Details TUV SUD BABT All Mr John Talbot Tel. +44 1932 251264 Fax: +44 1932 251201 E-mail: John.Talbot@tuv-sud.co.uk Mr Les Rowland Tel. +44 1932 251254 Fax: +44 1932 251201 E-mail: Les.Rowland@tuv-sud.co.uk E-mail: imei@babt.com V7.0 Page 20 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
Reporting Body Identifier 86 Reporting Body or allocated Use Bands/Modes Contact Details TAF (China) Telecommunication Approval Forum All Terminal Testing & Mr. Meng Xiangdong Tel: +86 10 82052809 Fax: +86 10 82053375 E-mail:mengxiangdong@catr.cn Ms. Su Hui Tel: +86 10 82052809 Fax: +86 10 82053375 E-mail: suhui@tenaa.com.cn 91 AB Mobile Standards Alliance India Pvt Ltd All (MSAI) Mr. Ashwani Budhiraja Tel: +91 981 802 0309 Tel: +91 958 279 7972 Mr. Ashok Budhiraja Tel: +91 981 802 0399 Tel: +91 958 279 7973 Ms Bhawna Kumari Tel: +91 958 279 7991 E-mail: Ashwani@msai.in E-mail: Bhawna@msai.in E-mail: Ashok@msai.in E-mail: ineedimei@msai.in V7.0 Page 21 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
Reporting Body Identifier 98 Reporting Body or allocated Use Bands/Modes Contact Details Reserved for Future Use Note: a few TAC codes had previously been assigned from this block 98000100 to 98007800 99 Global Hexadecimal Administrator (GHA) All John Derr TIA 2500 Wilson Blv., Suite 300 Arlington, VA 22201 USA E-mail: meidadmin@tiaonline.org Table 1: Bodies currently authorised to allocate IMEIs:
V7.0 Page 22 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
Reporting Body Identifier 10 30 33 44 45 49 50 51 52 53 54 Reporting Body or allocated Use Bands/Modes DECT PP with GSM functionality Iridium DGPT / ART DECT GSM Satellite 900/1800 900/1800 900/1800 900/1800 900/1800 900/1800 900/1800 900/1800 900/1800 BABT NTA BZT/BAPT/Reg TP BZT ETS Certification GmbH. Cetecom ICT Services GmbH CETECOM GmbH TUV Product Service GmbH (Munich) PHOENIX TEST-LAB GmbH Table 2: Bodies that no Longer Allocate IMEIs:
V7.0 Page 23 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
Annex B – List of Test IMEI allocating bodies:
1st 6 digits of the Test IMEI 001 001-001 017 00 44 MMMM ALLOCATING BODY Contact Person(s) Telephone Fax E-mail GSM CTIA North America, Mr. Will Lightfoot +1 202 736 3208 +1 202 736 1629 Wlightfoot@ctia.org IMEI@ctia.org Mr. John Talbot TUV SUD BABT +44 1932 251264 +44 1932 251201 John.Talbot@tuv-sud.co.uk Les.Rowland@tuv-sud.co.uk Mr. Les Rowland +44 1932 251254 imei@babt.com Mr. Meng Xiangdong Ms. Su Hui 00 86 MMMM TAF (China) +86 10 82052809 +86 10 82053375 mengxiangdong@catr.cn +86 10 82052809 +86 10 82051448 suhui@tenaa.com.cn 00 91 MMMM MSAI (India) Mr. Ashok Budhiraja +91 981 802 0399 +91 114 508 3259 ineedimei@msai.in V7.0 Page 24 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
Annex C – Informative Annex - IMEISV
The Network can also request the IMEISV from Phase 2 (or later) ME. The IMEISV shall contain the first 14 digits of the IMEI plus a Software Version Number (SVN). The SVN shall be incremented when the ME software is modified. Allocation of the 2 digit SVN may be controlled by the Reporting Body, at the discretion of the Reporting Body. SVN of “99” is reserved for future use (See GSM 03.03).
C.1 GSM 02.16 - MS Software Version Number (SVN)
A Software Version Number (SVN) field shall be provided. This allows the ME manufacturer to identify different software versions of a given type approved mobile.
The SVN is a separate field from the IMEI, although it is associated with the IMEI, and when the network requests the IMEI from the MS, the SVN (if present) is also sent towards the network. It comprises 2 decimal digits.
The White list shall use the IMEI, while the Black and Grey Lists may also use the SVN.
C.2 3GPP TS 22.016 - MS Software Version Number (SVN)
A Software Version Number (SVN) field shall be provided. This allows the ME manufacturer to identify different software versions of a given mobile.
The SVN is a separate field from the IMEI, although it is associated with the IMEI, and when the network requests the IMEI from the MS, the SVN (if present) is also sent towards the network.
The White list shall use the IMEI, while the Black and Grey Lists may also use the SVN.
C.3 Structure of the IMEISV
The structure of the IMEISV is as follows: TAC NNXXXXXX Notes:- NN Reporting Body Identifier ME Model Identifier defined by Reporting Body Allocated by Reporting Body but assigned per ME by the manufacturer Software Version Number 00 – 98. 99 is reserved for future use. XXXXXX ZZZZZZ SS
Serial No ZZZZZZ SVN SS Page 25 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
C.4 Software Version Number Allocation Principles
The Reporting Body, at their discretion, may control allocation of the SVN. All ME designed to Phase 2 or later requirements shall increment the SVN for new versions of software. The initial version number shall be 00. The SVN of 99 shall be reserved.
The allocation process for SVN shall be one of the following procedures:
The Reporting Body allocates a new SVN number a new software release. The Reporting Body defines the allocating process to be applied by the Type
Allocation Holder.
If there are more than 99 software versions released the Reporting Body may undertake one of the following options.
Issue a new TAC code for the ME Model
C.5 Security Requirements
The SVN is not subject to the same security requirements as the IMEI as it is associated with the ME software. The SVN should be contained within the software and incremented every time new software is commercially released. The SVN should uniquely identify the software version.
Page 26 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
Annex D – Informative Annex – Historical Structure of the IMEI
D.1
TAC NNXXXX
Discussions within the industry, including 3GPP2, agreed that the structure change to combine the TAC and FAC into a single eight-digit TAC code.
This format has been documented in the 3GPP requirements 02.16, 03.03, 22.016 and 23.003.
Effectively the FAC code should be considered as obsolete.
It was noted that there was a need for a transition period to allow:
The Operators to modify their systems to use the eight digit TAC rather than a six digit
one
The Manufacturers to make any necessary changes to their production processes The Reporting Bodies to make any changes to their IMEI allocation systems The GSM Association to make any changes to their databases and systems The Contractor to make any changes to its systems The transition period ran from 31/12/02 until 1/4/04.
To achieve this transition, all eight-digit TAC codes allocated between 31/12/02 and 31/3/04 were given unique combinations of the first six digits (NNXXXX) with the seventh and eighth digits (YY) being fixed to 00.
Any request by a Terminal Manufacturer for a FAC code after 31/12/02 resulted in that Manufacturer being supplied with a fresh 8 digit TAC. This was to allow the 3GPP industry to move to the 8-digit TAC code without the need to implement changes to their IMEI analysis and tracking systems before 1/4/04.
Historical IMEI Structure
The IMEI structure valid until 31/12/02 is as follows
FAC YY Serial No ZZZZZZ Check Digit A The meaning of the acronyms for the IMEI format valid until 31/12/02 is: TAC NN XXXX FAC YY Type Allocation Code, formerly known as Type Approval Code Reporting Body Identifier ME Type Identifier defined by Reporting Body Final Assembly Code Under control of the Reporting Body. May be used to indicate the manufacturing site. More than one FAC per site should be used to permit production of greater than 1000000 ME. Allocated by Reporting Body but assigned per ME by the manufacturer Page 27 of 32
ZZZZZZ
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
A Phase 1 = 0 Phase 2 (or later) = Check digit, defined as a function of all other IMEI digits
D.1.1 Type Allocation Code - 6 digits. (Valid prior to 01/01/03)
The TAC identifies the Type Allocation Code, formerly known as the Type Approval Code, for the type of the ME. It consists of two parts; the first part defines the Reporting Body allocating the TAC and the second part defines the ME type. The following allocation principles apply:
Each ME Type shall have a unique TAC code or set of TAC codes.
More than one TAC may be allocated to an ME Type at the discretion of the Reporting
Body. This may be done to permit the production of more than 1 million units or to distinguish between market variations.
The TAC code shall uniquely identify an ME Type.
If the TAC was granted to a particular software version of one ME Type that is then used
in another ME type the TAC code shall be different.
TAC codes may vary between software versions for a phase 1 ME Type at the discretion
of the Reporting Body.
In Phase 2 (and later releases) the TAC shall remain the same and the SV number shall
identify the software version. See IMEISV.
Where there is more than one Type Allocation Holder for an ME Type then the TAC code
shall be different.
D.1.2 Reporting Body Identifier (NN) – 2 digits (valid prior to 01/01/03)
The first two digits of the TAC are the Reporting Body Identifier. These digits indicate which Reporting Body issued the IMEI. The GSM Association shall coordinate the allocation of the first 2 digits to Reporting Bodies. See Annex A for IMEI Reporting Body Identifiers that have already been allocated.
Valid Range 00 – 99 in accordance with allocations in Annex A
The following allocation principles apply:
The GSM Association shall coordinate the allocation of the Reporting Body Identifier. The Reporting Body Identifier shall uniquely identify the Reporting Body.
If for some reason the same Reporting Body Identifier must be used then the first digit of
the ME Type Identifier will also be used to define the Reporting Body. The GSM
Association shall coordinate the allocation to the Reporting Body of the range of values of the first digit of the ME Type Identifier. This range shall be contiguous. This approach is to be avoided if at all possible.
Page 28 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
D.1.3 ME Type Identifier (XXXX) – 4 digits (valid prior to 01/01/03)
The following 4 digits of the TAC are under the control of the Reporting Body. These 4 digits together with the Reporting Body 2 digit identifier uniquely identify each ME Type. Valid Range 0000 – 9999
The following allocation principles apply:
Every ME Type shall have a unique TAC or set of TACs. A TAC may not be associated
with more than one ME Type. An ME Type may have more than one TAC.
Major changes to the ME Build Level shall require a new ME Type Identifier. Major
changes to ME Build Level would normally include the addition of new features or changes that modify the performance of the ME Type. Minor changes to the ME Build Level that do not change the performance of the ME require no new ME Type Identifier. The Reporting Body shall determine what constitutes a major or minor change to the ME Build Level.
The ME Type Identifier should be allocated sequentially wherever possible. Gaps in the
ME type range are to be avoided if possible.
Multiband or multimode ME shall only have one TAC and therefore one IMEI. Where
more than one Reporting Body is involved in the allocation of the IMEI coordination is required between the Reporting Bodies to ensure that all requirements have been met before the IMEI is allocated.
D.1.4 Final Assembly Code (FAC) - 2 digits (valid prior to 01/01/03)
These two digits (YY) are generally used to identify the specific factory or manufacturing site of the ME. The allocation of the FAC is under the control of the Reporting Body. Valid Range 00 – 99
The following allocation principles apply:
More than one FAC should be allocated where necessary to a Factory or site to allow for
the situation where the factory produces more than 1 million units per ME Type.
Further FACs should be requested and assigned for a ME type where the Serial Number
Range is exhausted.
A FAC shall not be used to distinguish between ME Types.
D.1.5 Serial Number (SNR) - 6 digits (valid prior to 01/01/03)
The 6 digit SNR (ZZZZZZ) in combination with the FAC is used to uniquely identify each ME of a particular ME Type. Valid Range 000000 – 999999
The following allocation principles apply:
Each ME of each ME Type must have a unique Serial Number in combination with the
FAC for a given TAC code.
SNR shall be allocated sequentially wherever possible.
The Reporting Body may allocate a partial range to be used for the serial number.
Page 29 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
D.1.6 Spare Digit / Check Digit – 1 digit (valid prior to 01/01/03)
D.1.6.1 Phase 1/1+ ME
For Phase 1 ME this is a spare digit and its use has not been defined. The spare digit shall always be transmitted to the network as “0”.
D.1.6.2 Phase 2 (and later) ME
For Phase 2 (or later) mobiles it shall be a Check Digit calculated according to Luhn formula (ISO/IEC 7812). See GSM 02.16. The Check Digit shall not be transmitted to the network. The Check Digit is a function of all other digits in the IMEI. The Software Version Number (SVN) of a Phase 2 (or later) mobile is not included in the calculation.
The purpose of the Check Digit is to help guard against the possibility of incorrect entries to the CEIR and EIR equipment.
The presentation of Check Digit (CD) both electronically (see Section 5) and in printed form on the label and packaging is very important. Logistics (using bar-code reader) and EIR/CEIR administration cannot use the CD unless it is printed outside of the packaging, and on the ME IMEI/Type Accreditation label.
The check digit shall always be transmitted to the network as “0”.
Page 30 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
Document Management
Document History Version Date 3.1.0 3.1.1 3.1.2 3.1.3 3.1.4 3.1.8 3.1.9 3.1.10 3.2.0 04/04/1998 18/06/1998 04/08/1998 August 1998 March 1999 April 2000 May 2000 October 2000 September 2002 December 2004 Brief Description of Change Approval Authority Editor Company / Clarifications and terminology changes as approved at MoU#39 Update to Annex A and B Update to Annex A and B Document Classification Scheme NS CR Fast Track Procedure Update to Annex A and B Update to Annex A Update to take account of R&TTE Directive Update to take account of JEM Meeting output and changes to the core specifications. Update to take account of changes to Test IMEI allocation and updates for revised TAC format, and Update of Test IMEI procedure, IMEI security, IMEI SV 3.3.0 3.3 6 January Updated format and version 2006 number to current methods, re-designated control number from TW.06 to DG.06 consistent with group name. 1 March Note about UMA terminal added 2007 to Section 1 ME Type 1 November 2007 TD-SCDMA requirements added. allocation 3.4 3.5 3.6 7 February The Test IMEI format description 2008 was corrected in the table in Annex B 8 December 2008 th 3.7 TD-SCDMA updated. allocation details Page 31 of 32
GSM Association
Official Document – TS.06 IMEI Allocation and Approval Process
Non-confidential
Version Date 4.0 October 2009 Brief Description of Change Re-writing of Document. Approval Authority DG#22 EMC# at Editor Company / Les Roland / BABT 5.0 15 Sept CR005 2010 References’ added to 3GPP2 & Approved EMC#86 GHA. Corrections to the “Check Sum” reference 02 Dec Document number changed from 2010 DG06 to TS06 Document owner changed from DG to TSG Paul Gosden / GSMA 5.1 TSG 01 Paul Gosden / GSMA 6.0 7.0 27 July CR0007 (TSG04_003r1) 2011 31 October 2013 stthTSG04 / DAG 83 / Paul Gosden / EMC 95 GSMA Updated in line with the new TAC application form and brought in TSG / DAG / Paul Gosden / line with current industry PSMC GSMA requirements
Other Information Type Document Owner Editor / Company Description Terminal Steering Group (TSG) Paul Gosden GSMA Contact information:- IMEI Helpdesk imeihelpdesk@gsma.com GSMA IMEI Database Phone: +91-9966526555, +91-877-6456669 Database - http://imeidb.gsm.org/imei/login.jsp Feedback
This document is intended for use by the members of GSMA. It is our intention to provide a quality product for your use. If you find any errors or omissions, please contact us with your comments. You may notify us at mailto:prd@gsma.com. Your comments or suggestions are always welcome.
Page 32 of 32
因篇幅问题不能全部显示，请点此查看更多更全内容