ETSI TS 102 147-1-2-2004 Broadband Radio Access Networks (BRAN) HIPERACCESS Conformance testing for the Cell based Convergence Layer Part 1 Common part Sub-part 2 Test Suite Struct.pdf

1、 ETSI TS 102 147-1-2 V1.2.1 (2004-04)Technical Specification Broadband Radio Access Networks (BRAN);HIPERACCESS;Conformance testing for the Cell based Convergence Layer;Part 1: Common part;Sub-part 2: Test Suite Structure andTest Purposes (TSS Essential, or potentially Essential, IPRs notified to ET

2、SI 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). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given

3、 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 present document. Foreword This Technical Specification (TS) has been produced by ETSI Project Broadband Radio Access Networks (BRAN). Th

4、e present document is part 1, sub-part 2 of a multi-part covering Broadband Radio Access Networks (BRAN); HIPERACCESS; Conformance testing for the Cell based Convergence Layer, as identified below: Part 1: “Common part“; Sub-part 1: “Protocol Implementation Conformance Statement (PICS) proforma“; Su

5、b-part 2: “Test Suite Structure and Test Purposes (TSS Sub-part 3: “Abstract Test Suite (ATS)“. Part 2: “UNI Service Specific Convergence Sublayer (SSCS)“. ETSI ETSI TS 102 147-1-2 V1.2.1 (2004-04) 5 1 Scope The present document contains the Test Suite Structure (TSS) and Test Purposes (TP) to test

6、the TS 102 115-1 1. The objective of this test specification is to provide a basis for conformance tests for BRAN HIPERACCESS equipment giving a high probability of air interface inter-operability between different manufacturers BRAN HIPERACCESS equipment. The ISO standards for the methodology of co

7、nformance testing (ISO/IEC 9646-1 3 and ISO/IEC 9646-2 4) as well as the ETSI rules for conformance testing (ETS 300 406 2) are used as a basis for the test methodology. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the presen

8、t document. 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. For a non-specific reference, the latest version applies. Referenced documents which are not found to b

9、e publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. 1 ETSI TS 102 115-1: “Broadband Radio Access Networks (BRAN); HIPERACCESS; Cell based Convergence Layer; Part 1: Common Part“. 2 ETSI ETS 300 406: “Methods for Testing and Specification (MTS); Protocol a

10、nd profile conformance testing specifications; Standardization methodology“. 3 ISO/IEC 9646-1: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“. 4 ISO/IEC 9646-2: “Information technology - Open Systems Interconnection

11、- Conformance testing methodology and framework - Part 2: Abstract test suite specification“. (See also CCITT Recommendation X.291 (1991). 5 ISO/IEC 9646-6: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test specific

12、ation“. 6 ISO/IEC 9646-7: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation conformance statement“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given

13、in ISO/IEC 9646-7 6 and TS 102 115-1 1 apply. ETSI ETSI TS 102 147-1-2 V1.2.1 (2004-04) 6 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 3, ISO/IEC 9646-6 5, ISO/IEC 9646-7 6, TS 102 115-1 1 and the following apply: AP Access Point AT Access Ter

14、minal ATM Asynchronous Transfer Mode BI Invalid Behaviour BO inopportune Behaviour BRAN Broadband Radio Access Networks (Project) BV Valid Behaviour CA CApability tests CCP Cell Common Part CL Convergence Layer CPCS Common Part Convergence Sublayer IUT Implementation Under Test LAN Local Area Networ

15、k PDU Protocol Data Unit PICS Protocol Implementation Conformance Statement RS Receiver Side SS Sender Side SSCS Service Specific Convergence Sublayer TP Test Purposes TSS Test Suite Structure UNI User Network Interface VCI Virtual Channel Identifier VPI Virtual Path Identifier 4 Test Suite Structur

16、e (TSS) 4.1 Structure Figure 1 shows the Common CBCL Test Suite Structure (TSS) including its subgroups defined for the conformance testing. Test Suite Protocol group Protocol subgroup Test group CA BV BI BO CCL-AP/ CCL-AT Common procedures Sender x Receiver x Figure 1: TSS for Hiperaccess Common pa

17、rt CBCL The test suite is structured as a tree with a first level defined as CCL-AP or CCL-AT representing the protocol group “Common part CBCL for AP and Common part CBCL for AT“. 4.2 Test groups The test groups are organized in three levels. The first level creates one protocol group representing

18、the protocol services. The second level separates the protocol services in functional modules. The last level in each branch contains one or more of the standard ISO subgroups CA, BV, BI and BO. 4.2.1 Protocol groups The protocol groups identify the common part procedures as defined in TS 102 115-1

19、1. ETSI ETSI TS 102 147-1-2 V1.2.1 (2004-04) 7 4.2.1.1 Common procedures The common part procedures group is divided in two functional modules. The first functional module identifies the procedures at the sender side. The last functional module identifies the procedures at the receiver side. 4.2.2 M

20、ain test groups The main test groups are the capability group, the valid behaviour group, the invalid behaviour group and the inopportune behaviour group. 4.2.2.1 Capability (CA) tests This test sub group shall provide limited testing of the major IUT capabilities aiming to insure that the claimed c

21、apabilities are correctly supported, according to the PICS. 4.2.2.2 Valid Behaviour (BV) tests This test sub group shall verify that the IUT reacts in conformity with the TS, after receipt or exchange of valid Protocol Data Units (PDUs). Valid PDUs means that the exchange of messages and the content

22、 of the exchanged messages are considered as valid. 4.2.2.3 Invalid Behaviour (BI) tests This test sub group shall verify that the IUT reacts in conformity with the TS, after receipt of a syntactically invalid PDU. 4.2.2.4 Inopportune Behaviour (BO) tests This test sub group shall verify that the IU

23、T reacts in conformity with the TS, after receipt of a syntactically correct PDU not expected in the actual message exchange. 5 Test Purposes (TP) 5.1 Introduction 5.1.1 TP definition conventions The TPs are defined following particular rules as shown in table 1. Table 1: TP definition rules TP Id a

24、ccording to the TP naming conventions Reference. Initial condition. Stimulus. Expected behaviour. TP Id The TP Id is a unique identifier it shall be specified according to the TP naming conventions defined in the clause 5.1.2. Reference The reference should contain the references of the subject to b

25、e validated by the actual TP (specification reference, clause, and paragraph). Condition The condition defines in which initial state the IUT has to be to apply the actual TP. Stimulus The stimulus defines the test event to which the TP is related. Expected behaviour Definition of the events that ar

26、e expected from the IUT to conform to the base specification. 5.1.2 TP naming conventions The identifier of the TP is built according to table 2. ETSI ETSI TS 102 147-1-2 V1.2.1 (2004-04) 8 Table 2: TP naming convention Identifier: TP/- = side type AP Access Point AT Access Terminal = protocol group

27、 CCP Cell Common part procedures = functional module SS Sender side RS Receiver sidex = Type of testing CA Capability tests BV Valid Behaviour tests BI Invalid Behaviour tests BO Inopportune Behaviour tests = sequential number (000-999) Test Purpose Number EXAMPLE: TP/AT/CCP/RS/BV-010 is the tenth p

28、urpose for the valid behaviour testing of the procedures at the receiver of the common part procedures implemented at the AT side. 5.1.3 Sources of TP definitions All TPs are specified according to TS 102 115-1 1. 5.2 Test purposes for AP 5.2.1 Procedures at the sender TP/AP/CCP/SS/BV-000 Reference:

29、 TS 102 115-1 1, clause 5.3.3.3. Initial condition: Connection established. IUT is the sender. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT manages correctly a continuous stream of CPCS PDU to send. TP/AP/CCP/SS/BV-001 Reference: TS

30、102 115-1 1, clause 5.3.3.3. Initial condition: Connection established. IUT is the sender. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT manages correctly a discontinuous flow of CPCS PDU to send. TP/AP/CCP/SS/BV-002 Reference: TS 102

31、 115-1 1, clause 5.3.3.3. Initial condition: Connection established. IUT is the sender. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT manages correctly the mapping between the ATM connection identifiers (VPI, VCI) and the CID / VCI fo

32、r each active CID. TP/AP/CCP/SS/BV-003 Reference: TS 102 115-1 1, clause 5.3.3.3. Initial condition: Connection established. IUT is the sender. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT sends a CPCS-PDU only if the mapping for the

33、 VPI, VCI exists. 5.2.2 Procedures at the receiver TP/AP/CCP/RS/BV-000 Reference: TS 102 115-1 1, clause 5.3.3.2. Initial condition: Connection established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT discards a

34、 received CPCS PDU, in case of a non-configured mapping for the CID and the VCI field. TP/AP/CCP/RS/BV-001 Reference: TS 102 115-1 1, clause 5.3.3.2. Initial condition: Connection established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the

35、IUT. Check, that: the IUT manages correctly a continuous stream of received CPCS PDU. TP/AP/CCP/RS/BV-002 Reference: TS 102 115-1 1, clause 5.3.3.2. Initial condition: Connection established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the I

36、UT. Check, that: the IUT manages correctly a discontinuous flow of received CPCS PDU. ETSI ETSI TS 102 147-1-2 V1.2.1 (2004-04) 9 5.3 Test purposes for AT 5.3.1 Procedures at the sender TP/AT/CCP/SS/BV-000 Reference: TS 102 115-1 1, clause 5.3.3.3. Initial condition: Connection established. IUT is t

37、he sender. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT manages correctly a continuous stream of CPCS PDU to send. TP/AT/CCP/SS/BV-001 Reference: TS 102 115-1 1, clause 5.3.3.3. Initial condition: Connection established. IUT is the s

38、ender. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT manages correctly a discontinuous flow of CPCS PDU to send. TP/AT/CCP/SS/BV-002 Reference: TS 102 115-1 1, clause 5.3.3.3. Initial condition: Connection established. IUT is the send

39、er. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT manages correctly the mapping between the ATM connection identifiers (VPI, VCI) and the CID / VCI for each active CID. TP/AT/CCP/SS/BV-003 Reference: TS 102 115-1 1, clause 5.3.3.3. In

40、itial condition: Connection established. IUT is the sender. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT sends a CPCS-PDU only if the mapping for the VPI, VCI exists. 5.3.2 Procedures at the receiver TP/AT/CCP/RS/BV-000 Reference: TS

41、 102 115-1 1, clause 5.3.3.2. Initial condition: Connection established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT discards a received CPCS PDU, in case of a non-configured mapping for the CID and the VCI fiel

42、d. TP/AT/CCP/RS/BV-001 Reference: TS 102 115-1 1, clause 5.3.3.2. Initial condition: Connection established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT manages correctly a continuous stream of received CPCS PDU

43、. TP/AT/CCP/RS/BV-002 Reference: ETSI TS 102 115-1 1, clause 5.3.3.2. Initial condition: Connection established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT manages correctly a discontinuous flow of received CPC

44、S PDU. ETSI ETSI TS 102 147-1-2 V1.2.1 (2004-04) 10Annex A (informative): Bibliography ITU-T Recommendation X.290: “OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications - General concepts“. ETSI ETSI TS 102 147-1-2 V1.2.1 (2004-04) 11History Document history V1.1.1 November 2002 Publication V1.2.1 April 2004 Publication