1 Routing

1.1 SMS scenarios

A number of SMS scenarios are analyzed to determine what nodes are utilized during the transfer of SMS traffic for both Mobile Originating and Application Originating traffic. Call flow sequences are used to show the flow of traffic through the relevant nodes for each particular traffic case. The following SMS scenarios are considered Mobile Originating SMS !MO " MT SMS# Application Terminating SMS !MO " AT SMS# Application Terminating $remium SMS !MO " AT $remium SMS# Application Originating SMS !AO " MT SMS# Application Originating $remium SMS !AO " MT $remium SMS#

%or the above scenarios the A&party and '&party can be one of the following A&party ($)M*+ ,$)M* !roaming#+ )arge Account+ )arge Account $remium '&party ($)M*+ ,$)M* !roaming#+ )arge Account+ )arge Account $remium+ O)O !Other )icensed Operator#+ O)O !roaming# 'illing is not considered in these scenarios+ only SMS transfer on a high level+ so the billing nodes and procedures are not included in the call flows.

1.1.1

MO MT SMS

%igure -&- depicts the call flow for a Mobile Originating SMS generated by a subscriber.

Figure 1-1: Mobile Orignating SMS

1 2 3 4

A subscriber sends an SMS and the MS forwards the message to the MSC.,)/. The MSC.,)/ forwards the SM to the SMSC and is sub0ected to the routing rules defined in the Te1t$ass rule base. The SM is forwarded by means of a MA$&MO&%O/2A/3&S(O/TM4SSA54 and contains the 3estination Address+ Originating Address and the Short Message itself. The SMS initiates a Send /outing 6nformation !S/6# to chec7 whether the A&number and '&number are allowed to use the SMSC. 6f S/6 response contains an 6MS6 from the operator defined range the SMS is allowed. 6f according to the T$/ !Te1t$ass /outer# rule base the SMS should be sent+ the SM is routed to the AMS !Active Message Store# where it is stored. The SMSC attempts to deliver the SMS to the '&party " this can be done with or without %irst time 3elivery Attempt !%3A#+ in which case the SMS will either be delivered immediately or on a subsequent try. After the delivery attempt+ ac7nowledgement responses are sent bac7 through the route to the MS.

Figure 1-2: Mobile Originating SMS

1.1.2

MO AT SMS

%igure -&8 depicts the call flow for a mobile originating SMS+ terminating at a )arge Account

Figure 1-3: Application Terminating SMS

1 2 3 4 5 6 7 8

A subscriber sends an SMS and the MS forwards the messages to the MSC.,)/. The MSC.,)/ forwards the SM to the SMSC and is sub0ected to the routing rules defined in the Te1t$ass rule base. The SM is forwarded by means of a MA$&MO&%O/2A/3&S(O/TM4SSA54 and contains the 3estination Address+ Originating Address and the Short Message itself. The SMS initiates a Send /outing 6nformation !S/6# to chec7 whether the A&number and '&number are allowed to use the SMSC. 6f S/6 response contains an 6MS6 from the Operator defined range the SMS is allowed. 6f according to the T$/ rule base the SMS should be sent+ the SM is routed to the AMS where it is stored. The SMSC sends a response bac7 to the MSC by means of a MA$&MO&%O/2A/3&S(O/TM4SSA54 AC9 message+ which in turn delivers a response to the MS. A )arge Account !)A# opens a session by means of a :C$;< Session management operation to the Application 5ateway !A52#. The SMSC forwards the message to the Application 5ateway. The message is sent by the Application 5ateway to the )A as a :C$=> message+ which in turn replies with an ac7nowledgement. The Application 5ateway sends a 3eliverSM/esponse bac7 to the SMSC.

Figure 1-4: Application Terminating SMS

1.1.3

MO AT Premium SMS

%igure -&= depicts the call flow for a mobile originating SM+ terminating at a $remium )arge Account.

Figure 1-5: Application Terminating Premium SMS

1 2 3 4 5 6 7 8

A $remium MT )arge Account opens a session by means of a :C$;< Session management operation to the Application 5ateway with the corresponding large account settings. A subscriber sends an SMS and the MS forwards the messages to the MSC.,)/. The MSC.,)/ forwards the SM to the SMSC and is sub0ected to the routing rules defined in the Te1t$ass rule base. The SM is forwarded by means of a MA$&MO&%O/2A/3&S(O/TM4SSA54 and contains the 3estination Address+ Originating Address and the Short Message itself. The SMS initiates a Send /outing 6nformation !S/6# to chec7 whether the A&number and '&number is allowed to use the Telfort SMSC. 6f S/6 response contains an 6MS6 from the Operator defined range the SMS is allowed. The SMSC forwards the message to the Application 5ateway as a 3eliverSM message. The message is sent by the Application 5ateway to the $remium )arge Account as a :C$=> message+ which in turn replies with an ac7nowledgement. The Application 5ateway sends a 3eliverSM/esponse bac7 to the SMSC. The SMSC sends a response bac7 to the MSC by means of a MA$&MO&%O/2A/3&S(O/TM4SSA54 AC9 message+ which in turn delivers a response to the MS.

Figure 1- : Application Terminating Premium SMS

1.1.4

AO MT SMS

%igure -&? depicts an application originating SMS+ terminating at the Operator@s subscriber.

Figure 1-!: Application Originating SMS

1 2

4 5 6 7 8

A )arge Account opens a session by means of a :C$;< Session management operation to the Application 5ateway with the corresponding large account settings. The Application 5ateway logs into the SMSC via a :C$;< message using the corresponding )A parameters as received from the )A itself. The )A then submits a SM to a subscriber by means of a :C$=- Submit Short Message operation to the A52. Subsequently the A52 sub0ects this SM to the rules as defined in the Te1t$ass rule base and performs defined actions if needed and routes the message to the SMSC+ which in turn ac7nowledges this message towards the )A via the A52 by means of a :C$=- Submit Short Message operation AC9 message. The SMSC needs to receive routing information from the ()/ for routing the SM to the serving MSC by means of MA$&S4*3&/O:T6*5&6*%O&%O/&SM message. The ac7nowledgement from the ()/ is routed to the 5MSC by means of a MA$&S4*3&/O:T6*5&6*%O&%O/&SM&AC9 message. The ()/ response may be a foreign 6MS6+ MSC and.or S5S* address and another national operator@s 6MS6. The SMSC forwards the SM to the serving MSC by means of a MA$&MT&%O/2A/3&SM message. At the serving MSC the ,)/ is interrogated for subscriber related information by means of a MA$&S4*3& 6*%O&%O/&MT&SMS+ and the SM is forwarded to the MS of the destined subscriber. The serving MSC will inform the SMSC of the status of forwarding by means of a MA$&MT&%O/2A/3&SMS& AC9 message. The SMSC sends a delivery notification to the Application 5ateway to indicate the status of the submitted SM. The Application 5ateway sends a delivery notification to the )A to indicate the status of the submitted SM by means of a :C$=8 3elivery notification operation.

Figure "-": Application Originating SMS

1.1.5

AO MT Premium SMS

The call flow of an application originating premium SMS delivered to the operator@s subscriber follows the same process as e1plained in AO " MT SMS !Section -.-.A# apart from some additional billing procedures. The billing system is not ta7en into consideration for these scenarios+ so from an SMS transfer prospective the routing process of AO " MT SMS also applies to AO&MT $remium SMS.