23.2.1 Procedure in the serving MSC

29.0023GPPMobile Application Part (MAP) specificationRelease 17TS

Any CAMEL-specific handling defined in this clause is omitted if the MSC does not support CAMEL control of MO SMS, or if the subscriber does not have a subscription for CAMEL control of MO SMS.

The process starts when the MSC receives a short message from the MS. The process invokes macros not defined in this clause; the definitions of these macros can be found as follows:

Receive_Open_Cnf see clause 25.1.2;

Check_Indication see clause 25.2.1;

Check_Confirmation see clause 25.2.2.

Sheet 1: If the MSC is integrated with the SMS-IWMSC, it communicates directly with the Short Message Service Centre (SMSC) using one of the protocols described in 3GPP TS 23.039 [25a]; otherwise it communicates with the SMS-IWMSC using MAP.

Sheet 3: If the capacity of a message signal unit in the lower layers of the protocol is enough to carry the content of the MAP_OPEN request and the content of the MAP_MO_FORWARD_SHORT_MESSAGE request in a single TC message, the test "Message segmentation needed" takes the "No" exit; otherwise the test takes the "Yes" exit.

Sheet 3:The decision box "TCAP Handshake required" takes the "yes" or "no" exit depending on agreements between the serving MSC’s operator and the SMS-IWMSC’s operator (see 3GPP TS 33.204 [34a]).

The mobile originated short message service process in the MSC is shown in figure 23.2/2.