updateLocation

Usage

This message is sent by a VLR to the HLR owning the IMSI when the mobile terminal moved in a location controlled by the VLR.

Expected actions

• The HLR must update its internal location it holds for the IMSI.

• The HLR must Invoke an insertSubscriberData request to the VLR to let it know about the settings and available services of the subscriber. This should be done in the same transaction and wait for the completion.

• If needed the HLR may Invoke an activateTraceMode to the VLR to request tracing of subscriber's activity. This should be done in the same transaction and wait for the completion.

• The HLR must ResultLast to the updateLocation including its own hlr-Number

• If the IMSI was previously located in a different VLR the HLR must Invoke a cancelLocation to the old VLR.

Invoke parameters

• imsi – IMSI of the SIM card

• msc-Number – MSC identification string / number

• vlr-Number – VLR identification string / number

• lmsi – Local mobile station identity (VLR specific)

• extensionContainer – Container for various extensions

Result parameters

• hlr-Number – HLR identification string / number

Possible errors

• systemFailure
• dataMissing
• unexpectedDataValue
• unknownSubscriber
• roamingNotAllowed

Example

<component remoteCID=1" type="Invoke" operationCode="updateLocation">
	<imsi>497012345678900</imsi>
	<msc-Number>49700500000</msc-Number>
	<vlr-Number>49700100123</vlr-Number>
</component>
...
<component remoteCID=1" type="ResultLast" operationCode="updateLocation">
	<hlr-Number>4970100</hlr-Number>
</component>

References

• ETSI TS 100 974 V7.15.0 (2004-03) p1045