1、 ETSI TR 102 529 V1.1.1 (2009-03)Technical Report Speech and Multimedia Transmission Quality (STQ);SMS Testing Guidelines;Measurement Methodologies and Quality AspectsETSI ETSI TR 102 529 V1.1.1 (2009-03) 2Reference DTR/STQ-00098m Keywords SMS, testing, scheduling ETSI 650 Route des Lucioles F-06921
2、 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.o
3、rg The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ET
4、SI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.ets
5、i.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoi
6、ng restriction extend to reproduction in all media. European Telecommunications Standards Institute 2009. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI re
7、gistered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI
8、TR 102 529 V1.1.1 (2009-03) 3Contents Intellectual Property Rights 4g3Foreword . 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Abbreviations . 5g34 General aspects of SMS functionality 6g34.1 Maximum character lengths . 6g34.2 Concatenated short messages
9、 . 6g34.3 SMSC queuing per destination/user . 7g34.4 SMSC retry mechanism 7g34.5 Alerting mechanism . 7g34.6 Triggering of the delivery procedure caused by the alerting mechanism . 8g34.7 SMSC behaviour at arrival of a new SM directed to the same destination/user . 9g35 SMS Testing guidelines 9g35.1
10、 Settings for SMS test and correlation between subsequent tests 9g35.2 Exemplary testing model - using one receiving terminal . 10g35.2.1 Effects of timeouts 11g35.2.2 Measurement flows. 11g35.3 Exemplary testing model - using two or more receiving terminals 12g35.4 Testing methods for concatenated
11、SMs 13g3History 14g3ETSI ETSI TR 102 529 V1.1.1 (2009-03) 4Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members,
12、and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp).
13、 Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the presen
14、t document. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee Speech and multimedia Transmission Quality (STQ). ETSI ETSI TR 102 529 V1.1.1 (2009-03) 51 Scope The goal of the present document is to point out all the aspects impacting SMS service measurement results, p
15、roviding many different approaches for SMS testing. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. Non-specific reference may be made only to a compl
16、ete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly availabl
17、e in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable for the
18、 application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. Not applicable. 2.2 Informative references The following referenced documents are not essential t
19、o the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. i.1 ETSI TS 102 250 (all parts): “Speech Processing, Transmission and Quality Aspects (S
20、TQ); QoS aspects for popular services in GSM and 3G networks“. i.2 ETSI TS 123 040: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Technical realization of Short Message Service (SMS) (3GPP TS 23.040)“. 3 Abbreviations For the purposes of t
21、he present document, the following abbreviations apply: HLR Home Location Register MNRF Mobile Not Reachable Flag MO Mobile Originated MS Mobile StationMWDL Message Waiting Data List ETSI ETSI TR 102 529 V1.1.1 (2009-03) 6QoS Quality of Service SM Short MessageSMS Short Message Service SMSC Short Me
22、ssage Service Center UDH User Data Header UDHI UDH Information VLR Visitor Location Register 4 General aspects of SMS functionality 4.1 Maximum character lengths The SMS service is designed to send up to 140 bytes of user data with a single SM. From a customers point of view, this leads to different
23、 amounts of available characters available to compose text messages, based on the encoding used. Table 1 provides an overview of the different available character sets including the maximum possible message lengths for a single SM. NOTE 1: Even if not all the available data is used from a customer p
24、erspective, e.g. if the actual text used for testing is less than 160 characters, the size of the user data element will stay constant. NOTE 2: Content integrity of single SMs is ensured by mechanisms on lower protocol layers of GSM and UMTS networks. Thus, there is - from an E2E testing perspective
25、 - no need to implement content integrity checking mechanisms on top of the SMS service. Table 1: Overview of the different available character sets including the maximum possible message lengths for a single SM Character set Encoding Maximum message length Default GSM alphabet 7-bit 160 characters
26、ANSI (e.g. Cyrillic) 8-bit 140 characters Unicode (e.g. Arabic, Asian) 16-bit (UCS2) 70 characters 4.2 Concatenated short messages In order to transfer text messages not fitting into a single SM, the text message can be split into multiple SMs containing a so called UDH (User-Data-Header), which wil
27、l lower the amount of available user data. The UDH is in general used to transfer additional information related to the user data of the SM and will vary in size. Please refer to TS 123 040 i.2 for a list of allowed UDH information elements (UDHI) defining possible ways to use the UDH. According to
28、TS 123 040 i.2, the UDH contains for each SM of a concatenated SM the indication that this single SM is part of a concatenated SM and will also provide information about the position of the SM within the long message. Thus, fewer characters can be transferred per single SM if this single SM is part
29、of a concatenated SM. Table 2 provides an overview of the maximum available characters of a single SM when using UDH to concatenate SM in order to form and send longer messages. Table 2: Overview of the maximum available characters of a single SM when using UDH to concatenate SM in order to form and
30、 send longer messages Character set Encoding Maximum message length using UDH for concatenation of SM Default GSM alphabet 7-bit 153 (160-7) characters ANSI (e.g. Cyrillic) 8-bit 134 (140-6) characters Unicode (e.g. Arabic, Asian) 16-bit (UCS2) 67 (140-6)/2) characters NOTE: For further details on S
31、MS, please refer to TS 123 040 i.2. ETSI ETSI TR 102 529 V1.1.1 (2009-03) 74.3 SMSC queuing per destination/user The SMSC platform maintains a single queue for every destination, storing the SMs in its memory buffers. Consequently, a newly arrived SM is added to the queue of the destination user. Th
32、is queuing method limits the SMSC to deliver SMs to the same destination based on arrival order. This queuing method causes the following behaviour: Before accepting an incoming SM, the queue length is verified and the message is accepted only if the queue for the specific recipient has not reached
33、the maximum allowed length. An incoming SM could trigger the delivery mechanism of all the queued SMs for the same destination. 4.4 SMSC retry mechanism In order to increase SMS reliability, SMSC platforms usually implement a mechanism to autonomously trigger the delivery procedure of an SM. This fe
34、ature is usually called “retry mechanism“ and the applied temporal plan is defined as a “retry scheme“. Usually, many delivery trials are foreseen within a retry scheme to achieve the foreseen goal of improving the perceived QoS of the Short Message Service, while reducing time between SM submission
35、 and delivery to its destination and increasing the delivery success rate. The applied “retry scheme“ is implementation-dependent and established based on the network operators plans. The time interval between two subsequent delivery attempts can vary from minutes to many hours. To avoid wasting net
36、work resources while optimizing the SMS delivery process, the retry scheme usually starts with time intervals of few minutes for the first attempts, gradually increasing up to many hours for subsequent trials. The retry mechanism also aims at ensuring SM delivery in case of fault of the following “a
37、lerting mechanism“. 4.5 Alerting mechanism If an SMS delivery is unsuccessful for a multitude of causes (terminal switched off, subscriber not reachable, etc.), the SM is stored in the SMSC for a subsequent delivery attempt. In order to trigger the new delivery procedure, different mechanisms can be
38、 utilized. The first is the above-mentioned retry mechanism, while the alternative is an alerting mechanism started by the HLR. In the following part of this clause, a detailed overview of the alerting mechanism will be provided. While delivering an SM to the foreseen destination, considering an MS
39、as the receiving party, a submission failure can happen due to unavailability of the destination. For example, the terminal of the receiving party could be switched off or could not be reachable due to poor radio signal power. In this case, the SMSC, as a consequence of the failed delivery attempt,
40、informs the HLR that the requested user is not reachable, setting the “Mobile Not Reachable Flag“ (MNRF) for that user. Furthermore, it adds its identifier to the Waiting Data List; this action, performed by the SMSC, has to be interpreted by the HLR as “there is at least one waiting SM for this use
41、r stored in the buffers of this SMSC“. The steps of the above-mentioned procedure are represented in the following scheme. ETSI ETSI TR 102 529 V1.1.1 (2009-03) 8SMS Delivery Procedure Unsuccessful Deliveryg44g62g90g3g296g367g258g336g400g855g882 g68g69g90g38 g894g68g381g271g349g367g286g3g69g381g410g
42、3g90g286g258g272g346g258g271g367g286g3g38g367g258g336g895g882 g68g116g24g62 g894g68g286g400g400g258g336g286g3g116g258g349g410g349g374g336g3g24g258g410g258g3g62g349g400g410g895g1005g895 g4g18g60g3g68g381g271g349g367g286g3g100g286g396g373g856g3g894g437g400g286g396g3g286g396g396g381g396g3g4g271g400g286
43、g374g410g3g94g437g271g400g272g396g349g271g286g396g895g1006g895 g68g381g271g349g367g286g3g69g381g410g3g90g286g258g272g346g258g271g367g286g3g38g367g258g336g1007g895 g68g286g400g400g258g336g286g3g116g258g349g410g349g374g336g3g24g258g410g258g3g62g349g400g410g94g437g271g400g272g396g349g271g286g396g3g396g
44、286g336g349g400g410g286g396g286g282g3g349g374g3g115g62g90g3g271g437g410g3g374g381g410g3g396g286g258g272g346g258g271g367g286g3g271g286g272g258g437g400g286g3g381g296g855g882g24g28g100g4g18g44g3g894g374g381g3g393g258g336g349g374g336g3g258g410g410g286g373g393g410g895g882g47g68g87g62g47g18g47g100g3g24g28
45、g100g4g18g44g3g894g374g381g3g393g258g336g349g374g336g3g258g410g410g286g373g393g410g895g882g4g17g94g28g69g100g3g94g104g17g94g18g90g47g17g28g90g3g894g393g258g336g349g374g336g3g258g410g410g286g373g393g410g895g47g374g3g258g367g367g3g410g346g286g3g258g271g381g448g286g3g373g286g374g410g349g381g374g286g282
46、g3g272g258g400g286g400g853g3g410g346g286g3g68g69g90g38 g894g68g381g271g349g367g286g3g69g381g410g3g90g286g258g272g346g258g271g367g286g3g38g367g258g336g895g3g349g400g3g400g286g410g1005g1006g1007g1005g1006g1007g44g62g90g94g68g94g882g18g100g90g876g94g100g87g115g62g90g1005g115g62g90g1006Figure 1: SMS Del
47、ivery Procedure - Unsuccessful Delivery The above-mentioned MNRF flag is also implemented in the VLR. As a consequence, when the user becomes unreachable for one of the above-mentioned reasons, the VLR autonomously sets the MNRF flag. The duplicate implementation of the MNRF aims at increasing the e
48、fficiency of the alerting mechanism. In the following, the details and motivations of this double information are explained. 4.6 Triggering of the delivery procedure caused by the alerting mechanism In the following, the alerting method is explained by means of two different examples. EXAMPLE 1: MS
49、Procedure involving HLR: Considering a terminal being initially switched off. After switching it on, the registering procedure will inform the HLR that the user became reachable. If, for the respective user, the HLR detects an MNRF flag set to 1, it will change this value to 0, taking into account the list of SMSCs storing SMs for that user, reported in the “Message Waiting Data List“ (MWDL). Subsequently, the HLR will inform each SMSC in the above-mentioned MWDL, sending an alerting message using the MAP primitive “MAP-ALERT-SERVICE-CENTRE“. As a conse
