Numbering Resources
Electronic Serial Numbers (ESN)
An electronic serial number (ESN) is the unique identification number embedded or inscribed on the microchip in a wireless phone by the manufacturer. The ESN cannot easily be altered in the field. The ESN differs from the mobile identification number (MIN), which is the wireless carrier's identifier for a phone in the network. MINs and ESNs can be electronically checked to help prevent fraud. ESN has been migrated to MEID with the first MEID range allocated January 9, 2006. ESN Guidelines and ESN issues are still supported by the TIA ESN Administrator. The last date for receipt of a new ESN MFR Code block request was June 30, 2010.
ESN
An electronic serial number (ESN) is the unique identification number embedded or inscribed on the microchip in a wireless phone by the manufacturer. The ESN cannot easily be altered in the field. The ESN differs from the mobile identification number (MIN), which is the wireless carrier's identifier for a phone in the network. MINs and ESNs can be electronically checked to help prevent fraud.
How is TIA involved?
TIA took over the ESN function from the Federal Communications Commission's (FCC) Wireless Telecommunications Bureau in September 1997. ESN has been migrated to MEID with the first MEID range allocated January 9, 2006. ESN and UM_ID guidelines and issues are still supported by the TIA as the sole global ESN and UM_ID administrator. The last date for receipt of a new ESN MFR Code block request was June 30, 2010.
Contact: John Derr and Cathy Wang of TIA, at jderr@tiaonline.org and ywang@tiaonline.org.
ESN Application and Modification
ESN Assignment Guidelines and Procedures (33 pages, 195k) (includes all forms A through G). ESN Manufacturers Code Assignment Guidelines and Procedures establishes that currently, June 30, 2010 (originally, December 31,2009 ) is the last date for receipt of an ESN MFR Code block request.
Industry Correspondence Related to Migration from ESN and UIM_ID to MEID and E-UM_ID
- TIA Reminder to ESN and UM_ID Assignees on 30 June 2010 Application Deadline
- TIA White Paper on the Exhaust of Electronic Serial Numbers (ESNs) and Migration to Mobile Equipment Identifiers (MEIDs) (November 2007; 6 pages; 70KB)
- TIA Numbering Administrator Correspondence to Assignees of ESN, MEID and UIM_ID Regarding UIM_ID Proposal Request (October 7, 2009; 2 pages; 57K)
- TR-45 Committee Correspondence to 3GPP2 TSG Chairs Regarding UIM_ID Proposal Request (September 2, 2009; 2 pages; 63K)
- TR-45 Committee Correspondence to CDG Regarding UIM_ID Proposal Request (September 2, 2009; 2 pages; 68K)
- TR-45 Letter to Industry Regarding UIM_ID Assignment Status Advisory (April 24, 2009; 3 pages; 143K)
- ESN Reissue/Reclamation December 2003 Letter Sent to Manufacturer's w/ID Codes 129-254 (Baseline Text; 2 pages, 52K)
- First Industry Outreach Letter Sent December 18, 2003 & January 7, 2004 (One Sample of 17 letters; 2 pages, 35K)
- Follow-Up Outreach Letter Sent to CTIA on March 9, 2004 (3 pages, 39K)
- White Paper on Pseudo-ESN Collisions (May 26, 2005, 14 pages, 139K)
UIM_ID: - UIM (User Identity Module) and E-UIM (Expanded User Identity Module used in R-UIM (Removable User Identity Module) Cards
The UIM_ID is a 32-bit identification number for the Removable User Identity Module card (R-UIM). Each UIM_ID is meant to be unique, i.e., different from any other assigned UIM_ID and Electronic Serial Number (ESN). The UIM_ID shares the same numbering space with the ESN.
The expanded R-UIM identifier (E-UIM_ID) addressed the exhaustion of the existing 32-bit UIM_ID/ESN numbering space.
- For more information on UIM_ID Assignment Guidelines and Procedures, please refer to User Identification Module ID Manufacturer's Code Assignment Guidelines and Procedures (3GPP2 SC.R4004-0, Version 2.0 - May, 2010; 32 pages, 184K)
- For more information on E-UIM_ID Numbering Administration Procedures, please refer to Expanded R-UIM Numbering Administrative Procedures (3GPP2 SC.R4003-0, Version 1.0-May 2007; 9 pages, 155K).
Mobile Equipment IDentifiers (MEID)
A Mobile Equipment IDentifier (MEID) is a globally unique 56-bit identification number for a physical piece of mobile station equipment. Equipment identifiers are "burned" into a device and should be resistant to modification. They are used as a means to facilitate mobile equipment identification and tracking. Additionally, MEIDs are coordinated with International Mobile Equipment Identifiers (IMEIs), facilitating global roaming and harmonization between 3G technologies as a universal mobile equipment identifier.
If you are interested in applying for MEIDs, please GO TO MEID NUMBER APPLICATION FORM
A Mobile Equipment IDentifier (MEID) is a globally unique 56-bit identification number for a physical piece of mobile station equipment. Equipment identifiers are "burned" into a device and should be resistant to modification. They are used as a means to facilitate mobile equipment identification and tracking. Additionally, MEID multimode assignments are coordinated with International Mobile Equipment Identifiers (IMEIs), facilitating global roaming and harmonization between 3G/4G/5G technologies as a universal mobile equipment identifier.
The MEID is a 14-digit hexadecimal value. The MEID is capable of being transmitted over the air upon a request from the network. The MEID is composed mainly of two basic components, the manufacturer code and the serial number, as follows:
All of these fields are defined as hexadecimal values with the following valid range.
- RR - valid range A0 . FF - globally administered
- XXXXXX - valid range 000000. FFFFFF
- ZZZZZZ - valid range 000000. FFFFFF
- C - valid range 0. F - Not transmitted over the air.
In the case of MEIDs for terminals designed to comply with both 3GPP and 3GPP2 specifications (i.e., multimode terminals), all these fields are defined as decimal values with the following valid range:
- RR - valid range '99', '98', '97'. - globally administered
- XXXXXX - valid range 000000. 999999
- ZZZZZZ - valid range 000000. 999999
- C - valid range 0 . 9 - Not transmitted over the air.
How is TIA involved?
TIA serves as the Global Hexadecimal Administrator (GHA) to assign MEID manufacturer codes. TIA is the sole global administrator with authority to assign a Hexadecimal MEID. TIA also coordinates with the International Mobile Equipment Identifier (IMEI) Global Decimal Administrator (GDA), the GSM Association, to administer Decimal IMEI/MEID codes for multi-mode equipment. The TIA Committee TR-45 ESN/UIM/MEID Ad Hoc, in cooperation with 3GPP2, successfully worked with industry to assist the smooth transition from ESN to MEID.
MEID Related Documents
The following library of MEID documents is intended to assist industry understanding of MEID and the migration from the ESN numbering resource to MEID:
- MEID FAQ (April 2, 2024)
- White Paper on Pseudo-ESN Collisions (May 26, 2005, 14 pages, 139K)
- TIA White Paper on the Exhaust of Electronic Serial Numbers (ESNs) and Migration to Mobile Equipment Identifiers (MEIDs) (November 2007; 6 pages; 70KB)
- TIA Numbering Administrator Correspondence to Assignees of ESN, MEID and UIM_ID Regarding UIM_ID Proposal Request (October 7, 2009; 2 pages; 57K)
- TR-45 Committee Correspondence to 3GPP2 TSG Chairs Regarding UIM_ID Proposal Request (September 2, 2009; 2 pages; 63K)
- TR-45 Committee Correspondence to CDG Regarding UIM_ID Proposal Request (September 2, 2009; 2 pages; 68K)
- Letter to CDG Executive Director from TR-45 Chair Regarding Critical Need at CDG CTO Level for 56-bit Mobile Equipment IDentifier (MEID) and Expanded UIM_ID ("E-UIM_ID") Implementation (July 31,2007; 3 pages; 99K)
- ESN Reissue/Reclamation December 2003 Letter Sent to Manufacturer's w/ID Codes 129-254 (Baseline Text; 2 pages, 52K)
- First Industry Outreach Letter Sent December 18, 2003 & January 7, 2004 (One Sample of 17 letters; 2 pages, 35K)
- Follow-Up Outreach Letter Sent to CTIA on March 9, 2004 (3 pages, 39K)
- Letter on Assignment of Test Mobile Blocks for MEIDs (October, 2004; 1 page, 26K)
- MEID Overview (Version 1.4-April 2006, 9 pages, 57K)
- MEID Standards Update (Version 1.8.4-April 2006, 36 pages, 737K)
- ESN-to-MEID Milestones & Timelines (Feb 24, 2015; 6 pages, 164K)
- 3G Mobile Equipment Identifier (MEID) (3GPP2 S.R0048-A, Version 4.0-June 23, 2005; 15 pages, 304KB) NOTE : See also Annex A: Decimal Representation of MEID [contained in TIA-928-3 [E] "MAP Support for the Mobile Equipment Identity (MEID)" published August 2011 based on 3GPP2 X.S0008-0, Version 3.0].
MEID Guidelines and Process
- The MEID assignment process is compliant with the MOBILE EQUIPMENT IDENTIFIER (MEID) GHA (Global Hexadecimal Administrator) assignment guidelines and procedures.
- Global Wireless Equipment Numbering Administrative Procedures v3.0 (April, 2011, 11 pages, 148K)
MEID Assignments
- The Global Hexadecimal Administrator (GHA) administrator's report may be available to materially- and directly-affected parties via the TIA MEID db. Login/password credentials are required.
Application Process
There is a fee for filing MEID application assignments. The fee chart is available here. Applicants are required to request MEID assignments from the GHA by completing FORM A (see GHA guidelines for MEID forms below). Once the form is received, the GHA will inform the applicant of the required fee. Assignments will NOT be processed until payment has been received.
For more information on applying for MEIDs please go to https://tiaonline.org/products-and-services/meid-database
Short Form Expanded UIM Identifier (SF_EUIMID)
SF-EUIMID uses the same MEID assignment process as the MOBILE EQUIPMENT IDENTIFIER (MEID) GHA (Global Hexadecimal Administrator) Assignment Guidelines and Procedures.
System Operator Codes for ANSI/TIA/EIA-136
The 12-bit System Operator Code (SOC) is used to identify a Service Provider (SP) and is used along with the System Identity (SID) by a mobile station to acquire or reject services offered by specific SPs.
What is an SOC?
The 12-bit System Operator Code (SOC) is used to identify a Service Provider (SP) and is used along with the System Identity (SID) by a mobile station to acquire or reject services offered by specific SPs.
The SOCs fall into two ranges (along with two reserved values), which identify the extent (domain) of the SOC. The following table indicates the domains of the SOC:
Value (hex) | Function |
000 | Reserved / Unknown |
001 - 7FF | National SOC Note 1 |
800 | Reserved / Unknown |
801 - FFF | International SOC |
Note 1 : The use of these National SOC Assignments may result in undesirable mobile station operation if the SOC is used to identify a service provider using Intelligent Roaming (see TIA/EIA-136-123). This is because in Intelligent Roaming the mobile station only attempts to match the broadcast SOC to any stored SOCs without consideration of Mobile Country Code. Because of this issue the use of new National SOCs is being reconsidered.
Who is eligible for a System Operator Code?
Any company (or division of a company) shall be eligible for a SOC if it is engaged in the business of providing wireless service using TIA/EIA-136 technology.
Why is national SOC no longer assigned?
Prior to September 1998, a TIA/EIA-136 system operator may have been assigned both a national SOC and an international SOC, where the national SOC must be associated with a country of operation denoted by the Mobile Country Code (MCC). Currently, no new national SOCs are being assigned due to the potential operational problem given in Note 1 above. However, the assigned international SOC can be used under all circumstances with no operational problems.
What is the difference between an SID and an SOC?
Whereas the SID identifies a specific system area, the SOC identifies the operator providing service within that system area. Where multiple service providers are operating in a given area, the SOCs are used in the Intelligent Roaming procedures to select the service provider on a priority basis determined by the Intelligent Roaming Database (IRDB).
- Latest National SOC Assignment (16K PDF; 4 pages)
SS7 TT & SSN Assignment Notification Information Repository
This repository may be used to enhance industry awareness of previous and proposed assignments including information for company representatives to contact peers. When questions arise, this repository provides a tool to resolve potential conflicts and to avoid possible collisions between carriers on similar services. The tables document known assignments and are not guaranteed to be accurate or up-to-date.
Disclaimer: The SS7 TT & SSN Assignment Notification Information Repository contains information to assist industry awareness of previous and proposed assignments including information for company representatives to contact peers. When questions arise, this repository provides a tool that may assist in the resolution of potential conflicts and to avoid possible collisions between carriers on similar services. The tables document known assignments but are not guaranteed for accuracy or necessarily up-to-date. Unless otherwise specified, all information contained herein has been provided to TIA without any warranty or representation.
TIA therefore, makes no representations or warranties, and disclaims any and all responsibility, with respect to the accuracy, correctness, completeness or scope of such information.
- SS7 TT Assignment Notification Form
- SS7 SSN Assignment Notification Form
- SS7 TT & SN Assignment Repository (Table as of August 2011)
SS7 TT & SSN Assignment Notification Information Background
The documentation for notification of assignments of SS7 TT (Translation Type) and SSN (Sub-System Number) values, in many cases have carrier-specific values used.
This repository may be used to enhance industry awareness of previous and proposed assignments including information for company representatives to contact peers. When questions arise, this repository provides a tool to resolve potential conflicts and to avoid possible collisions between carriers on similar services. The tables document known assignments and are not guaranteed to be accurate or up-to-date.
SS7 TT & SSN Assignment Notification Information Procedure
TIA Engineering Committee TR-45.8 moderates and administers the TIA SS7 TT & SSN assignment forms and tables referenced here in the SS7 TT & SSN Assignment Notification Information Repository on an ongoing basis.
The procedure for industry-wide (wireline/wireless) access to update assignment information and for industry notification is as follows.
- Wireline and Wireless industry personnel complete the information on the assignment notification form and provide to TR-45.8 by:
- email it to the TR-45.8 chair
OR - submit contribution with assignment form information during TR-45.8 meeting for action
- email it to the TR-45.8 chair
- TR-45.8 meeting participants review form & information received for action. TR-45.8 updates the information to the "repository database" tables upon consensus and creates the .pdf file.
- TR-45.8 provides TIA an updated .pdf file to post to the TIA Web site SS7 TT & SSN Assignment Notification Information Repository.
TIA OID (Object IDentifier) Assignment Guidelines and Procedures
These guidelines describe the TIA administration and assignment process for the sub-tree designations below OID "tia". The American National Standards Institute (ANSI) is the registration authority for the "iso/member-body/us" branch o f the tree [see section. 8.0]. TIA has registered sub-tree "tia" with ANSI and is the "tia" sub-tree Assignor.
TIA OID (Object IDentifier) Assignment Guidelines and Procedures These guidelines describe the TIA administration and assignment process for the sub-tree designations below OID "tia". The American National Standards Institute (ANSI) is the registration authority for the "iso/member-body/us" branch of the tree [see section. 8.0]. TIA has registered sub-tree "tia" with ANSI and is the "tia" sub-tree Assignor.
Disclaimer: "TIA OID (Object IDentifier) Assignment Guidelines and Procedures" contains information to assist the industry when referencing an "object" in a unique and universal way for Abstract Syntax Notation One (ASN.1) use. The information contained within this document is not guaranteed for accuracy or necessarily up-to-date. Unless otherwise specified, all information contained herein has been provided to TIA without any warranty or representation.
TIA therefore, makes no representations or warranties, and disclaims any and all responsibility, with respect to the accuracy, correctness, completeness or scope of such information.
- TIA OID (Object IDentifier) Assignment Guidelines and Procedures (102kb - 14 pages)
T.35 Code (T- and V-Series) Administration for the United States and Canada
Involving North America (within Region #2) national manufacturers of equipment according to International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) T-series (Terminals for telematic services) and V-Series (Data communication over the telephone network) Recommendations.
The Chair of TIA TR-30 (whomever is elected to this position) holds the position of V and T-series ITU-T T.35 Terminal Provider Codes Administrator for North America (U.S. and Canada), as designated by the assignment authority, U.S. Department of State EB/CIP/MA. The ITU-T has codified this assignment in Operational Bulletin 845 (October 2005).