1、ETSI ES 202 912-9 1.1.1 (2003-02) ETSI Standard Access and Terminals (AT); Short Message Service (SMS) for PSTNIISDN; Test Suites for SMS User Based Solution; Part 9: Test Suite Structure and Test Purposes (TSS Essential, orpotentially Essential, IPRs notlJied to ETSI in respect ofETSI standards“, w
2、hich is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (5). All published ETSI deliverables shall include information which directs the reader to the above source of information. Foreword This ETSI Standard (ES) has been produced by ETSI Technical Committee
3、Access and Terminals (AT). The present document is part 9 of a multi-part deliverable. Full details of the entire series can be found in part 1 1 i. ETSI 5 ETSI ES 202 912-9 VI .I .I (2003-02) 1 Scope The present document provides test suite structure and test purposes for Functional tests for a Ter
4、minal Equipment implementing the Short Message Service (SMS) for PSTNASDN, UBS Protocol 2 according to ES 201 912 i. Basic ISDN or PSTN call procedures apply in order to establish a circuit-switched band connection between such Terminal Equipment and an SM-SC. Tests for these procedures are outside
5、the scope of the present document, although some parameters related to these procedures are used (e.g. SME subaddressing). UBS2 terminals send and receive Data Link messages in the voice-band connection using the FSK signalling as defined in EN 300 659-2 3 and ES 200 778-2 6. Tests for the FSK signa
6、lling are outside the scope of the present document. Tests for Data Link Layer have been treated in ES 202 912-5 12. Terminal Equipment implementing the Short Message Service (SMS) for PSTNASDN according to UBS Protocol 2 are required to implement the Transfer Layer according to ES 201 912 i. The Re
7、mote Single Layer Embedded Test Method (see ISO/IEC 9646-2 9) is used for the UBS Protocol 2 Transfer layer. Figure 1 gives an overview of the reference architecture used for the UBS Protocol 2 operation. Figure 2 shows the configuration used for testing. ISO/IEC 9646-1 8 and ISO/IEC 9646-2 9 are us
8、ed as the basis for the test specification methodology. 2 Re fe re nces The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication andor edition number or version n
9、umber) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. Referenced documents which are not found to be publicly available in the expected location might be found at htlu:/docbox.etsi.or:eerence. il ETSI ES 201 912
10、 (Vl.l.1): “Access and Terminals (AT); Short Message Service (SMS) for PSTNASDN; Short Message Communication between a fixed network Short Message Terminal Equipment and a Short Message Service Centre“. ETSI EN 300 659-1 (V1.3.1): “Access and Terminals (AT); Analogue access to the Public Switched Te
11、lephone Network (PSTN); Subscriber line protocol over the local loop for display (and related) services; Part 1 : On-hook data transmission“. ETSI EN 300 659-2 (V1.3.1): “Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Subscriber line protocol over the loc
12、al loop for display (and related) services; Part 2: Off-hook data transmission“. ETSI EN 300 659-3 (V1.3.1): “Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Subscriber line protocol over the local loop for display (and related) services; Part 3: Data link
13、 message and parameter codings“. ETSI ES 200 778-1 (V1.2.2): “Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Protocol over the local loop for display and related services; Terminal equipment requirements; Part 1 : On-hook data transmission“. ETSI ES 200 7
14、78-2 (V1.2.2): “Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Protocol over the local loop for display and related services; Terminal equipment requirements; Part 2: Off-hook data transmission“. ETSI 6 ETSI ES 202 912-9 VI .I .I (2003-02) 71 ETSI ES 202
15、912-4 (Vl.l.1): “Access and Terminals (AT); Short Message Service (SMS) for PSTNASDN Test Suites for SMS User Based Solution; Part 4: Protocol Implementation Conformance Statement (PICS) proforma specification user side for Data Link Layer Protocol 2“ ISO/IEC 9646- 1 : “Information technology - Open
16、 Systems Interconnection - Conformance testing methodology and framework - Part 1 : General concepts“. ISO/IEC 9646-2: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification“. ISO/IEC 3 166-1: “Codes for the
17、representation of names of countries and their subdivisions - Part 1 : Country codes“. ETSI ES 202 912-1 (Vl.l.1): “Access and Terminals (AT); Short Message Service (SMS) for PSTNASDN; Test Suites for SMS User Based Solution; Part 1 : Protocol Implementation Conformance Statement (PICS) proforma spe
18、cification user side for Data Link Layer (DLL) Protocol 1“. ETSI ES 202 912-5 (Vl.l.1): “Access and Terminals (AT); Short Message Service (SMS) for PSTNASDN Test Suites for SMS User Based Solution; Part 5: Test Suite Structure and Test Purposes (TSS election Expr.: ream ble: -est description: ass cr
19、iteria: ostam ble: Test Purpose identifier like CON-OUT-EST-VB-O1 Reference to one or more clauses of ES 201 912 I, containing a requirement which is tested in connection with the current test purpose. References to standards other than ES 201 912 I are added if appropriate. Since ES 201 912 I is th
20、e basic standard on which this test specification relies, the first paragraph of the “Requirem. ref.“ cell contains only clause numbers, without identifying the standard explicitly. Whenever a reference to another standards are necessary, a new paragraph is added, identifying the standard, followed
21、by a colon and then clause numbers as for ES 201 912 I. Example : 6.3.2.1, table5; B.1.4.1 EN 300 659-2 3,clause 7.3.1 When an entry is present here, it denotes a selection expression (see clause 6.6), specifying a condition for the applicability of this test purpose. If there is no entry, the test
22、purpose is unconditionally applicable. Note that selection expressions can also be defined for a whole group of test purposes, .e. outside a test purpose table. Name of a Dreamble leadina to a condition or state. where the test DurDose can be verified. Sequence of events intending to lead to the ver
23、ification of the test purpose. A TTCN-like notation is used (see clause 6.5). Note that unexpected events are not shown here. Special indication of an event (or several events), an “ignore“-behaviour or specific received parameter vaiue(s), being essential for the verification of the test purpose. T
24、his can be a copy of one or more lines of the “Test description“, or can be a textual explanation. None or name of a Dostamble leadina to the IDLE condition of the IUT (no VB connection exists. 6 Test purposes presentation and environment specif cat ion 6.1 I n trod u ction After the definition of t
25、he Test Suite Structure, a suitable environment has to be created in order to formulate the test purpose descriptions properly (i.e. referring to elements of this environment). Apart from this, the environment is specified to support a systematic transition from the test purposes to the TTCN ATS. Th
26、is is e.g. taken into account in the naming conventions and “atomic phrases“ used in the descriptions. “Test parameters“ and other objects have been collected during the test purposes development, which will find their entry in the ATS, with few modifications, e.g. as TS Parameters. ETSI 12 PCO 1 ET
27、SI ES 202 912-9 VI .I .I (2003-02) ASP Name Di recti on OUTGO1 N G-CALL- req LT-UT 6.2 OUTG-SM-TE-STATUS-req Test Suite Structure (TSS) LT-UT Table 1 shows the structure of the UBS2 Functional tests Test Suite, as well as the TP group identifiers and the number of test purposes produced, per subgrou
28、p and in total. SU BM-RESU LT-VERI F-req SUBM-RESULT-VERIF-conf DIS PL-I N F-VERI F-req DISPL-INF-VERIF-conf STAT-RE P-I N F-VERI F-req Table 1: Test suite structure for Functional tests for UBS2 LT-UT UT-LT LT-UT UT-LT LT-UT Group Subgroup TL format and contents Incoming SMS call Status report rece
29、ption IPublic Kev Memory full Total: Subgroup Submit message Submit Report reception Valid Invalid Valid Invalid Group Ide nt if er I Count UBS2-FT-OUT-TL-SUBMIT I 17 UBS2-FT-INC-STATUSREP 2 UBS2 FT INC PUKEY VAL 1 - - - UBS2-FT-INC-PUKEY-INV 1 U BS2-FT-I NC-M EM 2 52 6.3 Abstract Service Primitives
30、 Three classes of ASPS are defined, according to the PCOs at which they operate (see figure 2): PCO ASP class O: FS: cc: ASPs related to the operator (Upper Tester), ASPs for SM-related to the transmission and reception of TL messages via DLL messages, and ASPs related to connection control. Table 2
31、 describes the general functions of the ASPs operating at the 3 PCOs. Detailed descriptions of the ASPs together with their parameters follow. Table 2: List of ASPs Description Make the SM-TE initiate a VB connection to the SM-SC in order to send an SM. Request the user to send an SM-TE-STATUS messa
32、ge when the “memory full“ condition has ceased to exist (if automatic sending of SM-TE-STATUS message under these circumstances is not implemented). Request the user to verify if the SM-TE indicates the acceptance or rejection of the submitted SM. Indication by the user if the SM-TE has indicated th
33、e acceptance or rejection of the submitted SM. Request the user to verify the sequence of text characters of the received SM (it may also be used to request the user to verify that a SM replacement has occurred). Indication by the user if the text displayed by the SM-TE is the expected text (and, in
34、 case of a SM replacement, if the second received SM has replaced the first one). Request the user to verify whether the information contained in the received SMS-STATUS-REP message and concerning the outcome at the recipient of an SM previously sent is made available to the user. ETSI 13 ETSI ES 20
35、2 912-9 VI .I .I (2003-02) STAT-REP-NOTIF-NUM-VERIF-req LT-UT Description Indication by the user that the information contained in the received SMS-STATUS-REP message and concerning the outcome at the recipient of an SM previously sent is made available to the user. Request the user to verify that t
36、he “Notification number“ received in an SMS-STATUS-REP message is made available to the user. STAT-REP-NOTIF-NUM-VERIF-conf S M- Rece ptio n- req S M- Rece ptio n-co nf SM-Reception2-req SM-Reception2-conf PUB L- KEY- PASSW D- req UT-LT LT-UT UT-LT LT-UT UT-LT LT-UT U B L- KEY- PASSW D-co nf EMPTY-
37、M EM-req EM PTY-M EM-ind CC INC-CALL-req Indication by the user that the “Notification number“ received in an SMS-STATUS-REP message is made available to the user. Request the user to check if the incoming SM has been UT-LT LT-UT UT-LT LT-LTS received by the SM-TE (see note). Indication bv the user
38、if the incoming SM has been - OUTG-CALL-resp received bythe SM-TE (see note). - Request the user to check if two incoming SMs within the same SMS call have been received by the SM-TE. Indication by the user if two incoming SMs within the same SMS call have been received by the SM-TE. Request the use
39、r to verify that an SM received with a public key corresponding to one of the values stored in the SM-TE, can be read when the appropriate password is entered. Indication by the user that an SM received with a public key corresponding to one of the values stored in the SM-TE, can be read when the ap
40、propriate password is entered. Request the user to delete the SMs stored in the SM-TE to make the SM-TE memory again available. Indicates that the SM-TE does not contain anymore stored SMs. Make the Lower Test System initiate the basic call control procedures for an incoming call, to establish a VB
41、connection from the SM-SC to the SM-TE. LT-LTS INC-CALL-conf LTS-LT CC FS CALL- RE LEAS E- in d LTS-LT CALL-RELEASE-req LT-LTS TRANSFER- INFO- MT- req LT-LTS TRANS FER-ACK-req LT-LTS TRANSFER-SUBMIT-ind TRANSFER-SM-TE-STA-ind TRANSFER-DELL-REP-ind NOTE: Depending on the kind of the received short me
42、ssa! could be stored or displayed or used just to change Derform an action. etc . LTS-LT LTS-LT LTS-LT The Lower Test System confirms that the requested basic call control procedures for an incoming call have been successfully completed and the VB connection to the SM-TE is established, or that the
43、connection attempt was not successful. Indication that the SM-TE has initiated the basic call control procedures for an outgoing call. Response to the Lower Test System that the basic call control procedures for an outgoing call have to be completed or refused. Indication from the Lower Test System
44、that the VB connection has been released by the SM-TE. Request the Lower Test System to release the VB connection. Request the Lower Test System to transfer an SMS-DELIVERY TL message or an SMS-STATUS-REP TL message, via the DLL-SMS-INFO-MT message, to the IUT on the established VB connection. Reque
45、st the Lower Test System to transfer an SMS-SUBMIT-REP TL message, via the DLL-SMS-ACKI message or the DLL-SMS-ACKO message, to the IUT on the established VB connection. Indication that the IUT has sent an SMS-SUBMIT TL I message to the tester on the established VB connection. Indication that the IU
46、T has sent an SM-TE STATUS TL message to the tester on the established fB connection. Indication that the IUT has sent an SMS-DELIVERY-REP TL message to the tester on the established VB connection. Je and the terminal implementation the received SM the terminal settings or state, or to make the term
47、inal ETSI 14 ETSI ES 202 912-9 VI .I .I (2003-02) Default value SMS“ Tables 3 to 3 1 contain the descriptions of the ASPS used in the present document, including the ASP parameters (if any) and the kinds of values these may assume. No ASP parameter is optional. Default values are indicated for most
48、of the ASP parameters. The meaning of “Default value“ is: If the ASP is applied in a TP behaviour description and no value is indicated explicitly for an ASP parameter, then the application of the default value is assumed. Whenever a value is explicitly indicated for an ASP parameter, this value rep
49、laces the default value (at this instance of ASP application). Description Media Identifier “SMS“: the SM to be submitted is addressed to an “FAX“: the SM to be submitted is addressed to a FAX. “E-mail“: the SM to be submitted is addressed to an electronic mailbox. “ConvMail“: the SM to be submitted is intended to be delivered as Conventional Mail. “TELEGRAM“: the SM to be submitted is intended to be delivered as TELEGRAM. “VOICE“: the SM to be submitted is intended to be delivered as vocal message. “DATA“: the SM to be submitted is intended to con
