SMS procedures performed by MAP

http://127.0.0.1:43231/NED/NED?service=printview&library=mschlr_r...

Library:

MSC/HLR, Rel. M14.1, Product Documentation, v.1

Identifier: dn60004908-3-en

SMS procedures performed by MAP The following figure illustrates the MO-SMS and MT-SMS from the point of view of MAP:

Figure: MT-SMS and MO-SMS procedures performed by MAP Note Numbers 1 6 in the figure apply to MO-SMS and numbers 7 14 to MT-SMS

The numbers given in the figure refer to the following: 1. RP-MO-Data 2. FwdSMarg 3. SC_RP_MO_DATA 4. SC_RP_MO_ACK 5. FwdSMres 6. RP-MO-Ack 7. SC_RP_MT_DATA 8. SRIforSMarg 9. SRIforSMres 10. FwdSMarg 11. RP-MT-Data

1 of 5

7/17/2010 10:16 PM

SMS procedures performed by MAP

http://127.0.0.1:43231/NED/NED?service=printview&library=mschlr_r...

12. RP-MT-Ack 13. FwdSMres 14. SC_RP_MT_ACK The following paragraphs explain the procedures in detail: 1. MobileOrginatingSM The MO SMS procedures are used to forward an SM from a mobile subscriber to an SMSC. The MAP offers a procedure which can be used to transfer an MO-SM from the VMSC to the SMS-IWMSC. a. MO SMS transfer procedure in MAP version 1 and version 2: ForwardSM (FSM) begins a dialogue, and the VMSC sends the operation in the TC-BEGIN message when it receives an SM from the MS. If the SMS-IWMSC knows the SMSC, it transfers the SM to it. When the SMS-IWMSC receives a response for the SM from the SMSC, it transfers the response to the VMSC. 2. RoutingInfoEnquiryForSM The SM handling function of the SMS-GMSC requests the routing information from the HLR when it receives an MT-SM from the SMSC. When the routing information is received, and the subscriber is registered in the MSC area in question (SMS-GMSC), the SMS-GMSC itself sends the MS to the MS. Otherwise the SMS-GMSC transfers the SM to the VMSC. RoutingInfoEnquiryForSM procedures offered by MAP are different in InformServiceCentre operation to tell the SMSC which ISDN number is used to indicate the availability of the SM for SMs. a. RoutingInfoEnquiryForSM procedure in MAP version 1: SendRoutingInfoForSM (SRI-SM) begins a dialogue, and the SMS-GMSC sends the operation in the TC-BEGIN message when it receives an SM from the SMSC. After handling the procedure, the HLR sends the result or an error message for SRI-SM in TC-END. b. RoutingInfoEnquiryForSM procedure in MAP version 2: The SendRoutingInfoForSM (SRI-SM) begins a dialogue, and the SMS-GMSC sends the operation in the TC-BEGIN message when it receives an SM from the SMSC. After handling the procedure, the HLR sends the result or an error message for the SRI-SM in the TC-END message. The HLR can send an optional InformServiceCentre operation which is packed in the same network primitive as the SRI-SM result/error. 3. MobileTerminatingSM The MT-SM transfer procedure is used to forward an SM or several SMs from an SMSC to a mobile subscriber. The MAP offers a procedure which can be used to transfer an MT-SM from the SMS-GMSC to the VMSC. MT-SM transfer procedures offered by MAP are different in the MAP versions 1 and 2. In version 1, only one SM can be transferred during a dialogue, but in version 2, several SMs can be transferred during the same dialogue. a. MT-SM transfer procedure in MAP version 1: ForwardSM begins a dialogue, and the SMS-GMSC sends the operation in the TC-BEGIN message if it has received routing information from the HLR, indicating that the subscriber is registered in another MSC area. If the subscriber is reachable, the VMSC sends him/her the SM. When the VMSC receives a response for the SM from the MS, it transfers the response to the SMS-GMSC. After receiving the response, the SMS-GMSC may start ReportSM-DeliveryStatus, in any case, it transfers the responses to the SMSC. b. MT-SM transfer procedure in MAP version 2: The ForwardSM operation can appear several times in a dialogue. Furthermore, the first FSM may contain only the MAP-OPEN PDU if the PDU and the SM are too large to fit together in one TCAP primitive. The ForwardSM begins a dialogue, and the SMS-GMSC sends the operation in the TC-BEGIN message if it has received routing information from the HLR indicating that the subscriber is registered in another MSC. If the message is too long to fit in the network message frame, only the MAP-OPEN-PDU is sent in the

2 of 5

7/17/2010 10:16 PM

SMS procedures performed by MAP

