Handling of SMSMT

3 Handling of the short message mobile
terminated service
3.1
© Alcatel University - 8AS 90200 0830 VT ZZA Ed.01
© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.1

3 Handling of the short message mobile terminated service
Session presentation
▼ Objective: to be able to solve a problem related to

the short message mobile terminated service
3.2

▼Program : HANDLING OF THE SHORT MESSAGE MOBILE TERMINATED SERVICE Page
3.1 Short message mobile terminated service scenario

Handling of the short message mobile terminated service 6
Data and flags associated with the service 7
Subscriber short message delivery 9
Delivery of several consecutive SMS to a subscriber 21
Alert procedure 25
Interactions with other services 32
3.2 Data structure

F_SMS_001 34
F_SMS_002 35
F_SMS_003 36
F_SMS_004 37
F_SMS_006 38
F_SMS_007 39
F_GPRS_002 40
F_GPRS_003 41
3.3 SMS-MT handling procedure

SMS delivery procedure at the HLR 44
SMS status report procedure at the HLR 48
Alert procedure at the HLR 51
Send information for SMT at the VLR 53
MS ready for SMT at the VLR 55
Handling procedure at the RCF of the GMSC 56
Report SM delivery at the RCF of the GMSC 64
Handling procedure at the RCF of the VMSC 65
Alert procedure at the RCF of the IWMSC 69
Evaluation 73

▼ Page intentionally left blank

3.1 short message mobile terminated service scenario
3.5

Handling of the short message mobile terminated service
The SMS_MT procedure is used to deliver a short message (TPDU) to a mobile,
and to deliver a short message delivery status report to a recipient for an earlier
SMS_MO procedure.
As with the SMS_MO service, several short messages can also be handled in
sequence in the same transaction with the short message server and the same
mobile connection. A call ticket is generated, containing the number of messages
delivered in addition to the SMS_MT service provision indication.
The SMS_MT procedure must therefore:
z perform all the actions needed to set up a transaction to transfer the
short message from the SC to the mobile station,
z transfer the short message,
z handle errors during setup of the transaction and during the transfer,
z inform the SC of the transfer result.
The components of the PLMN must also, when necessary, provide the alert
procedure. This procedure informs the SC that the mobile station is available
again or, that it has regained sufficient memory capacity to receive the short
messages that are waiting in the SC.
3.6

Data and flags associated with the service
HLR VLR
MNRF MCEF MNRF
MNRR
MS_ISDN Alert MWD SC address n
3.7
DATA AND FLAG ASSIOCIATED WITH THE SERVICE

Definition of flags:
MNRF : Mobile station Not Reachable Flag.
This flag is present in the HLR and VLR. When set, it indicates that an attempt to deliver a short message to a subscriber has
failed. The reason is "absent subscriber".
MNRR : Mobile Not Reachable Reason.
This field gives the reason for the "subscriber absence" when an attempt to deliver short messages has failed:
• Paging failure
• IMSI "detached”
• Subscriber not identified at the VMSC
• MS under roaming restriction (national roaming, regional roaming, etc)
MCEF: mobile station Memory Capacity Exceeded Flag.
This flag indicates that the MWD list contains at least one element because an attempt to deliver a short message to the
subscriber has failed due to memory capacity being exceeded.
MWD : Message Waiting Data.
MS_ISDN alert : MS_ISDN to be sent to the SCs concerned during an alert procedure. Value used by the SC for a repeat
attempt to deliver a short message after a failure.
SC address n : Addresses of the SCs that have short messages waiting to be delivered to a mobile station.
Data in the VLR's RTDMS database
Data associated with the MNRF parameter:
• Relation: WYR_TPTR
• Attribute: D_FLTPTR
Î Indicator: if D_MNRF = true, the mobile is unreachable,
if D_MNRF = false, the mobile is reachable.

Data in the HLR's RTDMS database
Data concerning the SMS
• Relation: HYR_MWD
• Attribute:
• HY_MSROW HYM_K_TUP /*Row of the subscriber in the relation HYR_MS*/
• HY_T_RSC HYM_T_RSC /*Table of the row-id of the HYR_SCA's tuples linked to a subscriber*/
Row1 Row2 Row3 Row4 Row5 Row6 Row7
• HY_T_ASC HYM_T_ASC /*Table of "time-stamping" of the addresses of the service centres linked to a
subscriber.*/
Time- Time- Time- Time- Time- Time- Time-

