ETSI ETS 300 374-6-1998 Intelligent Network (IN) Intelligent Network Capability Set 1 (CS1) Core Intelligent Network Application Protocol (INAP) Part 6 Protocol Implementation Conf.pdf

1、 STDOETSI ETS 300 374-b-ENGL 1998 D 3400855 0330037 554 D EUROPEAN v I ELECOMMUNICATION STANDARD ETS 300 374-6 September 1998 Source: SPS Reference: DUSPS-03032-2 ICs: 33.020 Key words: IN, INAP, CS1, PICS Intelligent Network (IN); Intelligent Network Capability Set 1 (CSI); Core Intelligent Network

2、 Application Protocol (INAP); Part 6: Protocol Implementation Conformance Statement (PICS) proforma specification for the Service Control Function (SCF) - Service Data Function (SDF) interface ETSI European Telecommunications Standards Institute ETSI Secretariat Postal address: F-06921 Sophia Antipo

3、lis CEDEX - FRANCE Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE Internet: secretariatetsi.fr - http:/www.etsi.fr - http:/www.etsi.org Tel.: +33 4 92 94 42 O0 - Fax: 43 4 93 65 47 16 Copyright Notification: No pari may be reproduced except as authofeed by written perm

4、ission. The copyright and the foregoing restriction extend to reproduction in all media. O European Telecommunications Standards Institute 1998. All rights reserved. Page 2 ETS 300 374-6: September 1998 Whilst every care has been taken in the preparation and publication of this document, errors in c

5、ontent, typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to “ETSI Standards Making Support Dept.“ at the address shown on the title page. STD-ETSI ETS 300 374-b-ENGL 1778 9 3400855 0330017 327 9 Page 3 ETS 300 374-6: September 1998 Contents Foreword .

6、 5 Introduction 5 1 Scape 7 2 Normative references 7 3 Definitions and abbreviations 7 3.1 Definitions 7 3.2 Abbreviations . 8 4 Conformance to this PICS proforma specification 8 Annex A (normative): PICS proforma for ETS 300 374-5 . 9 A . 1 A . 2 A.3 A.4 Guidance for completing the PICS proforma 9

7、A.1.1 Purposes and structure 9 A.1.2 Abbreviations and conventions 9 A.1.3 Instructions for completing the PICS proforma 11 Identification of the implementation . 11 A.2.1 Date of the statement Il A.2.2 Implementation Under Test (IUT) identification . 11 A.2.3 System Under Test (SUT) identification

8、11 A.2.4 Product supplier . 12 A.2.5 . Client 12 A.2.6 PICS contact person 13 Identification of the protocol 13 PICS proforma tables 13 A.4.1 Global statement of conformance 13 A.4.2 System definition 14 A.4.2.1 System implementation . 14 A.4.2.2 SDF implementation and/or system 14 A.4.2.3 SCF imple

9、mentation and/or system 15 IN Directory information objects supported 15 Operations and extensibility supported (SDF) . 15 A.4.4.1 Operations . 15 A.4.4.2 Extensibility 16 A.4.5 Parameters (SDF) 16 A.4.3 A.4.4 A.4.5.1 A.4.5.2 A.4.5.3 A.4.5.4 A.4.5.5 DirectoryBind Parameters . 16 A.4.5.1.1 DirectoryB

10、indArgument 16 A.4.5.1.2 DirectoryBindResult . 17 A.4.5.1.3 DirectoryBindError . 17 Search . 17 A.4.5.2.1 SearchArgument 17 A.4.5.2.2 SearchResult . 18 AddEnt ry 18 A.4.5.3.1 AddEntryArgument 18 A . 4.5.3.2 AddEntryResult 18 RemoveEntry . 19 A.4.5.4.1 RemoveEntiyArgument . 19 A.4.5.4.2 RemoveEntryRe

11、sult . 19 ModifyEntry 19 STD-ETSI ETS 300 374-b-ENGL 1798 W 3q00855 03311020 O43 = Page 4 ETS 300 374-6: September 1998 A.4.5.5.1 A.4.5.5.2 ModifyEntryArgument _._ 19 ModifyEntry Result . . . . A.4.5.6 Errors . A.4.5.8 Common results A.4.5.9 ServiceControls . A.4.5.10 EntrylnformationSelection 22 A.

