Huawei SMS Procedures and Troubleshooting Training

Security Level: Internal use
only
SMS procedures and

trouble shooting training
ISSUE1.0
www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential

The training course introduce all kinds of
SMS procedures and data configuration and
trouble shooting related to these procedures.
HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 2

References
 3GPP TS 23.040
Technical realization of the Short Message Service (SMS)
 3GPP TS 24.011
Point-to-Point (PP) Short Message Service (SMS)
 3GPP TS 29.002
Mobile Application Part (MAP) specification

Upon completion this course, you will be able to:
 Deeply understand SMS procedure
 Deeply understand data configuration related to
SMS procedure
 Trouble shooting related to SMS service.

Chapter 1 SMMO procedure
Chapter 2 SMMT procedure
Chapter 3 Short Message Alert Procedure
Chapter 4 SM Alert procedure due to Call failure
Chapter 5 SMS flow control
Chapter 6 Messages related to SM through A interface
Chapter 7 SMS cases analysis

Chapter 1 SMMO procedure
1.1 SMMO Signaling Procedure
1.2 SMMO Processing in MSOFTX3000
1.3 Data Table Querying Sequence Related to SMMO
1.4 Standard Intelligent SMMO Signaling Procedure
1.5 None Standard Intelligent SMMO

1.1 SMMO signaling procedure
Signaling procedure for SMMO
SMC HLR VLR MSC UE
Map_pocess access req Cm service request

Auth and
Map_process access req ack
cipher
Auth and cipher
Cm service accept
Cp data(Rp data(sms submit))
Cp ack
Map_send_info_for_sms
Map_send_info_for_sms_ack
Map_mo_forward_short_message
Map_mo_forward_short_message_ack
Cp
ta(Rp ack(submit report))
da
Cp ack

1.1 SMMO signaling procedure
Message tracing result in MSOFTX3000 LMT for 3G SMMO

1.1 SMMO signaling procedure explanation
Message tracing result in MSOFTX3000 LMT for 2G SMMO

SMMO signaling procedure explanation
1) When mobile subscriber send a SMS it initiate a “CM SERVICE

REQUEST” message to MSC.CM Service type is “short
message service“ .The following authentication and cipher mode
procedure is optional. For authentication and cipher mode
procedure see related training slides.

2) MSC send CM SERVICE REQUEST ACCEPT to MS. If cipher

mode is initiated the service accept message will be replaced
with SECURITY MODE COMPLETE(3G) and CIPHER MODE
COMPLETE(2G)

3) After MS received CM SERVICE ACCEPT or finish cipher mode

procedure it send CP DATA to MSC via A/IU interface. If MSC
receive the CP DATA message it will reply CP ACK

Continue… CP DATA

CP ACK

4) After MSC receive CP DATA message from MS send
Map_send_info_for_sms to VLR and VLR return subscriber data.
MSC will check subscriber parameters and verify whether local office
support SMS service (SET MAPACCFG: ISSSMMO=YES;)
If MSC support SMMO MSC send Map_mo_forward_short_message to
SMS Center according to the SMS center number in the CP data
message.
If SMC receive the SMS it will reply Map_mo_forward_short_message
ack to MSC.

 5) After MSC receive Map_mo_forward_short_message ack it send CP

DATA to MS to inform MS that the SM has been sent to the SMC
successfully. MS reply CP ACK to MSC to confirm the message.
 CP DATA
 Successful result Failure
•CP ACK

1.2 SMMO processing in MSOFTX3000
1) When MSC receive CP_DATA from MS MSC will check the SMS center
number format first.
If the number is not a international number MSC will add local country
code in front of the number which is configured by command SET OFI.
The SMS center number modification function is controlled by software
parameter P190BIT9 since MSoftX3000 R003 version is issued. The
default value is true.
If shutdown the function MSC will send RP_ERROR to MS with cause
value " Invalid mandatory information " (value 96)
2) Check the “SET MAPACCFG” if “ISSSMMO=NO” or after check license
SMS service is not provided the MSC will send RP_ERROR to MS with
cause value " Facility rejected "（Value 29). Otherwise MSC will send
MAP_Send_information_for_SMS to VLR to request the subscriber’s
data.

