ETSI TS 101 823-4-3-2004 Broadband Radio Access Networks (BRAN) HIPERLAN Type 2 Conformance testing for the Data Link Control (DLC) layer Part 4 Extension for Home Environment Sub-.pdf

《ETSI TS 101 823-4-3-2004 Broadband Radio Access Networks (BRAN) HIPERLAN Type 2 Conformance testing for the Data Link Control (DLC) layer Part 4 Extension for Home Environment Sub-.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 101 823-4-3-2004 Broadband Radio Access Networks (BRAN) HIPERLAN Type 2 Conformance testing for the Data Link Control (DLC) layer Part 4 Extension for Home Environment Sub-.pdf（57页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 101 823-4-3 V1.3.1 (2004-08)Technical Specification Broadband Radio Access Networks (BRAN);HIPERLAN Type 2;Conformance testing for the Data Link Control (DLC) layer;Part 4: Extension for Home Environment;Sub-part 3: Abstract Test Suite (ATS) specificationfloppy3 ETSI ETSI TS 101 823-4-3 V1.

2、3.1 (2004-08) 2 Reference RTS/BRAN-002T0B4-4-3 Keywords access, HIPERLAN, TSS 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.as

3、p). 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 SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present

4、document. Foreword This Technical Specification (TS) has been produced by ETSI Project Broadband Radio Access Networks (BRAN). The present document is part 4, sub-part 2 of a multi-part deliverable. Full details of the entire series can be found in part 1, sub-part 1 (see bibliography). ETSI ETSI TS

5、 101 823-4-3 V1.3.1 (2004-08) 7 1 Scope The present document contains the Abstract Test Suite (ATS) to test the BRAN HIPERLAN type 2; Data Link Control (DLC) layer; Extension for Home Environment. The objective of the present document is to provide a basis for conformance tests for BRAN H/2 equipmen

6、t giving a high probability of air interface inter-operability between different manufacturers. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 8 and ISO/IEC 9646-2 9) as well as the ETSI rules for conformance testing (ETS 300 406 7) are used as a basis for the test metho

7、dology. Annex A provides the Tree and Tabular Combined Notation (TTCN) part of the ATS. Annex B provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of the MT side ATS. Annex C provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) P

8、roforma of the AP side ATS. Annex D provides the Protocol Conformance Test Report (PCTR) Proforma of the MT side ATS. Annex E provides the Protocol Conformance Test Report (PCTR) Proforma of the AP side ATS. 2 References The following documents contain provisions which, through reference in this tex

9、t, 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 revisions do not apply. For a non-specific reference, the latest version applies. Referen

10、ced 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 761-2 (V1.3.1): “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Data Link Control (DLC) layer; Part 2: Radio Link Control (RLC) Sublayer“. 2

11、ETSI TS 101 761-4 (V1.3.2): “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Data Link Control (DLC) layer; Part 4: Extension for Home Environment“. 3 Void. 4 Void. 5 ETSI TS 101 823-2-3: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Conformance testing for the Data Link Control

12、 (DLC) layer; Part 2: Radio Link Control (RLC) sublayer; Sub-part 3: Abstract Test Suite (ATS) specification“. 6 Void. 7 ETSI ETS 300 406: “Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. 8 ISO/IEC 9646-1 (1994): “In

