ETSI ETS 300 476-5 ed.1 (1996-08)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Protocol Implementation Conformance Statement (PICS) proforma; Part 5: Data Link Control (DLC) layer - Fixed radio Termination (FT)33.070.30'(&7Digital Enhanced Cordless Telecommunications (DECT)ICS:Ta slovenski standard je istoveten z:ETS 300 476-5 E13SIST ETS 300 476-5:1999en01-MDQXDU-19993SIST ETS 300 476-5:1999SLOVENSKI
STANDARD
EUROPEANETS 300 476-5TELECOMMUNICATIONAugust 1996STANDARDSource: ETSI TC-RESReference: DE/RES-03042-5ICS:33.020, 33.060.50Key words:DECT, CI, PICSRadio Equipment and Systems (RES);Digital Enhanced Cordless Telecommunications (DECT);Common Interface (CI);Protocol Implementation Conformance Statement (PICS)proforma;Part 5: Data Link Control (DLC) layer -Fixed radio Termination (FT)ETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1996. All rights reserved.SIST ETS 300 476-5:1999

Page 2ETS 300 476-5: August 1996Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST ETS 300 476-5:1999

Page 3ETS 300 476-5: August 1996ContentsForeword.91Scope.112Normative references.113Definitions and abbreviations.123.1Definitions.123.2Abbreviations.124Conformance requirement to this PICS specification.12Annex A (normative):PICS proforma for DECT DLC FT.13A.1Introduction for completing the PICS proforma.13A.1.1Purposes and structure.13A.1.3Guidances for completing the PICS.15A.2Identification of the implementation.16A.2.1Date of statement.16A.2.2Implementation Under Test (IUT) identification.16A.2.3System Under Test (SUT) identification.16A.2.4Product supplier.16A.2.5Client identification.17A.2.6Contact person.17A.3Identification of the protocol.17A.4Global statement of conformance.18A.5Capabilities.18A.5.1Major capabilities.18A.5.1.1Services.18A.5.1.2Procedures.19A.5.1.2.1Generic signalling procedures.19A.5.1.2.2Class U procedures.19A.5.1.2.3Class A procedures.19A.5.1.2.4Class B procedures.20A.5.1.2.5Broadcast procedures.20A.5.1.2.6LU1 procedures.20A.5.1.2.7LU2 procedures.21A.5.1.2.8LU5 protected data procedures.21A.5.1.2.9LU5 unprotected data procedures.22A.5.1.2.10LU7 procedures.22A.5.1.2.11Management procedures.23A.5.2Protocol parameters.24A.5.2.1C-plane timers.24A.5.2.2U-plane timers.24A.5.2.3Class A parameters.25A.5.2.4Class B parameters.25A.5.2.5LU1 parameters.25A.5.2.6LU2 parameters.25A.5.2.7LU5 parameters.26A.5.2.8LU7 parameters.27A.5.3Protocol PDUs.27A.5.3.1C-plane PDUs.27SIST ETS 300 476-5:1999

Page 4ETS 300 476-5: August 1996A.5.3.1.1C-plane frame structure.27A.5.3.1.2C-plane messages.28A.5.3.1.2.1Message support.28A.5.3.1.2.2Class A I-command.29A.5.3.1.2.3Class A RR command/response.31A.5.3.1.2.4Class B I-command.32A.5.3.1.2.5Class B RR command/response.33A.5.3.1.2.6Class B RNR command/response.34A.5.3.1.2.7Class B REJ command/response.35A.5.3.1.2.8Class B SABM command.37A.5.3.1.2.9Class B DM response.38A.5.3.1.2.10Class B DISC command.39A.5.3.1.2.11Class B UA response.40A.5.3.1.2.12Class U UI command.41A.5.3.2U-plane PDUs.43A.5.3.2.1FU1 frame structure.43A.5.3.2.2FU4 frame structure.44A.5.3.2.3FU5 frame structure.45A.5.3.2.4FU6a frame structure.47A.5.3.2.5FU6b frame structure.48A.5.3.2.6FU7 frame structure.49A.5.4Protocol error handling.51A.5.4.1General error handling.51A.5.4.2Class A error handling and recovery.51A.5.4.3Class B error handling and recovery.51History.52QuestionsTable A.1: Date of Statement.16Table A.2: IUT identification.16Table A.3: SUT identification.16Table A.4: Product supplier.16Table A.5: Client.17Table A.6: Contact person.17Table A.7: Identification of protocol.17Table A.8: Global statement of conformance.18Table A.9: Data link services.18Table A.10: C-plane services.18Table A.11: U-plane services.18Table A.12: Management services.19Table A.13: Generic signalling procedures.19Table A.14: Class U procedures.19Table A.15: Class A procedures.19Table A.16: Class B procedures.20Table A.17: Broadcast procedures.20Table A.19: FU1 options.20Table A.20: LU2 procedures.21Table A.21: FU4 options.21Table A.22: FU5 options.21Table A.23: FU6 options.21Table A.24: LU5 protected data procedures.21Table A.25: LU5 unprotected data procedures.22Table A.26: LU7 procedures.22Table A.27: LU7 establishment and synchronisation procedures.22Table A.28: LU7 active phase procedures.22Table A.29: LU7 exceptional procedures.23Table A.30: Management procedures.23SIST ETS 300 476-5:1999