3) After VLR return subscriber data MSC will check whether MS subscribe
the SMS service. If no MSC will send RP_ERROR to MS with cause
value” Requested facility not subscribed " (Value 50)
4) If MS subscribes SMS service then check whether MS subscribe the ODB
BAOC service .If yes it will send RP_ERROR to MS with cause value
“Operator determined barring” ; If MS has SS BAOC service MSC will
send RP_ERROR to MS with cause value “ Call barred ” （Value10）
5) If MS has no ODB BAOC service and has SS BOIC then check “SET
MAPPARA: RSTSMSCODBBOIC=YES;”. If true and SMS center number
or the destination number is a international number then MSC will send
RP_ERROR to MS with cause value “ Call barred ” （Value10）
6) If MS has no SS BOIC service and has ODB BOIC then check SET
MAPPARA: RSTSMSCODBBOIC=YES; If true and SMS center number
or the destination number is a international number then MSC will send
RP_ERROR to MS with cause value “ Call barred ” （Value10）

7) If no above restriction check “SET MAPPARA: SMMOBLACKTABLE=YES;”

If it is true and calling or called number is configured in “ADD DNSRVIDX:
SRVCAT=SMMO_BKLST1-1&SMMO_BKLST2-1, MNPRF=FALSE;” then
MSC will send RP_ERROR to MS with cause value “ Call barred ”
（Value10）
8) If no above restriction and local office support MAP Pahse2+ and CAMEL3,
MS has SMS-CSI then trigger intelligent SMS flow which will be
introduced at the following chapter.
9) If not trigger the IN SMS flow then check SET MAPPARA:
IMSICHGSMCADDR=YES; if it is true change the SMS center number
according to ADD MAPIFNP: CHGOPT=SMMO;
10) After all the above check query the SCCPGT translation table with SMS
center number if GT translation error then MSC will send RP_ERROR to
MS with cause value " Congestion" （Value 42) .If success MSC send
Map_mo_forward_short_message to SMSC

 11) If SMS center return error in Map_mo_forward_short_message ,MSC

will convert MAP error causes to A interface causes which is shown in
the following tables.
 12) If SMSC return Map_mo_forward_short_message_conf then gnerate
SMS CDR and send CP_DATA to MS to inform the MS that the SM sent
to SMSC successfully.
 NOTE: RP_DATA is a message on the up layer of CP_DATA. It is a

Short Message Relay Layer message.

MAP cause value to A interface cause value
MAP MAP A interface A interface

interface interface cause Cause value
cause cause value description
description
Facility Not 21 Requested 69

Supported facility not
implemented
Sm Delivery 32 -------- --------
Failure
System 34 Network out of 38

Failure order
Unexpected 36 Network out of 38
Data Value order

The reason of the SM Delivery Failure can be one of

the following in the mobile originated SM
Sm Delivery Sm Delivery A interface A interface
Failure Failure cause cause value
cause cause Value description
Description
Unknown 3 Unassigned 1
Service (unallocated)
Centre number
Sc Congestion 4 Resources 47
unavailable,
unspecified
Invalid SME 5 Short message 21
Address transfer rejected
Subscriber 6 Unidentified 28
Not SC subscriber
Subscriber

1.3 Data table querying sequence related to
SMMO
According to the previous chapter the data table querying sequence

is shown as below:
SET MAPACCFG
SET MAPPARA
ADD MAPIFNP
ADD DNSRVIDX
ADD SCCPGT

1.4 Standard Intelligent SMMO Signaling
Procedure
MS Servicing
VLR SCP SMC
MSC
Short Message
MAP_SEND_INFO_FOR_MO_SMS
MAP_SEND_INFO_FOR_MO_SMS_ACK
Initial DP SMS
Request Report SMS Event
Furnish Charging Information SMS
Connect SMS
Continue SMS
MAP_MO_FORWARD_SHORT_MESSAGE
MAP_MO_FORWARD_SHORT_MESSAGE_ACK
Event Report SMS(O_SMS_Failure or O_SMS_Submitted)

