ETSI TS 102 149-2-2006 Broadband Radio Access Networks (BRAN) HIPERACCESS Conformance testing for the Data Link Control (DLC) layer Part 2 Test Suite Structure and Test Purposes (T.pdf

1、 ETSI TS 102 149-2 V1.3.1 (2006-06)Technical Specification Broadband Radio Access Networks (BRAN);HIPERACCESS;Conformance testing for the Data Link Control (DLC) layer;Part 2: Test Suite Structure andTest Purposes (TSS Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI sta

2、ndards“, 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 as to the existence of o

3、ther 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 Technical Committee Broadband Radio Access Networks (BRAN). The present doc

4、ument is part 2 of a multi-part deliverable covering Broadband Radio Access Networks (BRAN); HIPERACCESS; Protocol Implementation Conformance for the Data Link Control (DLC) layer as identified below: Part 1: “Protocol Implementation Conformance Statement (PICS) proforma“; Part 2: “Test Suite Struct

5、ure and Test Purposes (TSS Part 3: “Abstract Test Suite (ATS)“. ETSI ETSI TS 102 149-2 V1.3.1 (2006-06) 6 1 Scope The present document contains the Test Suite Structure (TSS) and Test Purposes (TP) to test the BRAN HIPERACCESS; Data Link Control (DLC) layer. The objective of the present document is

6、to provide a basis for conformance tests for HIPERACCESS equipment giving a high probability of air interface inter-operability between different manufacturers HIPERACCESS 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 ET

7、SI 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 present document. References are either specific (identified by date of publicati

8、on 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 be publicly available in the expected location might be found at http:/docbo

9、x.etsi.org/Reference. 1 ETSI TS 102 000: “Broadband Radio Access Networks (BRAN); HIPERACCESS; DLC protocol specification“. 2 ETSI ETS 300 406: “Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. 3 ISO/IEC 9646-1: “Info

10、rmation technology - Open Systems Interconnection - Conformance testing methodology 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/

11、IEC 9646-6: “Information technology - Open Systems Interconnection - Conformance 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: Implem

12、entation Conformance Statements“. 3 Definitions, symbols 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 102 000 1 apply. 3.2 Symbols For the purposes of the present document, the following symbol applies: ms mill

13、isecond(s) ETSI ETSI TS 102 149-2 V1.3.1 (2006-06) 7 3.3 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 000 1 and the following apply: AP Access Point (= base station) APC AP Controller APT AP Transceive

14、r AT Access Termination (= terminal = subscriber station) ATPC Automatic Transmit Power Control ATTC Automatic Transmit Time Control BO Inopportune Behaviour BV Valid Behaviour C/I Carrier-to-Interference power ratio CE Connection Establishment CID Connection IDCM Connection Modification COC COnnect

15、ion Control CT Connection Termination DES Data Encryption StandardDL DownLink DLC Data Link Control (layer) FS Frequency Scanning IA Initial AuthenticationID IDentity INC INitialization Control IP Internet ProtocolIUT Implementation Under Test KA Key Allocation KR Key RefreshKU Keys Usage LL Leased

16、Line LS Link Supervision MAC Medium Access Control MC MultiCast OC Other Capabilities negotiation PA Parameters Acquisition PDU Protocol Data Unit PHY PHYsical (layer) PICS Protocol Implementation Conformance Statement PN Physical capabilities Negotiation RA RAnging RE Reauthentication RF Radio Freq

17、uency RLC Radio Link Control RRC Radio Resource Control SA Security Association SAID Security Association IDentity SEC SEcurity Control SI Slip Indicator TD Transmission Delay TEK Traffic Encryption Key TI Timer TP Test Purposes TP Time for Processing TS Technical SpecificationTSS Test Suite Structu

18、re UL UpLink ETSI ETSI TS 102 149-2 V1.3.1 (2006-06) 8 4 Test Suite Structure (TSS) 4.1 Structure Figure 1 shows the RLC Test Suite Structure (TSS) including its subgroups defined for the conformance testing. Test Suite Protocol group Protocol subgroup DLC-AP/ DLC-AT Initialization Control Frequency

19、 scanning Synchronization Acquisition APC Identification UL and DL Parameters Acquisition Ranging Physical Capabilities Negotiation Other Capabilities Negotiation Radio Resource Control Link Supervision Change of PHY Mode, ATPC and ATTC Load Levelling Security Control Initial Authentication Reauthen

20、tication Key Allocation Key Refresh Traffic Encryption Keys Usage Connection Control Connection Establishment Connection Modification Connection Termination Multicast Connections Figure 1: TSS for HIPERACCESS RLC The test suite is structured as a tree with a first level defined as DLC-AP or DLC-AT r

21、epresenting the protocol groups “DLC for AP“ and “DLC for AT“. 4.2 Test groups The test groups are organized in three levels. The first level creates three protocol groups representing the protocol services. The second level separates the protocol services in functional modules. The last level in ea

22、ch branch contains one or more of the standard ISO subgroups BV, TI, BO. 4.2.1 Protocol groups The protocol groups identify the DLC services: Initialization control function, Radio resource control function, Security control and Connection control function, as defined in TS 102 000 1. 4.2.1.1 Initia

23、lization control function The initialization control function group is divided in seven functional modules. The first functional module identifies the Frequency scanning procedures. The second functional module identifies the Synchronization Acquisition procedures. The third functional module distin

24、guishes the APC Identification procedures. The fourth functional module distinguishes the UL and DL Parameters Acquisition procedures. The fifth functional module identifies the Ranging procedures. The sixth functional module distinguishes the Physical Capabilities Negotiation procedures. The last f

25、unctional module distinguishes the Other Capabilities Negotiation procedures. ETSI ETSI TS 102 149-2 V1.3.1 (2006-06) 9 4.2.1.2 Radio resource control function The Radio resource control protocol group is divided in three functional modules. The first functional module distinguishes the Link Supervi

26、sion procedures. The second functional module distinguishes the Change of PHY Mode, ATPC and ATTC procedures. The last functional module identifies the Load Levelling procedures. 4.2.1.3 Security control function The Security control protocol group is divided in four functional modules. The first fu

27、nctional module contains the Initial Authentication procedures. The second functional module contains the Reauthentication procedures. The third functional module contains the Key Allocation procedures. The last functional module identifies the Key Refresh procedures. 4.2.1.4 Connection control func

28、tion The Connection control protocol group is divided in four functional modules. The first functional module identifies the Connection Establishment procedures. The second functional module identifies the Connection Modification procedures. The third functional module distinguishes the Connection T

29、ermination procedures. The last functional module distinguishes the Multicast Connections procedures. 4.2.2 Main test groups The main test groups are the valid behaviour group, the invalid behaviour group and the inopportune behaviour group. 4.2.2.1 Valid Behaviour (BV) tests This test sub group sha

30、ll 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 of the exchanged messages are considered as valid. 4.2.2.2 Timer (TI) tests This test sub group shall verify that the

31、 IUT reacts in conformity with the TS, after expiry of a defined timer. 4.2.2.3 Inopportune Behaviour (BO) tests This test sub group shall verify that the IUT reacts in conformity with the TS, after receipt of a syntactically correct PDU not expected in the actual message exchange. ETSI ETSI TS 102

32、149-2 V1.3.1 (2006-06) 105 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 according to the TP naming conventions Reference. Initial condition. Stimulus. Expected behaviour. TP

33、Id The TP Id is a unique identifier it shall be specified according to the TP naming conventions defined in the clause below. Reference The reference should contain the references of the subject to be validated by the actual TP (specification reference, clause, and paragraph). Condition The conditio

34、n 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 are expected from the IUT to conform to the base specification. 5.1.2 TP naming conventions The identif

35、ier of the TP is built according to table 2. Table 2: TP naming convention Identifier: TP/- = side type AP Access Point AT Access Termination = protocol group INC INitialization Control function RRC Radio Resource Control function SEC SEcurity Control function COC COnnection Control function= functi

36、onal module FS Frequency Scanning SA Synchronization Acquisition SI APC Identification PA UL and DL Parameters Acquisition RA RAnging PN Physical capabilities Negotiation OC Other Capabilities negotiation LS Link Supervision PT Change of PHY Mode, ATPC and ATTC LL Load Levelling IA Initial Authentic

37、ation RE REauthentication KA Key AllocationKR Key Refresh KU traffic encryption Keys Usage CE Connection Establishment CM Connection Modification CT Connection Termination MC Multicast Connections x = Type of testing BV Valid Behaviour tests TI TImer tests BO Inopportune Behaviour tests = sequential

38、 number (000 to 999) Test Purpose number ETSI ETSI TS 102 149-2 V1.3.1 (2006-06) 11EXAMPLE: TP/AT/SEC/KU/BV-010 is the tenth purpose for the valid behaviour testing of the Key Usage procedures of the Security control function implemented at AT side. 5.1.3 Sources of TP definitions All TPs are specif

39、ied according to TS 102 000 1. 5.2 Test purposes for AP 5.2.1 Initialization Control 5.2.1.1 Frequency scanning TP/AP/INC/FS/BV-000 Reference: TS 102 000 1, clause 5.2.3. Initial condition: IUT is the AP. Tester is the AT. The IUT has powered up and is operating. Check that: the IUT transmits, on th

40、e correct frequencies, frames with 1 ms fixed duration each containing a valid preamble of 32 symbols and a valid control zone. Final pseudo state: the IUT continues operating. 5.2.1.2 UL and DL Parameters Acquisition TP/AP/INC/PA/BV-000 Reference: TS 102 000 1, clause 10.3.4. Initial condition: IUT

41、 is the AP. Tester is the AT. The IUT has powered up and is operating. Check that: the IUT transmits GBI messages. Final pseudo state: the IUT continues operating. 5.2.1.3 Ranging TP/AP/INC/RA/BV-000 Reference: TS 102 000 1, SDL InitializationControl_2004_09_22. Initial condition: the IUT is transmi

42、tting GBI messages. The IUT has yet to start ranging. The MAC address corresponding to the TE is in the IUTs database. Check that: to begin ranging, the IUT transmits in the most robust PHY mode a valid Ranging Invitation message containing the TEs MAC address. Final pseudo state: IUT has started ra

43、nging. NOTE: The IUTs transmission of Ranging Grants until transmitting the Ranging Invitation is acceptable behaviour but not required for conformance. TP/AP/INC/RA/BV-001 Reference: TS 102 000 1, SDL InitializationControl_2004_09_22. Initial condition: IUT has started ranging. Check that: the IUT

44、eventually transmits a Ranging Grant for the TE. Final pseudo state: IUT is waiting for a Ranging Request. NOTE: The IUTs transmission of additional Ranging Invitations between the first invitation and the Ranging Grant is acceptable behaviour but not required for conformance. TP/AP/INC/RA/BV-002 Re

45、ference: TS 102 000 1, SDL InitializationControl_2004_09_22. Initial condition: IUT is waiting for a Ranging Request. Check that: after not receiving a Ranging Request response for the Ranging Grant, the IUT eventually transmits a Ranging Invitation containing the TEs MAC address. Final pseudo state

46、: IUT has started ranging. NOTE: The IUTs transmission of additional Ranging Grants until transmitting the Ranging Invitation is acceptable behaviour but not required for conformance. TP/AP/INC/RA/BV-003 Reference: TS 102 000 1, SDL InitializationControl_2004_09_22. Initial condition: IUT is waiting

47、 for a Ranging Request. Check that: after not receiving a Ranging Request response for the Ranging Grant, the IUT continues transmitting Ranging Grants until receiving a valid Ranging Req message. Final pseudo state: IUT is waiting for a Ranging Request. NOTE: The IUT“ transmission of additional Ran

48、ging Invitation messages while transmitting the successive Ranging Grants is acceptable behaviour but is not required for conformance. ETSI ETSI TS 102 149-2 V1.3.1 (2006-06) 12TP/AP/INC/RA/BV-004 Reference: TS 102 000 1, SDL InitializationControl_2004_09_22. Initial condition: IUT is waiting for a

49、Ranging Request. Check that: when the TE sends a Ranging Request with transmission characteristics that require continued ranging, the IUT transmits a Ranging Continue message followed by a Ranging Grant at least 10 frames after the Ranging Continue message. Final pseudo state: IUT is waiting for a Ranging Request. TP/AP/INC/RA/BV-005 Reference: TS 102 000 1, SDL InitializationControl_2004_09_22. Initial condition: IUT is waiting for a Ranging Request. Check that: each time the TE sends a Ranging Request with transmission c