ODA Shared Global PLMN
Private Cellular Network Identifier
Your Private Network Identity — Globally Unique, Device-Ready
The ODA Network Identifier Program provides enterprises with a complete, globally unique 4G or 5G identifier package under the ODA shared PLMN ID. Unlike a standalone PLMN allocation, the ODA is working with device OEMs to enable native PLMN support across their device ecosystem.
// 01 — The Problem
Why Enterprises Need a Private Network Identifier
Every Private Cellular Network requires a PLMN-ID — the identity that allows devices to discover, authenticate, and connect to your network. Without one, your network is invisible to every device on your floor. Obtaining a globally unique PLMN-ID independently means navigating the ITU allocation process through a national regulator — a multi-year process designed for nation-scale mobile operators, not enterprise deployments.
Network Identity
The PLMN-ID is broadcast by every cell on your private network. Devices use it to decide whether they're allowed to connect. Without a valid, unique PLMN-ID, your network can't be distinguished from any other network.
Subscriber Uniqueness
Each SIM on your network carries an IMSI derived from your PLMN-ID. The ODA shared-PLMN model partitions the IMSI space into blocks so your subscribers never collide with another enterprise, anywhere in the world.
Cell & Area Planning
Every base station (eNodeB or gNodeB) and every tracking area on your network needs a unique identifier within the PLMN. These are required for paging, mobility, handover, E911, and location services.
Device Acceptance
All Private Cellualr Netowrk devices validate the PLMN-ID before allowing a connection. A PLMN-ID that isn't in a device's allowed list is rejected silently. The ODA Identifier Program addresses this through device enablement — something no other identifier program offers.
// 02 — Identifier Packages
Choose Your Package
Each option provides the complete set of 3GPP identifiers needed to deploy a Private Cellular Network. Select either 4G or 5G based on your PCN deployment needs and infrastructure choices. Both options are allocated from the ODA Shared Global PLMN-ID.
4G / LTE
4G Private Network Package
Complete EPC identifier set for LTE-only or LTE-anchor deployments. Supports up to 10 cell sites and 2 tracking areas.
- 1 IMSI Block Number (IBN) — 1,000 or 10,000 IMSIs
- 1 MMEGI — MME Group Identifier for GUTI/GUMMEI
- 10 eNodeB IDs — unique cell identifiers (ECGI)
- 2 Tracking Area Codes (TAC) — paging zones (TAI)
- ODA Identifier Registry certificate of assignment
- Additional eNB IDs and TACs available on request
5G / NR
5G Private Network Package
Complete 5GC identifier set for SA or NSA deployments. Supports up to 10 cell sites, 2 tracking areas, and 1 network slice.
- 1 IMSI Block Number (IBN) — 1,000 or 10,000 IMSIs
- 1 AMF Set ID — for GUAMI construction
- 10 gNodeB IDs — unique NR cell identifiers (NCGI)
- 2 Tracking Area Codes (TAC, 24-bit) — paging zones
- 1 S-NSSAI — network slice identifier (SST + SD)
- ODA Identifier Registry certificate of assignment
- Additional gNB IDs, TACs, and slices available on request
| Identifier |
4G Package |
5G Package |
3GPP Reference |
Purpose |
| PLMN-ID (shared) | 90X-XX | 90X-XX | TS 23.003 §2 | Network identity — broadcast in SIB1 |
| IBN → IMSI range | ×1 | ×1 | E.212 | Subscriber identity block (1K or 10K IMSIs) |
| MMEGI | ×1 | — | TS 23.003 §2.8.1 | MME Group ID for GUTI/GUMMEI construction |
| AMF Set ID | — | ×1 | TS 23.003 §2.10.1 | AMF routing for GUAMI construction |
| eNodeB ID | ×10 | — | TS 36.413 | Per-base-station identity → ECGI |
| gNodeB ID | — | ×10 | TS 38.413 | Per-base-station identity → NCGI |
| TAC (16-bit) | ×2 | — | TS 23.003 §19.4.2.3 | LTE tracking area / paging scope |
| TAC (24-bit) | — | ×2 | TS 23.003 §19A.4.2.3 | NR tracking area / paging scope |
| S-NSSAI | — | ×1 | TS 23.003 §28.4.2 | Network slice identifier (SST + SD) |
// 03 — The ODA Advantage
More Than an ID — Device-Side Guarantees
Other identifier programs give you a number. ODA gives you a number that works. The ODA Network Identifier Program is backed by the working-group output of the Open Device Alliance — the only industry body focused on removing device-side barriers to Private Cellular Network connectivity.
TG1
PLMN-ID Validation on Device
Your PLMN-ID is included in ODA's device enablement specifications. ODA-certified devices will increasingly accept 90x-xx without requiring MNO operator allowed-list inclusion — the single biggest enterprise pain point that standalone identifiers can't solve.
TG2
Band Enablement Attestation
For PCN deployments around the world — ODA validates which device models have your band enabled in production firmware. Your identifier comes with the device compatibility data that matters.
WG3
ODA Certified Device Compatibility
Every identifier issued is cross-referenced against the ODA Certified Device Registry. You know which devices will successfully connect to your network before you deploy — no trial-and-error in the field.
// 04 — How It Works
From Request to Deployment
The ODA Identifier Registry allocates identifiers from the ODA Shared Global PLMN-ID address space. Each allocation is conflict-free, globally unique, and recorded in the ODA audit log. The process is designed to get you from request to deployment-ready in days, not months.
01
Request
Submit your organization details and select your package tier (4G or 5G) via the contact form below or email.
02
Allocate
The ODA Identifier Registry assigns your IBN, base station IDs, TACs, and core network identifiers.
03
Certificate
You receive your ODA certificate of assignment confirming your exclusive identifier allocation.
04
Deploy
Configure your private network core with your assigned identifiers & consult the ODA Certified Device Registry for compatible devices.
// 05 — IMSI Block Sizing
Flexible Subscriber Capacity
The ODA shared PLMN-ID uses 10 MSIN digits after MCC+MNC (901-07). These 10 digits are split between your IMSI Block Number (IBN) and your User Identification Number (UIN). The split is configurable to match your deployment scale.
RECOMMENDED
1,000 IMSIs per Block
7-digit IBN + 3-digit UIN. Best for most enterprise deployments. Supports up to 10 million allocation blocks across the program.
- IMSI format: 90x xx BBBBBBB UUU
- 1,000 unique subscribers per block
- Sufficient for factories, campuses, venues, fleets
- 10,000,000 total blocks available in the program
LARGE SCALE
10,000 IMSIs per Block
6-digit IBN + 4-digit UIN. For large-scale deployments requiring high subscriber density on a single private network.
- IMSI format: 90x xx BBBBBB UUUU
- 10,000 unique subscribers per block
- Suitable for ports, airports, cities, large utilities
- 1,000,000 total blocks available in the program
// 06 — Questions
Frequently Asked
What is ODA Global PLMN-ID?▾
90x-xx is a globally unique PLMN-ID allocated under MCC 90x (international/shared networks). By using a shared PLMN-ID, enterprises avoid the multi-year ITU application process while still receiving a globally unique, collision-free identity for your private network.
Can I use this identifier with any spectrum?▾
Yes. The ODA Shared Global PLMN-ID is spectrum-agnostic. It works with CBRS (B48/n48), Anterix (B106/n106), Globalstar ATC (n53), locally licensed spectrum (n77, n78, n79), and any other spectrum your deployment uses. The ODA Band Enablement program (TG2) provides additional device-side validation for specific PCN bands.
Will my Samsung, Apple, or Google smartphone accept this PLMN?▾
This is precisely the problem ODA was built to solve. Standard PLMN-ID programs give you a number but can't guarantee device acceptance. ODA's TG1 (PLMN ID Enablement) and TG4 (Minimum PCN Profile) work directly with device OEMs to include native PLMN support to ensure ODA-certified devices accept 90x-xx without requiring MNO operator allowed-list inclusion. Check the ODA Certified Device Registry for current device compatibility status.
Do I need to renew my allocation?▾
Yes. There is a fee for administering and maintaining the ODA Identifier Registry. Once allocated, your IBN, base station IDs, TACs, and other identifiers are yours for as long as you meet deployment requirements and submit your yearly fee. The ODA Identifier Registry maintains the allocation record permanently.
What if I need more than 10 base station IDs?▾
Additional eNodeB IDs (4G), gNodeB IDs (5G), TACs, and S-NSSAI slices can be allocated on request. The 90x-xx address space supports over 1 million macro eNB IDs and over 4 million gNB IDs, so capacity is not a constraint. Contact the ODA Identifier Registry to expand your allocation if needed.
How is ODA's program different from other Network Identifier Programs?▾
ODA provides the identifier plus the device-side guarantees that make the identifier work. ODA's working groups (TG1, TG2, WG3) address the device barriers that prevent smartphones, tablets, laptops, cameras, AGVs, AMRs, and IoT devices from connecting to private networks, regardless of which PLMN-ID is used. An ODA identifier comes bundled with device compatibility data, band enablement attestation, and ODA Certified Device Registry that no standalone identifier program can offer. Additionally, ODA offers both 4G and 5G-native packages with SA-era identifiers (AMF Set ID, S-NSSAI, 24-bit TAC) that reflect current 3GPP standards.
Do I need to be an ODA member to get an identifier?▾
The ODA Network Identifier Program is available to both ODA members and non-members. ODA members gain additional access to working group participation, voting rights, and early specification drafts. Non-members can purchase identifier packages directly.
Ready to deploy your Private Cellular Network?
Get your globally unique identifier package and the device-side guarantees that make it work.