09.023GPPMobile Application Part (MAP) specificationTS
The short message handling function of the GMSC will request routing information when a mobile terminated short message is received from a Service Centre. The GMSC sends the MAP_SEND_ROUTING_INFO_FOR_SM request to the HLR containing the subscriber data of the mobile subscriber and the indication that the SMS-GMSC supports the GPRS functionality.
As an outcome of the procedure the MAP_SEND_ROUTING_INFO_FOR_SM confirmation is received indicating:
– an unsuccessful event indication containing an error;
The mapping between the MAP error causes and the RP_ERROR causes is explained in TS GSM 03.40.
– a successful event indication containing following parameters:
– an IMSI optionally accompanied by an LMSI; and
– routing addresses (servicing MSC, SGSN or both numbers).
The LMSI shall not be used in case the short message is routed towards the SGSN.
The GMSC may also receive a MAP_INFORM_SERVICE_CENTRE indication after the MAP_SEND_ROUTING_INFO_FOR_SM confirmation. The parameter MW Status in the message indicates whether or not the Service Centre address is stored in the Message Waiting Data. It also indicates the status of the MCEF , MNRF and MNRG flags in the HLR.
If the MSISDN-Alert stored in the MWD data is not the same as the one sent to the HLR, the MSISDN-Alert is received in the MAP_INFORM_SERVICE_CENTRE indication. This MSISDN number shall be transferred in a delivery failure report to the SC.
In the abnormal end or in the provider error case the system failure error is provided to the SC.
The forward short message procedure is initiated when the GMSC has obtained the routing information needed to forward a mobile terminated short message to the servicing MSC or SGSN.
If both numbers MSC and SGSN are received from HLR as routing information, the SMS-GMSC may choose which path (SGSN or MSC) first the SMS is to be transfered.
If an LMSI has been provided in the MAP_SEND_ROUTING_INFO_FOR_SM confirmation, it can be included in the sm-RP-DA information field of the first MAP_MT_FORWARD_SHORT_MESSAGE request sent to the servicing MSC. In this case, the IMSI must be included in the Destination Reference of the MAP_OPEN request. If the LMSI is not sent by the SMS Gateway MSC, the sm-RP-DA information field in the first MAP_MT_FORWARD_SHORT_MESSAGE request sent to the servicing MSC or SGSN shall contain the IMSI and the Destination Reference in the MAP_OPEN request shall not be present. The Service Centre address is sent in the parameter SM_RP_OA. The More Messages To Send flag is set to TRUE or FALSE depending on the information received from the Service Centre.
If the GMSC is the servicing MSC then the MAP service is not initiated. The procedure in the Servicing MSC is described in subclause 23.3.1 and in the figure 23.3/4.
If the grouping of MAP_OPEN request and MAP_MT_FORWARD_SHORT_MESSAGE request together would need segmenting, these primitives must not be grouped together. The MAP_OPEN request primitive is sent first without any associated MAP service request primitive and the dialogue confirmation must be received before the MAP_MT_FORWARD_SHORT_MESSAGE request is sent.
As a response to the procedure, the GMSC will receive the MAP_MT_FORWARD_SHORT_MESSAGE confirmation indicating:
– a successful forwarding of the short message. This indication is passed to the SC;
– unsuccessful forwarding of the short message:
In case only one number (MSC or SGSN) was received from HLR as routing information,the mapping of the MAP error causes and the RP_ERROR causes is explained in TS GSM 03.40. The appropriate error indication is sent to the SC.
In case both numbers (MSC and SGSN) were received from HLR as routing information, the transfer of SMS is re-attempted towards the second path only when one of the following errors is received from the unsuccessful transfer over the first path:
Facility Not Supported
Absent Subscriber with indication: GPRS or IMSI Detach
Unexpected Data Value
Subscriber Busy for MT SMS: GPRS Connection Suspended,
otherwise, the mapping of the MAP error causes and the RP_ERROR causes is performed (see TS GSM 03.40) and the appropriate error indication is sent to the SC.
If second forwarding of short message is unsuccessful, the mapping of the MAP error causes and the RP_ERROR causes is explained in TS GSM 03.40. The appropriate error indications are sent to the SC.
If second forwarding of short message is successful, the successful indication is passed to the SC.
A provider error is indicated as a system failure error to the SC.
The GMSC invokes the procedure MAP_REPORT_SM_DELIVERY_STATUS, if an absent subscriber_SM, an unidentified subscriber or SM delivery failure with error cause MS memory capacity exceeded indication is received from the servicing MSC, SGSN or both, and the corresponding flags received in the MAP_INFORM_SC are not already set or the SC address is not yet included in the MWD set.
If absent subscriber diagnostic information (see GSM 03.40) is included with the absent subscriber_SM error indication then this information is relayed to the HLR using the procedure MAP_REPORT_SM_DELIVERY_STATUS.
In case the SMS was attempted to be delivered towards the MSC and the SGSN, and both delivery failed with causes described above, the two unsuccessful SMS delivery outcomes for GPRS and non GPRS are sent to the HLR.
In case the SMS was attempted to be deliverd towards the MSC and the SGSN, and the first delivery failed with causes described above and the second delivery succeeded, the unsuccessful and successful SMS delivery outcomes for GPRS and non GPRS are sent to HLR.
The gateway MSC may also invoke the procedure when the first SMS delivery was successful towards MSC, if the MNRF, MCEF flags or both were set in the HLR.
The gateway MSC may also invoke the procedure when the fisrt SMS delivery was successful towards SGSN, if the MNRG, MCEF flags or both were set in the HLR.
This procedure is described in detail in subclause 23.5.
Unexpected data value, system failure errors are indicated as a system failure to the SC. Other errors are indicated using appropriate cause values and diagnostic information between the GMSC and the SC as described in TS GSM 03.40 and GSM 04.11.
The unidentified subscriber error is indicated to the SC as absent subscriber with diagnostic information set to ‘Unidentified subscriber’ as described in TS GSM 03.40.
Note that the indication, on which number belongs the SGSN and MSC, received from the HLR at routing information result (see subclause 23.3.3) will enable the GMSC to map the causes received from the SGSN, MSC or both into the appropriate causes for non GPRS, GPRS or both, and send them to the SC and HLR.
If there are more short messages to send in the Service Centre and the previous short message transfer succeeded, then the gateway MSC awaits the next short message.
When receiving the next short message from the SC, the gateway MSC sets the More Messages To Send flag according to the information received and starts the service MAP_MT_FORWARD_SHORT_MESSAGE again.
If the gateway MSC is the servicing MSC, then the short message transfer to mobile subscriber is started as described in the subclause 23.3.1.
The mobile terminated short message transfer procedure in the gateway MSC is shown in figure 23.3/7.
Figure 23.3/7 (sheet 1 of 6): Procedure MT_SM_GMSC
Figure 23.3/7 (sheet 2 to 6): Procedure MT_SM_GMSC
Figure 23.3/7 (sheet 3 of 6): Procedure MT_SM_GMSC
Figure 23.3/7 (sheet 4 of 6): Procedure_MT_SM_GMSC
Figure 23.3/7 (sheet 5 to 6): Procedure MT_SM_GMSC
Figure 23.3/7 (sheet 6 of 6): Procedure MT_SM_GMSC
Figure 23.3/8: Macro Check_Subscr_Identity_For_MT_SMS