Content for TS 23.040 Word version: 18.0.0

0… 3… 3.3… 4… 8… 9… 9.2… 9.2.2.2… 9.2.2.3… 9.2.3… 9.2.3.12… 9.2.3.24 9.2.3.24.1… 9.2.3.24.10… 9.2.3.24.10.1.12… 9.2.3.24.10.2… 9.2.3.24.11… 9.2.3.25… 9.3… 10… 10.1.1… 10.1.3… 10.1.5… 10.1.7… 10.1.9… 10.1.11… 10.1.13… 10.1.15… 10.1.17… 10.2 10.2.1… 10.2.3… 10.2.5… 10.2.7… 10.3 11… A… C C.1… C.3… C.5… C.7… C.9… C.11… C.13… C.15… D… E… F… G… G.2… G.6 G.7 H… I… J… K…

11.1 Mobile Terminated short message transfer 11.2 Memory available notification 11.3 Mobile Originated short message transfer
...

11 Mapping of error causes between RP layers p. 142

This clause describes the interworking between the relay layers on the radio interface (i.e. between the servicing MSC/SGSN and the mobile station), and within the network (i.e. between servicing MSC/SGSN, VLR, HLR, or GMSC).

11.1 Mobile Terminated short message transfer p. 142

If errors are indicated by the VLR after invocation of the "sendInfoFor-MT-SMS" operation, the appropriate error information is returned to the SMS-GMSC in a failure report as specified in TS 29.002 (negative outcome of "forwardShortMessage" see clause 10).

If errors are detected by the MSC or by the SGSN during the transfer on the radio interface, or by the IP-SM-GW, the error cause returned in the return error of the MAP procedure ForwardShortMessage shall be set as follows:

Table 11.1-1

Failure at the MSC , SGSN or IP-SM-GW	Return error to be included in the MAP-proc
RP-ERROR message with error cause:
22 Memory capacity exceeded	SM_DeliveryFailure with cause "MemoryCapacityExceeded" (Note 1)
Other error causes	SM_DeliveryFailure with cause "equipmentProtocolError" (Note 1)
CP or lower layer error (e.g. RR, layer 2 failure) (Note 2)	SM_DeliveryFailure with cause "equipmentProtocolError" (Note 1)
Mobile has no SM capability	SM_DeliveryFailure with cause "equipmentNotSM-Equipped" (Note 1)
TR1N timeout (Note 2) MNSMS-error-ind (No SAPI 3)	SM_DeliveryFailure with cause "equipmentProtocolError" (Note 1)
SIP transaction timeout in IP-SM-GW	SM_DeliveryFailure with cause "absentSubscriber" (Note 1)
SIP transport error (e.g. SIP failure response message) (Note 3)	SM_DeliveryFailure with cause "equipmentProtocolError" (Note 1)
NOTE 1: For definition of MAP error SM_DeliveryFailure and its parameter "cause" see TS 29.002. NOTE 2: The error causes of the RP-ERROR message, the CP layer and timer TR1N are defined in TS 24.011. NOTE 3: The failure response codes for the SIP MESSAGE request are defined in IETF RFC 3428, and the failure response codes for SIP transaction timeout in IETF RFC 3261.

11.2 Memory available notification p. 143

If errors are indicated by the HLR (via the VLR, the IP-SM-GW, or the SGSN) after invocation of the "ReadyForSM" operation, the MSC, the IP-SM-GW, or the SGSN shall return the appropriate error information to the MS in a failure report (i.e. a RP-ERROR message) containing the following error cause:

Table 11.2-1

Return error from ReadyForSM (Alert Reason is "memory available")	Cause value in the RP-ERROR message
DataMissing UnexpectedDataValue UnknownSubscriber FacilityNotSupported System Failure	38 Network out of order 38 Network out of order 30 Unknown Subscriber 69 Requested facility not implemented 38 Network out of order
Local or lower layer failure (e.g. reject condition, timer expired or transaction abort)	38 Network out of order

11.3 Mobile Originated short message transfer p. 143

If errors are indicated by the VLR after invocation of the "sendInfoForMO-SMS" operation.(see clause 10), the MSC shall return the appropriate error information to the MS in a failure report (i.e. a RP-ERROR message) containing the following error cause:

Table 11.3-1

Return error from SendInfoForMO-SMS	Cause value in the RP-ERROR message
DataMissing	38 Network out of order
UnexpectedDataValue	38 Network out of order
TeleserviceNotProvisioned	50 Requested facility not subscribed
CallBarred
- barringServiceActive	10 Call barred
- operatorBarring	8 Operator determined barring

If errors are indicated by the SMS-IWMSC (negative outcome of the "forwardShortMessage"),) the MSC, the IP-SM-GW, or the SGSN shall send a failure report (i.e. a RP-ERROR message) to the MS, with the error cause coded as follows:

Table 11.3-2

Return error from ForwardShortMessage	Cause value in the RP-ERROR message
System Failure	38 Network out of order
FacilityNotSupported	69 Requested facility not implemented

UnexpectedDataValue	38 Network out of order

SM-DeliveryFailure cause: unknownSC	1 Unassigned number

SM-DeliveryFailure cause: SC-Congestion	42 Congestion

SM-DeliveryFailure cause: invalidSME-Addr (NOTE 1)	21 Short message transfer rejected

SM-DeliveryFailure cause: subscriberNotSC-Subscriber	28 Unidentified subscriber
Local or lower layer failure (e.g. reject condition, timer expired or transaction abort)	38 Network out of order
NOTE 1: This cause includes the case when the outcome of optional HLR interrogation is unacceptable (see clause 8.2.2)