ETSI TS 101 852-1-2-2003 Broadband Radio Access Networks (BRAN) HIPERLAN Type 2 Conformance testing for the Cell based Convergence Layer Part 1 Common part Sub-part 2 Test Suite St.pdf

1、 ETSI TS 101 852-1-2 V1.2.1 (2003-07)Technical Specification Broadband Radio Access Networks (BRAN);HIPERLAN Type 2;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 t

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

3、iven 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)

4、. The present document is part 1, sub-part 2 of a multi-part deliverable. Full details of the entire series can be found in part 1, sub-part 1 7. ETSI ETSI TS 101 852-1-2 V1.2.1 (2003-07) 5 1 Scope The present document contains the Test Suite Structure (TSS) and Test Purposes (TP) to test the Broadb

5、and Radio Access Networks (BRAN) HIPERLAN Type 2; Cell based Convergence Layer; Part 1: Common Part. The objective of the present document is to provide a basis for conformance tests for Broadband Radio Access Networks (BRAN) HIPERLAN type 2 equipment giving a high probability of air interface inter

6、-operability between different manufacturers BRAN HIPERLAN type 2 equipment. The ISO standard for the methodology of conformance 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 Reference

7、s 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 and/or edition number or version number) or non-specific. For a specific reference, subsequent revision

8、s 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 http:/docbox.etsi.org/Reference. 1 ETSI TS 101 763-1 (V1.1.1): “Broadband Radio Access Networks (BRAN); HIPERLAN Type

9、 2; Cell based Convergence Layer; Part 1: Common Part“. 2 ETS 300 406: “Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. 3 ISO/IEC 9646-1: “Information technology - Open Systems Interconnection - Conformance testing m

10、ethodology and framework - Part 1: General concepts“. 4 ISO/IEC 9646-2: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification“. 5 ISO/IEC 9646-6: “Information technology - Open Systems Interconnection - Conf

11、ormance testing methodology and framework - Part 6: Protocol profile test specification“. 6 ISO/IEC 9646-7: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statement“. 7 ETSI TS 101 852-1-1 (V1.2.1): “Broadba

12、nd Radio Access Networks (BRAN); HIPERLAN Type 2; Conformance testing for the Cell based Convergence Layer; Part 1: Common part; Sub-part 1: Protocol Implementation Conformance Statement (PICS) proforma“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the t

13、erms and definitions given in ISO/IEC 9646-7 6 and TS 101 763-1 1 apply. ETSI ETSI TS 101 852-1-2 V1.2.1 (2003-07) 6 3.2 Abbreviations For the purposes of the present document, the abbreviations defined in ISO/IEC 9646-1 3, ISO/IEC 9646-6 5, ISO/IEC 9646-7 6, TS 101 763-1 1 and the following apply:

14、AP Access Point BI Invalid Behaviour BO Inopportune Behaviour BV Valid Behaviour CA Capability tests CL Convergence Layer DLC Data Link Control DUC DLC User Connection IUT Implementation Under Test MAC Medium Access Control MT Mobile Terminal PDU Protocol Data Unit PICS Protocol Implementation Confo

15、rmance Statement TP Test Purposes TSS Test Suite Structure 4 Test suite structure 4.1 Structure Figure 1 shows the Common PBCL 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-MT Com

16、mon procedures Sender x Receiver x Figure 1: TSS for HIPERLAN 2 Common part CBCL The test suite is structured as a tree with a first level defined as CCL-AP or CCL-MT representing the protocol group “Common part CBCL for AP and Common part CBCL for MT“. 4.2 Test groups The test groups are organized

17、in three levels. The first level creates one protocol group representing 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 protoc

18、ol groups identifies the common part procedures as defined in TS 101 763-1 1. 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 procedure

19、s at the receiver side. 4.2.2 Main test groups The main test groups are the capability group, the valid behaviour group, the invalid behaviour group and the inopportune behaviour group. ETSI ETSI TS 101 852-1-2 V1.2.1 (2003-07) 7 4.2.2.1 Capability (CA) tests This test sub group shall provide limite

20、d testing of the major IUT capabilities aiming to insure that the claimed capabilities 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 TS 101 763-1 1, after receipt or exchange of valid Protoco

21、l Data Units (PDUs). Valid PDUs means that the exchange of messages and the content 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 TS 101 763-1 1, after receipt of a syntactically invalid

22、 PDU. 4.2.2.4 Inopportune Behaviour (BO) tests This test sub group shall verify that the IUT reacts in conformity with TS 101 763-1 1, 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 T