Standard Intelligent SMMO Signaling
Procedure processing in MOSFTX3000
The processing of first 8 steps for Standard intelligent SMMO signaling procedure is
same as normal SMMO processing. The following processing will be introduced
after Step 8 which is described in “1.2 SMMO processing in MSOFTX3000”.
8) If no above restriction and local office support MAP Pahse2+ and CAMEL3, MS has
SMS-CSI then trigger intelligent SMS flow
9) MSC send SMS IDP message to SCP according to the GT address defined in SMC-
CSI.
10) MSC send or reject SMS according to the indication of SCP.
If MSC receive release SMS from SCP then MSC send CP_DATA to MS with cause
“Network out of order (value 38)”
If MSC receive Connect SMS or Continue SMS and Request Report SMS Even
before that MSC will maintain intelligent relationship with SCP and continue
sending the SM.
If MSC receive Connect SMS or Continue SMS and does not receive Request
Report SMS Even before that MSC will release intelligent relationship with SCP
and continue sending the SM.
In Connect SMS message SCP can change the SMS Center number, calling
number and called number.

Continue….
11) MSC send Map_mo_forward_short_message to SMS center according to
the GT of SMS center.
12) If the intelligent relationship is over and SET MAPACCFG:
IFSUPCAMELSMSBILL=YES; MSC generate CDR.
Otherwise:
If MSC send the SM to SMSC successfully MSC send O_SMS_Submitted
Event Report SMS to SCP and terminate the intelligent relationship with
SCP. If SET MAPACCFG: IFSUPCAMELSMSBILL=YES; then generate
CDR. Otherwise MSC will not generate CDR.
If MSC fail to send the SM to SMSC, MSC send O_SMS_Failure Event
Report SMS to SCP and terminate the intelligent relationship with SCP. If
SET MAPACCFG: IFSUPCAMELSMSBILL=YES; and MOD GBILLCTRL:
BCF=SMS_FAIL-1; then generate CDR. Otherwise MSC will not generate
CDR.
13) In this follow SCP decide whether MSC send or reject the SMMO request
of MS. SCP decide whether generate CDR according to the SMSMO
report which is sent from MSC. There is no intelligent flow for SMMT.

1.4 None Standard Intelligent SMMO Signaling
Procedure
MS Servicing
VLR SCP SMC
MSC
Short Message
VP_VDB_GetCamelData_VLR_Req
VDB_VP_GetCamelData_VLR_Rsp
Initial DP(OCSI DP2)
Continue
release Call
MAP_MO_FORWARD_SHORT_MESSAGE_ACK
Short Message Acknowledgement

None Standard Intelligent SMMO Signaling
Procedure processing in MOSFTX3000
None standard intelligent SMMO signaling procedure apply 3 messages

Initial DP、Continue and release Call. It is only used in Pakistan for the
moment. The subscriber who has subscribe the O-CSI can trigger the
procedure.
MSC will not report SMS delivery status to SCP so if the SMMO fail SCP
still charge the subscriber.
As it is not so broadly applied only it is not a key point here.

Questions
 What’s the function of CP_DATA message? What’s the diffrence between
CP_ERROR and RP_ERROR?
 If SMMO procedure fail how to check the data configuration?
 What’s the difference of CONTINUE and CONNECT message in IN SMMO

flow?

Chapter 2 SMMT procedure
2.1 SMMT Signaling Procedure
2.2 SMMT Processing in MSOFTX3000
2.3 Data Table Querying Sequence Related to SMMT

SMC HLR VLR MSC UE
Map_send_routing_info_for_sm
Map_send_routing_info_for_sm_ack
map_mt_forward_short_message
Map_send_info_for_mt_sms
Map_send_info_for_sms_ack
Paging
map_process_req Paging response

map_process_req_ack
Auth and cipher
Auth and cipher
Cp data(Rp data(sms delivery))
Cp ack
Cp data(Rp ack)
Cp ack
map_mt_forward_short_message_ack


