Wednesday 22 April 2009

Temporary Identities in LTE/SAE - 1

An MS may be allocated three TMSIs, one for services provided through the MSC (TMSI), one for services provided through the SGSN (P-TMSI for short) and one for the services provided via the MME (M-TMSI part GUTI for short).

The purpose of the GUTI is to provide an unambiguous identification of the UE that does not reveal the UE or the user's permanent identity in the Evolved Packet System (EPS). It also allows the identification of the MME and network. It can be used by the network and the UE to establish the UE's identity during signalling between them in the EPS.

The GUTI has two main components:
  • one that uniquely identifies the MME which allocated the GUTI; and
  • one that uniquely identifies the UE within the MME that allocated the GUTI.
Within the MME, the mobile shall be identified by the M-TMSI.

The Globally Unique MME Identifier (GUMMEI) shall be constructed from the MCC, MNC and MME Identifier (MMEI).

The MMEI shall be constructed from an MME Group ID (MMEGI) and an MME Code (MMEC).

The GUTI shall be constructed from the GUMMEI and the M-TMSI.

For paging purposes, the mobile is paged with the S-TMSI. The S-TMSI shall be constructed from the MMEC and the M-TMSI.
S-TMSI = MMEC + M-TMSI

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.

The GUTI shall be used to support subscriber identity confidentiality, and, in the shortened S-TMSI form, to enable more efficient radio signalling procedures (e.g. paging and Service Request).


The format and size of the GUTI is therefore the following:
GUTI = GUMMEI + M-TMSI, where
GUMMEI = MCC + MNC + MME Identifier and
MME Identifier = MME Group ID + MME Code
MCC and MNC shall have the same field size as in earlier 3GPP systems.
M-TMSI shall be of 32 bits length.
MME Group ID shall be of 16 bits length.
MME Code shall be of 8 bits length.

During Handover to GERAN/UTRAN
RAI = MCC + MNC + LAC + RAC
E UTRAN "MCC" maps to GERAN/UTRAN "MCC"
E UTRAN "MNC" maps to GERAN/UTRAN "MNC"
E UTRAN "MME Group ID" maps to GERAN/UTRAN "LAC"
E UTRAN "MME Code" maps to GERAN/UTRAN "RAC" and is also copied into the 8 most significant bits of the NRI field within the P TMSI;

"P-TMSI" includes the mapped NRI
P TMSI shall be of 32 bits length where the two topmost bits are reserved and always set to 11.

E UTRAN "M-TMSI" maps as follows:
6 bits of the E UTRAN "M-TMSI" starting at bit 29 and down to bit 24 are mapped into bit 29 and down to bit 24 of the GERAN/UTRAN "P TMSI";
16 bits of the E UTRAN "M-TMSI" starting at bit 15 and down to bit 0 are mapped into bit 15 and down to bit 0 of the GERAN/UTRAN "P TMSI";
and the remaining 8 bits of the E UTRAN "M-TMSI" are mapped into the 8 MBS bits of the "P-TMSI signature" field.

Abbreviations Summary:
GUTI - Globally Unique Temporary UE Identity
GUMMEI - Globally Unique MME Identifier
MMEGI - MME Group ID
MMEC - MME Code
S-TMSI = SAE Temporary Mobile Subscriber Identity
M-TMSI = MME Temporary Mobile Subscriber Identity

Reference: 3GPP TS 23.003: Technical Specification Group Core Network and Terminals; Numbering, addressing and identification (Release 8) - Section 2.8

7 comments:

जयंत - समर शेष said...

Very nicely presented information. Please keep up the good work.

You made it very easy to understand and follow the temporary IDs.

Anonymous said...

it was really nice to easily understand this identity concept

ahmed3188 said...

do you kno the meaning of "the 8 MBS bits of the "P-TMSI signature" field"??

Zahid Ghadialy said...

read it as '8 MSB bits' :)

Anonymous said...

nice explanation, keep it up :)

x said...

Can anybody tell me, Why S-tmsi is requires in LTE paging?

Zahid Ghadialy said...

X, please read this interesting discussion on Linkedin here

In short, "Because the paging is done in LTE domain not UMTS. The UE needs to know the MME id, hence S-TMSI (MMEC + M-TMSI). Why? For the routing NAS message to the appropriate MME"