12、4.5.11 Entrylnformation . A.4.5.12 FilterElements . A.4.5.13 FilterltemElements A.4.6 Operations and extensibility sup A.4.6.1 Operations . . 23 A.4.6.2 Extensibility . A.4.5.7 Common arguments . 21 A.4.7 Parameters (SCF) A.4.7.1 A. 4.7.2 A.4.7.3 A.4.7.4 A.4.7.5 A.4.7.6 A.4.7.7 A.4.7.8 A. 4.7.9 A.4.

13、7.1 0 A.4.7.11 A.4.7.12 A.4.7.13 DirectoryBind Parameters . 24 A.4.7.1.1 DirectoryBindArgument . ._._ 24 A.4.7.1.2 DirectoryBindResult 25 A.4.7.1.3 DirectoryBindError . A.4.7.2.2 SearchResult . . 26 A.4.7.3.1 AddEntryArgument A.4.7.3.2 AddEntryResult . . Errors ,. . 29 . 30 Entrylnformation 31 Filte

14、rElements . 31 FilterltemElements 31 A.4.8 Directory schema . 32 A.4.8.1 A.4.8.2 A.4.8.3 A.4.8.4 A.4.8.5 A.4.8.6 A.4.8.7 History . ,. ,. Supported object classes . 32 A.4.8.1.1 Standard es, _. _ 32 Supported attribute types . 32 A.4.8.2.1 Standard attribute types . . 32 Standard matching rules . . s

15、upported by the implementation?“. Status column The following notations, defined in ISO/IEC 9646-7 9, are used for the status column: m O mandatory - the capability is required to be supported. optional - the capability may be supported or not. nia not applicable - in the given context, it is imposs

16、ible to use the capability. i X o. i irrelevant or out-of-scope - this capability is outside the scope of this specification , and hence irrelevant and not subject to conformance testing for this specification. prohibited (excluded) - there is a requirement not to use this capability in the given co

17、ntext. qualified optional - for mutually exclusive or selectable options from a set. “i“ is an integer which identifies an unique group of related optional items and the logic of their selection which is defined immediately following the table. Page 10 ETS 300 374-6: September 1998 ci c: o c: m cond

18、itional - the requirement on the capability (“m“, “o“, “x“ or “da“) depends on the support of other optional or conditional items. “i“ is an integer identifying an unique conditional status expression which is defined immediately following the table. conditional optional - the capability may be supp

19、orted or not if the hierarchically preceding capability is supported. conditional mandatory - the capability is required to be supported if the hierarchically preceding capability is supported. Reference column The reference column gives reference to the requirements defined in ETS 300 374-5 l, exce

20、pt where explicitly stated otherwise. Support column The support column shall be filled in by the supplier of the implementation. The following common notations, defined in ISOIIEC 9646-7 191, are used for the support column: Y or y supported by the implementation. Norn not supported by the implemen

21、tation. NIA, nla or - no answer required (allowed only if the status is nla or i, directly or after evaluation of a conditional status). If this PICS proforma is completed in order to describe a multiple-profile support in a system, it is necessary to be able to answer that a capability is supported

22、 for one profile and not supported for another. In that case, the supplier shall enter the unique reference to a conditional expression, preceded by “?“ (e.g. ?3). This expression shall be given in the cell provided at the bottom of the table. It uses predicates defined in the SCS, each of which ref

23、ers to a single profile and which takes the value TRUE if and only if that profile is to be used. EXAMPLE: ?3: IF prof1 THEN Y ELSE N It is also possible to provide a comment to an answer in the space provided at the bottom of the table NOTE: As stated in ISOIIEC 9646-7 9, support for a PDU requires

24、 the ability to parse all valid parameters of that PDU. Supporting a PDU while having no ability to parse a valid parameter is non-conformant. Support for a parameter on a PDU means that the semantics of that parameter are supported. Values allowed column The values allowed column contains the value

