1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T F.515TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (04/2003) SERIES F: NON-TELEPHONE TELECOMMUNICATION SERVICES Directory services Unified Directory Specification ITU-T Recommendation F.515 ITU-T F-SERIES RECOMMENDATIONS NON-TELEPHONE TELECOMMUNICATION
2、SERVICES TELEGRAPH SERVICE Operating methods for the international public telegram service F.1F.19 The gentex network F.20F.29 Message switching F.30F.39 The international telemessage service F.40F.58 The international telex service F.59F.89 Statistics and publications on international telegraph ser
3、vices F.90F.99 Scheduled and leased communication services F.100F.104 Phototelegraph service F.105F.109 MOBILE SERVICE Mobile services and multidestination satellite services F.110F.159 TELEMATIC SERVICES Public facsimile service F.160F.199 Teletex service F.200F.299 Videotex service F.300F.349 Gene
4、ral provisions for telematic services F.350F.399 MESSAGE HANDLING SERVICES F.400F.499 DIRECTORY SERVICES F.500F.549 DOCUMENT COMMUNICATION Document communication F.550F.579 Programming communication interfaces F.580F.599 DATA TRANSMISSION SERVICES F.600F.699 AUDIOVISUAL SERVICES F.700F.799 ISDN SERV
5、ICES F.800F.849 UNIVERSAL PERSONAL TELECOMMUNICATION F.850F.899 HUMAN FACTORS F.900F.999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. F.515 (04/2003) i ITU-T Recommendation F.515 Unified Directory Specification Summary This Recommendation provides a directory sp
6、ecification to fulfil the service requirements of ITU-T Rec. F.510. The directory specification is named Unified Directory Specification (UDS) to reflect that it allows a great variety of database structures to be supported. The ITU-T Rec. F.510 service is realized by the Unified Directory Access Pr
7、otocol (UDAP). This protocol is expressed using the eXtensible Markup Language (XML) schema notation. UDAP has been designed in a way that facilitates an easy mapping to ITU-T Rec. E.115. The structure of this Recommendation follows the structure of ITU-T Rec. F.510. Certain clauses in ITU-T Rec. F.
8、510 do not require a corresponding specification and are left void. Source ITU-T Recommendation F.515 was prepared by ITU-T Study Group 17 (2001-2004) and approved under the ITU-T Recommendation A.8 procedure on 22 April 2003. ii ITU-T Rec. F.515 (04/2003) FOREWORD The International Telecommunicatio
9、n Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view
10、 to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendati
11、ons is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for concisene
12、ss to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation i
13、s achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELL
14、ECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whe
15、ther asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are c
16、autioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2003 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. F.515 (04/200
17、3) iii CONTENTS Page 1 Scope 1 2 Normative references 1 3 Definitions 1 3.1 White pages service definitions 1 3.2 Unified directory definitions 2 4 Abbreviations 2 5 Conventions 2 5.1 Text conventions 2 5.2 XML notation conventions. 3 6 Directory service model 3 7 Directory information model 4 7.1 I
18、nformation structure 4 7.2 Geography 9 7.3 Business classification 9 7.4 Organizational structure . 9 7.5 Subscriber entry 9 8 Service specification. 14 9 Common Protocol Specification element . 14 9.1 Character set, encoding and repertoire . 14 9.2 Matching rules 15 9.3 Language differences 15 9.4
19、Ordering of entries within a response. 15 9.5 Hierarchical groups 15 9.6 Number of entries. 17 9.7 Entry count . 17 9.8 Alternative directory attribute values . 17 9.9 Weighted directory attribute values 17 9.10 Geographical extensions. 17 9.11 Ignore if absent. 17 9.12 Paged Results request. 17 10
20、The Unified Directory Access Protocol (UDAP) . 18 10.1 Service model . 18 10.2 Search controls and indications 18 10.3 Predicates 18 iv ITU-T Rec. F.515 (04/2003) Page 10.4 Common query conditions . 18 10.5 Basic service offering. 19 10.6 Enhanced service offering 21 11 Operational issues. 21 11.1 S
21、ecurity. 21 12 Charging and accounting 21 13 Quality of Service. 21 Annex A Message codes and notifications . 21 A.1 Notification attribute types. 21 A.2 Message codes 22 Annex B XML schema for UDAP 28 B.1 Search request. 28 B.2 Search result . 29 B.3 Attribute Types. 30 Annex C Use of Web Service f
22、acilities 42 C.1 Use of Simple Object Access Protocol (SOAP). 42 Annex D ASN.1 version of UDAP . 44 ITU-T Rec. F.515 (04/2003) v Introduction This Recommendation provides a directory specification to fulfil the service requirements of ITU-T Rec. F.510. The directory specification is named Unified Di
23、rectory Specification (UDS) to reflect that it allows a great variety of database structures to be supported. The ITU-T Rec. F.510 service is realised by the Unified Directory Access Protocol (UDAP). This protocol is expressed using the eXtensible Markup Language (XML) schema notation. UDAP has been
24、 designed in a way that facilitates an easy mapping to ITU-T Rec. E.115. The structure of this Recommendation follows the structure of ITU-T Rec. F.510. Certain clauses in ITU-T Rec. F.510 do not require a corresponding specification and are left void. Annex A, which is an integral part of this Reco
25、mmendation, list the messages codes as defined in Annex A/F.510, and it lists the conditions under which they are generated and what additional information is associated with each message code. Annex B, which is an integral part of this Recommendation, gives the formal specification of UDAP in XML s
26、chema notation. Annex C, which is an integral part of this Recommendation, specifies how UDS uses underlying services. Annex D, which is an integral part of this Recommendation, gives the formal specification of UDAP in ASN.1 notation. An implementation shall implement the encoding specified either
27、in Annex B, or in Annex D, or in both. ITU-T Rec. F.515 (04/2003) 1 ITU-T Recommendation F.515 Unified Directory Specification 1 Scope This Recommendation only considers directory information retrieval using the search operation. Requirements on administrative workstations or administrative capabili
28、ties are outside the scope of this Recommendation. This Recommendation supports the Directory Service as specified by ITU-T Rec. F.510. However, it could be used in other environments. This Recommendation considers only client to directory server communication. It does not consider directory server
29、to directory server communication. 2 Normative references The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendation
30、s and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly publishe
31、d. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T Recommendation E.115 (1995), Computerized directory assistance. ITU-T Recommendation F.510 (2003), Automated directory assistance White pages service definitio
32、n. ITU-T Recommendation X.693 (2001) | ISO/IEC 8825-4:2002, Information technology ASN.1 encoding rules: XML Encoding Rules (XER). ISO/IEC 10646-1:2000, Information technology Universal Multiple-Octet Coded Character Set (UCS) Part 1: Architecture and Basic Multilingual Plane. ISO 3166 (all parts),
33、Codes for the representation of names of countries and their subdivisions. 3 Definitions 3.1 White pages service definitions The following terms are defined in ITU-T Rec. F.510: a) (directory) attribute; b) (directory) entry; c) directory service; d) hierarchical group; e) key attribute; f) query se
34、rvice entry. 2 ITU-T Rec. F.515 (04/2003) 3.2 Unified directory definitions This Recommendation defines the following terms: 3.2.1 client: An application that issues directory requests and receives directory information in responses. 3.2.2 directory server: An application that can return directory i
35、nformation when receiving request over the Unified Directory Access Protocol. 3.2.3 entry: A collection of directory attributes and families that comprises the information held about an object. 3.2.4 family: A grouping of related directory attributes within an entry. 3.2.5 filter: A construct carrie
36、d in a search request to be matched against entry information. 3.2.6 filter item: A component of a filter that carries information to be matched against directory attributes of a particular type. 3.2.7 object: An entity, e.g., a person, that is represented by an entry of a directory server. 4 Abbrev
37、iations This Recommendation uses the following abbreviations: ASN.1 Abstract Syntax Notation One DMD Directory Management Domain GSM Global System for Mobile communications IANA Internet Assigned Numbers Authority ISDN Integrated Services Digital Network LDAP Lightweight Directory Access Protocol PS
38、TN Public Switched Telephone Network SMS Short Message Service SOAP Simple Object Access Protocol UDAP Unified Directory Access Protocol UDS Unified Directory Specification UMTS Universal Mobile Telecommunications System XML eXtensible Markup Language 5 Conventions 5.1 Text conventions There is term
39、inology collision between that of directories and that of eXtensible Markup Language (XML). The terms attributes and schema are used in both environments. To avoid confusions, those two terms are qualified by “directory“ or “XML“, as appropriate. This Recommendation presents XML notation in Courier
40、New, 9-point typeface and ASN.1 in Courier New, 10-point typeface. When XML specifications are referenced in normal text, they are differentiated from other text by presenting them in the bold Courier New, 10-point typeface. ITU-T Rec. F.515 (04/2003) 3 5.2 XML notation conventions 5.2.1 General on
41、XML notation All complex and simple XML types defined by this Recommendation have a name that starts with an uppercase letter. All names of non-abstract XML elements defined by this Recommendation start with a lowercase letter. All names of XML attributes defined by this Recommendation start with a
42、lowercase letter. All names of abstract elements start with uppercase letter. 5.2.2 Syntaxes with upper bounds Most directory attribute types with string syntax has a maximum length, termed upper bound. Simple XML types, which specifies upper limits, are defined for that purpose. The name of such a
43、simple XML type is the letters Ub plus a number, for example Ub64, where the number indicates the upper bound in number of characters for the type. Such types are derived from the XML built-in string type. 5.2.3 Enumerated types Some elements and XML attributes may take one out of several predefined
44、 values. Special XML simple types are defined for such element types. The XML built-in type NCName is the base type for an enumerated type. An XML enumerated simple type is named by taking a descriptive name, e.g., AttributeType. The first character of the name of such a simple type is an uppercase
45、letter. The value of an XML element or an XML attribute of the enumerated type shall be exactly one of the defined enumerated values. 5.2.4 List types The XML list type facility is used where several values of an enumerated type may be required within a single XML element or XML attribute. An XML si
46、mple list type is given a descriptive name suffixed with an s, e.g., AttributeTypes. The first character of the name of such a simple type is an uppercase letter. A value of this type holds zero or more of the defined enumerated values. 5.2.5 Abstract element schema definitions and substitution grou
47、ps Abstract XML element schema definitions are used as “head“ elements for XML schema substitution groups. The first character of a name of an abstract XML element is an uppercase letter. 6 Directory service model Figure 1 illustrates the position of the UDAP with respect to different components def
48、ined within clause 6/F.510. The protocol between the access service and the query service agent could be any private or standardized protocol. In particular, it could be UDAP as defined by this Recommendation. The query service agent may, dependent on circumstances, provide some of the ITU-T Rec. F.
49、510 service elements. However, the UDAP supports the full set of ITU-T Rec. F.510 service elements. 4 ITU-T Rec. F.515 (04/2003) .F.515_F01UserUserUserLocal agentOperatorOperatorOperatorworkstationOperatorworkstationOperatorOperatorworkstationAccessserviceLocal agentUserWorkstation/access serviceQueryServiceAgentQueryServiceAgentUDAPUDAPUDSserverF.510serviceinterfaceFigure 1/F.515 Possible service scenarios As the UDAP may be used in other places than indicated in Figure 1, the term client is used for the function that issues a UDAP req