stamping 1 stamping 2 stamping 3 stamping 4 stamping 5 stamping 6 stamping 7
day-hour day-hour day-hour day-hour day-hour day-hour day-hour
• Relation: HYR_LMS
• Attribute:
• HY_VLR_I HYM_VLR_N /*Address of the VLR where the subscriber has been located*/
• HY_LMSI HYM_LMSI /*Local identifier of a mobile, parameter registered on location updating*/
• HY_MSC_I HYM_MSC_N /*ISDN number of the MSC*/
• HY_LMS_F HYM_LMS_FLAGS /*Restoration and location flags:
MNRF (HY_MNRF) bit 13 bool

True: MS not reachable for SMS
False: MS reachable for SMS
MCEF (HY_MCEF) bit 14 bool
True: SMS memory capacity exceeded
False: SMS memory capacity not exceeded
MNRR (HY_MNRR): bit 15, 16, 17:
000 Not set
001 No paging response
010 Detach
011 Unidentified subscriber via the MSC
100 and 111 not used

Subscriber short message delivery (1/4)
VMSC
MS
SC SMS-GMSC HLR RCF VLR
BSS
CONNECTION_REQUEST
CONNECTION_CONFIRMED
DATA_FORM 1 (RP_MT_DATA)
SEND_ROUTING_INFO_FOR_SM_INV
S_RGI_SM_I
SEND_ROUTING_INFO_FOR_SM_RES
S_RGI_SM_R
INFORM_SERVICE_CENTRE
I_SC_I
3.9
SUBSCRIBER SHORT MESSAGE DELIVERY (1/4)
When the connection has been established between the SC and the SMS-GMSC, the Service Centre sends the SMS-GMSC the
DATA_FORM 1 information containing the first short message in the RP_MT_DATA field.
The SMS_MT procedure then begins at the GMSC with verification of the content of the RP_MT_DATA message.
• If an error is detected, the GMSC informs the SC by sending it a DATA_FORM 1 message containing the nature of
the error in the RP_MT_Error field.
• Otherwise, the procedure continues normally. The GMSC asks the HLR to send it the necessary information
concerning the subscriber to be reached: S_RGI_SM_I.
At the HLR, when functional option F_SMS_006 is enabled ("HLR protection against optimal routing for SMS_MT"), the message
is rejected if the SMS_GMSC does not belong to the HPLMN. The TC_REJECT message is sent to the SMS_GMSC in phase 1.
If the dialogue between the SC and SMS_GMSC is in phase 2, the HLR returns a TC_U_ABORT.
If the procedure must be handled, the HLR checks:
1) the validity of the fields in the received S_RGI_SM_I message,
2) that the mobile station can be identified from its MS_ISDN,
3) that the MS is not blocked or restricted by ODB,
4) that the subscriber has subscribed to the SMS_MT service,
5) that the MS is located,
6) that the VMSC in which the subscriber is located supports the SMS_MT function (flag),
7) that the subscriber has no roaming restrictions.
If one of these conditions is not met, the HLR notifies the GMSC with the S_RGI_SM_E message giving the cause of the failure.
In cases 5, 6 and 7, the cause is "absent subscriber".
If all the conditions are met, the HLR then checks the priority of the message. For this, functional option F_SMS_004 ("Handling
in HLR of the priority on SM delivery") must be enabled. The SM_RP_PRI parameter of the S_RGI_SM_I message is analysed.

The HLR responds to the SMS_GMSC with the S_RGI_SM_R message if:
• the short message has priority (even if the MNRF and MCEF flags are set in the HLR)
• the message does not have priority and the MNRF is not set in the HLR.
the HLR replies to the SMS_GMSC with the S_RGI_SM_E message "Send Routing Information for Error", if:
• the message does not have priority and the MNRF flag is set in the HLR.
• if option F_SMS_004 is not enabled, the SM_RP_PRI parameter is ignored and the message considered non priority.
When the response from the HLR to the SMS_GMSC is S_RGI_SM_E with "absent subscriber" as the cause, the HLR adds the
SC's address to its MWD list, providing that the address is not already in the list and the list is not full. The HLR never sets the
MNRF in this case. The MNRF is set only when the subscriber is unreachable at VMSC level.
If the dialogue between SMS_GMSC/HLR is in MAP V1, the HLR inserts an mwd_set parameter indicating whether it has added
the SCs' address to its MWD list in the "S_RGI_SM_R" or "S_RGI_SM_E" message with "Absent subscriber" as the error cause.
In MAP >V 1, the HLR sends the I_SC_I message:
After sending S_RGI_SM_E with "Absent subscriber" as the error cause. The message contains the mw_status parameter and
the MS_ISDN_Alert if it is different from the MS_ISDN received in the "Send Routing Information for SM invoke" message.
After sending the S_RGI_SM_R message if:
• The MNRF and/or MCEF is set: the message then includes the mw-status parameter with its mnrf_set and/or
mcef_set fields set. The SC_AddressNotIncluded parameter is set if the SC's address is not in the MWD list.
• The MS_ISDN contained in S_RGI_SM_I is different from the MS_ISDN alert. The I_SC_I message then contains the
MS_ISDN_Alert.
At the SMS_GMSC, if:
• The message received is S_RGI_SM_R, the routing information is available and the short message delivery
procedure continues.
• The message received is S_RGI_SM_E, the SMS_GMSC informs the SC of the procedure failure via the
DATA_FORM 1 message which contains RP_MT_Error as the user data parameter.

VMSC
MS
BSS
F_SM_I or MT_F_SM_I*
FORWARD_SHORT_MESSAGE_INV
TC-BEGIN
SINF_SMT_I
SEND_INFO_FOR_SMT_INV
PAGING
SECURITY
IMEI CHECK
COM_SMT_I
COMPLETE_SMT_INV
RADIO CONNECTION
RELEASED END OF IMEI CHECK SUCCESSFULLY PERFORMED
CP_DATA (RP_DATA)
CP_ACK
CP_DATA (RP_ACK)
CP_ACK
F_SM_R or MT_F_SM_R*
FORWARD_SHORT_MESSAGE_RES
TC-END
* In MAP V3
3.11

F_SM_I (MAP V1 & V2 ”Forward short message”) or MT_F_SM_I (MAP > V2 ”MT_Forward short message”). This message is
sent by the RCF of the GMSC to the RCF of the VMSC to request the forwarding of an MS terminated short message.
After the determination of the MAP dialogue version, some checks are performed to determine if the length of User data allows
the MAP transfer and, in the positive case, if MAP segmentation is needed (see following pages) for MAP version > 1.
At the VMSC, on receiving F_SM_I or MT_F_SM_I, the RCF checks that:
• option F_SMS_002 "MSC supports SMS terminating" is enabled, in other words that the SMS_MT service can be offered
by the VMSC,
• the parameters of the message received are correct.
If there is an error, the RCF responds to the SMS_GMSC by sending an error report in the F_SM_E or MT_F_SM_E,
FORWARD_SHORTMESSAGE_ERROR message. Otherwise the procedure continues with transmission of the SINF_SMT_I
message to the VLR.
The VLR then checks the IMSI.
• If the IMSI is unknown and functional option F_SMS_003 "SMS delivery attempt even when IMSI is unknown" is enabled, a
paging procedure is executed.
• If the IMSI is unknown and option F_SMS_003 is not enabled, the VLR responds to the VMSC's RCF with the
SINF_SMT_E message with "unidentified subscriber" as the cause.
• If the IMSI is known ,the VLR checks that it is not detached and that the LA is authorised for that subscriber. If the IMSI is
detached or if the MS is in an unauthorized LA the VLR sets the MNRF flag and returns a "SendInfoForSMTInvokeError"
message to the RCF with "Absent subscriber" as the cause.
The error message is also sent to the RCF when the subscriber data is not available (MS_DATA_KNOWN flag). The cause of the
error is "Unidentified subscriber".
When all the checks have been performed and are OK:
• IMSI known,.
• Subscriber data available.
• IMSI not detached.
• LA authorized.
The VLR asks the RCF to carry out a paging operation by sending it the PAGE_SMT_I message to establish radio contact with
the required mobile station.

The RCF then executes the subscriber paging procedure.
• If paging is successful, the VLR is informed of the status of the radio connection with the mobile.
• If it is unsuccessful or the mobile station is not equipped to receive short messages (classmark 2 SM capability), the
message sent by the RCF to the VLR is PAGE_SMT_E.
• If it is unsuccessful, due to an MS not having the capability to receive short messages, the security procedure is carried out
nonetheless. The SMDeliveryfailure(MSNotEquipped) message is inserted in the F_SM_E if the security procedure is
successful. Otherwise, the paging error is forgotten and the error detected by the security procedure is taken into account.
When a subscriber has been paged successfully, the VLR carries out authentication of the mobile station.
The COM_SMT_I message sent to the RCF indicates that the short message delivery service can be offered to the subscriber.
If the RCF receives the "SendInfoForSMTInvokeError" message SINF_SMT_E from the VLR with any error cause, the RCF
forwards the error cause to the SMS_GMSC in the "ForwardShortMessageError" message, F_SM_E or MT_F_SM_E.
If the IMEI reveals that the mobile station is on a black list, the RCF forwards the F_SM_E or MT_F_SM_E message to the
SMS_GMSC with "Absent Subscriber" as the error cause.
The RCF waits for the result of the IMEI check before sending the CP_DATA (RP_DATA) message to the mobile station.
A short message can be delivered in parallel with a procedure such as a TC or OC, supplementary service access or SMS_MO.
However, only one short message can be delivered to the mobile at a time.
The RCF, which can receive several short messages (from different SCs) for the same subscriber, must buffer them and deliver
them one by one.
The RCF therefore checks that there are no other SMS_MT in progress. If there are, it must wait until they are finished before it
can send the CP_DATA(RP_DATA) message to the MS.
Release of the radio connection:
If the RCF receives the "Channel Release" message from the RM (Radio resource Management) function due to "radio interface
failure" or "IMSI detach" (the subscriber switches off his mobile during the short message transfer):
• The RCF returns the "ForwardShortMessageError" message F_SM_E or MT_F_SM_E to the SMS_GMSC with "Absent
Subscriber" as the error cause.
• The RCF sends the Set_MNRF message to the VLR so that it can set the MNRF flag.
Mobile station acknowledgement:
If the acknowledgement message sent by the mobile station indicates that the short message has been successfully delivered,
the VMSC sends F_SM_R or MT_F_SM_R to the RCF of the SMS_GMSC.
If delivery of the short message to the mobile fails:
• The mobile station returns a CP_ERROR message to the RCF in response to the CP_DATA(RP_DATA) message if the
problem is detected in the CP_DATA(RP_DATA) message received.
• The mobile station returns a CP_DATA(RP_ERROR) message to the RCF after the CP_ACK when a problem inside the
mobile is detected, for example, for a phase 2 mobile, if its memory capacity is exceeded.
• If an error is detected in the CP_DATA(RP_ACK) message received by the RCF, it responds to the mobile station with a
CP_ERROR.
The RCF informs the SMS_GMSC of the short message delivery failure with an error report contained in the
"ForwardShortMessageError" message.

ANALYSIS OF SHORT MESSAGE LENGTH

MAP application segmenting
L3 L2 L1
No need for MAP MAP Short message

Short message
segmentation segmentation call released
call released
whatever the necessary if
if MAP V>1
MAP version MAP V>1 Length of
short message
Short message
L5
SCCP segmenting call released
3.13

After determining the MAP version to be used to send the "FORWARD_SHORT_MESSAGE_INVOKE" message, the
SMS_GMSC checks the length of the message.
SCCP segmenting is used or not depending on a PLMN parameter and a PLMNs list, four situations can be managed by the
operator :
• either no segmenting,
• or segmenting only in the case where the VMSC belongs to the HPLMN,
• or segmenting in the case where the VMSC belongs to the HPLMN or belongs to an authorised foreign PLMN,
• or segmenting whatever the VMSC.
The following values are used :
• MAP application segmentating
Î L1 Max length of User data supported by MAP (any MAP version).
Î L2 Max length of User data supported by a MAP version > 1 with MAP segmenting process.
Î L3 Max length of User data which can be carried by a MAP version > 1 without MAP segmenting.
• SCCP segmenting
Î L5 Max length of a short message on the A interface or the G B interface.
With MAP application segmentation (Without SCCP segmentation)
• If User data length <= L3, then no MAP segmenting process is needed, whatever MAP version of dialogue.
• If L3 < User data length <= L2, then MAP segmenting process is required if the MAP version of dialogue is > 1. (with MAP
version >1, it is impossible to transport long messages because of additional fields)
• If L1 < User data length, the RP_MT_DATA is rejected during the check of the parameters just after the receipt of the
message from the SC.
With SCCP segmentation
• If User data length>L5, then the RP_MT_DATA is rejected.

VMSC
MS
BSS
REPORT_SM_DELIVERY_STATUS_INV S_MW_I or R_SMD_S_I
REPORT_SM_DELIVERY_STATUS_RES S_MW_R or R_SMD_S_R
DATA_FORM 1 (RP_MT_ACK)
RELEASE
RELEASE CONFIRMED
3.14
SUBSCRIBER SHORT MESSAGE DELIVERY (4/4) - "SM Delivery Status Report" procedure
CASE :Short message delivery failure

• SMS_GMSC/HLR dialogue: Map V1
Î If the short message delivery failure is caused by the memory capacity being exceeded, no specific action is taken
by the SMS_GMSC.
Î If the short message delivery failure is due to "Absent subscriber" or "Unidentified subscriber" and if the MNRF is
not set in the HLR* or the SC address does not appear in the MWD list:
ª the SMS_GMSC sends the "SetMessageWaitingDataInvoke" message, S_MW_I, to the HLR.
• SMS_GMSC/HLR dialogue: Map >V1
Î If the SMS_GMSC receives the "ForwardShortMessageError" message from the VMSC with error cause
"MemoryCapacityExceeded" in the DiagnosticInfo field, and if, in the HLR*, the MCEF is not set or the SC address
is not already included in the MWD list, the SMS_GMSC sends the "ReportSMDeliveryStatusInvoke" message to
the HLR with parameter "SM_DeliveryOutcome = MemoryCapacityExceeded".
Î If the SMS_GMSC receives the "ForwardShortMessageError" message from the VMSC with error cause "Absent
Subscriber" or "unidentified Subscriber" in the DiagnosticInfo field and if, in the HLR*, the MNRF is not set or the SC
address is not already in the MWD list, the SMS_GMSC sends the "ReportSMDeliveryStatusInvoke" message to
the HLR with the "SM_DeliveryOutcome = Absent Subscriber" parameter.
* The SMS_GMSC has received from the HLR the indication that the SC address is or is not included in the MWD list as well as
the status of the MNRF and MCEF in the "SendRoutingInfoForSM result" message, S_RGI_SM_R for MAP V1, or in the
"InformServiceCenter" message, I_SC_I, for MAP>V1. A default value, MNRF not set and SC address not in the list, may be
used.

CASE : Successful short message delivery procedure: "ForwardShortMessageResult" message received by the
SMS_GMSC.
• SMS_GMSC/HLR dialogue: Map V1
Î No specific action is taken.
• SMS_GMSC/HLR dialogue: Map >V1
Î In the HLR, if the MNRF and/or MCEF is set, the SMS_GMSC sends the "ReportSMDeliveryStatusInvoke" message
with the "SM_DeliveryOutcome = SuccessfulTransfer" parameter.
Process at the HLR, following receipt of the "SMDeliveryStatusReportInvoke" message, R_SMD_I, or the
"SetMessageWaitingDataInvoke" message, S_MW_I.
The HLR first checks that the message is correct and that the MS_ISDN it contains is known. If it is not, the HLR responds with
R_SMD_E or S_MW_E depending on the MAP version.
• When the HLR receives the "ReportSMDeliveryStatusInvoke" message with the "SM_DeliveryOutcome =
SuccessfulTransfer" parameter, the HLR initiates an alert procedure.
• On receipt of the "SetMessageWaitingDataInvoke" message or the "ReportSMDeliveryStatusInvoke" message with the
"SM_DeliveryOutcome = Absent Subscriber" parameter:
Î If the MWD list is full, the HLR sends to the SMS_GMSC the "SetMessageWaitingDataError" message S_MW_E or
the "ReportSMDeliveryStatusError" message R_SMD_S_E, depending on the version.
Î Otherwise, the HLR adds the SC address to the MWD list and sets the MNRF. The S_MW_R or R_SMD_S_R
message with the alert MS_ISDN as a parameter is sent to the SMS_GMSC
• When the HLR receives the "ReportSMDeliveryStatusInvoke" message with the "SM_DeliveryOutcome =
MemoryCapacityExceeded" parameter:
Î If the MWD list is full, the HLR sends the SMS_GMSC the "ReportSMDeliveryStatusError" message, R_SMD_S_E.
Î Otherwise, the HLR adds the SC address to the MWD list and sets the MCEF and resets the MNRF if it was set.
The S_MW_R or R_SMD_S_R message with the alert MS_ISDN as a parameter is sent to the SMS_GMSC.
• To avoid SC addresses remaining for too long in the MWD list and causing list congestion, the SC addresses are deleted
from the list if no alert procedure occurs after a time delay T_MWD.
SMS_GMSC call
At the end of the phase described above, the SMS_GMSC informs the SC of the result of the short message delivery procedure.
If there is an error, the DT1 message containing an RP_MT_ERROR with parameters dependent on the S_MW_E or R_SMD_E
is sent to the SC.
• In SMSAP V1:
Î The RP_MW flag tells the SC whether the MWD list has been updated in the HLR.
Î RP_cause contains the error cause received from the VMSC in the "ForwardShortMessageError" message.
• In SMSAP >V1:
Î The RP_MSISDN parameter contains the alert MS_ISDN if it is received from the HLR in the
"ReportSMDeliveryStatusResult" message.
Î In the DiagnosticInfo field, the RP_User_Data parameter contains the reason for the error, "SM_DeliveryFailure", if
it is received from the VMSC in the "ForwardShortMessageError" message

Structure of the main messages interchanged between Nes:
Send_Routing_Info_for_SM
These messages are interchanged between the RCF of the GMSC and the HLR for extraction of the routing information.
S_RGI_SM_I
1) MS_ISDN,
2) SM_RP_PRI, specifies the order of priority of the message indicated in RP_MT_DATA received from the SC. Option
F_SMS_004 must be enabled, otherwise all the messages are considered non priority.
3) ServiceCenterAddress: SC address in E.164 format received from the SC in the RP_MT_DATA message.
S_RGI_SM_E
1) UnknownSubscriber,
2) CallBarred, specifies the cause of call barring: "BarringServiceActive" or "OperatorBarring",
3) CUG_Reject,
4) TeleserviceNotProvisioned,
5) AbsentSubscriber, positioning of the mwd flag,
6) AbsentSubscriberSM, specifies the reason for the subscriber's absence, no reply to paging, IMSI detached, roaming
restriction, etc,
7) FacilityNotSupported, optional function not activated,
8) SystemFailure,
9) DataMissing,
10) UnexpectedDataValue.
S_RGI_SM_R
1) IMSI,
2) LocationInfo, contains the address of the visited MSC,
3) LMSI,
4) MWD set,
Inform_Service_Center
This message is sent by the HLR to the SMS_GMSC to inform the SC of the subscriber status (MNRF, MCEF) and to indicate
whether the MS_ISDN is in the MWD list. This message is transmitted after sending the routing information contained in the HLR.
I_SC_I
1) MS_ISDN_Alert,
2) mw_status : SC_AddressNotIncluded
mnrf_set
mcef_set

Forward_Short_Message
The messages in this category are interchanged between the RCF of the SMS_GMSC and the RCF of the VMSC for short
message transfer.
MAP V1, V2 MAP V3
F_SM_I MT_F_SM_I
SM_RP_DA, IMSI, LMSI, SM_RP_DA, IMSI, LMSI,
SM_RP_OA, contains the SC address, a parameter SM_RP_OA, contains the SC address, a parameter
that is ignored if several short messages are that is ignored if several short messages are
transferred. transferred.
SM_RP_UI, contains the RP_user_data field of the SM_RP_UI, contains the RP_user_data field of the
RP_MT_DATA message received from the SC. Short RP_MT_DATA message received from the SC. Short
message to be delivered to the subscriber. message to be delivered to the subscriber.
MoreMessageToSend, positioned according to the MoreMessageToSend, positioned according to the

indications from the SC. In MAP V1, this parameter indications from the SC.
is not supported.
F_SM_E MT_F_SM_E
UnidentifiedSubscriber UnidentifiedSubscriber
AbsentSubscriber AbsentSubscriberSM :
FacilityNotSupported
IllegalMS
• AbsentSubscriberDiagnosticSM :
No paging response via MSC, IMSI detached
IllegalSubscriber (Authentication procedure failed)
SystemFailure
FacilityNotSupported
UnexpectedDataValue
IllegalMS
IllegalSubscriber (Authentication procedure failed)
SM_DeliveryFailure :
SystemFailure
UnexpectedDataValue
• Cause :
Memory capacity exceeded SM_DeliveryFailure :
Equipment protocol error
Equipment not SM supported • Cause :
Memory capacity exceeded
• DiagnosticInfo : Equipment protocol error
IllegalEquipment Equipment not SM supported
DataMissing
SubscriberBusyForMT • DiagnosticInfo :
IllegalEquipment
DataMissing
SubscriberBusyForMT
F_SM_R MT_F_SM_R
No parameter SM_RP_UI

Send_Information_For_SMT
This message is sent by the RCF to the VLR to ask it whether the service can be offered to the subscriber.
SINF_SMT_I
IMSI
SINF_SMT_E
1) Unidentified subscriber,
2) Absent subscriber SM:
• No paging response via MSC,
• IMSI detached.
3) Illegal MS,
4) Illegal equipment,
5) System failure,
6) Impossible call completion,
7) MS not equipped.
Complete_SMT_Call
This message is sent by the VLR to the RCF to confirm that the SMS_MT service can be offered to the subscriber.
COM_SMT_I
Category, if the HLR does not support the MNRF, MCEF and MWD entities, this field is not completed,
MS_ISDN, if the IMSI is unknown to the HLR.
CP_DATA
This message can be sent to the mobile by the RCF or can be sent by the RCF to the mobile. To the mobile, it contains the short
message. To the RCF, it contains the acknowledgement.
CP_DATA
1) Transaction identifier,
2) Message Type,
3) CP_User_Data,
The RPDU field of the CP_user data parameter may contain:

• RP_DATA (RCF → MS), short message transfer.
• RP_SMMA (RCF → MS), available memory notification.
• RP_ACK (MS → RCF), positive acknowledgement.
• RP_ERROR (MS → RCF), negative acknowledgement.
CP_ERROR
CP_ERROR
This message is used to convey error information in the CP_Cause field.

RP_DATA
RP_DATA contains the short message to be transmitted to the MS.

1) Message reference.
2) Originator Address: this parameter contains the SC address.
3) RP_Userdata: This field transports the short message. Same as the RP_Userdata field received from the SC.
RP_ERROR
The mobile station has not received the short message. An error report is forwarded to the VMSC.
RP_ERROR
1) RP_CAUSE. The cause of the transfer failure is specified in this field.
2) RP_User_Data to be transferred in the SM_Delivery_Failure of forward short message message.
RP_ACK
RP_ACK
RP_UserData. TPDU received from the MS.
Report_SM_Delivery_Status
The message interchange is used here to inform the HLR that the short message has been successfully delivered or to position
the MWD in the HLR in MAP > V1.
R_SMD_S_I
1) MS_ISDN,
2) Service Centre address,
3) SM_DeliveryOutcome
• MemoryCapacityExceeded
• AbsentSubscriber
• SuccessfulTransfer
4 ) AbsentSubscriberDiagnosticSM, specifies the reason for the short message delivery failure when the failure is due to
"Absent subscriber". The values of this field can be:
• No paging response via the MSC,
• IMSI detached,
• Unidentified subscriber via the MSC,
5 ) AdditionalSM_DeliveryOutcome :
• MemoryCapacityExceeded,
• AbsentSubscriber
• SuccessfulTransfer
R_SMD_S_E
2) MessageWaitingListFull,
3) UnexpectedDataValue,
4) DataMissing.
R_SMD_S_R
StoredMS_ISDN, this parameter is completed when the MS_ISDN_alert is different from the MS_ISDN that is in the R_SMD_S_I
message.

Set_Message_Waiting_Data
Following this message interchange, the HLR inserts the SC address in the MWD list in MAP V1.
S_MW_I
1) MS_ISDN,
2) Service Centre address,
S_MW_E
2) MessageWaitingListFull,
3) UnexpectedDataValue,
4) DataMissing.
S_MW_R
No parameter

Delivery of several consecutive SMS to a subscriber (1/3)
VMSC
MS
BSS
CONNECTION_REQUEST
CONNECTION_CONFIRMED
Same as the short message delivery procedure
DATA_FORM 1 (RP_MT_DATA)
SEND_ROUTING_INFO_FOR_SM_INV
S_RGI_SM_I
Extraction of routing data
SEND_ROUTING_INFO_FOR_SM_RES
S_RGI_SM_R
INFORM_SERVICE_CENTRE
I_SC_I
Containing the parameter:

MoreMessageToSend
3.21
DELIVERY OF SEVERAL CONSECUTIVE SMS TO A SUBSCRIBER (1/3)
If the dialogue between the SC, SMS_GMSC and VMSC equipment is appropriate, that is, if the SMSAP and MAP versions are
higher than V1, the SC tells the SMS_GMSC that it has other short messages to send.

.
VMSC
SMSAP AND MAP VERSIONS > V1
MS
BSS
FORWARD_SHORT_MESSAGE_INV F_SM_I or MT_F_SM_I

TC-BEGIN
See previous scenario
FORWARD_SHORT_MESSAGE_RES F_SM_R or MT_F_SM_R
TC-CONTINUE
DATA_FORM 1 (RP_MT_ACK )
DATA_FORM 1 (RP_MT_DATA )
FORWARD_SHORT_MESSAGE_INV F_SM_I or MT_F_SM_I
TC-CONTINUE
Transfer of next
See previous scenario short message
FORWARD_SHORT_MESSAGE_RES F_SM_R or MT_F_SM_R

Radio connection
TC-CONTINUE released
OR TC-END
RELEASE
RELEASE_CONFIRMED
Containing the parameter:
If last short message MoreMessageToSend
3.22
Case of SMSAP and MAP versions greater than V1

The RP_MT_DATA message contains the "MoreDatatoSend" information indicating that subsequent short messages are to
follow. The SMS_GMSC forwards this information to the VMSC by inserting it in the "ForwardShortMessageInvoke" message.
In the VMSC, everything happens as for a short message transfer except that:
• The radio connection is not released at the end of the short message transfer to the MS.
• The "ForwardShortMessageResult" message forwarded to the SMS_GMSC is accompanied, at TCAP level, by a
continuation and not an end of transaction.
• A T_SUBSEQ timer is started by the VMSC. If, on expiry of that timer, the VMSC has not received a new
"ForwardShortMessageInvoke" message from the SMS_GMSC, the VMS closes its TCAP transaction with the
SMS_GMSC and releases its RR connection with the mobile station.
When the VMSC sends the "ForwardShortMessageError" message to the SMS_GMSC, the message is accompanied by an end
of TCAP transaction. The SMS_GMSC then sends a Data Form 1 message (RP_MT_Error) to the SC and no other subsequent
short message can be delivered.
After sending the Data Form 1 (RP_MT_ACK) acknowledgement message to the SC, the SMS_GMSC starts a T_SCRLS timer.
• After receiving the Data Form 1 acknowledgement from the SMS_GMSC, the SC can either release the SCCP
connection or send to the SMS_GMSC, in the same SCCP connection, a new Data Form 1 (RP_MT_Data) message
containing a new short message and, if necessary, the "MoreDatatoSend" message again.
• If the T_SCRLS timer expires before the SC has released the SCCP connection or sent a new short message to the
SMS_GMSC, the SMS_GMSC releases the SCCP connection.
The SC never sends a new short message unless it has received acknowledgement of the previous one.

Analysis at the SMS_GMSC of the new Data Form 1 (RP_MT_DATA) message:
The SMS_GMSC checks that:
• the message is correct,
• it is indeed intended for the same MS_ISDN.
If not, the SMS_GMSC sends the SC a Data Form 1 (RP_MT_Error) message containing the error cause.
When the two above requirements have been met, the SMS_GMSC sends the "ForwardShortMessageInvoke" message directly
(where necessary containing "MoreDatatoSend") to the VMSC. It does not interrogate the HLR to handle the subsequent short
message.
Process at the VMSC, following receipt of the "ForwardShortMessageInvoke" message (TC-Continue):
• The receipt of this message suspends the handling of the short messages in the queue (short messages from other SCs).
• The paging, authentication, ciphering and IMEI check are not repeated. (No interchange of SINF_SMT_I/COM_SMT_I
messages).
• The short message is transferred over the same radio link as before.
If the "ForwardShortMessageInvoke" message (TC-Continue) received from the SMS_GMSC contains "MoreDatatoSend":
• At the end of the short message transfer, the radio connection is not released.
• The "ForwardShortMessageResult" message that the VMSC forwards to the SMS_GMSC is accompanied at SCCP level
by a continuation and not an end of transaction.
• A T_SUBSEQ timer is started by the VMSC.
If, on expiry of this timer, the VMSC has not received a new "ForwardShortMessageInvoke" message from the SMS_GMSC, the
VMSC closes its SCCP transaction with the SMS_GMSC and releases the radio connection with the mobile station.
If the "ForwardShortMessageInvoke" message (TC-Continue) from the SMS_GMSC does not contain "MoreDatatoSend":
• At the end of the short message transfer, the radio connection is released.
• The "ForwardShortMessageResult" message that the VMSC forwards to the SMS_GMSC is accompanied at SCCP level
by an end of transaction.

VMSC
IN MAP V1
MS
BSS
FORWARD_SHORT_MESSAGE_INV F_SM_I
TC-BEGIN
See previous scenario
FORWARD_SHORT_MESSAGE_RES F_SM_R
TC-END
DATA_FORM 1 (RP_MT_DATA )
FORWARD_SHORT_MESSAGE_INV F_SM_I
TC-CONTINUE
Transfer of next
See previous scenario short message
FORWARD_SHORT_MESSAGE_RES F_SM_R
DATA_FORM 1 (RP_MT_ACK ) TC-END
RELEASE
Activation of
RELEASE_CONFIRMED T_SCRLS timer
New short
message
3.24

Case of MAP V1 dialogue
If the dialogue between the SC, SMS_GMSC and VMSC NEs is Phase1 /V1, the SC does not indicate that it has subsequent
short messages to send to the VMSC. Several subsequent short messages are handled at the VMSC as individual short
messages.
After sending the Data Form 1 (RP_MT_ACK) acknowledgement message to the SC following the "ForwardShortMessage_RES"
(TC-END), the SMS_GMSC starts a T_SCRLS timer.
• At the SC, after receiving the acknowledgement Data Form 1 from the SMS_GMSC, the SC can either release the SCCP
connection or send to the SMS_GMSC, in the same SCCP connection, a new Data Form 1 (RP_MT_Data) message
containing a new short message.
• If the T_SCRLS timer expires before the SC has released the SCCP connection or sent a new short message to the
SMS_GMSC, the SMS_GMSC releases the SCCP connection. The SC never sends a new short message unless it has
received an acknowledgement for the previous one.
The SMS_GMSC checks that:
• the new Data Form 1 message is correct,
• it is intended for the same MS_ISDN.
• If not, the SMS_GMSC sends the SC a Data Form 1 (RP_MT_Error) message containing the error cause.
• If, during the previous short message, the HLR interrogation procedure was successful, the SMS_GMSC does not repeat
the procedure and sends the "ForwardShortMessageInvoke" message directly to the VMSC. Otherwise, everything
happens as for sending the first short message.
• With each new short message, on sending the "ForwardShortMessageInvoke" message to the VMSC, the SMS_GMSC
opens a new TCAP transaction with the VMSC (the "ForwardShortMessageRes" response message from the VMSC to the
SMS_GMSC corresponding to the previous short message is always accompanied, at TCAP level, by an end of
transaction).
• In the VMSC, each time, everything happens as in the short message delivery procedure covered in section 3.3.

Alert procedure (1/5)
MS REACHEABLE
SC IWMSC VLR HLR
Security procedure performed (requested by an

operation such as TC, OC, SH, SMT, SMO, location
update… that is successfully completed).
_MNRF flag set.
NOTE_SUBSCRIBER_PRESENT or
READY _FOR_ SM MS_P_I or R_F_SM_I
R_F_SM_R
MAP > V2
ALERT_SERVICECENTER_ WITHOUT_RESULT A_SC_WR_I or A_SC_I Only if MCEF

is not set
TC-BEGIN
Unit DaTa (RP_Alert)
A_SC_R
TC-END
3.25
ALERT PROCEDURE (1/5)
The alert procedure is to inform an SC that a subscriber for which it has messages:
• is reachable again, (an attempt to deliver short messages has failed due to "absent subscriber" which means IMSI
detached, no response to paging, roaming restriction, etc),
• has free memory capacity again (MAP > V1),
• has just successfully received a short message, whereas a previous attempt ended in failure (MAP > V1).
The SC can then try again to deliver the short messages it has for that subscriber.
Triggering the alert procedure
A mobile station is reachable again * (cf NOTE).
When a mobile station is reachable again, the HLR will use the operations necessary to inform the SC that is holding messages
for that mobile.
The alert procedure can be triggered by the HLR after a location update.
The VLR can also ask the HLR to trigger the alert procedure if:
• The MNRF is set.
• And if one of the following procedures is successfully carried out in the VLR:
- Paging
- Location update
- IMSI attached
- Process access request
In MAP V1, the VLR immediately resets the MNRF. In MAP > V1 the VLR waits for the alert procedure to be completed
successfully before it resets the MNRF (receipt of the R_SM_R message).
The HLR responds positively to the request if the MCEF is not set. It then resets the MNRF and MNRR flags.

A mobile station regains its memory capacity (MAP > V1) *((cf NOTE).
The mobile station notifies the VMSC through an MS management procedure that it has regained its memory capacity.
If the F_SMS_002 "SMSMT supported" option is enabled in the VLR, the VLR's SMO function then notifies the HLR that the
mobile has regained sufficient memory to be able to receive one or more short messages.
Short message successfully delivered (MAP > V1).
If the MCEF or MNRF is set in the HLR and the HLR is informed by the SMS_GMSC that the delivery of a short message to a
mobile has been successful, the alert procedure is triggered after both indicators have been reset.
* NOTE: If the alert procedure is requested by the VLR because the subscriber is reachable or memory capacity has
been regained, when neither the MNRF nor the MCEF is set in the HLR, it is assumed that the system is in a
"race" situation. The short message delivery has failed at the VLR. But immediately afterwards, the cause of the
failure has disappeared and the VLR has notified the HLR (by setting flags) before it has received the
"ReportSMDeliveryStatusInvoke" message relating to the failure.
When the VLR sends an alert procedure trigger request to the HLR, and the MNRF and MCEF are not set, the HLR sets a
T_RACE timer. If the "ReportSMDeliveryStatusInvoke" message arrives before the end of the timer, it is handled normally and
can cause the MNRF or MCEF to be set.
When the timer expires, if the MNRF or MCEF is set, the HLR executes the alert procedure.
Structure of the main messages interchanged between network elements:
Note_Subscriber_Present
This message is sent by the VLR to the HLR when the mobile is reachable again in MAP V1.
MS_P_I
IMSI
Ready_For_SM
The messages are interchanged between the VLR and HLR when the mobile station is reachable again or has regained sufficient
memory capacity in MAP > V1
R_F_SM_I
1) IMSI,
2) Alert reason,
• MS_Present
• Memory available
R_F_SM_E
1) DataMissing
2) UnexpectedDataValue
3) FacilityNotSupported
4) UnknownSubscriber

R_F_SM_R
No parameter
Alert_Service_Center_Without_Result
This message is sent by the HLR to trigger the alert procedure at the IWMSC in MAP V1.
A_SC_WR_I
1) MS_ISDN,
2) ServiceCenterAddress.
Alert_Service_Center
This message is sent by the HLR if a subscriber, who is on the MWD list, becomes "active" or has regained sufficient memory
capacity in MAP > V1.
A_SC_I
1) MS_ISDN,
2) ServiceCenterAddres.
A_SC_E
1) SystemFailure,
2) DataMissing,
3) UnexpectedDataValue.
A_SC_R
No parameter

MEMORY CAPACITY REGAINED VMSC
MS
BSS
CP_DATA (RP_SMMA)
CP_ACK
READY_FOR_SM R_F_SM_I
READY_FOR_SM R_F_SM_I
(memory available)
A_SC_WR_I or A_SC_I
UDT (RP_ALERT) TC-BEGIN Suscriber has

gained SMS
memory
A_SC_R
READY_FOR_SM_RESULT R_F_SM_R
TC-END
READY_FOR_SM_RESULT R_F_SM_R
CP_DATA (RP_ACK)
CP_ACK
3.28

AN SMS_MT PROCEDURE HAS BEEN PERFORMED SUCCESSFULLY
SC IWMSC RCF GMSC RCF HLR
REPORT_SM_DELIVERY_STATUS
(successful transfer)
R_SMD_S_I
R_SMD_S_R
DATA FORM 1 (RP_MT_ACK)
A_SC_WR_I or A_SC_I
TC-BEGIN
A_SC_R
TC-END
3.29

RACE SITUATION
SMS_GMSC VLR
SC HLR
RCF
MS_P_I or R_F_SM_I
READY_FOR_SM
MNRF and MCEF
are not set
R_F_SM_R
Race Situation.
The T_RACE timer is activated.
REPORT_SM_DELIVERY_STATUS_INV R_SMD_S_I
If the message is received before

REPORT_SM_DELIVERY_STATUS_RES R_SMD_S_R expiry of the timer, it is handled
normally and may lead to set the
MNRF or MCEF flag and, the alert
procedure is not triggered.
If R_SMD_S_I not received before
ALERT_SERVICECENTER_WITHOUT_RESULT A_SC_WR_I or A_SC_I timer expiry, the alert procedure is
triggered
TC-BEGIN
A_SC_R
TC-END
3.30

LOCATION UPDATE IN THE HLR
SC IWMSC RCF VLR HLR
Location update
ALERT_SERVICECENTER_WITHOUT_RESULT A_SC_WR_I or A_SC_I
TC-BEGIN
A_SC_R
TC-END
3.31

Interactions with other services
▼ Incoming call barring (SS) and operator determined barring (ODB) apply
▼ Handling an OC, TC or a supplementary service
z MM procedure is in progress at the same time as the delivery of a short message :
Î the VMSC waits for the end of the MM procedure.
z OC, TC or SH (Supplementary service Handling) call is set up :
Î A short message can be delivered at the same time.
z OC or SH call occurs during the transfer of a short message :
Î the call is handled as if there was no SMS_MT process.
z A TC occurs when a message is being transferred to a mobile :
Î no message is delivered to the mobile.
▼ Network access request for an OC, SMS_MO or SH procedure and paging response for an
SMS_MT procedure :
Î priority given to the access request. SMS_MT procedure fails (busy subscriber)
▼ Location update and short message delivery procedures:
Î in parallel.
▼ Procedure for delivering a short message from another SC:
Î a queue is formed in the VMSC
▼ SMS_MO and SMS_MT procedures:
Î Can take place in parallel.
3.32
INTERACTION WITH OTHER SERVICES
Incoming call barring and operator determined barring apply to the SMS_MT service.
Handling of an OC, TC or supplementary service (SH):
• If an MM procedure is in progress for a voice or data call or for a supplementary service transaction at the same time
as the delivery of a short message, the VMSC waits for the end of the MM procedure.
• When an OC, TC or SH (Supplementary service Handling) call is set up, a short message can be delivered at the
same time.
• If an OC or SH call occurs during the transfer of a short message, the call is handled as if there was no SMS_MT
process.
• If a TC occurs when a message is being transferred to a mobile, no message is delivered to the mobile.
Instead of receiving a "paging" response concerning an SMS_MT procedure, the VMSC receives a network access request for
an OC, SMS_MO or SH call. Priority is given to the access request. The SMS_MT procedure fails due to "busy subscriber".
The location update and short message delivery procedures can take place in parallel.
Messages from different SCs for the same mobile station are never sent in the same transaction by the SMS_GMSC to the
VMSC.
• There can be only one SMS_MT transaction between the VMSC and the mobile. This means that a queue is formed
in the VMSC (the maximum number of messages is programmable). The authentication and ciphering procedures are
not carried out for the messages in that queue.
The SMS_MO and SMS_MT procedures can take place in parallel.

3.2 Data structure
3.33

3.2 Data structure
F-SMS-001
▼ F-SMS-001 in the HLR

z Sys. Par.: PARNAME = HLS_F_SMS_001, BOOLVAL
z RTDMS database: RELNAME = RYR_SYSB, attribute: HY_U_HLR
▼ F-SMS-001 lets the operator warn each SC (Service Centre) or only the one specified
by the HLS_IWMSC parameter when a message is successfully received by a mobile
and the MWD (message waiting data) lists are not empty.
▼ Meaning :
z TRUE: The HLR notifies each SC via the IWMSC for each SC address in the
MWD.
z FALSE: The HLR notifies only the SC (via the IWMSC address) specified by
HLS_IWMSC.
3.34

3.2 Data structure
F-SMS-002
▼ F-SMS-002 in the RCP of the SMS_VMSC, SMS_GMSC and SMS_IWMSC

z Sys. Par.: PARNAME = RB_F_SMS_002, BOOLVAL
z RTDMS database: RELNAME = RYR_SYSB, attribute: D_F_MT02
▼ F-SMS-002 indicates whether the short message mobile terminated service is

available in the VMSC.
▼ Meaning :
z TRUE: The short message mobile terminated service is available in the VMSC.
z FALSE: The short message mobile terminated service is not available in the
VMSC. An error message is sent to the service centre when there is an attempt
to send a short message.
3.35

3.2 Data structure
F-SMS-003
▼ F-SMS-003 RCP of the SMS_VMSC

▼ F-SMS-003 Describes the VMSC ’s reaction when short messages are to be sent to
mobiles not registered in the VLR database.
▼ Meaning :
z TRUE: When a short message to a mobile that is not registered in the VLR is
received, a search procedure (SEARCH) is launched. If the mobile is reached, a
location Update procedure is used to send the short message to the mobile.
z FALSE: Short messages to mobiles not registered in the VLR are rejected.
3.36

3.2 Data structure
F-SMS-004

▼ Sys. Par.: PARNAME = HLS_F_SMS_004, BOOLVAL
z RTDMS database: RELNAME = HYR_HLS, attribute: HY_U_HLR
▼ F-SMS-004 lets the operator manage priorities for mobile terminated short messages.
When priorities are not supported, all the SMS messages are considered non priority.
For non priority SMS messages, the HLR checks that the MNRF indicator (mobile
station unreachable) is not defined before retrieving the routing information. For a
priority SMS message, the HLR tries to retrieve the routing information without taking
account of the MNRF and MCEF flag states (mobile station memory capacity
exceeded).
▼ Meaning :
z TRUE: Priority is managed for SMS messages if there is a priority value in the
MAP_SEND_ROUTING_INFO_FOR_SM message. If the priority value does not
exist, the message is non priority.
z FALSE: All messages are non priority for the SMS.
3.37

3.2 Data structure
F-SMS-006

z Sys. Par.: PARNAME = HLS_F_SMS_006, BOOLVAL
▼ F-SMS-006 lets the operator allow messages to the HLR only from the SMS_GMSC
belonging to the HPLMN.
▼ Meaning :
z TRUE: The MAP_SEND_ROUTING_INFO_FOR_SM operation is rejected by
the HLR if the SMS_GMSC does not belong to the HPLMN. When TRUE, the
SMS service between PLMNs is rejected.
z FALSE: The MAP_SEND_ROUTING_INFO_FOR_SM request is handled
irrespective of whether the GMSC belongs to the HPLMN.
▼ Note : The data F_VH_002 allows to restrict messages from determined (instead of all
FPLMN) PLMN by setting the Application Context to NSUP via MODNET irrespectively
of the lowest version.
z P2B_F_VH_002 (RCP)
z HLS_F_VH_002 (HLR)
3.38
When enabled, this functional option rejects the "SendRoutingInformationForSM" message requesting routing information for
delivering a short message to the mobile when the message is from an FPLMN (SMS_GMSC).

3.2 Data structure
F-SMS-007
▼ F-SMS-007 in the RCP of the SMS_VMSC

▼ F-SMS-007 enables explicit requests for a standalone dedicated control channel

SDCCH to transfer a short message mobile originated or mobile terminated.
▼ Meaning:
z TRUE: A standalone dedicated control channel (SDCCH) is requested from the
BSC for the short message mobile originated or mobile terminated service when
necessary:
Î The short message is not sent during the call and the BSC has first
assigned the traffic channel, TCH (Very Early Assignment). In this
particular case, an explicit request is sent by the RCF to the BSC.
z FALSE: No explicit request for an SDCCH is sent to the BSC.
3.39
Functional option F-SMS-007, once the mobile has responded to a paging message, involves sending an "assignment request"
to the BSC station asking it to assign an SDCCH channel. This request is sent only if the "chosen channel" parameter in the
paging response is absent or different from the SDCCH. If the response is negative (which includes choosing another type of
channel), the system uses the processes provided for standard situations to avoid failing to deliver the messages.
If the option is disabled, the process is as follows:
• if no call is in progress, the SDCCH channel is assigned,
• otherwise, the SACCH channel is assigned.

3.2 Data structure
F-GPRS-002
▼ F-GPRS-002 in the HLR

z Sys. Par.: PARNAME = HLS_GPRS_002, BOOLVAL
▼ F-GPRS-002 offers the « Mobile Terminated SMS over the GPRS » functionality.
Short messages to a GPRS subscriber can be routed to the SGSN for delivery to the
mobile.
▼ Meaning :
z TRUE: The SMS functionality on the GPRS is offered and short messages can
be routed to an SGSN.
z FALSE: The SMS functionality on the GPRS is not offered and short messages
can be sent only to the MSC.
F-GPRS-002 is meaningful if F-GPRS-001 is TRUE (the HLR supports the
GPRS function).
3.40

3.2 Data structure
F-GPRS-003
▼ F_GPRS_003 in the RCP of the SMS_GMSC

z Sys. Par.: PARNAME = RB_F_GPRS_003, BOOLVAL
z RTDMS database: RELNAME = RYR_SYSB, attribute: D_GPRS03
▼ F-GPRS-003 offers the SMS_MT function for GPRS subscribers.
▼ Meaning :
z TRUE: The SMS function on the GPRS is offered via the MSV and/or the SGSN.
z FALSE: The SMS function is not offered for mobiles on the GPRS.
3.41


3.3 SMS-MT handling handling procedures
3.43

3.3 SMS-MT handling procedures
SMS delivery procedure at the HLR (1/4)
IDLE
1
From the GMSC S_RGI_SM_I
N F_ODB_ 001 Y
Delivery of short messages from set?
a foreign PLMN rejected
N Originating address Y F_SMS_ 006 ODB SMS_TC
CC/NDC belongs to set? check
HPLMN?
N Operator
Y MS Y
Y MAP dialogue N
locked? * A determined
= V1? barring
Data missing or incorrect N Data
N
N
OK? Barring?
TC_U_ABORT
Y Y
Check and adaptation Subscriber has not
MS_ISDN
of the MS_ISDN format subscribed to the
only if F-TR -012 is active
translation* short message service
MS has subscribed
TC_REJECT to SMS? N
N Translation
Y
OK?
A
Y
See SMS
Subscriber’s MS_ISDN process over
not known N MS_ISDN Y GPRS
known? To the
GMSC S_RGI_SM_E
S_RGI_SM_E 1 2
IDLE
3.44
SMS DELIVERY PROCEDURE AT THE HLR (1/4)
F_SMS_006: a routing information request to deliver a short message is rejected when it comes from a foreign PLMN (an
SMS_GMSC).
* MS locked : refer to MSBARR parameter of the xxxSBR command.

N VMSC not present in the subscriber data

MSC address
present?
Y
N Subscriber is not located

MS_registration flag
= registered?
Y
Roaming allowed N Roaming not allowed

for this subscriber?
Y
SMS_MT N SMS_MT function not supported by the VMSC

flag set? Set MNRF
Supplementary service: To be inserted in the

ICB_CHECK
incoming calls barred S_RGI_SM message Memorize
if the subscriber diagnostic
is absent
Call barred?
S_RGI_SM_E
3 4
IDLE
3.45

3
Map V1 Y
dialogue?
MESSAGE PRIORITY N
MANAGEMENT Y
F-SMS-004 N MNRF set?
set?
N
Y Y
MCEF set?
N
SM_RP_PRI Non priority
MW_STATUS Fill MWD_set
taken message
is included in parameter
into account is assumed
inform SC with
message MWD state
Priority Y MS_ISDN = N N MS_ISDN = Y

message? MS_ISDN_alert? MS_ISDN_alert?
N
Y
N Stored_MS_ISDN
MNRF set?
is included in Stored_MS_ISDN
=
Y inform SC MS_ISDN_alert
message
Set MS
Absent subscriber routing
information S_RGI_SM_R
4
S_RGI_SM_R I_SC_I S_RGI_SM_R
IDLE
3.46
F_SMS_004 is for handling message priorities.
The S_RGI_SM_R message containing the routing information is sent to the SMS_GMSC in the following two cases:
• If the short message has priority.
• If the short message has no priority and the MNRF is not set in the HLR database.
The I_SC_I message is sent to the SMS_GMSC after the S_RGI_SM_R if:
• The MNRF and/or MCEF are set.
• The MS_ISDN of the S_RGI_SM_I message is not the same as the MS_ISDN_Alert. The Stored_MS_ISDN
parameter is then replaced by the MS_ISDN_Alert.
Assignment of the MS_ISDN_Alert to a subscriber:
• The MS_ISDN_Alert must be one of the MS_ISDNs assigned to the subscriber for another service.
• In the CRESBR command, the BSERV parameter equals SN_BCN where:
SN = The explicit alert MS_ISDN that needs to be assigned to the subscriber. BCN = SMSMTAL.
• For a subscriber who already has the SMS_MT service but no MS_ISDN_Alert, the following parameters have to be
used in the CHASBR command: NBSERV = MS_ISDN_Alert_SMSMTAL and OBSWOSN = SMSMT.

4 MNRF set MAP version > V1 A
SC address N
included Prepare data for the
in MWD? message:
Y Inform Service Centre
Y MWD full?
N
Stop timer Add SC address
T_MWD to MWD MS_ISDN
Y
=
MS_ISDN_alert?
N
Start timer
T_MWD Stored MS_ISDN
is included in
the message I_SC_I
Fill MWD_set parameter

MAP version Y
of absent subscriber
= V1? S_RGI_SM_E
error with MWD state
N
S_RGI_SM_E I_SC_I
A
IDLE
3.47
T_MWD: timer started for each SC address placed in the MWD list and, when the timer expires, the address is deleted from the
list if no alert procedure has deleted it in the meantime.
By default: 24 hours.
Maximum value: ten days (risk of MWD file congestion).
Stored MS_ISDN = MS_ISDN_Alert

SMS status report procedure at the HLR (1/2)
IDLE
Delivery
N
Outcome =
successful?
R_SMD_S_I S_MW_I Y
SC address
already N
included
Delete SC address in MWD?
matching this Y
Delivery out-
report if present N
come = Absent MWD full?
in the MWD file
subscriber
and stop T_MWD
Y
MWD list is full
Stop
Data not in the timer T_MWD
N
message received Data OK?
or incorrect
Y Clear MCEF Add SC address
and MNRF to MWD
MS_ISDN received in
the S_MW_I N MS_ISDN Y R_SMD_S_R
or known? Report SM Delivery
R_SMD_S_I
message not known
Status
2
R_SMD_S_E
R_SMD_S_E or
Report SM Delivery
S_MW_E Alert SC Error or S_MW_E
A_SC_I
IDLE
3.48
SMS STATUS REPORT PROCEDURE AT HLR (1/2)
The procedure is triggered on short message delivery failure:
• Absent subscriber (IMSI detached, no paging response, LA not authorised)
• Unidentified subscriber
• Memory capacity exceeded
The S_MW_I or R_SMD_S_I message is then sent by the RCF of the SMS_GMSC to the HLR to include the SC address in the
MWD list.
The procedure may also be triggered to notify the HLR that a short message delivery has been successful and so activate the
alert procedure.

SMS status report procedure at the HLR (2/2)
2 If MWD is correctly updated
MS_ISDN = N
MS_ISDN alert?
Y Set Stored
MS_ISDN parameter
Delivery outcome N
=
Memory capacity exceeded
Absent subscriber?
Y
And delete the related reason
Set MNRF Clear MNRF in the MNRR
If the diagnostic is known Store diagnostic

Set MCEF
in MNRR
R_SMD_S_R
or
S_MW_R
Start timer
IDLE
T_MWD
3.49
SMS STATUS REPORT PROCEDURE AT HLR (2/2)

Alert procedure at the RCF in the VMSC
“memory available” notification
3 SEE SMS_MO CHAPTER
The call is release: the SMS_MT function is not supported.

N This means, it is not possible to notify that the memory is available
F_SMS_002
offered?
Y
CP_ACK
BSS
Memorisation of
RP_msg ref
Start timer
TC1N
N
IMEI checked? WAIT FOR CP DATA
Set indicator
ReadyForSM Invoke Message sent by the RCF to the VLR to indicate that “MO subsequent allowed”
R_F_SM_I ; VLR the mobile has regained its memory capacity
WAIT FOR VLR WAIT FOR CP ACK

RESPONSE OR SUBSEQUENT
3.50
HANDLING PROCEDURE AT THE RCP IN THE VMSC

When receiving a notification from the MS that it has memory available to receive one or more short messages, the RCF
performs some checks at the RP level and at the CP layer.
• If functional option F_SMS_002 is not offered, the call is released.
• If all checks succeed, SMO in RCF sends the MAP message Ready_For_SM to the VLR indicating memory available,
which forwards this message to the HLR in case of MAP > V1 dialogue.
• In case of a V1 dialogue with the HLR, the VLR sends back the message Ready_For_SM Error to the RCF, which will
send back an error report to the MS.
Then, the HLR initiates the alert procedure, clears the Mobile station Not Reachable Flag (MNRF) and the Memory Capacity
Exceeded Flag (MCEF) and returns a Ready_For_SM Result to the VLR which forwards it to the RCF.
Then, RCF sends back a successful report to the MS.

Alert procedure at the HLR (1/2)
If one message is correctly received and the MWD is not
Alert SC empty, the HLR for each SC address of the MWD sends
A_SC_I to the IWMSC the message A_SC_I
A
Update MNRF
R_F_SM_I MS_P_I Timer T_MWD and MCEF
From the VMSC expiry and Alert SC, A_SC_I
End TCAP
transaction
Delete SC address
associated to MS
1
N Data missing or incorrect
Data OK?
Subscriber N MS_ISDN not known in the message received

Known?
Y
R_F_SM_R R_F_SM_E
The alert procedure is delayed if neither
MCEF nor MNRF flag is set
N Start T_race and N

MCEF or MNRF MCEF or MNRF
wait for T_race IDLE
set? set?
expiry
Y Y MCEF or MNRF remains set
at true
3.51
ALERT PROCEDURE AT THE HLR (1/2)
MS_P_I, MAP V1 "Note subscriber present".
R_F_SM_I, MAP > V1 with "ms_present" as the reason for the alert.
These two messages are sent by the VLR of the VMSC when one of the following procedures is successful:
• Paging or searching
• Update location area
• Attach IMSI
• Process access request
And the MNRF flag indicates that there is at least one message waiting to be delivered to the mobile.
T_race: timer of the "R_SMD_S_I" message that is started after receipt by the VLR of a message triggering the alert procedure
when neither the MNRF nor the MCEF is set (race situation).

Alert procedure at the HLR (2/2))
1
N
Data OK?
Y
MCEF or MNRF N
set?
Y Start T_race timer and
MCEF or MNRF remains set
wait for T_race expiry at true
MCEF or MNRF N
MCEF or MNRF
reset set?
Y
Alert reason
Clear MNRF, Clear MNRF, MCEF

and and Memory available
Subscriber present related reason MNRR related reason MNRR
N
MCEF set?
Y Alert SC
IDLE
3.52
ALERT PROCEDURE AT THE HLR (2/2)

Send information for SMT at the VLR (1/2)
Message sent by the RCF
IDLE to the VLR to request whether the call
can be offered to the MS
Short message delivery

information request from SINF_SMT_I
the RCF
A
N
* Short message delivery attempt, IMSI known?
even if the IMSI is not known
N Y
F_SMS_003 *?
Y Y
IMSI detached?
Register N
subscriber
N Location area
ID known?
Y
N
Register OK?
Unidentified subscriber Y
Y LA not allowed
N
MNRF
=
MS_DATA = N true
known? A
Search for MS
(SMS_MT) Y
Diagnostic =
SINF_SMT_E SINF_SMT_E IMSI detached
PAGE To the RCF
WAIT FOR
ACCESS
IDLE REQUEST IDLE
3.53
SEND INFORMATION FOR SMT AT THE VLR (1/2)
At the VMSC, on receipt of the F_SM_I or MT_F_SM_I message from the GMSC, the RCF checks that functional option
F_SMS_002 is active and checks the message parameters. If it is received correctly, the RCF asks the VLR if the service can be
offered to the subscriber by sending the SINF_SMT_I message.
If the IMSI is known, the VLR checks that the IMSI is not "detached" and that the LA is known.
• If the IMSI is "detached" or the LA is not authorised, the VLR sets the MNRF to true and informs the RCF of the
VMSC (SINF_SMT_E).
• If all the requirements are satisfied - IMSI not detached, LA authorised and MS data known - the VLR activates the
paging procedure to establish a radio connection with the called mobile.
If the IMSI is not known (at the VLR, but known at the HLR), and
• The F_SMS_003 function is enabled, the search procedure is activated.
• The F_SMS_003 function is not enabled, the VLR sends an error message to the RCF.

Send information for SMT at the VLR (2/2)
WAIT FOR
ACCESS
Page_SMT_R is sent
REQUEST by the RCF when paging is
realised successfully
From the RCF, Page Search Process Access

Search positive
(PAGE_SMT_E) negative result negative result acknowledgement Request
Security_For_
N LAC received Terminating request
Which known in VLR?
LA not known
cause? Y N Authent. Y
Other errors
(MS not equipped…) = OK?
Absent subscriber
Update LAI Search requested
Y
with “IMSI detached” or paging over
Set MNRF = all the cells?
or “No Paging response”
as the diagnostic true
WAIT FOR Calculate LA not N
ACCESS allowed
REQUEST
N Result =
LA not N
Abort?
allowed?
Y
Y
SINF_SMT_E Set MNRF SINF_SMT_R

= true
IDLE
3.54
SEND INFORMATION FOR SMT AT THE VLR (2/2)
In the VMSC, the SINF_SMT_R (COM_SMT_I, Complete Short Message Call) message is sent by the VLR to the RCF to
confirm that the service can be offered to the subscriber.PAGE_SMT_E is transmitted in case of paging failure, mobile not SMS
equipped …

MS ready for SMT at the VLR
Procedure called by the security
MS READY
function when this function has
FOR SMT finished processing
N MNRF In the VLR

= true
Y
The mobile was unreachable
Y before this short message Note subscriber present, to HLR to trigger the alert procedure 1
MAP V1? delivery attempt
N MAP version > V1 Alert procedure triggered, with
“MS present” as the reason ; message sent to the VLR 2
MS_P_I 1 R_F_SM_I 2
Set MNRF = Activation of the T_rfsm timer

Wait for R_F_SM_R
false
R_F_SM_R From the HLR T_rfsm ,

R_F_SM_E
timer expiry
Set MNRF =
false Abort
HLR-VLR
transaction
IDLE
3.55
MS READY FOR SMT AT THE VLR
T_rfsm is the timer supervising receipt of the response to the R_F_SM_I message.

Handling procedure at the RCF of the GMSC (1/8)
An SCCP connection has been set up between
the SC and GMSC (Connection_request and
IDLE
Connection_Confirm). SCCP connection
release timer, T_SCRLS, activated.
Message received from Timer T_SCRLS

RP_MT_DATA Release (RLSD) RP_MO_DATA
the SC
expiry
Stop Timer
T_SCRLS Stop Timer To the SC
Release (RLSD)
T_SCRLS
F_SMS_002 N
enabled?
The origin and destination
SMS_MT function Y addresses are incorrect in the
supported by the GMSC? RP_MT_DATA message
RP_OA and RP_DA N
correct?
Y
Memorize “ More
message to send
if present”
To the HLR S_RGI_SM_I RP_MT_Error To the SC
Wait for Start Timer

IDLE
S_RGI_R from HLR T_SCRLS
3.56
HANDLING PROCEDURE AT THE RCF OF THE GMSC (1/8)
When the SC/GMSC connection is set up, the SC sends the GMSC the first short message to be delivered to the subscriber. At
the SMS_GMSC, the SMS_MT procedure begins when the RP_MT_DATA message is received.
T_SCRLS: timer started by the SMS_GMSC to release the SCCP connection with the SC or supervise the wait for a possible
subsequent message (RP_MT_DATA) from the SC which will be a new short message to be delivered to the same subscriber.

Wait for
S_RGI_R from HLR
S_RGI_SM_R Timer T_SMR Abort S_RGI_SM_E

From the HLR
(TC_End) expiry indication (TC_End)
Abort
transaction
Location information N
=
an MSC address?
Y
RP_MT_ERROR
Store routing
information as
destination address Translation error or
for SM Start Timer other indication in
T_SCRLS the transaction
Incorrect data in the

1 IDLE 2 message received
3.57
ERR_SM_324, a subsequent message is received when a message is being processed.

1 SUCCESS CASE
Other component N No I_SC_I message awaited Analysis of the

present S_RGI_SM_R message
in TC_End?
Y
Memorize mwd_set
Wait for component If present or set it to
false
From the HLR I_SC_I Stored_MS_ISDN

=
MS_ISDN_Alert Reset and memorize
Stored_MS_ISD Y MNRF and MCEF
present?
N Memorize
Stored_MS_ISDN
Memorize MNRF The MW_status field is in the
and MCEF value I_SC_I message.
of MW_status It contains the flags:
-SC_Address_Not_included
-mnrf
-mcef
Y SC_Address_Not_Included N
= true? The SC address is
in the list
Set and memorize Set and memorize
mwd_set = false mwd_set = true True = SC address
not in MWD list
3.58
I_SC_I "InformServiceCenter". This service is used between the HLR and the SMS_GMSC to notify the SC of the MS_ISDN
stored in the MWS list.
The "Stored_MS_ISDN" is the MS_ISDN_Alert. The I_SC_I message:
• contains the MS_ISDN_Alert,
• contains the states of the MNRF and MCEF,
• indicates the presence of a particular SC address in the MWD list.

2 FAILURE CASE
Other component
N
present
in TC_End?
Y
Set RP_MNRF et RP_MCEF
Wait for component with false value in
RP_MT_Error
From the HLR I_SC_I
Fill RP_MT_Error with data received:

Set RP_mwd_set to false Depends on version
if not received use false value
or as received
for MW_status
To the SC in response
RP_MT_ERROR to the RP_MT_DATA message
False value means:

- The MWD file does not contain the SC address Start timer
- Flags are not set T_SCRLS
IDLE
3.59
µThis slide describes the operations performed in the RCF of the SMS_GMSC when the HLR has sent it the S_RGI_SM_E
message.

4
3
LMSI received in N
S_RGI_SM_R? RP_DATA length
process
Y
Y
MAP V1?
RP_data length N
N
IMSI in process OK?
SM_RP_DA Y
F_SM_I To the RCF of the VMSC RP_MT_Error To the SC

LMSI to be
LMSI in inserted if used
SM_RP_DA by the HLR
Reset Start Timer

“ More Message to send ” T_SCRLS
More Message to send N flag
set by SC
Y Reset
“ More Message to send ”
Y flag
MAP V1?
Set “ More Message to send ” Wait for

Wait_More_Message
parameter in F_SM_R from VLR
F_SM_I
3.60

Wait for
F_SM_R from VLR
From VMSC F_SM_R F_SM_R Timer T_fsm Abort indication

F_SM_E
TC_END TC_CONT expiry GMSC/VMSC
Store charging Store charging Abort VMSC

info info 5 transaction
More Message to N
Reset send requested by
“ More Message” SC
to send” flag Y 4
Message received from
Set
the VMSC: F_SM_R,
SMS to the mobile OK
“ More Message”
RP_MT_Ack + Abort transaction
to send” flag to the VMSC
MNRF or MCEF N
memorized was
set?
Y
Set
Start Timer
Report SM delivery “ More Message”
T_SCRLS
to send” flag
Acknowledgement message
RP_MT_Ack
returned to the SC
Start Timer
Wait_More_Message
T_SCRLS
3.61
The "Report SM delivery" procedure is activated at the GMSC to inform the HLR that the short message has been successfully
delivered to the subscriber and to update the MWD list in the HLR.

Message received: F_SM_E,
5 SMS delivery tomobile failed A
N The error in the F_SM_E

Unidentified subscriber message is inserted in the Fill RP_MNRF_set
error? RP_cause field of RP_MCEF_set with
MT_RP_Error memorized values.
Y
_Fill RP_MW_set with
Set absent subscriber Absent subscriber N mwd_set value
diagnostic to unidentified error?
subscriber
Y N SMD delivery
failure error? Search error
Y
MNRFclear N
or mwd_set” = To the SC
false? N Cause = memory
Y capacity exceeded? RP_MT_Error
MNRF was cleared
SMDelivery outcome Y or Y
= mwd_set=false
absent subscriber and
SMDelivery outcome set? N MCEF clear or Start Timer
MWD_set =false? T_SCRLS
N
Store, if present, SMDelivery Y
outcome* and diagnostic In message,
if corresponding MNRF or MWD_set flags
are set to false in the SMS_GMSC Reset “More Message
to send” a flag
Received from the HLR in the
ReportSMDelivery or inform
Report SM delivery
SC message
SMDelivery outcome
Store_MS_ISDN Y Fill RP_alerting_MS = Wait_More_Message
parameter received? of RP_MT_Error memory capacity ex.
N
A
3.62

Wait_More_Message
Abort VMSC
From the SC RP_MT_DATA From the SC RLSD Timer T_SCRLS
transaction
expiry
Stop Timer Stop Timer Stop Timer

T_SCRLS T_SCRLS T_SCRLS RLSD To the SC
Short message for N

the same MS RLSD To the SC
Y “More message to Y
send” flag set?
RP_DATA N
length process
RP_MT_Error Abort transaction To the VMSC
RP_data length Y
process OK?
N
RP_MT_Error
Generate
CDR
Start Timer
F_SM_I T_SCRLS
IDLE
Wait
Wait_More_Message
for F_SM_R from VLR
3.63

Report SM delivery at the RCF of the GMSC
Report SM delivery
N
MAP V1?
MAP > V1
Y
S_MW_I To the HLR

R_SMD_S_I
(TC_Begin) (TC_Begin)
From R_SMD_S_R From R_SMD_S_E Abort indication

Timer T_mwd From the SC RLSD RCF_HLR
the HLR the HLR From the HLR
(TC_End) (TC_End) expiry transaction
Msg sent for Y

Ignore Abort transaction
successful transfer? error RCF-HLR
N
Memorize MCEF
and, Abort transaction
To the HLR
MNRF clear RCF-HLR
At least one Message
Message sent for Y N forwarded?
absent subscriber? Y
N Memorize
MNRF set Generate
CDR
Message sent for N
absent subscriber?
Y
Memorize MNRF
clear and, IDLE
MCEF set
3.64
REPORT SM DELIMERY AT THE RCF OF THE GMSC
This procedure is activated to update the MWD list in the HLR and inform the HLR whether delivery of the short message to the
mobile was successful or not.

Handling procedure at the RCF of the VMSC (1/4)
IDLE
F_SM_I
Phase 1
TC_BEGIN
SMS_MT function supported N

F_SMS_002?
by the MSC
Y
RP_DA is an N
IMSI?
Y
RP_OA is an N
SC address?
Y
SC address length N
< 11 bytes?
Y
F_SM_E or,
To the VLR, to check that the
MT_F_SM_E To the SMS_GMSC
SINF_SMT_I LA is allowed and that the
IMSI is not detached TC_END
Wait_for_Page IDLE
SMT
3.65
HANDLING PROCEDURE AT THE RCF OF THE VMSC (1/4)

Wait_for_Page
Message sent by the VLR when the
SMT
subscriber in unidentified, the IMSI is
unknown or the LA not allowed
Message sent by the VLR to Message sent by the VLR instead of the
the RCF to activate the PAGE SMT message to activate the
PAGE_ SMT_I SEARCH_ SMT_I SMINF_ SMT_E
paging procedure paging procedure when the LA is not
known to the VLR
Y F_PA_003 Y F_ SM_E or To the

MM procedure
Waiting_for_MM_Procedure active? MT_F_SM_E SMS_GMSC
running?
N If a “ MM ” procedure is in progress, N
Wait_for_Page
the RCF waits for the end of the SEARCH_ SMT
SMT
procedure before activating “PAGING” for MS negative To the VLR
N response
RR connection
established?
RR connection N
Y
established?
Y
N MS has SMS
capabilities?
Y N Ms has SMS
capabilities?
Y
1A 1B 1 2A 2B 2 IDLE
3.66

MM procedure allowed and radio
connection not set up with the mobile 1
PAGE_MS_MSC Execution of Paging
N
Result OK? Abort
Y N indication
Result = fail?
MS has SMS N
capabilities? Y
Radio connection set up Y
with the mobile
and mobile can receive short
1B 1A
messages Get_SDCCH
N
Result = fail?
Y
Channel assignment
Initial channel not possible
Y can be used? N
Process_access
request_MSC
To the VLR,
Y Wait_for_answer Page SMT
Result OK? PAGE_ SMT_E negative
from_VLR
response
N
Security procedure, IMSI check,

LAC check, enciphering, F_SM_E
TMSI IDLE or MT_F_SM_E To the SMS_GMSC
TC_End
3.67

MM procedure allowed and radio
connection not set up with the mobile 2
SEARCH_FOR_MS_MSC Execution of the searching procedure

with LA unknown to the VLR
N
Result OK? Abort
Y N indication
Result = fail?
MS has SMS N
capabilities? Y
Radio connection set up Y
with the mobile
and mobile can receive short
2B 2A
messages Get_SDCCH
N Y
Result = fail? Channel assignment
not possible
Initial channel
To the VLR Y can be used? N
Message containing Search SMTfor SMS ack
the current LA reference
Process_access
request_MSC
Y Wait_for_answer
Result OK? SEARCH_ SMT_E To the VLR
from_VLR
N
F_SM_E
IDLE or MT_F_SM_E To the SMS_GMSC
TC_End
3.68

Alert procedure at the RCF of the IWMSC (1/2)
IDLE
Alert service centre

Messages received from Alert service centre,
without result
(TC Begin) the HLR (TC_Begin)
MS_ISDN is N MS_ISDN is N
correct? correct?
Y Y
Alert Service
End TCAP
To the HLR Centre error To the HLR
transaction (TC_End)
IDLE IDLE
Alert message sent to

RP_Alert
the SC
Start timer
T_wait_SCCP
Wait
T_WAIT_SCCP
3.69
ALERT PROCEDURE AT THE RCF OF THEIWMSC (1/2)

Alert procedure at the RCF of the IWMSC (2/2)
Wait
T_WAIT_SCCP
From the HLR Abort indication T_Wait_SCCP

expiry
Stop timer
To the HLR,
T_wait_SCCP Abort
transaction
Dialogue MAP N
HLR/IWMSC
version 1?
Cause =SCCP Y
IDLE Y
translation failure?
Warning N
WR_SM_300
Analysis of the SC
address not possible To the HLR,
End TCAP Alert Service
Dialogue MAP alert message
N transaction centre result
acknowledgement
version 1?
End TCAP Alert Service

To the HLR centre error To the HLR
transaction (TC_End)
IDLE
IDLE
3.70
ALERT PROCEDURE AT THE RCF OF THEIWMSC (2/2)

In case of SCCP translation failure the following spontaneous message is issued:
WR_SM_300
wording CALLED NUMBER/SCCP ROUTE TRANSLATION FAILURE CLDLEN= CLDNBR=
meaning This warning is edited when the analysis of the called number to determine the SCCP route
information has failed (No SCCP route from MSISDN number or from MSC address or from SC
address).
parameters CLDLEN = Called number length
CLDNBR = Called number

Evaluation
▼ Objective: to be able to solve a problem

related to the short message mobile
terminated service
Thank you for answering the self

assessment of the objectives sheet
3.71


Handling of SMSMT

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Handling of SMSMT

Hochgeladen von

Copyright:

Verfügbare Formate

3 Handling of the short message mobile

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.1

▼ Objective: to be able to solve a problem related to

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.2

3.1 Short message mobile terminated service scenario

3.2 Data structure

3.3 SMS-MT handling procedure

Handling procedure at the RCF of the GMSC 56

Report SM delivery at the RCF of the GMSC 64

Handling procedure at the RCF of the VMSC 65

Alert procedure at the RCF of the IWMSC 69

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.3

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.4

3.1 short message mobile terminated service scenario

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.5

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.6

MNRF MCEF MNRF

MS_ISDN Alert MWD SC address n

DATA AND FLAG ASSIOCIATED WITH THE SERVICE

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.7

Data concerning the SMS

Row1 Row2 Row3 Row4 Row5 Row6 Row7

Time- Time- Time- Time- Time- Time- Time-

• HY_LMSI HYM_LMSI /*Local identifier of a mobile, parameter registered on location updating*/