Page 5ETS 300 476-5: August 1996Table A.31: MAC connection management procedures.23Table A.32: DLC C-plane management procedures.23Table A.33: DLC U-plane management procedures.24Table A.34: Connection ciphering management procedures.24Table A.35: C-plane timers.24Table A.36: U-plane timers.24Table A.37: Class A parameter values.25Table A.38: Class B parameter values.25Table A.39: LU1 Frame types.25Table A.40: LU1 Connection types.25Table A.41: LU2 Frame types.25Table A.42: LU2 Connection types.26Table A.43: LU2 Transmission classes.26Table A.44: LU5 Frame types.26Table A.45: LU5 Connection types.26Table A.46: LU5 Transmission classes.27Table A.47: LU7 Frame types.27Table A.48: LU7 Connection types.27Table A.49: LU7 Transmission classes.27Table A.50: Frame structures (Receipt P to F).27Table A.51: Frame structures (Sending F to P).27Table A.52: Frame format type FA (Receipt P to F).28Table A.53: Frame format type FA (Sending F to P).28Table A.54: Broadcast service frame structure (Sending F to P).28Table A.55: Class A messages support (Receipt P to F).28Table A.56: Class A messages support (Sending F to P).28Table A.57: Class B messages support (Receipt P to F).29Table A.58: Class B messages support (Sending F to P).29Table A.59: Class U messages support (Receipt P to F).29Table A.60: Class U messages support (Sending F to P).29Table A.61: Class A I-command (Numbered Information) (Receipt P to F).29Table A.62: Class A I-command (Numbered Information) (Sending F to P).30Table A.63: Class A I-command Control field (Receipt P to F).30Table A.64: Class A I-command Control field (Sending F to P).30Table A.65: Class A I-command Address field (Receipt P to F).30Table A.66.: Class A I-command Address field (Sending F to P).30Table A.67: Class A RR-command/response (Receive ready) (Receipt P to F).31Table A.68: Class A RR-command/response (Receive ready) (Sending F to P).31Table A.69: Class A RR Control field (Receipt P to F).31Table A.70: Class A RR Control field (Sending F to P).31Table A.71: Class A RR Address field (Receipt P to F).31Table A.72: Class A RR Address field (Sending F to P).32Table A.73: Class B I-command (Numbered Information) (Receipt P to F).32Table A.74: Class B I-command (Numbered Information) (Sending F to P).32Table A.75: Class B I-command Control field (Receipt P to F).32Table A.76: Class B I-command Control field (Sending F to P).32Table A.77: Class B I-command Address field (Receipt P to F).33Table A.78: Class B I-command Address field (Sending F to P).33Table A.79: Class B RR-command/response (Receive ready) (Receipt P to F).33Table A.80: Class B RR-command/response (Receive ready) (Sending F to P).33Table A.81: Class B RR Control field (Receipt P to F).33Table A.82: Class B RR Control field (Sending F to P).34Table A.83: Class B RR Address field (Receipt P to F).34Table A.84: Class B RR Address field (Sending F to P).34Table A.85: Class B RNR command/response (Receive Not Ready) (Receipt P to F).34Table A.86: Class B RNR command/response (Receive Not Ready) (Sending F to P).34Table A.87: Class B RNR Control field (Receipt P to F).35Table A.88: Class B RNR Control field (Sending F to P).35Table A.89: Class B RNR Address field (Receipt P to F).35Table A.90: Class B RNR Address field (Sending F to P).35Table A.91: Class B REJ command/response (Reject) (Receipt P to F).35Table A.92: Class B REJ command/response (Reject) (Sending F to P).36Table A.93: Class B REJ Control field (Receipt P to F).36SIST ETS 300 476-5:1999