23、Ps are defined following particular rules as shown in table 1. Table 1: TP definition rules TP Id 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 below. Reference Th

24、e reference should contain the references of the subject to be validated by the actual TP (specification reference, clause, and paragraph). Initial 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 t

25、he TP is related. Expected behaviour Definition of the events that are expected from the IUT to conform to the base specification. ETSI ETSI TS 101 852-1-2 V1.2.1 (2003-07) 8 5.1.2 TP naming conventions The identifier of the TP is built according to table 2. Table 2: TP naming convention Identifier:

26、 TP/- = side type AP Access Point MT Mobile Terminal = protocole group 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 (00

27、0-999) Test Purpose Number EXAMPLE: TP/MT/CCP/RS/BV-010 is the tenth purpose for the valid behaviour testing of the procedures at the receiver of the common part procedures implemented at MT side. 5.1.3 Sources of TP definitions All TPs are specified according to TS 101 763-1 1. 5.2 Test purposes fo

28、r AP 5.2.1 Procedures at the sender TP/AP/CCP/SS/CA-000 Reference: TS 101 763-1 1, clause 5.3.3.3. Initial condition: DUC 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 strea

29、m of CPCS PDU to send. TP/AP/CCP/SS/CA-001 Reference: TS 101 763-1 1, clause 5.3.3.3. Initial condition: DUC 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 PD

30、U to send. TP/AP/CCP/SS/CA-002 Reference: TS 101 763-1 1, clause 5.3.3.3. Initial condition: DUC 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 iden

31、tifiers (VPI, VCI) and the combination of DLC connection identifier (DLCC_ID) and the CL_Tag for the CPCS PDUs to send. TP/AP/CCP/SS/CA-003 Reference: TS 101 763-1 1, clause 5.3.3.3. Initial condition: DUC established. IUT is the sender. A loop back mechanism is implemented on top of either CPCS lay

32、er or SSCS layer at the IUT. Check that the IUT sends a CPCS-PDU only in case of the mapping for the VPI, VCI exists. ETSI ETSI TS 101 852-1-2 V1.2.1 (2003-07) 9 5.2.2 Procedures at the receiver TP/AP/CCP/RS/CA-000 Reference: TS 101 763-1 1, clause 5.3.3.2. Initial condition: DUC established. IUT is

33、 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 DUC ID (MAC_ID, DLCC_ID) and the CL_Tag. TP/AP/CCP/RS/CA-001 Reference: TS 101 763-1 1, clause 5.3.3.

34、2. Initial condition: DUC 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. TP/AP/CCP/RS/CA-002 Reference: TS 101 763-1 1, clause 5.3.3.2. Initial

35、 condition: DUC 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 CPCS PDU. 5.3 Test purposes for MT 5.3.1 Procedures at the sender TP/MT/CCP/SS/CA-000 Ref

36、erence: TS 101 763-1 1, clause 5.3.3.3. Initial condition: DUC 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/MT/CCP/SS/CA-001 Reference: TS 10

37、1 763-1 1, clause 5.3.3.3. Initial condition: DUC 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/MT/CCP/SS/CA-002 Reference: TS 101 763-1 1, c

38、lause 5.3.3.3. Initial condition: DUC 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 combination of DLC connection id

39、entifier (DLCC_ID) and the CL_Tag for the CPCS PDUs to send. TP/MT/CCP/SS/CA-003 Reference: TS 101 763-1 1, clause 5.3.3.3. Initial condition: DUC 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 CPC

40、S-PDU only in case of the mapping for the VPI, VCI exists. 5.3.2 Procedures at the receiver TP/MT/CCP/RS/CA-000 Reference: TS 101 763-1 1, clause 5.3.3.2. Initial condition: DUC established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IU

41、T. Check that the IUT discards a received CPCS PDU, in case of a non-configured mapping for the DUC ID (MAC_ID, DLCC_ID) and the CL_Tag. TP/MT/CCP/RS/CA-001 Reference: TS 101 763-1 1, clause 5.3.3.2. Initial condition: DUC established. IUT is the receiver. A loop back mechanism is implemented on top

42、 of either CPCS layer or SSCS layer at the IUT. Check that the IUT manages correctly a continuous stream of received CPCS PDU. TP/MT/CCP/RS/CA-002 Reference: TS 101 763-1 1, clause 5.3.3.2. Initial condition: DUC 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 CPCS PDU. ETSI ETSI TS 101 852-1-2 V1.2.1 (2003-07) 10History Document history V1.1.1 December 2001 Publication V1.2.1 July 2003 Publication