Location Updating

Commands
MSC
Mgepp

!Prints exchange properties!

Mgbsp

!Prints BSCs off the MSC!

Mgidp
timers!

!Prints Implicit Detach supervision data, BTDM timers and GTDM

Mgadp

!Prints automatic Deregistration data!

Mgcep

!Prints cell data!

BSC
RLCRP:CELL=cell; !Prints cell data!
RLSBP:CELL=all;

!Prints T3212 timer value for periodic registration!

Affected by
Radio:
Increase periodic registration timer, T3212. Decrease location updating load by
increasing the timer value (note this will increase the paging load and may
adversely affect paging success rate especially in cells with combined SDCCH/BCCH
(SDCCH/4 config). If T3212 is increased, BTDM (implicit detach) must also be
increased since BTDM must be equal to or greater than T3212.
SDCCH congestion.
Changing the size of location areas/splitting location areas will reduce location
update load. Also moving cells to another location area.
C7 links to MGW/MSS from the BSC. Interruptions of service to the links will affect
location update success.
Core:
Sigtran links from MSC to HLR. Interruptions of service in the SCTP associations may
also affect location updating success.

Statistics
See Alex for full list of counters and counter information for these Objecttypes.
Objecttype

UPDLOCAT

Counter

Description

NLNOLDTOT

Number of normal Location updating attempts for already registered

subscribers.
This counter is increased at normal Location Updating attempts for already
registered subscribers.

NLOCNRGTOT

Number of location updating attempts from non-registered subscribers.

This includes IMSI attach, normal location updating, or periodic location
updating.

NLOCOLDTOT
NLOCPERTOT

Number of location updating attempts for already registered subscribers.

Number of periodic location updating attempts for already registered
subscribers.

NLOCATTTOT

Number of IMSI attach messages received.

This counter is increased each time a IMSI attach message is received.

NLOCNRRTOT

Number of national roaming restriction events.

This counter is increased each time a national roaming restriction event
take place.

NLAPAGERR

NLALIOSUCC

NLALNNSUCC

Number of unsuccessful page responses to a location area (including

unexpected page responses at location area level)
This counter is increased when a page response is received for a mobile
subscriber not being paged.
Number of successful IMSI attached location updating for already
registered subscriber.
This counter is increased when a location updating with IMSI attach for an
already registered subscriber is successfully terminated.
Number of successful normal location updating for non-registered
subscriber.
This counter is increased when a normal location updating for a nonregistered subscriber is successfully terminated.

NLALNOSUCC

Number of successful normal location updating for already registered

subscriber.
This counter is increased when a normal location updating for an already
registered subscriber is successfully terminated.

NLALOCPRRFLT

Number of location updating rejections due to partial roaming.

This counter is increased when the location updating is rejected due to
partial roaming.

NLALOCSUCC

Number of successful location updates.

This counter is increased when the location updating is successfully
terminated.

NLALOCTOT

Total number of location updating attempts.

This counter is increased for each location updating if the location area is a
known location area.

NLALPESUCC

Number of successful periodic location updating.

This counter is increased when a periodic location updating is successfully
terminated.

NLALPETOT

Total number of periodic location updating.

This counter is increased for each periodic location updating.

LOCAREAST

Some EOS Codes related to Location Updating

2298

GRI

Call to a mobile
subscriber, who is
temporarily absent
Recommended task:
1. COS = No call
acknowledgement
for mobile subscribers
2. Redirection F, M.
Recommended location:
Local network
Recommended cause:
Subscriber absent

2312

MTBCC, MTBSS

IMSI DETACH message

received.
Recommended task:
1. COS = No call acknowledgement
for mobile subscribers
2. Redirection F, M.
Recommended location:
Local network
Recommended cause:
Subscriber absent

4788

MTACC

IMSI detach received from calling

mobile subscriber.
Recommended task:
FRE = Forced release

AXE parameters
DBTSP:TAB=AXEPARS,SETNAME=GSMMMSC,NAME=AUTHENTICATE;
AXE Paramter

Description

Settings

AUTHENTICATE

AXE parameter AUTHENTICATE in

GSMMMSC parameter set determines
whether authentication is performed in
the MSC/VLR Server.

0 = Authentication not
performed
1 = Authentication
performed

SELAUTH

AXE parameter SELAUTH in GSMMMSC

parameter set determines whether
selective authentication is used in
Global System for Mobile
Communications (GSM) security
context in the MSC/VLR Server.
AXE parameter SELAUTHCALL in
GSMMMSC parameter set determines
whether selective authentication is used
for calls in GSM security context in the
MSC/VLR Server.

0 = Selective authentication
not used in GSM security
context
1 = Selective authentication
not used in GSM security
context
0 = Selective authentication
for calls not used in GSM
security context
1 = Selective authentication
for calls used in GSM
security context
0 15 Number of
successive accesses

SELAUTHCALL

SELAUTHCIPNR

AXE parameter SELAUTHCIPNR in

GSMMMSC parameter set defines the

Default
Value
1

10

SELAUTHLOCUP

TMSIPAR

number of consecutive subscriber

accesses allowed to be performed
without authentication if selective
authentication is enabled for GSM
security context in the MSC/VLR Server.
The AXE parameter determines whether
selective authentication is used or not
for location updating in GSM security
context in the MSC/VLR.

AXE parameter TMSIPAR in GSMMMSC

parameter set determines whether
TMSI allocation is performed in the
MSC/VLR Server.

performed without
authentication in GSM
security context
Value 0 indicates that
selective authentication is
not used for location
updating in GSM security
context.
Value 1 indicates that
selective authentication is
used for location updating
in GSM security context.
0 = TMSI not allocated
1 = TMSI allocated only on
encrypted connections
2 = TMSI allocated on all
connections

Exchange properties

Property

Description

Value Range

Defaul
t

CIPHER

Exchange property CIPHER controls if

ciphering is performed in the
MSC/VLR Server.

0 = Ciphering not performed

during LU
1 = Ciphering performed
during LU

CIPHERALGALLOW

Exchange property CIPHERALGALLOW

indicates the allowed ciphering
algorithms in the MSC/VLR Server.
Exchange property AUTSENDREJECT
determines whether authentication reject is
to be sent after authentication failure. If
mobile station receives authentication
reject, all access attempts except
emergency call will be rejected by the
MSC/VLR Server.
Exchange property IMEICONTROLLU
determines whether the IMEI check is to be
performed for location updating.

AUTSENDREJECT

IMEICONTROLLU

PURGECONTROL

Mobile subscriber purging control. The

parameter is optional. It indicates whether
or not the MAP operation 'Purge MS' is sent
to HLR when manual or automatic
deregistration of a mobile subscriber is
performed.

APPENDIX: Supplementary imformation

2
0 = No sending authentication
reject
1 = Sending authentication
reject

0 = Not Active.
1 = Active for IMSI attach and
normal location updating.
2 = Active for IMSI attach,
normal and periodic location
updating
0 = Send 'Purge MS' operation
to HLR
1 = Do not send 'Purge MS'
operation to HLR

TEST CASES

3.1

LOCATION UPDATING

Check following MT Exchange Properties and CUSTOM class AXE parameters

to find out how security functions are handled in the exchange:
DBTSP:TAB=AXEPARS,SETNAME=GSMMMSC,NAME=AUTHENTICATE;
DBTSP:TAB=AXEPARS,SETNAME=GSMMMSC,NAME=SELAUTH;
DBTSP:TAB=AXEPARS,SETNAME=GSMMMSC,NAME=SELAUTHCALL;
DBTSP:TAB=AXEPARS,SETNAME=GSMMMSC,NAME=SELAUTHCIPNR;
DBTSP:TAB=AXEPARS,SETNAME=GSMMMSC,NAME=SELAUTHLOCUP;
DBTSP:TAB=AXEPARS,SETNAME=GSMMMSC,NAME=TMSIPAR;
MGEPP:ID=CIPHER;
MGEPP:ID=CIPHERALGALLOW;
MGEPP:ID=AUTSENDREJECT;
MGEPP:ID=IMEICONTROLLU;
MGEPP:ID=PURGECONTROL;

3.1.1

IMSI attach and detach

Action: MS is powered off and registered in node A.

HGSDP:MSISDN=msisdn,ALL;
Action: Remove the location in the HLR by MML command.
HGSLR:MSISDN=msisdn;
Action: Check MS location in the HLR and VLR.
HGSDP:IMSI=imsi,LOC;
MGSLP:IMSI=imsi,ALL;
Result: MS is removed from the MSC/VLR and VLR address
is UNKNOWN.
Action: Trace outgoing signal AUTHENTICATER from b'MAUTH.
Power on MS (IMSI attach).
HGSDP:IMSI=imsi,ALL;
MGSSP:IMSI=imsi;
MGSLP:IMSI=imsi,ALL;
Result: Check that MS is registered in MSC/VLR and all MS data
are correctly updated. MS state in VLR is IDLE.
Authentication and ciphering are performed correctly
(tracing of s'AUTHENTICATER from b'MAUTH)
ON OUT MAUTH AUTHENTICATER;
D2 result (0-successful procedure)
D4 ciphering (1-performed, 0-not performed)
D5 authentication (0-performed, 1-not performed)
D6 IMEI digits (0-not present, 1-present in D7-D10)
D11: H0 = encryption algorithm (1-no encryption)
(2-GSM A5/1)
(3-GSM A5/2)
Action: Power off MS (IMSI detach).
HGSDP:IMSI=imsi,ALL;
MGSSP:IMSI=imsi;
MGSLP:IMSI=imsi,ALL;
Result: MS1 is registered in MSC/VLR and VLR address
is known in HLR. MS state in VLR is Detached.

Action: Power on MS again.

HGSDP:IMSI=imsi,ALL;
MGSSP:IMSI=imsi;
MGSLP:IMSI=imsi,ALL;
Result: MS is marked attached in VLR (state IDLE). No
authentication and ciphering performed when IMSI
attach without Location Updating.

3.1.2

Location Updating when roaming to new MSC/VLR area

This test case needs 2 nodes configuration.

Action: MS is powered on and registered in node A.
Check MS location in the HLR and VLR.
HGSDP:IMSI=imsi,LOC;
MGSSP:IMSI=imsi;
MGSLP:IMSI=imsi,ALL;
Action: Trace outgoing signal AUTHENTICATER from b'MAUTH (node B).
Make roaming to node B service area.
Check location of MS1 and updating of subscriber data.
HGSDP:IMSI=imsi,ALL;
MGSSP:IMSI=imsi;
MGSLP:IMSI=imsi,ALL;
Result: Check that MS is registered in new MSC/VLR (node B) and
all MS data are correctly updated. MS state in VLR is
IDLE. VLR address in HLR must be node B address and MS is
removed from old VLR (node A).
Result: Check that authentication and ciphering are performed
correctly (tracing of s'AUTHENTICATER from b'MAUTH)
ON OUT MAUTH AUTHENTICATER;
D2 result (0-successful procedure)
D4 ciphering (1-performed, 0-not performed)
D5 authentication (0-performed, 1-not performed)
D6 IMEI digits (0-not present, 1-present in D7-D10)
D11: H0 = encryption algorithm (1-no encryption)
(2-GSM A5/1)
(3-GSM A5/2)
Action: Power off MS.
MGSSP:IMSI=imsi;
Result: Check that MS state is Detached.
Action: Power on MS in node A service area.
Check location of MS1 and updating of subscriber data.
HGSDP:IMSI=imsi,ALL;
MGSSP:IMSI=imsi;
MGSLP:IMSI=imsi,ALL;
Result: Check that MS is registered in new MSC/VLR (node A) and
all MS data are correctly updated. MS state in VLR is
IDLE. VLR address in HLR must be node A address and MS is
removed from old VLR (node B).
Result: Check that authentication and ciphering are performed
correctly (tracing of s'AUTHENTICATER from b'MAUTH)

3.1.3

Location Updating at call to not registered MS

This is not possible to test when MS Purging is active.

Action: Check MT Exchange Property PURGECONTROL
(0-send PURGE MS, 1-do not send PURGE MS to HLR).
MGEPP:ID=PURGECONTROL;
Action: MS1 and MS2 are powered on and registered in node A.
HGSDP:MSISDN=msisdn1&MSISDN2,LOC;
MGSSP:IMSI=imsi1&imsi2;
Action: Deregister MS2 from MSC/VLR by command.
MGSRE:IMSI=imsi2;
Action: Check MS2 location in the HLR and VLR.
HGSDP:IMSI=imsi2,LOC;
MGSSP:IMSI=imsi2;
Result: MS is removed from the MSC/VLR but VLR address is known
in HLR. If MS Purging is active HLR knows that MS
PURGED IN VLR and call is not routed to this MS.
Action: Trace outgoing signal AUTHENTICATER from b'MAUTH.
Action: Make a call from MS1 to MS2.
Result: Call is successful. Verify speech connection.
Check that authentication and ciphering are performed
correctly (tracing of s'AUTHENTICATER from b'MAUTH)
D2 result (0-successful procedure)
D4 ciphering (1-performed, 0-not performed)
D5 authentication (0-performed, 1-not performed)
D6 IMEI digits (0-not present, 1-present in D7-D10)
D11: H0 = encryption algorithm (1-no encryption)
(2-GSM A5/1)
(3-GSM A5/2)
Action: Check MS2 location and data in the HLR and VLR.
HGSDP:IMSI=imsi2,ALL;
MGSSP:IMSI=imsi2;
MGSLP:IMSI=imsi2,ALL;
Result: Check that MS is registered in MSC/VLR and all MS data
are correctly updated. MS state in VLR is BUSY.
Action: Release the call.

3.1.4

Location Updating at call from not registered MS

Action: MS1 and MS2 are powered on and registered in node A.

HGSDP:MSISDN=msisdn1&MSISDN2,LOC;
MGSSP:IMSI=imsi1&imsi2;
Action: Remove the MS1 location in the HLR by command.
HGSLR:IMSI=imsi1;
Action: Check MS1 location in the HLR and VLR.

HGSDP:IMSI=imsi1,LOC;
MGSSP:IMSI=imsi1;
Result: MS is removed from the MSC/VLR and VLR address is
UNKNOWN in HLR.
Action: Trace outgoing signal AUTHENTICATER from b'MAUTH.
Action: Attempt to make a call from MS1 to MS2.
Result: Call is rejected and location updating is made.
Check that authentication and ciphering are performed
correctly (tracing of s'AUTHENTICATER from b'MAUTH)
D2 result (0-successful procedure)
D4 ciphering (1-performed, 0-not performed)
D5 authentication (0-performed, 1-not performed)
D6 IMEI digits (0-not present, 1-present in D7-D10)
D11: H0 = encryption algorithm (1-no encryption)
(2-GSM A5/1)
(3-GSM A5/2)
Action: Check MS1 location and data in the HLR and VLR.
HGSDP:IMSI=imsi1,ALL;
MGSSP:IMSI=imsi1;
MGSLP:IMSI=imsi1,ALL;
Result: Check that MS is registered in MSC/VLR and all MS data
are correctly updated. MS state in VLR is IDLE.
Action: Make a new call attempt from MS1 to MS2.
Result: Call is successful. Verify speech connection.
Check that authentication and ciphering are performed
correctly (tracing of s'AUTHENTICATER from b'MAUTH)
Action: Release the call.

3.1.5

Periodic registration and implicit detach

This test case needs access to BSC.

Action: MS is powered on and registered in node A.
HGSDP:MSISDN=msisdn,LOC;
MGSSP:IMSI=imsi;
Action: Find out the cell where MS is locating (in BSC) and
check original value of periodic registration.
RLCRP:CELL=all;
RLCRP:CELL=cell;
RLSBP:CELL=all;
Action: Set periodic registration in BSC to 6 minutes.
RLSBC:CELL=cell,T3212=1;
Action: Print the parameters for implicit detach.
MGIDP;
Action: Set base and guard time in minutes for implicit detach.
MGIDI:BTDM=6,GTDM=1;

Action: Remove the MS location in the HLR by command.

HGSLR:IMSI=imsi;
Action: Check MS location in the HLR and VLR.
HGSDP:IMSI=imsi,LOC;
MGSSP:IMSI=imsi;
Result: MS is removed from the MSC/VLR and VLR address is
UNKNOWN in HLR.
Action: Wait more than 6 minutes and print the registration
data for MS.
HGSDP:IMSI=imsi,LOC;
MGSSP:IMSI=imsi;
MGSLP:IMSI=imsi,ALL;
Result: Check that MS is again registered in MSC/VLR and all MS
data are correctly updated. MS state in VLR is IDLE.
Action: Remove MS antenna or battery.
Result: MS is out of coverage.
Action: Wait more than 7 minutes and print registration data
for MS in MSC/VLR.
MGSSP:IMSI=imsi;
Result: MS is marked IDET in MSC/VLR.
Action: Set periodic registration value in the BSC and implicit
detach parameters in MSC back to original values.
RLSBC:CELL=cell,T3212=oldvalue; (in BSC)
MGIDE;
MGIDI:BTDM=old_btdm,GTDM=old_gtdm;