Page 6ETS 300 476-5: August 1996Table A.94: Class B REJ Control field (Sending F to P).36Table A.95: Class B REJ Address field (Receipt P to F).36Table A.96: Class B REJ Address field (Sending F to P).36Table A.97: Class B SABM command (Receipt P to F).37Table A.98: Class B SABM command (Sending F to P).37Table A.99: Class B SABM Control field (Receipt P to F).37Table A.100: Class B SABM Control field (Sending F to P).37Table A.101: Class B SABM Address field (Receipt P to F).37Table A.102: Class B SABM Address field (Sending F to P).38Table A.103: Class B DM-response (Disconnect Mode) (Receipt P to F).38Table A.104: Class B DM-response (Disconnect Mode) (Sending F to P).38Table A.105: Class B DM Control field (Receipt P to F).38Table A.106: Class B DM Control field (Sending F to P).38Table A.107: Class B DM Address field (Receipt P to F).39Table A.108: Class B DM Address field (Sending F to P).39Table A.109: Class B DISC command (Disconnect) (Receipt P to F).39Table A.110: Class B DISC command (Disconnect) (Sending F to P).39Table A.111: Class B DISC Control field (Receipt P to F).39Table A.112: Class B DISC Control field (Sending F to P).40Table A.113: Class B DISC Address field (Receipt P to F).40Table A.114: Class B DISC Address field (Sending F to P).40Table A.115: Class B UA-response (Unnumbered ACK) (Receipt P to F).40Table A.116: Class B UA-response (Unnumbered ACK) (Sending F to P).40Table A.117: Class B UA Control field (Receipt P to F).41Table A.118: Class B UA Control field (Sending F to P).41Table A.119: Class B UA Address field (Receipt P to F).41Table A.120: Class B UA Address field (Sending F to P).41Table A.121: Class U UI command (Unnumbered Information) (Receipt P to F).41Table A.122: Class U UI command (Unnumbered Information) (Sending F to P).42Table A.123: Class U UI Control field (Receipt P to F).42Table A.124: Class U UI Control field (Sending F to P).42Table A.125: Class U UI Address field (Receipt P to F).42Table A.126: Class U UI Address field (Sending F to P).42Table A.127: U-plane frames (Receipt P to F).43Table A.128: U-plane frames (Sending F to P).43Table A.129: FU1 frame structure (Receipt P to F).43Table A.130: FU1 frame structure (Sending F to P).43Table A.131: FU4 frame structure (Receipt P to F).44Table A.132: FU4 frame structure (Sending F to P).44Table A.133: FU4 Length indicator field (Receipt P to F).44Table A.134: FU4 Length indicator field (Sending F to P).44Table A.135: FU4 Send sequence number (Receipt P to F).44Table A.136: FU4 Send sequence number (Sending F to P).44Table A.137: FU4 Receive sequence number (Receipt P to F).45Table A.138: FU4 Receive sequence number (Sending F to P).45Table A.139: FU5 frame structure (Receipt P to F).45Table A.140: FU5 frame structure (Sending F to P).45Table A.141: FU5 Address field (Receipt P to F).45Table A.142: FU5 Address field (Sending F to P).46Table A.143: FU5 Length indicator field (Receipt P to F).46Table A.144: FU5 Length indicator field (Sending F to P).46Table A.145: FU5 Send sequence number (Receipt P to F).46Table A.146: FU5 Send sequence number (Sending F to P).46Table A.147: FU5 Receive sequence number (Receipt P to F).46Table A.148: FU5 Receive sequence number (Sending F to P).47Table A.149: FU6a frame structure (Receipt P to F).47Table A.150: FU6a frame structure (Sending F to P).47Table A.151: FU6a Length indicator field (Receipt P to F).47Table A.152: FU6a Length indicator field (Sending F to P).47Table A.153: FU6a Send sequence number (Receipt P to F).47Table A.154: FU6a Send sequence number (Sending F to P).48Table A.155: FU6b frame structure (Receipt P to F).48Table A.156: FU6b frame structure (Sending F to P).48SIST ETS 300 476-5:1999