25、s or the ranges of values allowed. Values supported column The values supported column shall be filled in by the supplier of the implementation. In this column, the values or the ranges of values supported by the implementation shall be indicated. References to items For each possible item answer (a

26、nswer in the support column) within the PICS proforma exists a unique reference, used, for example, in the conditional expressions. It is defined as the table identifier, followed by a solidus character “P, followed by the item number in the table. If there is more than one support column in a table

27、, the columns shall be discriminated by letters (a, b, etc.), respectively. EXAMPLE 1: A.5/4 is the reference to the answer of item 4 in table 5 of annex A. STD-ETSI ETS 300 374-b-ENGL 1998 I 3400855 0330027 4T3 I Page 11 ETS 300 374-6: September 1998 EXAMPLE 2: A.6/3b is the reference to the second

28、 answer (.e. in the second support column) of item 3 in table 6 of annex A. Prerequisite line A prerequisite line takes the form: Prerequisite: . A prerequisite line after a clause or table title indicates that the whole clause or the whole table is not required to be completed if the predicate is F

29、ALSE. A.1.3 Instructions for completing the PICS proforma The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. More detailed instructions are given at the beginning of the different subclauses of the PICS proforma. A.2 Identification of the implementati

30、on Identification of the Implementation Under Test (IUT) and the system in which it resides (the System Under Test (SUT) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should

31、 both be filled in if they are different. A person who can answer queries regarding information supplied in the PICS should be named as the contact person. A.2.1 Date of the statement . A.2.2 Implementation Under Test (IUT) identification IUT name: . . IUT version: A.2.3 SUT name: System Under Test

32、(SUT) identification . Hardware configuration: . . . STD*ETSI ETS 300 374-b-ENGL 1998 3400855 0330028 33T Page 12 ETC 300 374-6: September 1998 Operating system: A.2.4 Product supplier Name: Address: Telephone number: Facsimile number: E-mail address: Additional information: A.2.5 Client Name: Addre

33、ss: Telephone number: Facsimile number: STD-ETSI ETS 300 374-b-ENGL 1998 3400855 0330027 27b M Page 13 ETS 300 374-6: September 1998 E-mail address: . Additional information: . . . A.2.6 PICS contact person Name: . Telephone number: . Facsimile number: . E-mail address: . Additional information: . .

34、 . A.3 Identification of the protocol This PICS proforma applies to the following standard: ETS 300 374-5 (1996): “intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core Intelligent Network Application Protocol (INAP); Part 5: Protocol Specification for the Service Control Functi

35、on (SCF) - Service Data Function (SDF) interface“. A.4 PICS proforma tables An explicit answer shall be entered, in each of the support or supported column boxes provided, using the notation described in subclause A.1.2. A.4.1 Global statement of conformance Are all mandatory capabilities implemente

36、d? (Yes/No) . NOTE: Answering “No“ to this question indicates non-conformance to ETS 300 374-5 l specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming, on pages attached to the PICS proforma. Page 14 ETS

37、300 374-6: September 1998 A.4.2 System definition Item 1 2 A.4.2.1 System implementation Question Status Support The supplied implementation is an SDF The supplied implementation is an SCF 0.1 0.1 Table A.l: Identification of the system 13 classes? (ITU-T Recommendation X.501, 12.3) for its portion

38、of the DIT? (ITU-T Recommendation X.501, 14) Is the SDF capable of supporting the subschema 3 ; 14 O o. 1 At least on of the implementations should be supplied. A.4.2.2 SDF implementation andlor system Table A.2: SDF implementation andlor system Prerequisite: A.1/1 lattributes? (ITU-T Recommendation

39、 X.501, 12.4) I 12 Ils the SDF capable of supporting auxiliary object 13 ; 12.3 O - STDeETSI ETS 300 374-b-ENGL 1778 9 3400855 0330033 72Li Item 1 2 3 4 Page 15 ETS 300 374-6: September 1998 Question Reference Status Support Is the inDirectoryAccessAC application-context lo ;2.2.2.2.2.2.1 m supporte

40、d? Supported Security 31 ; 15 m Level) :3 ; 15 O Does the SCF/DUA follow the rules of m extensibility as define in section 7.5 of ITU-T Recommendation X.519? 6 ; 7.5 A.4.2.3 SCF implementation andlor system Item 1 Table A.3: SCF implementation and/or system Name Reference Status Support Values Allow

