Difference between revisions of "ReportSM-deliveryStatus"

Latest revision as of 17:20, 27 August 2013

[edit] Usage

This operation is used between the gateway MSC and the HLR. It sets the Message Waiting Data into the HLR or informs the HLR of a successful SM transfer after polling. This service is invoked by the gateway MSC.

[edit] Invoke parameters

This operation has the following invoke parameters:

• msisdn - ISDN number assigned to the mobile subscriber.
• serviceCentreAddress - the address of the SMSC.
• sm-DeliveryOutcome - indicates the cause for setting the Message Waiting Data in the mobile terminated SM delivery. It can have one of the following values: memoryCapacityExceeded, absentSubscriber, successfulTransfer.
• absentSubscriberDiagnosticSM - indicates the reason why the subscriber is absent.
• extensionContainer
• gprsSupportIndicator - indicates that the MSC supports GPRS specific procedure of combine delivery SM via MSC and/or via the SGSN.
• deliveryOutcomeIndicator - indicates that the delivery outcome sent to the HLR is for GPRS.
• additionalSM-DeliveryOutcome - this parameter is used to indicate the GPRS delivery outcome in case a combination between delivery outcome for GPRS and non-GPRS are sent to the HLR
• additionalAbsentSubscriberDiagnosticSM - indicates the reason why the subscriber is absent.
• ip-sm-gw-Indicator - indicates by its presence that sm-deliveryOutcome is for delivery via IMS.
• ip-sm-gw-sm-deliveryOutcome - is used to indicate the delivery outcome for the IMS domain. It can have one of the values liste for sm-DeliveryOutcome.
• ip-sm-gw-absentSubscriberDiagnosticSM - indicates the reason why the subscriber is absent.

[edit] Result parameters

This operation does expect a result. It can have one of the following parameters:

• storedMSISDN - - the stored MSISDN in the Message Waiting Data file.
• extensionContainer

[edit] Possible errors

• dataMissing
• unexpectedDataValue
• unknownSubscriber
• messageWaitingListFull

[edit] Example

 <component remoteCID="1" type="Invoke" operationCode="reportSM-DeliveryStatus">
   <msisdn nature="international" plan="land-mobile">19786148973</msisdn>
   <serviceCentreAddress nature="international" plan="land-mobile" enc="e212">89379726071</serviceCentreAddress>
   <sm-DeliveryOutcome>successfulTransfer</sm-DeliveryOutcome>
   <absentSubscriberDiagnosticSM>2</absentSubscriberDiagnosticSM>
   <gprsSupportIndicator/>
   <deliveryOutcomeIndicator/>
   <additionalSM-DeliveryOutcome>absentSubscriber</additionalSM-DeliveryOutcome>
   <additionalAbsentSubscriberDiagnosticSM>5</additionalAbsentSubscriberDiagnosticSM>
   <ip-sm-gw-Indicator/>
   <ip-sm-gw-sm-deliveryOutcome>memoryCapacityExceeded</ip-sm-gw-sm-deliveryOutcome>
   <ip-sm-gw-absentSubscriberDiagnosticSM>6</ip-sm-gw-absentSubscriberDiagnosticSM>
 </component> 
 ...
 <component localCID="1" type="ResultLast" operationCode="reportSM-DeliveryStatus">
   <storedMSISDN nature="international" plan="land-mobile">19786148973</storedMSISDN>
 </component> 

[edit] References

• ETSI TS 129 002 V10.6.0 (2012-04) p.342