1、 ETSI TS 101 823-2-2 V1.5.1 (2004-11)Technical Specification Broadband Radio Access Networks (BRAN);HIPERLAN Type 2; Conformance testing for the Data Link Control (DLC) layer;Part 2: Radio Link Control (RLC) sublayer; Sub-part 2: Test Suite Structure and Test Purposes (TSS Essential, or potentially
2、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.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by E
3、TSI. 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 document. Foreword This Technical Specification (TS) has been produced by ETSI Project Broadband Radio A
4、ccess Networks (BRAN). The present document is part 2, 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 101 823-2-2 V1.5.1 (2004-11) 7 1 Scope The present document contains the Test Suite Structure (TSS) and
5、 Test Purposes (TP) to test the BRAN HIPERLAN type 2; Data Link Control (DLC) layer; Radio Link Control (RLC) sublayer. The objective of the present document is to provide a basis for conformance tests for BRAN HIPERLAN type 2 equipment giving a high probability of air interface inter-operability be
6、tween 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 References The following
7、 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 revisions do not apply.
8、 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 761-2 (V1.3.1): “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Data Link C
9、ontrol (DLC) layer; Part 2: Radio Link Control (RLC) Sublayer“. 2 ETSI ETS 300 406: “Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. 3 ISO/IEC 9646-1 (1994): “ Information technology - Open Systems Interconnection -
10、Conformance testing methodology and framework - Part 1: General concepts “. (See also ITU-T Recommendation X.290 (1995). 4 ISO/IEC 9646-2 (1994): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract test suite specification“. (See
11、also ITU-T Recommendation X.291 (1995). 5 ISO/IEC 9646-6 (1994): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test specification“. 6 ISO/IEC 9646-7 (1995): “Information technology - Open Systems Interconnection - Co
12、nformance testing methodology and framework - Part 7: Implementation Conformance Statements“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 6 and TS 101 761-2 1 apply. ETSI ETSI TS 101 823-2-2 V1.5.1 (2004-
13、11) 8 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 761-2 1 and the following apply: ACF Association Control Function AP Access Point APT Access Point Transceiver BCH Broadcast CHannel BI Invalid
14、BehaviourBO Inopportune Behaviour BV Valid Behaviour CA Capability tests CC Central Controller CL Convergence Layer DFS Dynamic Frequency Selection DLC Data Link Control DM Direct Mode DUC DLC User Connection IUT Implementation Under Test MAC Medium Access Control MT Mobile Terminal PDU Protocol Dat
15、a Unit PICS Protocol Implementation Conformance Statement RLC Radio Link Control RRC Radio Resource Control SCH Short CHannel TP Test Purposes TSS Test Suite Structure ETSI ETSI TS 101 823-2-2 V1.5.1 (2004-11) 9 4 Test suite structure 4.1 Structure Figure 1 shows the RLC Test Suite Structure (TSS) i
16、ncluding its subgroups defined for the conformance testing. Test Suite Protocol group Protocol subgroup Test group CA BV BI BO TI RLC-AP/ RLC-MT Association control function RBCH association x Mac ID assigment x Link_Capability x Encryption x Authentication x Common Key x Info_Transfer x Multicast x
17、 Disassociation x Key refresh x Radio Resource Control DFS Requesting x DFS Reporting x Sector Handover x Radio Handover x Network Handover x Sleep x Alive x Absence x DLC user connection CM Set-up x CM Release x CM Modify x CM Reset x DM Set-up x DM Release x DM Modify x DM Relay Set-up x DM Relay
18、Release x DM Relay Modify x DM Reset x TM Set-up x Figure 1: TSS for HIPERLAN 2 RLC The test suite is structured as a tree with a first level defined as RLC-AP or RLC-MT representing the protocol group “RLC for AP and RLC for MT“. 4.2 Test groups The test groups are organized in three levels. The fi
19、rst level creates three protocol groups 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, BO and TI. 4.2.1 Protocol groups The protocol groups identi
20、fy the RLC services: Association control function, Radio resource control function, and DLC user connection function, as defined in TS 101 761-2 1. ETSI ETSI TS 101 823-2-2 V1.5.1 (2004-11) 104.2.1.1 Association control function The association control function group is divided in ten functional mod
21、ules. The first functional module identifies the RBCH association procedures. The second functional module identifies the Mac Id assigment procedures. The third functional module distinguishes the Link Capability procedures. The fourth functional module distinguishes the Encryption procedures. The f
22、ifth functional module distinguishes the Authentication procedures. The sixth functional module distinguishes the information transfer procedures. The seventh functional module distinguishes the common key distribution procedures. The eighth functional module distinguishes the multicast procedures.
23、The ninth functional module distinguishes the disassociation procedures. The last functional module identifies the key refresh procedures. 4.2.1.2 Radio resource control function The Radio resource control protocol group is divided in eight functional modules. The first functional module distinguish
24、es the DFS requesting procedures. The second functional module distinguishes the DFS reporting procedures. The third functional module distinguishes the Sector handover procedures. The fourth functional module identifies the radio handover procedures. The fifth functional module distinguishes the ne
25、twork handover procedures. The sixth functional module distinguishes the sleep procedures. The seventh functional module distinguishes the alive procedures. The last functional module distinguishes the absence procedures. 4.2.1.3 DLC user connection function The DLC user connection protocol group is
26、 divided in eight functional modules. The first functional module identifies the centralized mode set-up procedures. The second functional module identifies the centralized mode release procedures. The third functional module identifies the centralized mode modify procedures. The fourth functional m
27、odule identifies the centralized mode reset procedures. The fifth functional module distinguishes the direct mode set-up procedures. The sixth functional module distinguishes the direct mode release procedures. The seventh functional module distinguishes the direct mode modify procedures. The four l
28、ast functional modules distinguish the direct mode relay procedures and the direct mode reset procedure. 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. 4.2.2.1 Capability (CA) tests Thi
29、s test sub group shall provide limited 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 the present document,
30、 after receipt or exchange of valid Protocol 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 the present d
31、ocument, after receipt of a syntactically invalid PDU. 4.2.2.4 Inoportune Behaviour (BO) tests This test sub group shall verify that the IUT reacts in conformity with the present document, after receipt of a syntactically correct PDU not expected in the actual message exchange. 4.2.2.5 Timer (TI) te
32、sts This test sub group shall verify that the IUT reacts in conformity with the present document, after timer activity (start, stop, expiration, etc.). ETSI ETSI TS 101 823-2-2 V1.5.1 (2004-11) 115 Test Purposes (TP) 5.1 Introduction 5.1.1 TP definition conventions The TPs are defined following part
33、icular rules as shown in table 1. Table 1: TP definition rules TP Id according 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 clause 5.1.2. Referen
34、ce The reference should contain the references of the subject to be 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
35、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 823-2-2 V1.5.1 (2004-11) 125.1.2 TP naming conventions The identifier of the TP is built according to table 2. Table 2: TP naming convention Identifier: TP
36、/- = side type AP Access Point MT Mobile Terminal = protocol group ACF Association control function RRC Radio resource control function DUC DLC user connection function = functional module RA RBCH association MA Mac Id assigment LC Link_Capability EN EncryptionAU Authentication CK Common Key distrib
37、ution IT Info_Transfer MT Multicast DI Disassociation KR Key refresh AR Association rejection RQ DFS Requesting RP DF Reporting SH Sector Handover RH Radio Handover NH Network Handover HR Handover rejection SL Sleep AL Alive AB Absence CS Centralized Mode Set-up CR Centralized Mode Release CM Centra
38、lized Mode Modify CT Centralized Mode Reset DS Direct Mode Set-up DR Direct Mode Release DM Direct Mode Modify RS Direct Mode Relay Set-up RR Direct Mode Relay Release RM Direct Mode Relay Modify DT Direct Mode Reset TM Test Mode Set-up UM Unsupported message x = Type of testing CA Capability Tests
39、BV Valid Behaviour Tests BI Invalid Behaviour Tests BO Inoportune Behaviour Tests TI Timer Tests = sequential number (000-999) Test Purpose Number EXAMPLE: TP/MT/DFS/RP/BV-010 is the tenth purpose for the valid behaviour testing of the reporting procedures of the dynamic frequency selection function
40、 implemented at MT side. 5.1.3 Sources of TP definitions All TPs are specified according to TS 101 761-2 1. ETSI ETSI TS 101 823-2-2 V1.5.1 (2004-11) 135.2 Test purposes for AP 5.2.1 Association control function 5.2.1.1 RBCH Association TP/AP/ACF/RA/CA-000 Reference: TS 101 761-2 1, clause 5.1.1.1 I
41、nitial condition: MT_disassociated_from_AP. Check, that the IUT sends periodically the RBCH_ASSOCIATION message. TP/AP/ACF/RA/CA-001 Reference: TS 101 761-2 1, clause 5.1.1.1 Initial condition: MT_disassociated_from_AP Check, that the IUT, having received a RLC_RBCH_ASSOCIATION_REQ message reply wit
42、h the relevant RLC_RBCH_ASSOCIATION message. A configuration primitive is used to initialize the tester with the expected value of the broadcast variables: Number of sectors, NET ID, AP ID, AP TX level, AP RX UL level, Version indicator, AP traffic load indicator, Maximum power indicator. 5.2.1.2 Ma
43、c Id assigment TP/AP/ACF/MA/CA-000 Reference: TS 101 761-2 1, clause 5.1.1.2 Initial condition: MT_disassociated_from_AP. Check, that: after receiving the RLC_MAC_ID_ASSIGN message the IUT replies with a RLC_MAC_ID_ASSIGN_ACK message containing the assigned Mac Id. TP/AP/ACF/MA/CA-0001 Reference: TS
44、 101 761-2 1, clause 5.1.1.2 Initial condition: MT_disassociated_from_AP Check, that: after receiving the RLC_MAC_ID_ASSIGN message the IUT, if it cannot assign a MAC Id, replies with a RLC_MAC_ID_ASSIGN_NACK message. 5.2.1.3 Link capability TP/AP/ACF/LC/CA-000 Reference: TS 101 761-2 1, clause 5.1.
45、1.3 Initial condition: MAC_ID_Assigned. Check, that: after receiving the RLC_LINK_CAPABILITY message the IUT replies with a RLC_LINK_CAPABILITY_ACK message containing a set of selected parameters. 5.2.1.4 Encryption TP/AP/ACF/EN/CA-000 Reference: TS 101 761-2 1, clause 5.1.1.4 Initial condition: Lin
46、k_Agreed. Check, that: after receiving the RLC_KEY_EXCHANGE_MT_1 message and the RLC_KEY_EXCHANGE_MT_2 message, the IUT replies to the LT with a RLC_KEY_EXCHANGE_AP_1 message and a RLC_KEY_EXCHANGE_AP_2 message. ETSI ETSI TS 101 823-2-2 V1.5.1 (2004-11) 145.2.1.5 Authentication TP/AP/ACF/AU/CA-000 R
47、eference: TS 101 761-2 1, clause 5.1.1.5.3.2 Initial condition: Encryption_active. For IUT supporting IEEE MT authentication. Check, that: for IEEE MT authentication, after receiving the RLC_AUTHENTICATION (more 0) message, the IUT replies to the LT with a RLC_AUTHENTICATION_MT message with the corr
48、ect MT challenge value. TP/AP/ACF/AU/CA-001 Reference: TS 101 761-2 1, clause 5.1.1.5.3.3 Initial condition: Encryption_active. For IUT supporting extended IEEE MT authentication. Check, that: for extended IEEE MT authentication, after receiving the RLC_AUTHENTICATION (more 0) message, the IUT repli
49、es to the LT with a RLC_AUTHENTICATION_MT message with the correct MT challenge value. TP/AP/ACF/AU/CA-002 Reference: TS 101 761-2 1, clause 5.1.1.5.3.4 Initial condition: Encryption_active. For IUT supporting Net_Acc_Id MT authentication. Check, that: for Net_Acc_Id MT authentication with MT auth id up to 46 octets, after receiving the RLC_AUTHENTICATION (more 0) message, the IUT replies to the LT with a RLC_AUTHENTICATION_MT message with the correct MT challenge va
