23.3.2 Procedure in the HLR
29.0023GPPMobile Application Part (MAP) specificationRelease 17TS
The process starts when the HLR receives a MAP_SEND_ROUTING_INFO_FOR_SM indication from the SMS-GMSC. If an SMS Router is deployed, the HLR receives MAP_SEND_ROUTING_INFO_FOR_SM from the SMS Router (step 4 in figure 23.3/2a); relaying a message received from the SMS-GMSC to the SMS Router on SCCP level (steps 2 and 3 in figure 23.3/2a) is done by implementation specific means and is not shown in figure 23.3/5.
The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows:
Check_Indication see clause 25.2.1.
Sheet 1: The decision box "Relay to IP-SM-GW" takes the "yes" exit if an IP-SM-GW is deployed and the message was not received from an IP-SM-GW.
Sheet 3: If the SMS-GMSC does not support GPRS functionality, it uses the protocol defined in the Release 96 version of this specification. The parameter "msc-Number" in "RoutingInfoForSM-Res" in the Release 96 version of the protocol definition corresponds to the parameter "networkNode-Number" in "RoutingInfoForSM-Res" in the Release 97 (and later) version of the protocol definition; therefore if the HLR populates the parameter "networkNode-Number" with the SGSN number, the Release 96 SMS-GMSC will interpret the SGSN number as an MSC number. If the HLR populates the "gprsNodeIndicator" parameter in the MAP_SEND_ROUTING_INFO_FOR_SM response, a Release 96 SMS-GMSC will silently discard the parameter.
Sheet 5: If the HLR received a LMSI from the VLR at location updating, it shall include the LMSI in the MAP_SEND_ROUTING_INFO_FOR_SM response only if the MAP_SEND_ROUTING_INFO_FOR_SM response also includes the MSC number.
The mobile terminated short message transfer process in the HLR is shown in figure 23.3/5.