Detailed Error Information

CR SMSC_2002_043

Sergey Marin
Consultant

Welcome to LogicaCMG

16 January 2016

Purpose

Provide fine-grained error information for the following message

retry functions:
Usual SMSC retry
Error Dependent Retry (CR SMSC_1998_107)
Intelligent retry
Catch-all routing (a retry via an SMPP gateway,
CR SMSC_2002_175)

Welcome to LogicaCMG

16 January

What we have changed

We changed error codes returned in case of an unsuccessful

MT delivery attempt to the GSM PLMN
Before in place of errors covered by this change the GIW
returned System Failure to the DIWGSM
In place of this System Failure we provided detailed error codes

Welcome to LogicaCMG

16 January

How it works

An error occurs either in the network or in the GIW

The GIW generates an error code (either from the existing
codes or from the codes we added)
The GIW sends this error code to the DIWGSM
The DIWGSM maps the error code using the ppl_nerr.txt file
(we have updated this file with new error codes) to the MERR
and MSTA values
The DIWGSM sends mapped MERR and MSTA to the SMH
The SMH makes a decision what to do with the message

Welcome to LogicaCMG

16 January

Error code classes

The return cause in an (ITU, ANSI or China)

UDTS/XUDTS/LUDTS SCCP packet
Refuse reason in MAP-Open confirm packet
Provider error in MAP confirm primitives for MAP SMS
management services
User error in MAP confirm primitives for MAP SMS management
services (already existed, not changed)
Problem diagnostic in MAP-Notice
Provider reason in MAP-P-Abort
Combination of user reason and diagnostic info in MAP-U-Abort,
MAP version1
Combination of user reason and diagnostic info in MAP-U-Abort,
MAP version 2 or higher

Welcome to LogicaCMG

16 January

MAP-U-Abort V1 and V2

This abort occurs if an error takes place on the MAP user level
Examples of MAP users
An HLR application (over GSM MAP)
An MSC application (over GSM MAP)

User reason and diagnostic info provide abort reason and

additional information
The GIW maps both these values to one value that is forwarded
to the DIWGSM

Welcome to LogicaCMG

16 January

MAP-P-Abort

This abort occurs if an error takes place on the MAP Provider

level
It can be a local SMSC MAP provider (the one the GIW uses)
or a remote MAP provider (on other network node)
Parameter Provider Reason indicates abort reason=error code
The GIW maps the value it receives from the network to the
Nerr value that is forwarded to the DIWGSM

Welcome to LogicaCMG

16 January

MAP-Open confirm

Failed MAP open dialogue attempt (on MAP Provider)

Refuse reason contains the error code
The error code can indicate MAP version incompatibility:
Application context not supported (never returned to the DIWGSM
because it triggers MAP version fallback V3->V1)
Potential version incompatibility
If (MAP Version==2) triggers fallback and is not returned to the
DIWGSM
If (MAP Version==1) is returned to the DIWGSM (mapped to
Nerr by the GIW)

Welcome to LogicaCMG

16 January

MAP-Open confirm

Failed MAP open dialogue attempt (on MAP Provider)

Refuse reason contains the error code
The error code can also be
Invalid originating reference
Invalid destination reference
No reason provided

The originating/destination reference are checked by a remote

MAP provider
The MAP provider generates a negative confirmation if a
reference is not correct

Welcome to LogicaCMG

16 January

MAP-Open confirm Important

If an UDTS error occurs as a result of MAP request the GIW

receives TC-NOTICE.ind
If
MAP dialogue not established AND
MAP-Open.req sent AND
No MAP-Open.cnf received
GIW MAP user receives TC-NOTICE.ind

this TC-NOTICE.ind according to MAP Spec must be

mapped to MAP-Open.cnf, refuse reason = Remote node
not reachable
So all UDTS return causes must be mapped to Remote node
not reachable in this case and therefore lost

Welcome to LogicaCMG

16 January

MAP-Open confirm Important

We decided not to do that!

If an UDTS error occurs when a MAP dialogue is not
established yet the GIW maps the UDTS return cause=error
code to a Nerr value and forwards it to the DIWGSM
In this way we do not loose the UDTS error info!

Welcome to LogicaCMG

16 January

UDTS/XUDTS/LUDTS SCCP packet

If a MAP dialogue is already established the TC-NOTICE.ind

resulting from an UDTS packet is mapped to the MAPNotice.ind.
The GIW maps Problem diagnostic parameter of the MAPNotice.ind (containing UDTS return cause) to a Nerr value
The GIW forwards the Nerr value to the DIWGSM

Welcome to LogicaCMG

16 January

UDTS/XUDTS/LUDTS SCCP packet

One important example of an UDTS return cause is No