13、formation technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“. (See also ITU-T Recommendation X.290 (1995). ETSI ETSI TS 101 823-4-3 V1.3.1 (2004-08) 8 9 ISO/IEC 9646-2 (1994): “Information technology - Open Systems Interconnection -

14、Conformance testing methodology and framework - Part 2: Abstract Test Suite specification“. (See also ITU-T Recommendation X.291 (1995). 10 ISO/IEC 9646-3 (1998): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 3: The Tree and Tabular Com

15、bined Notation (TTCN)“. (See also ITU-T Recommendation X.292 (2002). 11 Void. 12 ISO/IEC 9646-6 (1994): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test specification“. 13 ISO/IEC 9646-7 (1995): “Information techno

16、logy - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statement“. 14 ETSI TS 101 493-3: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Packet based Convergence Layer; Part 3: IEEE 1394 Service Specific Convergence Sublayer

17、 (SSCS)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions defined in ISO/IEC 9646-7 13, TS 101 761-2 1 and TS 101 761-4 2 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations defined in ISO/IEC 9646-1

18、 8, ISO/IEC 9646-6 12, ISO/IEC 9646-7 13, TS 101 761-2 1, TS 101 761-4 2 and the following apply: ACF Association Control Function ACH Access feedback CHannel AP Access Point APC Access Point Controller APT Access Point Transceiver ARQ Automatic Repeat Request ASP Abstract Service Primitive BCH Broa

19、dcast CHannel BI Invalid BehaviourBO Inopportune Behaviour BV Valid Behaviour CA Capability tests CC Central Controller CL Convergence Layer DCCH Dedicated Control CHannel DES Data Encryption Standard DFS Dynamic Frequency SelectionDLC Data Link Control DM Direct Mode DUC DLC User Connection EC Erro

20、r Control IUT Implementation Under Test LCCH Link Control CHannel LCH Long CHannelMAC Medium Access Control MAC-ID MAC IDentifier MT Mobile Terminal NET-ID NETwork-IDentifier ETSI ETSI TS 101 823-4-3 V1.3.1 (2004-08) 9 PDU Protocol Data Unit PHY Physical layer PICS Protocol Implementation Conformanc

21、e Statement RLC Radio Link Control RRC Radio Resource Control RSS Received Signal Strength SAP Service Access Point SBCH Slow Broadcast CHannel SCH Short CHannel SSCS Service Specific Convergence Sublayer SSK Session Secret Key TP Test Purposes TSS Test Suite Structure TTCN Tree and Tabular Combined

22、 Notation WT Wireless Terminal 4 Abstract Test Method (ATM) This clause describes the ATM used to test the HIPERLAN 2 Data Link Control (DLC) Protocol - Extension for Home Environment at the AP side and at the MT side. 4.1 Test architecture RCP PCOPHYDLC/MACDLC/MACLower TesterPHYSUTARQRLC(IUT)RLC(AT

23、S)Notional UTFigure 1: Test architecture for DLC Extension for Home Environment A single-party testing concept is used, which consists of the following abstract testing functions: Lower Tester: A Lower Tester (LT) is located in the remote BRAN H/2 test system. It controls and observes the behaviour

24、of the IUT. RLC ATS: A RLC Abstract Test Suite (ATS) is located in the remote BRAN H/2 test system. RCP PCO: the Point of Control and Observation (PCO) for RLC testing is located at a SAP between the RLC layer and the MAC layer. All test events at the PCO are specified in terms of Abstract testing S

25、ervice Primitives (ATSP defined in clause 7) containing complete PDU. To avoid the complexity of data fragmentation and recombination testing, the SAP is defined below these functions. Notional UT: No explicit upper tester (UT) exists in the system under test. Nevertheless, some specific actions to

26、cover implicit send events and to obtain feedback information are necessary for the need of the test procedures. A black box covering these requirements is used in the SUT as a notional UT as defined in ISO 9646. This notional UT is part of the test system. ETSI ETSI TS 101 823-4-3 V1.3.1 (2004-08)

27、104.2 Test Configurations 4.2.1 Test Configurations for MT Four configurations are defined for MT testing. AP(T ester)MT(IU T )Figure 2: Normal configuration for MT The normal configuration is defined and used for functionality that requires only interaction between the tested MT and one AP. AP1MT(I

28、U T )AP2TesterFigure 3: Handover configuration for MT The handover configuration is used when the MT has to interact with two AP. In that case, the two simulated AP are configurable to be either a multi-sector AP or two separate AP. The concurrent TTCN facilities are used in this configuration. MT1M

29、T2(IU T )APTesterFigure 4: Direct mode configuration for MT The direct mode configuration is used for direct mode testing. The test system simulates one AP and one MT. The AP part of the test system is used to initialize the direct mode with the tested MT. The MT part of the system is used to verify

30、 the communication of the tested MT when the direct mode is active. The concurrent TTCN facilities are used in this configuration. ETSI ETSI TS 101 823-4-3 V1.3.1 (2004-08) 11WT2 WT1 Sender (IU T ) AP/CC T ester WT3 Figure 5: Direct mode Multicast with QoS configuration for MT The direct mode Multic

31、ast with QoS configuration is used for multicast connection with required QoS testing. The test system simulates one AP/CC and two WT. The AP/CC part of the test system is used to initialize the direct mode with the tested WTs. The WTs part of the test system is used to verify the communication of t

32、he tested MT when a multicast connection with QoS is active. The concurrent TTCN facilities are used in this configuration. 4.2.2 Test Configurations for AP Two configurations are defined for AP testing. MT(T ester)AP(IU T )Figure 6: Normal configuration for AP The normal configuration is defined an

33、d used for functionality that requires only interaction between the tested AP and one MT. MT1AP(IU T )MT2TesterFigure 7: Direct mode configuration for AP The direct mode configuration is used for direct mode testing. The test system simulates two MT. The two MT of the test system are necessary to te

34、st the centralized initialization procedure of the direct mode. The concurrent TTCN facilities are used in this configuration. ETSI ETSI TS 101 823-4-3 V1.3.1 (2004-08) 125 Untestable Test Purposes (TP) This clause gives a list of TP, which are not implemented in the ATS due to the chosen ATM or oth

35、er restrictions. Table 1: Untestable TP Test purpose Reason 6 ATS conventions The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These conventions shall be considered during any later maintenance or f

36、urther development of the ATS. The ATS conventions contain two clauses, the naming conventions and the implementation conventions. The naming conventions describe the structure of the naming of all ATS elements. The implementation conventions describe the functional structure of the ATS. To define t

37、he ATS, the guidelines of the document ETS 300 406 7 was considered. 6.1 Naming conventions 6.1.1 Declarations part This clause describes the naming conventions chosen for the elements of the ATS declarations part. 6.1.1.1 General The following general rules apply for the name giving in the declarat

38、ions part. All type definitions (simple type definitions, structured type definitions, ASP type definitions and PDU type definitions) shall be written in uppercase. All element names (structured type definition), parameter names (ASP type definition) and field names (PDU type definition) shall be wr

39、itten in lowercase. Predefined types (e.g. BITSTRING8) are never used in structured type definitions, ASP type definitions or PDU type definitions. Simple types are used instead. 6.1.1.2 Test suite operations definition The test suite operation identifiers are composed of substrings in lowercase let

40、ters, except for standard prefix “TSO_“. An underscore character (“_“) separates each substring. EXAMPLE: TSO_substring 6.1.1.3 Test suite parameter declarations The test suite parameter identifiers are composed of substrings in lowercase letters, except for the standard prefix “TSP_“. An underscore

41、 character (“_“) separates each substring. EXAMPLE 1: TSP_t_wait If the test suite parameter references a Protocol Implementation Conformance Statement (PICS) item, the letter “C“ is added to the standard prefix. EXAMPLE 2: TSPC_encryption_support ETSI ETSI TS 101 823-4-3 V1.3.1 (2004-08) 13If the t

42、est suite parameter references a PIXIT item, the letter “X“ is added to the standard prefix. EXAMPLE 3: TSPX_pid 6.1.1.4 Test case selection expression definition The test case selection expression identifiers are composed of substrings in lowercase letters, beginning with the prefix “TCS_“. An unde

43、rscore character (“_“) separates each substring. 6.1.1.5 Test suite constant declarations The test suite constant identifiers are composed of substrings in lowercase letters, except for the prefix “TSC_“. An underscore character (“_“) separates each substring. If the test suite constant represents a

44、 system parameter, the complete name defined in the protocol standard is used. 6.1.1.6 Test suite variable declarations The test suite variable identifiers are composed of substrings in lowercase letters, except for the prefix “TSV_“. An underscore character (“_“) separates each substring. Complete

45、names as defined in the protocol standard are used. 6.1.1.7 Test case variable declarations The test case variable identifiers are composed of substrings in lowercase letters, except for the prefix “TCV_“. An underscore character (“_“) separates each substring. Complete names as defined in the proto

46、col standard are used. 6.1.1.8 Timer declarations Two types of timers can be identified: 1) Standardized: - Those defined in the protocol standard, e.g. T201. They use exactly the same name as in the standard. As there is a tolerance margin accepted for these timers, three values are needed: - The m

47、aximum value allowed, which will use the suffix “_max“; - The minimum value allowed, which will use the suffix “_min“; - The value actually implemented, with no suffix; EXAMPLE 1: T201_max, T201_min, and T201. 2) Not standardized: - Those not defined in the protocol standard, i.e. for execution use,

48、 e.g. a timer waiting for a response. These timers begin with the prefix “T_“, followed by a string in lowercase letters. EXAMPLE 2: T_resp represents a timer for controlling the response time of the IUT. 6.1.1.9 ASP type definitions The general conventions in clause 6.1.1.1 apply. The identifier of

49、 an ASP type uses the same name as the name defined in the protocol standard. ETSI ETSI TS 101 823-4-3 V1.3.1 (2004-08) 146.1.1.10 PDU type definitions The general conventions in clause 6.1.1.1 apply. The PDU type identifier shall identify the related structure or type as defined in the protocol standard. 6.1.1.11 CM type definitions The CM types are defined as the ASP types without sub-fields. 6.1.1.12 Alias definitions Alias definitions are not used. 6.1.2 Constraints part This clause describes the naming conventions chosen for