No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.



Publication Date:  2018-01-16 Views:  388 Downloads:  0
Issue Description

Many times when we execute it we note that many entries do not have the identifier UEID (random value) or S-TMSI. 

Handling Process

We shoud run the next MML COMMAND: DSP ALLUEBASICINFO to observe the above output. 

When you run the command: DSP ALLUEBASICINFO the UE can be identified by S-TMSI or UEID, sometimes one or both are “NULL” and other times both are NULL.


Please take a look at the below examples:


Figure 1 S-TMSI has value, but UEID is NULL



Figure 2 UEID has value, but S-TMSI is NULL



Figure 3 S-TMSI and UEID are both NULL.


UEID and S-TMSI haven’t at the same time because the UEID is a random value used to identify user when the user is not assigned the S-TMSI.

Figure 1. When a user has assigned a S-TMSI, the UEID is NULL.
Figure 2. The UEID shows a random value and the S-TMSI is NULL.
Figure 3. The inter-eNodeB handover process, the UEID, S-TMSI and RRC Setup reason are all NULL because these information are not carried in the handover request message, so there is normally to result NULL.