41、ed I Supported directoryAccessAC 161 : 7.2.1 m n-ds*) 3 1 I Prerequisite: A.1/2 Item 1 2 Name Reference Status Support Values Allowed Supported directoryOperationsAS 11 O ; 2.2.2.2.2.1.1 m il-dS*) 5 1 directoryBindingAS 301 ; 2.2.2.2.2.1.1 m i ?-dS*) 5 2 A.4.3 IN Directory information objects suppor

42、ted *) in-ds = ITU-T Recommendation Q.1218 sdf-object *) in-ds = ITU-T Recommendation (2.1218 sdf-object A.4.4 Operations and extensibility supported (CDF) A.4.4.1 Operations Table A.6: Operations supported (SDF) Prerequisite A.1/1 - if SDF implemented Page 16 ETS 300 374-6: September 1998 A.4.4.2 E

43、xtensibility 1 1.1 1.1.1 1.1.1.1 1.1.1.2 1.1.1.3 1.1.1.3.1 1.1.1.3.2 1.2 This table defines a number of extensions which are available in the 1993 edition of the Directory. The supplier of the implementation shall indicate in the following table, which conformance is claimed. DirectoryBindArg creden

44、tials simple name validity password unprotected protected versions Table A.7: Extensibility Prerequisite A.1/1 - if SDF implemented Parameters A.4.5 Parameters (SDF) This clause needs only to be completed if SDF is implemented. A.4.5.1 DirectoryBind Parameters A.4.5.1.1 Directory BindArgument Table

45、A.8: DirectoryBindArgument Parameters (SDF) Prerequisite A.l/l - if SDF implemented 1 Item I Parameter c802: IF A.2/3 then m else N/A -simple security STD-ETSI ETS 300 379-b-ENGL 1998 3900855 0330033 ?T? m Item 1 1.1 1.2 1.3 Page 17 ETS 300 374-6: September 1998 Parameter Reference Status Support Va

46、lues Allowed Supported DirectoryBindError :5 ; 8.1.1 m versions 51 : 8.1.1 c:m d (vl ) ServiceError :5 : 8.1.1 c: m 2 SecuritvError -51: 8.1.1 c:m 1.2.7 A.4.5.1.2 Directory BindResult Table A.9: DirectoryBindResult Parameters (SDF) Prerequisite A.1/1 - if SDF implemented c902: IF A.2/3 then m else N

47、/A -simple security A.4.5.1.3 DirectoryBindError Table A.lO: DirectoryBindError Parameters (SDF) Prerequisite A.1/1 - if SDF implemented A.4.5.2 Search A.4.52.1 Search Argument Table A.11: SearchArgument Parameters (SDF) Prerequisite A.l I1 AND A.27/3 then m else N/A - if SDF and Search implemented

48、c1101: IF A.28/7 then m else N/A - Page 18 ETS 300 374-6: September 1998 A.4.5.2.2 SearchResuit Item 1 Table A.12: SearchResuit Parameters (SDF) Parameter Reference Status Support Values Allowed I Supported AddEntryResult 51; 11.1.1 m Prerequisite A.1/1 AND A.27 /3 then m else N/A - if SDF and Searc

49、h implemented A.4.5.3 AddEntry A.4.5.3.1 AddEntryArgument Table A.13: AddEntryArgument Parameters (SDF) Prerequisite A.1/1 AND A.27 /4 then m else N/A - if SDF and AddEntry implemented Parameter A.4.5.3.2 AddEntry Result Table A.14: AddEntryResult Parameters (SDF) Prerequisite A.1/1 AND A.27/4 then m else N/A - if SDF and AddEntry implemented STDnETSI ETS 300 374-b-ENGL 1998 3L+00855 0330035 57T Item Parameter Reference Status Support Values Allowed I Supported . 1 RemoveE