2.1 SMMT Signaling Procedure explanation
1) SMS center receive SM from MSC it will send
MAP_SEND_ROUTING_INFO_FOR_SM to HLR.
2) HLR return MAP_SEND_ROUTING_INFO_FOR_SM to SMS center with
number of MSC in which the called subscriber register. If any of the
following clause come into existence HLR will return error information to
SMS center.
 - Unknown subscriber;
 - Roaming not allowed
 -Call Barred;(BOIC)
 - Teleservice Not Provisioned;(SMS)
 -MNRF（Mobile-Station-Not-Reachable-Flag) is ture.
 MCEF（Mobile-Station-Memory-Capacity-Exceeded-Flag is ture
 Absent Subscriber_SM; (Puruged by VLR)
If the failure cause is that MNRF flag is true HLR will store the SMS
center number in HLR.

Continue…
3) SMS center send MAP_MT_FORWARD_SHORT_MESSAGE to MSC.
4) MSC send MAP_SEND_INFO_FOR_MT_SMS to VLR. If the called
subscriber status is absent, detach or it has no MT-SMS service MSC
will return error to SMS center and set MNRF flag to true.
5) If there’s no above problem MSC will send PAGING to BSC if no paging
response MSC will return error to SMS center and set MNRF flag to true.
6) If MSC receive paging response MSC will send CP_DATA which including
the SMS content to the MS. MS return CP_ACK to MSC.
7) MS send CP_DATA to MSC indicate that it received the SMS.
MSC return CP_ACK to MS.

8) MSC send MAP_MT_FORWARD_SHORT_MESSAGE to SMS center to
inform it the SM is sent to the called subscriber successfully.

Continue…
In step 7 if MS return RP-ERROR message to MSC with cause value

22 “Memory capacity exceeded” MSC will report SMS delivery failure
to SMS Center with cause value “Memory capacity exceeded” .If the
MS return other cause value MSC will report SMS delivery failure to
SMS Center with cause value “sm-DeliveryFailure(32)”
9) After SMS center receive MAP_MT_FORWARD_SHORT_MESSAGE
it will compare subscriber’s MNRF、MCEF with HLR if they are not
consistent then send MAP_REPORT_SM_DELIVERY _STATUS to
inform HLR update the subscriber’s MNRF and If the message
delivery fail it send MAP_REPORT_SM_DELIVERY_STATUS to
inform HLR to store the SMS center number.

2.2 SMMT Processing in MSOFTX3000
1) When MSC receive MAP_MT_FORWARD_SHORT_ MESSAGE, if

SET MAPACCFG: ISSSMMT=NO; and license does not support SMMT
then return message to SMS center with cause value 21 “facility Not
Supported”
2) If above checking is OK MSC send MAP_SEND_INFO_FOR_MT_SMS
to VLR. If the called subscriber is unknown or not confirmed by HLR
MSC will return error to SMS center with cause value “unidentified
Subscriber (5)”.
3) If the called subscriber status is absent, detach MSC will return error to
SMS center with cause value “absent subscriber SM (6)” and set
MNRF flag to true.
4) If the called subscriber status has not subscribe SMMT service or
subscriber is in the SMS blacklist MSC will return error to SMS center
with cause value “sm Delivery Failure(32)” and set MNRF flag to true.

Continue…
 5) If there’s no above problem MSC will send PAGING to BSC if

no paging response MSC will return error to SMS center and set
MNRF flag to true
 6) If MSC send CP_DATA to MS successfully it will generate
SMMT CDR.

2.3 Data Table Querying Sequence Related to
SMMT
According to the previous chapter the data table querying sequence

is shown as below:
SET MAPACCFG
SET MAPPARA
ADD MAPIFNP
ADD DNSRVIDX
ADD SCCPGT

Questions
 Why HLR need store the subscriber’s MNRF,MCEF and short message center
number? How HLR get these information?
 Describe the possible reason of SMMT failure in Msoftx3000.

Chapter 3 Short message Alert procedure
The Short Message Alert procedure is used for alerting the Service Centre when the mobile
subscriber is active after a short message transfer has failed because the mobile subscriber is
not reachable or when the MS has indicated that it has memory capacity to accept a short
message.
3.1 Short message alert procedure (Mobile is present)
3.2 Short message alert procedure (MS memory capacity available)
3.3 Short message alert procedure (Successful transfer after polling)

