ETSI EN 301 823-2-2 V1.1.1 (2001-01)

SLOVENSKI STANDARD
01-februar-2006
Širokopasovna radijska dostopovna omrežja (BRAN) – Zelo zmogljivo radijsko
lokalno omrežje (HIPERLAN), tip 2 – Specifikacija za preskušanje skladnosti
protokola krmiljenja podatkovnih povezav (DLC) – 2. del: Podplast kontrole
radijske povezave (RLC) – 2. poddel: Zgradba preskušalnega niza in namen
preskušanja (TSS&TP) – Specifikacija
Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Conformance testing
for the Data Link Control (DLC) protocol; Part 2: Radio Link Control (RLC) sublayer; Sub-
part 2: Test Suite Structure and Test Purposes (TSS&TP) specification
Ta slovenski standard je istoveten z: EN 301 823-2-2 Version 1.1.1
ICS:
33.060.01 Radijske komunikacije na Radiocommunications in
splošno general
35.110 Omreževanje Networking
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)
Broadband Radio Access Networks (BRAN);
HIPERLAN Type 2;
Conformance testing for the
Data Link Control (DLC) protocol;
Part 2: Radio Link Control (RLC) sublayer;
Sub-part 2: Test Suite Structure and
Test Purposes (TSS&TP) specification

