1、- c PLEASE NOTE This document is normally accompanied by a disk/dish wnen purchased in hardcopy. The dislddisks contain information which would be of no value as a hardcopy document. If you require a copy of the diskldisb, please use the contact information below for your request. When submitting yo
2、ur request, please have the following irzfonnation vuiizble: Your company name/account number Originating orsanisacion Document number USMCanada Enformation Handling Services E-mail Te!: 800-U$-3352 Outside USAiCanada Except the United I(ingdom) Information Handling Services E-mai Te!: i 1-303-790
3、-0600 Technic3 Tz!: (O Fax: (O United Kingdom Indexes Ltd 344) 404409, Custoinet Support 34.1) 40442 I, Ccistoiner Suppori In formation Handing Senices and Teclinicai Indexer - Cortitiziad to Service Excellence ETSI EN 301 469-5 1.1.1 (2000-10) European Standard (Telecommunications series) Digital E
4、nhanced Cordless Telecommunications (DECT); DECT Packet Radio Service (DPRS) Test Case Library (TCL); Part 5: Abstract Test Suite (ATS) - Data Link Control (DLC) layer - Portable radio Termination (PT) 2 ETSI EN 301 469-5 V1.l.l (2000-1 O) The pre Reference D ENID ECT-040047-5 Keywords ATS, DECT, DP
5、RS, layer 2, testing, ATS-GR file, ATS-MP file, TSS Essential, or potentially Essential, IPRs notifed to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (-). Pursuant to the ETSI IPR Policy, no investigation, inclu
6、ding 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 O00 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 (Telecommunic
7、ations series) has been produced by ETSI Project Digital Enhanced Cordless Telecommunications (DECT). The present document is part 5 of a multi-part deliverable covering the Digital Enhanced Cordless Telecommunications (DECT); DECT Packet Radio Service (DPRS) Test Case Library (TCL), as identified b
8、elow: Part 1: Part 2: Part 3: Part 4: Part 5: Part 6: Part 7: Part 8: Part 9: “Test Suite Structure (TSS) and Test Purposes (TP) - Medium Access Control (MAC) layer“; “Abstract Test Suite (ATS) - Medium Access Control (MAC) layer - Portable radio Termination (PT)“; “Abstract Test Suite (ATS) - Mediu
9、m Access Control (MAC) layer - Fixed radio Termination (FT)“; “Test Suite Structure (TSS) and Test Purposes (TP) - Data Link Control (DLC) layer“; “Abstract Test Suite (ATS) - Data Link Control (DLC) layer - Portable radio Termination (PT)“; “Abstract Test Suite (ATS) - Data Link Control (DLC) layer
10、 - Fixed radio Termination (FT)“; “Test Suite Structure (TSS) and Test Purposes (TP) - Network (NWK) layer“; “Abstract Test Suite (ATS) - Network (NWK) layer - Portable radio Termination (PT)“; “Abstract Test Suite (ATS) - Network (NWK) layer - Fixed radio Termination (FT)“. National transposition d
11、ates Date of adoption of this EN: Date of latest announcement of this EN (doa): Date of latest publication of new National Standard or endorsement of this EN (dop/e): Date of withdrawal of any conflicting National Standard (dow): 13 October 2000 3 1 January 200 1 3 1 July 200 1 3 1 July 200 1 ETSI 6
12、 ETSI EN 301 469-5 V1.l.l (2000-1 O) 1 Scope The present document contains the Abstract Test Suite (ATS) specification to test the DECT Packet Radio Service (DPRS) Data Link Control (DLC) layer at the Portable radio Termination (PT). The objective of this test specification is to provide a basis for
13、 conformance tests for DECT equipment giving a high probability of air interface inter-operability between different manufacturers DECT equipment. The IS0 standard for the methodology of conformance testing (ISO/IEC 9646-1 4 and ISO/IEC 9646-2 5) as well as the ETSI rules for conformance testing (ET
14、S 300 406 3) are used as a basis for the test methodology. Annex A provides the Tree and Tabular Combined Notation (TTCN) part of this ATS. Annex B provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of this ATS. Annex C provides the Protocol Conformance Test
15、Report (PCTR) Proforma of this ATS. 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.
16、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. il ETSI EN 300 175-3: “Digital Enhanced Cordless Telecommu
17、nications (DECT); Common Interface (CI); Part 3: Medium Access Control (MAC) layer“. ETSI EN 300 175-4: “Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 4: Data Link Control (DLC) layer“. ETSI ETS 300 406: “Methods for Testing and Specification (MTS); Protocol and pr
18、ofile conformance testing specifications; Standardization methodology“. ISO/IEC 9646- 1: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“. (See also ITU-T Recommendation X.290). ISO/IEC 9646-2: “Information technology
19、- Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract test suite specification“. (See also ITU-T Recommendation X.29 i). Pl 31 41 51 ISO/IEC 9646-3: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Pa
20、rt 3: The tree and tabular combined notation“. (See also ITU-T Recommendation X.292). ISO/IEC 9646-6: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test specification“. ISO/IEC 9646-7: “Information technology - Open
21、Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation conformance statement“. ETSI EN 30 1 649: “Digital Enhanced Cordless Telecommunications (DECT); DECT Packet Radio Services (DPRS)“. ETSI 7 ETSI EN 301 469-5 V1.l.l (2000-1 O) 3 3.1 Definitions and abbrev
22、iations Definitions For the purposes of the present document, the following terms and definitions apply: a) the terms given in ISOIIEC 9646-1 41; and b) the definitions given in EN 300 175-4 21. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ISOIIEC 9646-1 41,
23、 ISOIIEC 9646-6 71, ISOIIEC 9646-7 SI and EN 300 175-4 2 apply. In particular, the following abbreviations apply: ASP ATM ATS BI BO BV CA DLC FP FT IUT LT MAC NWK PCO PDU PICS PIXIT PMID PP PT RF RFP SAP SUT TC TDMA TP TSS TTCN UT Abstract Service Primitive Abstract Test Method Abstract Test Suite I
24、nvalid Behaviour Inopportune Behaviour Valid Behaviour Capability tests Data Link Control Fixed Part Fixed radio Termination Implementation Under Test Lower Tester Medium Access Control Network Point of Control and Observation Protocol Data Unit Protocol Implementation Conformance Statement Protocol
25、 Implementation Extra Information for Testing Portable Part MAC Identity Portable Part Portable radio Termination Radio Frequency Radio Fixed Part Service Access Point System Under Test Test Case Time Division Multiple Access Test Purposes Test Suite Structure Tree and Tabular Combined Notation Uppe
26、r Tester 4 Abstract Test Method (ATM) This clause describes the ATM used for testing the DECT DLC protocol. It is the embedded variant of Remote Single (RSE) layer test method. The RSE test method has been selected, because: - - - this test method implies no specific requirements from the IUT; the U
27、pper Service Access Point (USAP) of the IUT cannot be directly observed; the variety of the possible DECT implementations is a serious technical obstacle for the adoption of a different ATM; ETSI 8 ETSI EN 301 469-5 V1.l.l (2000-1 O) - this test method places the minimum limitations in the realizati
28、on of conformance testing. The embedded variant of the remote test method provides sufficient control of the IUT DLC behaviour, through NWK layer messages conveyed by DLC frames. Test System I 1 SUT Subset of Lc entity and FBx entities MAC-CO-DATA Figure 1 : RS test Method embedded variant LT A Lowe
29、r Tester (LT) is located in a remote DECT test system. It controls and observes the behaviour of the IUT. MSAP MAC Service Access Point - A unique MAC SAP is defined at the DECT interface and used to exchange service data of the DLC protocol. To avoid the complexity of data fragmentation and recombi
30、nation testing, the SAP is defined below this functions of the DLC layer. PCO The PCO for DLC layer testing is located on the MSAP. All test events at the PCO are specified in terms of MAC Abstract Service Primitives (ASPS) and DLC layer Protocol Data Units (PDUs). Notional UT No explicit upper test
31、er (UT) exists in the system under test. Nevertheless, some network messages are sent to the SUT for the need of the co-ordination procedures. The network layer of the SUT is used as a notional UT as defined in IS0 9646. The MAC primitives are defined according to EN 300 175-3 i clause 8 and associa
32、ted subclauses. 5 Untestable Test Purposes (TP) Due to the ATM chosen for this ATS or other restrictions, the test purposes in table 1 have been identified as being in the untestable category, and therefore have not been derived into final test case: ETSI 9 ETSI EN 301 469-5 V1.l.l (2000-1 O) Table
33、O: Untestable TP Test purpose I Reason 6 ATS Conventions This clause describes the conventions applied to define the ATS and gives the naming conventions chosen for the different elements of the ATS. The ATS conventions are intended to give a better understanding of the ATS but they describe also th
34、e conventions made for the development of the ATS, thus for any later maintenance purposes or further development of the ATS the conventions described in this clause shall be considered. The ATS conventions contain two subclauses, the naming conventions and the implementation conventions. The naming
35、 conventions describe the structure of the naming of all ATS elements. The implementation conventions describe the functional structure of the ATS. To define the ATS, the guidelines of ETS 300 406 3 was considered. 6.1 Naming conventions 6.1.1 Declarations part This subclause describes the naming co
36、nventions chosen for the elements of the ATS declarations part. 6.1 .I .I Test suite type and structured type definitions The test suite type and test suite structured type identifiers describe the information elements, and are written in uppercase: EXAMPLE: PROTOCOL-DISCRIMINATOR simple type. FILLS
37、TRING structured type. 6.1 .I .2 Test suite operations definitions The test suite operation identifiers are composed of substrings in lowercase letters, except for standard prefix “TSO-“. Each substring is separated by an underscore character (I-I). EXAMPLE: TSO-compute -checksum. 6.1 .I .3 Test sui
38、te parameter declarations The test suite parameter identifiers are composed of substrings in lowercase letters, except for the standard prefix “TSP-“. Each substring is separated by an underscore character (I-I). EXAMPLE: TSP-window-size. If the test suite parameter references a Protocol Implementat
39、ion Conformance Statement (PICS) item, the letter “C“ is added to the standard prefix. EXAMPLE: TSPC-pics-item-s23. If the test suite parameter references a PIXIT item, the letter “X“ is added to the standard prefix. EXAMPLE: TSPX-pixit-item-2. ETSI 10 ETSI EN 301 469-5 V1.l.l (2000-1 O) 6.1 .I .4 T
40、est case selection expression definitions The naming conventions for the test case selection expression definitions use free text starting with an uppercase letter. The name of the expression shall explain clearly the selection rule. The test case selection expressions are logical combinations of th
41、e test suite parameters definitions. 6.1 .I .5 Test suite constant declarations The test suite constant identifiers are composed of substrings in lowercase letters, except for the prefix “TSC-“. Each substring is separated by an underscore character (I-I). EXAMPLE: TSCretry. Complete names as define
42、d in the specifications are used. 6.1 .I .6 Test suite variable declarations The test suite variable identifiers are composed of substrings in lowercase letters, except for the prefix “TSV-“. Each substring is separated by an underscore character (I-I). EXAMPLE: TSV-count. Exception: If the test sui
43、te variable represents a system parameter or value, the name defined in the specifications is used. EXAMPLE: VR,VS . 6.1 .I .7 Test case variable declarations The test case variable identifiers are composed of substrings in lowercase letters, except for the prefix “TCV-“. Each substring is separated
44、 by an underscore character (I-I). EXAMPLE: TCV-cr-value. 6.1 .I .a PCO declarations The point of control and observation identifiers are composed of two or four capital letters, beginning with “L“, as there are only LTs. EXAMPLE: LMAC represents a PCO on MAC interface as LT in the test equipment. L
45、DLC represents a PCO on DLC interface as LT in the test equipment. 6.1 .I .9 Timer declarations Two kinds of timers can be distinguished: i) standardized: Those defined in the standard, e.g. DL-04, use exactly the same name as in the standard, beginning with a capital “T“. As there is a tolerance ma
46、rgin accepted for these timers, three values are needed: - the maximum 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 : TDL-04-max, TDL-04-min, and TDL-04. ETSI 11 ETSI EN 301
47、 469-5 V1.l.l (2000-1 O) 2) not standardized: - Those not defined in the standard, i.e. for execution use, e. g. a timer waiting for a response. These timers begin with the prefix “T-“, followed by a string in lowercase letters. EXAMPLE 2: Tresp represents a timer for controlling the response time o
48、f the IUT. 6.1 .I .IO ASP type definitions The identifier of an ASP uses exactly the nearest name as the name defined in the specifications. It is written in uppercases, finishing by an underscore character (I-I), and three capital letters indicating whether it is a request, an indication, a respons
49、e or a confirmation primitive. EXAMPLE: DL-RELEASE-REQ for an ASP containing a layer 3 release request passed to layer 2; MAC-DATA-REQ for an ASP containing a layer 2b PDU passed to layer 2a. 6.1 .I .I 1 PDU type definitions The identifier of a PDU is given in a string in uppercase letters, which represents the layer message. EXAMPLE 1: RR for the Receive Ready layer 2 message; DISCONNECT for the DISCONNECT layer 3 message. Where the message is a composite word, an underscore character (I-“) appears in the string. EXAMPLE