3.1 Short message alert procedure (Mobile is
present)
NOTE 1: To all Service Centres in the Message Waiting List.

NOTE 2: The HLR initiates the MAP_ALERT_SERVICE_CENTRE service only if the MS Memory
Capacity Exceeded flag is clear.

3.2 Short message alert procedure (MS
memory capacity available)
(NOTE)
NOTE: To all Service Centres in the Message Waiting List.

3.3 Short message alert procedure
(Successful transfer after polling)
NOTE: To all Service Centres in the Message Waiting List.

Chapter 4 SM Alert procedure due to Call failure
The Short Message Alert message service due to call failure is used for alerting the mobile
subscriber that it has missed a call because it is unreachable or busy or has no reply. The alert
short message including the calling subscriber and the call time.
4.1 SM Alert procedure due to Call failure (trigged in GMSC)
4.2 SM Alert procedure due to Call failure (trigged in VMSC)

4.1 SM Alert procedure due to Call failure
(trigged in GMSC)
MS (V)MSC (G)MSC HLR SMSC
SETUP
IAM
MAP_SEND_ROUTING_INFO_REQ
MAP_SEND_ROUTING_INFO_CNF
MO_FORWARD_SM_ARG
MO_FORWARD_SM_RES
When GMSC receive MAP_Send_routing_info_conf from HLR with cause value

”absent subscriber” GMSC will send MAP_MO_FORWARD_SHORT_MESSAGE
to SMSC to inform the called subscriber it has a missed call.

4.2 SM Alert procedure due to Call failure
(trigged in VMSC)
RNC/BS
(G)MSC (V)MSC
C
IAM
MS detach or
roaming restriction
Busy status decided

by network
PAGING
No response to
paging
SETUP
Wireless congestion
Alerting
No reply
VMSC will send alert message to the SMS center according to the
trigger point shown in the above figure

Questions
 Please describe the procedures in VMSC,HLR,SMSC in SM alert procedures.
 Describe the SM alert procedure due to call failure.

Chapter 5 SMS flow control
The purpose of The Short Message Service flow control is to prevent the CPU from overload
when heavy SMS traffic appear in MSOFTX3000.
To reduce the traffic for SMMO the best control point is at A interface.
To reduce the traffic for SMMT the best control point is at E interface.
5.1 SMMO Service flow control
5.2 SMMT Service flow control

5.1 SMMO Service flow control
MS MSC
CM_SERVICE_REQ
Check
Point
Every CCU/CSU module set a global variable to count the SMMO messages. If the result
exceed the number which is configured by command ADD SERVCTRLCFG(NOTE) MSC
will reject the CM_SERVICE_REQ from the MS with cause value ”End user congestion”
To monitor the SMMO traffic control the following traffic measurement tasks should be
registered in MSOFTX3000:
MSC Basic Service Measurement ->Traffic Measurement For SMS->SMMO Success Times
MSC Basic Service Measurement ->Traffic Measurement For SMS->SMMO Times

5.2 SMMT Service flow control
SMC MSC
MAP_MT_FORWARD_SHORT_M
ESSAGE
Check
point
Every CCU/CSU module set a global variable to count the SMMT messages. If the result
exceed the number which is configured by command ADD SERVCTRLCFG(NOTE) MSC
will reject the MAP_MT_FORWARD_SHORT_MESSAGE from the SMC with cause value ”
ressource limitation (congestion) ”
To monitor the SMMT traffic control the following traffic measurement tasks should be
registered in MSOFTX3000:
MSC Basic Service Measurement ->Traffic Measurement For SMS->SMMT Success Times
MSC Basic Service Measurement ->Traffic Measurement For SMS->SMMT Times

Chapter 6 Messages related to SM through A interface
6.1 SMMO messages through A interface
6.2 SMMT messages through A interface
6.3 MS memory available notification procedure

6.1 SMMO messages through A interface

Continue….
 After service request procedure :
MS send first CP_DATA with RP_DATA which imply SMS content to

