MDN/MSID Population
1
Introduction
1.1 Purpose
This document describes and discusses the population of the MDN and MSID fields
in the CIBER Record protocol when the MDN and the MSID are the same and when
they are split.
1.2 Referenced Documents
CIBER Protocol
1.3 Acronyms and Abbreviations
Term
MDN
MIN
MSID
MBI
IMSI
CIBER
2.5
Meaning
Mobile Directory Number
Mobile Identifier Number
Mobile Station IDentification
MIN Block Identifier
International Mobile Subscriber Identity
CIBER’s current version.
1.4 Contributors
Cibernet Corporation
2
Introduction of Wireless Local Number Portability (LNP)
Cibernet introduced the X2 record types in 1999 in response to the United States’
Wireless Number Portability (WNP) initiative. With WNP, a wireless consumer has
the ability to change service providers and keep the same phone number.
Previously the MIN was tied to a specific carrier, and served as both the dialable
number and the network registration and call processing number. To support
WLNP, the MIN remained the same and a new number type/space called MDN was
created. The MSID is either the IMSI that can be up to 15-digit long or the 10digit MIN. The first 5 or 6 digits of an IMSI or the first 6 digits of a MIN identifies
the carrier that owns that MSID. An MSID is not generally known to the customer.
The MDN value is dialable and can be ported from one carrier to another.
Page 1 of 3
The MSID field is required to be populated because it is utilized by the
clearinghouse to guide records to their correct home carrier. The MBI, which is the
first 6 digits of a block of 10,000 MINs, is used to uniquely identify a wireless
service provider. Each serving carrier exchanges Technical Data Sheets with their
roaming partners providing the market and BID information for each MBI line
range. This information is used by each serving carrier to map the home BID on
the CIBER Record.
This split needs identification and population in the CIBER Record to correctly bill
the subscriber’s home carrier via the MSID, and to identify the correct customer
via the MDN.
Below, are examples on how to populate an X2 record when the MDN and MSID
are split, and when they are the same:
2.1 MDN/MIN Split
When a subscriber decides to port his/her number to another service provider, the
customer will now have two numbers: The MIN, which identifies the subscriber’s
service provider, and the MDN, which is the dialable phone number of the
subscriber.
When populating the CIBER Record, if the customer’s MIN is 1-301-555-4321,
and the MDN is 1-703-543-5387.
The MSID field will be populated as follows:
MSID
130155543210000
The MSISDN/MDN field will be populated as follows:
MSISDN/MDN
170354353870000
2.2 MDN/MIN Split Not Required
If the subscriber has not ported his/her number, then the MIN and the MDN will be
the same.
Page 2 of 3
When populating the CIBER Record, if the customer’s MDN is 1-301-555-4321,
then the MSID field will be populated as follows:
MSID
130155543210000
The MSISDN/MDN field will be populated as follows:
MSISDN/MDN
130155543210000
2.3 MSID Indicator
It is also necessary to populate the MSID Indicator, to identify if this field will be
populated with either an ITU-T E.212 IMSI or a MIN.
3
Relevance
The correct population of the MDN, MSID and MSID Indicator fields within the
CIBER 22 records with the applicable data will ensure successful collection of the
wholesale usage and end-user billing.
3.1 Next Steps
The CIBER X2 records provide these fields, however they may be zero-filled.
Cibernet proposes in conjunction with the X0 cutover date, an implementation of
edit conditions that remove the ability to zero-fill these fields. Cibernet will finalize
these changes in the January 1, 2007 CIBER Update.
Page 3 of 3