Page 7ETS 300 476-5: August 1996Table A.157: FU6b Receive sequence number (Receipt P to F).48Table A.158: FU6b Receive sequence number (Sending F to P).48Table A.159: FU7 64 kbit/s frame structure (Receipt P to F).49Table A.160: FU7 64 kbit/s frame structure (Sending F to P).49Table A.161: FU7 64 kbit/s control field (Receipt P to F).49Table A.162: FU7 64 kbit/s control field (Sending F to P).50Table A.163: FU7 72 kbit/s frame structure (Receipt P to F).50Table A.164: FU7 72 kbit/s frame structure (Sending F to P).50Table A.165: FU7 72 kbit/s control field (Receipt P to F).50Table A.166: FU7 72 kbit/s control field (Sending F to P).51Table A.167: General error handling.51Table A.168: Class A error handling and recovery.51Table A.169: Class B error handling and recovery.51SIST ETS 300 476-5:1999

Page 8ETS 300 476-5: August 1996Blank pageSIST ETS 300 476-5:1999

Page 9ETS 300 476-5: August 1996ForewordThis European Telecommunication Standard (ETS) has been produced by the Radio Equipment andSystems (RES) Technical Committee of the European Telecommunications Standards Institute (ETSI).The DECT Common interface Protocol Implementation Conformance Statement (PICS) proformastandard comprises seven parts as follows:Part 1:"Network (NWK) layer - Portable radio Termination (PT)";Part 2:"Data Link Control (DLC) layer - Portable radio Termination (PT)";Part 3:"Medium Access Control (MAC) layer - Portable radio Termination (PT)";Part 4:"Network (NWK) layer - Fixed radio Termination (FT)";Part 5:"Data Link Control (DLC) layer - Fixed radio Termination (FT)";Part 6:"Medium Access Control (MAC) layer - Fixed radio Termination (FT)";Part 7:"Physical layer".Annex A of this specification contains the PICS proforma for the FT data link control layer.Transposition datesDate of adoption of this ETS:16 August 1996Date of latest announcement of this ETS (doa):30 November 1996Date of latest publication of new National Standardor endorsement of this ETS (dop/e):31 May 1997Date of withdrawal of any conflicting National Standard (dow):31 May 1997SIST ETS 300 476-5:1999

Page 10ETS 300 476-5: August 1996Blank pageSIST ETS 300 476-5:1999

Page 11ETS 300 476-5: August 19961ScopeThis European Telecommunication Standard (ETS) provides the Protocol Implementation ConformanceStatement (PICS) proforma for the Digital Enhanced Cordless Telecommunications Data Link Controllayer at the Fixed Termination as defined in ETS 300 175 Part 4 [4] in compliance with the relevantrequirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [14].The supplier of an implementation which is claimed to conform to ETS 300 175 Part 4 [4] is required tocomplete a copy of the PICS proforma provided in the annex A of this standard.2Normative referencesThis ETS incorporates, by dated or undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this ETS only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]ETS 300 175-1: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 1:Overview".[2]ETS 300 175-2: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 2: PhysicalLayer".[3]ETS 300 175-3: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 3: MediumAccess Control (MAC) layer".[4]ETS 300 175-4: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 4: DataLink Control (DLC) layer".[5]ETS 300 175-5: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 5: Network(NWK) layer".[6]ETS 300 175-6: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 6:Identities and addressing".[7]ETS 300 175-7: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 7: Securityfeatures".[8]ETS 300 175-8: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 8: Speechcoding and transmission".[9]ETS 300 175-9: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 9: PublicAccess Profile (PAP)".[10]ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocoland profile conformance testing specifications; Standardization methodology".[11]ISO/IEC 9646-1 (1995): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 1:General concepts".SIST ETS 300 476-5:1999