translation for this specific address or No translation for an
address of this kind
This cause indicates that the PLMN on the SCCP level could not
perform a translation for a specific recipient address, the
translation is not defined
This situation can occur if, for example, an SRI request is sent to
a range that is not covered by any HLR in the network:
If we need to send a message to another country we often do not
know whether certain address belongs to a mobile or to a fixed
network
If the recipient belongs to a network which is not SS7
interconnected with the current network (e.g. other technology
network: TDMA, CDMA)

Welcome to LogicaCMG

16 January

UDTS/XUDTS/LUDTS SCCP packet

Why the example of an UDTS return cause No translation for

this specific address is important (scenario 1):
There are clients that allow people from the whole world to send
the SMS messages via their SMSC. These messages are often
sent to the recipients in different countries.
It is not always possible to check for a message that goes to
another country whether the recipient address is correct
If the address is not correct we do not want to retry
If we receive an UDTS error code in MAP-Open.cnf we know that
we do not have to retry

Welcome to LogicaCMG

16 January

UDTS/XUDTS/LUDTS SCCP packet

Why the example of an UDTS return cause No translation for

this specific address is important (scenario 2):
There are countries where subscribers can switch from one mobile
technology (e.g. GSM) to another (e.g. CMDA) while keeping their
number (Mobile Number Portability)
The SMSC tries the message to the GSM network first
The GSM network can be configured such that it returns an UDTS
packet with the cause No translation for this specific address or
No translation for an address of this kind if it find out the the
subscriber is ported out to the network of another technology
In this case the SMSC can retry the message via an SMPP
connection, for example
It can also be used in more general scenario when a GSM
subscriber sends a message to a CDMA subscriber, for example.

Welcome to LogicaCMG

16 January

MAP Confirm primitives,

Provider Error
Optional parameter in following confirmation primitives the GIW
can receive in MT scenarios:
MAP-SEND-ROUTING-INFO-FOR-SM.confirm
MAP-MT-FORWARD-SHORT-MESSAGE.confirm
MAP-REPORT-SM-DELIVERY-STATUS.confirm

Indicates provider errors occurred while handling a

corresponding request primitive
The error info from MAP-REPORT-SM-DELIVERYSTATUS.confirm is not forwarded to the DIWGSM
Examples of errors:
No response from the peer (~Timeout)
Service not supported (other party does not support the MAP
operation requested)

Welcome to LogicaCMG

16 January

MAP Confirm primitives,

User Error
Compulsory parameter in following confirmation primitives the GIW
can receive in MT scenarios:
MAP-SEND-ROUTING-INFO-FOR-SM.confirm
MAP-MT-FORWARD-SHORT-MESSAGE.confirm
MAP-REPORT-SM-DELIVERY-STATUS.confirm

Indicates user errors occurred while handling a corresponding request

primitive
The error info from MAP-REPORT-SM-DELIVERY-STATUS.confirm is
not forwarded to the DIWGSM
Examples of errors:
Unknown Subscriber (subscriber is not registered)
Absent Subscriber_SM (e.g. subscriber is not reachable)
Teleservice Not Provisioned (e.g. subscriber is not allowed to receive
SMS)

Welcome to LogicaCMG

16 January

Configuration
You can enable/disable this functionality by means of an O&M
attribute GIW_COMMON/SS7_ERR_DETAIL_ENABLED.
You do not have to restart the GIW. The change is effective for
the next following delivery or SRI request.
If the functionality is disabled all these error codes are mapped
to the System_Failure (old behaviour).

Welcome to LogicaCMG

16 January

Configuration (Important)
Before the change the GIW provided the indication whether the
MAP confirm primitives provider errors originated from an HLR
or an MSC (the errors itself were not provided).
If the functionality is enabled the GIW provides the provider
errors, however it is not possible anymore to say from what kind
of a network node the error comes.
If the functionality is disabled the GIW keeps the old behaviour
as described in bullet one.

Welcome to LogicaCMG

16 January

Backwards compatibility
The values of the new error codes between the GIW and the
DIWGSM require two bytes
The b_status field of the IOS used to transport these codes is
one byte long
We could not change the IOS interface: it is a patch
The GIW compresses the two byte error codes into one byte
The DIWGSM decompresses the codes before it maps them
against the ppl_nerr.txt file

Welcome to LogicaCMG

16 January

Tracing
In the IOS trace you will see the compressed codes
The GIW traces the two byte (uncompressed) error as an SC
error
The mapped MERR and MSTA you can see in the IDI trace as
usual

Welcome to LogicaCMG

16 January

Additional information
Release note: SMSC_V04_61_012 (for release 4.6)
ATP: Option 11c
Design:
\\nlattp1sfs3\sys\project\smsc
\intern\team south\Project TS SMSC Baseline 5\08. project
deliverables\01. working documents\NA MNP\Design_UDTS_043_
01_Proposed_V3.doc
Requirements, requirements analysis and change request
description (CR SMSC_2002_043):
http://telecomi/teams/smsc_req/SMSC/Baseline 4.htm

Welcome to LogicaCMG

16 January

Questions

Welcome to LogicaCMG

16 January