Sga-HLRQuery

The ‘HLR Query’ function,
implemented by
Aitia International Inc.

Table of contents

• How does it work?

• Software components

Basic operation of the HLRQuery service

Click to enlarge!

• After establishing a connection the web client sends a SOAP request with a subscriber's number (MSISDN).
• Sga-HLRQuery asks the HLR for the operator determined barring (ODB) and unconditional call forwarding data (Requested SS-Info=CFU) using a MAP/anyTimeSubscriptionInterrogation-v3 operation.
• From the HLR's answer Sga-HLRQuery sets the following fields:
  • OpBarringInfo = "YES"
    • if ODB-Info/ODB-Data/ODB-GeneralData tag exists and the value of its 19th bit is 1)
  • DataCard = "YES"
    • if callForwardingData/basicService:ext-Teleservice = { 10 } does not exists
  • CallForward = "YES"
    • if there is a CFU set in callForwardingData/basicService:ext-Teleservice = { 10 }
  • CallForward_AM = "YES"
    • if there is a CFU set and forwardedToNumber is listed in Sga_HLRQuery2.ini/[Voice Mail MSISDN] section
• In case at least one state above is "YES" there will be no further HLR interrogation and value of Busy and NotReachable and Roaming fields will be "UNKNOWN".
• Otherwise the next step will be a MAP/anyTimeInterrogation-v3 operation towards the HLR with LocationInformation and SubscriberState parameters.
• Based on the answer Sga-HLRQuery sets the following fields:
  • Busy = "YES"
    • if subscriberInfo/subscriberState = camelBusy
  • NotReachable = "YES"
    • if subscriberInfo/subscriberState = netDetNotReachable
  • Roaming = "YES"
    • subscriberInfo/vlr-number =/= 36xxxxxxxxx)
• If any of parameters and values could not be retrieved or is not provided by the HLR will be set "UNKNOWN".
• According to gathered information Sga-HLRQuery composes an answer for the web client.