Basic Call Flows

Table of Contents:
1. 2. 3. 4. Call Flow of Update Location of Subscriber Call flow diagram Parameters for Update Location and Authentication . Details of various scenario of location update failure.. 3 4 5 5

1.

Call Flow of Update Location of a subscriber : Basic Call Flow: 1. Invoke sendAuthenticationInfo: This message is sent by VLR to HLR via STP because HLR is connected to STP and all the message meant for HLR come through STP(Either Banglore STP or HYD STP). 2. returnResultLast This is acknowledge message sent by HLR to VLR which confirm last message and send 3 triplets along with the message .If triplets matches with the auc triplet which VLR have, subscriber is authenticated and send next message. 3. invoke updateLocation: This message is sent by VLR to HLR to do location update of subscriber. If data sent is appropriate HLR response with message invoke insert Subscriber Data otherwise in case of failure it send return Error. 4. invoke insertSubscriberData: This message is sent by HLR to VLR to insert subscriber information in VLR. Sometime HLR send more than one message of its type because subscriber info is large thus required more message of same type. InvokeId of these message start from 0 and it increment till the number of same kind of message. For ex in this call flow HLR has sent invoke insert Subscriber Data thrice. 5. returnResultLast insertSubscriberData: This is acknowledge message sent by VLR to HLR which confirm Success of insertion of data in VLR. 6. invoke insertSubscriberData: 7. returnResultLast insertSubscriberData: 8. invoke insertSubscriberData: 9. returnResultLast insertSubscriberData: 10. returnResultLast updateLocation: This is acknowledge message sent by HLR to VLR confirming successful location update of subscriber.

2.

Call flow diagram : This call flow will be more clear by the figure drawn below: VLR HLR 1. invoke sendAuthenticationInfo

2 . returnResultLast sendAuthenticationInfo sendAuthenticationInfo

3. invoke updateLocation

4.. invoke insertSubscriberData

5 . returnResultLast insertSubscriberData 6.. invoke insertSubscriberData

7 . returnResultLast insertSubscriberData 8.. invoke insertSubscriberData

9. returnResultLast insertSubscriberData

10.returnResultLast updateLocation

3.

Parameters for Update Location and Authentication : Here are attached 2 word docs one for update location and second one for authentication which has details of parameter with respect to all layers which should be referred while analyzing traces efficiently. 1.

call_flow_LU_gen_ca se

2.

Authentication_detail s

4.

Details of various scenario of location update failure of subscriber : Location update failure in case of roaming due to ODB barring. In subscriber ODB profile, if roaming parameter is set Roaming outside HPLMN. It means that roaming is barred for this subscriber and if this subscriber tries to roam its location update fail. This is shown by parameter in GSM Mobile Application layer. GSM Mobile Application Component: returnError (3) returnError invokeID: -28 errorCode: localValue (0) localValue: roamingNotAllowed (8) roamingNotAllowedCause: operatorDeterminedBarring (3) Pls find details of message in attached word doc.

LU_failure_roam ing_ case_ODB

 Location update failure in case of roaming due non existence of GT of network in which subscriber is trying to latch in Roaming Restriction RES parameter of subscriber. In subscriber roaming profile , Roaming Restriction RES is suppose 53 and in Remote Entity Sets GT in which subscriber is trying to latch do not exist for 53 .In this case also in traces we get roaming not allowed. Ex GSM Mobile Application(MAP Layer) Component: returnError (3) returnError invokeID: -28 errorCode: localValue (0) localValue: roamingNotAllowed (8) Location update failure when T11 service is not there in subscriber profile. In subscriber Profile if T11 service is not there and when it tries to latch in network , Its location update will not happen and reason will be systemFailure . T11 is code for basic speech call. This is shown by parameter in GSM Mobile Application layer. GSM Mobile Application(MAP Layer) Component: returnError (3) returnError invokeID: 1 errorCode: localValue (0) localValue: systemFailure (34) extensibleSystemFailureParam networkResource: hlr (1) Pls find details of message in attached word doc.

LU_failure_gen_case

Location update failure due to issue in STP : Sometime STP delay sending of message and loop is created at its side. We can identify this message as these message has sack(negative Acknowledge) word before original message for ex. sack returnResultLastinsertSubscriberData.Its not necessary that whenever we receive this type of message, failure happen but it can lead to failure. We also receive this kind of message when STP send same message to HLR in response which it

received from it. After receiving this HLR abort this message conversation thus failure happen. Location update failure for prepaid subscriber in which HLR do not receive parameter containing IN information. Sometime it happens that when VLR send message invoke update Location message to HLR , it is not able to identify weather this message is for prepaid subscriber or postpaid and because of this failure occur. There is parameter in GSM Mobile Application layer ie vlr-Capability which give information about subscriber.Highlighted parameter is used to determine about subscriber profile. PREPAID vlr-Capability Padding: 5 supportedCamelPhases: E0 (phase1, phase2, phase3) 1... .... = phase1: True .1.. .... = phase2: True ..1. .... = phase3: True ...0 .... = phase4: False longFTN-Supported Padding: 6 supportedLCS-CapabilitySets: C0 (lcsCapabilitySet1, lcsCapabilitySet2) 1... .... = lcsCapabilitySet1: True // in prepaid case .1.. .... = lcsCapabilitySet2: True ..0. .... = lcsCapabilitySet3: False ...0 .... = lcsCapabilitySet4: False .... 0... = lcsCapabilitySet5: False POSTPAID vlr-Capability Padding: 5 supportedCamelPhases: E0 (phase1, phase2, phase3) 1... .... = phase1: True .1.. .... = phase2: True ..1. .... = phase3: True ...0 .... = phase4: False longFTN-Supported Padding: 6 supportedLCS-CapabilitySets: C0 (lcsCapabilitySet1, lcsCapabilitySet2) 1... .... = lcsCapabilitySet1: False // in postpaid case .1.. .... = lcsCapabilitySet2: False ..0. .... = lcsCapabilitySet3: False

...0 .... = lcsCapabilitySet4: False .... 0... = lcsCapabilitySet5: False