• HY_MSC_I HYM_MSC_N /*ISDN number of the MSC*/

• HY_LMS_F HYM_LMS_FLAGS /*Restoration and location flags:

MNRF (HY_MNRF) bit 13 bool

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.8

SC SMS-GMSC HLR RCF VLR

SUBSCRIBER SHORT MESSAGE DELIVERY (1/4)

If the procedure must be handled, the HLR checks:

1) the validity of the fields in the received S_RGI_SM_I message,

2) that the mobile station can be identified from its MS_ISDN,

3) that the MS is not blocked or restricted by ODB,

4) that the subscriber has subscribed to the SMS_MT service,

5) that the MS is located,

7) that the subscriber has no roaming restrictions.

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.9

In MAP >V 1, the HLR sends the I_SC_I message:

After sending the S_RGI_SM_R message if:

At the SMS_GMSC, if:

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.10

SC SMS-GMSC HLR RCF VLR

SUBSCRIBER SHORT MESSAGE DELIVERY (2/4)

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.11

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.12

ANALYSIS OF SHORT MESSAGE LENGTH

No need for MAP MAP Short message

SUBSCRIBER SHORT MESSAGE DELIVERY (3/4)

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.13

SC SMS-GMSC HLR RCF VLR

REPORT_SM_DELIVERY_STATUS_INV S_MW_I or R_SMD_S_I

REPORT_SM_DELIVERY_STATUS_RES S_MW_R or R_SMD_S_R

CASE :Short message delivery failure

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.14

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.15

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.16

MAP V1, V2 MAP V3

SM_RP_DA, IMSI, LMSI, SM_RP_DA, IMSI, LMSI,

MoreMessageToSend, positioned according to the MoreMessageToSend, positioned according to the

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.17

The RPDU field of the CP_user data parameter may contain:

This message is used to convey error information in the CP_Cause field.

© Alcatel University - 8AS 90200 0830 VH ZZA Ed.01 Page 3.18

• HY_LMSI HYM_LMSI /Local identifier of a mobile, parameter registered on location updating/

• HY_MSC_I HYM_MSC_N /ISDN number of the MSC/