Page 12ETS 300 476-5: August 1996[12]ISO/IEC 9646-7 (1995): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 7:Implementation Conformance Statements".3Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, the following terms and definitions apply:-terms defined in ETS 300 175-1 [1]-terms defined in ISO/IEC 9646-1 [11] and in ISO/IEC 9646-7 [12].In particular, the following terms defined in ISO/IEC 9646-1 [11] apply:Implementation Conformance Statement (ICS): A statement made by the supplier of an implementationor system claimed to conform to a given specification, stating which capabilities have been implemented.The ICS can take several forms: protocol ICS, profile ICS, profile specific ICS, information object ICS, etc.ICS proforma: A document, in the form of a questionnaire, which when completed for an implementationor system becomes an ICS.Protocol ICS (PICS): A PICS for an implementation or system claimed to conform to a given protocolspecification.3.2AbbreviationsFor the purposes of this ETS, the abbreviations defined in ISO/IEC 9646-1 [11], the data link control layerabbreviations defined in ETS 300 175-4 [4], and the following abbreviations apply.ICSImplementation Conformance StatementIUTImplementation Under TestPICSProtocol Implementation Conformance StatementSCSSystem Conformance StatementSUTSystem Under Test4Conformance requirement to this PICS specificationIf it claims to conform to this ETS, the actual PICS proforma to be filled in by a supplier shall be technicallyequivalent to the text of the PICS proforma given in annex A, and shall preserve the numbering/namingand ordering of the proforma items.A PICS which conforms to this ETS shall be a conforming PICS proforma completed in accordance withthe instructions for completion given in clause A.1.SIST ETS 300 476-5:1999

Page 13ETS 300 476-5: August 1996Annex A (normative):PICS proforma for DECT DLC FTNotwithstanding the provisions of the copyright clause related to the text of the present ETS (see frontpage), ETSI grants users of this ETS to freely reproduce the PICS proforma in this annex so that it can beused for its intended purposes and may further publish the completed PICS.A.1Introduction for completing the PICS proformaA.1.1Purposes and structureThe purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation ofthe portable termination specific data link control layer requirements of ETS 300 175-4 [4]: DECT Data linkcontrol layer may provide information about the implementation in a standardized manner.The PICS proforma is subdivided into subclauses for the following categories of information:-instructions for completing the PICS proforma;-identification of the implementation;-identification of the ETS 300 175-4 [4]: DECT Data link control layer;-PICS proforma tables;-global statement of conformance;-functional groups and procedures;-timers and protocol parameters;-messages;-information elements;-protocol error handling.The PICS proforma contained in this annex is comprised of information in tabular form in accordance withthe guidelines presented in ISO/IEC 9646-7 [12].Item columnThe item column contains a number which identifies the item in the table.Item description columnThe item description column describes in free text each respective item (e.g. parameters, timers, etc.). Itimplicitly means "is supported by the implementation?".SIST ETS 300 476-5:1999

Page 14ETS 300 476-5: August 1996Status columnThe following notations, defined in ISO/IEC 9646-7 [12], are used for the status column:m or Mmandatory - the capability is required to be supported.o or Ooptional - the capability may be supported or not (e.g. the capability is notallowed because the underlying DECT layers (service provider) cannot handle itor the requirement belongs to an application i.e. does not belong to the data linkcontrol layer)n/a or N/Anot applicable - in the given context, it is impossible to use the capability.x or Xprohibited (excluded) - there is a requirement not to use this capability in thegiven context.o.i or O.iqualified optional - for mutually exclusive or selectable options from a set. "i" isan integer which identifies an unique group of related optional items and thelogic of their selection which is defined immediately following the table.ci or Ciconditional - the requirement on the capability ("m", "o", "x" or "n/a") depends onthe support of other optional or conditional items. "i" is an integer identifying anunique conditional status expression which is defined immediately following thetable.i or Iout-of-scope - this capability is outside the scope of the given specification, andhence irrelevant and not subject to conformance testing. This status is inparticular applicable for data fields which are reserved for future use. Thestructure of such fields has to be supported, but the value is undefined and thusto be ignored.Reference columnThe reference column gives reference to ETS 300 175-4 [4]: Data link control layer, except whereexplicitly stated otherwise.Support columnThe support column shall be filled in by the supplier of the implementation. The following commonnotations, defined in ISO/IEC 9646-7 [12], are used for the support column:Y or ysupported by the implementationN or nnot supported by the implementationN/A, n/a or - no answer required (allowed only if the status is n/a, directly or after evaluationof a conditional status)In each context, the kind of "non-support" which is implemented at the receipt may be additionallyindicated such as:-Errthe item is treated as a protocol error;-lgthe item is received and ignored (i.e. processed syntactically, but not semantically);-rjthe item is received and rejected.NOTE:As stated in ISO/IEC 9646-7 [12], support for a PDU requires the ability to parse allvalid parameters of that PDU. Supporting a PDU while having no ability to parse a validparameter is non-conformant. Support for a parameter on a PDU means that thesemantics of that parameter are supported.SIST ETS 300 476-5:1999

