ETSI ES 202 912-7-2003 Access and Terminals (AT) Short Message Service (SMS) for PSTN ISDN Test Suites for SMS User Based Solution Part 7 Test Suite Structure and Test Purposes (TS.pdf

《ETSI ES 202 912-7-2003 Access and Terminals (AT) Short Message Service (SMS) for PSTN ISDN Test Suites for SMS User Based Solution Part 7 Test Suite Structure and Test Purposes (TS.pdf》由会员分享，可在线阅读，更多相关《ETSI ES 202 912-7-2003 Access and Terminals (AT) Short Message Service (SMS) for PSTN ISDN Test Suites for SMS User Based Solution Part 7 Test Suite Structure and Test Purposes (TS.pdf（49页珍藏版）》请在麦多课文档分享上搜索。

1、ETSI ES 202 912-7 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 7: 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 7 of a multi-part deliverable. Full details of the entire series can be found in part 1 9. ETSI 6 ETSI ES 202 912-7 VI .I .I (2003-02) 1 Scope The present document provides test suite structure and test purposes for Functional tests for a Termi

4、nal Equipment implementing the Short Message Service (SMS) for PSTNASDN, UBS Protocol 1 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 th

5、e scope of the present document, although some parameters related to these procedures are used (e.g. SME subaddressing). UBS1 terminals send and receive Data Link messages in the voice-band connection using the FSK signalling as defined in EN 300 659-2 5 and ES 200 778-2 SI. Tests for the FSK signal

6、ling are outside the scope of the present document. Tests for Data Link Layer have been treated in ES 202 912-2 lo. Terminal Equipment implementing the Short Message Service (SMS) for PSTNASDN according to UBS Protocol 1 are required to implement the Transfer Layer according to ES 201 912 i. The Rem

7、ote Single Layer Embedded Test Method (see ISO/IEC 9646-2 13) is used for the UBS Protocol 1 Transfer layer. Figure 1 gives an overview of the reference architecture used for the UBS Protocol 1 operation. Figure 2 shows the configuration used for testing. ISO/IEC 9646-1 121 and ISO/IEC 9646-2 131 ar

8、e used 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 versi

9、on number) 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

10、 912 (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“. 51 71 ETSI TS 100 900 (V7.2.0): “Digital cellular telecommunications system (Phase 2+) (GSM);

11、 Alphabets and language-specific information (GSM 03.38 version 7.2.0)“. ETSI TS 100 901 (V7.4.0): “Digital cellular telecommunications system (Phase 2+) (GSM); Technical realization of the Short Message Service (SMS) (GSM 03.40 version 7.4.0)“. ETSI EN 300 659-1 (V1.3.1): “Access and Terminals (AT)

12、; Analogue access to the Public Switched Telephone 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 (P

13、STN); Subscriber line protocol over the local 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 displa

14、y (and related) services; Part 3: Data link 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

15、: On-hook data transmission“. ETSI 7 ETSI ES 202 912-7 VI .I .I (2003-02) ETSI ES 200 778-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: O

16、ff-hook data transmission“. 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 specification user side for Data Link Layer (DLL) Protocol 1“.

17、 ETSI ES 202 912-2 (Vl.l.1): “Access and Terminals (AT); Short Message Service (SMS) for PSTNASDN; Test Suites for SMS User Based Solution; Part 2: Test Suite Structure and Test Purposes (TSS Short Message Service (SMS) for PSTNASDN; Test Suites for SMS User Based Solution; Part 3: Abstract Test Sui

18、te (ATS) user side for Data Link Layer (DLL) Protocol 1“. ISO/IEC 9646- 1 : “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1 : General concepts“. ISO/IEC 9646-2: “Information technology - Open systems interconnection - Conformance testin

19、g methodology and framework - Part 2: Abstract test suite specification“. 121 i31 3 Definitions and abbreviations 3.1 De fi nit ions For the purposes of the present document, the following terms and definitions apply: incoming VB-connection: VB-connection initiated by an SM-SC Lower Test System (LTS

20、): part of the Test System performing basic signalling procedures to establish a VB- connection and to transmit and receive FSK frames originator (of an SM): SM-TE sending an SM to another SM-TE outgoing VB-connection: VB-connection initiated by an SM-TE peer (entities): SM-TE and SM-SC, for which a

21、 voice-band connection exists or is pending, are considered as peers SMS call: an outgoing call established by the SM-TE to the SM-SC in order to submit an SM or an incoming call established by the SM-SC to the SM-TE in order to deliver an SM (in this case the CLI used to establish the call contains

22、 the address of the SM-SC stored in the SM-TE) VB-connection: Voice-Band connection between two peers NOTE 1 : A Voice-band connection is considered to be completed or established, when the basic call control procedures, performed according to the type of network access the SM-TE is connected to (i.

23、e. PSTN or BRA ISDN or PRA ISDN), are completed and the voice-band connection is ready for FSK frame transfer. NOTE 2: In order to establish an incoming VB-connection, the CLI information has to be previously provided to the terminal equipment. The way of providing CLI (e.g. by DTMF or FSK signallin

24、g and using a data transmission associated with ringing or not, etc ., in the case of PSTN) is out of the scope of the present document . VB-Initiator: entity (SM-TE or SM-SC) initiating a voice-band connection to the peer entity VB-Responder: entity (SM-TE or SM-SC) having received a voice-band con

25、nection attempt from the peer entity ETSI 8 SM-TE (Initiator) ETSI ES 202 912-7 VI .I .I (2003-02) Network SM-SC (PSTNIISDN) (store only unformatted text is transferred in the SMS-SUBMIT, SMS-DELIVER and SMS-STATUS-REPORT messages, using the GSM default 7-bit character encoding; no user data are tra

26、nsferred in the SMS-SUBMIT-REPORT message. - 5.4 Grouping of test purposes ES 201 912 i specifies requirements for the SM-TE functional behaviour and for the mapping of TL messages to/from DLL messages. TS 100 901 3 specifies format and contents of the TL messages and the TL procedures. The tests ar

27、e grouped in two main categories: 1) 2) Outgoing SMS call related tests, and Incoming SMS call related tests. Detailed information on the test groups and subgroups can be found in clause 6.2. 5.5 Test purpose naming convention The present document is created together with other similar TSSelection E

28、xpr.: ream ble: -est description: ass criteria: ostam ble: Test Purpose identifier like UBSI-FT-OUT-SUBMIT-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 ad

29、ded if appropriate. Since ES 201 912 I is the basic standard on which this test specification relies, the first paragraph of the “Requirem. ref.“ cell normally contains only clause numbers, without identifying the standard ES 201 912 I explicitly. Whenever a reference to another standards are necess

30、ary, a new line is added, identifying this standard, followed by a colon and then clause numbers as for ES 201 912 I. EXAMPLE: 5.3.2.1, table 5 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 the

31、re is no entry, the test 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 preamble leading to a condition or state, where the test purpose can be verified. Sequence of events int

32、ending to lead to the verification 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 value(s), being essential for the verificati

33、on of the test purpose. EN 300 659-2 5, 7.3.1 This can be a copy of one or more lines of the “Test description“, or can be a textual explanation. None or name of a postamble leading to the IDLE condition of the IUT (no VB connection exists). ETSI 13 ETSI ES 202 912-7 VI .I .I (2003-02) Group Outgoin

34、g SMS call 6 Test purposes presentation and environment specif cat ion Subgroup Group Ide nt if er Count SME subaddressing and Deliver Mode Identifier UBSI-FT-OUT-SUBADDRDMI 3 Submit message format and contents UBSI-FT-OUT-SUBMIT 3 UBSI -FT-OUT-TEXTCOD 1 Submit Report UBSI-FT-OUT-SUBREP 2 SME subadd

35、ressing and Deliver Mode Identifier UBSI-FT-INC-SUBADDRDMI 10 SM text coding 6.1 I n trod u ction Status report reception SM text decoding SM Replace More SMs in one call Deliver rennri After the definition of the Test Suite Structure, a suitable environment has to be created in order to formulate t

36、he 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. This is e.g. taken into account in the naming conventions and “atomic phrases“ used in the

37、descriptions. Test parameters and other objects like Selection Expressions have been collected during the test purposes development to provide this test specification with the necessary parametrization and selection information. It is assumed that these objects will also appear in a TTCN ATS based o

38、n this test specification, with a few modifications resulting from the notation change (the Test Parameters e.g. being transformed into Test Suite Parameters). UBSI-FT-INC-STATUSREP 1 UBSI-FT-INC-TEXTDEC 2 UBSI-FT-INC-MORESMS 1 U BS 1 - FT- I N C-S M RE PLACE 1 IIRSI FT INC DFI I/FRRFP 7 6.2 Test Su

39、ite Structure (TSS) Table 1 shows the structure of the UBSl Functional tests Test Suite, as well as the TP group identifiers and the number of test purposes produced, per subgroup and in total: Incoming SMS call ITotal: I 26 I 6.3 Abstract Service Primitives Three classes of ASPS are defined, accord

40、ing to the PCOs at which they operate (see figure 2). PCO ASP class O: FS: cc: ASPs related to the operator (Upper Tester), ASPs related to transmission and reception of TL messages via DLL messages, and ASPs related to connection control. ETSI 14 ETSI ES 202 912-7 VI .I .I (2003-02) SU BM-RESU LT-V

41、ERI F-req SUBM-RESULT-VERIF-conf DIS PL-I N F-VERI F-req Table 2 describes the general functions of the ASPs operating at the 3 PCOs. Detailed descriptions of the ASPs together with their parameters follow. set the SM-TE in the “Busy“ condition. (see note 1) Request the user to verify if the SM-TE i

42、ndicates the acceptance or rejection of the submitted SM, .e. that the SMS-SUBMIT-REPORT message has been received without or with a failure cause. Indication by the user that the SM-TE has indicated the acceptance or rejection of the submitted SM at the SM-SC. Request the user to verify that the in

43、dicated text is received in the latest received SM and is displayed in the indicated form. Request the user also to check if the latest SM has replaced a LT-UT UT-LT LT-UT Table 2: List of ASPs ASP Name I Direction I Description OUTGO1 N G-CALL- req ILT-UT IMake the SM-TE initiate a VB connection to

44、 the SM-SC in DISPL-INF-VERIF-conf STAT-RE P-I N F-VERI F-req lorder to send an SM. IMake the SM-TE establish one or more phone calls in order to BUSY- req ILT-UT previously received SM (optional). Indication by the user whether the expected text has been received and displayed by the SM-TE. Request

45、 the user to verify whether the information contained in UT-LT LT-UT STAT-REP-INF-VERI F-conf S M- Rece ptio n- req S M- Rece ptio n-co nf SM-Reception2-req the received SMS-STATUS-REPORT message and concerning the outcome at the recipient of an SM previously sent is made available to the user. Indi

46、cation by the user that the information contained in the received SMS-STATUS-REPORT message and concerning the outcome at the recipient of an SM previously sent is made available to the user. Request the user to check for the next incoming SM whether has been received by the SM-TE (see note 1). Indi

47、cation by the user that the latest incoming SM has been received by the SM-TE (see note 1). Request the user to check if two incoming SMs within the UT-LT LT-UT UT-LT LT-UT EMPTY- M EM-req EM PTY-M E M-ind I N C-CALL- req INC-CALL-conf OUTG-CALL-ind OUTG-CALL-resp CALL-RE LEAS E-ind CALL-RELEASE-req

48、 Isame SMS call have been received by the SM-TE. Ilndication by the user that the two latest incoming SMs within SM-Reception2-conf IUT-LT the same SMS call have been received by the SM-TE. Request the user to delete the SMs stored in the SM-TE to make the SM-TE memory again available. Indicates tha

49、t the SM-TE does not contain anymore stored SMs (and can now accept incoming SMs). Make the Lower Test System initiate the basic call control procedures for an incoming SMS call, to establish a VB connection from the SM-SC to the SM-TE. The Lower Test System confirms that the requested basic call control procedures for an incoming SMS call have been successfully completed and the VB connection to the SM-TE is established, or that the connection attempt was not successful. Indication that the SM-TE has initiated the basic call control procedu