Description
The Mobile Station Identification Number (MSIN) is a critical component of the International Mobile Subscriber Identity (IMSI), which is the primary permanent identifier for a cellular subscription. The IMSI is structured as a string of decimal digits, typically 15 digits long, divided into three parts: the Mobile Country Code (MCC, 3 digits), the Mobile Network Code (MNC, 2 or 3 digits), and the MSIN (up to 10 digits). The MSIN is the portion assigned by the mobile network operator (MNO) to uniquely identify a subscriber within that operator's network, as defined by the MCC and MNC.
Architecturally, the MSIN is stored on the subscriber's USIM card and is a key used by the core network to retrieve subscription data. When a UE attaches to the network, it may present the IMSI. The network (specifically, the MME in LTE/5G or the SGSN/VMSC in earlier systems) uses the MCC and MNC to route the authentication request to the correct operator's network. Once within the operator's home network, the HSS (Home Subscriber Server) or its predecessor, the HLR (Home Location Register), uses the full IMSI, with the MSIN being the primary key, to locate the exact subscriber record in its database. This record contains the subscriber's authentication credentials (Ki), service profile, allowed services, and other subscription data.
How it works is integral to subscriber management. The MSIN is an opaque number from the perspective of the radio and core network signaling protocols; these protocols treat the IMSI as a whole. However, for the operator's internal administrative and database systems, the MSIN is the unique handle for a subscription. Its role is to provide unambiguous identification at the operator level. It is used not only for HSS/HLR lookups but also for generating charging records (CDRs), provisioning services, and managing the subscriber lifecycle. The MSIN's value is crucial for correlating all network events and service usage to a specific customer account.
Purpose & Motivation
The MSIN was created as part of the IMSI structure to solve the problem of scalable and unique subscriber identification within a single operator's network. Early mobile systems needed a way to manage potentially millions of subscribers. A simple sequential number (the MSIN) assigned from a national number space, combined with country and network codes (MCC/MNC), created a globally unique identifier (the IMSI) that was essential for automatic roaming.
The purpose of the MSIN is to provide the operator-defined unique key within the globally unique IMSI framework. It addresses the limitation of having only a network code (MNC) by allowing an operator to distinguish between all its subscribers. Its creation was motivated by the need for a hierarchical addressing scheme: the MCC routes to a country, the MNC routes to an operator within that country, and the MSIN finally identifies the subscriber within that operator. This structure is efficient for database lookups and routing in international roaming scenarios. Furthermore, the MSIN allows operators flexibility in their numbering plans; they can structure the MSIN digits to encode information like subscriber type or region, though this is operator-specific and transparent to the standard network procedures.
What changed in its specifications
The latest release-to-release comparison of specifications that define MSIN. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-19 adds security annex clauses for Store and Forward Satellite operation to TS 33.401. It also adds definitions for feeder link, service link, Store and Forward Satellite operation, and IOPS-enabled UE.
Full comparison in TS 33.401 →Technology family
Subscriber and device identifiers · User Equipment
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 7 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
Introduced in Phase 1 (release dating of the term; no individual change cited).
MSIN is specified as the part of the IMSI identifying the mobile subscriber within a GSM PLMN, and HLR ids may include its leading digits.
- “Mobile Subscriber Identification Number (MSIN) identifying the mobile subscriber within a GSM PLMN.” TS 23.003 v3.15.0
- “consisting of the leading digits of the IMSI (MCC + MNC + leading digits of MSIN)” TS 23.003 v3.15.0
TS 33.401 first appears in Rel-8 with MSIN defined as an abbreviation and a requirement that it be confidentiality protected, except when it must be sent in cleartext, e.g. at first attach.
- “From subscriber's privacy point of view, the MSIN (also IMEI) should be confidentiality protected.” TS 33.401 v8.8.0
- “In some cases, e.g., the very first attach procedure, MSIN has to be sent to network in cleartext.” TS 33.401 v8.8.0
The requirement that MSIN be confidentiality protected was reworded to also cover IMEISV, with a note that MSIN must be sent in cleartext in cases like the first attach.
- “From subscriber's privacy point of view, the MSIN, the IMEI, and the IMEISV should be confidentiality protected.” TS 33.401 v9.9.0
- “In some cases, e.g., the very first attach procedure, MSIN has to be sent to network in cleartext.” TS 33.401 v9.9.0
MSIN's role and coding in SUCI/SUPI were specified: MSIN is the scheme input for IMSI-type SUPIs, coded as packed BCD with odd-length padding of 1111 in the final octet.
- “If the MSIN is composed of an odd number of digits, then the bits 5 to 8 of final octet shall be coded as "1111".” TS 33.501 v15.20.0
- Essential clarification of MSIN coding for the ECIES protection shemes TS 33.501CR0560
- “The Mobile Subscriber Identification Number (MSIN) as defined in clause 2.2 or the username identifies the mobile subscription within the Home Network.” TS 23.003 v15.11.0
The MSIN description in 23.003 was reworded to identify the subscription within a PLMN or SNPN, and its use was extended to the username part of an NAI for the Network-Specific Identifier, GLI and GCI SUPI types.
- “Mobile Subscriber Identification Number (MSIN) identifying the mobile subscription within a PLMN or SNPN.” TS 23.003 v16.12.0
- “the "username" corresponds to the username part of a NAI, and it is applicable to SUPI types Network-Specific Identifier” TS 23.003 v16.12.0
For NSWO service in TS 33.501, the UE must construct a SUCI in NAI format whose username carries the encrypted MSIN and whose realm carries the MCC/MNC when the SUPI type is IMSI.
- “the UE shall construct the SUCI in NAI format with username containing the encrypted MSIN and the realm part containing the MCC/MNC” TS 33.501 v17.16.0
Defining Specifications
3GPP specifications that define or reference MSIN, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TR 22.975 v310 | UMTS Numbering and Addressing Requirements | R99 read |
| TS 33.401 vj20 | EPS Security Architecture | Rel-19 read |