2 ETSI EN 301 823-2-2 V1.1.1 (2001-01)
Reference
DEN/BRAN-002T004-2-2
Keywords
access, HIPERLAN, TSS&TP
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33492 94 4200 Fax: +33493 65 4716
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at http://www.etsi.org/tb/status/
If you find errors in the present document, send your comment to:
editor@etsi.fr
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2001.
All rights reserved.
ETSI
3 ETSI EN 301 823-2-2 V1.1.1 (2001-01)
Contents
Intellectual Property Rights .6
Foreword.6
1 Scope.7
2 References.7
3 Definitions and abbreviations.7
3.1 Definitions . 7
3.2 Abbreviations. 8
4 Test suite structure.9
4.1 Structure . 9
4.2 Test groups . 9
4.2.1 Protocol groups. 9
4.2.1.1 Association control function . 9
4.2.1.2 Radio resource control function . 10
4.2.1.3 DLC user connection function. 10
4.2.2 Main test groups . 10
4.2.2.1 Capability (CA) tests . 10
4.2.2.2 Valid Behaviour (BV) tests. 10
4.2.2.3 Invalid Behaviour (BI) tests . 10
4.2.2.4 Inopportune Behaviour (BO) tests. 11
4.2.2.5 Timer (TI) tests. 11
5 Test Purposes (TP).11
5.1 Introduction. 11
5.1.1 TP definition conventions. 11
5.1.2 TP naming conventions. 12
5.1.3 Sources of TP definitions . 12
5.2 Test purposes for AP . 13
5.2.1 Association control function. 13
5.2.1.1 RBCH Association . 13
5.2.1.2 Mac Id assignment. 13
5.2.1.3 Link capability. 13
5.2.1.4 Encryption. 13
5.2.1.5 Authentication. 13
5.2.1.6 Common Key distribution. 15
5.2.1.7 Information transfer. 15
5.2.1.8 Multicast . 15
5.2.1.9 Disassociation . 16
5.2.1.10 Key refresh. 16
5.2.1.11 Association rejection . 16
5.2.1.12 Unsupported messages. 16
5.2.1.13 Timers and repetitions of messages . 17
5.2.2 Radio resource control . 17
5.2.2.1 Dynamic frequency selection . 17
5.2.2.1.1 Requesting . 17
5.2.2.2 Handover. 18
5.2.2.2.1 Sector Handover. 18
5.2.2.2.2 Radio Handover . 18
5.2.2.2.3 Network Handover . 18
5.2.2.2.4 Handover Rejection. 18
5.2.2.3 Power saving. 19
5.2.2.3.1 Sleep. 19
5.2.2.3.2 Alive. 19
5.2.2.3.2.1 Mobile originated . 19
5.2.2.3.2.2 Mobile terminated. 19
ETSI
4 ETSI EN 301 823-2-2 V1.1.1 (2001-01)
5.2.2.3.3 Absence . 19
5.2.2.4 Unsupported messages. 19
5.2.2.5 Timers and repetitions of messages . 20
5.2.3 DLC user connection. 20
5.2.3.1 Centralized mode. 20
5.2.3.1.1 Set-up . 20
5.2.3.1.1.1 Mobile originated . 20
5.2.3.1.1.2 Mobile terminated. 20
5.2.3.1.2 Release . 20
5.2.3.1.2.1 Mobile originated . 20
5.2.3.1.2.2 Mobile terminated. 21
5.2.3.1.3 Modify. 21
5.2.3.1.3.1 Mobile originated . 21
5.2.3.1.3.2 Mobile terminated. 21
5.2.3.1.4 Reset. 21
5.2.3.1.4.1 Mobile originated . 21
5.2.3.1.4.2 Mobile terminated. 21
5.2.3.2 Direct mode. 22
5.2.3.2.1 Set-up VOID. 22
5.2.3.2.2 Release VOID. 22
5.2.3.2.3 Modify VOID . 22
5.2.3.2.4 Relay VOID. 22
5.2.3.3 Unsupported messages. 22
5.2.3.4 Timers and repetitions of messages . 22
5.3 Test purposes for MT . 23
5.3.1 Association control function. 23
5.3.1.1 RBCH Association . 23
5.3.1.2 Mac Id assignment. 23
5.3.1.3 Link capability. 23
5.3.1.4 Encryption. 24
5.3.1.5 Authentication. 24
5.3.1.6 Common Key distribution. 25
5.3.1.7 Information transfer. 25
5.3.1.8 Multicast . 26
5.3.1.9 Disassociation . 26
5.3.1.10 Key refresh. 26
5.3.1.11 Unsupported messages. 26
5.3.1.12 Timers and repetitions of messages . 27
5.3.2 Radio resource control . 27
5.3.2.1 Dynamic frequency selection . 27
5.3.2.1.1 Requesting . 27
5.3.2.1.2 Reporting. 27
5.3.2.2 Handover. 28
5.3.2.2.1 Sector Handover. 28
5.3.2.2.2 Radio Handover . 28
5.3.2.2.3 Network Handover . 28
5.3.2.3 Power saving. 29
5.3.2.3.1 Sleep. 29
5.3.2.3.2 Alive. 29
5.3.2.3.2.1 Mobile originated . 29
5.3.2.3.2.2 Mobile terminated. 29
5.3.2.3.3 Absence . 30
5.3.2.4 Unsupported messages. 30
5.3.2.5 Timers and repetitions of messages . 30
5.3.3 DLC user connection. 30
5.3.3.1 Centralized mode. 30
5.3.3.1.1 Set-up . 30
5.3.3.1.1.1 Mobile originated . 30
5.3.3.1.1.2 Mobile terminated. 31
5.3.3.1.2 Release . 31
5.3.3.1.2.1 Mobile originated . 31
5.3.3.1.2.2 Mobile terminated. 31
ETSI
5 ETSI EN 301 823-2-2 V1.1.1 (2001-01)
5.3.3.1.3 Modify. 31
5.3.3.1.3.1 Mobile originated . 31
5.3.3.1.3.2 Mobile terminated. 31
5.3.3.1.4 Reset. 32
5.3.3.1.4.1 Mobile originated . 32
5.3.3.1.4.2 Mobile terminated. 32
5.3.3.2 Direct mode. 32
5.3.3.2.1 Set-up VOID. 32
5.3.3.2.2 Release VOID. 32
5.3.3.2.3 Modify VOID . 32
5.3.3.2.4 Relay VOID. 32
5.3.3.3 Unsupported messages. 32
5.3.3.4 Timers and repetitions of messages . 32
History .33
ETSI
6 ETSI EN 301 823-2-2 V1.1.1 (2001-01)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); 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://www.etsi.org/ipr).
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 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 European Standard (Telecommunications series) has been produced by ETSI Project Broadband Radio Access
Networks (BRAN).
The present document is sub-part 2 of a multi-part deliverable covering Broadband Radio Access Networks (BRAN);
HIPERLAN Type 2; Conformance testing for the Data Link Control (DLC) protocol; Part 2: Radio Link Control (RLC)
sublayer, as identified below:
Sub-part 1: "Protocol Implementation Conformance Statement (PICS) proforma";
Sub-part 2: "Test Suite Structure and Test Purposes (TSS&TP) specification";
Sub-part 3: "Abstract Test Suite (ATS) specification".
National transposition dates
Date of adoption of this EN: 19 January 2001
Date of latest announcement of this EN (doa): 30 April 2001
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 October 2001
Date of withdrawal of any conflicting National Standard (dow): 31 October 2001
ETSI
7 ETSI EN 301 823-2-2 V1.1.1 (2001-01)
1 Scope
The present document contains the Test Suite Structure (TSS) and Test Purposes (TP) to test the BRAN HIPERLAN
Type 2; Data Link Control (DLC) protocol; Radio Link Control (RLC) sublayer [1].
The objective of the present document is to provide a basis for conformance tests for HIPERLAN Type 2 equipment
giving a high probability of air interface inter-operability between different manufacturers' 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 documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1] ETSI TS 101 761-2 (V1.1.1): "Broadband Radio Access Networks (BRAN); HIPERLAN Type 2;
Data Link Control (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 (1991): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 1: General concepts". (See also CCITT
Recommendation X.290 (1991)).
[4] ISO/IEC 9646-2 (1991): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 2: Abstract test suite specification". (See also CCITT
Recommendation X.291 (1991)).
[5] ISO/IEC 9646-6 (1991): "Information technology - Open Systems Interconnection - Conformance
testing methodology and framework - Part 6: Protocol profile test specification".
[6] ISO/IEC 9646-7 (1991): "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 following terms and definitions apply:
a) the terms defined in ISO/IEC 9646-7 [6]; and
b) the definitions in TS 101 761-2 [1].
ETSI
8 ETSI EN 301 823-2-2 V1.1.1 (2001-01)
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], the abbreviations defined in TS 101 761-2 [1] apply. In particular, the following abbreviations
apply:
ACF Association Control Function
AP Access Point
APT Access Point Transceiver
ARQ Automatic Repeat Request
BCH Broadcast CHannel
BI Invalid Behaviour
BO Inopportune Behaviour
BV Valid Behaviour
CA Capability tests
CC Central Controller
CL Convergence Layer
DFS Dynamic Frequency Selection
DLC Data Link Control
DUC DLC User Connection
DCC DLC user Connection Control
DM Direct Mode
EC Error Control
IUT Implementation Under Test
IV Initialization Vector
MAC Medium Access Control
MAC ID MAC Identifier
MT Mobile Terminal
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
RLC Radio Link Control
RRC Radio Resource Control
TP Test Purposes
TSS Test Suite Structure
ETSI
9 ETSI EN 301 823-2-2 V1.1.1 (2001-01)
4 Test suite structure
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 Test group
CA BV BI BO TI
RLC-AP/ RLC-MT Association control function RBCH association x
Mac ID assignment x
Link_Capability x
Encryption x
Authentication x
Common Key x
Info_Transfer x
Multicast x
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
DM Release
DM Modify
DM Relay
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 first 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 identify the RLC services: Association control function, Radio resource control function, and DLC
user connection function, as defined in TS 101 761-2 [1].
4.2.1.1 Association control function
The association control function group is divided in ten functional modules. The first functional module identifies the
RBCH association procedures. The second functional module identifies the Mac Id assignment procedures. The third
functional module distinguishes the Link Capability procedures. The fourth functional module distinguishes the
Encryption procedures. The fifth 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. The ninth functional
module distinguishes the disassociation procedures. The last functional module identifies the key refresh procedures.
ETSI
10 ETSI EN 301 823-2-2 V1.1.1 (2001-01)
4.2.1.2 Radio resource control function
The Radio resource control protocol group is divided in eight functional modules.
• The first functional module distinguishes 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 network 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 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 module 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 last functional module distinguishes the direct mode relay procedures.
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
This 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 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.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.
ETSI
11 ETSI EN 301 823-2-2 V1.1.1 (2001-01)
4.2.2.4 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.
4.2.2.5 Timer (TI) tests
This test sub group shall verify that the IUT reacts in conformity with the TS, after timer activity (start, stop, expiration,
etc.).
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 according to the TP Reference.
naming conventions 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 subclause 5.1.2.
Reference 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 TP is related.
Expected behaviour Definition of the events that are expected from the IUT to conform to the base
specification.
ETSI
12 ETSI EN 301 823-2-2 V1.1.1 (2001-01)
5.1.2 TP naming conventions
The identifier of the TP is built according to Table 2.
Table 2: TP naming convention
Identifier: TP////-
= 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 Assignment
LC Link_Capability
EN Encryption
AU Authentication
CK Common Key distribution
IT Info_Transfer
MT Multicast
DI Disassociation
KR Key Refresh
AR Association Rejection
RQ DFS Requesting
RP DFS 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 Centralized Mode Modify
CT Centralized Mode Reset
DS Direct Mode Set-up
DR Direct Mode Release
DM Direct Mode Modify
DY Direct Mode Relay
UM Unsupported message
x = Type of testing CA Capability Tests
BV Valid Behaviour Tests
BI Invalid Behaviour Tests
BO Inopportune 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 implemented at MT side.
5.1.3 Sources of TP definitions
All TPs are specified according to TS 101 761-2 [1].
ETSI
13 ETSI EN 301 823-2-2 V1.1.1 (2001-01)
5.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 - 5.1.1.1
Initial 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 - 5.1.1.1
Initial condition: MT_disassociated_from_AP.
Check, that the IUT, having received an RLC_RBCH_ASSOCIATION_REQ message
replies with 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 Mac Id assignment
TP/AP/ACF/MA/CA-000 Reference: TS 101 761-2 - 5.1.1.2
Initial condition: MT_disassociated_from_AP.
Check, that: after receiving the RLC_MAC_ID_ASSIGN message the IUT replies with
an RLC_MAC_ID_ASSIGN_ACK message containing the assigned Mac Id.
5.2.1.3 Link capability
TP/AP/ACF/LC/CA-000 Reference: TS 101 761-2 -5.1.1.3
Initial condition: MAC_ID_Assigned.
Check, that: after receiving the RLC_LINK_CAPABILITY message the IUT replies with
an 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 - 5.1.1.4
Initial condition: Link_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 an
RLC_KEY_EXCHANGE_AP_1 message and an RLC_KEY_EXCHANGE_AP_2
message.
5.2.1.5 Authentication
TP/AP/ACF/AU/CA-000 Reference: TS 101 761-2 - 5.1.1.5
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 an RLC_AUTHENTICATION_MT
message with the correct MT challenge value.
TP/AP/ACF/AU/CA-001 Reference: TS 101 761-2 - 5.1.1.5
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 replies to the LT with an
RLC_AUTHENTICATION_MT message with the correct MT challenge value.
ETSI
14 ETSI EN 301 823-2-2 V1.1.1 (2001-01)
TP/AP/ACF/AU/CA-002 Reference: TS 101 761-2 - 5.1.1.5
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 an RLC_AUTHENTICATION_MT message with the correct MT challenge value.
TP/AP/ACF/AU/CA-003 Reference: TS 101 761-2 - 5.1.1.5
Initial condition: Encryption_active.
For IUT supporting Net_Acc_Id MT authentication.
Check, that: for Net_Acc_Id MT authentication with MT auth id longer than 46 octets,
after receiving the RLC_AUTHENTICATION (more 1) message and the
RLC_AUTHENTICATION (more 0) message, the IUT replies to the LT with an
RLC_AUTHENTICATION_MT message with the correct MT challenge value.
TP/AP/ACF/AU/CA-004 Reference: TS 101 761-2 - 5.1.1.5
Initial condition: Encryption_active.
For IUT supporting Compressed authentication.
Check, that: for compressed authentication, after receiving the
RLC_AUTHENTICATION (more 0) message, the IUT replies to the LT with an
RLC_AUTHENTICATION_MT message with the correct MT challenge value.
TP/AP/ACF/AU/CA-005 Reference: TS 101 761-2 - 5.1.1.5
Initial condition: Encryption_active.
For IUT supporting Generic authentication.
Check, that: for Generic authentication with MT auth id up to 46 octets, after receiving
the RLC_AUTHENTICATION (more 0) message, the IUT replies to the LT with an
RLC_AUTHENTICATION_MT message with the correct MT challenge value.
TP/AP/ACF/AU/CA-006 Reference: TS 101 761-2 - 5.1.1.5
Initial condition: Encryption_active.
For IUT supporting Generic authentication.
Check, that: for Generic authentication with MT auth id longer than 46 octets, after
receiving the RLC_AUTHENTICATION (more 1) message and the
RLC_AUTHENTICATION (more 0) message, the IUT replies to the LT with an
RLC_AUTHENTICATION_MT message with the correct MT challenge value.
TP/AP/ACF/AU/CA-007 Reference: TS 101 761-2 - 5.1.1.5
Initial condition: Encryption_active.
For IUT supporting X509 Cert. MT authentication.
Check, that: for X509 Cert. 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 an RLC_AUTHENTICATION_MT message with the correct MT challenge value.
TP/AP/ACF/AU/CA-008 Reference: TS 101 761-2 - 5.1.1.5
Initial condition: Encryption_active.
For IUT supporting X509 Cert. MT authentication.
Check, that: for X509 Cert. MT authentication with MT auth id longer than 46 octets,
after receiving the RLC_AUTHENTICATION (more 1) message and the
RLC_AUTHENTICATION (more 0) message, the IUT replies to the LT with an
RLC_AUTHENTICATION_MT message with the correct MT challenge value.
TP/AP/ACF/AU/CA-009 Reference: TS 101 761-2 - 5.1.1.5
Initial condition: MT authenticated.
For IUT supporting Pre Shared AP authentication.
Check, that: for Pre Shared AP authentication after receiving the
RLC_AUTHENTICATION_AP_1 message with the correct AP challenge value, the
IUT replies to the LT with an RLC_AUTHENTICATION_ACK_1 message with the
correct response value.
TP/AP/ACF/AU/CA-010 Reference: TS 101 761-2 - 5.1.1.5
Initial condition: MT authenticated.
For IUT supporting RSH_Signature_64 AP authentication.
Check, that: after receiving the RLC_AUTHENTICATION_AP_1 and
RLC_AUTHENTICATION_AP_2 messages containing together the correct AP
challenge value, the IUT replies to the LT with RLC_AUTHENTICATION_ACK_1 and
RLC_AUTHENTICATION_ACK_2 messages with the correct response value.
TP/AP/ACF/AU/CA-011 Reference: TS 101 761-2 - 5.1.1.5
Initial condition: MT authenticated.
For IUT supporting RSH_Signature_96 AP authentication.
Check, that: after receiving the RLC_AUTHENTICATION_AP_1,
RLC_AUTHENTICATION_AP_2 and RLC_AUTHENTICATION_AP_3 messages
containing together the correct AP challenge value, the IUT replies to the LT with
RLC_AUTHENTICATION_ACK_1 and RLC_AUTHENTICATION_ACK_2 messages
with the correct response value.
ETSI
15 ETSI EN 301 823-2-2 V1.1.1 (2001-01)
TP/AP/ACF/AU/CA-012 Reference: TS 101 761-2 - 5.1.1.5
Initial condition: MT authenticated.
For IUT supporting RSH_Signature_128 AP authentication.
Check, that: after receiving the RLC_AUTHENTICATION_AP_1,
RLC_AUTHENTICATION_AP_2 and RLC_AUTHENTICATION_AP_3 messages
containing together the correct AP challenge value, the IUT replies to the LT with
RLC_AUTHENTICATION_ACK_1, RLC_AUTHENTICATION_ACK_2 and
RLC_AUTHENTICATION_ACK_3 messages with the correct response value.
5.2.1.6 Common Key distribution
TP/AP/ACF/CK/CA-000 Reference: TS 101 761-2 - 5.1.1.6
Initial condition: Link_Agreed_or_Encryption_active_or_Authenticated
Only for IUT that support the Direct Mode procedures.
Check, that: immediately after termination of either the link capability process or the
encryption process or the authentication process, the IUT initiates the common key
distribution procedure by sending an RLC_DM_COMMON_KEY_DISTR message to
the LT.
5.2.1.7 Information transfer
TP/AP/ACF/IT/CA-000 Reference: TS 101 761-2 - 5.1.1.7
Initial condition: Link_Agreed_or_Encryption_active_or_Authenticated
Check, that: after receiving the RLC_INFO message, the IUT replies to the LT with an
RLC_INFO_ACK message and considers the MT (LT) as MT_Associated_to_AP.
5.2.1.8 Multicast
TP/AP/ACF/MT/CA-000 Reference: TS 101 761-2 - 5.1.4
Initial condition: MT_Associated_to_AP and MT has made connection setup for
unicast traffic.
Check, that: after receiving the RLC_GROUP_JOIN message, the IUT replies to the
LT with an RLC_GROUP_JOIN_ACK message.
TP/AP/ACF/MT/CA-001 Reference: TS 101 761-2 - 5.1.5
Initial condition: MT_Associated_to_AP and MT has made connection setup for
unicast traffic.
Check, that: after receiving the RLC_CL_BROADCAST_JOIN message, the IUT
replies to the LT with an RLC_CL_BROADCAST_JOIN_ACK message.
TP/AP/ACF/MT/CA-002 Reference: TS 101 761-2 - 5.1.4
Initial condition: MT_Associated_to_AP and MT has joined a group.
Check, that: after receiving the RLC_GROUP_LEAVE message, the IUT replies to
the LT with an RLC_GROUP_LEAVE_ACK message.
TP/AP/ACF/MT/CA-003 Reference: TS 101 761-2 - 5.1.5
Initial condition: MT_Associated_to_AP and MT has joined a group.
Check, that: after receiving the RLC_ CL_BROADCAST_LEAVE message
correspondi
...