SMS Call flow , GSM , SMSC call flow, SMSCG detail

MSCDOCM13 M13.0 Product Documentation SMS Guide dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 1 (267) SMS Guide The information in this documentation is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia's customers only for the purposes of the agreement under which the documentation is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia and the customer. However, Nokia has made all reasonable efforts to ensure that the instructions contained in the documentation are adequate and free of material errors and omissions. Nokia will, if necessary, explain issues which may not be covered by the documentation. Nokia's liability for any errors in the documentation is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this documentation or the information in it. This documentation and the product it describes are considered protected by copyright according to the applicable laws. NOKIA logo is a registered trademark of Nokia Corporation. Other product names mentioned in this documentation may be trademarks of their respective companies, and they are mentioned for identification purposes only. Copyright © Nokia Corporation 2005. All rights reserved. 2 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en Contents Contents Contents 3 List of tables 6 List of figures 7 Summary of changes 11 1 1.1 1.2 1.3 1.3.1 1.3.2 1.4 1.4.1 1.4.2 1.4.3 1.4.4 1.5 1.6 1.6.1 1.6.2 1.7 1.8 1.9 1.10 1.11 1.12 1.12.1 1.12.2 1.12.3 1.12.4 1.13 1.14 1.14.1 1.14.2 1.14.3 1.15 1.15.1 1.15.2 1.16 1.17 1.17.1 1.17.2 1.17.3 1.18 Short Message Services 15 Short Message Services Overview 17 SMS information elements 18 Mobile-originating short message 21 MO-SM procedure 22 Unsuccessful MO-SM delivery 24 Mobile-terminating short message 24 MT-SMS procedure 25 Unsuccessful MT-SM delivery 27 More-messages-to-send 30 Command SM and MO-SM with Status Report request 30 SMSC Alert 34 SMS load sharing 36 SMRSE over X.25 36 SMRSE over TCP/IP 38 Barring SMS in the MSC 41 Welcome SM to the roamer 46 Real Time triggering 47 Incoming Call Treatment 50 Missed Calls Log Service 51 Short Message Service on GPRS 52 SMS over GPRS with MAP version 2 53 SMS over GPRS with MAP version 3 54 Comparative example of SMS over GPRS with MAP version 2 and MAP version 3 59 GPRS with SMSC-MSC connection through MAP interface 62 IN Short Message functionality 63 CAMEL short message service 65 Control of MO-SM with CAMEL 66 Control of MT-SM with CAMEL 71 Interworking between CAMEL SM and IN SM 75 Short message routing 76 SMS routing enhancements 80 Short message routing based on subscriber type 81 Sending SMS without SMSC 82 SMS Forwarding 87 Basic forwarded MT-SMS 87 Provisioning and activating SMS forwarding 89 MMI procedures to activate SMS forwarding 89 Same CLI for multiple subscribers 89 dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 3 (267) SMS Guide 1.19 1.19.1 1.19.2 1.20 1.20.1 1.20.2 1.20.3 1.20.4 1.20.5 1.20.6 1.21 1.21.1 1.21.2 1.22 1.22.1 1.22.2 1.22.3 1.22.3.1 1.22.3.2 1.22.4 1.22.5 1.22.6 1.22.7 1.23 1.23.1 1.23.2 1.23.3 1.24 2 2.1 2.1.1 2.2 2.2.1 2.2.2 2.2.3 2.3 2.3.1 2.3.2 2.3.3 2.4 2.4.1 2.5 3 4 4.1 4.2 4.3 4.4 Sequential alerting and parallel alerting for MultiSIM Service 90 Delivery of mobile-terminating short messages 91 MT-SMS routing to the primary member 91 Short message charging 91 SMS charging for subscribers 95 Charging of SMs generated by applications 97 Charging of SMs to service applications 98 Charging of CAMEL SMs 99 MO-SM fraud prevention 100 Mobile number portability solutions for MO-SM charging 100 SMS-related statistics 101 SMS statistics in the MSC 102 SMS statistics in the HLR 107 Network elements involved in SMS 108 SME 109 SMSC 109 VMSC and VLR 110 VMSC and VLR in MO-SM procedure 110 VMSC and VLR in MT-SM procedure 113 SMS-IWMSC 117 SMS-GMSC 117 HLR 118 Traffica 120 Interfaces between SMS network elements 121 A interface in SMS 122 SMRSE in SMS 122 MAP in SMS 125 Subscriber interface of SMS 128 Configuring network elements for SMS 131 Configuring MAP interface for SMS 132 Creating global title analysis 133 Configuring X.25 interface for SMS 138 Connecting the SMSC to the SMS-GMSC/SMS-IWMSC 138 Creating analysis on SMS application level in the MSC 148 Setting parameters so that GSM phase 2+ and MT-SM are supported 151 Configuring TCP/IP connection for SMS 153 Connecting the SMSC to the SMS-GMSC/SMS-IWMSC 153 Creating analysis on SMS application level in the MSC 155 Setting parameters so that GSM phase 2+ and MT-SM are supported 156 Handling SMS-related MAP operations in MSC and HLR 158 Handling Error counters in SMS 160 Handling the Welcome SM related parameters 161 Managing SMS subscriber-specific data 165 Managing SMS network element-specific data 171 Handling User Data in SMS 171 Handling of MNRR in SMS 172 Activating selective CDR generation in SMS 173 Activating Picture message information in the CDR 175 4 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en Contents 4.5 4.5.1 4.5.2 4.6 4.7 5 5.1 5.2 5.3 5.4 5.5 5.6 6 6.1 6.2 6.3 7 7.1 7.2 7.3 7.4 8 8.1 8.2 8.3 8.3.1 8.4 8.5 8.6 8.7 8.8 8.9 8.9.1 8.9.2 Preventing SMS 175 Preventing MT-SMS 176 Preventing MO-SM 177 Activating SMS measurement 179 Activating routing enhancement in SMS 181 Activating Nokia-specific SMS features 183 PNP numbering for SMS (MO) 183 Handling of IN SMS 185 Activating Real Time triggering 186 Activating MT-SM for Camel Phase 4 189 Activating Direct SM delivery 189 Activating B-IMSI retrieval in MO-side for MNP 190 Working examples for SMS management 191 Configuring network elements for short message services with load sharing 191 Configuring network elements for short message services with more MSCs connected to the same SMSC 200 Configuring network elements for SMS with load sharing of SMSC clusters when the traffic category is normal traffic 208 Short Message Service Troubleshooting 229 Problems related to SMS network elements 229 Problems related to SMS A interface 230 SMS problems related to SMRSE interface 232 Problems related to SMS charging 236 Additional information on SMS 239 MT operation in VMSC 239 SMS procedures performed by MAP 245 Comparison of the SMS functionalities in case of SMRSE over X.25 or TCP/IP and SS7 MAP SMSC 251 Functional differences between SMRSE over X.25 or TCP/IP and SS7 MAP SMSC 253 Functions of SMSC level in SMS 256 Alarms and their meanings in Short Message Service 257 SMS-related general parameter file (PRFILE/FIFILE) parameters 260 Parameters needed for CAMEL SM 264 Parameters for SMS A-interface configuration 265 Parameters needed for Sending SMS without SMSC 266 FIFILE parameter 266 PRFILE parameters 266 dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 5 (267) Table 5. Explanation of bytes in UTPFIL records 199 104 6 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Clear codes involved in SMS measurement counter update Table 11. Table 6. Table 9. criteria and types of control DPs used for the MO SMS State Model DPs used for the MT-SMS state model Example of a routing table 78 95 Types of CDR and network elements Table 10.SMS Guide List of tables Table 1. Table 2. Table 7. Table 8. Table 3. Short Message Services overview MNRR reason codes 28 37 17 Distribution of number range in available SMSCs Error codes in MT-SMS barring 44 48 67 73 Events. Table 4. case 2 Figure 15. Figure 3. Operation of Real Time triggering Figure 20. Basic Short Message Service procedure 15 16 Key characteristics of Short Message Service MO-SM successful case 21 23 MO-Forward SMS procedure MT-SM successful case 25 MT-Forward-SMS procedure 26 31 33 34 SMS command and status report Successful MO-SM transfer with SMSC-GT-1 parameter Successful MT-SM transfer with the SMSC-GT-1 parameter 35 37 40 42 43 43 44 Figure 10. Overview of involved network elements Figure 21. MS detached for GPRS Figure 22.List of figures List of figures Figure 1. MO-SMS barring configured to the VMSC. Figure 2. case 1 Figure 14. MT-SMS barring. CAMEL mobile-originating short message Figure 27. Figure 8. MO-SMS barring configured to the IWMSC. SMS over MAP interface 60 62 55 Figure 24. Figure 6. Case 2 45 46 48 53 Figure 19. MO-SMS barring configured to the IWMSC. Figure 7. SMS load sharing Figure 12. Case 1 Figure 18. Sending SMs over GPRS Figure 23. Mobile-terminating short message delivery. Functional architecture for the support of CAMEL control of MSC-switched MO SMS 66 Figure 25. Figure 5. CAMEL mobile-originating short message with notification of successful submission to gsmSCF 70 dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 7 (267) . case 2 Figure 17. The use of MO-SMS Limiter in load sharing Figure 13. Figure 9. MT-SMS barring. SMSC alerting Figure 11. case 1 Figure 16. MO-SMS barring configured to the VMSC. MO SMS state model 67 68 Figure 26. Figure 4. SMSC address used in MT-SMS between different network elements 79 Figure 33. OSI compared to ITU-T No. Network elements involved in SMS Figure 46. MT-SMS successful case (positive response) Figure 44. GT analyses in the SMS-GMSC/SMS-IWMSC. Unsuccessful SM delivery. MO-SMS request 111 Figure 40. MT-SM interfaces 131 132 134 130 Figure 54. Functional architecture for the support of CAMEL control of MSC-switched MT SMS 72 Figure 29. 7 126 Figure 49. Unsuccessful SM delivery. absent subscriber Figure 37. Short message routing based on prepaid and post-paid subscribers Figure 34. Charging of SMs generated by applications Figure 39. SMS routing 77 Figure 32. MT-SMS request 114 115 Figure 43. MO-SMS unsuccessful case (negative response) Figure 42. Protocol stack for SMS with TCP/IP Figure 48. MAP-Gd interface in the SMS GSM Phase 2+ network architecture 128 Figure 50. the result is the HLR Figure 55. CAMEL mobile-terminating short message Figure 31. MT-SMS unsuccessful case (negative response) Figure 45. GT analyses in the SMS-GMSC. OSI protocol stack 123 125 121 115 Figure 47. Successful SM delivery 85 86 86 81 Figure 35. MO-SM interfaces Figure 53. An example for alphanumeric addressing from the MS Figure 52. MT SMS state model 73 74 Figure 30. An example for hexadecimal numbers used in alphanumeric addressing 129 Figure 51. MO-SMS successful case (positive response) 112 113 Figure 41. Basic forwarded MT-SMS functionality 87 98 Figure 38. the result is the VMSC 134 8 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . no paging response Figure 36.SMS Guide Figure 28. MT-SM in the MSC. the result is SMS-IWMSC 135 135 136 Figure 57. channel handover. Real-life configuration with load sharing and more MSCs connected to the same SMSC 201 Figure 64. GT analyses in the VMSC. SM resending takes place Figure 68. channel handover. MT-SM in the MSC. MT-SMS and MO-SMS procedures performed by MAP Figure 70. SM resending takes place Figure 69. GT analyses in the SMS-GMSC. Real life configuration with load sharing of SMSC clusters Figure 65. GT analyses in the HLR. T1 expires. the result is the SMS-GMSC Figure 59. Real-life configuration with load sharing 192 Figure 63. MT-SM sending fails. the result is the VMSC Figure 61. An example of outputting a subscriber's SMS data Figure 62. SMS architecture in case of SS7 MAP 253 Figure 74. MT-SM in the MCS. ReadyForSM and Alert-SC procedures 249 251 252 245 243 Figure 72. the result is the SMS-IWMSC Figure 58.List of figures Figure 56. no SM resending 209 240 241 242 Figure 66. the result is the HLR 137 138 167 Figure 60. GT analyses in the SMS-IWMSC. MT-SM in the MSC. channel handover.25 or TCP/IP Figure 73. Successful MT-SM transfer with two new parameters towards the SMSC 257 dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 9 (267) . HLR is notified Figure 71. GT analyses in the VMSC. SMS architecture in case of SMRSE over X. SM resending takes place Figure 67. SMS Guide 10 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Subsection Control of MT-SM with CAMEL has been added to Section CAMEL short message service . . Parameter CAMEL_ACTIVE has been added to Section Parameters needed for CAMEL SM . . Changes made between issues 50 and 45 Changes due to feature MT-SM for CAMEL Phase 4 : . . Information related to this feature has been added to parameter CAMEL_SUPPORTED_PHASE in Section Parameters needed for CAMEL SM . Therefore. NVLAI parameter has been added to Subsection Real Time triggering . Information on activating Common MSISDN Sending has been added to Subsection Activating Real Time Triggering . Changes due to feature SMS Routing Based on Subscriber Type : . Subsection Activating MT-SM for Camel Phase 4 has been added to Section Activating Nokia-specific SMS features . Changes made between issues 45 and 44 Changes due to feature Terminal Management Support : . Information on the additional functionality of Terminal Management Support has been added to Subsection Real Time triggering . Information on IN MT functionality has been added to Subsection Interworking between CAMEL SM and IN SM . Changes due to feature Supplementary Services Phase 2 Extensions : dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 11 (267) . Subsection Short message routing based on subscriber type has been added to Section Short Message Routing . . the latest document issue contains all changes made to previous issues. . . Information on the activation and deactivation of the feature has been added to Subsection Real Time triggering .Summary of changes Summary of changes Summary of changes Changes between document issues are cumulative. Parameter B_IMSI_FOR_MO_SM has been added to Subsection SMSrelated general parameter file (PRFILE/FIFILE) parameters . . Information on new SMS CFU counters has been added to Subsection SMS-related statistics . . Section SMS Forwarding has been added to Chapter Short Message Services . Section Incoming Call Treatement has been added to Chapter Short Message Services . Changes due to feature Same CLI for Multiple Subscribers : . Section Sending SMS without SMSC has been added to Chapter Short Message Services . Subsection Activating B-IMSI retrieval in MO-side for MNP has been added to Section Activating Nokia-specific SMS features . Changes due to feature Sequential and Parallel Alerting for MultiSIM Service : . 12 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Subsection Mobile number portability solutions for MO-SM charging has been added to Section Short Message Charging . Changes due to feature Missed Calls Log Service : . . . Changes due to feature Direct SM Delivery : . Section Sequential and Parallel Alerting has been added to Chapter Short Message Services . Changes due to feature B-IMSI Retrieval in MO side for MNP : . Section Same CLI for Multiple Subscribers has been added to Chapter Short Message Services .SMS Guide . Section Missed Calls Log Service has been added to Chapter Short Message Services . Subsection Activating Direct SM delivery has been added to Section Activating Nokia-specific SMS features . Changes due to feature Incoming Call Treatment : . Parameter SMS_FORW_IN_HLR has been added to Subsection SMSrelated general parameter file (PRFILE/FIFILE) parameters . . Changes made between issues 43 and 41 No content changes. . The title VMSC and VLR in SMS has been changed to VMSC and VLR in Chapter Short Message Services . Changes made between issues 44 and 43 No content changes. Other changes . The title HLR in SMS has been changed to HLR in Chapter Short Message Services . Information on SMS measurement related to SMs sent without the SMSC has been added to Section SMS-related statistics . The title Traffica in SMS has been changed to Traffica in Chapter Short Message Services . . Subsection Parameters needed for Sending SMS without SMSC has been added to Section Additional information on SMS . .Summary of changes . dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 13 (267) . SMS Guide 14 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . A short message is a freely phrased text message with the maximum length of 140 octets. for example. Basic Short Message Service procedure There are two different and independent point-to-point services depending on the direction of the SM transfer: . but if some other coding method is used. Mobile-terminating Short Message (MT-SM) transported from an SMSC to an MS and received by subscriber B. or facsimile.Short Message Services 1 Short Message Services The Point-to-Point Short Message Service (SMS-PP) is a basic teleservice used for transferring Short Messages (SMs) between a Short Message Entity (SME ) and a GSM Mobile Station (MS ). This message can be input to the SMSC by other mobile users (through an MOSM) or by a variety of other sources. This means 160 characters if a seven-bit coding method is used. telex. speech. SMS is very popular since a message can be sent to other subscribers at any time. SME application GSM/PLMN network SMSC MO-SM MT-SM Figure 1. e-mail. even when the MS is not reachable. For more information. Mobile-originating Short Message (MO-SM) sent by subscriber A and transported from an MS to an SMSC . see 3GPP TS 23. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 15 (267) .038. the number of characters is less. . 16 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . The figure below describes the key characteristics of SMS. The SM delivery to the SMSC is always acknowledged to the sender. the network initiates the Alert SC procedure to inform the SMSC that the subscriber is available again. though it takes more time. . There are special sources of SMs: . Short messaging is independent of the voice services: SMs can be sent and received also during voice calls. SMSC Store and forward point Address + message Interface to other systems Platform for applications Mobile-terminating: SMSC to mobile Mobile-originating: from MS to SMSC (or to another MS) SMS-Alert: relay when reachable Max. The MS is able to receive one MT-SM and send one MO-SM at a time.SMS Guide The SMSC is able to send only one MT-SM to a subscriber address (MSISDN ) at a time. the network stores an indication of absence. 160 characters/message Figure 2. IMSI detached). and when the MS is active again. If an MT-SM cannot be delivered to the MS because it is absent (for example. A subscriber can send an SM to subscriber B even when subscriber B's MS is switched off or not reachable. Key characteristics of Short Message Service Main characteristics of SM delivery The main characteristics of SM delivery are the following: . 1 Short Message Services Overview The following topics are covered under Short Message Services: Table 1. 327: Short Message Services 412: SMS-SMSC Interface. thus the VMS can make a delivery call to the subscriber. various kinds of terminals connected to the SMSC Note The topics included in the following sections cover all SMS matters and contain the following features. 1. In some cases the SMSC can also tell the VMS that the subscriber's MS has become reachable in the GSM network. which can send voice mail alerts to a subscriber to indicate that voice messages were left in the voice mailbox. . Short Message Services overview Short Message Services Instructions Short Message Services descriptions and referential material Short Message Services Additional information on SMS Configuring network elements for SMS Managing SMS subscriber-specific data Managing SMS network element-specific data Activating Nokia-specific SMS features Working examples for SMS management Short Message Service troubleshooting dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 17 (267) .Short Message Services - - Voice Mail System (VMS ). . . There are no separate feature activation instructions available for the following features in the current release: . GSM Phase 2 Enhancements 714: Short Message Service Enhancements . GMSC/IWMSC 476: PNP Numbering for SMS (MO) 619: Short Message Service Enhancements 620: Short Message Services. . Protocol-Identifier (PID) The Short Message Transfer Layer (SM-TL) uses it either to refer to a higher layer protocol. queueing.SMS Guide 1. if the SM cannot be delivered to subscriber B immediately. Delivery attempts are made until the delivery succeeds. The main parameters are explained in the following. The time value is included in every SMS-DELIVER message (TPService-Centre-Time-Stamp field) delivered to the MS.2 SMS information elements SMS-related information elements. There is also a maximum validity period system parameter to inhibit the use of excessive validity period values. For details regarding each type of mobile phone. The subscriber chooses the method of sending the SM. PID. The method of giving the validity period depends on the capabilities of the mobile phone used. MoreMessagesToSend. Each SM has a validity period. X. in the latter case. after which SMs that have not been delivered are deleted. refer to their respective instructions and user guides. The contents and the transfer mechanisms have been specified in 3GPP TS 23. that is. priority request. This control parameter is an internal SMS functionality. the SMSC inserts a default validity period. If no validity period is given by the originator. are used for sending and receiving SMs.400 mail transfer protocols. The SM can be converted. or on the application that sends the message. they decide for how long the delivery attempts should be made if the SM cannot be delivered immediately. into SMTP . Service-Centre-Time-Stamp The SMSC uses it to inform the MS about the time when the SM arrived in the SMSC. service centre time stamp. or until the validity period expires. This control parameter is an internal MT-SMS functionality. 18 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . such as validity period. and normally it is a regular mobile-to-mobile message. and MessagesWaiting. the length of time the SMSC stores the SM before discarding it if all delivery attempts fail. the SM is deleted. This control parameter is an internal MOSM functionality. These parameters give information about the Short Message (SM). Validity-Period It indicates how long the SM is valid. or to indicate interworking with a certain type of device. for example.040. or fax. As the originator of an SM submits the SM for delivery. the system does not try to deliver it. If the value is zero.Short Message Services More-Messages-to-Send (MMS) The SMSC uses this functionality to inform the network in a Mobile-terminating Short Message (MT-SM) that the SMSC has more messages to send to the same subscriber. also when it has been identified as having no free memory capacity. . The next short message is not sent until an acknowledgement for the previous one is received. then the receiving entity ignores the whole Information Element. Sequence number of the current short message : this value starts at 1 and increments by one for every SM sent within the concatenated short message. Priority Request This parameter tells the PLMN whether an SM is a priority message or not. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 19 (267) . . The system tries to deliver a priority SM even if the MS has been identified as temporarily absent or having no free memory capacity. However. Concatenated short message reference number : this reference number remains constant for every SM which makes up a particular concatenated short message. The field includes the following elements: . The connection path between the SMSC and the MS is not closed until all SMs have been delivered to the MS. Information-Element This field contains information set by the application in the SMS-SUBMIT/ DELIVERY. If the SM is not a priority message. with which the receiving entity is able to re-assemble the concatenated short messages in the correct order. Maximum number of short messages in the concatenated short message : it indicates the total number of SMs within the concatenated short message. and the MS has been identified as temporarily absent. The value remains constant for every SM which makes up the concatenated short message. the system tries to deliver the non-priority SM if the MS has not been identified as temporarily absent. SMS queuing Queueing takes place when more SMSCs are sending short messages to the same subscriber at the same time. In this case all incoming SMs are placed in a queue in the VMSC and they are served according to the First-In-First-Out (FIFO) principle. Main parameters on the Short Message Relay Protocol (SM-RP) layer The following parameters are visible on the Short Message Relay Protocol (SMRP) layer according to 3GPP TS 23. Messages Waiting Data (MWD ) including the address list of the SMSCs having messages waiting to be delivered to the MS Mobile Station Not Reachable Flag (MNRF) indicating if the address list of the MWD contains one or more entries as a result of an unsuccessful SM delivery attempt (stored in the VLR and HLR) Mobile Station Not Reachable Flag for GPRS (MNRG) indicating if the address list of the MWD contains one or more entries as a result of an unsuccessful SM delivery attempt (stored in the SGSN and HLR) Mobile Station Not Reachable Reason (MNRR ) for GSM and SGSN storing the reason why an MS is absent when an attempt to deliver a short message failed in the MSC Mobile Station Memory Capacity Exceeded Flag (MCEF) indicating that the mobile station memory capacity does not allow short message delivery (stored in the HLR). . The MWI contains the following elements: . . SMSC Address Destination Address (IMSI or MSISDN of subscriber B) User Data containing Short Message Transfer Layer Protocol Data Unit (SM-TL PDU ) Message Reference Priority Request More Messages To Send . . For more information on SMS elements. Mobile-originating short messages: 20 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .040. . . . .040.SMS Guide Messages Waiting (MW) This service element makes the PLMN store information (Messages Waiting Indication (MWI)) listing the SMSCs that have made unsuccessful short message delivery attempts to the MSs in the PLMN in question. Mobile-terminating short messages: . see 3GPP TS 23. . 3 Mobile-originating short message The Mobile-originating Short Message (MO-SM) procedure is used to forward an SM from a mobile subscriber to an SMSC . MO-SM successful case dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 21 (267) . 1. . Message Reference Originating Address (subscriber A) Destination Address (SMSC) User Data containing Short Message Transfer Layer Protocol Data Unit (SM-TL PDU) . The following figure shows the MO-SM successful case: VLR HLR 2 MO-ForwardSM 1 7 MSC 3 6 SMS-IWMSC 4 5 SMSC Figure 3. An active MS is able to send an SMSSUBMIT at any time. no matter if there is a speech or data call in progress or not.Short Message Services . . it either confirms that the SMSC has received the SMS-SUBMIT. A special OSI or TCP/IP application is used between SMS-IWMSC and SMSC. depending on whether the sending was successful or not. 7. The MS sends an SM to the VMSC through SDCCH (if the MS is idle) or SACCH (if the MS is busy) signalling channel on the radio interface. 2. The SMS-IWMSC sends a delivery report to the VMSC.1 MO-SM procedure MO-SM procedure when the SMSC is connected through the SMRSE interface 1. The report is a delivery or a failure report. 3.3.SMS Guide 1. In other words. The SMSC sends a delivery report to the SMS-IWMSC through the OSI or TCP/IP application. The SM includes the address of the SME where the SMSC eventually attempts to forward the SM. The SMS-IWMSC routes the SM to the SMSC. 5. and the SM can be sent through this application. 22 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . The VMSC sends a report to the MS of subscriber A through SDCCH or SACCH . including the reason why. 6. The VMSC routes the SM to the SMS-IWMSC . or informs the MS that it was impossible to deliver the SMS-SUBMIT to the SMSC. The VMSC checks the data of subscriber A from the VLR. 4. The result of the Global Title analysis should be the own signalling point code in the IWMSC . MO-Forward SMS procedure For more information. see MAP in SMS . see SMRSE in SMS .Short Message Services SC SMSIWMSC HLR MSC VLR Access request and possible authentication CP-DATA (RP-DATA) CP-ACK sendInfoForMO-SMS MS MOforwardSM Message transfer Delivery report Delivery report CP-DATA (RP-ACK) CP-ACK User Data relevant to Feature 1043 is sent in CP-DATA (RP-ACK). 2. For related information. MO-SM procedure when the SMSC is connected through the MAP interface The VMSC and SMSC are connected through Common Channel Signalling (CCS). dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 23 (267) . the VMSC can route the SM directly to the SMSC. the SMSC can send the delivery reports directly to the VMSC. If a CCS solution is used. If a CCS solution is used. 1. Figure 4. 24 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Subscriber A does not have the T22 (MO-SMS) subscription (TeleserviceNotProvisioned). 1. Operator-determined barring is activated by the network operator or barring supplementary service is activated by the subscriber. . . . The Short Message Service Centre is unknown (UnknownSc on the MAP interface). the SCP can bar the short message submission. A-number prevention is defined (UnknownSC on the MAP interface). The short message transfer is rejected because the SME address is invalid (InvalidSME-Addr on the MAP interface). . . and Network elements involved in SMS . Subscriber A is not the subscriber of the relevant SMSC (UnidentifiedSubscriber on the MSC-SMSC interface). In case of an Intelligent Network (IN ) subscriber. There is congestion in the SMSC (SC-Congestion on the MSC-SMSC interface). independently of whether or not there is a speech or data call in progress. . An active MS is able to receive an SMS-DELIVER at any time.4 Mobile-terminating short message The MT-SM procedure is used to transfer an SM sent from the SMSC to a mobile station. System failure (SystemFailure on the MAP interface and MSC-SMSC interface) 1.3. . . The MO-SM facility is not supported in the network (FacilityNotSupported on the MAP interface). . The error code depends on the SCP.2 Unsuccessful MO-SM delivery The sending of the MO-SM can fail in any of the below situations: . SMSC address prevention is defined (UnknownSc on the MAP interface). . The following figure shows the successful MT-SM case.SMS Guide You can also find related information in Welcome SM to the roamer . 1 MT-SMS procedure MT-SMS procedure when the SMSC is connected through SMRSE interface The following figure shows a normal case where the sending of MT-SM succeeds: Note that when the priority flag is set. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 25 (267) . MT-SM successful case 1.Short Message Services HLR VLR SendRoutingInfoForSM 2 7 4 MT-ForwardSM 1 8 SMSC SMS-GMSC 3 6 MSC 5 Figure 5. the delivery is attempted even when the MNRF flag is set.4. SMS Guide SC SMSGMSC HLR MSC VLR MS Message transfer SendRoutingInfo ForShortMsg MTforwardShortMessage SendInfoForMT-SM SendInfoForMT-SM (Ack/NAck) Provide Loaction Info Provide Loaction Info Ack/NAck Page Authent. 3. 4. Figure 6. The SMS-GMSC routes the SM to the VMSC/SGSN. CP-DATA (RP-DATA) Delivery report Delivery report User Data relevant to Feature 1043 is sent in CP-ACK. The VMSC asks the VLR for the status and location area of the MS of subscriber B . see Mobileterminating short message over GPRS . The SMS-GMSC requests the VMSC or SGSN address from the HLR. 2. MT-Forward-SMS procedure 1. 26 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . For information on the operations in the SGSN. The SMSC sends the SM to the SMS-GMSC by using the SMRSE protocol. Some related information can also be found in Welcome SM to the roamer and Network elements involved in SMS . If the MS is in idle mode. see MAP in SMS .Short Message Services 5. For related information. If the MS is in busy mode. 8. If a CCS solution is used. See also Handling of MNRR . the MNRR stores one of the below detailed reasons for the MS being absent. MT-SMS procedure when the SMSC is connected through the MAP interface The SMSC in the MT-SMS procedure has a MAP interface and has the SMSGMSC function. As a result. every MSC must have a GT analysis for routing the SMSCISDN address to the SMSC. the VMSC sends the SM through the SACCH . 7. In the case of CCS solution. or informing the SMSC that it was impossible to deliver the SM to the MS. For more information. 2. and the SMSC must have the GT analysis for receiving that message. 1. see SMRSE in SMS . Note that these reason codes are not available through X. MWD (including the SMSC address) and the MNRF flag are set in the HLR. Subscriber B is absent (AbsentSubscriber on the MAP interface). If a CCS solution is used. The VMSC sends the delivery report to the SMS-GMSC. Furthermore. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 27 (267) . the VMSC starts paging and delivers the SM to it through the SDCCH of the BTS where the MS is located. 6. The SMS-GMSC sends the delivery report to the SMSC either confirming that the MS has received the SM.25. 1.4. The MS sends a delivery report to the VMSC after receiving the SM. The SMS-GMSC sends the delivery report to the HLR if needed. the VMSC can send the delivery reports directly to the SMSC.2 Unsuccessful MT-SM delivery The delivery of the MT-SM can fail if any of the following conditions are applicable: . including the reason why. the SMSC can request the VLR address from the HLR and route the SM directly to the VMSC. . Reason code MNRR reason codes Network element setting the reason code VLR VLR HLR HLR SGSN HLR SMS-GMSC SMS-GMSC SGSN No paging response through the MSC IMSI detached Roaming restriction MS purged for non-GPRS No paging response through the SGSN MS purged for GPRS Unidentified subscriber through the MSC * Unidentified subscriber through the SGSN * GPRS detached * Note that the VMSC or SGSN sends the Unidentified Subscriber error code to the SMS-GMSC and the SMSGMSC maps it to Absent Subscriber error code.SMS Guide Table 2. and the MNRR is sent to the HLR. . . This way the useless load of the network can be avoided. An SMSC is trying to send an SM to the subscriber while another SMSC is already sending him SMs (the paging request is rejected due to BusySubscriber on the MAP interface). As a result. If both Feature 714: Short Message Services Enhancements and Feature 1043: Short Message Services GSM Phase 2+ are active. 28 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . For detailed information see Short Message Service on GPRS . feature 1043 overrides feature 714. the MWI is not set. If the global title analysis fails in the SMS-GMSC towards the HLR. This error code is a permanent error code. the SMSC receives the Unknown_Subscriber error code from the SMSGMSC. . and consequently the SMSC ceases to retry the sending of the SM. The subscriber is unknown in the VLR (UnidentifiedSubscriber on the MSC-SMSC interface). The subscriber is unknown in the HLR (UnknownSubscriber on the MSCSMSC interface). (including the SMSC address) the MNRF flag is set in the HLR. In this case. . The service centre address is set in the subscriber's message waiting data (MWD) list. SMSC address is barred for the visitor subscribers (FacilityNotSupported on the MAP interface). The corresponding error code is transferred on the MSC-SMSC interface. A positive response is received for paging. . and it is transferred on the MAP interface. If no MT-SM delivery is possible through the MSC. but the priority flag is not set. so the MNRF is not checked until a call or a periodic location update is made. SMSC address is barred for home subscribers (IllegalSubscribers on the MAP interface). dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 29 (267) . The error code depends on the SCP. System failure occurs (SystemFailure on the MAP interface). . an MNRF is set in the VLR. . which results in the MSC/VLR not forwarding the SM to Subscriber B. but the memory capacity of the MS is exceeded (the MCEF flag was not set in the HLR). When the MS goes back to coverage area. and the Memory Capacity Exceeded informing procedure starts (MemoryCapacityExceeded on the MAP interface). This situation causes delay in the SM delivery. the VLR does not recognise any change. MWD (including the SMSC address) and the MCEF flag are set in the HLR. the SCP can respond with a ReleaseCall message. This error code is not used for any other MT-SM procedure. If subscribers are temporarily out of coverage.Short Message Services . so the SMSC can handle it as a temporary error situation and polls the subscriber periodically because only the MWF is set in the VLR. The SMSGMSC maps this 'System failure' to temporary 'Invalid SME address' error code towards the SMSC. . In case of an Intelligent Network (IN ) subscriber. the SGSN route can also be tried. As a result. Note that the solution works only with Nokia SMS-GMSC and VMSC. Information is found in the HLR that incoming call barring applies to subscriber B (CallBarred on the MSC-SMSC interface). and a short message is sent to them. . Special conditions . As a Nokia proprietary solution. MNRF flag is set in the HLR. . instead of 'Absent Subscriber' a 'System failure' error code is sent to the SMS-GMSC from the VMSC. or not.SMS Guide . These commands appear as ordinary SMs to the network. If the SM was delivered. 1. MO-SM with Status Report request When subscribers send mobile-originating SMs. can cancel an SM that has not yet been delivered to subscriber B. It is possible if the Status Report Request field is set in the mobile-originating SM by the sender. for example. see MMS-related parameters in SMSrelated general parameter file (PRFILE/FIFILE) parameters . 1. This message type is extracted from the SM for charging and statistical purposes. Subscriber A. but the SM data contains a field indicating the message type. you are able to apply different charging for MO-SMs in which Status Report is requested. or cannot be delivered at all. The SMS application reads the MMSWaitTimer from the PRFILE. or can request a status report about whether the SM was delivered to the subscriber or not. and in this case the SMMO CDR can be generated with the 'Mobile originated short message status report requested' SMS type value.4.4. The network indicates the result of the command to the subscriber by Status Report. It means that if the optional PRFILE parameter MO_SM_STATUS_REP_REQ is turned on.3 More-messages-to-send More-messages-to-send (MMS) is an information element offering an MS (receiving a short message from an SMSC) the data whether there are still more messages waiting to be sent from that SMSC to the MS. If a mobile station cannot receive short messages because of memory shortage. the MS is able to command the SMSC . The information about whether the Status Report request is set in the MO-SM is carried from the SMS application to the charging application. a special error code 'memory capacity exceeded' is returned and carried to the SMS-GMSC through the MAP protocol. Status Report is sent to the originator of the SM indicating the result of the delivery. they can request information on whether the SM was delivered to the destination MS. In MMS case the second route is never tried in the SMS-GMSC.4 Command SM and MO-SM with Status Report request In GSM phase 2. For more information on the PRFILE. 30 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . This message type is extracted from the SM for charging and statistical purposes. see SMS status report . If an SMSC number modification happens in the MSC due to different SMS applications (such as bank information). you do not need to use predefined SMSC addresses because the StatusReport is appropriate even if you have several SMSC addresses. SMS-Command 2 3 SMS-StatusReport MSC SMSC Figure 7.Short Message Services SMS-Command: What happened to the SM I sent to my friend? 1 4 SMS-StatusReport: Your SMS was delivered at 16:51 pm. Note dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 31 (267) . the old SMSC address is also needed in the StatusReport case. SMSC address on the MSC-SMSC interface The SMSC address used by the MS can be sent to the SMSC on the TCP/IP interface. The MSC sends the SMSC address given by the subscriber to the SMSC on the TCP/IP interface. that is. the new SMSC address is used for routing purposes. SMS command and status report For related information. With the help of this functionality you can also use the networked SMSC solution: several SMSCs can be connected to the network with a single SMSC number. because the mobiles can only understand the SMSC addresses stored in them. It does not affect the MSC-SMSC interface because this parameter was implemented on the interface already for future use. the ones that were used in SM sending. The relevant parameter can be found among SMS-related general parameter file (PRFILE/FIFILE) parameters . With SMSC address sent to the SMSC. resulting in messages being routed according to destination number to the nearest SMSC. However. SMS Guide You can use this feature if you have the SMSC connected through MAP (in the VMSC function). and the SMSC-GT-2 represents the SMSC address given by the VMSC. In this case the number given by the subscriber is sent to the SMSC (SMSC-GT-1). then the new SMSC address (SMSC-GT-2) is used on the SCCP level for routing purposes. and the new address (SMSC-GT-2) is used only for routing purposes. MAP version 3 is needed for this functionality. and also if you have the SMSC connected through SMRSE with TCP/IP. If the SMSC address is changed in the VMSC. For details refer to the feature activation instructions of Feature 1165: Short Message Services. but the MS-defined address is sent in the MO_FORWARD_SM MAP operation. In MO-SMS the SMSC-GT-1 represents the SMSC address given by the subscriber. GSM Phase 2+ Enhancements . 32 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Number modification can also take place in the SMS-IWMSC. SMS-IWMSC. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 33 (267) . The transfer of the SMSC address given by the subscriber to the SMSC causes changes in the VMSC. Successful MO-SM transfer with SMSC-GT-1 parameter In MT-SMS the SMSC-GT-1 represents the SMSC address given by the MS. and SMS-GMSC .Short Message Services MS CP_DATA CP_ACK VMSC SMS IWMSC SMSC number modification MAP_MO_FORWARD_SM (SMSC-GT-1) SMSC-GT-2 on SCCP level for routing SC_RP_MO_DATA (SMSC-GT-1) SC_RP_MO_DATA_ACK MAP_MO_FORWARD _SM_ACK CP_DATA CP_ACK Figure 8. and the SMSC-GT-2 represents the physical SMSC address that is used by the subscriber. SMS Guide SMSC SMSGMSC MAP_SEND_ ROUTING_INFO_ FOR_SM (SMSCGT-2 HLR VMSC MS SC_RP_MT_DATA (SMSC-GT-1. Successful MT-SM transfer with the SMSC-GT-1 parameter 1. There are two cases in which the system knows when to send the Alert-SC: 34 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . that a subscriber has become available again and can now receive new messages.5 SMSC Alert The GSM system uses Alert-SC to inform the SMSC (which acts as a store and forward centre for SMs). SMSCGT-2) MAP_SEND_ ROUTING_INFO_FOR_ SM_ACK MAP_MT_FORWARD_ SHORT_MESSAGE (SMSC-GT-1) Page Positive page response CP_DATA CP_ACK CP_DATA MAP_MT_FORWARD_ SHORT_MESSAGE _ACK SC_RP_ACK CP_ACK Figure 9. After the HLR has been informed about the available memory. Finally. the VLR sends the ReadyForSM operation to the HLR. SMSC alerting The steps are the following: dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 35 (267) . the mobile was turned off). The memory capacity was exceeded (either the mobile station or the SIM card memory was full). the MCEF is cleared. the Message-Waiting-Data of that subscriber is read and an alert is sent to every SMSC address found on the MWD list. 2. See MAP in SMS for a more detailed description of ReadyForSM operation. Finally. After the HLR has been informed about the available subscriber. the MNRF is cleared. and the Mobile-Not-Reachable-Flag (MNRF ) has been set in the VLR and HLR. turns his or her mobile on).Short Message Services 1. the VLR sees from the MNRF that there are messages waiting for the subscriber. and informs the HLR with ReadyForSM operation. and the Memory-Capacity-Exceeded-Flag was set in the HLR. See the figure below: ReadyForSM 2 HLR 3 AlertServiceCentre 1 Alert 4 MSC/VLR SMS-IWMSC SMSC Figure 10. Finally. When the MS informs the VLR that it has free memory again. When the subscriber becomes available (for example. the MNRF is cleared. The subscriber has been absent (for example. the Message-Waiting-Data of that subscriber is read and an alert is sent to every SMSC address found on the MWD list. OSI management automatically switches the traffic onto a functional connection.6. Connection parameters are handled in OSI management by defining parameter sets and linking them to an Application Entity Name (AEN). 4. An automatic repeated delivery attempt performed by the SMSC. 2.SMS Guide 1.6 1. 2. The VLR informs the HLR with ReadyForSM that the subscriber is available or that there is free memory. In the MSC/VLR. several connections can be used for load sharing.1 SMS load sharing SMRSE over X. 36 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . The HLR searches all SMSC addresses listed in MWD from the subscriber data and sends an Alert-SC to each of them. In case of a malfunction. If two or more links exist to an SMSC and the connections are open. A repeated delivery attempt because the SMSC has been informed that the MS is active and available for receiving SMs. The maximum amount of AEN connections is 5. The SMS-IWMSC forwards the Alert-SC to the SMSC through OSI or TCP/IP application. You can also find a list of SMS information elements . OSI management cannot know how much traffic is going within various connections and suggests the first one to be used so long as it is functional. they use the ISDN number to select an SMSC. For further details. You can also find a list of SMS information elements . 3. 1. see SMS load sharing . There are two types of repeated delivery attempts from the SMSC (the providers of the SMSC and the network define their application): 1. When subscribers send SMs. see SMS load sharing . the ISDN address is tied to an AEN. During the Alert-SC procedure there is no load sharing. For further details. By defining several AENs to an ISDN address. The MS informs the VLR that it has free memory or has become reachable again . It provides load sharing only when opening a connection.25 OSI management does not fully support load sharing. 2. if there are three or five SMSCs (1. number to be used 1 2 3 4 5 1 2 dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 37 (267) . SMSC01 SMS-IWMSC SMSC02 SMSC-1 SMSC03 SMS-IWMSC has three (3) Application Entities in SMSC address analysis SMSC-2 Figure 11. SMS load sharing The algorithm uses a modulus from the last three digits so that the number range is distributed evenly to all available SMSCs within load sharing. 3.Short Message Services Load sharing. because command messages must be routed to the same SMSC where the original message was sent while concatenated messages must be routed to the same SMSC where the previous messages were sent. thus. uses a modified algorithm where the AENs used are determined from the last three digits of the sending subscriber's number. This must be used instead of random selection. 4 and 5) to be shared. Subscriber number's last three digits 160 161 162 163 164 165 166 Distribution of number range in available SMSCs 3 SMSCs. number to be used 1 2 3 1 2 3 1 5 SMSCs. For example. the following table applies: Table 3. thus. This must be used instead of random selection. For details. because command messages must be routed to the same SMSC where the original message was sent while concatenated messages must be routed to the same SMSC where the previous messages were sent. For more information. More details can be found in Short message routing . but logically they all mean one SMSC address which then routes the SM further. see the feature description of Feature 619: Short Message Services Enhancements. 38 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . number to be used 2 3 1 5 SMSCs.2 SMRSE over TCP/IP Load sharing without MO SMS limiter The maximum amount of SMSC's TCP/IP connections in one MO-SMS load sharing group is increased from 5 to 32. number to be used 3 4 5 A consequence of load sharing is that when the SMSCs send MT-SMs. Subscriber number's last three digits 167 168 169 Distribution of number range in available SMSCs (cont.SMS Guide Table 3. Note Note that during the Alert-SC procedure there is no load sharing. uses a modified algorithm where the IP address used is determined from the last three digits of the sending subscriber's number.) 3 SMSCs.6. see SMSC Alert . For the illustration of SMS load sharing. 1. Load sharing. they all use individual SMSC addresses. see Figure SMS load sharing . You can also find related information in SMRSE in SMS . 2. 3. For more information. The MO-SMS limiter is sent by the SMSC to the MSC during the connection establishment between the MSC and the SMSC. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 39 (267) . proportionally equal load can be achieved in all SMSCs if you have Feature 1165: Short Message Services GSM Phase 2+ Enhancements in use in your network. see the feature descriptions of Feature 931: Short Message Service Transfer over TCP/IP and Feature 619: Short Message Services Enhancements . For example. It tells the MSC what the upper limit for MO-SMs is per second per TCP/IP link. If there are SMSCs with different capacity in the network. More details can be found in Short message routing . see Table Distribution of number range in available SMSCs A consequence of load sharing is that when the SMSCs send MT-SMs. Note For using this functionality you must have the SMSC connected through SMRSE with TCP/IP. You can also find related information in SMRSE in SMS . if there are three or five SMSCs (1. they all use individual SMSC addresses. There is an MO-SMS limiter for each SMSC link. 4 and 5) to be shared. The possible value of this parameter ranges from 0 to 10000 MO-SM/sec. Load sharing with MO-SMS limiter Improved load sharing based on the SMSC link capacity value is possible with MO-SMS limiter. that is. the proportionally equal load sharing in the MSC requires the capacity information from the SMSC. The MSC then controls the number of MO-SMs sent to the SMSC (on one TCP/ IP link) per second on the basis of the value of the MO-SMS limiter. but logically they all mean one SMSC address which then routes the SM further. Weighted distribution can be achieved among SMSCs with different capacity.Short Message Services The algorithm uses a modulus from the last three digits so that the number range is distributed evenly to all available SMSCs within load sharing. TCP/IP protocol also helps in SMRSE capacity problems. There is no change on the MSC-SMSC interface.SMS Guide Note. The MSC makes the weighted equal distribution among the links involved in the load sharing based on this value. An exception to this is when the error indication is coming from a link because of overload situation. that the AlertSC messages are not counted here. 40 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . The following figure illustrates how the limiter is used in load sharing: MO-SMS Limiter:10 SMSC-1 MSC MO-SMS Limiter:20 SMSC-2 MO-SMS Limiter:30 SMSC-3 MO-SMS Limiter:40 SMSC-4 MO-SMS Limiter:50 SMSC-5 Figure 12. The value of the MO-SMS limiter for a specific SMSC link is stored in the connection table of the MSC. If a link goes down. In this case the link stays in the load sharing group. the load sharing is executed among the rest of the SMSC links. The use of MO-SMS Limiter in load sharing This functionality causes changes in the SMS-IWMSC. because the MO-SMS limiter parameter is already supported. For details. GSM Phase 2+ Enhancements in use but there is no MO Limiter value given for the TCP/IP link. When a home subscriber is in the home PLMN. Further information can also be found in TCP/IP connection .7 Barring SMS in the MSC Barring of MO-SMS You can configure certain SMSC and A-subscriber addresses into the VMSC or SMS-IWMSC corresponding to where the MO-SM is not allowed to be sent and from whom it is not allowed to be originated. the A-subscriber barring is not relevant since the removal of the teleservice code from the HLR has the same effect. . respectively. but only if you have Feature 1043: Short Message Services GSM Phase 2+ in your network. When a foreign subscriber is in the home PLMN. See also Alarms and their meaning in Short Message Service . visitor subscribers or for all subscribers. the usage of a foreign SMSC can be barred. both the A-subscriber number and the usage of the own SMSC can be barred. The MAP interface uses the UnknownSC error code in A-subscriber or SMSC barring. When a home subscriber is in the home PLMN. refer to the feature descriptions and feature activation instructions of Feature 1165: Short Message Services. which results in the UnassignedNumber error code sent from the VMSC to the MS. Missing Mo limiter for SMSC link is issued. With the help of this feature you can separately define whether the SMSC is barred for home subscribers. The following barring cases can be considered in the VMSC: . and Alarm 1224. a new SMSC address analysis (MO-DENY analysis based on SMSC address) is needed to decide whether the use of the SMSC is denied or not. In this case load sharing works in the previously described equal distribution method. . If you want to use this functionality.Short Message Services Error situation is raised if you have Feature 1165: Short Message Services. the A-subscriber MSISDN analysis is also added to the feature. 1. In addition. GSM Phase 2+ Enhancement s. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 41 (267) . Without feature 1043 you can only configure MO-deny for all subscribers. If you want to use A-number prevention in the home country. to prevent SMs sent by the subscribers of another operator and there is MNP in the network. case 1 42 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Similarly. For example. MO-SMS barring configured to the VMSC. if you want to bar SMs sent by the subscribers of a foreign operator from a foreign country. they will not be able to send short messages. The following figures illustrate possible examples for the use of this functionality: home PLMN GSM network home subscribers foreign PLMN SMSC operator does not allow SMs to be sent to a foreign SMSC Figure 13. and if subscribers from another operator becomes your subscribers keeping their old MSISDN number for which the barring exists. you can also bar those sent by the subscribers of another operator in the same foreign country.SMS Guide Special conditions When the network has Mobile Number Portability (MNP). if you set A-number prevention when there is MNP in the network. you have to be careful when setting A-number prevention to subscribers. it can happen that your own subscribers will also be barred as a result of their using the MNP functionality. Short Message Services home PLMN GSM network foreign subscribers SMSC operator does not allow SMs to be sent to his own SMSC or to be originated from a foreign subscriber Figure 14. When a foreign subscriber is in the foreign PLMN. The following figures illustrate possible examples for the use of this functionality: foreign PLMN GSM network foreign subscribers home PLMN SMSC operator does not allow SMs to be sent to his own SMSC or to be originated from a foreign subscriber Figure 15. This barring case can only be configured to the IWMSC. the barring SMSC address is not relevant in this case. . In addition. When a home subscriber is in the home PLMN the A-subscriber barring is not relevant since the removal of the teleservice code from the HLR has the same effect (similarly to the VMSC). case 2 The following barring cases can be considered in the SMS-IWMSC: . MO-SMS barring configured to the VMSC. MO-SMS barring configured to the IWMSC. case 1 dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 43 (267) . you can bar both the Asubscriber number and the usage of the own SMSC. you can bar both the Asubscriber number and the usage of the own SMSC. When a foreign subscriber is in the home PLMN. . The following error codes can be sent according to the groups of subscribers concerned: Table 4.SMS Guide home PLMN GSM network foreign subscribers SMSC operator does not allow SMs to be sent to his own SMSC or to be originated from a foreign subscriber Figure 16. Group of subscribers affected Home Error codes in MT-SMS barring Type of failure Re-delivery according to the SMSC No Error code IllegalSubscriber Permanent 44 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . This means that no MT-SM is allowed to be originated from that SMSC address. one located in a foreign country) into the VMSC if you have Feature 1043: Short Message Services GSM Phase 2+ in your network. it sends an error code to the SMSC. It is also possible for you to separately define whether a certain SMSC is barred . for home subscribers for visitor subscribers or . for all subscribers When there is barring in the VMSC. case 2 Barring of MT-SMS You can configure certain SMSC addresses (for example. MO-SMS barring configured to the IWMSC. . Group of subscribers affected Visitor All Error codes in MT-SMS barring (cont. Case 1 dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 45 (267) .Short Message Services Table 4. for example. you need to set the FacilityNotSupported error code in the SMSC in such a way that the interval between two resendings is as big as possible. while for visitor subscribers you set the barring as temporary if you want to enable the subscribers to receive the short messages after returning to their home network. For home subscribers the barring is set as permanent. The following figures illustrate possible examples for the use of this functionality: foreign PLMN SMSC home PLMN GSM network foreign subscriber no roaming contract due to charging problems Figure 17.) Type of failure Re-delivery according to the SMSC Yes Yes Error code FacilityNotSupported FacilityNotSupported Temporary Temporary Due to the possibility of SMSC barring in MT-SMS case. barring for home subscribers or nothing (meaning there is no restriction in the VMSC). barring for visitor subscribers. MT-SMS barring. This functionality can be useful. This results in a decreased load in the network. To avoid the frequent resending of short messages. The result of the analysis can be barring for all subscribers. if you want to bar the delivery of short messages coming from a special SMSC used by an internet service. the filtering needs an SMSC address analysis (MT-DENYanalysis based on the SMSC address) for barring purpose in the VMSC. the VMSC checks whether it has just arrived from another PLMN (even if it is in the same country). In this special MO-SM. 1. The TP-User-Data field contains the roaming subscribers MSISDN number.8 Welcome SM to the roamer With this function. MT-SMS barring. the SMSC can have the possibility to send a welcome note with predefined text to the roaming subscriber. The SMSC has to identify the received welcome MO-SM based on the sender virtual subscriber s address and it sends a welcome MT-SM as a welcome note to the roaming subscriber.SMS Guide foreign PLMN home PLMN GSM network SMSC operator does not allow SMs to be originated from an Internet service all subscribers Internet service application Figure 18. Managing SMS network element-specific data and Preventing SMS . If it has. Case 2 For information on how to configure MT-SMS barring. 46 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . the VMSC generates a special MO-SM and sends it through the SMS-IWMSC towards a specific SMSC. LAC and Cell ID in this sequence. When a roaming subscriber makes a location update in the operator's own PLMN. IMSI. see Configuring network elements for SMS . in the SMS TP-header the TP-Destination-Address is a national address for the SMSC application which is configured also in the VMSC. 9 Real Time triggering With Real Time triggering.25 towards the SMSC. see the following figure: dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 47 (267) . For further details see the feature description of Feature 1043: Short Message Services. which works with an SMSC which supports SM routing towards the application. As soon as the VLR detects an event. You also have to define a virtual MSISDN number (C-MSISDN) as the originator of the created MO-SM in the VMSC. the MSC/VLR can provide data to the Nokia Terminal Management Server. and these triggers are sent by Short Message. It is not necessary in case of MAP version 3.Short Message Services You have to configure the SMSC address and the SMSC application address in the VMSC for the welcome SM. You can also find related information in Mobile-terminating short message . It can be SS7. it sends the trigger to NTMS. For an overview of the operation of the Real Time triggering. and in this way NTMS can configure the mobile phone without the manual typing of end user or operator. TCP/IP or X. GSM Phase 2+ . For activation instructions see Handling the Welcome SM related parameters . since NTMS has direct connection to the SMSC. The welcome SM functionality is based on a Nokia proprietary solution. Note In MAP version 2 the virtual subscriber also has to be created in the HLR. 1. The interface type does not affect the Welcome SM operation. New visitor with special previous LAC Statistic report: trigger SM Trigger SM (MSISDN.SMS Guide Detected Event . Table 5. you can control which event has to be detected.Inter-PLMN location update . After the successful location update VLR or IMEI changes in the database (IMEI1 changes to IMEI2) the Real Time triggering functionality can start. Event detection Events. Detec.IMEI changes in the database . criteria and types of control Control of event detection Default activation status ON Filtering criteria IMEI changes in the VLR database HOME / VISITOR subscriber or MS-CLASSMARK Can be switched ON/OFF 48 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Operation of Real Time triggering When the VLR receives an access request from the subscriber and the IMEI checking is switched ON. IMEI.event. Since these trigger SMs result in additional load in the MSC-SMSC interface. the VLR gets the subscriber's IMEI number. Common MSISDN) NTMS CIMD IMEI checking Forward MO-SM VMSC MS Operator has to set IWMSC SMSC SMSC address SMSC application address Sender (A number) of the trigger SM IMEI checking Figure 19. IMSI. it can also mean an unsuccessful location update. Note If the special previous LAC is zero.Short Message Services Table 5. The New visitor with special previous LAC event can indicate a new subscription in the network. you can set three kinds of EVENT. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 49 (267) . Event detection Events. criteria and types of control (cont. or both. . . and two kinds of CRITERIA in the VLR parameter file.) Control of event detection Default activation status OFF Filtering criteria Inter-PLMN location update of new visitor HOME / VISITOR subscriber or MS-CLASSMARK Can be switched ON/OFF New visitor with special previous LAC HOME / VISITOR subscriber or MS-CLASSMARK Can be switched ON/OFF OFF Based on this table. . It is possible to differentiate between the types of mobile stations by using the MS_CLASSMARK parameter. With the configurable UTPFIL parameter. or the VISITOR subscriber is detected only. The Inter-PLMN location update event indicates a subscriber who has just arrived from a foreign country. . The HOME/VISITOR parameter makes it possible that either the HOME subscriber. The national roamers are not detected. it is possible to set a different kind of initial value for the event 'New visitor with special previous LAC value'. see the feature description of Feature 1433: Terminal Management Support . When the operator has two home networks. It also provides filtering to detect only those subscribers who belong to the appropriate HPLMN. you also have to define a virtual MSISDN number as the sender of the created MO-SM (A number) in the VMSC. For further details. The user can choose the termination mode from this menu before the rejection.SMS Guide Additional information on Real Time triggering If the detected event meets the filtering criteria.B subscriber number) in the VMSC. Moreover. IMEI. In addition to regular call answer and reject. As an additional functionality. For activation instructions. the subscriber can predefine rules for the possible terminations. and Common MSISDN in ASCII format. The called party has the following possibilities to handle the call: 50 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . The trigger SM functionality is based on a Nokia proprietary solution. which informs the NTMS that this is a multi SIM user. MSC_36209956524_490523102400750_21601585458_PLMN_36209956500 Flag+MSISDN + IMEI + IMSI + Detect. The numbers are separated with a space. the VMSC generates the Trigger SM. see Activating Real Time triggering . Terminal Management Support provides both common MSISDN and own MSISDN to the NTMS. The Trigger SM TP-User-Data field contains the subscriber MSISDN. which works with an SMSC which supports SM routing towards the application.event + Common MSISDN You have to configure the SMSC address and SMSC application address (Destination . the subscriber's data of the HPLMN1 can be sent only to the NTMS of the HPLMN1. 1. These rules are represented in a menu. IMSI number. Detected event. The VMSC sends both the common MSISDN and the own MSISDN to the NTMS.10 Incoming Call Treatment The Incoming Call Treatment service enables the subscriber to decide how the incoming calls should be terminated if they cannot accept the calls. The structure of the User Data can be found below. and there are different NTMSs for each network. and the reason why the call was unsuccessful. In these cases the network generates a special Short Message (SM). . dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 51 (267) .11 Missed Calls Log Service This feature provides indication about the missed calls to the served user. The called party can personalise the service by defining the forwarding numbers and the text in the short message. The ICT service plays an announcement to the called party until the network receives an answer on how the call should be treated. . . with or without Call Forwarding on Not Reachable (CFNRe ).Short Message Services . 1. . The phone is switched off (International Mobile Subscriber Identity (IMSI) detach. simply rejecting the call forwarding the call to a certain pre-defined number forwarding the call to voice mail rejecting the call with a pre-defined notification to be sent in SMS to the caller normal SM: it is stored immediately flash SM (class 0): it is received to the user's screen. The network is busy or there is a congestion. . Unconditional Call Forwarding (CFU ) The phone is out of radio coverage. For more information see the feature description and the feature activation manual of Feature 1607: Incoming Call Treatment . The following situations are recorded as missed calls: . The SM is sent to the MS when it is connected to the network again. With the Missed Calls Log (MCL) functionality the subscriber receives information about those calls which were unsuccessful before the alerting phase. The ICT service functions in case of home and outbound roaming. Network Determined User Busy (NDUB ) network failure before the alerting phase . which contains the caller's number. It is also possible for the user to define more alternatives for the diverted-to numbers and the texts to be sent. . . time of the missed call. 12 Short Message Service on GPRS General Packet Switched Services (GPRS) provides packet switched mode service to mobile stations and terminals. The following figure gives a general overview of the different network elements and interfaces involved. and separate SMS-GMSC and SMS-IWMSC exist. This way data can be sent and received by the MS at any time without prearranged network resource reservation or call setup.SMS Guide The log contains the following information: . 1. For more information see the feature description and the feature activation manual of Feature 1606: Missed Calls Log Service . Please note. one SM contains one log entry (one unsuccessful call attempt). You can. The mobile station receives the logs in short messages. Short messages can be efficiently delivered over the GPRS radio interface as data packets. . By default. 52 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .25 interface. caller's number (if available) time and date of the missed call reason why the call was unsuccessful . A GPRS service can be subscribed just like the GSM service. that this architecture is characteristic of those networks only in which TCP/IP or X. or subscribers having GPRS services only. There can be subscribers (IMSIs) having both circuit switched GSM services and GPRS services. as an option. choose to combine all log entries for one subscriber into as few SMs as possible. or circuit switched services only. It means that always that route is tried when delivering SMs. With the help of this parameter in MAP version 2. even if the subscriber is not reachable through that defined route. or through the SGSN. Gf) VMSC SGSN HLR BSS AUC EIR GPRS MS Figure 20. the MTSM through the SGSN is already available. 1.Short Message Services External data networks SMS-GMSC/SMS-IWMSC MAP (Gd) GGSN MAP (C) DX 200 HLR/AUC/EIR MAP (Gr. Overview of involved network elements For further details see the feature descriptions of Feature 857: Support of General Packet Radio Services (GPRS) .12.1 SMS over GPRS with MAP version 2 If MAP version 2 is supported in the MAP-C and MAP-Gd interfaces. This kind of environment does not require any special 'SMS over GPRS' support in the SMS-GMSC or the SMSIWMSC because as a subscription option you chose in the HLR whether the MTSM is always delivered through an MSC or through an SGSN. naturally. There is a subscriber-specific parameter which indicates whether the MT-SM should be sent through the MSC/VLR. Note that in this kind of implementation the MT-SM is never tried through the other route. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 53 (267) . The result is. negative acknowledgement to the SMS-GMSC. you can predefine the preferred route in the HLR. 54 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . In the HLR it is activated similarly to the MAP version 2 case. and the SMS-GMSC never knows whether the GSM or the GPRS channel is used to route the SM. only HLR support is needed. Comparative example of SMS over GPRS with MAP version 2 and MAP version 3. The delivery through CS network is successful. SMS over GPRS with MAP version 3 .2 SMS over GPRS with MAP version 3 If MAP version 3 is supported. 1. This is entirely dependent on the HLR parameter. The details of MT-SM-related HLR activation can be found in the feature activation instructions of Feature 857: Support of General Packet Radio Services (GPRS ). Then the SMS-GMSC tries to deliver the MT-SM through the CS network. Mobile-terminating short message service over GPRS The below example shows an MT-SM delivery where both GPRS and CS networks are used.12. You can also find related information in MAP in SMS . The subscriber has both SGSN and MSC addresses set in the HLR. For delivering SMs over GPRS. You can also find related information in Handling of SMSrelated MAP parameters .SMS Guide Note The Send-Routing-Info-for-SM response includes a single switch address. The SMS-GMSC first tries the delivery through the GPRS network but it fails because the subscriber is detached. because both routes can be tried if the subscriber has both circuit-switched and packet-switched connection. the MT-SM delivery can be more efficient. described in feature activation instructions of Feature 857: Support of General Packet Radio Services (GPRS) . short_message_delivery_request (primary route=SGSN) The SMSC requests MT SM delivery. Mobile-terminating short message delivery. MAP-Send-Routing-Info-for-SM-rsp (MSC address. 3. SGSN address) dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 55 (267) . 2. SGSN address) MAP-MT-forwardSM-req 3 4 MAP-MT-forwardSM-rsp (Absent: GPRS detached) MAP-MT-forwardSM-req 5 Succesful_ SM_delivery 6 MAP-MT-forwardSM-rsp MAP-Report-SMdelivery-Status-req (succesful via MSC.Short Message Services SMSC SMSGMSC HLR SGSN VMSC MS short_message_ MAP-Send-Routingdelivery_request Info-for-SM-req (primary route=SGSN) (SMS-GMSC 1 supports GPRS) 2 MAP-Send-RoutingInfo-for-SM-rsp (MSC address. absent via GPRS) MAP-Report-SMdelivery-Status-rsp 7 8 9 short_message_ delivery_rsp (succesful delivery) 10 11 Figure 21. MS detached for GPRS The procedure is the following: 1. MAP-Send-Routing-Info-for-SM-req (SMS-GMSC supports GPRS) The SMS-GMSC request the routing information for the MT-SM from the HLR indicating 'SMS-GMSC supports GPRS'. with primary route indicator=SGSN. 7. Successful_SM_delivery The MT-SM is successfully delivered through the VMSC to the subscriber. 10. 5. the VMSC. MAP-Report-SM-delivey-Status-req (successful through MSC. MAP-MT-forward-SM-req Since the route indicator received from SMSC tells that the GPRS network is the primary route.SMS Guide SMS-GMSC receives two addresses from HLR: the VMSC address and the SGSN address. The SMS-GMSC receives the reason for unsuccessful delivery. because the subscriber was absent. 9. MAP-MT-forward-SM-rsp (Absent: GPRS detached) MT-SM delivery was unsuccessful through GPRS network because the subscriber is detached. informing the HLR that the MTSM was successfully delivered through the VMSC and failed through the GPRS network. MAP-report-SM-delivery-Status-rsp HLR acknowledges the report. the SMS-GMSC first tries to deliver the MT-SM through GPRS network using the SGSN address received. MAP-MT-forward-SM-req SMS-GMSC tries to deliver the MT-SM through the secondary route. MAP-MT-forward-SM-rsp The VMSC informs the SMS-GMSC about the successful delivery of the MT-SM. short_message_delivery_rsp (successful delivery) SMS-GMSC informs the SMSC that the MT-SM delivery was successful. 11. 4. 6. that is. 8. 56 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . absent through GPRS) SMS-GMSC reports the delivery status. SGSN and MSC address handling in the HLR and SMS-GMSC If the subscriber has both SGSN and MSC addresses in the HLR. the HLR can return one or both of them in response to the MAP-Send-Routing-Info-for-SM. . or the SMS-GMSC indicates in the request that it supports the GPRS SM delivery and 'MT-SM through GPRS suppressed' is set OFF for subscriber in HLR and 'network access mode' is set to BOTH or GPRS. The HLR might return only the SGSN address in case that: the SMS-GMSC does not indicate the support of GPRS SM delivery and MT-SM through SGSN is set to SGSN and 'network access mode' is set to BOTH. respectively. - - If MNRG . 'SGSN area restricted'. and MT-SM through SGSN is set to MSC. If the MS is not reachable through the primary route (for example. . The HLR might return only the MSC address in case that: the SMS-GMSC does not indicate the support of GPRS SM delivery. or 'MT-SM through GPRS suppressed' is set ON for subscriber in the HLR. or 'network access mode' is set to GPRS for subscriber in HLR. or if the delivery was successful for a priority short message. the subscriber is detached or unidentified). MNRF . or 'network access mode' is set to MSC for the subscriber in the HLR. and 'MSC area restricted' flags in the subscriber data indicate that the subscriber is not reachable through either the SGSN and/or the MSC. Also the MNRR is set according to the absent subscriber diagnostic received from the SMS-GMSC. and network access mode is set to BOTH. on the basis of the indicator received from SMSC or if not available. on the basis of an operator-controlled parameter it determines whether the GPRS or CS network is the primary route to try the delivery. the secondary route is tried. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 57 (267) . The HLR is allowed to return both the MSC address and the SGSN address in case that: the SMS-GMSC indicates in the request that it supports the GPRS SM delivery and subscriber-specific HLR parameter 'network access mode' is set to BOTH and 'MT-SM through GPRS suppressed' is set OFF for that subscriber. If the delivery was unsuccessful through one or both the routes.Short Message Services . the delivery status is reported to the HLR. then the HLR does not return that address. and MNRF and MNRG flags are set accordingly. When the SMS-GMSC receives two addresses. SMS Guide If the MT-SM delivery was successful through either of the routes, SMSC is informed only of the successful delivery. If there is only one route available and the MT-SM delivery failed, the error situation is indicated also to the SMSC. If the delivery failed both through MSC and through SGSN, the error codes of both routes are indicated to the SMSC. You can select the primary route by defining the option in the SMS-GMSC (GPRS_SUPP_IN_SMSGMSC ). However, if the SMSC indicates the primary route to the SMS-GMSC, it overrides this option. Parameters needed for sending SM over GPRS Subscriber-specific parameters: network access mode: It is used to indicate if the subscriber has access to both the CS (MSC) and the GPRS (SGSN) networks, or only to one of them. MT-SM through GPRS suppressed: It is used to suppress the SGSN route for the subscriber. MT-SM through GPRS: It indicates if the MT-SM should be sent through the MSC or through the SGSN if the SMS-GMSC does not support GPRS SM delivery (that is, the GPRS_SUPP_IN_SMSGMSC is set to zero). The value of this parameter has an effect only when network access mode is 'access to both networks' and the 'MTSM through GPRS suppressed' parameter is OFF. Network-specific parameters: GPRS_SUPP_IN_SMSGMSC: It is used for the activation/deactivation of the service. It also states the primary route through which the mobile-terminating short message service (MT-SMS) is sent (MSC or SGSN), in case the Short Message Service Centre (SMSC) does not provide the primary route indicator. If its value is 0, it means that the SMS-GMSC can receive only one address in response to MAP-Send-Routing-Info-forSM. If its value is 1, the SMS-GMSC can receive both MSC and SGSN address in response to MAP-Send-Routing-Infofor-SM, the primary route is SGSN. If its value is 2, the SMSGMSC can receive both the MSC and the SGSN address in response to MAP-Send-Routing-Info-for-SM, the primary route is MSC. 58 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en Short Message Services GPRS_V2_IN_USE: It indicates the activation status of GPRS v2. For related information, see SMS-related general parameter file (PRFILE/ FIFILE) parameters . Mobile-originating short message service over GPRS If the MS is GPRS-attached, it sends the short message through SGSN to the SMS-IWMSC which forwards them to the short message service centre. Subscription check is done in the SGSN according to the data received from the HLR in the GPRS location update. Ready for SM indication in SGSN When the MS informs the HLR of its presence through SGSN (Gr interface), the MNRG flag is reset and the SMSCs, if there are any SMSC addresses in the HLR database, are alerted. Note that it is possible that a MNRG or a MNRF flag is set in the database even if there are no SMSC addresses. The reason is that the MS can become reachable through SGSN and still remain not reachable through MSC (or vice versa). For further information, see MAP in SMS , and Comparative example of SMS over GPRS with MAP version 2 and MAP version 3 . 1.12.3 Comparative example of SMS over GPRS with MAP version 2 and MAP version 3 Generally, the MT-SMS with MAP version 3 includes ten basic steps as described in the following figure. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 59 (267) SMS Guide SMSC 1. MSC/VLR 7. 6. SMS-GMSC SMS-IWMSC 10. 9. 8. 2. 7. 6. 5. 4. 3. HLR BSC SGSN BTS Figure 22. Sending SMs over GPRS 1. 2. SMSC sends an MT-SM. Send-Routing-Info-for-SM arg GMSC requests for routing info from the HLR. 3. Send-Routing-Info-for-SM res HLR sends back the SGSN and VMSC address (because the subscriber has both GSM and GPRS subscription, and is available through both routes) 4. MTForward-SM arg SMS-GMSC tries to deliver the SM through the primary route, that is the SGSN. 5. MTForward-SM res Negative acknowledgement is sent back by the SGSN as the subscriber is not reachable through GPRS. 60 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en Short Message Services 6. MTForward-SM arg SMS-GMSC tries to deliver the SM through the secondary route, that is the MSC/VLR. 7. MTForward-SM res Positive acknowledgement is sent back by the MSC/VLR as the SM was successfully delivered to the subscriber. 8. Report-SM-Delivery-Status arg Successful delivery through the MSC/VLR is reported to the HLR. 9. Report-SM-Delivery-Status res HLR acknowledges the receipt of successful delivery status. 10. SMS-GMSC acknowledges the SM delivery to the SMSC. If a subscriber has both GSM and GPRS subscription, the subscriber is recognized in the HLR as being available through both SGSN and MSC, the primary route indicator set by you is GPRS and the default route in the HLR is set to GPRS, then the main differences between the short message service over GPRS with MAP version 2 and MAP version 3 are the followings: MAP version 2 An MT-SM is sent from the SMSC, the SMS-GMSC request for routing information, and the HLR sends back the SGSN address. The delivery through SGSN is tried but since the subscriber is absent, an AbsentSubscriber Delivery Outcome is sent back to the HLR. The HLR sets the MNRG flag, and the SMSGMSC sends back a negative acknowledgement to the SMSC. (The SMSC waits for AlertSC , or retries delivering the SM according to the SMSC`s RetryTable value for AbsentSubscriber.) If a second SM is sent to the same subscriber, the HLR finds that the MNRG is set, and as the GPRS is set to be the primary route it sends a SendRoutingInfoForSM negative acknowledgement. The GSM route is not tried, and any SM can be delivered only when the subscriber becomes active through GPRS again. It means that although the subscriber is available through GSM, the SM is waiting in the SMSC until the subscriber is GPRS attached again. MAP version 3 dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 61 (267) SMS Guide An MT-SM is sent from the SMSC, the SMS-GMSC request for routing information and the HLR sends back both the SGSN and the VMSC address. Based on the primary route indicator coming from the SMSC or the one stored in the SMS-GMSC, for example, the GPRS route is tried first. The subscriber is absent through this route, so the SMS-GMSC tries the VMSC route where the SM delivery succeed and finally a successful report goes back to the SMSC. At the same time the MNRG flag is set in the HLR, so the next SM delivery for that subscriber is tried only through the GSM network. If the subscriber switches over to GPRS, the Ready-For-SM is sent to the HLR by the SGSN. For more information, see MAP interface operations (MT) , MAP in SMS , and GPRS with SMSC-MSC connection through MAP interface . 1.12.4 GPRS with SMSC-MSC connection through MAP interface SMS over GPRS is also possible in such SMS architecture which includes SS7 MAP interface between the MSC and the SMSC. However, the functions supporting sending short messages over the GPRS network must be implemented in the HLR and in the SMSC as well. VMSC BSC SGSN MAP SMSC MAP Gd HLR Figure 23. SMS over MAP interface For more information, see SMSC product descriptions and instructions. You can also find related information in Comparison of the SMS functionalities in case of SMRSE over X.25 or TCP/IP and SS7 MAP SMSC. 62 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en both the SMSC address and subscriber B to whom the message was originally sent. the SM transfer continues: . The SCP responds with the Continue message.Short Message Services 1. In this case. the TDP is met after the authentication and ciphering for the MO-SMS has been carried out and the MSC has received the SM from the MS. for example. and does not change the SM. The MSC/VLR forwards the original SM to the original SMSIWMSC . Status Report) make IN services possible for example. the MSC/VLR alters the original SM header and sends the message to the SMS-IWMSC. The SCP responds with the Connect message. MT. . . Event Detection Points have been introduced for MO-. The triggers defined for the IN SMS are located in the VMSC . The SCP can also change other parameters in the SM header.and Status Report TDP. In the following cases. The type of the EDPs can be either notification (EDP-N ) or request (EDP-R ). Also. SM transfer is rejected if the SCP sends the ReleaseCall message. The SCP sends the FurnishChargingInformation message(s) related to the Connect or Continue message. It means that the subscriber can benefit the services provided by the SCP only when inside the HPLMN . which can react in several ways. When the MSC/VLR receives this message. The SCP can change the destination. . Mobile-originating IN SMS In the MO case.13 IN Short Message functionality There is a Nokia-specific INAP interface between the MSC and the SCP which realises the IN SMS. redirecting of short messages to another subscriber. When receiving the changed header from the SCP. or allowing the user to prevent short messages from a certain source. MT-. it generates the IN CDR . The SMS triggering detection points (MO-. the type of the message. or can request the monitoring mode. If the TDP is armed (the TDP data is included in the subscriber data). dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 63 (267) . the MSC/ VLR sends an IN service request to the SCP . the MSC/VLR does not forward the SM to the SMS-IWMSC. The SCP arms one or both EDPs (successful or failure). the TDP is met at the earliest possible point after the MSC has received the SM from the SMS-GMSC . If the short message transfer to the SMSC is unsuccessful. In that case the MSC/VLR disarms the request of the SCP. The SCP must change the SMS type from mobile-terminating to mobile-originating before forwarding it to the specified SMS-IWMSC. When the MSC/VLR has received the Connect message with MTHeader (SMS DELIVER) . it delivers the status report to the mobile subscriber. The SCP can change the A-subscriber's address. the MSC reports the success or failure of the transfer to the SCP. In that case the MSC/VLR disarms the request of SCP. which can react in several ways. . or can send it back to the SSP (changed/unchanged) in a MT-Connect operation (MT-VMSC). The event is not reported to the SCP if the EDP has been armed in MT/SR-SMS Connect case. the MSC reports an error back to the GMSC. After receiving the acknowledgement from the IWMSC. . These are the following: When the MSC/VLR has received the Connect message. or the A-. it delivers the MTSM to the mobile subscriber. That is. which makes improved SMS-based services. After receiving the acknowledgement from the MS. After receiving the acknowledgement from MS. If the TDP is armed (the TDP data is included in the subscriber data). the MSC/VLR sends an IN service request to the SCP . the MSC reports the success or failure of the transfer to the SCP. and the MSC/VLR starts paging. - - 64 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . it responds with the Connect message. the SM transfer continues: . the mobile terminated SM (derived from the Connect case) can contain also the A subscriber's address in the originating address field.SMS Guide Mobile-terminating IN SMS / Status Report SMS In the MT case. for example banking services available If the SCP wants to reroute the SM. depending on whether the EDPs are armed or not. When the MSC/VLR has received the Connect message with Status report-Header (SMS REPORT). and the subscriber data in the VLR has been checked. The transfer continues normally. depending on whether the EDPs are armed or not. The event is not reported to the SCP if the EDP has been armed in MT/SR-SMS Connect case. The SCP responds with the Continue message and does not change the SM. and forwards the SM to the MS. and Bsubscriber's addresses as well. it generates the MO short message and forwards it to the specified IWMSC. MSC/VLR can receives three different kind of SM Header from SCP. The SCP can provide the address of the SMSC. the MSC can report the success of the transfer to the GMSC. The SCP also changes the message header of the SM. In the following cases. bar the SM submission allow the submission to continue unchanged allow the SMS processing with modified information (called party number. refer to the feature description of Feature 910: IN Short Message Service . 1. makes contact with the CSE and waits for further instructions. the CSE is able to instruct the VPLMN to include information received from the CSE in charging records and/or to activate other control service events for the SM submission (Unsuccessful SM Submission). It can also send FurnishChargingInformation message(s) but no IN CDR is created. The MSC/VLR does not forward the SM to the MS. Activation information can be found in Handling of IN SMS . calling party number.14 CAMEL short message service CAMEL (Customised Applications for Mobile network Enhanced Logic) is a tool to provide operator-specific services independently of the serving network. . at SMS set-up. For more information. In this case the subscriber can benefit from the services provided by the SCP even when roaming outside the HPLMN . If the subscriber is provided with CAMEL based SMS MO service. or can request the monitoring mode. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 65 (267) . The VPLMN shall be able to detect a SMS set-up request and the CSE shall be able to modify the handling of the SMS set-up request. the VPLMN suspends SMS processing. SMSC address) . Once the CSE has concluded issuing the above instructions. For further information. When the VPLMN has made contact with the CSE. In CAMEL SMS there is a standardized CAP interface between the MSC and the SCP . it issues one of the following instructions: . With CAMEL improved control of MO-SM is possible. see Interworking between CAMEL SM and IN SM . SM transfer is rejected if the SCP responds with the ReleaseCall message. Before sending the ReleaseCall message. the SCP can arm the EDP(s).Short Message Services The SCP can also arm EDP s (of either notification or request type). SMS Guide 1. 66 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . It is applicable from CAMEL 3 onwards. The MO SMS state model is activated when the subscriber sends a mobileoriginating short message.1 Control of MO-SM with CAMEL The following figure describes the relevant network elements and interfaces for the support of CAMEL control of MSC switched MO SMS. GSM Service Control Function GSM Service Switching Function Camel Application Part Functional architecture for the support of CAMEL control of MSCswitched MO SMS The MO SMS State Model contains the service logic for CAMEL control of MO SMS.14. HLR MAP gsmSCF CAP SMSC MAP SMSC SMRSE MS VLR gsmSSF A Interface VMSC IWMSC MAP gsmSCF: gsmSSF: CAP: Figure 24. ReleaseSMS. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 67 (267) .Short Message Services SMS_Null_&_Start_& Authorize SMS_Exception DP SMS_Collected_Info SMS_Analyse & Routing DP O_SMS_Failure DP O_SMS_Submitted O_SMS_Exception Figure 25. RequestReportSMSEvent. Indication that the short message has been successfully delivered to the SMSC. ContinueSMS. MO SMS state model The detection points (DPs) of the model: Table 6. O_SMS_Failure EDP-N EDP-R Indication that the short message submission to the SMSC has failed. FurnishChargingInformationSMS. ResetTimerSMS. The gsmSCF can control short message processing with the following operations: ConnectSMS. CAMEL DP SMS_Collected_Info DPs used for the MO SMS State Model DP Type TDP-R Use of the DP Indication that the SMS-CSI is analysed and a mobileoriginating short message is received. O_SMS_Submitted EDP-N EDP-R For more information refer to feature description of Features 1148 and 1159: CAMEL Phase 3 . OR 2. In this example the destination number and the SMSC address are not modified. The gsmSCF ends the dialogue with the gsmSSF with the CAP operation ContinueSMS. 1. after which the VMSC makes the initial contact with the gsmSCF (through gsmSSF) in the SMS_Collected_Info DP of the MO-SM. The SMS CSI has been provisioned for the A-subscriber. VLR gsmSSF Setup MSC MS MO SMS outgoing leg Visited Network Figure 26. The CAP operation InitialDPSMS is used.SMS Guide Scenario of CAMEL mobile-originating short message Home Network HLR gsmSCF 2. CAMEL mobile-originating short message Preconditions: . Steps: 1. The VMSC/VLR has noticed that the A-subscriber has the SMS-CSI. 68 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . 2. The short message is routed to the new destination. it generates the IN CDR . dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 69 (267) . The SMS-CSI has been provisioned for the A-subscriber. Steps: 1. The VMSC/VLR has noticed that the A-subscriber has the SMS-CSI. Scenario of CAMEL mobile-originating short message with modified destination For the Scenario of mobile-originating short message with modified destination. The SCP arms one or both EDPs (successful or failure).Short Message Services The gsmSCF ends the dialogue with the gsmSSF with the CAP operation ReleaseSMS. The type of the EDPs can be either notification (EDP-N ) or request (EDP-R ). In this case the MSC does not submit the MO-SM towards the SMSC. . The CAP operation InitialDPSMS is used. The gsmSCF ends the dialogue with the gsmSSF with the CAP operation ConnectSMS that instruct the gsmSSF to change the destination number. after which the VMSC makes the initial contact with the gsmSCF (through gsmSSF) in the SMS_Collected_Info DP of the MO-SM. that step 2 of Scenario of CAMEL mobile-originating short message with modified destination differs from step 2 of Scenario of CAMEL mobileoriginating short message . When the MSC/VLR receives this message. Precondition: . . The SCP sends the FurnishChargingInformation message(s) related to the Connect or Continue message. Note Please note. see Figure Scenario of mobile-originating short message. Steps: 70 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .SMS Guide Scenario of CAMEL mobile-originating short message with notification of successful submission to gsmSCF Home Network HLR gsmSCF 4 1 3 2 VLR gsmSSF Setup MSC MS MO SMS outgoing leg Visited Network Figure 27. The SMS-CSI has been provisioned for the A-subscriber. CAMEL mobile-originating short message with notification of successful submission to gsmSCF Preconditions: . 4. the SM was successfully delivered to the SMSC). refer to the feature description of Features 1148 and 1159: CAMEL Phase 3 . the gsmSSF sends the EventReportSMS (Notify and Continue) operation to the gsmSCF. OR When the O_SMS_Failure DP is met (that is. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 71 (267) . The VMSC/VLR has noticed that the A-subscriber has the SMS-CSI.Short Message Services 1. 3. SMS reference number The SMS reference number makes it possible to correlate the SMS Call Detailed Records (CDR) produced by the MSC/SGSN with the SMS CDRs produced by the Service Control Point (SCP) for Camel Control of MO SMS. The gsmSCF arms the detection points O_SMS_Submitted and O_SMS_Failure in the notify mode (EDP-N) with the RequestReportSMSEvent operation. The CAP operation InitialDPSMS is used.14. after which the VMSC makes the initial contact with the gsmSCF (through gsmSSF) in the SMS_Collected_Info DP of the MO-SM.2 Control of MT-SM with CAMEL The following figure describes the relevant network elements and interfaces for the support of CAMEL control of MSC switched MT SMS. For more information. After this the relationship is terminated. After this the relationship is terminated. 1. the gsmSSF sends the EventReportSMS (Notify and Continue) operation to the gsmSCF. When the O_SMS_Submitted DP is met (that is. The gsmSCF sends the ContinueSMS or ConnectSMS operation. In this example the destination number and the SMSC address are not modified. 2. the SM delivery to the SMSC was unsuccessful). GSM Service Control Function GSM Service Switching Function Camel Application Part Functional architecture for the support of CAMEL control of MSCswitched MT SMS The MT SMS state model contains the service logic for CAMEL control of MT SMS. 72 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . It is applicable from CAMEL 4 onwards.SMS Guide HLR MAP gsmSCF CAP SMSC MAP SMSC SMRSE MS VLR gsmSSF A Interface VMSC GMSC MAP gsmSCF: gsmSSF: CAP: Figure 28. MT SMS state model The detection points (DPs) of the model: Table 7. Indication that the SM delivery to the MS has failed. DP T_SMS_Failure EDP-N EDP-R DP T_SMS_Delilvered EDP-N EDP-R For more information refer to the feature description of Feature 1364: MT-SM for CAMEL Phase 4 . Indication that the SM has been successfully delivered to the MS. CAMEL detection point DP SMS Delivery Request DPs used for the MT-SMS state model DP type TDP-R Description Indication that the MT-SMS-CSI is analysed and a mobile-terminating short message is received. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 73 (267) .Short Message Services SMS Null & Start & Authorize SMS_Exception DP SMS_Delivery_Request SMS Delivery DP T_SMS_Failure DP T_SMS_Delivered T_SMS_Exception Figure 29. 1. OR 2. The gsmSCF ends the dialogue with the gsmSSF with the CAP operation ContinueSMS. The CAP operation InitialDPSMS is used. In this example the destination number and the SMSC address are not modified. VLR gsmSSF Deliver MSC MS MT SMS outgoing leg Visited Network Figure 30. CAMEL mobile-terminating short message Precondition: . The SMS CAMEL subscription information (CSI ) has been provisioned for the B-subscriber. after which the VMSC makes the initial contact with the gsmSCF (via gsmSSF) in the DP SMS Delivery Request of the MT-SM.SMS Guide Scenario of CAMEL mobile-terminating short message Home Network HLR gsmSCF 2. The VMSC/VLR has noticed that the B-subscriber has the SMS-CSI. 74 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Steps: 1. SMS reference number The SMS reference number makes it possible to correlate the SMS Call Detailed Records (CDR) produced by the MSC/SGSN with the SMS CDRs produced by the Service Control Point (SCP) for Camel Control of MT SMS. . The MT-SMS-CSI has been provisioned for the B-subscriber. after which the VMSC makes the initial contact with the gsmSCF (via gsmSSF) in the SMS_Delivery_Request DP of the MT-SM.14. The gsmSCF ends the dialogue with the gsmSSF with the CAP operation ConnectSMS that instruct the gsmSSF to change the Calling Party address.Short Message Services The gsmSCF ends the dialogue with the gsmSSF with the CAP operation ReleaseSMS. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 75 (267) . For more details. 1. Steps: . The type of the EDPs can be either notification (EDP-N ) or request (EDP-R ). Note The Called Party Address and the SMSC address can not be changed. The VMSC/VLR has noticed that the B-subscriber has the MT-SMS-CSI. Scenario of CAMEL mobile-terminating short message with modified destination Precondition: . The short message is delivered to subscriber B.3 Interworking between CAMEL SM and IN SM IN Short Message Service (feature 910) has a proprietary functionality which is similar to the SMS part of CAMEL 3 and CAMEL 4. The SCP arms one or both EDPs (successful or failure). see IN short message functionality . The CAP operation InitialDPSMS is used. In this case the MSC does not submit the MT-SM towards the SMSC. If you want CAMEL 4 to work for that subscriber also in the HPLMN. because if they want to use all the services. after which the MSC should know in which SMSC the application exists.400).SMS Guide When the subscriber is roaming. the subscriber selects the appropriate PID value (for example.15 Short message routing Most of the operators have GSM network with more than one SMSC. you have to set off Feature 910: IN Short Message Service MO DP for that subscriber. 1. When the subscriber is in the Home PLMN. you have to set off Feature 910: IN Short Message Service MT DP for that subscriber. If you want CAMEL 3 to work for that subscriber also in the HPLMN. 76 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . and so on. they should not only know many SMSC addresses. and another for e-mail. telefax. but also remember to change the address in the MS before using the services. For example. and to configure the VMSC in a way that the MO-SM is routed to the right SMSC in the PLMN. and for accessing service provider services (such as weather. The standard procedure for this is to use a PID (Protocol Identifier). stock market information). This is possible only if the MSC is able to solve the destination application from the MO-SM. . when sending an MO-SM. CAMEL 3 CAMEL 4 are the features that can be active. X. When IN functionality MT DP is set for the subscriber. one SMSC can be dedicated for MO-MTs and voice mail alert services. If the IN functionality MO DP is set for the subscriber. IN MT functionality will take precedence over CAMEL 4. The MML command for creating SMS routing analysis is CFE . This means that services offered by one SMSC are not the same as those offered by another SMSC. the IN MO functionality takes precedence over CAMEL 3. the following case cases can be distinguished: . A solution for overcoming this is to always use the same SMSC address in the MS. For example. telefax. This is confusing for the subscribers. 991 for service provider applications. The SAP can be. Each application known by the SMSC has its own SAP. Note that in this way it is not necessary to change the PID value for e-mail or telefax. 991 indicates the service provider application.Short Message Services SMSC1 for MS-to-MS messages normal MO-SMS 1 SMS-IWMSC1 1 1 2 VMSC fax MO-SMS 2 SMS-IWMSC2 fax MO-SMS 2 SMSC2 for fax and email messages Figure 31. and an MML for maintaining the table. The subscriber gives the SAP in the beginning of the destination address. and 1000 the service (here: weather reports). as shown in the example below: dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 77 (267) . for example. The Nokia SMSC also uses this prefix to differentiate between the applications. 993 for telefax and so on. 992 for e-mail. In this case. SMS routing However. because there are applications which do not have PID values of their own. In the Nokia VMSC you can solve this by using a Service Application Prefix (SAP). the PID alone is not enough. weather reports could be requested by sending a message to address '991 1000'. There is a table for MO-SM routing based on PIDs and/or SAPsin the MSC. for example. SMS Guide Table 8. Only faxes are handled in a different way. You can also set a default SMSC to be used and/or a tariff class for it in a case where no SAP or PID analysis is found. a PID is defined for fax only. If a PID in the MO-SM has been defined in the table. This could be used. If. for example. Service Application Name CIMD FAX E-MAIL E-MAIL MT DEFAULT Example of a routing table SAPTYPE SMSC address Tariff class PID SAP  52 53  0  991 993 EMAIL 992   international national alphanumeric international   443580002 443580001 443580001 443580001 443580003 443589999 1 3 4   2 The fields of the table are interpreted in the following way: 1. for example. 78 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . When routing SMs from one MSC to another. This could happen when the MSC1 routes messages to MSC2 which again forwards them to the MSC1. you must be careful that a loop between MSCs does not occur. see Charging of SMs to service applications . use the SMSC address defined for the PID. If a SAP in the MO-SM has been defined in the table. 3. 2. use the SMSC address defined for the SAP. For more information on the relation of tariff classes and charging. the normal SMS functionality is not affected. If none of the above have been defined. everything else is handled as if no PID/SAP analysis existed. to make all the subscribers of a particular network use the operator's own SMSCs. use the SMSC address normally given by the subscriber. it compares this MT-SMS address with the original address stored in mobile setup.Short Message Services One consequence of SMS routing is that when the SMSCs send MT-SMs. However. that is. The following figure describes how SMSC address are used in MT-SMS between different network elements: SMSCA SMSC A SMSCB SMS-GMSC SMSCA SMSCB HLR SMSC SMSC B SMSC VMSC Linetype Linetype means SMS transfer from SMSCA means SMS transfer from SMSCB Figure 32. If you have feature 1165 in use in your network. they are sent from the HLR to the correct SMSC. they all use individual SMSC addresses. and Managing SMS network element-specific data . depends on the availability of Feature 1165: GSM Phase 2+ Enhancements . This can be solved by configuring the SMSC address used towards subscribers in the SMS-GMSC . For more information see SMS management instructions in Configuring network elements for SMS . dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 79 (267) . SMSC address used in MT-SMS between different network elements SMS routing analysis The decision whether the SMS routing analysis is executed or not in the VMSC. they correspond to one logical SMSC address. when receiving status reports. See also Working examples for SMS management . the SMSC address is analysed by invoking the SMS routing support analysis. This can cause problems with an MS if. This analysis indicates whether the SMS routing analysis should be executed or not. The same address that SMSC originally used in MT-SMS when setting the MWD must be used to make sure that alerts work correctly. The execution of the analysis in the SMS-IWMSC is unconditional if you have this function in use. the roaming status will be 'HOME' despite the different network codes. If you set the home PLMNs in the PLMN-specific parameter file with the MXN command so that HPLMN=Y. GSM Phase 2+ Enhancements in your network.1 SMS routing enhancements Routing of short messages is enhanced by: . 80 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . the SMS routing analysis is invoked. If the roaming status is home network/home subscriber. this feature enables you to define an SMSC address on the basis of which the routing analysis is executed. The roaming status is determined from the IMSI of the subscriber in the VLR. a change in the routing analysis the use of alphanumeric addresses . 1. This way the SMS routing analysis is executed for all home subscribers. There is a change in the logic which defines when the routing analysis (based on PID or SAP) applies for a short message. see Alphanumeric addressing of SMS-related applications . As the protocol identifier and SAP are tightly related to the SMSC's function. Note If the SMS routing support analysis function is not active. the decision about executing the SMS routing analysis is entirely based on the roaming status information received form the VLR. For further information. These enhancements are available if you have Feature 1165: Short Message Services. GSM Phase 2+ Enhancements . For details. HCOUN=Y. the VLR sets the subscriber's roaming status by reading the status of HPLMN and home country (HCOUN) from the result record in the PLMN-specific parameter file and sends it to the SMS application.SMS Guide If you do not have feature 1165 in use. If you define a need for the SMSC routing analysis. refer to the feature activation instructions of Feature 1165: Short Message Services.15. Note MAP version 3 is needed for these functionalities. the routing analysis is executed. Application level or SCCP level load sharing is executed between SMSC1 and SMSC2. that the alphanumeric destination address can be maximum 11 characters. but all the other destination addresses is extended. The following figure shows a solution for routing SMs based on the type of the subscriber: GT analysis for Logical SMSC address DPC=IN platform Logical SMSC address remains SMSC address: Logical SMSC address IN platform MS Prepaid SMSC address: Logical SMSC address SMSC address is changed to virtual SMSC address as this is the input of the load sharing algorithm. Note that the length of not only the alphanumeric. international and alphabetical addresses. 1. see Activating routing enhancement in SMS . and in the storage of numbers in the analysis files.15. This results in further changes in the charging and statistics for alphanumeric addresses. For related information.2 Short message routing based on subscriber type If you have Feature 1598: SMS Routing Based on Subscriber Type in use. The SAP analysis has to be defined separately for national. international and alphabetical destination addresses.Short Message Services The routing enhancement also enables you to define different routing rules for national. by routing Short Messages (SMs) either to the Short Message Service Center (SMSC) or to the IN platform based on the subscriber type. Short message routing based on prepaid and post-paid subscribers dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 81 (267) . SMSC1 MS Post-paid VMSC SMSC2 Figure 33. Please note. it is possible to reduce the load of the Intelligent Network (IN) platform node. 1. or directly to the SMSC in case of a post-paid subscriber. and that each subscriber is marked with the ICK (IN category key) parameter if they are prepaid or post-paid subscribers. the load of the Interworking MSC (IWMSC) and the Gateway MSC (GMSC ) is also reduced. it is possible to provide solution for direct SM delivery without the involvement of the Short Message Service Centre (SMSC ). it is necessary that only one logical SMSC address is used in the network.SMS Guide By splitting the SM traffic of prepaid and post-paid subscribers. the MO-VMSC can directly deliver the MO-SM by converting it to an MT-SM. and forwarding it to the proper Mobile-Terminated Visited Mobile Services Switching Centre (MTVMSC) after the Home Location Register (HLR) enquiry. and SM delivery is carried out in the traditional way. this value is shown in the Mobile-Originated Short Message Service Charging Records (SMMO CDR). This feature is implemented in the Mobile-Originated Visited Mobile Services Switching Centre (MO-VMSC). The type of the subscriber is determined by checking the value of ICK parameter. This solution also enables you to distinguish the direct SMs from normal SMs in the SMS measurement and in the Charging Data Records (CDRs). it is possible to route Mobile-Originated Short Messages (MO-SMs) from the Home Public Land Mobile Network (HPLMN) to the IN platform in case of a prepaid subscriber.16 Sending SMS without SMSC If you have Feature 1633: Direct SM Delivery in use. This solution provides a considerable decrease in the load of the SMSC and also the MAP or SMRSE interface between the Mobile Services Switching Centre (MSC ) and the SMSC. If subscriber B is available and subscriber A is not roaming. the MO-VMSC forwards the MO-SM to the SMSC. To route SMs depending on subscriber type. In case of SMRSE SMSC. In case of any error. The decision on 'Non-store and forward' SM delivery without the SMSC is made as follows: 82 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . If you use this feature. The MO-VMSC receives a normal MO-SM from the subscriber. the MO-SM is forwarded to the SMSC in the traditional way. If the SMSC address of the MT-SM is the same as stored in the HRNFIL. the SM can be handled in the following ways: . The MO-VMSC then forwards the SM to the SMSC. the MSC delivers the SM directly. 2. If the MT-SM delivery is not successful. For more information about possible parameter setting. Depending on whether there is routing analysis for the B-number. When the MT-SM arrives in the MT-VMSC. If there is analysis for the application terminated SM. If DIRECT_SM_STA_CHA_INFO parameter is activated. It also checks if there is routing analysis for the Bnumber of the MO-SM. The MT-VMSC delivers the MT-SM in a normal way. If the SMSC supports this functionality. and the barring checking. and the next delivery attempt will be based on the SMSC retry table. If there is no analysis for the B-number of the MO-SM. see the feature description of Feature 1633: Direct SM Delivery Direct SM delivery When direct SM delivery is performed. the MT-SM is a DIRECTSM. the SMS application checks the SMSC address. the MT-VMSC sends back a negative acknowledgement to the MT-GMSC/MO-VMSC. This means that the MSC makes the HLR enquiry and sends the Forward-SM MAP operation to the correct MT-VMSC. The SMS application executes the IN interaction (if needed). If DIRECT_SM_FAILURE_IND parameter is activated. The SMS application also converts the MO-SM to an MT-SM. the SMS application sends positive acknowledgement to the MS. which has to be indicated in the statistics and charging data records. the MO-VMSC sets the reserved value of Transport Protocol-Message Type Indication (TP-MTI) field in the SUBMIT-MO-SM. if SMS routing analysis is used in the network also for MO-MT SMs (not just for MO-AT SMs). which allows that the SM delivered by the MSC can be differentiated from the normal SM in the statistics reports and charging data records. and starts the GMSC functionality. . which receives a 'Message sent' response. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 83 (267) . the SMSC address of the MO-SM is changed to the operator-predefined SMSC address. it can handle the SM based on this reserved value as delayed delivery.Short Message Services 1. It is possible to check the Service Application Name (SAN) to decide if direct SM delivery should be performed. 10. and it is not affected by this feature. 2. If the SMSC has SMRSE interface. and converting MO-SM to MT-SM (GMSC functionality invoked) SMS-SUBMIT-REPORT SRI-FOR-SM SRI-FOR-SM-ACK MT-FORWARD-SM SMS-DELIVER SMS-DELIVER-REPORT SMMT CDR. 9. 7. 11. 3. 8. the IWMSC is a separate network element.SMS Guide The following figures illustrate the SMSC with MAP interface including the Interworking Mobile Services Switching Centre (IWMSC ) functionality. STATISTICS REPORT UPDATE SMMO CDR from MO-VMSC. 12. SUBMIT-MO-SM Checking SMS routing analysis (Application-terminated SM). 4. 5. if it is requested 84 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . 6. 13. 4 1 3 13 2 12 11 MO-VMSC MT-GMSC 6 10 HLR 5 7 8 9 MT-VMSC SMSC 1. STATISTICS REPORT UPDATE MSC generates the status report. STATISTICS REPORT UPDATE MT-FORWARD-SM-ACK SMMT CDR from GMSC. 9. 8. 14. and converting MO-SM to MT-SM (GMSC functionality invoked) SMS-SUBMIT-REPORT SRI-FOR-SM SRI-FOR-SM-ACK MT-FORWARD-SM PAGING No paging response (timer expires) SMMT CDR from MT-VMSC. STATISTICS REPORT UPDATE dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 85 (267) . 6. 10. STATISTICS REPORT UPDATE MT-FORWARD-SM-NACK SMMT CDR from MT-GMSC.Short Message Services Figure 34. 7. 13. 12. Successful SM delivery 1 3 2 14 4 5 11 MO-VMSC MT-GMSC 6 10 12 13 HLR 7 8 9 MT-VMSC SMSC 1. STATISTICS REPORT UPDATE MO-FORWARD-SM to SMSC MO-FORWARD-SM-ACK SMMO CDR from MO-VMSC. 4. 3. SUBMIT-MO-SM Checking SMS routing analysis (Application-terminated SM). 2. 5. 11. 3. no paging response 4 1 3 2 9 MO-VMSC MT-GMSC 7 8 HLR 6 5 MT-VMSC SMSC 1. 8. 9. and converting MO-SM to MT-SM (GMSC functionality invoked) SMS-SUBMIT-REPORT SRI-FOR-SM SRI-FOR-SM-NACK (subscriber in detach state) SMMT CDR from MT-GMSC. STATISTICS REPORT UPDATE Unsuccessful SM delivery. 5. 4. absent subscriber Figure 36. 7. Unsuccessful SM delivery. SUBMIT-MO-SM Checking SMS routing analysis (Application-terminated SM). 6. 86 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . STATISTICS REPORT UPDATE MO-FORWARD-SM to SMSC MO-FORWARD-SM-ACK SMMO CDR from MO-VMSC. 2.SMS Guide Figure 35. SMS CFU also works in situations where the subscriber receives an SM from a foreign PLMN. VMSC GMSC/ SMSC SendRoutingInfoForSM HLR-B HLR-C SendIMSI SendIMSIAck SendRoutingInfoForSM SendRoutingInfoForSMAck Inform-SC SendRoutingInfoForSMAck Inform-SC MT-ForwardSM MT-ForwardSMAck Figure 37.1 Basic forwarded MT-SMS The following figure shows the basic forwarded MT-SMS functionality. SMS forwarding is an HLR-feature. but MAP version 3 must be supported in the HLR. If you have Feature 626: Supplementary Services Phase 2 Extensions in use.Short Message Services 1. Basic forwarded MT-SMS functionality dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 87 (267) . 1. the subscriber can flexibly define the number to which the SM is forwarded.17.17 SMS Forwarding Short Message Service Call Forwarding Unconditional (SMS CFU ) supports SMS forwarding either to an active subscriber or to a subscriber who is currently detached. and inform-SC is always sent from HLR-C. For more information. SendRoutingInfoForSM is sent to HLR-C. HLR-C acknowledges the operation to the GMSC with subscriber C's information. The maximum number of forwardings is one. Exceptions: 1. It notices that subscriber B has CFU active and the request should be forwarded to HLR-C. 4. but subscriber C is not allowed to forward it further. and not forwarded to subscriber C. In that case the SM is sent to subscriber B. see the feature description of Feature 626: Supplementary Services Phase 2 Extensions . The procedure is the following: 1. Otherwise there are some restrictions in the functionality. subscriber B has SMS CFU active to subscriber C the feature is active in subscriber B's HLR SMS forwarding is allowed to subscriber C's network. The subscriber C's HLR should also support the SMS forwarding feature. This can happen if subscriber C has changed the operator after subscriber B has registered SMS CFU to subscriber C. Subscriber C must belong to the same network with subscriber B or to one of the additional networks defined by the operator. The Inform-SC operation contains the MSISDN-C number. . If the SMSC does not support the Inform-SC procedure. this SM can be forwarded to subscriber C under the following conditions: . This means that subscriber B can forward the SMS to subscriber C. HLR-B receives SendRoutingInfoForSM operation. Subscriber C is in a PLMN where forwarding is not allowed. 88 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . 2. This kind of situation causes problems if subscriber C is unreachable and then becomes reachable again. If forwarding is allowed. 3. 5. HLR-B checks that forwarding is allowed to the destination PLMN by requesting subscriber C's IMSI from the HLR. Before forwarding. 2. .SMS Guide When subscriber A sends an SM to subscriber B. MSISDN-C is not stored in the SMSC. especially when subscriber C is not reachable. 1. This means that if CFU is provisioned or activated to all basic services by using MML commands. each subscriber has its own record. . It is also not possible to remove SMS CFU separately. . If the MS understands these MMI strings (for example.Short Message Services 1.3 MMI procedures to activate SMS forwarding The subscriber can manage SMS CFU by using the MMI of the mobile station (MS). this does not include SMS forwarding. activate. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 89 (267) . The following MMI procedures can be used: . If you give CFU for SMS. It is not possible to provide CFU only for SMS.18 Same CLI for multiple subscribers If you have Feature 1541: Same CLI for Multiple Subscribers in your network. which is extended with an attribute. . You can give SMS at the same time with the provision of CFU or add CFU for SMS afterwards. **21*nbr*16# (RegisterSS) *21**16# (ActivateSS) ##21**16# (EraseSS) #21**16# (DeactivateSS) *#21**16# (InterrogateSS) . The own MSISDN number is a unique identifier. In the HLR. The HLR stores the subscriber (IMSI) -related data under the so-called 'own MSISDN' number. If the MS does not support these service codes. and the subscriber does not have CFU. register). 1.17. then the HLR automatically provides CFU for the subscriber. they are sent as GSM standard supplementary service operations. This attribute contains the 'common MSISDN' number. but the complete CFU must be removed. the subscriber cannot manage the service with the MS. Create SMS basic service to the subscriber before provisioning SMS CFU. otherwise the command fails with error code 'Teleservice not provided'.2 Provisioning and activating SMS forwarding SMS CFU is provisioned and activated separately from CFU. The phones can belong to one or more users. whereas the common MSISDN number can belong to several records. it is possible that several mobile phones (IMSIs) use a common MSISDN number when originating calls (voice or data) or sending short messages.17. As an option. The CLI restriction. exchange info. Even if the common MSISDN is used as the primary identifier. train timetable). This service is applicable only to voice calls and data calls in case of sequential alerting. The Same CLI for Multiple Subscribers feature makes it possible for several subscribers to use a common MSISDN in mobile-originating transactions. and Parallel Alerting. the own MSISDN number is still sent to the VLR as a normal subscriber attribute (in a proprietary extension). Sequential Alerting. 1. Other mobile-terminating transactions with the ringing group MSISDN are delivered only to a dedicated member called primary member. The features Sequential Alerting and Parallel Alerting make it possible to terminate speech calls to a group MSISDN sequentially (in a user definable order) or simultaneously alerting the phones (SIMs). Depending on the visited PLMN's capability. This means that the short messages sent to the common MSISDN will reach the primary phone. 90 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . the CLI restriction service can be set to hide the own MSISDN number in permanent mode if the PLMN does not support storing many records with the same MSISDN number in the same VLR/SGSN. the primary IMSI-related data is retrieved and included in the response of the transaction.19 Sequential alerting and parallel alerting for MultiSIM Service MultiSIM is a service that makes it possible to group several individual subscriptions behind the same Mobile Subscriber International ISDN Number (MSISDN). however. When the user sends short message from the non-primary phone (the own MSISDN is different from the common MSISDN) to a service center requesting some content (for example. either the own MSISDN number or the common MSISDN number is transferred to the VLR/SGSN during a location update as primary identifier (preconfigurable in the HLR).SMS Guide The primary phone has the same own and common MSISDN number. the server responds to the received originating MSISDN (the common MSISDN) and the response SM finally goes to the primary phone. has no effect on the 'CLI' included in MO-SM. In case of an HLR query with the common MSISDN number. The usage of Same CLI for multiple subscribers feature can have effect on SMS based services. The MultiSIM service comprises of the combination of the following features: Same CLI for Multiple Subscribers. The members of the ringing group can also be considered as individual subscribers. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 91 (267) . then the internal method is the only possibility. Traffic administration can collect SMS data in the VMSC. In the internal method. MT-SMs to their member MSISDN are delivered only to the specific member. MWD is stored into both the group subscriber and primary member data. an internal method which is not visible to MAP level SMS forwarding mechanism of Feature 626: GSM Supplementary Services Phase 2 Extensions The SMS Forwarding mechanism requires that Feature 626: GSM Supplementary Services Phase 2 Extensions is in use.19. If that feature is not in use. 1.20 Short message charging It is possible to collect charging data for both the MT-SMS and MO-SMS in the VMSC . and the SMS-IWMSC . The functionality of the primary member is exactly the same as the functionality of C-subscriber in case of SMS CFU. see Feature 1545 and 1576: Sequential and Parallel Alerting.Short Message Services For more information about the functionality. Delivery status report for MO-SMs from any of the phones normally goes to the primary member. 1. It is possible to restrict the mobile-terminating speech calls and MT-SMs with the member number. 2.2 MT-SMS routing to the primary member There are two alternative methods to route SMS to the primary member: 1. A new flag: Mobile Not Reachable Multi (MNRM) is stored into the primary member data to indicate that there is MWD in the group subscriber data. otherwise the MT-SM fails due to the absent subscriber. the Message Waiting Data (MWD ) is stored into the group subscriber data. the SMS-GMSC .19. In the SMS Forwarding mechanism. 1. when the common MSISDN number is delivered to the MSC/ VLR and it identifies a ringing group. SMS-GMSC and SMS-IWMSC.1 Delivery of mobile-terminating short messages MT-SM to the ringing group number is delivered only to the primary phone if the primary member exists. the group subscriber in MultiSIM service uses the MSISDN of the primary member in the same way as c-number of SMS Call Forwarding Unconditional (CFU). SMS Guide If Feature 619: Short Message Service Enhancements is in use in your exchange. . Charging records (CDRs) The SMS-related CDRs are the following: . charging of command SMs and status reports between MS and SMSC. . In addition. You can use the commands of Detailed Charging Handling GT command group to control SMS-related charging. For further information. charging based on subscriber's IMSI. tariff class calling IMSI called IMSI calling VMSC number called number SMS length dialled number . since these SMs do not contain an MT-SM part. . The most important exception to this is when MO-SMs are being sent to a service application. . Operators usually charge the subscribers for short messages on the basis of the MO-SM CDRs. In this case. and thus no MT-SM CDR is generated. . These include charging of roaming subscribers. . However. The different charging cases are explained below. 92 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . see Charging of SMs to service applications . charging of SMs created by applications. you can create different charging cases for different short message services. the MO-SM CDRs are the only place to charge. the CDRs contain information such as: . as well as charging of SMs to service applications such as fax and e-mail. the amount of CDRs generated in the VMSC can be limited. For operating instructions and descriptions refer to Charging Handling . the majority of the billing information can also be obtained from the MT-SM CDR. SMMO CDRs (for mobile-originating SMS) SMMT CDRs (for mobile-terminating SMS) SMMF CDRs (for forwarded SMS) IN CDRs (for IN SMS) . . If charging is concentrated in the SMS-IWMSC/SMS-GMSC. The routing category can be defined separately for each subscriber. . SMS type picture message routing category . the called number field in the SMS-IWMSC is empty. For related information. you can apply different charging for mobile-originating short messages without having separate MT-SM CDRs for status reports if the subscribers wishes to receive a status report about whether their SMs were delivered to subscriber B or not. see Alphanumeric addressing of SMS-related applications . . If the dialled number is not of alphanumeric type. . The charging data record for MO-SMs has a new field dialled_digits_TON to indicate the dialled alphanumeric number type. that is. Direct SM. In case of concatenated short messages. and this information in the CDR can be used. Generating CDRs only for the first SM in a concatenated short message substantially decreases the load of both the network and the billing centre. . . Trigger SM) . for example. The SMS type field contains information about whether the SM is: . SM status request indication can also be included in the MO-SM CDRs. to distinguish between prepaid and postpaid subscribers. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 93 (267) . MO-SM mobile-originating command short message MT-SM mobile-terminating status report mobile-originating message status report requested forwarded short message special SM (Welcome SM.Short Message Services Note If the subscriber B number is wrong. while the dialled number field is filled. . it is possible to generate CDRs only for the first SM by setting the 031:0028 PRFILE parameter on. . the value of this field is unknown. The CDRs also include information on concatenated short messages and picture messages. Note In the SMMO CDR there is a VMSC address field indicating through which VMSC the SM is sent. However. You can reduce the CDR generation by using an option in the TSC (SMS-IWMSC and SMS-GMSC) by allowing CDR generation only when they are really needed. the TSC (which means here the SMS-IWMSC and SMS-GMSC) generates CDRs for all the MO-/ MT-SMs.SMS Guide The following fields can have alphanumeric value in the SMMO CDR: . This way you can decrease the load of both the network and the billing centre. For more information on CDRs in general. For more information on CDR improvements see the feature descriptions of Feature 619: Short Message Service Enhancements . dialled_digits called_number . In case of SMs originating and terminating in the same PLMN. if SM rerouting takes place. The SMSC application can send MT-SM when the originating address (A number) is of alphanumeric type. note that in the SMMO CDR created in the second SMS-IWMSC this field contains the previous SMS-IWMSC address instead of the VMSC address. Selective CDR generation in the Transit MSC (TSC) Nowadays. and Feature 1043: Short Message Services GSM Phase 2+ . the TSC (SMSIWMSC and SMS-GMSC) does not generate CDRs for the MO-/MT-SMs which come from or go to the same PLMN. the same CDRs are generated in the visited MSC and TSC (for subscriber A and subscriber B ). that is. Interface Specification. It means that if the optional FIFILE parameter 031:0026 TRANS_SEL_CDR_GEN is turned on. Interface Specification and MSC/HLR-BC. The MSC/VLR supports this function and generates SMMT and SMMF CDRs. for subscriber charging and/or inter-operator accounting. 94 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . see CDR Field Description. depending on whether the subscribers are roaming in different network elements.1 SMS charging for subscribers Improvements made in charging data transfer enable you to perform different types of charging. This results in a decrease of load in the MSC/billing centre.Short Message Services Note You can control the MO-SM and MT-SM CDR generation separately with the direction parameter. Selective CDR generation based on SMSC address Charging Records (CDRs) can be suppressed depending on the SMSC ISDN address. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 95 (267) . SMS-GMSC VMSC In connection with this functionality. The following table shows from which network elements the CDRs can be controlled: Table 9. Type of CDR MO-SM CDR MT-SM CDR MF-SM CDR Types of CDR and network elements Network element from where it can be controlled VMSC. You can control the MO-SM and MT-SM CDR generation with MML commands. a new SMSC address analysis is needed in the MSC to decide whether the MO-SM or the MT-SM CDR is barred or not. it is possible to suppress either the MO-SM CDR generation. SMS-IWMSC VMSC. You can also charge different value-added applications that use MS services. that by defining the SMSC address.20. or both at the same time. see Activating selective CDR generation in SMS . and on what services they are using. 1. For related information. This means. or the MT-SM CDR generation only. . In the SMS-IWMSC. . Create a CDR for all SMS-COMMAND SMs which are sent. Create a CDR only for SMS-STATUS-REPORT SMs which were sent successfully.SMS Guide SMS charging for mobile subscribers If feature 327 is in use in your exchange. or. Create a CDR only for roaming subscribers for all SMs which are sent (including SMS-COMMAND and STATUS-REPORT). if charging is concentrated in SMS-IWMSC/SMS-GMSC. For more information. Create a CDR for all SMS-STATUS-REPORT SMs which are sent. . where the address is added to the MT-SM CDR. . . For more information. Create a CDR only for SMS-COMMAND SMs which were sent successfully. see Feature 619: Short Message Service Enhancements . and the traffic administration can collect SMS data in all of them. you can set the CDR to be created in the VMSC for roaming subscribers only. SMS-GMSC and SMS-IWMSC . Create a CDR only for roaming subscribers for only those normal SMs which were sent successfully (including SMS-COMMAND and STATUSREPORT). . the charging implications include an option to make detail record of MO-SMs (both in the VMSC and the SMSIWMSC and MT-SMs (both in the SMS-GMSC and the VMSC). the 96 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . subscriber A's VMSC address is transferred to the SMSC which further transfers it to a SMS-GMSC. The billing centre can now analyse at least the networks where the subscriber is roaming. Create a CDR for all normal SMs which are sent (excluding SMSCOMMAND and STATUS-REPORT). SMS charging for roaming subscribers Roaming subscribers cannot be charged according to their location unless information is transferred on subscriber A's location (VMSC address) in the MTSM CDR . Create a CDR for only those normal SMs which were sent successfully (excluding SMS-COMMAND and STATUS-REPORT). if both are located in their own networks. Both MT-SMs and MO-SMs can be charged in the VMSC . Furthermore. . You can choose how to perform SMS charging by following steps given below. . see the feature description of Feature 327: Short Message Services . Inter-network addressing is usually based on global title addresses. 1. An analysis of the MO-SM CDR is no longer needed. cases like this are likely to happen only within one's own network. Feature 619 makes it possible for you to control whether IMSI is sent to the SMSC for charging purposes. The billing centre can now set the fee by using tariff classes which have been defined only once for both the SMSC and the billing centre. The following figure shows the charging of SMs generated by applications. You have to set the CHARGING_BASED_ON_IMSI PRFILE parameter on to determine whether the IMSI of a subscriber is used for charging purposes within the SMS.20. In case of MAP version 3 the VMSC sends the IMSI to the SMS-IWMSC through the MO-Forward-SM operation.Short Message Services MSCs where the subscribers are located. If signalling point addressing is used on the SCCP level. On the other hand. where they are added to the MT-SM CDR. In MO-SMS in case of MAP version 2 . In MTSMS a subscriber's IMSI is available both in the SMS-GMSC and the VMSC . Adding subscriber A's VMSC field in the MT-SM CDR allows determining extra charges for an MO-SM sent from a subscriber roaming outside the subscriber's own network. New services with different origins can easily be added because the fee can be determined on the basis of tariff class information. Note that the availability of a VMSC address depends on the network configuration. IMSI is not available in the SMS-IWMSC.2 Charging of SMs generated by applications To avoid constant changes in configurations. You can find a list of parameters in SMS-related general parameter file (PRFILE/FIFILE) parameters . and VMSC addresses are available. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 97 (267) . the VMSC address cannot be obtained. The SMSC transfers tariff classes to the SMSGMSC. SMS charging based on subscriber's IMSI Charging can generally be based on IMSI rather than MSISDN address. It is possible for SMS-IWMSC to fetch the subscriber's IMSI from the HLR by using MAP phase 2 operation send_IMSI if you have feature 619 in use. information on new tariff classes is added to the MT-SM CDR . charging can be determined on the basis of the prefix associated with the relevant WAP application. an MO-SM to another MS can be charged quite low. for example. The tariff class is included in the MO-SM CDR . it is not sent to the charging applications.SMS Guide HLR Application SRI 2 SMS-GMSC VMSC MT-SMS 4 SMSC MT-SMS 1 Tariff Class 3 ForwardSM Tariff Class -> MT-CDR Figure 38. Charging of SMs generated by applications The tariff class field makes it easier to add new service applications without having to define them in the billing system. The use of prefixes for charging can be useful. in case of short messages sent to Wireless Applications Protocol (WAP) servers. Neither the PID nor the prefix are sent to charging applications. The MO-SMs to different applications can have different prices. 98 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .3 Charging of SMs to service applications The MO-SM routing analysis in the MSC is useful also for charging purposes. In this case. while an MO-SM to a telefax address can be much more expensive. SMs to applications are charged according to the MO-SM CDRs. If no tariff class has been defined for a certain PID /prefix. 1. and SMs to MSs are charged according to the MT-SM CDRs. for example.20. Charging of these SMs is handled from the SMS-IWMSC/VMSC CDRs. 1. 3. To be able to charge subscribers sending SMs to different services (users) from different locations. MT-SMs generated by an application service are charged from the SMSGMSC if a tariff class has been received from the SMSC. In CAMEL 2. For background information see CAMEL short message service . and not carried in all interfaces. the SCP manages the billing. In case of a prepaid service. These can be used for billing the subscriber by the service based at the billing center. 2. A PID and/or a prefix analysis with a tariff class is created for every application service for an MO-SM. they are not necessarily available for charging and statistical purposes in every MSC/VLR. IN4 CDR is used already in call related cases. and the new IN5 CDR is introduced. CAMEL_EXCHANGE_ID. The fee can be determined by comparing subscriber A's VMSC address with the SMS-GMSC address. CAMEL_EXCHANGE_ID_TON AND PARTY_TO_CHARGE). In CAMEL 3. New CDR Fields IN5 CDR includes the same fields as IN4 CDR. note the following suggestions on the configuration: 1. the modified number is used in CDRs.Short Message Services Note that some of the new parameters are optional.20. Separate charging can be created for SMS commands by transferring the SM type 'command' to the charging application in the SMS-IWMSC/ VMSC. Therefore. When the gsmSCF modifies the subscriber number. 4. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 99 (267) . and/or by comparing subscriber B's VMSC address with the SMS-GMSC address. and the call time of the subscriber is restricted in the SSP according the instructions of the SCP. CDR generation in CAMEL SMS SMMO CDR is generated for originated SM.4 Charging of CAMEL SMs The CAMEL service at the SCP can create special CDRs for SMs containing free format data by FCI operation. the maximum length of FCI data raises from the current 40 octets to 160 octets. Fields to which the information is not available are filled with FF's (CAMEL_CALL_REFERENCE. Normal MS-to-MS SMs are charged from the SMS-GMSC of the MTCDR. the gsmSCF was not available and whether CAMEL encountered default SMS handling. which is sent towards the charging application.SMS Guide DEFAULT_SMS_HANDLING and CAMEL_SMS_MODIFICATION fields are added to SMMO CDR. the B-MSISDN number does not specify the destination network of an SM and therefore not enough for charging purposes. 1. You can find a list of parameters in section SMS-related general parameter file (PRFILE/FIFILE) parameters . The release message can be received if the subscriber. If you want to offer different prices based on the mobile service provider of the called party in case of MNP. calling number destination subscriber number SMSC address SMS Reference number .5 MO-SM fraud prevention You can allow real charging information to be forwarded from the SMS application to charging application with the CHAR_WITHOUT_ACK_TO_MS PRFILE parameter even if a release message has been received from the MS before the acknowledgement from the SMSC. since only this number can identify the network of the B subscriber. In case of a FALSE value. for example. These are the following: . the SMS application informs the charging application about the MO-SM being unsuccessful even if it is delivered successfully to the SMSC.6 Mobile number portability solutions for MO-SM charging If Mobile Number Portability (MNP ) is used in the network. the SMS application ignores the release message from the MS and waits for the real result of the MO-SM. .20. B-IMSI number needs to be put into the SM-MO CDR. This flag is set ON when gsmSCF connection fails. . removes the battery from the MS (or in some mobiles. but the event is not cleared. Default SMS Handling parameter indicates what happened.20. 1. if. for example. pushes the 'red button') right after sending an MO-SM. If the parameter has a TRUE value. CAMEL SMS Modification indicates the parameters that CAMEL has modified. 100 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . 21 SMS-related statistics The following statistical reports and functions provide SMS-related statistical information: . the SMS application initiates SEND_IMSI operation with the B-MSISDN number to get the IMSI number of subscriber B through the SRRi towards the HLR. Note The functionality is implemented in MO_IWMSC. the SMS application (which runs in MO-IWMSC) has to initiate a SEND_IMSI MAP operation to retrieve the B-subscriber's IMSI number because of the MNP service. When MAP version 2 is in use between the network elements. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 101 (267) . B-IMSI is written into the SMMO_CDR as follows: 1. 2. 3. If the MO-SM is not application terminated SM.Short Message Services If you have Feature 1641: B-IMSI retrieval in MO side for MNP in use in your network. the received B-IMSI is written into the SMMO-CDR. For this. So double SEND_IMSI operations must be done in MO-IWMSC to gain both IMSIs for charging purposes. . 1. For more information. . see the feature description of Feature 1641: B-IMSI Retrieval in MO side for MNP. or MS to MS SM. When a SUBMIT MO-SM arrives to the IWMSC and the feature is active. When the response arrives from HLR. SMS application checks the SMS routing analysis to decide if the MO-SM is application terminated SM. SMS measurement service measurement MSC SMS observation report MAP measurement . then A-IMSI is not transferred from MO-VMSC to MO-IWMSC. you can charge differently the MO-SMs which are sent to home or to different networks. welcome MT-SMs are included in the MT-SM counters. Note The measurement of the Welcome SMs means the Welcome MO trigger SM count. You can check whether. Detailed information on statistics on SMS can be found in NSS Statistics .21. The measurements include welcome MT-SMs. GSM Phase 2+ Enhancements in use in your network. for example. for example.SMS Guide . a foreign PLMN's SMSC is frequently used by roaming subscribers or it is misused by their own subscribers. You can use this functionality if you have the SMSC connected through MAP (in the VMSC function). Reports (ASCII. you can use SMS measurement. There are statistical counters for the number of mobile-terminating short messages (including welcome MT-SMs) coming from a certain SMSC and for the number of MO-SMs going to a certain SMSC. However. and in NSS Statistics.25 and TCP/IP). Welcome MO-SMs are separately counted. or if you have the SMSC connected through SMRSE (both with X. For more information on welcome MO-SMs and welcome MT-SMs. This measurement counts the successful and unsuccessful MO-SMs and successful and unsuccessful MT-SMs according to SMSC address. because they are seen by SMSC as ordinary MT-SMs.1 SMS statistics in the MSC SMS measurement If you have Feature 1165: Short Message Services. see Welcome SM to the roamer . 1. SCP visits can be seen in INAP measurement as protocol level events. In the MT-SM unsuccessful cases it can be either temporary or permanent. for filtering the misuse of SMs by easily recognizing SMSCs frequently used by the subscribers. This can be used. Binary) . 102 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Rejected Calls Observation Report Traffica . SCP visit preventions are shown in IN service gapping measurement. In the latter case you can define the appropriate barring to avoid bulk short messages. The report can contain measurements for maximum 5 x 50 SMSC addresses. and XML reports can be either SMSC-GT-1 (logical SMSC address given by the subscriber) or SMSCGT-2 (physical SMSC address resulting from the SMS routing analysis) or both. If direct SM delivery fails. Note. IWMSC-MO (logical). The SMSC address appearing in the ASCII. MOBILE TERMINATING SHORT MESSAGES IN GMSC PHYSICAL SMSC SUCCESSFUL TEMP FAIL 945387587 22564 344 945853123 675 5 940020001 2567 78 MSC DELIVERED SM 21202 5222 PERM FAIL 23 1 0 3224 However. for example. if the parameter DIRECT_SM_STA_CHA_INFO is activated. that there is one exception: you cannot define measurement with MML commands for MO-SM with SMSC link addresses.25 address. VMSC-MT (physical). MSC DELIVERED SM. In case of the IWMSC the physical SMSC address means an IP (either IPv4 or IPv6) or an X. This means that if. TD MML command group. Furthermore. the predefined SMSC address (defined by the operator) can be seen in the MOVMSC/MT-VMSC. The 50th record indicates all the other SMSC addresses.Short Message Services The Real Time trigger functionality can be seen in the Field Reporting Service Measurement as TSMS Triggered SMS IWMSC. the SM is delivered to the SMSC and this SM is counted in the SMS measurement. In the MT-VMSC the SM is indicated as a normal MT-SM again. The successful and unsuccessful SM transactions can also be counted through links with IPv6 addresses. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 103 (267) . There are 50 SMSC addresses in each type of MSC (for VMSC-MO (logical). are also included in the SMS measurement report. In the GMSC the SMS measurement also shows the SM sent without the SMSC in a separate object. In the GMSC a new counter. You can define maximum five SMSC addresses in each type of MSC in the measurement with an MML command (see also Destination Object Lists. IP version 6 addresses. in the IWMSC part by the Logical SMSC address. The maximum number of SMSC addresses in a given type of MSC is 49. In normal cases the logical SMSC address is visible in the MO-VMSC/MTVMSC. IWMSC-MO (physical) and GMSC-MT (physical) cases). The facility is available only in the IWMSC. binary. shows the number of directly delivered SMs. which can be used for TCP/IP connection between the SMS-IWMSC and the SMSC. this SM can be seen in the SMS measurement as well. and Activating SMS measurement . see referential material NSS Statistics. the measurements of 44 other SMSC addresses is indicated separately in the reports depending on their actual use (giving altogether 49 SMSC addresses). Table 10.SMS Guide you define 5 SMSC addresses. the 50th record will add up the number of SMs of the remaining 51 SMSC addresses. If there are 100 SMSC addresses used in an hour. MSC Observation Report The MSC SMS observation report contains the following blocks: 104 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Additional information on XML reports can be found in the feature description of Feature 1258: XML File Format for Statistics . Clear codes involved in SMS measurement counter update Clear codes for permanently failed SMs 0x250 cd_t_a_not_sc_subscriber 0x300 cd_t_restrict_in_out_direction 0x301 cd_t_oper_restr_in_out_direct 0x312 cd_t_tele_serv_not_prov 0x313 cd_t_illegal_subscriber 0x314 cd_t_unidentified_subscriber 0x319 cd_t_illegal_subscriber_station 0x410 cd_t_gt_analysis_failed 0x509 cd_t_file_error 0x7FF cd_t_initialization_value 0x812 cd_t_map_failure 0xD04 cd_t_subs_sig_protocol_error 0xD11 cd_t_invalid_ie_content Clear codes for temporary failed SMs 0x5 cd_t_b_subscriber_busy 0x10 absent subscriber 0x12 cd_t_no_paging_response 0x304 cd_t_b_line_out_of_service 0x316 cd_t_memory_capacity_exceeded 0x405 cd_t_err_req_from_co_process 0x407 cd_t_err_answer_from_co_process 0x40C cd_t_map_congestion 0x603 cd_t_no_response_from_co_process 0x60B cd_t_overload_congestion 0x60E cd_t_unit_restarted 0x815 cd_t_ciphering_not_succeeded 0x810 cd_t_facility_not_supported 0x811 cd_t_network_failure 0x850 cd_t_sc_congestion For the activation and deactivation information of this measurement see the command descriptions of Measurement Handling. T2 command group. Please note. For more information on reports. Reports (ASCII) . that the counters for the successful SMs are updated for the clear code of 0x0. The following table lists the clear codes that are involved in updating the counter for temporary failed and permanently failed SMs. . Note This report is available only if you have Feature 593: GSM Phase 2 Trace in your network. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 105 (267) . . It contains valid information if the Radio System is GSM. . the line is not printed out at all. The radio system to/from where the subscriber sends/receives the SMS. This is due to the fact that the statistical program block only fills in the fields for which the required information is available at the moment the report is generated. RECEIVED SMSC ADDRESS: the logical SMSC address. ROUTING CATEGORY: stands for the routing category of the subscriber ROUTING CATEGORY+: stands for the additional routing category of the subscriber Two new fields for the Type Of Number (TON) of the called and dialled (address) number. CAMEL MODIFICATION: the called/calling number or the used SMSC address can be modified by the gsmSCF in case the gsmSCF has controlled SMS processing with CAP operations. These numbers can be alphanumeric. . It contains valid information if the Radio System is UMTS. certain report fields can be missing. The report contains the following new information: . . . it is indicated here. heading information (similar in all phase 2 trace reports) subscriber data information on the short messages . If the parameter of a specific report line does not have a value. CELL BAND: the band of the cell (GSM/DCS/WCDMA) RNC ID: shows the identifier of the Radio Network Controller. which is given by the subscriber in MO-SM. . . .Short Message Services . . . MCC and MNC are added to the cell identifier SMS reference number (MO-SM). BSC ID: shows the identifier of the Base Station Controller. If any of them is modified. Depending on the invoking event. Advanced Guide and NSS Statistics.. incoming service requests the percentage of service requests rejected because of overload control the number of rejected service requests . The field reports contain the following measurement data: . Reports (ASCII) . see NSS Statistics. MAP measurement MAP measurements provide information about SMS usage. or from the TRANSIT MSC..SHORT MESSAGE MT VMSC representing the VMSC .VMSC interface in MO-SM. The SMS-related subscriber facilities are the following: . T22. Service measurement Service measurement gives information on the usage of SMS. MO-SMs are further separated to show SMs coming from the VMSC .SMS Guide For more information. . These reports contain the following data: .SHORT MESSAGE MT GMSC representing the SMSC -SMSGMSC interface in MT-SM. See instructions and descriptions on NSS Statistics . Rejected calls observation report In the rejected calls observation report the services can be observed per computer unit. MT-SMs are further separated to show SMs handled in the VMSC or SMS-GMSC. See also referential material NSS Statistics. Reports (ASCII) . T21. T21.. SMS-IWMSC.MS interface in MT-SM.SHORT MESSAGE MO VMSC representing the MS. 106 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . . facility name usage times . The SMS service measurement includes field reports. . HLR measurement Field reports contain the following measurement data: .. Through Traffica.2 SMS statistics in the HLR Information on SMS statistics in the HLR can be obtained from HLR measurement and HLR observation report. Reports (ASCII) .ATTEMPTED REQUEST FOR SM ROUTING INFORMATION New SMS CFU counters are added to the basic services. See also referential material NSS Statistics. . dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 107 (267) .SHORT MESSAGE MO IWMSC representing the SMS-IWMSC SMSC interface in MO-SM. . 1.. the SM is sent form the VMSC the SM is forwarded the SM is sent from SMS-IWMSC or SMS-GMSC governed by parameter (if the VMSC is not in the same network) . T22. a detailed report is sent if the following conditions are met: .Short Message Services . . Traffica in SMS statistics Note This functionality is available only if you have Feature 939: MSC Support for Real Time Reporting in your network..21. For detailed information see the feature description of Feature 939: MSC Support for Real Time Reporting and Traffica product description. The new counters are visible only if the feature is active. T22.SHORT MESSAGE MO TRANSIT representing the SMS-IWMSC SMS-IWMSC interface in MO-SM. T21. Note that SMS-GMSC and SMS-IWMSC are functional roles that a single DX 200 MSC can fulfil. The HLR subscriber observation report contains the following blocks: . For detailed information refer to feature description of Feature 593: GSM Phase 2 Trace . HLR Observation. 108 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .22 Network elements involved in SMS The network elements involved in SMS are SME . 1. . . SGSN is also involved if the SM delivery takes place through the GPRS network. . See also referential section NSS Statistics. Note This report is available only if you have Feature 593: GSM Phase 2 Trace in your network. SMSGMSC . SMSC . heading information (similar in all phase 2 trace reports) subscriber data. the name of the service and the time) result of the operation that caused the report information on the use of short message services new routing category . SMS-IWMSC . and HLR . . . . ready for SM. VMSC . and alert service center. VLR .SMS Guide HLR observation report The HLR subscriber observation report shows the types of the HLR operations that have been carried out by the subscriber under observation. The HLR observation report is printed after the following events: SRI for SM. such as MSISDN or IMSI location update information information on the use of basic services information on the use of supplementary services (the type of action. and retaining the responsibility of the SM until a report has been received or the validity period set for it expires receiving a report from the PLMN receiving an SM from an MS returning a report to the PLMN for a previously received SM .2 SMSC The SMSC acts as: .22. the MSISDN of T11 can be used for T21 as well. An SME can send and receive SMs if: .Short Message Services 1. . . Thus a GSM PLMN needs to support the transfer of SMs between SMSCs and MSs.22. . Of all the SMEs. . . The MSISDN of T11 can be used for T22 as well. 1. There should also be empty storage space in the memory of either the mobile equipment or the SIM. in an MS or in an SMSC. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 109 (267) . For example. or one PLMN can have more than one SMSC. it has a display facility it is able to handle SM Transfer Protocol Data Units (TPDUs) the BSC supports SMS (proper BSSAP version) the MSCs and HLRs in the PLMN have SMS routing definitions . An MS can send SMs if the subscriber has subscription to the basic service T22.1 SME A Short Message Entity (SME) is a terminal that can receive and send SMs. submitting an SM to an MS. It stores and forwards SMs. SMS-MO/PP. a store and a forward point for SMs an interface to other systems a platform for applications . The SME can be located in a fixed network. The subscriber does not need a different MSISDN for this basic service. One SMSC can have a connection to more than one PLMN. An SMSC must be capable of: . only an MS can receive SMs if the subscriber has subscription to the basic service T21 (SMS-MT/PP). The SMSC is not part of the GSM PLMN. The SMSC has to recognise this special MO-SM from the VMSC. the SMSC receives a trigger message from the VMSC at the arrival of a new roamer. which contains the subscriber's MSISDN number.SMS Guide All SM services which a GSM operator sells to subscribers are implemented in the SMSC: the role of the GSM network in a nutshell is just to pass the SMs between the SMSC and the MS. The SMSC has to recognise this special MO-SM from the VMSC. which contains the subscriber's MSISDN number. and VMSC address. The request includes authentication. see Figure MO-Forward SMS procedure . 1. 1.22. This opens the way for a wide range of services to be offered to the mobile subscribers. ciphering. If the Welcome SM function is active in the MSC. The acknowledgement of the SMSC is transmitted back to the MS in CP DATA message. such as weather forecast service and stock market information service. The actions are defined in VLR and subscriber parameters. The MS sends the SM in CP DATA message and receives an acknowledgement in CP ACK message. The SMSC can be connected to any computer that has a specialised service. see Welcome SM to the roamer . The service subscription data consists of T21 basic service (MT-SMS) and T22 (MO-SMS).25 or MAP SS7 is also possible. SMRSE over X. These operations are exactly the same as in ordinary voice calls. IMSI. see Real Time Triggering . and Common MSISDN.3. The Message Waiting Indication consists of the Mobile Station Not Reachable Flag. IMEI checking and TMSI reallocation . the SMSC receives a trigger message from the VMSC at triggering detection. IMSI. For further information. and the MS acknowledges it in CP ACK.22. For further information. 110 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . LAC. If the Trigger SM function is active in the MSC.3 VMSC and VLR The VLR contains two different kinds of subscriber data: service subscription data and Message Waiting Indication.1 VMSC and VLR in MO-SM procedure VMSC and VLR provide the following properties in the MO-SM: A interface operations in VMSC and VLR (MO) MS starts the MO-SMS operation by sending a Common Service Request to the network. The SMRSE over the TCP/IP interface is supported between the MSC and SMSC. For detailed description. IMEI. Message Reference . for example. see A interface in SMS . it transfers the response to the VMSC. For more information. . plus the SM data. The MS can use this service to inform the SMSC that it is ready to receive messages that it could not receive earlier because it had no free memory. or the MS does not acknowledge it. see SMS procedures performed by MAP . dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 111 (267) . When the SMS-IWMSC receives a response for the SM from the SMSC. it transfers the SM to it.Destination (SMSC) Address . The reason for changing the RR connection can be a handover. If the SMS-IWMSC knows the SMSC. The ReadyForSM operation and MWD support Memory Capacity Available facility.Originating (A-subscriber) Address . If the VMSC and the SMS-IWMSC are physically in one MSC then the information is transferred internally and not on the MAP interface.Originating (A-subscriber) Address .User Data MAP VMSC SMS-IWMSC A-IF - Message Reference Originating (A-subscriber) Address Destination (SMSC) Address User Data SMRSE . The message contains different kinds of data.User Data MS SMSC Figure 39.Short Message Services CP DATA is retransmitted if the RR (Radio Resource) connection is changed. For background information. for example the addresses of subscriber A and the SMSC. MO-SMS request MAP interface operations The MO-SM is transmitted further from the VMSC in MOForwardSM operation. SMS Guide VMSC MAP SMS-IWMSC A-IF . interworking between subscriber-activated outgoing call barring service. Operator-determined barrings: barring of outgoing calls barring of outgoing inter-zonal calls barring of outgoing inter-zonal calls except those directed to the home PLMN country barring of outgoing international calls except those directed to the home PLMN country and barring of outgoing inter-zonal calls . MO-SMS successful case (positive response) VLR operations in SMS (MO) The VLR receives data from the HLR. The VLR parameters define what operations are performed for the subscriber during the set-up phase.Message Reference .User Data MS SMSC Figure 40.User Data SMRSE . Supplementary service barrings: barring of all outgoing calls barring of outgoing international calls barring of outgoing calls except those directed to the home country Please take the following restrictions into account: 112 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . The relevant barring categories are the following: . and the barrings set by you. that is.Message Reference . whether IMEI is authenticated or ciphered. that is. that contains information about barrings set by the subscriber. Subscribers who have not been provisioned the MO-SMS in that particular VLR area are not allowed to use the service. The SMSC can send diagnostic data in negative acknowledgements to the MS. Two MO-SMS requests are not allowed simultaneously. VMSC SMS-IWMSC A-IF . .User Data SMRSE . If the SMSC address is unknown or outgoing calls are barred.Cause (error code) .User Data MS SMSC Figure 41. the SM transfer to the SMSC is not possible.2 VMSC and VLR in MT-SM procedure VMSC and VLR provide the following properties in the MT-SM: dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 113 (267) . Special conditions . The MO-SMS is provisioned for every subscriber as a basic service. see Mobile-originating short message .Cause (error reason) . For related information. and the SMS request is denied in the MSC. a session between MSC and MS is not disconnected before the last message has been transferred.Short Message Services . and vice versa. The amount of data is at most the same as in MO-SMS.3.Message Reference . but if there are more messages from the same subscriber. MO-SMS unsuccessful case (negative response) The MO-SMS is allowed at the same time when an active call and/or MT-SMS and/or USSD or SS operation to the subscriber is taking place.Message Reference .Cause (error code) .User Data MAP . 1.22. . Next the MSC sends the SM in a CP DATA message and the MS acknowledges it in a CP ACK message. The acknowledgement of the MS is transmitted back to the MSC in the CP DATA message. The paging procedure includes authentication.Message Reference .Destination Address (B-subscriber) . ciphering.User Data SMSC MS Figure 42.SMS Guide A interface operations in VMSC and VLR (MT) The GSM system starts the A interface MT-SMS operation by paging the MS.Originating Address (SMSC) . See Figure MO-Forward SMS procedure and the figures below: More Message To Send Originating Address (SMSC) Destination Address (B-subscriber) User Data SMS-GMSC SMRSE MAP VMSC A-IF - Priority Request More Message To Send Message Reference Originating Address (SMSC) Destination Address (B-subscriber) User Data SGSN . and the MSC acknowledges it in the CP ACK. MT-SMS request 114 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . IMEI checking and TMSI reallocation . User Data SMSC .Message Reference SMSC MS Figure 43.User Data MS Figure 44.Cause (error type) .Cause (error type) .User Data MAP VMSC A-IF MAP SGSN A-IF .Message Reference A-IF . MT-SMS unsuccessful case (negative response) For background information see A interface in SMS .Message Reference . dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 115 (267) .Cause (error code) .Message Reference .Short Message Services SMS-GMSC SMRSE MAP VMSC A-IF MAP SGSN . MT-SMS successful case (positive response) SMS-GMSC SMRSE . Special conditions . 116 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . For further information. The MT-SMS is allowed when an active call and/or MO-SMS and/or USSD or SS-operation to the subscriber is taking place. For more information. and the connection is left open. queueing is needed. For more information on SMS procedures performed by MAP. see MT operation in VMSC . The MSC has a functionality which resends the MT-SM to the MS if a handover or a time-out takes place: if More-Messages-to-Send functionality is in use. for example. The MS is informed about this. except with call barrings. and the SMSC plus the SM data.SMS Guide MAP interface operations (MT) MT-SM is transmitted further from the SMS-GMSC in MTForwardSM operation. is not provided in the VMSC/VLR. If the SMSC has more messages to send. and they are served according to FIFO principle. . and make sure that the specified maximum queuing time will not be exceeded. the address of subscriber B. Calculations based on this information define how long the SM is expected to stay in the queue. that if the VMSC has a direct connection to the SMSC. see Mobile-terminating short message . The queue handling takes into account what kind of A interface connection is used (fast/slow). how long the queued SM is. the SMS-GMSC and the IWMSCfunctions as specified later on in this section are available in the SMSC. and vice versa. see troubleshooting instructions in Short Message Service troubleshooting . When queueing takes place. . Multiple messages during one A interface connection are possible. and how many SMs the queue contains. all incoming SMs are placed in a queue in the VMSC. For information on SMS resending and timer values. . the SMSC informs the MSC that the SMSC contains one or more SMs waiting to be delivered to the MS. or several SMSCs are sending SMs to the same subscriber. . The connection path between the SMSC and the MS is not closed when there are more than one SMs to the same subscriber. Note. Interworking with supplementary services. All SMs are transferred to the MS in the same connection between VMSC and MS. The mobile station not reachable flag is initialized in the VLR restart. The message contains different kinds of data. see SMS procedures performed by MAP . The amount of data is as long as the data in MO-SM at the most. the SMS-GMSC initiates ReportSM-DeliveryStatus operation towards the HLR. it uses the ReportSM-DeliveryStatus operation to set the MNRF /MNRG or MCEF flag. if the SMSC address received from the VMSC is unknown. The subscriber address. The SMS-GMSC is capable of receiving SMs from the SMSC and interrogating the HLR for routing and SMS information with SendRoutingInfoForSM operation. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 117 (267) .Short Message Services 1. see 3GPP TS 23. If the SMSC address received from the HLR is unknown. In case of an MO-SM. See Figure MT-SMS procedure .22.5 SMS-GMSC In the case of an MT-SM. In case of MAP interface. and to put the SMSC address to the MWD list of the subscriber.4 SMS-IWMSC In the case of an MO-SM. . Special conditions In case the absent subscriber error code is received from the HLR. Special conditions . the Alert-SC request is cancelled. the MSC that has direct SMSC connections is called Gateway MSC (SMS-GMSC). For more information. the function of the SMSIWMSC is implemented in the SMSC. 1. The SMSC can send diagnostic data in negative acknowledgements to the MS. is sent to the SMSC. information indicating whether the SMSC address is included in the MWD list or not. It also provides the Alert-SC function to inform the SMSC of subscribers who have become active and who have an MT-SM waiting to be delivered to them.22. the function of the SMS-GMSC is implemented in the SMSC.040. provided that the SMSC address was not previously included in the MWD list. The purpose of the SMS-IWMSC is to receive MO-SMs from within the PLMN. the MSC with a connection to an SMSC is called Interworking MSC (SMS-IWMSC). If the SMSC is connected through MAP interface. the SM delivery is rejected. and of transferring them from the VMSC to the SMSC. is also returned. The SM is stored in the SMSC. which is used for alerting when the subscriber becomes available. In case of an unsuccessful SM delivery attempt. If an error code indicating an absent or unidentified subscriber is received from the VMSC. The purpose of the SMS-GMSC is to transfer an MT-SM from the SMSC to an appropriate VMSC /SGSN . an SM with priority indication can be sent. Subscriber management functions provide the management of SMS: they allow the addition. the SMS-GMSC informs the HLR about a successful transfer. The implementation of SMS in the HLR can be divided into the storage of SMSrelated data in the HLR. but if there are more messages for the same subscriber. For SMS. deletion. SM services (mobile-terminating and mobile-originating are considered as separate services) subscriber-specific SMSC address lists for each subscriber for whom the SMS services have been allocated . see Managing SMS subscriber-specific data . There are three different kinds of procedure concerning the SM operation: 118 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .SMS Guide If a subscriber has MWD in HLR. the session between the SMSC and the MS is not disconnected before the last message is transferred. causing the HLR to return routing information. An MS can send diagnostic data in negative acknowledgements to the SMSC. the operations for the SMS service. If the SM transfer succeeds. it is possible to obtain routing information for an incoming SM.22. The HLR provides these functions together with MAP. The amount of data is as long as the data in the MT-SM at the most. SMS-related data in HLR The HLR provides two information elements for the SMS function that form an integral part of the HLR and its file system.6 HLR Both MO-SMS and MT-SMS are implemented as basic services in the HLR. and modification of subscribers' basic services. Two MT-SMS requests are not allowed simultaneously. This is indicated with the MoreMessagesToSend parameter in the MT-SM. 1. These are the following: . For detailed instructions. and the management of SMS functions. which in turn starts the Alert-SC operation. the HLR sends a positive acknowledgement. The HLR is also notified if a transfer succeeds when an MWD was set. When the HLR receives a ReportSMDeliveryStatus message. There is no inherent limit to the length of a subscriber's SMSC list. ReportSM-DeliveryStatus In the case of a non-deliverable SM. If the address already exists.Short Message Services 1. a negative acknowledgement is sent with the error code 'absent subscriber' to the SMSC. the SMS-GMSC informs the HLR. ReadyForSM When the subscriber has again become active. which stores the address of delivered SMSC for subsequent use. it sets the address of the SMSC into the MWD list and returns a positive acknowledgement to the element that requested it. and the subscribers' lists are implemented by relational indexing inside this common pool. In this case. the VLR sends this operation to the HLR. it means that the subscriber is unreachable and all inquiries about the SM routing are rejected. 3. HLR operations for SMS service The following MAP-level operations implemented in the HLR are supported: 1. 3. The only exception is the priority SM. The HLR provides the supplementary service support. When the MWD list contains SMSCs. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 119 (267) . routing an SM to a subscriber is attempted even if MWD contains addresses. 4. For the SMSC address lists only one address list space is provided. all SMS-related operations are rejected for that subscriber. If the SMS services (both MO/PP and MT/PP) are not defined for a subscriber as basic services. The incoming call barring supplementary services and also operator-determined barring can be used with the MT-SMS. 2. or has free memory capacity again. If no priority is used and the MWD contains addresses. SendRoutingInfoForSM This operation allows MT-SMs to be routed to mobile subscribers everywhere in the GSM networks using VMSC address. and the SM services are not available for him in the network. 2. and the SMSC address is stored in the MWD. InformServiceCentre This operation informs the SMSC which ISDN number is used for indicating that an MS can receive SMs. see Welcome SM to the roamer. which is a real time monitoring tool. SMS Forwarding functionality is implemented in the HLR. AlertServiceCentre When a subscriber has again become active. 1.22. . Service subscription data consists of the following two services: .7 Traffica The information about the Welcome SM is sent to Traffica. For statistics-related information on Traffica see Traffica in SMS Statistics .SMS Guide 5. For background information. The data in the HLR can be further divided into service subscription data and message waiting data. Message Waiting Data List (SMSC addresses) Mobile Station Not Reachable Flag (MNRF) Mobile Station Not Reachable for GRPS Flag (MNRG) Mobile Station Not Reachable Reason (MNRR) Mobile Station Memory Capacity Exceeded Flag . When the system attempts to send an SM to a subscriber. T21 basic service (MT-SMS) T22 basic service (MO-SMS) . . the HLR informs all SMSCs that have undeliverable SMs waiting for him. For more information. Message Waiting Indication consists of: . If the subscriber does not have the T21 basic service provisioned. 120 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . . the HLR rejects the operation. the HLR receives the routing inquiry for the SM. see SMS information elements . The E interface functions either as the MAP interface. if the MSC performs the tasks of the SMS-GMSC and VMSC. like C and D interfaces. simultaneously. .23 Interfaces between SMS network elements The interfaces and the network elements involved in SMS are introduced below: HLR MAP-D VLR MAP-C SMRSE MAP-E A-IF SMSC MAP-Gd SMS-GMSC MSC MAP Gr. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 121 (267) . . and MAP. or as an internal service interface in the DX 200 MSC. The C and D interfaces use common channel signalling protocols MTP. Network elements involved in SMS . The A interface uses common channel signalling protocols MTP .Short Message Services 1. and BSSAP . TCAP . SCCP . or the SMSIWMSC and VMSC. Gf SGSN Figure 45. SCCP. USSD and SMS are possible simultaneously. When there is no voice call active.47. and A interface operations in VMSC and VLR (MT) . . Each SDCCH or traffic channel is accompanied by a twoway SACCH. even during a call. Each SMSC can support either the TCP/IP or X. . SACCH If a voice call is active. see Feature 931: Short Message Service transfer over TCP/IP .SMS Guide . which means that messages can be sent and received even during a call. ACSE and SMRSE (Short Message Relay Service Element). For more information.25 interface.25 and TCP/IP connection. For more information. There is also a Nokia-specific TCP/IP interface for P interface. a Slow Associated Control Channel is used for short messaging.008 and 24. With SACCH the sending of the SM takes about three times longer than with SDCCH.25 connection. The SMRSE needs a reliable transport service to exchange messages. ROSE. USSD uses FACCH channel. When there is no active call. Both interface options can co-exist in the MSC site.23. when SMS uses SACCH.1 A interface in SMS Short Messaging uses only the following signalling channels: . 1.47. SDCCH A Stand Alone Dedicated Control Channel is a two-way signalling channel normally used for call establishment and location updates. SDCCH channels are used for short messages. The following OSI protocols are used in this interface: OSI-layers 4-6. see 3GPP TS 24. One traffic channel (TCH) can be combined into 8 SDCCHs.2 SMRSE in SMS The exchange of messages between the MSC and the SMSC is based on Short Message Relay Service Element (SMRSE) interface defined in Technical report 03. The SMRSE is specified in ETSI Specification 03. During a call. The P interface functions as the X. see A interface operations in VMSC and VLR (MO) . The transfer of USSD with FACCH is 5-7 times faster than SMS with SACCH. 1. There are two alternatives: X. For more information on the A interface. 122 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . USSD and SMS use the same SDCCH signalling channel.011.23. the X. In case of high capacity links. This means that a maximum of 256 of messages from one SMSC can be made at the same time in the network. IS-IS MSW PAD Transport layer CONS X. ES-IS. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 123 (267) .25 connection OSI application with X.Short Message Services X.25 packet level X. the number of simultaneous MS transfers (message reference) is limited to 255.25 data link level physical level SNDCF LLC CSMA/CD 802. In this method the user must create a definition in the SMS-IWMSC to link the SMSCISDN address to an OSI application.25 network Figure 46.25 connection is considered to be a safer way.25 connection: if the SMSC operator and the PLMN operator are the same.3 subnetwork X. and therefore more space is reserved (1000). The following figure describes the OSI protocol stack: Non OSI applications OSI applications FTAM ACSE VT CMISE ROSE SMRSE Presentation layer Transport service user CONS network service user Session layer Transport layer 0 Transport layer 4 CLNS ISO IP. this limitation can result in a bottleneck. OSI protocol stack In the technical report of the SMRSE. you can control the maximum value of message references towards SMSC (MO-SMS). It implements the functionality defined for SMRSE. There are also some Nokia-specific features. which have to be implemented. The following figure describe the protocol stack for SMS with TCP/IP.25 connection is quite heavy for transferring relatively simple data. the number of messages that can be handled simultaneously increases significantly. TCP/IP connection The full seven layered OSI stack of the X. there must be a way to restrict the traffic.SMS Guide If feature 619 is in use in your exchange. Because of the high capacity. Therefore. The purpose of TCP/IP is to provide a fast and efficient way of transferring SMs between MSCs and SMSCs. This prevents the SM transfer system from producing too high a load in the rest of the system. if Feature 931: Short Message Service Transfer over TCP/IP is in use in your network. TCP/IP reduces the amount of protocol layers and therefore the time needed for processing a message. 124 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . and therefore it unnecessarily loads the physical line transfer capacity and the processing capacity of the computer unit that controls the line. such as SMs. The interface improves the SM transfer capacity considerably. it can increase the performance of the transmission between the MSC and the Nokia SMSC conveying SM traffic. for example. The amount of the messages can be tuned up to the optimal for the system configuration used. additional parameters. Consequently. Altogether this feature provides all the tasks and features of the previous solution. but in a more efficient way. Protocol stack for SMS with TCP/IP Both IPv4 and IPv6 are supported. see Comparison of SMS functionalities in case of SMRSE over X. For related information.23. For a more detailed information refer to the feature descriptions of Feature 931: Short Message Service Transfer over TCP/IP . TCP/IP stack TCP MAP TCAP IP Link Layer 802.25 or TCP/IP and SS7 MAP SMSC .3 SCCP MTP TCP/IP Protocol Stack Ethernet SS7 Figure 47.3 MAP in SMS MAP is an interface that follows the GSM specification. See the figure below: dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 125 (267) . 1.Short Message Services SMS-IWMSC/GMSC SMSC SMRSE SMRSE SMS Appl. In the GPRS network the following MAP interfaces exist: . . 7 MAP TCAP TUP/ ISUP level 4 OSI layer 7 layer 6 layer 5 layer 4 BSSAP SCCP level 3 level 2 layer 3 layer 2 MTP level 1 layer 1 Figure 48. C interface between MSC and HLR D interface between VLR and HLR E interface between MSC and MSC F interface between MSC and EIR G interface between VLR and VLR . 126 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . MAP-Gd: between MSC and SGSN MAP-Gr: between SGSN and HLR MAP-Gf: between SGSN and HLR . . OSI compared to ITU-T No. . 7 MAP covers the following interfaces in the GSM network: .SMS Guide ITU-T Nr. . B interface between MSC and VLR is not described in these descriptions of Short Message Services. MAP-Gd MAP-Gd is the interface between the MSC and the Serving GPRS Support Node (SGSN).25 connection. . The alternative to OSI for implementing SMSC and SMS-GMSC or SMSIWMSC connection is the MAP interface with CCS7 link. .Short Message Services MAP provides the following SMS procedures for its users: . Routing definitions are easier than with the X. The SMS-related MAP version 3 makes the usage of Feature 857: Support of General Packet Radio Service (GPRS ) possible. Every MSC and HLR can send SMs directly to the SMSC. One MAP procedure can be executed during one TCAP dialogue. . In this case the SMSC is integrated to the CCS7 network. . For more information refer to feature descriptions of Feature 1043: Short Message Services GSM Phase 2+ and Feature 857: Support of General Packet Radio Service (GPRS) . and the functionalities of SMS-GMSC and SMS-IWMSC are combined to the SMSC. MAP version 3 is supported if you have Feature 1043: Short Message Services GSM Phase 2+ in the network. . dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 127 (267) . The following figure shows the SMS architecture with SGSN. See SMS procedures performed by MAP for detailed explanations of the procedures. . MOForwardSM: between VMSC and SMS-IWMSC or between VMSC and SMSC MTForwardSM: between SMS-GMSC and VMSC or between SMSC and VMSC SendRoutingInfoForSM: between SMS-GMSC and HLR or between SMSC and HLR ReportSM-DeliveryStatus: between SMS-GMSC and HLR or between SMSC and HLR InformServiceCentre: between HLR and SMS-GMSC or between HLR and SMSC ReadyForSM: between VLR and HLR AlertServiceCentre: between HLR and SMS-GMSC or between HLR and SMSC SendIMSI: between SMS-IWMSC and HLR or between SMSC and HLR . as well as receive them directly from there. This MAP version includes the parameters necessary for SMS over GPRS . MAP-Gd interface in the SMS GSM Phase 2+ network architecture For related information. the latter notification only means that the SM was successfully sent to the SMSC. 1. see Command SM and MO-SM with Status Report request . However. A status report informs the subscriber of the status of the MO-SM that was sent. Whether the SM delivery was successful or not is indicated in a status report . Its status can be either successful.24 Subscriber interface of SMS SMS status report The subscribers receive a notification when there are one or more SMs delivered to them. 128 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . for example.25 or TCP/IP and SS7 MAP SMSC . the SM was delivered successfully to the MS. such as fax. see SMS procedures performed by MAP . and Comparison of the SMS functionalities in case of SMRSE over X.SMS Guide HLR MAP-E MSC A-IF MAP-C BSS SMS-GMSC SMSC SMRSE Short message service centre MAP-Gd Gb SGSN Figure 49. that is. a notification that a message has been sent. or unsuccessful. and when they send a message. For background information. but the subscribers can also set it themselves when they are using other than the usual kind of SMs. Short Message Service on GPRS . Usually the SMSC address is stored in the MS. nothing about a future delivery. This can be useful in cases when. The alphabetical address is carried in the MO-SM. if they bar all incoming and/or outgoing calls. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 129 (267) . thus. represented as below: MSB 1 0 0 1 0 1 0 "4" "A" LSB Figure 50. the character 'J' is represented as 0x4A (01001010 in binary format). SIM data download becomes possible. for example. Alphanumeric addressing of SMS-related applications The subscriber has the benefit of easy addressing of SMS-related applications as this feature supports alphanumeric addresses for the destinations of short messages. they. or both. The upper 4 bits (from the most significant bit (MSB)) contains the first digit of the hexadecimal number and the below 4 bits (from the least significant bit (LSB)) contains the second digit thereof. For example.Short Message Services Prevention of SMS If the subscribers want to bar incoming or outgoing SMs or both. see Barring SMS in the MSC . the address in hexadecimal format is 4A 4F 4B 45 42 4F 58 (see below). in general. this automatically means that SMs are also barred. An example for hexadecimal numbers used in alphanumeric addressing Accordingly. User Data in MT/MO-SMS acknowledgement message Since the UserData in the acknowledgement messages is available. They can bar all incoming/ outgoing SMs if the menu of their MS supports it. if the subscriber sends a short message to the address 'JOKEBOX'. the user has a prepaid SIM card because the data download is possible by the SMS. Likewise. must bar all incoming or outgoing calls. For background information. The characters are represented by a hexadecimal number in an 7bit octet. Our example (the letter 'J') can be. .... An example for alphanumeric addressing from the MS 130 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .SMS Guide short message 4A 4F 4B 45 42 4F 58 ............-- MS Figure 51... and the connection between the SMSIWMSC/SMS-GMSC and the SMSC. see the Feature descriptions of Feature 327: Short Message Services and SMSC Guide to Commissioning for HP 9000/700 and 9000/800 and the instructions on OSI. MS BSS A VMSC E SMSGMSC P SMSC B VLR In the examples below the network element addresses are: VMSC address: 4434050 VLR address: 4434051 IWMSC address: 443406 SMSC address: 44340600001 Figure 52. For more information. the creation of Global Title analyses. the SMSC address analysis. MO-SM interfaces dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 131 (267) .Configuring network elements for SMS 2 Configuring network elements for SMS The SMS-PP is available for use after the SW installation. The interfaces and the network elements involved in SMS-PP are shown in the following figures. see Parameters for SMS A-interface configuration . 2. see Short Message Services Overview.SMS Guide MS BSS A VMSC E SMSGMSC C P SMSC B D VLR HLR In the examples below the network element addresses are: HLR address: 443404 VMSC address: 4434050 VLR address: 4434051 GMSC address: 443406 SMSC address: 44340600001 The relevant signalling point codes are: HLR SPC: 340 VMSC SCP: 342 SMS-IWMSC SCP: 341 SMS-GMSC SCP: 341 Figure 53. 132 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . MT-SM interfaces For related information. For the whole topic summary.1 Configuring MAP interface for SMS The MAP configuration contains global title analyses used by the Short Message Service. the SMSC address of the SMSC is 44340600001. ZNBC:::<digits>:<result record index>. Thus. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 133 (267) . NA1. You are recommended to use route on global title (RI=GT) if there are any SCCP gateway node points between the origin and destination point. The default is all networks. ZNET:<signalling network>.RI=GT. 2. Create global title translation result and global title analysis (NAC. IN0. To interrogate the translation results. for the SMS-GMSC address (443406).Configuring network elements for SMS You can find detailed information on MAP in MAP in SMS . and the address of the SMS-GMSC is 443406.1. Create global title analysis. so check their existence first and create only the ones that are missing. It is enough to route the SM to the SMSC because the beginning of the SMSC address is the same. Use the benefits offered by network topology. NBC) Create global title translation result. ZNAC:NET=<primary network>. You can only use an existing network. IN1). if possible. where <signalling network> is the symbolic name of the signalling network which the signalling point belongs to. Steps 1. you need to create a global title analysis. if one does not already exist.DPC=<primary destination point code>. Before you start Some of these global title analyses can already exist. use the following command: ZNAI:.1 Creating global title analysis Before you start Find out what network is in use (NA0. In the examples presented in this section. as shown in the figure below: SMS-GMSC/ GT-analyses: 443405 SMS-IWMSC Result record: 2 VMSC VMSC address: 4434050 Figure 55.SMS Guide 2.164 VMSC number in the SMSGMSC/SMS-IWMSC (NAC. the result is the HLR a.RI=GT. Here the value of <destination point code> is the HLR SPC.DPC=340.RI=GT.DPC=342. Create global title analyses for the E. GT analyses in the SMS-GMSC/SMS-IWMSC. Create a global title analysis. NBC) The result is the VMSC. ZNAC:NET=NA0. b. Create global title analyses for the E. the result is the VMSC a. GT analyses in the SMS-GMSC. Here the value of <digits> is the MSISDN number of subscriber B (the first five digits). ZNBC:::443404:1. 134 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . b. as shown in the figure below: SMS. Here the value of <destination point code> is the VMSC SPC. Create a global title translation result. ZNAC:NET=NA0.GT-analyses: 443404 GMSC Result record: 1 HLR HLR address: 443404 Figure 54. 3.164 MSISDN number in the SMS-GMSC (NAC. Create a global title translation result. Create a global title analysis. NBC) The result is the HLR. Here the value of <signalling point code> is the VMSC SPC.164 SMSC address in the VMSC (NAC. GT-analyses: 443406 VMSC Result record: 3 SMSIWMSC SMSC SMS-IWMSC address: 443406 SMSC address: 44340600001 Figure 56.164 SMSC address in the SMSIWMSC (NAC. so check whether you need to create this analysis or whether it already exists. the result is the SMS-IWMSC dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 135 (267) . Create global title analysis for E. b. ZNBC:::443406:3.RI=GT. GT analyses in the VMSC.Configuring network elements for SMS ZNBC:::443405:2. Create global title analyses for the E. ZNAC:NET=NA0. Create a global title translation result. Here the value of <digits> parameter is the SMSC ISDN number. NBC) The result is the SMS-IWMSC. The start of the SMSC address can be the same as the SMS-IWMSC address. the result is SMS-IWMSC a. GT analyses in the SMS-IWMSC. See the figure below: GT-analyses: 443406 VMSC Result record: 3 SMSIWMSC SMSC SMS-IWMSC address: 443406 SMSC address: 44340600001 Figure 57. 5.DPC=342. Create a global title analysis. NBC) The result is the SMS-IWMSC. 4. See the figure below. SMS Guide a. Create a global title translation result. Here the value of <signalling point code> is the SMS-IWMSC SPC. ZNAC:NET=NA0,DPC=341,RI=GT; Create a global title analysis. Here the value of <digits> parameter is the SMSC ISDN number. ZNBC:::443406:3; b. 6. Create global title analyses for the E.164 SMS-GMSC number in the SMS-GMSC (NAC, NBC) The result is the SMS-GMSC. See the figure below: HLR GT-analyses: 443406000001 Result record: 3 SMSIWMSC SMSC SMS-IWMSC address: 443406 Figure 58. GT analyses in the SMS-GMSC, the result is the SMS-GMSC a. Create a global title translation result. Here the value of <signalling point code> is the SMS-GMSC SPC. ZNAC:NET=NA0,DPC=341,RI=GT; Create a global title analysis. Here the value of <digits> is the SMS-GMSC ISDN number. ZNBC:::443406:3; b. Note Due to the configuration we are using, this analysis is the same as the previous analysis. 7. Create global title analysis for E.164 SMSC number in the HLR (NAC, NBC) The result is the SMS-IWMSC. 136 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en Configuring network elements for SMS a. Create a global title translation result. Here the <destination point code> is the HLR SPC. ZNAC:NET=NA0,DPC=340,RI=GT; Create a global title analysis. Here the value of <digits> is the SMSC ISDN number. ZNBC:::443406:3; b. 8. Create global title analyses for the E.164 HLR number in the HLR (NAC, NBC) The result is the HLR. See the figure below: GT-analyses: 443404 Result record: 1 HLR SMS-GMSC/ SMS-IWMSC HLR address: 443404 Figure 59. GT analyses in the HLR, the result is the HLR a. Create a global title translation result. Here the <destination point code> is the HLR SPC. ZNAC:NET=NA0,DPC=340,RI=GT; Create a global title analysis. Here the value of <digits> is the HLR ISDN number. ZNBC:::443404:1; b. 9. Create global title analyses for the E.164 VMSC number in the VMSC (NAC, NBC) The result is the VMSC. See the figure below: dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 137 (267) SMS Guide SMS-GMSC/ SMS-IWMSC GT-analyses: 443405 Result record: 2 VMSC VMSC address: 4434050 Figure 60. GT analyses in the VMSC, the result is the VMSC a. Create a global title translation result. Here the value of <destination point code> is the HLR SPC. ZNAC:NET=NA0,DPC=342,RI=GT; Create a global title analysis. Here the value of <digits> is the HLR ISDN number. ZNBC:::443405:2; b. Further information: Note It is very important to check that there is no loop between the global title analyses you created. 2.2 Configuring X.25 interface for SMS Configuring the X.25 connection consists of three parts: 2.2.1 Connecting the SMSC to the SMS-GMSC/SMS-IWMSC Before you start: Check the parameter set Note that the consistency of the parameter set has to be checked so that both the SMSC and the MSC have similar settings. The basic settings that are changed are: L3UDS, L3WIN, L3HTC, and L3LTC. 138 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en Configuring network elements for SMS L3UDS tells the length of the user data, and L3WIN the window size. L3LTC is the lowest and L3HTC is the highest traffic channel used. If the X.25 connection from the SMSC to the MSC does not work, check the value of the highest traffic channel in the MSC. The DTE entity creates the connection with the highest, and the DCE entity with the lowest traffic channel defined. Therefore, make sure that these values are the same in the SMSC and the MSC. Use command ZQXI; for checking the parameter set. Steps 1. Create a parameter set (QXC) ZQXC:<parameter set name>:; where <parameter set name> is the identifier of the parameter set with 1 - 8 characters. 2. Modify a parameter set (QXM) ZQXM:<parameter set name>:<changed parameters>; 3. Set the physical level characteristics for an analogue interface (QTC) These characteristics are set for a unit which has an interface with the SMS. Repeat the command for each interface. For more detailed information, see instructions on OSI management and SMSC Guide to Commissioning for HP 9000/700 and 9000/800. ZQTC:BDCU,<unit index>:<plugin unit type>,<plugin unit index>: <interface type>, <bit rate>; To find out the unit index, use the command ZUSI:BDCU; To find out the analog terminal index, use the command ZWTI:P:BDCU; or ZQTI; dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 139 (267) SMS Guide 4. Create a physical channel (QCS) Repeat the command for each channel. ZQCS::BDCU,<unit index>,<terminal number>:: <terminal mode>,<X.25 parameter set>; To find out the unit index, use the command ZUSI:BDCU; To find out the analog terminal index, use the command ZWTI:P:BDCU; or ZQTI; 5. Unlock the physical channel (QSC) Repeat the command for each channel. ZQSC:<physical channel numbers>,UNL; where <physical channel numbers> identifies the physical channel(s). Characters & and && are allowed. To find out the number, use the QSI command (address number). 6. Create a channel group (QGC) Repeat the command for each channel group. The channel group includes all channels to the group. ZQGC:<physical channel group name>:<physical channel number>,,<physical channel priority>; 7. Create the NSAPs (QBN) ZQBN:<NSAP number>:<NSAP role>:<NSAP type>: DTE=<DTE number>,SPI=<subsequent protocol identifier>,CHG=<X.25 channel group name>; Note that CHG is used only for creating remote NSAPs. 140 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en a. Unlock the NSAP addresses (QBG) ZQBG:<NSAP number>. Set the OSI access control method (QQM.<state change>. Create an application to the first CCSU unit only. If you use the value L (use access control list). Create a local application. <unit index>:<application type>:<network address name>:<P-selector>:<S-selector>:<Tselector>. ZQDL:<AE name>:::<state change>:<unit type>. 11.Configuring network elements for SMS To find out the C number. use the QNI command: ZQNI. ZQQM:<access control method>. 8. QQC) There are two alternatives in the MSC for allowing connection requests from outside: either all incoming calls are allowed. Create OSI applications (QDL. add SNPA to OSI access control list. 10. Attach the NSAP addresses of the interfaces to this network address. or only the calls whose addresses are defined as allowed ones. b. QDR) You can create local or remote application. Create network addresses to connect application to the relevant interface (QBC) Create network addresses to connect application to the interface which it is going to use. 9. that is. a process that uses OSI services. 12. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 141 (267) . ZQBC:<network address name>:<network address role>. Create a remote OSI application ZQDR:<AE name>:::<state change>:<application type>:<network address name>. Attach NSAPs (QBT) ZQBT:<network address name>:<NSAP number>. Further information: If the creation of a physical channel fails. a. ZWTI:P:BDCU. Example 1. where <SNPA address> is the remote SMSC DTE address. Especially wrong memory addresses in plug-unit equipping can cause error situations. An example printout: CREATED X25 CONFIGURATION PARAMETER SET DATA PARAMETER SET NAME: SMSCSET ================== MAXIMUM NETWORK SERVICE DATA UNIT LENGTH: 2048 BYTES L2 CONNECTION MODE: INITIATED AFTER START UP LEVEL 2 PARAMETERS: -----------------L2 TIMER T1: 6 SECONDS L2 BITS IN FRAME: 1024 BITS L2 TIMER T2: NOT IN USE L2 RETRY COUNT: 10 TIMES L2 TIMER T3: NOT IN USE L2 WINDOW: 7 FRAMES L2 INTERFRAME FILL: 01111110 L2 LINE DOWN TIMER: 20 (NOT SUPPORTED) LEVEL 3 PARAMETERS: -----------------L3 USER DATA SIZE: 128 BYTES L3 SEND WINDOW SIZE: 2 FRAMES L3 MODULO: 8 L3 TIMER T20: 180 SECONDS L3 TIMER T21: 200 SECONDS L3 TIMER T22: 180 SECONDS L3 RESET RETRY COUNT: 5 TIMES L3 TIMER T23: 180 SECONDS L3 CLEAR RETRY COUNT: 5 TIMES L3 FIRST PVC: 0 (= NOT IN USE) L3 LAST PVC: 0 (= NOT IN USE) L3 LIC: 0 (NOT SUPPORTED) L3 HIC: 0 (NOT SUPPORTED) L3 LTC: 0 (= NOT IN USE) L3 HTC: 0 (= NOT IN USE) L3 LOC: 0 (NOT SUPPORTED) L3 HOC: 0 (NOT SUPPORTED) USER FACILITIES: --------------- 142 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .SMS Guide ZQQC:<SNPA address>. Check the parameter set ZQXI. Connecting the SMSC to the SMS-GMSC/SMS-IWMSC 1. Create a parameter set ZQXC:SMSCSET:. check the equipping of the plug-in units with following command. Configuring network elements for SMS NO USER FACILITIES COMMAND EXECUTED b. Modify a parameter set ZQXM:SMSCSET:L3UDS=1024. L3LTC=1.L3HTC=2.L3WIN=7.. An example printout: OLD X25 CONFIGURATION PARAMETER SET DATA PARAMETER SET NAME: SMSCSET ================== MAXIMUM NETWORK SERVICE DATA UNIT LENGTH: 2048 BYTES L2 CONNECTION MODE: INITIATED AFTER START UP LEVEL 2 PARAMETERS: -----------------L2 TIMER T1: 6 SECONDS L2 BITS IN FRAME: 1024 BITS L2 TIMER T2: NOT IN USE L2 RETRY COUNT: 10 TIMES L2 TIMER T3: NOT IN USE L2 WINDOW: 7 FRAMES L2 INTERFRAME FILL: 01111110 L2 LINE DOWN TIMER: 20 (NOT SUPPORTED) LEVEL 3 PARAMETERS: -----------------L3 USER DATA SIZE: 128 BYTES L3 SEND WINDOW SIZE: 2 FRAMES L3 MODULO: 8 L3 TIMER T20: 180 SECONDS L3 TIMER T21: 200 SECONDS L3 TIMER T22: 180 SECONDS L3 RESET RETRY COUNT: 5 TIMES L3 TIMER T23: 180 SECONDS L3 CLEAR RETRY COUNT: 5 TIMES L3 FIRST PVC: 0 (= NOT IN USE) L3 LAST PVC: 0 (= NOT IN USE) L3 LIC: 0 (NOT SUPPORTED) L3 HIC: 0 (NOT SUPPORTED) L3 LTC: 0 (= NOT IN USE) L3 HTC: 0 (= NOT IN USE) L3 LOC: 0 (NOT SUPPORTED) L3 HOC: 0 (NOT SUPPORTED) USER FACILITIES: --------------NO USER FACILITIES NEW X25 CONFIGURATION PARAMETER SET DATA PARAMETER SET NAME: SMSCSET ================== MAXIMUM NETWORK SERVICE DATA UNIT LENGTH: 2048 BYTES L2 CONNECTION MODE: INITIATED AFTER START UP LEVEL 2 PARAMETERS: -----------------L2 TIMER T1: 6 SECONDS L2 BITS IN FRAME: 8192 BITS L2 TIMER T2: NOT IN USE L2 RETRY COUNT: 10 TIMES L2 TIMER T3: NOT IN USE L2 WINDOW: 7 FRAMES L2 INTERFRAME FILL: 01111110 L2 LINE DOWN TIMER: 20 (NOT SUPPORTED) LEVEL 3 PARAMETERS: -----------------L3 USER DATA SIZE: 1024 BYTES L3 SEND WINDOW SIZE: 7 FRAMES L3 MODULO: 8 L3 TIMER T20: 180 SECONDS L3 TIMER T21: 200 SECONDS L3 TIMER T22: 180 SECONDS L3 RESET RETRY COUNT: 5 TIMES L3 TIMER T23: 180 SECONDS L3 CLEAR RETRY COUNT: 5 TIMES dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 143 (267) . These characteristics are set for a unit which has an interface with the SMS.-----.0. ZQSC:1.---------------.------------. Set the physical level characteristics for an analog interface.0:AC25S.SMS Guide L3 FIRST PVC: 0 (= NOT IN USE) L3 LAST PVC: 0 (= NOT IN USE) L3 LIC: 0 (NOT SUPPORTED) L3 HIC: 0 (NOT SUPPORTED) L3 LTC: 1 L3 HTC: 2 L3 LOC: 0 (NOT SUPPORTED) L3 HOC: 0 (NOT SUPPORTED) USER FACILITIES: --------------NO USER FACILITIES COMMAND EXECUTED 2. ZQTC:BDCU.35 61440 COMMAND EXECUTED CREATING ANALOG TERMINAL DATA PIU PIU INTERFACE BIT PHYS UNIT TYPE INDEX TYPE RATE CHAN NB ---------. ZQCS::BDCU.--------. An example printout: CREATED PHYSICAL CHANNEL DATA SNPA DTE/ X.1:V35. Unlock the physical channel.SMSCSET:. An example printout: CHANGING PHYSICAL CHANNEL STATE CHANNEL OLD STATE NEW STATE INFO ------.21 153600 COMMAND EXECUTED 3. Create a physical channel.------BDCU-0 AC25-S 1 V.--------.---.61440:.------------.---.---1 LOC-ENA UNL-ENA COMMAND EXECUTED 144 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Repeat the command for each channel.-----.--------1 SNPA NOT IN USE IGNO BDCU-0 1 DCE SMSCSET V.--------.--------.25 PHYS DATA RATE CHANNEL SNPA-ADDRESS INTP UNIT TERM DCE PARAM SET LEVEL BITS/S ------.-----.-------. Repeat the command for each interface.UNL.---. Repeat the command for each channel. Example printouts: CREATING ANALOG TERMINAL DATA PIU PIU INTERFACE BIT PHYS UNIT TYPE INDEX TYPE RATE CHAN NB ---------.------BDCU-0 AC25-S 1 X.--------.35 61440 COMMAND EXECUTED 4.1::DCE. -------.25 NETWORK PROTOCOL ADDRESS INFORMATION NBR ROLE STATE CHG DTE SPI ----.-------1 REMOTE LOC-DIS SMSCG1 450530 03010100 COMMAND EXECUTED 7. or ZQBN::R:1:DTE=450530.--------------. Example printouts for the commands: CREATED NSAP X.-----SMSCLNET LOCAL COMMAND EXECUTED CREATED NETWORK ADDRESS dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 145 (267) . Repeat the command for each channel group. Create a channel group. The channel group includes all channels to the SMSCG1. ZQGC:SMSCG1:0.. Create the NSAPs ZQBN::L:1:DTE=37926.--------------.-------.SPI=03010100.50.------. Create network addresses to connect application to the interface which it is going to use. An example printout: CREATED PHYSICAL CHANNEL GROUP DATA VC CHAN CHAN GROUP ID CHAN NUMBER PRIO STATE -------.37926 03010100 COMMAND EXECUTED CREATED NSAP X. Example printouts: CREATED NETWORK ADDRESS NET ADDR ROLE -------. Attach the NSAP address of the interface to this network address.-----..-----. or ZQBC:SMSCRNET:R:. ZQBC:SMSCLNET:L:.SPI=03010100.-------1 LOCAL LOC-DIS .------.CHG=SMSCG1.-------------------------SMSCG1 0 0 50 UNL-ENA COMMAND EXECUTED 6.25 NETWORK PROTOCOL ADDRESS INFORMATION NBR ROLE STATE CHG DTE SPI ----.Configuring network elements for SMS 5. ---SMSCRNET REMOTE 2 50 COMMAND EXECUTED 9.------.-----SMSCRNET REMOTE COMMAND EXECUTED 8.---------.--------. An example printout: CREATED OSI APPLICATION AE-NAME APPL NET ADDR STATE UNIT FAM ID PROC ID ---------------. ZQDL:SMHPRB:::UNL:CCSU.------. that is.UNL.SMS Guide NET ADDR ROLE -------.------. Example printouts for the commands: TTACHED NSAP NET ADDR ROLE NSAP NR PRIO -------.-----. a process that uses OSI services.---SMSCLNET LOCAL 1 COMMAND EXECUTED ATTACHED NSAP NET ADDR ROLE NSAP NR PRIO -------.--------1 LOC-DIS UNL-ENA 2 LOC-DIS UNL-ENA COMMAND EXECUTED 10.-----.-------. or ZQBT:SMSCRNET:2:. Create OSI applications a.-----. An example printout: CHANGING NSAP STATE NBR OLD STATE NEW STATE ----. Create a local application.------SMHPRB SMS SMSCLNET UNL-ENA CCSU AP_TYPE : NOT IN USE 146 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .0:SMS: SMSCLNET:03:03:03:. Unlock the NSAP addresses ZQBG:.------. Attach NSAPs ZQBT:SMSCLNET:1:. Create an application to the first CCSU unit only. -------.-----. allow all incoming calls and allow incoming calls only from the SMSC. Set the OSI access control method. Allow incoming calls only from the SMSC ZQQM:L. Examples of both are presented below. An example printout: MODIFYING OSI ACCESS CONTROL METHOD OLD METHOD NEW METHOD --------------------------------------------------ALL INCOMING CALLS DENIED ALL INCOMING CALLS ALLOWED COMMAND EXECUTED b. a. Create a remote OSI application ZQDR:REMSMSC:::UNL:SMS:SMSCRNET:. Allow all incoming calls ZQQM:A. An example printout: CREATED OSI APPLICATION AE-NAME APPL NET ADDR STATE ---------------. There are two alternatives.------REMSMSC SMS SMSCRNET UNL-ENA AP_TYPE : NOT IN USE AP_TITLE : AEQ : P-SELECTOR: S-SELECTOR: T-SELECTOR: COMMAND EXECUTED 11. An example printout: MODIFYING OSI ACCESS CONTROL METHOD OLD METHOD NEW METHOD --------------------------------------------------ALL INCOMING CALLS DENIED ACCESS CONTROL LIST IN USE COMMAND EXECUTED dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 147 (267) .Configuring network elements for SMS AP_TITLE : AEQ : P-SELECTOR: 03 S-SELECTOR: 03 T-SELECTOR: 03 COMMAND EXECUTED b. Create an SMS routing analysis (CFE) ZCFE:PID=<protocol identifier>. Create SMS routing support analysis (CFU) You can create a SMS routing support analysis for defining the case when SMS routing analysis is started.2. 148 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .<result type>:<SMSC level>: <operation>:<application entity name>.TC=<tariff class>. 2. Note This step is optional and is necessary only if you want to route the subscriber's SMS request to the service application in the desired SMSC or if you want to create different tariff classes for MO-SMs.2 Creating analysis on SMS application level in the MSC Steps 1. for the available conditions see SMS routing analysis . If you do not have feature 1165.SAN=<service application name>. Note You can execute this command only if you have Feature 1165: Short Message Services GSM Phase 2+ Enhancements in use in your network.SMS Guide 2. 3. ZCFU:SMSC=<smsc address>.SAPTYPE=<service application prefix type><option>:SMSC=<short message service centre address>. Create an SMSC address analysis (CFS) ZCFS:<SMSC address>.SAP=<service application prefix>. By giving multiple X.25 connections (applications entity names) you can enable load sharing in your system. Preconfigure the SMSC address. e. Find out the UTPFIL and its number running in the CCSU / GSU (WQV. Creating an analysis for the SMSC address in the SMS- dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 149 (267) .<application entity name5>. If the variant part (the last 4 digits) is 0000. f. a. DFL) ZWQV:CCSU:UTP%.<result type>:<SMSC level>:ADD: <application entity name1>. 20000 can be given as 2. Restart every CCSU unit one by one d. see Working examples for SMS management .Configuring network elements for SMS For more information. Add the SMSC address into UTPFIL records ZDFS:CM. Note This step is necessary only if you do not have Feature 1165: Short Message Services GSM Phase 2+ Enhancements in use in your network. For more information. given as a hexadecimal.<application entity name2>. you have to add the address to the UTPFIL. ZDFL:CCSU.x:<file number>.x:<file number>. 4. c. Add the SMSC address into UTPFIL records Make sure that you do the changes in every CCSU. For example.<application entity name3>. it can be omitted. Find the CM in WO-EX state ZUSI:CM.<record number>. Further information: Example 2.0:NAME= <UTPFIL name>.<application entity name4>. if necessary If you want to use always the same SMSC address towards the MS. ZCFS:<SMSC address>. see SMS load sharing . where x means the active CM. Find out three free records in UTPFIL (DFD) ZDFD:CM. <file number> is the number for the UTPFIL. b. x:. b.SMS Guide IWMSC 1.x:5AC0007. where x is the active CM.SAP=N:SMSC=222.. ZDFS:CM. Create an SMS routing analysis ZCFE:PID=53.. where x is the active CM. 4. that for compact MSCi the UTPFIL number is 5AC01017. Find out three free records in UTPFIL ZDFD:CM.y+1. Add the SMSC address (44340600001) into UTPFIL records. where x is the active CM and y+2 is the record to be patched. In this example the records in the UTPFIL should look like this after the commands: 9D 01 25 00 07 91 44 43 9D 01 26 00 91 F0 FF FF 9D 01 27 00 60 00 00 10 c.SMSC03. 3. ZCFS:44340600001. Create an SMSC address analysis ZCFS:44340600001. The changes are made in every CCSU. Note Note. ZDFS:CM..AEN:LEVEL=S1: ADD:SMSC01.. and y is the record to be patched. Preconfigure the SMSC address a.x:. Restart every CCSU unit one by one 150 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .. where x is the active CM and y+1 is the record to be patched.AEN:LEVEL=S1:ADD:REMSMSC. 2. ZDFS:CM.x:..SMSC02... Create SMS routing support analysis ZCFU:SMSC=223..y.y+2.SAN=E-MAIL. . see MAP in SMS especially MAP version 3. Check the SMS-related application context-specific MAP versions ZOPH:INTERR.2. Steps 1. Set parameters so that GSM phase 2+ is supported by default (OPH) a.3 Setting parameters so that GSM phase 2+ and MT-SM are supported For more information. 20 shortMsgGateway . dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 151 (267) . 25 shortMsgMT-Relay Modify the parameters. 24 mwdMngt . 21 shortMsgMO-Relay . if necessary ZOPH:MODIFY:AC=<application context>:VER=<MAP version>. Setting parameters so that GSM phase 2+ and MT-SM are supported 1. ZMXM::::T22=Y. b. 23 shorMsgAlert Note that MAP version 2 is allowed only in this application context. Check the SMS-related application context-specific MAP versions ZOPH:INTERR. Further information: Example 3. 2. There is no change for MAP version 3. Examine the SMS-related application contexts on the execution printout. Make sure MT-SM is supported in the MSC/VLR (MXM) You can activate MT-SMs by giving the following commands in the VLR: ZMXM::::T21=Y.Configuring network elements for SMS 2. . Set parameters so that GSM phase 2+ is supported by default a. MAP version 3 related instructions can be found in section Handling SMSrelated MAP operations in MSC and HLR . 23 (shortMsgAlert) and 25 (shortMsgMT-Relay) on the execution printout. 2. For phase 2+ use the following version numbers: ZOPH:MODIFY:AC=21:VER=3. if necessary. ZOPH:MODIFY:AC=25:VER=3. Modify the parameters. 152 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . ZOPH:MODIFY:AC=23:VER=2. AC NBR AC NAME ALLOWED MAP VERSIONS 1 networkLocUp 1 2 3 2 locationCancellation 1 2 3 3 roamingNumberEnquiry 1 2 3 5 locationInfoRetrieval 1 2 3 7 reporting 3 8 callCompletion 3 10 reset 1 2 11 handoverControl 1 2 13 equipmentMngt 1 2 14 infoRetrieval 1 2 15 interVlrInfoRetrieval 1 2 16 subscriberDataMngt 1 2 3 17 tracing 1 2 3 18 networkFunctionalSs 1 2 19 networkUnstructuredSs 2 20 shortMsgGateway 1 2 3 21 shortMsgMO-Relay 1 2 3 23 shortMsgAlert 1 2 24 mwdMngt 1 2 3 25 shortMsgMT-Relay 1 2 3 26 imsiRetrieval 2 27 msPurging 2 3 28 subscriberInfoEnquiry 3 29 anyTimeEnquiry 3 32 gprsLocationUpdate 3 36 ss-InvocationNotification 3 37 locationSvcGateway 3 38 locationSvcEnquiry 3 b. Make sure MT-SM is supported in the MSC/VLR ZMXM::::T21=Y.SMS Guide Examine the SMS-related application contexts 21 (shortMsgMORelay). ZMXM::::T22=Y. <track>: INT=<interrupt level>.1 Connecting the SMSC to the SMS-GMSC/SMS-IWMSC Steps 1. Connect the SMSC to the MSC Connect the SMSC to the MSC physically with the Ethernet cable.0::<interface name>:<destination IP address>. see Interfaces between SMS network elements .25 or TCP/IP and SS7 MAP SMSC . . In case of i-series products the TCP/IP connection is accessible through the CPU card of the BDCU. Create the COCEN plug-in units to the system in case of subrack MSC (WTP) ZWTP:BDCU.0:COCEN. Create a TCP/IP network interface for each BDCU unit (QRN) Create a TCP/IP network interface for each BDCU unit running the short message transfer system by using the QRN command. otherwise the COCEN card of the BDCU is used. Expected outcome You can check the terminal number available in BDCU-0 for the network interface with the following command: dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 153 (267) . It is EL0 in case of a cartridge MSC.25 interface between the SMSC and the MSC.3.<DEL>:<netmask length>:<state>. where: <interface name> . ZQRN:BDCU. Configuring the TCP/IP connection consists of three parts: 2. 3. and Comparison of SMS functionalities in case of SMRSE over X. 2. Unblock the created interfaces. It is COx (x means the PIU index) in case of a subrack MSC.3 Configuring TCP/IP connection for SMS The TCP/IP connection is an alternative to the X. SMRSE in SMS . For more information on TCP/IP.<L/P>.<piu index>.Configuring network elements for SMS 2. 0:CO5:188. The netmask length is 25. Connect the SMSC to the MSC physically with the Ethernet cable.IMG file (MXP) Make sure that the ZIPBOXMX. The plug-in unit is located in slot 5 in the cartridge. ZUSU:BDCU. Create a TCP/IP network interface for each BDCU unit running the short message transfer system.IMG:* 5.67.47:INT=22. 4. Note In i-series products the terminal number of the CPU card can be used. ZWTP:BDCU. Restart BDCU units (USU) Restart the BDCU units which you modified. Force the units to load the code from the disk with the USU command. 2.0:C=DSK.89. Connecting the SMSC to the SMS-GMSC/SMS-IWMSC 1. ZQRN:BDCU. and its interrupt level is 22H. 3.IMG file can be found in the BLCODE directory. The track number is 47. which is usually 0. In case of i-series products the TCP/IP connection is accessible through the CPU card of the BDCU.0.SMS Guide ZWTI:P:BDCU.0:COCEN. Further information: Example 4.P:25:UP. You can check it with the following Service Terminal command in the OMU. Check ZIPBOXMX.128. otherwise the COCEN card of the BDCU is used. Unblock the created interface. 154 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . ZMXP:WO-BLCODE/ZIPBOXMX.5. Create the COCEN plug-in units for the BDCU-0. Configuring network elements for SMS 4. Create SMS routing support analysis (CFU) You can create a SMS routing support analysis for defining the case when SMS routing analysis is started. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 155 (267) . see SMS routing analysis . for the available conditions. Make sure that the ZIPBOXMX.2 Creating analysis on SMS application level in the MSC Steps 1. Create an SMS routing analysis (CFE) Note This step is optional and is necessary only if you want to route the subscriber's SMS request to the service application in the desired SMSC or if you want to create different tariff classes for MO-SMs. ZUSU:BDCU.3. Force the units to load the code from the disk.0:C=DSK. Restart the BDCU units which you modified.IMG:* 5. You can check it with the following Service Terminal command in the OMU: ZMXP:WO-BLCODE/ZIPBOXMX.IMG file can be found in the BLCODE directory. ZCFU:SMSC=<smsc address>. Note You can execute this command only if you have Feature 1165: Short Message Services GSM Phase 2+ Enhancements in use in your network. 2. 2. If you do not have feature 1165. For more information. a. Find out three free records in UTPFIL (DFD) ZDFD:CM. you have to add the address to the UTPFIL. If the variant part (the last 4 digits) is 0000. where <file number> is the number for the UTPFIL. c.SMS Guide ZCFE:PID=<protocol identifier>.SAPTYPE=<service application prefix type><option>:SMSC=<short message service centre address>. For example. 20000 can be given as 2. 4. Add the SMSC address into UTPFIL records Make sure that you do the changes in every CCSU. PASSW=<password>:<operation>:<IP address>. 3. if necessary If you want to use always the same SMSC address towards the MS.x:<file number>. it can be omitted. Find out the UTPFIL and its number running in the CCSU / GSU (WQV. 156 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Create an SMSC address analysis (CFS) ZCFS:<SMSC address>. ZDFS:CM. e.x:<file number>.IP:LEVEL=<SMSC level>.0:NAME= <UTPFIL name>. DFL) ZWQV:CCSU:UTP%. ZDFL:CCSU.SAN=<service application name>.3 Setting parameters so that GSM phase 2+ and MT-SM are supported See also MAP in SMS .3. b. Preconfigure the SMSC address. Restart every CCSU unit one by one d. 2. MAP version 3 related instructions can be found in Handling SMS-related MAP operations in MSC and HLR . see Working examples for SMS management . Find the CM in WO-EX state ZUSI:CM. given as a hexadecimal.TC=<tariff class>.<record number>.SAP=<service application prefix>. especially MAP version 3 for more information. Further information: Example 5. 23 (shortMsgAlert) and 25 (shortMsgMT-Relay) on the execution printout. ZMXM::::T22=Y. . Set parameters so that GSM phase 2+ is supported by default a. 25 shortMsgMT-Relay Modify the parameters.Configuring network elements for SMS Steps 1. There is no change for MAP version 3. You can activate them by giving the following commands in the VLR: ZMXM::::T21=Y. if necessary ZOPH:MODIFY:AC=<application context>:VER=<MAP version>. Set parameters so that GSM phase 2+ is supported by default (OPH) a. . AC NBR AC NAME ALLOWED MAP VERSIONS 1 networkLocUp 1 2 3 dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 157 (267) . Setting parameters so that GSM phase 2+ and MT-SM are supported 1. Examine the SMS-related application contexts on the execution printout. 2. Check the SMS-related application context-specific MAP versions. 24 mwdMngt . Check MT-SM support in MSC/VLR (MXM) Make sure MT-SM is supported in the MSC/VLR. . b. 23 shorMsgAlert Note that MAP version 2 is allowed only in this application context. Examine the SMS-related application contexts 21 (shortMsgMORelay). Check the SMS-related application context-specific MAP versions ZOPH:INTERR. 20 shortMsgGateway 21 shortMsgMO-Relay . ZOPH:INTERR. if necessary. From Feature 1043 point of view the SMS related Application Context (AC) defaults should be set to version 3. ZOPH:MODIFY:AC=23:VER=2. ZMXM::::T22=Y. ZOPH:MODIFY:AC=25:VER=3.4 Handling SMS-related MAP operations in MSC and HLR The possibility to set MAP version 3 by MMLs appears only if you have Feature 1043: Short Message Services GSM Phase 2+ in use in your network . 2. Modify the parameters. Make sure MT-SM is supported in the MSC/VLR ZMXM::::T21=Y.SMS Guide 2 locationCancellation 1 2 3 3 roamingNumberEnquiry 1 2 3 5 locationInfoRetrieval 1 2 3 7 reporting 3 8 callCompletion 3 10 reset 1 2 11 handoverControl 1 2 13 equipmentMngt 1 2 14 infoRetrieval 1 2 15 interVlrInfoRetrieval 1 2 16 subscriberDataMngt 1 2 3 17 tracing 1 2 3 18 networkFunctionalSs 1 2 19 networkUnstructuredSs 2 20 shortMsgGateway 1 2 3 21 shortMsgMO-Relay 1 2 3 23 shortMsgAlert 1 2 24 mwdMngt 1 2 3 25 shortMsgMT-Relay 1 2 3 26 imsiRetrieval 2 27 msPurging 2 3 28 subscriberInfoEnquiry 3 29 anyTimeEnquiry 3 32 gprsLocationUpdate 3 36 ss-InvocationNotification 3 37 locationSvcGateway 3 38 locationSvcEnquiry 3 b. These ACs are the following: 158 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . 2. For phase 2+ use the following version numbers: ZOPH:MODIFY:AC=21:VER=3. Further information: Example 6. set back the MAP version of SMS related operations to version 2 using the MML commands mentioned above (OPH for Application Contexts. Note If there is MAP version 3 in the VMSC. 25) to version 3. If you do not want to use MAP version 3 signalling between network elements for SMS operations. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 159 (267) . 21. Steps 1. If the MAP version of shortMsgMO-Relay (21) Application Context is set to version 3. then the IMSI of A-subscriber is sent to SMS-IWMSC form the VMSC. shortMsgGateway 20 shortMsgMO-Relay 21 mwdMngt 24 and shortMsgMT-Relay 25 . ZOPH:MODIFY:AC=<AC code>:VER=<version number>. Interrogate the Application Context-Specific defaults (OPH) ZOPH:INTERR. 2. which makes it possible to have Feature 714: Short Message Service Enhancements and Feature 1043: Short Message Services. OPS for Alarm Thresholds). OPA and OPR for Error Counters. .Configuring network elements for SMS . . ZOPH:MODIFY:AC=20:VER=3. GSM Phase 2+ switched on at the same time. Set the version of SMS related Application Contexts to version 3 (OPH) Set the version of SMS related Application Contexts (20. 24. Feature 714: Short Message Service Enhancements is disregarded and normal reason code (MNRR) is sent back instead of system failure. 3. Reset Error Counter ZOPR:<operation code>:<version number>. ZOPA:2:3:ACT. Setting Error Alarm Threshold (OPS) 160 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .SMS Guide Further information: Due to the new MAP version. you can activate/deactivate/reset Error Counters to MAP operations using the OPA and OPR commands. 4. b.4. Further information: Example 8. there is a change in the Network Entity Address Analysis Result Handling. The Error Counters can be activated/ deactivated/reset to MAP version 3 operations also. Setting Error Counters for MAP version 3 (OPR) a. Interrogate the Error Counter ZOPA. Activate/Deactivate Error Counter (OPA) ZOPA:<operation code>:<version number>:<Activate/ Deactivate/Interrogate>. Interrogate the Error Counters (OPA) ZOPA. In the OPV command the new MAP version 3 is also a possible value for the MAP operation version. 2. 2. Steps 1. ZOPR:2:3. Further information: Example 7.1 Handling Error counters in SMS Optionally. MEDIUM=150. <activation_status>. Set Error Alarm Thresholds for MAP operation ZOPS:<operation code>:<version number>: LOW=<0. Interrogate Error Alarm Thresholds for MAP operation ZOPQ:<operation code>. The parameter can be checked by the WOS command: dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 161 (267) ..MEDIUM=<0. If you have the 'Welcome-SM' function you can activate it by MML commands: . The 'Welcome-SM' function can be activated by setting the WELCOME_SM (class 2) FIFILE parameter to A (activate).5 Handling the Welcome SM related parameters Description of the Welcome SM functionality can be found in Welcome SM to the roamer . <parameter_number> The number of the WELCOME_SM parameter. HIGH=200.1000>.Configuring network elements for SMS a. for example: ZOPS:2:3:LOW=100.. for example: ZOPQ:2. and the MEDIUM value should be higher than the LOW value. b.. <activation_status> Given value can be D (deactive) or A (active). Where: <parameter_class> Parameter class in FIFILE (=2).<parameter_number>. 2. Before you start The 'Welcome-SM' related parameters appears only if the WELCOME_SM FIFILE parameter is set to value ACTIVE. HIGH=<0... The HIGH value should be higher than the MEDIUM value.1000>. ZWOA:<parameter_class>..1000>. MSISDN=<msisdn>. 3.TON=<type_of_number>.TON=INT. Set the SMSC address (in MSC and HLR) (WVS) ZWVS:SCADDR=<smsc_address>:NP=<numbering_plan>. 2. ZMIC:IMSI=262030024020388. Note After setting these three parameters.TON=<type_of_number>. 4. Example 12. Example 11.MSISDN=491774020388. Set the Configurable MSISDN address ZWVS:CMSISDN=491774020388:NP=E164.SMS Guide ZWOS:<parameter_class>.<parameter_number>.TON=INT. you need to wait 2 minutes to get the global data updated in MSC. Example 9. Set the SMSC address ZWVS:SCADDR=491770000097:NP=E164. 162 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Set the Configurable MSISDN address of virtual subscriber (WVS) ZWVS:CMSISDN=<cmsisdn_address>: NP=<numbering_plan>. Create virtual subscriber in the HLR if you use MAP version 2 (MIC) ZMIC:IMSI=<imsi>. Set the SMSC application address (in MSC and HLR) (WVS) ZWVS:WSCAPP=<smsc_application_address>: NP=<numbering_plan>. Example 10. Steps 1. TON=<type_of_number>.TON=INT. Set the SMSC application address ZWVS:WSCAPP=491776789:NP=E164. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 163 (267) . for example: ZWVR:SCADDR=491770000097:NP=E164. TON=INT. Interrogate the parameters (in MSC and HLR) (WVI) a. Remove the Configurable MSISDN address ZWVR:CMSISDN=<cmsisdn_address>: NP=<numbering_plan>. Interrogate Configurable MSISDN address ZWVI:CMSISDN. c. Interrogate SMSC application address ZWVI:WSCAPP. Remove the SMSC application address ZWVR:WSCAPP=<smsc_application_address>: NP=<numbering_plan>.TON=<type_of_number>.TON=<type_of_number>. TON=INT. Remove virtual subscriber form HLR ZMID:IMSI=<imsi> or MSISDN=<msisdn>. c. Remove the parameters (in MSC and HLR) (WVR) a. TON=INT. b. Interrogate SMSC address ZWVI:SCADDR. for example: ZWVR:CMSISDN=491774020388:NP=E164. 6. for example: ZWVR:WSCAPP=491776789:NP=E164.Configuring network elements for SMS 5. b. d. Remove the SMSC address ZWVR:SCADDR=<smsc_address>: NP=<numbering_plan>.TON=<type_of_number>. SMS Guide 164 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . MBC) a. MBC) If you want to create a basic service with a new basic service code index for a subscriber. The teleservice to be created is 'short message MT/PP' (T21). dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 165 (267) . . Further information: Example 13.BSERV=<basic service code>. . . Create SMS for a subscriber in HLR (MBF. The subscriber can use the SM services only if SMS is provided for him/her through subscriber management.Managing SMS subscriber-specific data 3 Managing SMS subscriber-specific data The subscriber management functions allow the addition and deletion of the subscriber's short message services. you must create first the new basic service code index with the MBF command. Create SMS for subscriber ZMBC:IMSI=<international mobile subscriber identity>. The recommended way of creating SMS for a number of subscribers at a time is to use multiple subscribers handling. see Subscriber Administration . Define the SMS basic services by using the MB command group. see Short Message Services Overview. Create SMS for a subscriber in HLR (MBF. b. Creating SMS for a subscriber Create a basic service for a subscriber whose IMSI number is 244041112346 and MSISDN number 358401154322. For more information. For IN SMS-related information. see Handling of IN SMS . Create the new basic service for the subscriber with the MBC command afterwards. For the whole topic summary. Other parameters have default values.MSISDN=<mobile subscriber international ISDN number>. see instructions on Basic Service Handling . For more information. Steps 1. ..000 ALL T21... MOBILE STATION ISDN NUMBER ...MSISDN=<msisdn>...... These are followed by a list of the bearer capabilities of the subscriber's basic services as determined with the basic service code index (see the MBF command)......... List the subscriber's service centers in the HLR ZMIS:IMSI=<imsi>. MIS) You can list the basic service data of a given subscriber with the MBO command in the HLR.... The execution printout of the command is the following: BASIC SERVICE DATA: INTERNATIONAL MOBILE SUBSCRIBER IDENTITY ............. BASIC SERVICE ....... or the MVO command in the VLR. b.. Outputting a subscriber's SMS data List the basic services of a subscriber whose IMSI is 244041112345...SMS Guide ZMBC:IMSI=24404112346... Further information: Example 14. Output a subscriber's SMS data in HLR (MBO. COMMAND EXECUTED 24404112346 358401154322 T11..... a...000 ALL 166 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en ... basic service........ mobile subscriber international ISDN number.... BASIC SERVICE ............. SERVICE AREA OF MSISDN .... ZMBO:IMSI=244041112345....... MOBILE STATION ISDN NUMBER ................ service area of MSISDN..MSISDN=358401154322................................. where <international mobile subscriber identity> specifies the IMSI of the subscriber whose basic services are displayed....... BASIC SERVICE .......................BSERV=T21... The parameter is a decimal number of 15 digits at the maximum.. List the basic service data of a subscriber in the HLR ZMBO:<international mobile subscriber identity>....000 ALL T22..... The command lists the following information of the subscriber: international mobile subscriber identity.... MOBILE STATION ISDN NUMBER ....... 2... SERVICE AREA OF MSISDN ... SERVICE AREA OF MSISDN ............... .... Listing the subscribers service centers in the HLR Display the service center addresses of subscriber whose IMSI number is 244051112345. MOBILE STATION MEMORY CAPACITY EXCEEDED FLAG The value Y (Yes) in this field indicates that an attempt to transfer a short message has been unsuccessful because the mobile memory capacity has been exceeded... ZMIS: IMSI=2440511123445.. N MOBILE STATION NOT REACHABLE REASON FOR GPRS: IMSIDET!!!!!! MOBILE STATION NOT REACHABLE REASON FOR NON GPRS: USUBMSC SERVICE CENTER ADDRESS (ES) -------------------------------------------------12345678 87654321 COMMAND EXECUTED The fields in the execution printout have the following meanings: MOBILE STATION NOT REACHABLE FLAG The value Y (Yes) in this field indicates that an attempt to transfer a short message has been unsuccessful because the subscriber has not been reached..Managing SMS subscriber-specific data Figure 61.N MOBILE STATION MEMORY CAPACITY EXCEEDED FLAG . Y MOBILE STATION NOT REACHABLE FOR GPRS FLAG ..... The execution printout of the command is the following: INTERNATIONAL MOBILE SUBSCRIBER IDENTITY ... 244051112345 MOBILE STATION NOT REACHABLE FLAG ...... An example of outputting a subscriber's SMS data Example 15. MOBILE STATION NOT REACHABLE FOR GPRS FLAG The value Y (Yes) in this field indicates that an attempt to transfer a short message through GPRS has been unsuccessful because the subscriber has not been reached... MOBILE STATION NOT REACHABLE REASON FOR GPRS or MOBILE STATION NOT REACHABLE REASON FOR NON GPRS These fields give the reason why a mobile station is not reachable for General Packet Radio Service (GPRS) or for non-GPRS.. The possible reasons are the following: dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 167 (267) . . . in which case the subscriber cannot receive or send SMs when roaming in the given network. 4. . Delete basic services from a subscriber (MBD) Note You cannot delete a subscriber's primary basic service. NPMSC (no paging response through the MSC) IMSIDET (IMSI detached) NPSGSN (no paging response through the SGSN) GPRSDET (GPRS detached) USUBMSC (Unidentified subscriber through the MSC) USUBSGSN (Unidentified subscriber through the SGSN) 3. The MSISDN number of the basic service to be deleted is 358401154321. For more information. You can also use HLR parameters to prevent the sending of MT-SMS and MO-SMS basic services to a given PLMN. ZMBD:<international mobile subscriber identity>. ZMBD:IMSI=244041112345. You can activate ODB categories that affect also the subscriber's MO-SMs and MTSMs. . 168 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .<mobile subscriber international ISDN number>. Deleting a subscriber's SMS Delete basic service data from a subscriber whose IMSI is 244041112345. Delete a subscriber's SMS (MBD) a.MSISDN=358401154321. Prevent roaming from other networks A subscriber can activate normal MT and MO barrings for SMS.SMS Guide . see Feature 220: Operator Determined Barring . . Further information: Example 16. The GSM barrings and operator-determined barrings do not have an effect if the subscriber's SMs go through SGSN. The HLR contains a separate parameter management for a GPRS subscriber's MT-SMS and MO-SMS basic services. see the feature description of Feature 857: Support for General Packet Radio System .Managing SMS subscriber-specific data You can also affect the sending and receiving of SMs with Feature 910: IN Short Message Service . dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 169 (267) . For more information. SMS Guide 170 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . SMS prevention. 4.1 Handling User Data in SMS The transfer of UserData in MO/MT-SM with positive and negative acknowledgement requires MAP version 3 SMS-related operations between the network elements. In this case the SMSC level should be set to SMS phase 2+ (S3) in the MSC using the CFS command. It means that the version of the SMS-related MAP operations should be set to version 3 both in the MSC and HLR. and routing enhancement. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 171 (267) .Managing SMS network element-specific data 4 Managing SMS network element-specific data This section gives procedural information on various network element-related functions. For the ability to transfer the UserData to the SMSC.IP:LEVEL=<SMSC level>. Set the SMSC level to SMS Phase 2+ in MSC (CFS) ZCFS:<SMSC address>. such as user data and MNRR handling. the network provides full support of SMS GSM phase 2+ standard and MAP version 3 (SMS-related operations). activation of picture message information. The MAP version of the SMS-related Application contexts should be set to MAP version 3. the SMSC should be connected to the MSC through TCP/IP. SMS measurement. For the whole topic summary. as described in Handling SMS-related MAP operations in MSC and HLR . see Short Message Services Overview. Steps 1. This parameter should be set both in the MSC and HLR. Before you start If you have Feature 1043: Short MessageServices GSM Phase 2+ in use. ZCFS:1234567890. For the ability to transfer the MNRRs to the SMSC. Test the UserData transfer in positive acknowledgement a. Feature 714: Short Message Service Enhancements is disregarded. which makes it possible to have Feature 714: Short Message Service Enhancements and Feature 1043: Short Message Services. and normal reason code (MNRR) is sent back instead of system failure.SMS Guide Example 17.IP:LEVEL=S3. 2. 2.2 Handling of MNRR in SMS The transfer of MNRR requires MAP version 3 SMS-related operations between the network elements. c. Make a Location Update Send a successful MT-SMS to MS(A) Send a successful MO-SMS to a subscriber Deactivating the User Data transferring If you do not want to transfer the UserData between the Mobile Station and the SMSC: 1. Before you start If you have Feature 1043: Short Message Services GSM Phase 2+ in use. It means that the version of the SMS-related MAP operations should be set to version 3 both in the MSC and HLR. Set the MAP version 2 for the SMS operations Set the SMSC level to SMS level 2 using the MML command CFS 4. In this case the SMSC level should be set to SMS phase 2+ (S3) in the MSC by using the CFS command. the SMSC should be connected to the MSC through TCP/IP. 172 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . The MAP version of the SMS-related Application contexts should be set to MAPv3 as described in Handling SMS-related MAP operation in MSC and HLR . b. the network provides full support of SMS GSM phase 2+ standard and MAP version 3 (SMS-related operations). Note If there is MAP version 3 in the VMSC. GSM Phase 2+ switched on at the same time. IP:LEVEL=S3. or refer to feature description of Feature 1043: Short Message Services.3 Activating selective CDR generation in SMS With the selective CDR generation functionality the CDR generation can be reduced in the TMSC or based on the SMSC address. For background information. Expected outcome The MNRF flag and the MNRR field is set in the HLR . do the following a. Make a Location Update For example to test the IMSI Detached reason code: Make an IMSI Detach. The MNRR should be IMSI Detached. ZCFS:1234567890. see Charging records and Selective CDR generation in TMSC and Selective CDR generation based on SMSC address . which results in a decrease of load in the MSC/billing centre. Send an MT-SM to MS (A) b.IP:LEVEL=<SMSC level>. Example 18. Set the MAP version 2 for the SMS operations Set the SMSC level to SMS level 2 by using the MML command CFS 4. command. 2. b. Test the MNRR a. GSM Phase 2+ . dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 173 (267) . 3. This feature makes it possible to differentiate between the suppression of MO and MT CDRs. Deactivate MNRR transferring If you do not want to transfer MNRRs between the Mobile Station and the SMSC.Managing SMS network element-specific data Steps 1. Check the MNRR field in the HLR by using the ZMIS:IMSI=<imsi>. Set the SMSC level to SMS Phase 2+ in the MSC (CFS) ZCFS:<SMSC address>. b.and MT-SMS cases. MO MT BOTH prevent CDR generation for MO-SM prevent CDR generation for MT-SM prevent CDR generation for both MO. 5. Interrogate the existing analysis in MSC ZCFI:TYPE=CDR.and MTSM 3. Expected outcome Check that no charging record is generated in MO. Prevent CDR generation for the used SMSC address ZCFR:SMSC=<SMSC address>. 4. 2. Deactivating selective CDR generation You can deactivate the Selective CDR generation by deleting the created SMSC analysis for SELECTIVE CDR PREVENTION with the CFD command. 174 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . DIRECTION=<direction>. Steps 1. Send an MT-SM to MS(A) Send an MO-SM with MS(A) Delete the unnecessary SMS CDR generation prevention (CFD) ZCFD:TYPE=CDR:DIG=<SMSC address>.SMS Guide Before you start You must have Feature 1043: Short Message Services GSM Phase 2+ in your network to suppress the not needed CDR generation based on the SMSC address. Make a Location Update Prevent the CDR generation in the MSC (CFR) a. and an SMSC connected to one of them (this is the 'home switch'). the GEN_CDR_FOR_FIRST_SM PRFILE parameter must be turned on. <parameter_value>. For testing the different kind of prevention cases you need two switches connected to each other. you can choose to generate a CDR only for the first SM.<parameter_number>. .Managing SMS network element-specific data 4. For further background information see Charging records . instead of generating CDRs for all the SMs in the concatenated SM. Turn on the GEN_CDR_FOR_FIRST_SM PRFILE parameter (WOC) ZWOC:<parameter_class>. The following addresses can be configured: . if Feature 1043: Short Message Services GSM Phase 2+ is available in your network. or 00h (FALSE). Steps 1.4 Activating Picture message information in the CDR There is a Picture message information in the CDR: concerning to concatenated short message in case of a picture message. Where: <parameter_class> 31 <parameter_number> 28 <parameter_value> parameter value is FFh (TRUE).5 Preventing SMS You are allowed to configure SMSC or A number addresses in the VMSC by MML commands. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 175 (267) . 4. In this case. SMSC address from where the MT-SM is not allowed to be sent SMSC address to where the MO-SM is not allowed to be sent A-subscriber number from where the MO-SM is not allowed to be originated . and make a Location Update Create MS(B) to 'visitor switch' with SMS capacity and make a Location Update 2. <deny object> can be .5. .DIRECTION=<direction>. 4. . or refer to feature description of Feature 1043: Short Message Services. HOME if the barring is for home subscribers VISITOR if the barring is for visitor subscribers ALL if the barring is for all subscribers 176 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . see Barring SMS in the MSC .SMS Guide You can deactivate the prevention of SMs from both directions by deleting the created A-NUMBER PREVENTION and SMSC DENY analyses by using the CFD command. Steps 1. Create MS(A) to 'home switch' with SMS capacity.1 Preventing MT-SMS Steps 1. Where: <smsc address> is the ISDN address of the SMSC <direction> can be . For background information. Roam with MS(A) to 'visitor switch' Create an SMSC address barring to 'visitor switch' for the SMSC address (CFL) ZCFL:SMSC=<smsc address>. GSM Phase 2+ . DENYOBJ=<deny object>. 'MO' for MO-SMS prevention or 'MT' for MT-SMS prevention . 2. If the prevention analysis for MT-SMS is set for visitor or all subscribers. Prevent MO-SM (preventing certain SMSC address) For background information. If the prevention analysis for MT-SMS is set for home subscribers. 4.5.Managing SMS network element-specific data Further information: Example 19. 3. .DENYOBJ=VISITOR. especially SMSC barring. 4. Expected outcome . see Section Barring of MO-SM .2 Preventing MO-SM MO-SM prevention can be configured both into the VMSC and into the SMSIWMSC. it means permanent error for the SMSC so it will not try to deliver the SM again. 5.DIRECTION=MT. Interrogate the existing analysis (CFI) ZCFI:TYPE=MT-DENY. Steps 1. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 177 (267) . Send an MT-SM to both MS(A) and MS(B) Test the prevention for HOME and ALL subscribers For testing the prevention for HOME and ALL subscribers delete the existing analysis and create a new one for HOME/ALL subscribers For deleting MT-SMS prevention analysis use the CFD command: ZCFD:TYPE=MT-DENY:DIG=<smsc address>. it means temporary error for the SMSC so it tries to deliver the SM according to its Retry Table (when real SMSC is used). Test the analysis affecting VMSC Make a Location Update with both MS(A) and MS(B) to 'home switch'. ZCFL:SMSC=<smscaddress>. a. d. c. Create an analysis to 'home switch' for MO-SMs (CFL) ZCFL:SMSC=<smsc address>. e. DENYOBJ=VISITOR. Send an MO-SM with MS(A) Delete analysis (CFD) ZCFD:TYPE=PREV:DIG=<msisdn>. Interrogating the existing analysis (CFI) ZCFI:TYPE=PREV. Send an MO-SM with both MS(A) and MS(B) The MO-SM should be successful for MS(A) as a home subscriber but not successful for MS(B) as a visitor subscriber. d. Test the analysis affecting the VMSC Make a Location Update with MS(A) to 'home switch'. Interrogate the existing analysis (CFI) ZCFI:TYPE=MO-DENY. c. Further information: To test the proper functioning in the SMS-IWMSC for the analyses for MO-SMs that was mentioned above. delete the existing analysis and create a new one for HOME/ALL subscribers Delete MO-SMS prevention analysis (CFD) ZCFD:TYPE=MO-DENY:DIG=<smsc address>. Prevent MO-SM (preventing certain subscriber/range of subscribers) a.SMS Guide b. c. f. 2. Make a Location Update with both MS(A) and MS(B) to SMSGMSC Create similar analyses to 'home switch' for MO-SMSs by using the MMLs mentioned earlier Try to send MO-SMs with MS(A) /home/ and MS(B) /visitor/ subscribers using the address of the SMSC (SMS generator) connected to the 'home switch' 178 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . do the following: a.DIRECTION=MO. b. Test the prevention for HOME and ALL subscribers For testing the prevention for HOME and ALL subscribers. b. Create an analysis to 'home switch' for MS(A) MSISDN (CFV) ZCFV:MSISDN=<msisdn>. e. In the transit MSC the load increases about 45800 byte/s. In DX 200 MSC the SMS measurement takes place in the STU. Create Destination Object List for SMS measurement (TDC) You can add 5 SMSC addresses in each type of the SMS measurement.<object_list_number>: SMSCTYPE=<smsc_type>:MSC=<msc_type>: SMSC=<smsc_address>. the load of the message bus increases about 1000 byte/s (assuming 120000 SMs in peak hour). For details. Steps 1. which means a 0. ZTDC:SMS. In DX 200 Transit MSC the SMS measurement takes place in the CMU.8 million SMs in peak hour). which is 0. GSM Phase 2+ Enhancements in your network. which means 0. This enhancement works only if you have Feature 1165: Short Message Services. The value of the SMS_ENHANCEMENT parameter in the PRFILE should be ON.Managing SMS network element-specific data 4.5 million SMs in peak hour).13% increase with the 32 Mbyte/s MB (assuming 5. Before you start The SMSC (latest NOKIA SMSC) should be connected to the DX 200 MSC over TCP/IP connection.02% load increase with the 4 Mbyte/s MB (subrack). and for the number of MO-SMs going to a certain SMSC. refer to the feature description of Feature 1165: Short Message Services.6 Activating SMS measurement SMS measurement provides statistical counters for the number of mobileterminating short messages (including welcome MT-SMs) coming from a certain SMSC. the load of the Message Bus (MB) in the cartridge MSC increases about 15000 byte/s. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 179 (267) . GSM Phase 2+ Enhancements .08% load increase with the 16 Mbyte/s MB (assuming 1. Note When the SMS measurement is active. In the subrack MSC. ZT2C:MID=135:OID=001:OLN=TEST.ROP=0800-2400.OD=10. Further information: Example 23. Further information: Example 21.ED=<stop_date>. 001). Modify SMS measurement (T2M) 180 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . 2. ROP=<result_output_period>.ED=2001-02-03.ET=06-06-06. 4.OD=<output_delay>. ZT2I:NAME=<measurement_name>:OID=001:ICH=B. Create Object List (T2C) ZT2C:MID=<measurement_id>: OID=<object_list_identifier>: OLN=<object_list_name>. ZTDC:SMS. Further information: Example 22. 5.1:SMSCTYPE=L:MSC=VMSC:SMSC=491770000097.ET=<stop_time>. Start SMS measurement (T2S) ZT2S:NAME=PMEAS135:OID=<object_list_identifier>: RAP=<result_accumulation_period>.SD=2001-02-02.SD=<start_date>.ST=0606-06. ST=<start_time>.SMS Guide Further information: Example 20. 3. Interrogate SMS measurement (T2I) ZT2I:NAME=<measurement_name>: OID=<object_list_identifier>: ICH=<interrogate_choice>. The object list identifier must be 3 digits (for example. ZT2S:NAME=PMEAS135:OID=001:RAP=15. Stop SMS measurement (T2E) ZT2E:NAME=<measurement_name>: OID=<object_list_identifier>:ED=<stop_date>. ET=06-0 6-06.7 Activating routing enhancement in SMS Routing is enhanced by that national and international destinations are handled differently.OD=<output_delay>. Further information: For background information on SMS measurement. You can define for which SMSC address the SMS routing analysis must be started. 4. 6.Managing SMS network element-specific data ZT2M:NAME=<measurement_name>: OID=<object_list_identifier>: RAP=<result_accumulation_period>. the alphabetical numbering makes it easier for the subscribers to use special services which are using applications connected to the SMSC. ZT2M:NAME=<measurement_name>:OID=001:RAP=15. Further information: Example 24. This way you can use the number for national service code (with the same digits) with no restrictions. Before you start dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 181 (267) . that is. ROP=<result_output_period>. It can result in increased SMS usage and increased revenue. and that the destination can be addressed with an alphanumeric address. there is no conflict if the country code is the same as the national service code. ET=<stop_time>. In addition. see Section SMS measurement .OD=10.ROP=08002400. ZT2E:NAME=<measurement_name>:OID=001:ED=2001-02-03. Further information: Example 25. SAP=99887766. Create SMS routing support analysis (CFU) This analysis identifies the SMSC for which the SMS routing analysis has to be executed. GSM Phase 2+ Enhancements in your network.SAN=TEST. ZCFU:SMSC=491770000097. The SMSC should support the alphanumeric destination address and the extended destination address length. SAN=<service_application_name>. Further information: Example 26. 182 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . see SMS routing enhancements . ZCFE:PID=N.25 connection. Further information: Example 27. ZCFU:SMSC=<smsc_address>. MAP version 3 is needed for this functionality. Steps 1. SAP=<service_application_prefix>.TC=<tariff_class>.SMS Guide The SMSC (latest NOKIA SMSC) should be connected to the DX 200 MSC over either TCP/IP or X. TC=500. This enhancement works only if you have Feature 1165: Short Message Services. For details refer to the feature description of Feature 1165: Short Message Services GSM Phase 2+ Enhancements .SAPTYPE=NAT:SMSC=491770000098. Further information: For description on the SMS routing enhancement. Create SMS routing analysis for the SMSC (CFE) ZCFE:PID=<protocol_identifier>. 2. SAPTYPE=<service_application_prefix's type>: SMSC=<smsc_address>. Activating Nokia-specific SMS features 5 Activating Nokia-specific SMS features This section provides information on how to activate the use of private numbers when sending MO-SMs within a PNP group. Destination addresses sent from the SMSC to MSs are in national or international number format. see Short Message Services Overview. Steps 1. that feature activation instructions on these functions may not be available separately. 3. 2. Create MO-SMS and MT-SMS services dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 183 (267) .1 PNP numbering for SMS (MO) Feature 476: PNP Numbering for SMS (MO) makes it possible to use private numbers when sending MO-SMs in the same PNP group. 5. the PNP service converts the destination address in the SMS SUBMIT primitive into international number format. The IN SMS related procedural information can also be found. MAP converts it into international number format before making the HLR inquiry to obtain routing information for MT-SMs. If a PNP mobile subscriber dials a number in private number format or in unknown number format. For the whole topic summary. . Create SMSC routing analysis Create SMSC routing analysis as described in Creating analysis on SMS application level in the MSC . but if the national number format is used. Please note. Connect the SMSC to the SMS-GMSC/IWMSC Connect the SMSC to the SMS-GMSC/IWMSC as described in Connecting the SMSC to the SMS-GMSC/SMS-IWMSC . Create PNP service in the HLR (MSD) ZMSD:IMSI=<international mobile subscriber identity>:PNI=<private numbering index>. 4. For more information. 6. 3. 2. 184 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . 6. Create the analysis for the PNP in the VMSC (MPC) ZMPC:PNI=<private numbering index>.SMS Guide Create the MO-SMS and MT-SMS services to the MS in the HLR and provision the services in the VLR as described in Managing SMS subscriber-specific data . Further information: Example 28. Create global title analyses for the SMSC address Create global title analyses for the SMSC address as described in Creating global title analysis .ESC=<escape code>:SDIG=<private number>. 7. Connect the SMSC to the GMSC/IWMSC as described in Connecting the SMSC to the SMS-GMSC/SMS-IWMSC Create SMSC routing analysis as described in Creating analysis on SMS application level in the MSC Set the SMSC number in the mobile station (+<country code><network code><number>) Create the MO-SMS and MT-SMS services to the MS in the HLR and provision the services in the VLR as described in Managing SMS subscriber-specific data Define and private numbering index for the subscriber whose IMSI is 244051154324 ZMSD:IMSI=244051154324:PNI=98345.LDIG=35834513888. Create global title analyses for the SMSC address as described in Creating global title analysis. 5.ESC=0:SDIG=3325. Create analysis for number 35834513888 and short code 3325 ZMPC:PNI=98345.LDIG=<long number>. 5. see Configuring network elements for SMS. Creating PNP numbering for SMS 1. 4. Steps 1. The SMS triggering detection points (MO-.SKEY=1111. 2. ZMQT:IMSI=244051112345:ACT=A.DP=MO. MT-.SCP=5678. Activating IN-SMS service in HLR (MQT) ZMQT:IMSI=<international mobile subscriber identity>:ACT=<activation status of service>. Status Report) with event detection points (EDPs).SCP=<service control point address>. Another application is that IN-SMS allows the subscriber to prevent SMs from a certain source and also to forward incoming SMs to another mobile user. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 185 (267) . see Configuring network elements for SMS .DP=<detection point>. Activating IN-SMS service Activate IN-SMS service with mobile-originating SM transfer. TAMM=N:. Background information is available in the feature description of Feature 910: IN Short Message Service . Handling IN SMS in subscriber data To create and modify IN SMS service data in the HLR.TAMM=<triggering all multiple messages>:. Further information: Example 29. You can delete the data with the MQD command and output it with the MQO command. make prepaid charging possible. SCP address 5678. for example. see IN Short Message functionality .Activating Nokia-specific SMS features 5. Related topics For related information.2 Handling of IN SMS IN Short Message Service (IN-SMS) allows you to create better services in the area of restricted mobility.SKEY=<service key>. service key 1111 and triggering type 'triggering to one SM' for a subscriber whose IMSI is 244051112345. implement new services based on SMS control. For more information. use the MQT command. and Managing SMS subscriber's data . and manage the interaction between GSM and IN services. SMS Guide 5.3 Activating Real Time triggering This functionality provides support to the Nokia Terminal Management Server to explore when a new subscriber or new mobile equipment appears in the network. Note Since the MSC/VLR can detect the international roamer, the number of trigger SMs can be increased significantly in those MSCs which serve an airport or country border area. Steps 1. Activate the feature (WOA) Activate the feature with the MTMS_DATA FIFILE parameter: ZWOA:2,714,A; 2 714 class identifier identifier of MTMS_DATA Note There is no separate activation parameter for the Real time triggering functionality. 2. Set IMEI checking on The IMEI checking has to be set on at least for new visitors. 3. Configure the SMSC address, the SMSC application address, and a virtual subscriber (WVS) a. Set the SMSC address ZWVS:TRIGSC=<SMSC address of the trigger SM>: NP=numbering plan>,TON=<type of number>; 186 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en Activating Nokia-specific SMS features b. c. Set the SMSC application address ZWVS:TRIGAC=<application address of the trigger SM>:NP=numbering plan>,TON=<type of number>; Set the common MSISDN number ZWVS:TMSISDN=<common MSISDN number of trigger SM>:NP=numbering plan>,TON=<type of number>; 4. Define the detection criteria (MXM) a. Event detection: inter-PLMN location update ZMXM:INPLU=Y; This parameter is used when the subscriber arrives from a foreign country, to set that the VMSC generates a trigger SM. Event detection: new visitor and previous LAI is zero ZMXM:NVLAI=Y; This parameter is used to set that VMSC generates a trigger SM when the subscriber arrives to the VLR and the subscriber's previous LAI is zero. Filtering criteria: HOME or VISITOR ZMXM:RSTAT=H; H V E home subscriber visitor subscriber every subscriber b. c. d. The HOME/VISITOR parameter makes it possible that either the HOME subscriber or the VISITOR subscriber is detected only, or both. Filtering criteria: MS_CLASSMARK ZMXM:MCLASS=PH2; PH1 PH2 PH3 Phase 1 and above equipments are triggered Phase 2 and above equipments are triggered Phase 3 equipments are triggered This parameter controls that either the newer mobile phone or every mobile phone is detected. 5. Activate Common MSISDN Sending dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 187 (267) SMS Guide Activate this functionality with the COMMON_MSISDN_SENT parameter. ZWOC:2,867,FF; 2 867 class identifier identifier of COMMON_MSISDN_SENT FF 6. value: TRUE Activate PLMN-specific Filtering Activate this functionality with the NTMS_PLMN_SPEC_FILT parameter. ZWOA:2,942,A; 2 942 class identifier identifier of NTMS_PLMN_SPEC_FILT 7. Activate/deactivate Real Time SM Sending Activate the functionality with the NTMS_REAL_TIME_SM_ACTIVE parameter. ZWOC:31,49,1; 31 49 1 class identifier identifier of NTMS_REAL_TIME_SM_ACTIVE value: TRUE Further information: For further details, see the feature description and the feature activation instructions ofFeature 1433: Terminal Management Support . For more background information, see Real Time triggering . 188 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en Activating Nokia-specific SMS features 5.4 Activating MT-SM for Camel Phase 4 Camel Phase 4 extends the available MT-SM services to the roaming subscribers. Steps 1. Activate the feature (WOA) Activate the feature with the CAMEL_ACTIVE parameter. ZWOA:41,2,04H; 41 2 04H class identifier identifier of CAMEL_ACTIVE value: TRUE Further information: For further details, see the feature description and the feature activation instructions of Feature 1364: MT-SM for Camel Phase 4 . 5.5 Activating Direct SM delivery The feature provides solution for direct SM delivery without involving the SMSC. Steps 1. Activate the feature (WOA) Activate the feature with the MSC_DELIVERED_SM parameter. ZWOA:2,991,A; 2 991 class identifier identifier of MSC_DELIVERED_SM Further information: For detailed information, refer to the feature activation instructions of Feature 1633: Direct SM delivery . dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 189 (267) SMS Guide 5.6 Activating B-IMSI retrieval in MO-side for MNP The feature provide solution for differentiated MO-SM charging for MNP by putting B-IMSI into the SM-MO CDR. Steps 1. Activate the feature (WOA) Activate the feature with the B_IMSI_FOR_MO_SM parameter. ZWOA:2,1029,A; 2 1029 class identifier identifier of B_IMSI_FOR_MO_SM 190 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en load sharing. 358400000003. the physical SMSC addresses are 358400000001.1 Working examples for SMS management Configuring network elements for short message services with load sharing In this example a real configuration is described with more clusters (gateways). Configure network elements for short message services where the logical SMSC address is 358400000000. and 358400000004. the VMSC addresses are 358411111111 and 358422222222. 358400000002. the destination point codes of the gateway MSCs are 340 and 341. and the destination point codes of the VMSCs are 301 and 302 (see the figure below). dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 191 (267) .Working examples for SMS management 6 6. and the service application being connected to where the operator wants a special routing. 192 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .SMS Guide SMSC-1 VMSC-1 NAMP G/IWMSC-1 Cluster 1 SMSCREMOTE-1 SMSCREMOTE-2 SMSC-2 HLR HPLMN SMSC-3 SMSCREMOTE-3 SMSCREMOTE-4 Cluster 2 VMSC-2 G/IWMSC-2 SMSC-4 Figure 62. the SMS routing support and SMS routing analyses to access NAMP can be done in the VMSCs. Note In the following examples the SMSC level can be set to S2 as well. This means that MO-SMs can be directly routed to G/IWMSC-1 without passing through G/ IWMSC-2. Real-life configuration with load sharing Note The G/IWMSC presented in the figure has gateway and interworking functions. If the VMSCs are connected to both G/IWMSCs. Steps 1.Working examples for SMS management In these examples no GT analyses have been defined previously. Group the VMSCs (NAC. In VMSC-1: ZNAC:NET=NA0.RI=GT. If yes. the result record index of the GT analyses starts from the first free record.RI=GT. ZNBC:::358400000001:1. ZNBC:::358400000000:1. Create a GT for G/IWMSC-2 ZNAC:NET=NA0. This grouping (defined for logical number) can be implemented through GT analyses in a way that the GT analyses for the logical SMSC address in all VMSCs in cluster 1 should point to G/IWMSC-1 and those in cluster 2 to G/IWMSC-2. NBC) Group the VMSCs (358411111111 and 358422222222) into two clusters. NBC) Create global title analyses in the HLR for all physical SMSC ISDNs pointing to their own G/IWMSCs. In VMSC-2: ZNAC:NET=NA0. ZNBC:::358400000003:2. so when creating GT analysis with the NAC command the resulting analysis is defined as result record index 1.DPC=340.DPC=341. b. a. the next GT analysis is defined as result record index 2. You can check whether there are already GT analyses defined in your system with the NAI command.DPC=341. ZNBC:::358400000000:1. Create a GT for G/IWMSC-1 ZNAC:NET=NA0. 2. ZNBC:::358400000004:2. b. a. Create global title analyses in the HLR for all physical SMSC ISDNs pointing to their own G/IWMSCs (NAC. ZNBC:::358400000002:1.RI=GT.RI=GT. and so on. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 193 (267) .DPC=340. In VMSC-1: ZNAC:NET=NA0. NBC) a.DPC=341. ZNBC:::358422222222:3.RI=GT.DPC=301. ZNBC:::358411111111:2.DPC=340. Create GT analysis in the G/IWMSCs for the logical SMSC-ISDN pointing to itself (NAC. b. In G/IWMSC-1: ZNAC:NET=NA0.RI=GT. Create a GT analysis in the G/IWMSC-2 for the physical SMSC-ISDN to route the SMs to NAMP (NAC. b. 5.RI=GT. ZNBC:::358400000000:1. 7.DPC=340.RI=GT.DPC=302. NBC) a. In G/IWMSC-1: ZNAC:NET=NA0.RI=GT. ZNBC:::358411111111:2. In G/IWMSC-2: ZNAC:NET=NA0. In G/IWMSC-2: ZNAC:NET=NA0.RI=GT. 6. ZNBC:::358400000001:2. Create GT analysis in both G/IWMSCs for the VMSC-ISDN to route MT-SMs (NAC. NBC) a.DPC=301. In VMSC-2: ZNAC:NET=NA0. 4. b. Create GT analysis in the G/IWMSCs for the physical SMSC addresses for Alert SC purposes pointing to themselves (NBC) 194 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .DPC=302. ZNBC:::358422222222:2. Create GT analysis in both VMSCs for the VMSC-ISDNs pointing to themselves (NAC. ZNBC:::358400000000:1. NBC) ZNAC:NET=NA0.RI=GT.SMS Guide 3. ZNBC:::358400000003:1.AEN:LEVEL=S3:ADD:SMSCREMOTE2. ZCFS:358400000001. 9. SAN=NAMP. ZCFS:358400000002. Create SMSC analyses to G/IWMSC-1 (CFS) ZCFS:358400000000. 358400000002) are needed for the Alert SC request routing. Further information: The execution printout of this command is the following: CREATING SMS ROUTING ANALYSIS PID SAP SAPTYPE SMSC ADDRESS TARIFF SERVICE CLASS APPLICATION NAME N 991 NAT 358400000001 . The analyses for the physical addresses (358400000001.NAMP COMMAND EXECUTED 10.AEN:LEVEL=S3:ADD:SMSCREMOTE1. In G/IWMSC-2 As in Step 3 this GT analysis has already been created. ZNBC:::358400000002:1. 8. result record 1 has to be used. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 195 (267) . Create an SMS routing analysis to access NAMP in both G/IWMSCs pointing to the physical SMSC-ISDN connected to NAMP (CFE) ZCFE:SAP=991. result record 1 has to be used.Working examples for SMS management a. Create SMS routing support analysis for the logical SMSC ISDN address (CFU) ZCFU:SMSC=358400000000. ZNBC:::358400000001:1.SAPTYPE=NAT:SMSC=358400000001. ZNBC:::358400000004:1.AEN:LEVEL=S3: ADD:SMSCREMOTE1.SMSCREMOTE2. b. In G/IWMSC-1: As in Step 3 this GT analysis has already been created. SMS Guide Note In this example the SMSC level can be set to S2 as well. use the CFI command. Expected outcome The execution printouts of the above commands are the following: CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL AENS = = = = 358400000000 ROUTE SM TO SMSC WITH AEN STANDARD PHASE 2+ SMSCREMOTE1 SMSCREMOTE2 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL AENS = = = = 358400000001 ROUTE SM TO SMSC WITH AEN STANDARD PHASE 2+ SMSCREMOTE1 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL AENS = = = = 358400000002 ROUTE SM TO SMSC WITH AEN STANDARD PHASE 2+ SMSCREMOTE2 COMMAND EXECUTED Further information: If you want to check the SMSC address analyses. 196 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . AEN:LEVEL=S3: ADD:SMSCREMOTE3. Create SMSC analyses to G/IWMSC-2 (CFS) ZCFS:358400000000.SMSCREMOTE4. ZCFS:358400000003.AEN:LEVEL=S3:ADD:SMSCREMOTE3. ZCFS:358400000004.AEN:LEVEL=S3:ADD:SMSCREMOTE4.Working examples for SMS management ZCFI:TYPE=SMSC. The example for the execution printout is the following: SMSC ADDRESS ANALYSES SMSC ADDRESS = 358400000000 RESULT = ROUTE SM TO SMSC WITH AEN SMSC LEVEL = STANDARD PHASE 2+ AENS = SMSCREMOTE1 SMSCREMOTE2 SMSC ADDRESS = 358400000001 RESULT = ROUTE SM TO SMSC WITH AEN SMSC LEVEL = STANDARD PHASE 2+ AENS = SMSCREMOTE1 SMSC ADDRESS = 358400000002 RESULT = ROUTE SM TO SMSC WITH AEN SMSC LEVEL = STANDARD PHASE 2+ AENS = SMSCREMOTE2 COMMAND EXECUTED 11. Expected outcome The execution printouts of the commands mentioned above are the following: CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL AENS = = = = 358400000000 ROUTE SM TO SMSC WITH AEN STANDARD PHASE 2+ SMSCREMOTE3 SMSCREMOTE4 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 197 (267) . SMS Guide CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL AENS = = = = 358400000003 ROUTE SM TO SMSC WITH AEN STANDARD PHASE 2+ SMSCREMOTE3 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL AENS = = = = 358400000004 ROUTE SM TO SMSC WITH AEN STANDARD PHASE 2+ SMSCREMOTE4 COMMAND EXECUTED Further information: If you want to check the SMSC address analyses. ZCFI:TYPE=SMSC. 198 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . that is. use the CFI command. The example for the execution printout is the following: SMSC ADDRESS ANALYSES SMSC ADDRESS = 358400000000 RESULT = ROUTE SM TO SMSC WITH AEN SMSC LEVEL = STANDARD PHASE 2+ AENS = SMSCREMOTE3 SMSCREMOTE4 SMSC ADDRESS = 358400000003 RESULT = ROUTE SM TO SMSC WITH AEN SMSC LEVEL = STANDARD PHASE 2+ AENS = SMSCREMOTE3 SMSC ADDRESS = 358400000004 RESULT = ROUTE SM TO SMSC WITH AEN SMSC LEVEL = STANDARD PHASE 2+ AENS = SMSCREMOTE4 COMMAND EXECUTED 12. Patch UTPFIL in both G/IWMSCs Patch UTPFIL in both G/IWMSCs. put the logical SMSC-ISDN (358400000000) to UTPFIL. c. ZDFS:CM. Patch the following three records ZDFS:CM. a.y+1. b.y. The new value for the record is: 9D 01 26 00 00 00 00 00. where x is the active CM and y is the record to be patched.x:5AC0007. Identify the active CM ZUSI:CM. The new value for the record is: 9D 01 25 00 0C 91 53 48. 12 = 0C) dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 199 (267) . where x is the active CM and y+1 is the record to be patched....y+2. where x is the active CM. where x is the active CM and y+2 is the record to be patched.x:5AC0007.x:5AC0007. ZDFS:CM. Note For compact MSCi the UTPFIL number is 5AC01017. Byte(s) 9D 01 25 00 5th byte in record 1 Explanation of bytes in UTPFIL records Explanation 019D (SMHPRB) index in SMHPRB number length of logical SMSC address (for example. Restart every CCSU unit one by one The meaning of the record is the following: Table 11.x:5AC0007.Working examples for SMS management Note This step is necessary only if you do not have Feature 1165: Short Message Service GSM Phase 2+ Enhancements in your network. The new value for the record is: 9D 01 27 00 FF FF FF FF. Find the first free record in CCSU-UTPFIL (= record full of zeros) ZDFD:CM. d.. the physical SMSC addresses are 358400000001 and 358400000002. It shows a possible configuration of network elements for short message services where the logical SMSC address is 358400000000.) Explanation number indicator first part of the number (for example. 00 00 00 00 ==> 00000000) end of the number (for example. FF FF FF FF) 5th .8th bytes in record 2 Explanation of bytes in UTPFIL records (cont. 200 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .2 Configuring network elements for short message services with more MSCs connected to the same SMSC This example shows that it is possible to connect more MSCs to the same SMSC . Byte(s) 6th byte in record 1 7th and 8th bytes in record 1 5th . 53 4 8 ==> 3584) continuation of the number (for example.8th bytes in record 3 6. the destination point codes of the gateway MSCs are 340 and 341 and the destination point codes of the VMSCs are 301 and 302 (see also the figure below). the VMSC addresses are 358411111111 and 358422222222.SMS Guide Table 11. the result record index of the GT analyses starts from the first free record. If yes. You can check whether there are already GT analyses defined in your system with the NAI command. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 201 (267) .Working examples for SMS management VMSC-1 G/IWMSC-1 Cluster 1 SMSCREMOTE-1 SMSCREMOTE-3 SMSC-1 NAMP HLR HPLMN G/IWMSC-2 SMSCREMOTE-2 SMSCREMOTE-4 SMSC-2 Cluster 2 VMSC-2 Figure 63. In the following examples the SMSC level can be set to S2 as well. the resulting analysis is defined as result record index 1. therefore when creating GT analysis with the NAC command. Real-life configuration with load sharing and more MSCs connected to the same SMSC Note The G/IWMSC presented in the figure has gateway and interworking functions. the next GT analysis is defined as result record index 2. and so on. In these examples no GT analyses have been defined previously. DPC=340. In VMSC-2: ZNAC:NET=NA0. Create global title analyses in the HLR for the physical SMSC ISDNs pointing to their own G/IWMSCs (NAC. 2.DPC=340. b. NBC) a. b. result record 1 has to be used. In G/IWMSC-2: ZNAC:NET=NA0. In VMSC-1: ZNAC:NET=NA0. Create global title analyses ZNBC:::358400000001:1.SMS Guide Steps 1.RI=GT. Create GT analysis in G/IWMSC1 (NBC) Create GT analysis in G/IWMSC1 for the physical SMSC addresses poiting to itself for Alert SC purposes.RI=GT. NBC) a. This grouping (defined for logical number) can be implemented through GT analyses in a way that the GT analyses in the VMSC in cluster 1 should point to G/IWMSC 1 and that in cluster 2 to G/IWMSC 2. ZNBC:::358400000000:1. Create a global title translation result ZNAC:NET=NA0.RI=GT.RI=GT. ZNBC:::358400000000:1. b.DPC=340. ZNBC:::358400000000:1. Group the VMSCs (NAC. As this GT analysis has already been created in the previous step. 202 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Create GT analysis in the G/IWMSCs for the logical SC-ISDN pointing to themselves (NAC.RI=GT. In G/IWMSC-1: ZNAC:NET=NA0. 4.DPC=341. ZNBC:::358400000002:1. NBC) Group the VMSCs (358411111111 and 358422222222) into two clusters. a. ZNBC:::358400000000:1.DPC=341. 3. Expected outcome The execution printout of this command is the following: dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 203 (267) . ZNBC:::358411111111:2. ZNBC:::358422222222:2.DPC=302. In VMSC-1: ZNAC:NET=NA0. ZNBC:::358422222222:2. a. Create SMS routing support analysis for logical SMSC ISDN address (CFU) ZCFU:SMSC=358400000000. In VMSC-2: ZNAC:NET=NA0. ZCFE:SAP=991. ZNBC:::358400000002:1.Working examples for SMS management ZNBC:::358400000001:1.RI=GT. 7. In G/IWMSC-2: ZNAC:NET=NA0. In G/IWMSC-1: ZNAC:NET=NA0. 8. NBC) Create GT analysis in both G/IWMSCs for the VMSC-ISDNs to route MTSMs. Create GT analysis in both VMSCs for the VMSC-ISDNs pointing to themselves (NAC. SAN=NAMP.RI=GT.DPC=301. ZNBC:::358411111111:2. b. 5. b.RI=GT.DPC=302. Create an SMS routing analysis to access NAMP (CFE) Create an SMS routing analysis to access NAMP in both G/IWMSCs poiting to the physical SMSC-ISDN connected to NAMP.RI=GT. NBC) a. 6. Create GT analysis in both G/IWMSCs (NAC.DPC=301.SAPTYPE=NAT:SMSC=358400000001. ZCFS:358400000001. ZCFS:358400000002.AEN:LEVEL=S3:ADD:SMSCREMOTE2. The analyses for the physical addresses (358400000001.AEN:LEVEL=S2: ADD:SMSCREMOTE1.SMSCREMOTE2.AEN:LEVEL=S3:ADD:SMSCREMOTE1. Note In this example the SMSC level can be set to S2 as well. Expected outcome The execution printouts of the above commands are the following: CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL AENS = = = = 358400000000 ROUTE SM TO SMSC WITH AEN STANDARD PHASE 2+ SMSCREMOTE1 SMSCREMOTE2 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND 204 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .SMS Guide CREATING SMS ROUTING ANALYSIS PID SAP SAPTYPE SMSC ADDRESS TARIFF CLASS - SERVICE APPLICATION NAME NAMP N 991 NAT 358400000001 COMMAND EXECUTED 9. Create SC analyses to G/IWMSC-1 (CFS) ZCFS:358400000000. 358400000002) are needed for the Alert SC request routing. use the CFI command.AEN:LEVEL=S3: ADD:SMSCREMOTE3. The example for the execution printout is the following: SMSC ADDRESS ANALYSES SMSC ADDRESS = 358400000000 RESULT = ROUTE SM TO SMSC WITH AEN SMSC LEVEL = STANDARD PHASE 2+ AENS = SMSCREMOTE1 SMSCREMOTE2 SMSC ADDRESS = 358400000001 RESULT = ROUTE SM TO SMSC WITH AEN SMSC LEVEL = STANDARD PHASE 2+ AENS = SMSCREMOTE1 SMSC ADDRESS = 358400000002 RESULT = ROUTE SM TO SMSC WITH AEN SMSC LEVEL = STANDARD PHASE 2+ AENS = SMSCREMOTE2 COMMAND EXECUTED 10.SMSCREMOTE4. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 205 (267) . Create SMSC analyses to G/IWMSC-2 (CFS) ZCFS:358400000000.Working examples for SMS management CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL AENS = = = = 358400000001 ROUTE SM TO SMSC WITH AEN STANDARD PHASE 2+ SMSCREMOTE1 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL AENS = = = = 358400000002 ROUTE SM TO SMSC WITH AEN STANDARD PHASE 2+ SMSCREMOTE2 COMMAND EXECUTED Further information: If you want to check the SMSC address analyses. ZCFI:TYPE=SMSC. AEN:LEVEL=S3:ADD:SMSCREMOTE3. use the CFI command. ZCFI:TYPE=SMSC.SMS Guide ZCFS:358400000001. The example for the execution printout is the following: SMSC ADDRESS ANALYSES SMSC ADDRESS = 358400000000 RESULT = ROUTE SM TO SMSC WITH AEN SMSC LEVEL = STANDARD PHASE 2+ AENS = SMSCREMOTE3 SMSCREMOTE4 SMSC ADDRESS = 358400000001 RESULT = ROUTE SM TO SMSC WITH AEN SMSC LEVEL = STANDARD PHASE 2+ AENS = SMSCREMOTE3 COMMAND EXECUTED 206 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Expected outcome The execution printouts of these commands are the following: CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL AENS = = = = 358400000000 ROUTE SM TO SMSC WITH AEN STANDARD PHASE 2+ SMSCREMOTE3 SMSCREMOTE4 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL AENS = = = = 358400000001 ROUTE SM TO SMSC WITH AEN STANDARD PHASE 2+ SMSCREMOTE3 COMMAND EXECUTED Further information: If you want to check the SMSC address analyses. ZDFS:CM. Find the first free record in CCSU-UTPFIL (= record full of zeros) ZDFD:CM. where x is the active CM and y+2 is the record to be patched.. where x is the active CM. where x is the active CM and y+1 is the record to be patched.x:5AC0007. c. ZDFS:CM. put the logical SMSC-ISDN (358400000000) to UTPFIL.. a.y+1.x:5AC0007. The new value for the record is: 9D 01 25 00 0C 91 53 48. Patch UTPFIL in both G/IWMSCs Patch UTPFIL in both G/IWMSCs. that is. d. b.. Restart every CCSU unit one by one dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 207 (267) .x:5AC0007.x:5AC0007. Note This step is necessary only if you do not have Feature 1165: Short Message Services GSM Phase 2+ Enhancements in use in your network.Working examples for SMS management 11. The new value for the record is: 9D 01 27 00 FF FF FF FF. You can find the meaning of the record in Table Explanation of bytes in UTPFIL records . where x is the active CM and y is the record to be patched. Patch the following three records ZDFS:CM. Identify the active CM ZUSI:CM. The new value for the record is: 9D 01 26 00 00 00 00 00.y+2..y. Note For compact MSCi the UTPFIL number is 5AC01017. and the destination point codes of the VMSCs are 301 and 302 (see also the figure below). it is recommended to utilize 2 BDCUs (do not necessarily be dedicated to SMS) in the MSC and create two LAN connections between MSC and SMSC and use 2 IP addresses for one SMSC. 358400000002. the destination point codes of the gateway MSCs are 340 and 341. The example shows a possible configuration of network elements for short message services where the logical SMSC address is 358400000000. Note It is not allowed to connect SMSC(s) having the same IP address to one MSC. 358400000003. and 358400000006. the VMSC addresses are 358411111111 and 358422222222. the physical SMSC addresses are 358400000001. The main difference between this example and the example given for Configuring network elements for short message services with load sharing. To utilise most effectively this interface and reach full redundancy. 358400000004. 358400000005.3 Configuring network elements for SMS with load sharing of SMSC clusters when the traffic category is normal traffic In this example a real configuration is described with TCP/IP interface between the network elements.SMS Guide 6. 208 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . is the way in which the G/IWMSC and the SMSC are connected. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 209 (267) . Real life configuration with load sharing of SMSC clusters Note The G/IWMSC presented in the figure has gateway and interworking functions.Working examples for SMS management SMSC cluster 1 SMSC-1 IP1 IP2 SMSC-2 NAMP G/IWMSC-1 Cluster 1 BDCU BDCU HLR HPLMN SMSC-4 LAN 1 BDCU BDCU G/IWMSC-2 LAN 2 IP8 SMSC-5 IP7 LAN 1 IP5 LAN 2 IP6 SMSC-3 IP4 VMSC-1 IP3 Cluster 2 VMSC-2 IP9 IP10 SMSC-6 IP11 IP12 SMSC cluster 2 Figure 64. Create a GT for G/IWMSC-2: ZNAC:NET=NA0. 2. If yes. NBC) Group the VMSCs (358411111111 and 358422222222) into two clusters. ZNBC:::358400000000:1. and so on. Create a GT for G/IWMSC-1: ZNAC:NET=NA0. In VMSC-1: ZNAC:NET=NA0. NBC) a. the next GT analysis is defined as result record index 2.DPC=340. a.DPC=341.DPC=341. b.SMS Guide In these examples no GT analyses have been defined previously. the result record index of the GT analyses starts from the first free record. the resulting analysis is defined as result record index 1.RI=GT. ZNBC:::358400000001:1. ZNBC:::358400000002:1. You can check whether there are already GT analyses defined in your system with the NAI command. ZNBC:::358400000006:2.DPC=340. so when creating GT analysis with the NAC command. ZNBC:::358400000004:2. b. In VMSC-2: ZNAC:NET=NA0.RI=GT. Steps 1.RI=GT. This grouping (defined for logical number) can be implemented through GT analyses in a way that the GT analyses for the logical SMSC address in all VMSCs in cluster 1 should point to G/IWMSC-1 and those in cluster 2 to G/IWMSC-2. ZNBC:::358400000003:1.RI=GT. ZNBC:::358400000000:1. ZNBC:::358400000005:2. Create global title analyses in the HLR for the physical SMSC ISDNs pointing to their own G/IWMSC (NAC. Group the VMSCs (NAC. 210 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . In G/IWMSC-2: ZNAC:NET=NA0. 5.RI=GT.RI=GT.Working examples for SMS management 3. 7.DPC=341.DPC=301.RI=GT.RI=GT. Create GT analysis in both G/IWMSCs (NAC. 4. Create a GT analysis in the G/IWMSC-2 for the physical SMSC-ISDN to route the SMs to NAMP (NAC. Create GT analysis in both G/IWMSCs for the logical SMSC-ISDN pointing to themselves (NAC. Create a GT analysis in G/IWMSC-1 for the physical SMSC-ISDN for NAMP pointing to itself (NBC) As this GT analysis has already been created in step 3 in the G/IWMSC-1 result record 1 has to be used. In G/IWMSC-1: ZNAC:NET=NA0.RI=GT. In G/IWMSC-2: ZNAC:NET=NA0. ZNBC:::358422222222:3.DPC=301. ZNBC:::358400000000:1. NBC) a. ZNBC:::358400000000:1. 6. In VMSC-1: ZNAC:NET=NA0. b. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 211 (267) . NBC) Create GT analysis in both G/IWMSCs for the VMSC-ISDNs to route the MT-SMs. b. NBC) ZNAC:NET=NA0.RI=GT. ZNBC:::358411111111:2. NBC) a.DPC=302. Create GT analysis in both VMSCs for VMSC-ISDNs pointing to themselves (NAC. a. In G/IWMSC-1: ZNAC:NET=NA0. ZNBC:::358400000111:1.DPC=340. ZNBC:::358400000111:2.DPC=340. SAPTYPE=NAT:SMSC=358400000111. SAN=NAMP. 9. ZNBC:::358400000003:1. Create an SMS routing analysis to access NAMP (CFE) Create an SMS routing analysis to access NAMP in both G/IWMSCs pointing to the physical SMSC-ISDN connected to NAMP. ZNBC:::358400000002:1.RI=GT. 10. In VMSC-2: ZNAC:NET=NA0. Create GT analyses in the G/IWMSCs (NBC) Create GT analyses in the G/IWMSCs for the physical SMSC addresses for Alert SC purposes pointing to themselves. ZNBC:::358400000006:1. ZCFE:SAP=991. ZNBC:::358400000005:1. ZNBC:::358400000004:1. b. ZNBC:::358400000001:1. ZNBC:::358411111111:2. In G/IWMSC-2: As this GT analysis has already been created in step 3 result record 1 has to be used. 8. In G/IWMSC-1: As this GT analysis has already been created in step 3 result record 1 has to be used.DPC=302. Expected outcome The execution printout of this command is the following: CREATING SMS ROUTING ANALYSIS 212 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . ZNBC:::358422222222:2. Create SMS routing support analysis for logical SMSC ISDN address (CFU) ZCFU:SMSC=358400000000.SMS Guide b. a. PASSW=PASSWORD: ADD:IP5.IP2..IP:LEVEL=S3.PASSW=PASSWORD: ADD:IP1.IP:LEVEL=S3.IP:LEVEL=S3:ADD:IP4.PASSW=PASSWORD: ADD:IP3 . ZCFS:358400000000. and so on.IP5. ZCFS:358400000111. ZCFS:358400000111.IP:LEVEL=S3.IP6. Create SMSC analyses for IP addresses one by one like this: ZCFS:358400000000..IP:LEVEL=S3..PASSW=PASSWORD: ADD:IP1.Working examples for SMS management PID SAP SAPTYPE SMSC ADDRESS TARIFF CLASS - SERVICE APPLICATION NAME NAMP N 991 NAT 358400000111 COMMAND EXECUTED 11. Confirm each command execution.IP:LEVEL=S3:ADD:IP2. ZCFS:358400000003. Create SC analyses to G/IWMSC-1 (CFS) ZCFS:358400000000.PASSW=PASSWORD: ADD:IP1.PASSW=PASSWORD: ADD:IP2. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 213 (267) . ZCFS:358400000002.PASSW=PASSWORD: ADD:IP3.IP:LEVEL=S3.IP:LEVEL=S3. ZCFS:358400000000..IP:LEVEL=S3.IP4. ZCFS:358400000001. ZCFS:358400000002.IP:LEVEL=S3:ADD:IP4.IP:LEVEL=S3.PASSW=PASSWORD: ADD:IP3. ZCFS:358400000001.IP3. 71 CONFIRM COMMAND EXECUTION: Y/N ? Y MODIFYING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 71 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND: SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 24. 358400000002. 72 214 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Expected outcome The execution printouts of the above commands are the following: CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172.175. It is important to define two IP addresses compulsorily belonging to one SMSC. In case of Alert SC there is no load sharing between the IP addresses. 24. 358400000003) are needed for the Alert SC request routing. the Alert SC sending will succeed through the other LAN.175. The analyses for the physical addresses (358400000001. 24.175. 71 172. and always the first IP address is used.SMS Guide ZCFS:358400000003.175. 24. because if one LAN breaks down.IP:LEVEL=S3:ADD:IP6. 24. 73 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND: SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 73 CONFIRM COMMAND EXECUTION: Y/N ? Y MODIFYING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 24. 24.175. 24. 71 172. 72 dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 215 (267) .175. 24.175. 71 172. 72 172. 24.175. 24.175.175.175. 72 CONFIRM COMMAND EXECUTION: Y/N ? Y MODIFYING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 71 172.175. 24. 72 172.Working examples for SMS management COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND: SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 71 172. 24.175.175. 24. 73 172. 72 172.175.175.175.175. 74 172.175.175. 24. 74 172. 24. 24. 24. 72 172. 24. 24. 71 172. 24. 71 172. 24. 74 CONFIRM COMMAND EXECUTION: Y/N ? Y MODIFYING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172.175.175. 24.SMS Guide 172.175. 75 CONFIRM COMMAND EXECUTION: Y/N ? Y MODIFYING SMSC ADDRESS ANALYSIS 216 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . 24.175. 72 172.175. 73 172. 71 172.175.175. 24. 73 172. 24.175. 24. 24.175. 73 172.175. 24. 75 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND: SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 74 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND: SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 24. 175. 73 172. 24. 24.175. 75 172. 74 COMMAND EXECUTED dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 217 (267) . 73 CONFIRM COMMAND EXECUTION: Y/N ? Y MODIFYING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000111 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172.175.175.175. 72 172.175. 71 172. 24. 73 172.175.175.175. 24. 24. 24. 76 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000111 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 24. 24. 74 172.175. 24.Working examples for SMS management SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 73 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND: SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000111 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 24. 24.175. 24. 71 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND: SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000001 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172.SMS Guide CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000001 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 71 CONFIRM COMMAND EXECUTION: Y/N ? Y MODIFYING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000001 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 72 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS = 358400000002 RESULT = ROUTE SM TO SMSC WITH IP SMSC LEVEL = STANDARD PHASE 2+ 218 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .175.175. 24. 24.175. 71 172. 175.175. 24. 24.175. 73 172.Working examples for SMS management PASSWORD IPS = PASSWORD = 172.175. 24.175. 24. 74 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000003 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 73 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND: SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000002 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 73 CONFIRM COMMAND EXECUTION: Y/N ? Y MODIFYING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000002 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 24. 75 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND: SMSC ADDRESS = 358400000003 dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 219 (267) . The execution printout should look like this: SMSC ADDRESS ANALYSES SMSC ADDRESS = 358400000001 RESULT = ROUTE SM TO SMSC WITH SMSC LEVEL = STANDARD PHASE 2+ PASSWORD = PASSWORD IPS = 172.175. 76 SMSC ADDRESS = 358400000111 RESULT = ROUTE SM TO SMSC WITH SMSC LEVEL = STANDARD PHASE 2+ PASSWORD = PASSWORD IPS = 172.175. 24. 74 SMSC ADDRESS = 358400000003 RESULT = ROUTE SM TO SMSC WITH SMSC LEVEL = STANDARD PHASE 2+ PASSWORD = PASSWORD IPS = 172. 76 COMMAND EXECUTED Further information: If you want to check the SMSC address analyses. 24. 24. 24. 74 SMSC ADDRESS = 358400000000 IP IP IP IP 220 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .175.175. 24.175.175. 24. 24. 75 172.175. 75 CONFIRM COMMAND EXECUTION: Y/N ? Y MODIFYING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000003 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 73 172. 75 172. 73 172. 72 SMSC ADDRESS = 358400000002 RESULT = ROUTE SM TO SMSC WITH SMSC LEVEL = STANDARD PHASE 2+ PASSWORD = PASSWORD IPS = 172.175. 24.175. use the CFI command.SMS Guide RESULT SMSC LEVEL PASSWORD IPS = = = = ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 24. 71 172.175.175. ZCFI:TYPE=SMSC. 24. 24. IP:LEVEL=S3:ADD:IP8. 24.IP12.PASSW=PASSWORD: ADD:IP7.175. Expected outcome The execution printouts of these commands are the following: CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS = 358400000000 RESULT = ROUTE SM TO SMSC WITH IP SMSC LEVEL = STANDARD PHASE 2+ dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 221 (267) . Create SMSC analyses for IP addresses one by one like in the previous step.PASSW=PASSWORD: ADD:IP9.PASSW=<PASSWORD>: ADD:IP7. 74 172. 24.175. ZCFS:358400000005.IP:LEVEL=S3.PASSW=PASSWORD: ADD:IP11.IP10.175. 24. ZCFS:358400000006.175.175.Working examples for SMS management RESULT = ROUTE SM TO SMSC WITH IP SMSC LEVEL = STANDARD PHASE 2+ PASSWORD = PASSWORD IPS = 172. ZCFS:358400000005. ZCFS:358400000004. 71 172. 24. 73 172.IP11. ZCFS:358400000006. 72 172. 24.IP8.IP9.IP:LEVEL=S3:ADD:IP10. 75 172. ZCFS:358400000004. Create SMSC analyses to G/IWMSC-2 (CFS) ZCFS:358400000000. Then confirm each command execution. 24.IP:LEVEL=S3.IP:LEVEL=S3.IP:LEVEL=S3.IP:LEVEL=S3:ADD:IP12.175. 76 COMMAND EXECUTED 12. 24. 78 CONFIRM COMMAND EXECUTION: Y/N ? Y MODIFYING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172.175.175. 77 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND: SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172.175. 77 CONFIRM COMMAND EXECUTION: Y/N ? Y MODIFYING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 24.SMS Guide PASSWORD IPS = PASSWORD = 172.175. 24. 77 172. 24. 24. 77 172. 78 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND: SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172.175. 24.175.175. 24. 77 222 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . 175. 24.175. 24.175.175. 78 172. 24.175. 79 172. 24. 80 CONFIRM COMMAND EXECUTION: Y/N ? Y MODIFYING SMSC ADDRESS ANALYSIS dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 223 (267) . 79 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND: SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172.175. 78 172.Working examples for SMS management 172.175. 24. 24. 24.175. 24.175.175. 77 172. 24. 24.175. 77 172. 77 172.175. 24. 24. 80 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND: SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 78 172. 79 172. 78 172.175. 79 CONFIRM COMMAND EXECUTION: Y/N ? Y MODIFYING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 24. 175.SMS Guide SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 78 172.175. 79 172. 78 172.175. 24. 80 172. 77 172. 80 172.175. 24.175.175. 24. 24.175. 24. 77 172.175.175. 24. 82 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS 224 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . 79 172.175. 78 172. 80 172. 24.175.175.175. 81 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND: SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 24. 24. 81 172. 24. 24. 24. 81 CONFIRM COMMAND EXECUTION: Y/N ? Y MODIFYING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000000 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 24. 24. 24.175. 79 172. 77 172. 24.175.175. 175. 24. 77 172. 77 CONFIRM COMMAND EXECUTION: Y/N ? Y MODIFYING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000004 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 24. 77 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND: SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000004 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 78 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000005 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 24.175. 24.Working examples for SMS management SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000004 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 79 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 225 (267) .175.175. 24.175. 81 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND: SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000006 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172.175. 79 CONFIRM COMMAND EXECUTION: Y/N ? Y MODIFYING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000005 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 81 CONFIRM COMMAND EXECUTION: Y/N ? Y 226 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . 24.175. 24.175.175.SMS Guide EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND: SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000005 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172.175. 24. 80 COMMAND EXECUTED CREATING/MODIFYING SMSC ADDRESS ANALYSIS NO EXISTING ANALYSIS FOR THIS SMSC ADDRESS FOUND CREATING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000006 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 79 172. 24. 24. 24. 79 172. 24. 77 172.175. 77 172. 82 SMSC ADDRESS = 358400000000 RESULT = ROUTE SM TO SMSC WITH SMSC LEVEL = STANDARD PHASE 2+ PASSWORD = PASSWORD IPS = 172. 82 COMMAND EXECUTED IP IP IP IP 13.175.175. 24.175.175. 24. 81 172. 24. 24.175. The example for the execution printout is the following: SMSC ADDRESS ANALYSES SMSC ADDRESS = 358400000004 RESULT = ROUTE SM TO SMSC WITH SMSC LEVEL = STANDARD PHASE 2+ PASSWORD = PASSWORD IPS = 172. 81 172. ZCFI:TYPE=SMSC. 80 172. 24.175. 82 COMMAND EXECUTED Further information: If you want to check the SMSC address analyses.Working examples for SMS management MODIFYING SMSC ADDRESS ANALYSIS SMSC ADDRESS RESULT SMSC LEVEL PASSWORD IPS = = = = = 358400000006 ROUTE SM TO SMSC WITH IP STANDARD PHASE 2+ PASSWORD 172. 79 172.175. 24.175.175.175. 81 172. 80 SMSC ADDRESS = 358400000006 RESULT = ROUTE SM TO SMSC WITH SMSC LEVEL = STANDARD PHASE 2+ PASSWORD = PASSWORD IPS = 172.175. 24. 24. 24. use the CFI command. 24. 24. 78 SMSC ADDRESS = 358400000005 RESULT = ROUTE SM TO SMSC WITH SMSC LEVEL = STANDARD PHASE 2+ PASSWORD = PASSWORD IPS = 172.175. Patch UTPFIL in both G/IWMSCs dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 227 (267) .175. 78 172. 24. where x is the active CM and y+1 is the record to be patched. Restart every CCSU unit one by one Further information: For the whole topic summary.SMS Guide Patch UTPFIL in both G/IWMSCs. put the logical SC-ISDN (358400000000) to UTPFIL.y. where x is the active CM. ZDFS:CM. Note For compact MSCi. the UTPFIL number is 5AC01017. where x is the active CM and y+2 is the record to be patched. a.x:5AC0007. The new value for the record is: 9D 01 26 00 00 00 00 00. The new value for the record is: 9D 01 27 00 FF FF FF FF. You can find the meaning of the record in Table Explanation of bytes in UTPFIL records . Find the first free record in CCSU-UTPFIL (= record full of zeros) ZDFD:CM. The new value for the record is: 9D 01 25 00 0C 91 53 48.. Identify the active CM ZUSI:CM. ZDFS:CM. Patch the following three records: ZDFS:CM.y+1. Note This step is necessary only if you do not have Feature 1165: Short Message Services GSM Phase 2+ Enhancements .x:5AC0007.. b.y+2. that is.. see Short Message Services Overview.. 228 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .x:5AC0007. c. d. where x is the active CM and y is the record to be patched.x:5AC0007. These deficiencies can cause delay in the SM transfer to subscribers.1 Problems related to SMS network elements The current SMS contains certain deficiencies in the service level because of some incomplete standardisation (3GPP TS 23. how to correct situations when subscribers do not receive their SMs or receive them twice. Discrepancy between MWF and MWD Situation: In some circumstances an error situation can occur where the MNRF is set in VLR but the MWD is not set in HLR. however. together with possible corrective methods. or vice versa. and the delivery of the SM fails. This is due to a signalling collision in the A interface and in the lower layers.002). see Short Message Services Overview. 7. In this case a subscriber is detached and switches his/her mobile on (IMSI attach) but receives no SMs. The defects that can occur because of incomplete standardisation are listed below.040 and 29. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 229 (267) . the signalling takes so much time that the SM arrives too early. or when SMS charging is not appropriate. ciphering and other activities are defined to take place during IMSI attach or location updating. can cause the subscriber not to receive SMs. This causes the MWD to be set again. because it causes only an additional indication of a mobile becoming reachable. or when the SM is not sent though the SMSC acknowledges the successful sending. and in the worst case the subscribers can be jammed out so that they are unable to receive SMs unless some corrective action is taken. If TMSI reallocation. For the whole topic summary. The latter. for example.Short Message Service Troubleshooting 7 Short Message Service Troubleshooting The following sections give instructions on what to do in case of problems related to SMS sending. when the mobile cannot yet answer to paging requests. The first one is not a problem. The reason is that the new VLR address is accepted in the HLR only after a certain period of time. It should now take about 5 seconds before subscriber B receives an SM after switching his/her MS on. Analysis You can check the status of the MWF and the provisioned SMS basic services for the subscriber with MML commands. The delay prevents SMs from arriving too early to the MSC. For more information. or manually by the operator. The SMSC address is set in the subscriber's MWD list. Give the following MML command: ZMJM:ALERT=5. thus it cannot clear the MWF. 230 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . the VLR does not receive the information. see Special conditions of unsuccessful MT-SM delivery.SMS Guide Only after a call or period location updating the VLR notices its MNRF and the delivery is attempted again. signalling delays can cause the old VLR to set its MNRF and to send an MWD to the HLR when the new VLR has no MNRF. and no knowledge of the MWD in the HLR. The MWD can only be cleared after a location update in the HLR. The VLR notices the MWF only after a call or a period location updating. and an SM is sent to him/her. Only priority SMs can be sent to the subscriber if the SMSC supports priority SMs. 7. When the MS is reachable again. Corrective action: Add delay to the sending of Alert-SC from HLR to SMSC so that the new VLR is ready to receive the SM. Analysis: During update location to a new VLR. the MWF is set in the VLR even if the subscriber does not have MTSMS basic service provisioned.2 Problems related to SMS A interface Subscriber does not receive SM after becoming reachable Situation: If a subscriber is temporarily away from the coverage area. This is done by using internal error codes in the MAP and X.25 protocols that both the MSCs and SMSC support. an 'absent subscriber' error indication is returned to the SMSC. which assumes that the HLR notifies SMSC when a subscriber is reachable again (MWF and MWD are set). Subscriber receives duplicated SMs Corrective action: CP DATA retransmission can be controlled in the PRFILE with the following A interface parameters. 000 TC1 MINIMUM default value 0 seconds allowed range from 0 (0 s) to 3000 (30 s) minimum duration of the timer TC1 controlling CP-DATA resending dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 231 (267) . If the SMSC receives 'invalid SME address' when delivering an MT-SM.Short Message Service Troubleshooting The VLR knows when the subscriber is registered in the VLR (IMSI attached) and does not respond to paging requests. Another way. The first model is implemented because the latter error code has other meanings as well. In this situation the subscriber is presumed not to be under the coverage area. Usually when paging fails. In this case both the MWF and the MWD are set. see Alarms and their meanings in Short Message Service. The SMSC polls the MS periodically with a priority SM to check if the subscriber has come to coverage area. Normally you do not need to modify these parameters: PRFILE class 31 SHORT MESSAGE SERVICE . is to change the 'absent subscriber' error indication to a 'system failure' towards the SMSC. Corrective action: One method of improving reachability is to change the 'absent subscriber' error indication towards the SMSC to another one which better indicates that the situation is temporary. This error cause indicates a temporary error situation in which the SMSC must poll the subscriber periodically because only the MWF is set in the VLR. For related information. that depends on the SMSC functionality. it indicates that the subscriber can be in a blind spot and does not answer to paging. despite the fact that the SMSC has delivered the SM successfully to MS-B.SMS Guide . Analysis: 232 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . a timer is started in the MSC. If any MO. ZCFI:type=conn_tbl. That timer controls the MO-SM transaction. In this case the MO-ACK arrives after the timer expiration. 001 TC1 DELTA value presented in 10 ms default value 0 no allowed range defined for this parameter delta to the timer TC1* value retrieved from the channel type and the short message length . as a help to identify the problem. therefore the SMRSE application has already sent MONACK towards MS-A. an advanced monitoring and checking possibility is provided with the CFI command.3 SMS problems related to SMRSE interface Some frequent problem situations caused by SMRSE interface configuration failures are presented below. If there is congestion somewhere in the SMRSE interface or the SMSC is temporarily overloaded. MS-A gets 'Message not sent this time' although MS-B receives the SM successfully Situation: Every time an MO-SM is sent to the SMSC. which allows you to obtain information on the current state of the SMRSE links. the MO-ACK message can arrive later than the default 10 s time limit. or connection establishment fails in the SMSC.and MT-SMS traffic breakdown happens. 002 CP_DATA_REPETITION default value 1 allowed range from 1 to 3 maximum number of CP-DATA message resendings See also Sections SMS-related general PRFILE/FIFILE parameters and Alarms and their meanings in Short Message Service . 7. MO timeout delayed MO/ALERT-ACK number of delayed MO/ALERT-ACKs . Corrective action: Increase the value of the timer controlling the MO-SM by setting the PRFILE parameter called SMRSE_MO_TIMER (31:38) to the appropriate value. then the parameter should be set to the default time plus the average delay time value). WRITE TIME: YYYY-MM-DD HH:MM:SS PARAMETERS: E-02 001C. This value should be the default value (10 s = 1000D) plus the maximum delay time (if the maximum delay time is much greater than the average delay time. This interval can be calculated by comparing the timestamps of that 'MO timeout' and 'Delayed MO/ALERT-(N) ACK' error log pair whose message reference in the user data information field is matching. .00009C10 USER TEXT : MO timeout.0000DF99 USER TEXT : Delayed MO/ALERT-ACK. The delay time of an MO-(N)ACK is the time which elapses starting form the MO timeout until the delayed MO-(N)ACK arrives and the 'Delayed MO/ ALERT-(N)ACK' error log is written. The following error logs indicate this error situation: .Short Message Service Troubleshooting Check the BDCU computer log of the SMS-IWMSC with the GSC service terminal command. USER DATA : 00F5 WRITE TIME: YYYY-MM-DD HH:MM:SS PARAMETERS: E-02 001C.09 s.00007650 00000001 000C. USER DATA : 00F5 Note dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 233 (267) .00007650 00000001 000C. these two errors indicate a different situation from the previous one: the MO-SM transaction was unsuccessful and MS-B did not receive the SM. For example. in case of the following MO-SM transaction. the delay is 0. However. The following error logs also indicate that there is some delay in the MO-SM processing: . which is identified by message reference 00F5. delayed MO/ALERT-NACK number of delayed MO/ALERT-NACKs . if you accidentally set the MO timer value too short (1. Consequently. a timer is started which controls that MT-SM transaction. If there is a congestion in the network towards the MS. 3. and those without message entry are negatively acknowledged back to the SMS application. or part of the NSS is overloaded. A radically increased MO timer value also means that the message entries in the MO pending table are kept reserved for a longer time. The setting of the SMRSE_MO_TIMER requires special attention because a timer which is not correctly configured can cause problems in the SM transfer. Consequently. and at the same time lots of incoming MOSMs. the SMSC re-sends this SM despite the fact that MS-B has successfully received it. the MT-ACK sent by the SMS application can arrive later than the default 90 s time limit. For example. you should set this parameter to a lower value than the MO control timer value of the SMS application in the SMSIWMSC. Analysis: Check the BDCU computer log of the SMS-GMSC with the GSC service terminal command.1 s instead of 11 s) it results in even more MO-NACK than before changing the parameter. 038 SMRSE_MO_TIMER default value 1000D (10 s) allowed range from 0 (0 s) to 2000D (20 s) SMRSE MO-SM response timer in SMS-IWMSC Subscriber receives duplicated SMs Situation: Every time the SMRSE application in the SMS-GMSC forwards an MT-SM to the SMS application. In this case the MT-ACK arrives after the timer expiration. there is no free message entry for every MO-SM.SMS Guide 1. the MO pending table can be filled up. 2. therefore the SMRSE application has already sent MT-NACK towards the SMSC. Change the SMRSE_MO_TIMER only if the problem described above occurs regularly. Configure the parameter very carefully to reach the optimal settings. so if there are several slow MO-transactions. which is 12 s by default. The following error logs indicate this error situation: 234 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Also. PRFILE class 31 SHORT MESSAGE SERVICE . 0000B3AD USER TEXT : MT timeout. The delay time of an MT-(N)ACK is the time that elapses starting form the MT timeout until the delayed MT-(N)ACK arrives and the 'MT entry not found' error log is written. the delay is 2.00007654 00000001 000C.46 s. Corrective action: Increase the value of the timer controlling the MT-SM by setting the PRFILE parameter called SMRSE_MT_TIMER (31:39) to the appropriate value. The following error log also indicates that there is some delay in the MT-SM processing: . in case of the following MT-SM transaction. USER DATA : 02E1 Note dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 235 (267) . For example. as opposed to the previous situation. This interval can be calculated by comparing the timestamps of that 'MT timeout' and 'MT entry not found' error log pair whose message reference in the user data information field is matching. USER DATA : 02E1 WRITE TIME: YYYY-MM-DD HH:MM:SS PARAMETERS: E-02 001C. in this case.00006D09 USER TEXT : MT entry not found.00007654 00000001 000C. so MS-B might not receive the SM several times. then the parameter should be set to the default time plus the average delay time value). MT timeout MT entry not found Delayed MT ACK (only in case of TCP/IP SMRSE application) . . This value should be the default value (90 s = 9000D) plus the maximum delay time (if the maximum delay time is much greater than the average delay time. delayed MT NACK (only in case of TCP/IP SMRSE application) However. the MT-SM transaction was unsuccessful. WRITE TIME: YYYY-MM-DD HH:MM:SS PARAMETERS: E-02 001C.Short Message Service Troubleshooting . which is identified by message reference 02E1. The setting of the SMRSE_MT_TIMER requires special attention. the value of this parameter can not exceed the MT control timer of the SMSC either. for example. Change the SMRSE_MT_TIMER only if the problem described above occurs regularly. For more information.4 Problems related to SMS charging Real charging information is not forwarded to the charging application Situation: It can happen that the subscriber. so if there are several slow MT-transactions and at the same time lots of incoming MTSMs. commits fraud. if you accidentally set the MT timer value too short it causes more MT-NACK. so its buffers can be filled more easily. the MT pending table can be filled up. 3. with longer MT timer the SMSC has to store the pending messages for a longer time.SMS Guide 1. That is. and this can result in congestion. PRFILE class 31 SHORT MESSAGE SERVICE . Configure the parameter very carefully to reach the optimal settings. Consequently. A radically increased MT timer value also means that the message entries in the MT pending table are kept reserved for a longer time. a too long MT timer can affect the retransmission of the unsuccessful MT-SMs in the SMSC. Analysis: 236 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . see MO-SM fraud prevention . On the other hand. Furthermore. pushes the 'red button') right after sending a short message and thus. removes the battery from the MS (or in some mobiles. For example. because a timer which is not correctly configured can cause problems in the SM transfer. 039 SMRSE_MT_TIMER default value 9000D (90 s) allowed range from 0 (0 s) to 15000D (150 s) SMRSE MT-SM response timer in SMS-GMSC 7. 2. there is no free message entry available for every MT-SM and these SMs are negatively acknowledged back to the SMSC. see Short message routing . and Short message charging . the subscriber forces the SMS application to inform the charging application about the MO-SM being unsuccessful despite the fact that the MO-SM was delivered to the SMSC successfully.Short Message Service Troubleshooting For example. Corrective action: You can use the 031:0025 CHAR_WITHOUT_ACK_TO_MS PRFILE parameter to prevent MO-SM fraud. For related information. if the subscriber removes the battery (or pushes the 'red button') right after sending a short message. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 237 (267) . SMS Guide 238 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . because it is possible that the MS has not received the first CP-DATA message at all. The SMS resending is performed only after the supervision time has exceeded. and varies between 3 . It is calculated from the SM length and varies between 1 .Additional information on SMS 8 8. timer T1 is set again in order to see whether the MS received the first CP-DATA message. The result is that no duplication is made as the MS has time to acknowledge this with the CP-ACK message: dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 239 (267) . It is calculated from the SMS length. this guard timer is set before the CP-DATA message is resent. T2 T5 T6 The following figure shows a case where a handover takes place after the MS has received the CP-DATA message. The time period after which the MS is likely to have received the CP-DATA message. If a handover is received during a time period after which the MS is likely to have received the CP-DATA message.15 seconds. The overall supervision time for the total SM transfer. and the MSC delays the SM resending. This may happen after the T5 has expired.1 Additional information on SMS MT operation in VMSC SMS resending In handover cases the MSC notices that a handover occurred and sets a new timer supervision that is greater than the one in the MS.20 seconds. If a handover is received during this time. The following logical timers are presented in the message sequences listed below: T1 Supervision for CP-ACK message when CP-DATA message is sent. SMS Guide MS CP-DATA MSC 1 MSC starts timers T1, T2 and T5 TO SIM MT-SMS 2 T5 has expired in MSC, T1 T2 are running FROM BTS handover 3 MSC starts timer T6 CP-ACT 4 T6, T1 and T2 are running in MSC resending causing duplication is avoided CP-DATA 5 CP-ACK 6 Figure 65. MT-SM in the MCS, channel handover, no SM resending 1. 2. 3. 4. 5. 6. The MSC sends an MT-SM to an MS in the CP-DATA message. The MS receives the MT-SM and begins to store it. The MSC is notified about the handover. The 10 second timer is started in the MS before the CP-ACK message is resent. The MS acknowledges that the MT-SM has been received. The MS sends a response to the MT-SM. The MSC replies that the MT-SM has been acknowledged by the MS. The following figure shows a case where a handover takes place after the MS has received the CP-DATA message, and the MSC delays the SMS resending. The CP-ACK message sent by the MS is lost and will be resent: 240 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en Additional information on SMS MS CP-DATA MSC 1 MSC starts timers T1, T2 and T5 TO SIM MT-SMS 2 T5 has expired in MSC, T1 T2 are running FROM BTS handover 3 MSC starts timer T6 FROM TIMER T6 4 CP-DATA 5 CP-ACK 6 CP-DATA 7 CP-ACK 8 Figure 66. MT-SM in the MSC, channel handover, SM resending takes place 1. 2. 3. 4. 5. 6. 7. 8. The MSC sends an MT-SM to an MS within the CP-DATA message. The MS receives the MT-SM and begins to store it. The MSC is notified about the handover. Supervision timer T6 expires. The SM resending takes place. The MS acknowledges that the MT-SM has been received. The MS sends a response to the MT-SM. The MSC replies that the MT-SM has been acknowledged by the MS. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 241 (267) SMS Guide The following figure shows a case where a handover takes place before the MS has received CP-DATA message, and the MSC resets timer T1, thus delaying the resending of CP-DATA message: MS CP-DATA MSC 1 MSC starts timers T1, T2 and T5 FROM BTS handover 2 T5, T1 and T2 are running in MSC T1 timer is set again CP-DATA 3 CP-ACK 4 5 CP-DATA CP-ACK 6 Figure 67. MT-SM in the MSC, channel handover, SM resending takes place 1. 2. 3. 4. 5. The MSC sends an MT-SM to the MS within the CP-DATA message. SMS resending takes place. Timer T1 expires, resulting in SM resending. The MS acknowledges that the MT-SM has been received. The MS sends a response to the MT-SM. The MSC replies that MT-SM has been acknowledged by the MS. The following figure shows a case where no handover takes place, but the MS does not reply at all. T1 expires, which results in the SM resending: 242 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en Additional information on SMS MS CP-DATA MSC 1 MSC starts timers T1, T2 and T5 CP-DATA 2 T1 has expired in MSC, T2 is running CP-ACK 3 4 CP-DATA CP-ACK 5 Figure 68. MT-SM in the MSC, T1 expires, SM resending takes place 1. 2. 3. 4. 5. The MSC sends an MT-SM to the MS within the CP-DATA message. SM resending takes place. The MS acknowledges that the MT-SM has been received. The MS sends a response to the MT-SM. The MSC replies that the MT-SM has been acknowledged by the MS. Values for timers The MSC has the timeout supervision T1 for CP-ACK. The timeout is calculated from the SM length according to the following rules: . Channel type is SACCH : (SMS_LENGTH/18)*0.96 sec + 6 sec + delta . Channel type is SDCCH : (SMS_LENGTH/20)*0.24 sec + 3 sec + delta dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 243 (267) SMS Guide If CP-ACK is not received during the time calculated on the basis of the channel type and SM length, it will be resent. Resending counts may vary from 1 to 3. Counts and timer delta values can be set in Parameter File (PRFILE), Class 31. In practice, timer T1 varies from 3.3 to 15 seconds, and SMS_LENGTH in the A interface from 33 to 172 octets. Timer T5 is related to T1, it is the part of T1 used for sending CP-DATA to the MS when T1 includes also the CP-ACK sent by the mobile station. Therefore T5 is estimated to be T1 - 5 seconds in SACCH channel, and T1 - 2 in SDCCH channel. Timer T6 is derived from the MS resending timer. In the MS the timer value is 10 seconds, therefore the MSC has the value of 13 seconds. Timer T2 is the maximum time that can be left for the A interface signalling. When the SM arrives through the MAP interface to the MSC, the maximum timeout in the SMS-GMSC for sending the MT-SM is 60 seconds. The 58 second timer is set for the VMSC MAP, and the 55 second time is left for the A interface. You can find an estimate of the worst case for T2 below: . If a handover takes place at the latest point when the resending is possible, the time is Start + T1 (that is, 15 s). The next step is to start resending the guard timer T6. T6 is 13 seconds (in MS 10 seconds, in MSC a margin of 3 seconds must be added). T6 expires, and resending takes place. T1 is started again, the time now is Start + T1 + T6 (that is, 15 + 13 s). The MS gives an acknowledgement just before T1 expires, the time now is Start + T1 + T6 + T1 (that is, 15 + 13 + 15 s). . . . If you want to make sure that a duplication exists, prepare to wait for responses for a long time. Here the total time would be 43 seconds, and that does not include MS paging, authentication, and what needs to be done before beginning to send an MT-SM. Also check when resending is possible, that is, how much time has already been consumed by comparing the present time with the time left in T2. For example, if several handovers take place, each of which causes T6 to be reset, there are 14 seconds left in T2 at the point when the last handover takes place, and T1 is calculated to be 15 seconds, stop the SM transfer. The reason for the interruption is that the time left would probably not be sufficient. For more information, see VMSC and VLR . 244 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en 11. 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. VMSC 5. 12. 10. VMSC 13. 2. HLR 9. B subs. 7. 1. SMSC 6.2 SMS procedures performed by MAP The following figure illustrates the MO-SMS and MT-SMS from the point of view of MAP: A subs.Additional information on SMS 8. SMS-GMSC 8. Figure 69. 3. 14. 2. RP-MO-Data FwdSMarg dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 245 (267) . 4. 13. When the routing information is received. 10. 9. Otherwise the SMS-GMSC transfers the SM to the VMSC. 4. 11. When the SMS-IWMSC receives a response for the SM from the SMSC. it transfers the SM to it. 7. SC_RP_MO_DATA SC_RP_MO_ACK FwdSMres RP-MO-Ack SC_RP_MT_DATA SRIforSMarg SRIforSMres FwdSMarg RP-MT-Data RP-MT-Ack FwdSMres SC_RP_MT_ACK The following paragraphs explain the procedures in detail: 1. 2. and the VMSC sends the operation in the TC-BEGIN message when it receives an SM from the MS. 12. 246 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . and the subscriber is registered in the MSC area in question (SMS-GMSC).SMS Guide 3. 5. it transfers the response to the VMSC. If the SMS-IWMSC knows the SMSC. 6. 14. MobileOrginatingSM The MO SMS procedures are used to forward an SM from a mobile subscriber to an SMSC . 8. a. the SMS-GMSC itself sends the MS to the MS. The MAP offers a procedure which can be used to transfer an MO-SM from the VMSC to the SMS-IWMSC . MO SMS transfer procedure in MAP version 1 and version 2: ForwardSM (FSM) begins a dialogue. 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. the HLR sends the result or an error message for SRI-SM in TC-END. b. . and the SMS-GMSC sends the operation in the TC-BEGIN message when it receives an SM from the SMSC. the HLR sends the result or an error message for the SRI-SM in the TC-END message. a. If the subscriber is reachable. several SMs can be transferred during the same dialogue. MT-SM transfer procedure in MAP version 1: ForwardSM begins a dialogue. In version 1. After receiving the response. The HLR can send an optional InformServiceCentre operation which is packed in the same network primitive as the SRI-SM result/error. 3. RoutingInfoEnquiryForSM procedure in MAP version 2: . After handling the procedure. only one SM can be transferred during a dialogue. MT-SM transfer procedure in MAP version 2: . . b. the SMS-GMSC may start ReportSMDeliveryStatus. The MAP offers a procedure which can be used to transfer an MT-SM from the SMS-GMSC to the VMSC. After handling the procedure.Additional information on SMS 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. and the SMSGMSC sends the operation in the TC-BEGIN message when it receives an SM from the SMSC. MT-SM transfer procedures offered by MAP are different in the MAP versions 1 and 2. RoutingInfoEnquiryForSM procedure in MAP version 1: SendRoutingInfoForSM (SRI-SM) begins a dialogue. in any case. The SendRoutingInfoForSM (SRI-SM) begins a dialogue. but in version 2. When the VMSC receives a response for the SM from the MS. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 247 (267) . . a. it transfers the response to the SMS-GMSC. MobileTerminatingSM The MT-SM transfer procedure is used to forward an SM or several SMs from an SMSC to a mobile subscriber. the VMSC sends him/her the SM. and the SMS-GMSC sends the operation in the TC-BEGIN message if it has received routing information from the HLR. it transfers the responses to the SMSC. indicating that the subscriber is registered in another MSC area. 4. it transfers the response to the SMS-GMSC. only the MAPOPEN-PDU is sent in the TC-BEGIN message. Furthermore. the VMSC sends an SM to it.SMS Guide The ForwardSM operation can appear several times in a dialogue. The ForwardSM begins a dialogue. The following figure illustrates a situation where MT-SM sending fails and the HLR is notified: 248 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . If the MS can be reached. and the message part is sent separately after that. If the message is too long to fit in the network message frame. the SMS-GMSC can inform this to the HLR by using the ReportSM-DeliveryStatus operation. The FSM is always acknowledged to the SMSC before the next SM is sent. If the MT-SM transfer fails. In the multiple SM transfer. the FSM service can be used several times. . 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. . in any case. . When the VMSC receives a response for the SM from the MS. After receiving the response. . ReportSM-DeliveryStatus Note This operation was called SetMessageWaitingData in the old specification. it transfers the responses to the SMSC. the SMS-GMSC can start the ReportSM-DeliveryStatus. 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. . or SM delivery failure with 'error cause MS memory capacity exceeded' indication is received from the visited MSC. ReportSM-Delivery Status arg d. FwdSMarg/res c. MT-SM sending fails. ReportSM-Delivery Status res The SMS-GMSC informs the HLR if an absent subscriber. unidentified subscriber. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 249 (267) . HLR Figure 70. SRIforSMarg/res b. HLR is notified The numbers given in the figure refer to the following: a. a. 3. if the MNRF and MCEF flags. 1. 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. and the corresponding flags received in the InformServiceCentre operation are not already set. ReportSM-DeliveryStatus (RSM-DS) begins a dialogue. or both. After handling the procedure. were set in the HLR. SMS-GMSC 4. and the SMS-GMSC sends the operation in the TC-BEGIN message when it receives ForwardSM response from the VMSC.Additional information on SMS SMSC VMSC 2. ReportSM-DeliveryStatus procedure in MAP version 1 and version 2: . the HLR sends the result or an error message for RSM-DS in the TC-END message. and the procedure does not contain any other operations. Alert-SC in MAP version 2 The Alert-SC operation begins the dialogue. If an error occurs in the HLR. a. FacilityNotSupported and SystemFailure. otherwise it sends an empty result for Alert-SC in the TC-END message. and the HLR sends the operation in the TC-BEGIN message. The ReadyForSM procedures offered by MAP are different in MAP versions 1 and 2. and the HLR receives ReadyForSM. The following figure illustrates the ReadyForSM and Alert-SC procedures: 250 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . while the MS not reachable flag (MNRF) is set. UpdateLocation or Supplementary Service Control request for this subscriber. DataMissing. it can start Alert-SC procedure to all SMSCs included in the subscriber's MWD. DataMissing. ReadyForSM When receiving the ProcessAccessRequest or UpdateLocationArea indication from the MS. a. b. 6. Alert-SC When the subscriber has an SMSC address or addresses in the MWD. the HLR sends an error message containing UnknownSubscriber. ReadyForSM in MAP version 2 The ReadyForSM operation begins a dialogue. Because this is a class 4 operation. the dialogue is ended immediately. and the VLR sends the operation in the TC-BEGIN message to the HLR. and the HLR sends the operation in the TC-BEGIN message to the SMS-IWMSC. and the procedure does not contain any other operations. the dialogue is ended immediately. and the VLR sends the operation in the TC-BEGIN message to the HLR. The Alert-SC procedures offered by MAP are different in MAP version 1 and 2. ReadyForSM in MAP version 1 The NoteSubscriberPresent operation begins and ends a dialogue. otherwise it sends an empty result for the ReadyForSM in the TC-END message to the VLR. b. Alert-SC in MAP version 1 The Alert-SC-WithoutResult operation begins and ends a dialogue.SMS Guide 5. the VLR starts the ReadyForSM procedure to the HLR. If an error occurs in the HLR. FacilityNotSupported and SystemFailure. the HLR sends an error message containing the UnknownSubscriber. Because this is a class 4 operation. 8. 4. NoteMSpresent (MAP 1) ReadyForSMarg 2. 2. Ready res AlertSCwithoutRes Arg (MAP 1) AlertSC Arg 4. AlertSCRes For more information. see MAP in SMS and Interfaces between SMS network elements .Additional information on SMS VMSC GMSC SMSC 1. 3. The SMS architecture in case of SMRSE over X.3 Comparison of the SMS functionalities in case of SMRSE over X. HLR Figure 71.25 or TCP/IP and SS7 MAP SMSC The DX 200 MSC/VLR enables you to use the SMSC with SMRSE or SS7 MAP connection. ReadyForSM and Alert-SC procedures The numbers given in the figure refer to the following: 1.25 or TCP/IP SMSC is the following: dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 251 (267) . 3. 25 or TCP/IP The SMS architecture in case of SS7 MAP is the following: 252 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .SMS Guide VMSC SMS-IWMSC MAP-E A MS MAP-E MAP-C SMRSE SMSC MAP-Gd SMRSE Gb MAP-Gd SGSN SMS-GMSC MAP-C HLR Figure 72. SMS architecture in case of SMRSE over X. SMS architecture in case of SS7 MAP Due to the different architecture.25 or TCP/IP and SS7 MAP SMSC Charging and statistics The charging and statistic functionalities in the SMS-IWMSC and the SMSGMSC are the following: . 8.1 Functional differences between SMRSE over X. Note that this section does not cover the functionalities provided with the SMRSE over TCP/IP SMSC. the provided functionalities are different in the cases given above.Additional information on SMS MS A VMSC SMSC MAP-E MAP-Gd MAP-C HLR SGSN Figure 73.3. See the following examples: dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 253 (267) . Creating CDR s Subscriber billing can be based on the CDRs generated in the SMSIWMSC and the SMS-GSMC. The charging of the command SM and/or the status report SM can be in the SMS-GMSC and the SMS-IWMSC when the home subscriber is out of the HPLMN. if the charging is in the SS7 MAP SMSC and the SMSC has an interface with the Billing Centre.25 over SMRSE SMSC. see Short message charging . The result of SMSC address analysis can be number modification or SMSC deny in case of SS7 SMSC. The SMs generated by applications can be charged in the SMSGMSC where the tariff class information is available. or when the destination home subscriber is out of the HPLMN. therefore in case of changing the SMS architecture the SMS routing analysis and the SMSC address analysis should be reconsidered in all MSCs. and SMS-related statistics . MAP measurement The SendRoutingInfoForSM and the ReportSM-DeliveryStatus operation are not counted according to the source in the MSC in case of MAP SMSC. 3. . . The logic of these analyses is strongly determined by the used SMS architecture. 2. Field reporting . Those home subscribers' SMs who are roaming out of the HPLMN can be charged in the SMS-IWMSC. it is preferable to include this information in SMS routing analysis results in every MSC of the HPLMN.SMS Guide 1. . 254 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Tips for checking the analyses: . If you uses tariff class information for charging SMs. the above cases can be handled also in the SS7 MAP SMSC. the result can be AEN(s) in case of X. however. the application generated SMs can be charged only in the SMS-GMSC. Beyond these results. . Routing of SMs to service applications The SMS routing analyses are used to route the SMs based on PID and/or prefix towards the proper SMSC. For more information. Online call monitoring (OLCM) and Lawfully Authorized Electronic Surveillance (LAES) information is not available from the SMS-IWMSC and the SMS-GMSC in case of MAP SMSC. The CDRs generated in the SMS-IWMSC and the SMS-GMSC are not available in case of SS7 MAP SMSC.service measurement T21 SHORT MESSAGE MT GMSC and T22 SHORT MESSAGE MO IWMSC counters are not updated in case of MAP SMSC. The MAP-Gd interface is also supported by the SS7 MAP SMSC. and routing to the SMS-GMSC in case of SMRSE SMSC. MAP interface The MAP operation SendIMSI is not available in case of MAP SMSC. the SCCP routings are also different: . For further information. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 255 (267) . see SMS-related general parameter file (PRFILE/ FIFILE) parameters . . Possible defects The function which provides corrective method for the incomplete standardisation problems (subscriber does not receive SM after becoming reachable. For further information about the function see the feature description of Feature 714: Short Message Service Enhancements .Additional information on SMS Additionally. the SS7 MAP SMSC implements the SendIMSI operation and fetches the subscriber's IMSI from the HLR. In MSC: using GT analysis. therefore the IMSI as a subscriber identifier cannot be used in charging. the result of the GT analysis should be the routing to the MAP SMSC in case of MAP SMSC. For related information. CHARGING BASED ON IMSI (feature 619): the value of this parameter has no effect SMS_EXT_MSG_REF_IN_X25 (feature 619): the value of this parameter has no effect MMS_SMSC_TIMER (feature 620): the value of this parameter has no effect . However. . PRFILE parameters without effects in case of MAP interface . In HLR: using GT analysis. discrepancy between Messages Waiting (MWF) and MWD ) does not work in case of SS7 SMSC. see Short message routing . and routing to the SMS-IWMSC in case of SMRSE SMSC. so the subscribers using only GPRS can send and receive short messages to and from the MAP SS7 SMSC. the result of the GT analysis should be the routing to the MAP SMSC in case of MAP SMSC. 256 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . Alert SC address in Alert message Identifying the SMSC to be used for the alerting procedure. IMSI and VMSC/SGSN address in Rp_Ack and RP_error message (MT case) IMSI and VMSC/SGSN address sent to the SMSC in MT SMS The IMSI number of subscriber B and the destination VMSC/SGSN address are sent to the SMSC (on the TCP/IP interface) in the MT SMS acknowledgement (RPAck and RPError) messages. In addition. MO logical SMSC address in Rp_timeout message Making the use of predefined SMSC addresses unnecessary through enabling that the status report is appropriate even if the operator has several SMSC addresses. . while in the RPError message both addresses are sent regardless of the HLR settings. The following message sequence shows how the parameters are sent in the RP_Ack message. The SMSC level has to be set to N3. . and the SMSC levels associated with them are described in the interface specification of MSC-SMSC Interface for TCP/IP in the MSC Specification . GSM Phase 2+ Enhancements . MAP version 3 is needed for this functionality. Note You can use this feature if you have the SMSC connected through SMRSE with TCP/IP. For details. The SMSC requires the IMSI and VMSC/SGSN data for statistical purposes. The following addresses can be transferred only if the SMSC level is set to N3.SMS Guide 8.4 Functions of SMSC level in SMS The available functions of SMS. . In the RPAck message the VMSC or the SGSN address is sent depending on which delivery was successful. if the SMSC charges for SMS. the VMSC address is a useful piece of information for locating subscriber B. refer to the feature activation instructions of Feature 1165: Short Message Services. Successful MT-SM transfer with two new parameters towards the SMSC 8. For more information. VMSC/SGSN) Figure 74. VMSC/SGSN) MAP_MT_FORWARD_ SHORT_MESSAGE Page Positive page response CP_DATA CP_ACK CP_DATA MAP_MT_FORWARD_ SHORT_MESSAGE _ACK CP_ACK SC_RP_ACK (IMSI.5 Alarms and their meanings in Short Message Service The following alarms may be issued in connection with SMS.Additional information on SMS SMSC SMSGMSC MAP_SEND_ ROUTING_INFO _FOR_SM HLR VMSC MS SC_RP_MT_DATA MAP_SEND_ ROUTING_INFO _FOR_SM_ACK (IMSI. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 257 (267) . see referential material on Alarms . This alarm is related to the A interface. This alarm is generated when CPDU encoding fails due to: 258 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . . . The effect on the functioning of the system and on the service received by the subscriber depends on the operation in question. In case of TCP/IP links. 1088. 2439.SMS Guide . This alarm is related to MAP protocol. for example. This alarm is related to X. an error occurred in the encoding of the TPDU . 1652. The data in the TPDU contains erroneous values. and as a result. HAND CREATION FAIL This alarm is issued if there is overload in the network or in one of the units. 1024. or in situations when the capacity is increased (especially in the transit MSC) because of heavy traffic. OPERATION TIMER EXPIRY An operation has been sent to the network. SMSC LINK FAILURE The system sets the alarm when SM sending to SMSC fails because of link failure.25 and TCP/IP link. Logical SMSC addresses cannot be alarmed. 1647. It is raised if there is a failed attempt for a connection. The priority of the alarm is three stars. but an acknowledgement to it has not been received fast enough. . The situation occurs if the SC address analysis is missing for the SMSC which tries to open a connection. Check the link state and connection parameters as well as hardware. The alarm is also used when the connection drops down in an unexceptional way. 1572. the alarm is generated only for physical SMSC addresses. SMSC ACCESS FAILURE This alarm is used to indicate an unauthorised attempt to create a connection. SMS SUBMIT PRIMITIVE ENCODING FAILURE Due to the use of the PNP service in the SMS. when the physical medium breaks down. . . The disturbance can indicate a routing problem. the ongoing dialogue is interrupted. DECODING ERROR OF THE MESSAGE RECEIVED FROM THE MS The alarm notifies the user about a message which was received from the MS and could not be decoded. The system clears the alarm automatically after recovery. or congestion in the network element to which the operation was sent. 25 link. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 259 (267) . This alarm is related to MAP protocol. The disturbance can be cleared by the operator. but no analysis can be found for this number in the MSC. This indicates that the protocol cannot send the operation to the network because its own subsystem does not function. . This alarm is related to X. protocol traffic is congested either partly or totally.25 link. The fault may affect the traffic capacity of the system. The identifier is used in an inquiry to find out the OSHORT identifier and the PSAP addresses. 2749. The alarm is caused by erroneous configuration of the system. SCCP ROUTING FAILURE The SCCP has failed in routing a message received from the user part of the SCCP. . CP-ERROR or CP-DATA) incorrect protocol identifier (not SMS) incorrect transaction identifier or when RPDU encoding fails due to: .Additional information on SMS incorrect message type (not CP-ACK. Due to the error situation. NO ANALYSIS FOR SMSC ADDRESS The HLR sends the number of the SMSC to the MSC in connection with the AlertSC operation. 2748. the alarm is generated. This alarm is related to X. NO ANALYSIS FOR SMSC AEN The number of the SMSC is analysed in connection with the AlertSC operation. MISSING MOLIMITER FOR SMSC LINK The missing_molimiter_a alarm is raised by ZIPBOX PRB during the connection establishment between the MSC and SMSC if there is no MO Limiter value in the SMR-BIND request for the given TCP/IP link and the SMS_ENHANCEMENT and the DYN_TCPIP_LOADSHARING PRFILE parameters are turned on. too long SM (TPDU ) incorrect SC address 2246. The result is the identifier of the remote application. 2646. If the inquiry fails. PROTOCOL ROUTING FAILURE A routing problem has been detected in a protocol dialogue. . 1224. or that a faulty routing address has been received from the network or from the user of the protocol. Also the identifiers of the O45LRS and the plug-in unit are received. . or that there is no global title translation for the routing address used. This alarm is related to MAP protocol. NUMBER_OF_MMS 031:0009 Maximum number of simultaneous MMS short messages. TC1_DELTA 031:0001 Delta to timer TC1* value retrieved from channel type and short message length. MMS_WAIT_TIMER 031:0007 Subsequent short message waiting timer. MMS_PHASE_1_MS_SUPPORT 031:0008 MMS is supported for phase 1 mobiles. CP_DATA_REPETITION 031:0002 Maximum number of CP-DATA message resending.SMS Guide 8. 260 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . MMS_SMSC_TIMER 031:0010 SMSC timer for subsequent short message in GMSC. SMS_QUEUING_TIME 031:0003 Maximum queuing time of short messages.6 SMS-related general parameter file (PRFILE/FIFILE) parameters The following PRFILE/FIFILE parameters are related to SMS: TC1_MINIMUM 031:0000 Minimum duration of TC1* timer. GPRS_SUPP_IN_SMSGMSC 031:0024 GPRS support in SMS-GMSC. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 261 (267) .Additional information on SMS SMS_EXT_MSG_REF_IN_X25 031:0013 Short Message Service. MAX_MO_REFERENCE 031:0017 Maximum number of concurrent MO short messages. MAX_MT_REFERENCE 031:0016 Maximum number of concurrent MT short messages.25 link. SELECT_SMS_CDR_GEN 031:0023 Suppress unnecessary CDR generation based on the SMSC address. IN_MM_FOR_SMS_ACT 031:0015 IN Short Message Service. Extended SMS message reference in X. CHARGING_BASED_ON_IMSI 031:0014 SMS charging based on IMSI. ALIVE_CHECK_INTERVAL 031:0019 Timer value for TCP/IP connection check. SMS_PORT_NUMBER 031:0018 TCP/IP port number for short message service. SMS_MAP_SMSCADDR 031:0031 SMSC address transfer on MAP. X25_LENGHT_ENC_SCHEME 031:0033 Encoding of SMS on X. IN_MM_FOR_SMS_MO 031:0034 Activation of MO-SMS IN-TDP. A_NUM_CHECK_IN_CONN 031:0037 262 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . DYN_TCPIP_LOADSHARING 031:0032 Dynamic loadsharing on TCP/IP links between MSC and SMSC.25 interface.SMS Guide CHAR_WITHOUT_ACK_TO_MS 031:0025 Fraud prevention in MO-SM. GEN_CDR_FOR_FIRST_SM 031:0028 Generation of a CDR only for the first message in the concatenated SM. IN_MM_FOR_SMS_MT 031:0035 Activation of MT-SMS IN-TDP. MO_SM_STATUS_REP_REQ 031:0027 Mobile-originated short message with the indication of status report requested. Additional information on SMS Checking the MSISDN number of the A-subscriber in the CONNECT operation (MT-VMSC. BDCU_UNHA_MSGS_LIM_OUT 012:0076 Overload control. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 263 (267) . MO_TIMER_SMRSE 031:0038 MO timer for the SMRSE interface operations. SCP_AVAILABILITY_TIMER 006:0036 SCP availability timer. WELCOME_SM 002:0681 Activation and use of the Welcome SM operation in the VMSC. SMS_FORW_IN_HLR 002:0851 HLR-based SMS CFU. BDCU_UNHA_MSGS_LIM_IN 012:0075 Overload control. MT_TIMER_SMRSE 031:0039 MT timer for the SMRSE interface operations. MT-SM). TCPIP_SMMT_OLC_USED 012:0074 Overload control. see Parameters needed for CAMEL SM . MMS-related parameters MMS_WAIT_TIMER 031:0007 Subsequent short message waiting timer. NTMS_REAL_TIME_SM_ACTIV 031:0049 Activation and deactivation of Real-time trigger SM sending. after which the gsmSSF aborts the dialogue with the gsmSCF if no response has been received from the gsmSCF. NUMBER_OF_MMS 031:0009 Maximum number of simultaneous MMS short messages. MMS_PHASE_1_MS_SUPPORT 031:0008 MMS is supported for phase 1 mobile stations. MMS_SMSC_TIMER 031:0010 SMSC timer for subsequent short message in GMSC. For related information. 8. CAMEL_ACTIVE (0041:0002) The parameter also indicates whether CAMEL is in use. 264 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en .7 Parameters needed for CAMEL SM CAMEL_TSSF_TIMER (0041:0004) The TSSF timer determines the time in 100 milliseconds.SMS Guide B_IMSI_FOR_MO_SM 002:1029 B-IMSI retrieval in MO side for MNP. the gsmSCF contact is possible if the MO-SMS-CSI has been provisioned to the sending subscriber.interface and MAP connection is released in the VMSC dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 265 (267) . In case of mobile-terminating short messages. 3 and 4 is active or deactive in the network element (MSC/VLR. 2. Class 31: Short Message Services . CAMEL phase 1. This means that originating short messages are handled with the control of CAMEL service if the parameter value is set to 4. With this parameter you can make sure that all CAMEL services (of all phases) provisioned to the gsmSCF can be used. or CAMEL phase 1. In CAMEL phase 1 only the active/deactive values are used. 8. CAMEL_SUPPORTED_PHASE (0041:0001) This parameter indicates which CAMEL phase is supported in the network element (MSC/VLR. in case of mobile-originating short messages. HLR).8 Parameters for SMS A-interface configuration Check and set the following PRFILE parameters controlling SMS queuing and multiple messages. 031:0003 SMS QUEUING TIME default value 3000 (30 s) allowed range is not limited but MAP timers require values less than 30 s maximum waiting time in the queue . 2 and 3. CAMEL phase 1. the gsmSCF contact is possible if the MT-SMS-CSI has been provisioned to the sending subscriber. 031:0007 MMS WAIT TIMER default value 90 allowed range from 0 to 300 how long subsequent short message is waited before the A. It controls whether no CAMEL functionality. HLR). CAMEL phase 1 and 2.Additional information on SMS That is. This means that originating short messages are handled with the control of CAMEL service if the parameter value is set to 3. This allows that normal SMs and DIRECT-SMs can be differentiated in the statistic report and CDRs. TRUE This parameter defines whether the more messages facility may be sent for phase 1 mobile stations. 266 (267) # Nokia Corporation Nokia Proprietary and Confidential dn98905102 Issue 5-0 en . DIRECT_SM_STA_CHA_INFO (031:0044) This parameter enables the MSC to change the SMSC address to predefined SMSC address.2 PRFILE parameters ROUTE_IND_MSC_DELIV_SM (031:0042) This parameter sets the preferred delivery route (MT-VMSC/Serving GPRS Support Node (SGSN)) for the DIRECT-SM. DIRECT_SM_STAT_REP_USED (031:0045) This parameter allows you to enable or disable the sending of status report (if it is requested by subscriber A) after successful direct SM delivery. which can be seen in the SMS measurement and charging data records.9.1 Parameters needed for Sending SMS without SMSC FIFILE parameter MSC_DELIVERED_SM (002:0991) This parameter controls the feature activation and deactivation. the SMSC can be informed about the MTSM delivery failure. DIRECT_SM_FAILURE_IND (031:0043) This parameter allows the MSC to set the reserved value of the TP-MTI field in the SUBMIT-MO-SM. 031:0008 MMS PHASE 1 SUPPORT default value TRUE allowed range FALSE.9 8. . 8. 031:0010 MMS SMSC TIMER 8.9. Thus.SMS Guide . FORW_SM_TO_SC_IF_SR_REQ (031:0047) If the MSC performs Direct SM delivery. If this parameter is set. the Service Application Name in SMS routing table has to decide whether Direct SM delivery is used for the arriving MO-SM. and MO-SM contains a status report request. the MSC forwards the MO-SM to SMSC but does not make Direct SM delivery DIRECT_SM_BASED_ON_SAN (031:0048) If MS-MS SMS routing is used in the network. dn98905102 Issue 5-0 en # Nokia Corporation Nokia Proprietary and Confidential 267 (267) . it is possible that subscriber A does not receive the Status report back.Additional information on SMS DIRECT_SM_FOR_PREPAIDS (031:0046) Using this parameter you can enable or disable direct SM delivery of MO-SMs initiated by prepaid subscribers with special routing category values (defined in UTPFIL).