MSC.
CP_ACK message is a response to CP_DATA.
MSC send CP_DATA to inform the MS that the SM has been
forwarded to the SMC successfully.

6.1 SMMT messages through A interface
After Paging procedure :

Network send CP_DATA imply SM content to MS
MS reply CP_ACK to CP_DATA.
After MS stored the message in the memory it send CP_DATA to MSC
to inform that MS has received the SM successfully.

6.3 MS memory available notification
procedure
The procedure is same as SMMO procedure . The difference is the SM RP layer

message in CP_DATA message sent to MSC.
In SMMO flow it is a RP_DATA message.
In memory available notification procedure it is a RP_SMMA message.
For detailed information see 3gpp. 24011

Chapter 7 SMS cases analysis
When MS send SM it cancel the operation immediately. Then the
SM has been sent successfully to destination address but
SCP has not charge the SMMO.
MS Servicing
VLR SCP SMC
MSC
CP_DATA
CP_ACK
Initial DP SMS
Request Report SMS Event
Furnish Charging Information SMS
Continue SMS
CP_ERROR
U_ABORT
U_ABORT
clear_command
clear_complete

Continue….
From the above signaling flow:

After MS send CP_DATA to MSC it initiate CP_ERROR to cancel the SMMO
flow. Then MSC send U-ABORT to SCP and SMC. SCP terminate the
SMMO flow and will not charge the subscriber which initiate the SMMO.
The problem is MSC maybe have received the MAP_FOWARD_SM_ACK
from the SMC so that the U_ABORT message has not been sent to the
SMC successfully.
To resolve the problem MSC forbidden MS to send CP_ERROR after
service request procedure.
This problem has already fixed since version MSOFTX3000
V100R003C01B051

Summary
 This training course introduce the SMMO flow,

intelligent SMMO flow and SMMT flow in detail
and also the related data configuration tables
to help the troubleshooting of the SM problem
in MSOFTX3000.

Thank You
www.huawei.com

Huawei SMS Procedures and Troubleshooting Training

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Huawei SMS Procedures and Troubleshooting Training

Caricato da

Copyright:

Formati disponibili

Security Level: Internal use

SMS procedures and

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 2

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 3

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 4

Chapter 2 SMMT procedure

Chapter 3 Short Message Alert Procedure

Chapter 4 SM Alert procedure due to Call failure

Chapter 5 SMS flow control

Chapter 6 Messages related to SM through A interface

Chapter 7 SMS cases analysis

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 5

1.1 SMMO Signaling Procedure

1.2 SMMO Processing in MSOFTX3000

1.3 Data Table Querying Sequence Related to SMMO

1.4 Standard Intelligent SMMO Signaling Procedure

1.5 None Standard Intelligent SMMO

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 6

SMC HLR VLR MSC UE

Map_pocess access req Cm service request

Cp data(Rp data(sms submit))

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 7

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 8

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 9

1) When mobile subscriber send a SMS it initiate a “CM SERVICE

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 10

2) MSC send CM SERVICE REQUEST ACCEPT to MS. If cipher

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 11

3) After MS received CM SERVICE ACCEPT or finish cipher mode

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 12

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 13

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 14

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 15

 5) After MSC receive Map_mo_forward_short_message ack it send CP

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 16

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 17

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 18

7) If no above restriction check “SET MAPPARA: SMMOBLACKTABLE=YES;”

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 19

 11) If SMS center return error in Map_mo_forward_short_message ,MSC

 NOTE: RP_DATA is a message on the up layer of CP_DATA. It is a

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 20

MAP cause value to A interface cause value

MAP MAP A interface A interface

Facility Not 21 Requested 69

System 34 Network out of 38

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 21

The reason of the SM Delivery Failure can be one of

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 22

According to the previous chapter the data table querying sequence

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 23

Request Report SMS Event

Furnish Charging Information SMS

Event Report SMS(O_SMS_Failure or O_SMS_Submitted)

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 24

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 25

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 26

Initial DP(OCSI DP2)

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 27

None standard intelligent SMMO signaling procedure apply 3 messages

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 28

 What’s the difference of CONTINUE and CONNECT message in IN SMMO