http://127.0.0.1:43231/NED/NED?service=printview&library=mschlr_r...

TC-BEGIN message, and the message part is sent separately after that. If the MS can be reached, the VMSC sends an SM to it. When the VMSC receives a response for the SM from the MS, it transfers the response to the SMS-GMSC. After receiving the response, the SMS-GMSC can start the ReportSM-DeliveryStatus, in any case, it transfers the responses to the SMSC. In the multiple SM transfer, the FSM service can be used several times. The FSM is always acknowledged to the SMSC before the next SM is sent. 4. ReportSM-DeliveryStatus Note This operation was called SetMessageWaitingData in the old specification.

If the MT-SM transfer fails, the SMS-GMSC can inform this to the HLR by using the ReportSM-DeliveryStatus operation. The following figure illustrates a situation where MT-SM sending fails and the HLR is notified:

Figure: MT-SM sending fails, HLR is notified The numbers given in the figure refer to the following: a. SRIforSMarg/res b. FwdSMarg/res c. ReportSM-Delivery Status arg d. ReportSM-Delivery Status res The SMS-GMSC informs the HLR if an absent subscriber, unidentified subscriber, or SM delivery failure with 'error cause MS memory capacity exceeded' indication is received from the visited MSC, and the corresponding flags received in the InformServiceCentre operation are not already set, or the SMSC address is not yet included in the MWD set. The SMS-GMSC may also invoke the procedure when the transfer was successful, if the MNRF and MCEF flags, or both, were set in the HLR. a. ReportSM-DeliveryStatus procedure in MAP version 1 and version 2: ReportSM-DeliveryStatus (RSM-DS) begins a dialogue, and the SMS-GMSC sends the operation in the TC-BEGIN message when it receives ForwardSM response from the VMSC. After handling the procedure, the HLR sends the result or an error message for RSM-DS in the TC-END message. 5. ReadyForSM When receiving the ProcessAccessRequest or UpdateLocationArea indication from the MS, while the MS not reachable flag (MNRF) is set, the VLR starts the ReadyForSM procedure to the HLR. The ReadyForSM procedures offered by MAP are different in MAP versions 1 and 2.

3 of 5

7/17/2010 10:16 PM

SMS procedures performed by MAP

http://127.0.0.1:43231/NED/NED?service=printview&library=mschlr_r...

a. ReadyForSM in MAP version 1 The NoteSubscriberPresent operation begins and ends a dialogue, and the VLR sends the operation in the TC-BEGIN message to the HLR. Because this is a class 4 operation, and the procedure does not contain any other operations, the dialogue is ended immediately. b. ReadyForSM in MAP version 2 The ReadyForSM operation begins a dialogue, and the VLR sends the operation in the TC-BEGIN message to the HLR. If an error occurs in the HLR, the HLR sends an error message containing UnknownSubscriber, DataMissing, FacilityNotSupported and SystemFailure, otherwise it sends an empty result for the ReadyForSM in the TC-END message to the VLR. 6. Alert-SC When the subscriber has an SMSC address or addresses in the MWD, and the HLR receives ReadyForSM, UpdateLocation or Supplementary Service Control request for this subscriber, it can start Alert-SC procedure to all SMSCs included in the subscriber's MWD. The Alert-SC procedures offered by MAP are different in MAP version 1 and 2. a. Alert-SC in MAP version 1 The Alert-SC-WithoutResult operation begins and ends a dialogue, and the HLR sends the operation in the TC-BEGIN message. Because this is a class 4 operation, and the procedure does not contain any other operations, the dialogue is ended immediately. b. Alert-SC in MAP version 2 The Alert-SC operation begins the dialogue, and the HLR sends the operation in the TC-BEGIN message to the SMS-IWMSC. If an error occurs in the HLR, the HLR sends an error message containing the UnknownSubscriber, DataMissing, FacilityNotSupported and SystemFailure, otherwise it sends an empty result for Alert-SC in the TC-END message. The following figure illustrates the ReadyForSM and Alert-SC procedures:

Figure: ReadyForSM and Alert-SC procedures The numbers given in the figure refer to the following: 1. NoteMSpresent (MAP 1) ReadyForSMarg 2. Ready res 3. AlertSCwithoutRes Arg (MAP 1) AlertSC Arg 4. AlertSCRes

4 of 5

7/17/2010 10:16 PM

SMS procedures performed by MAP

http://127.0.0.1:43231/NED/NED?service=printview&library=mschlr_r...

For more information, see MAP in SMS and Interfaces between SMS network elements. Printed from NED5 Copyright Nokia Siemens Networks. All rights reserved.

5 of 5

7/17/2010 10:16 PM