Page 15ETS 300 476-5: August 1996Values allowed columnThe values allowed column contains the values or the ranges of values allowed. The range of value isdefined as follows: [min value] . [max value]. Alternative values are defined as follows:[value1], [value 2], ., [value n].EXAMPLE:'00110000'B . '01001011'B is the value rangefrom '00110000'B to '01001011'B'00110000'B, '01001011'B the value can be '00110000'B or '01001011'B.Values supported columnThe values supported column shall be filled in by the supplier of the implementation. In this column, thevalues or the ranges of values supported by the implementation shall be indicated.Prerequisite lineA prerequisite line takes the form: Prerequisite: .A prerequisite line before a clause or table title indicates that the whole clause or the whole table is notrequired to be completed if the predicate is FALSE.A.1.3Guidances for completing the PICSThe supplier of the implementation shall complete the PICS proforma in each of the spaces providedusing the notation described in subclause A.1.2. Specific instruction is provided in the text which precedeseach table.SIST ETS 300 476-5:1999

Page 16ETS 300 476-5: August 1996A.2Identification of the implementationA.2.1Date of statementIdentification of the Implementation Under Test (IUT) and the system in which it resides (the SystemUnder Test (SUT)) should be filled in so as to provide as much detail as possible regarding versionnumbers and configuration options.Table A.1: Date of statementDate of statementDayMonthYearA.2.2Implementation Under Test (IUT) identificationThe supplier of the implementation shall enter information necessary to uniquely identify the IUT in thetable below.Table A.2: IUT identificationIUT identificationIUT nameIUT versionA.2.3System Under Test (SUT) identificationThe supplier of the implementation shall enter information necessary to uniquely identify the SUT in thetable below.Table A.3: SUT identificationIUT identificationSUT nameInternational Portable Equipment Identity (IPEI):Hardware configurationA.2.4Product supplierTable A.4: Product supplierProduct supplierNameAddressPhone No.Fax No.E-mail addressAdditionalinformationSIST ETS 300 476-5:1999

Page 17ETS 300 476-5: August 1996A.2.5Client identificationThe product supplier information and client information should both be filled in if they are different.Table A.5: ClientClientNameAddressPhone No.Fax No.E-mail addressAdditionalinformationA.2.6Contact personA person who can answer queries regarding information supplied in the PICS should be named as thecontact person.Table A.6: Contact personContact personNameAddressPhone No.Fax No.E-mail addressAdditionalinformationA.3Identification of the protocolTable A.7: Identification of protocolIdentification of protocolTitle of specificationRadio Equipment and Systems Digital Enhanced Cordless TelecommunicationsCommon Interface Part 4: Data Link Control LayerReference no.ETS 300 175-4Date of PublicationSIST ETS 300 476-5:1999

Page 18ETS 300 476-5: August 1996A.4Global statement of conformanceAn explicit answer shall be entered, in each of the support or supported column boxes provided, using thenotation described in subclause A.1.2.Table A.8: Global statement of conformanceGlobal statement of conformanceAre all mandatory capabilities implemented?NOTE:Answering "No" to this question indicates non-conformance to the specification. Non-supported mandatory capabilities are to beidentified in the ICS, with an explanation of why the implementation is non-conforming,on pages attached to the ICS proforma.A.5CapabilitiesA.5.1Major capabilitiesA.5.1.1ServicesTable A.9: Data link servicesItemData link servicesRef.StatusSupport1C-plane services5o2U-plane services11oTable A.10: C-plane servicesPrerequisite: A.9/1ItemC-plane servicesRef.StatusSupport1Class U service5.1o.102Class A service5.1o.103Class B service5.1o.104Broadcast service5.2, 9.4o.10o.10: It is mandatory to support at least one of this optionsTable A.11: U-plane servicesPrerequisite: A.9/2ItemU-plane servicesRef.StatusSupport1LU1 - Transparent Unprotected service (TRUP)11.2o.112LU2 - Frame Relay service (FREL)11.3o.113LU3 - Fram
...