tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Glossaries     Architecture     IMS     UICC    |    search     info

3GPP Glossaries

|   Features_Services   |   Network_Entities   |   Reference_Points   |   SIM_UICC_Dir_Files   |   Identifiers   |

 

Identifiers

J

K

U

V

W

X

Y

 

 

 

 

Here          Top

|   MCC   |   MMEC   |   MMEGI   |   MMEI   |   MNC   |   MSIN   |   MSISDN   |   MSRN   |   M‑TMSI   |

 

Source:   TS 23.003, clause 2.2

The MCC consists of 3 digits (12 bits). The allocation of MCCs is administered by the ITU‑T and the current allocation is given in the COMPLEMENT TO ITU‑T RECOMMENDATION E.212.

Some examples: 208 (France), 214 (Spain), 228 (Switzerland)

Up       Top

Source:   TS 23.003, clause 2.8.1

The length of the MME Code is 8 bits.

The operator shall need to ensure that the MMEC is unique within the MME pool area and, if overlapping pool areas are in use, unique within the area of overlapping MME pools.

Up       Top

Source:   TS 23.003, clause 19.4.2.1

The MMEGI identifies a Pool of MMEs and its length is 16 bits.

The MME Pool FQDN shall be constructed as:

mmegi<MMEGI>.mme.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org

<MMEGI> is the hexadecimal string of the MMEGI. If there are less than 4 significant digits, "0" digit(s) shall be inserted at the left side to fill the 4 digit coding.

Up       Top

Source:   TS 23.003, clause 19.4.2.1

An MME within an operator's network is identified using an MMEGI identifying the MME Pool, and an MMEC identifying the MME node within this Pool.

A subdomain name shall be derived from the MNC and MCC by adding the label "mme" to the beginning of the Home Network Realm/Domain.

The MME node FQDN shall be constructed as:

mmec<MMEC>.mmegi<MMEGI>.mme.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org

<MMEC> and <MMEGI> are the hexadecimal strings of the MMEC and MMEGI. If there are less than 2 significant digits in <MMEC>, "0" digit(s) shall be inserted at the left side to fill the 2 digit coding. If there are less than 4 significant digits in <MMEGI>, "0" digit(s) shall be inserted at the left side to fill the 4 digit coding.
3GPP MMEI Structure

 

Up       Top

Source:   TS 23.003, clause 2.2

The length of the MNC is two or three digits (8 bits or 12 bits) and depends on the value of the MCC.

Up       Top

Source:   TS 23.003, clause 2.2

The MSIN is part of the IMSI. It identifies the mobile subscriber within a PLMN.

Up       Top

Source:   TS 23.003, clause 3.3

MS international ISDN numbers are allocated from the ITU-T Recommendation E.164 numbering plan; see also ITU-T Recommendation E.213. The number consists of:
  • Country Code (CC) of the country in which the MS is registered, followed by:
  • National (significant) mobile number, which consists of:
    • National Destination Code (NDC) and
    • Subscriber Number (SN).
For GSM/UMTS applications, a National Destination Code is allocated to each PLMN. In some countries more than one NDC may be required for each PLMN.
MSISDN Structure

 

Up       Top

Source:   TS 23.003, clause 3.4

The Mobile Station Roaming Number (MSRN) is used to route calls directed to an MS. On request from the Gateway MSC via the HLR it is temporarily allocated to an MS by the VLR with which the MS is registered; it addresses the Visited MSC collocated with the assigning VLR. More than one MSRN may be assigned simultaneously to an MS. The MSRN is passed by the HLR to the Gateway MSC to route calls to the MS.

The Mobile Station Roaming Number for PSTN/ISDN routing shall have the same structure as international ISDN numbers (MSISDN) in the area in which the roaming number is allocated, i.e.:
  • the country code of the country in which the visitor location register is located;
  • the national destination code of the visited PLMN or numbering area;
  • a subscriber number with the appropriate structure for that numbering area.

Up       Top

Source:   TS 23.003, clause 2.8

The M-TMSI is part of the GUTI, and the S-TMSI.

Its length is 32 bits.

 

Up       Top