ITU-T H 350 1-2011 Directory services architecture for H 323 (Study Group 16)《H 323目录业务结构 16号研究组》.pdf

1、 International Telecommunication Union ITU-T H.350.1TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (05/2011) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMSInfrastructure of audiovisual services Directory services architecture for audiovisual and multimedia services Directory services architecture for

2、 H.323 Recommendation ITU-T H.350.1 ITU-T H-SERIES RECOMMENDATIONS AUDIOVISUAL AND MULTIMEDIA SYSTEMS CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS H.100H.199 INFRASTRUCTURE OF AUDIOVISUAL SERVICES General H.200H.219 Transmission multiplexing and synchronization H.220H.229 Systems aspects H.230H.239 C

3、ommunication procedures H.240H.259 Coding of moving video H.260H.279 Related systems aspects H.280H.299 Systems and terminal equipment for audiovisual services H.300H.349 Directory services architecture for audiovisual and multimedia services H.350H.359Quality of service architecture for audiovisual

4、 and multimedia services H.360H.369 Supplementary services for multimedia H.450H.499 MOBILITY AND COLLABORATION PROCEDURES Overview of Mobility and Collaboration, definitions, protocols and procedures H.500H.509 Mobility for H-Series multimedia systems and services H.510H.519 Mobile multimedia colla

5、boration applications and services H.520H.529 Security for mobile multimedia systems and services H.530H.539 Security for mobile multimedia collaboration applications and services H.540H.549 Mobility interworking procedures H.550H.559 Mobile multimedia collaboration inter-working procedures H.560H.5

6、69 BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES Broadband multimedia services over VDSL H.610H.619 Advanced multimedia services and applications H.620H.629 IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV General aspects H.700H.719 IPTV terminal devices H.720H.729 IPTV middleware H.730H

7、.739 IPTV application event handling H.740H.749 IPTV metadata H.750H.759 IPTV multimedia application frameworks H.760H.769 IPTV service discovery up to consumption H.770H.779 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T H.350.1 (05/2011) i Recommendation ITU-T H

8、.350.1 Directory services architecture for H.323 Summary Recommendation ITU-T H.350.1 describes a lightweight directory access protocol (LDAP) schema to represent ITU-T H.323 endpoints. It is an auxiliary class related to Recommendation ITU-T H.350 and derives much of its functionality from that arc

9、hitecture. Implementers should review Recommendation ITU-T H.350 in detail before proceeding with this Recommendation. Its attributes include all ITU-T H.323 alias types. These aliases can be downloaded to an endpoint for automatic configuration, accessed by a gatekeeper for call signalling and auth

10、orization, and published to white pages to create user dialling directories. The scope of this Recommendation does not include normative methods for the use of the LDAP directory itself or the data it contains. The purpose of the schema is not to represent all possible data elements in the ITU-T H.3

11、23 protocol, but rather to represent the minimal set required to accomplish the design goals enumerated in Recommendation ITU-T H.350. This revised version of Recommendation ITU-T H.350.1 introduces several enhancements and clarifications to the previous version, primarily the addition of ITU-T X.50

12、0 directories support and clarification of h323IdentitypartyNumber. This Recommendation includes an electronic attachment containing a text-only version of the schema configuration file for h323Identity. History Edition Recommendation Approval Study Group 1.0 ITU-T H.350.1 2003-08-06 16 1.0 ITU-T H.

13、350.1 attachment 2003-08-06 16 2.0 ITU-T H.350.1 2011-05-14 16 Keywords Directory services, ITU-T H.235.0, ITU-T H.320, ITU-T H.323, LDAP, SIP, ITU-T X.500. ii Rec. ITU-T H.350.1 (05/2011) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field

14、of telecommunications, information and communication technologies (ICTs). 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 to standardizing

15、 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 Recommendations is covered by

16、 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 conciseness to indicate bo

17、th 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 is achieved when

18、 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. INTELLECTUAL PROPERTY

19、 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, whether asserted b

20、y 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, implementers are cautioned that t

21、his may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2012 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. IT

22、U-T H.350.1 (05/2011) iii Table of Contents Page 1 Scope 1 1.1 Extending the schema . 1 2 References. 1 3 Definitions 2 4 Abbreviations 3 5 Conventions 3 6 Object Class definitions 3 6.1 h323Identity 3 6.2 h323IdentityGKDomain . 4 6.3 h323Identityh323-ID 4 6.4 h323IdentitydialedDigits 5 6.5 h323Iden

23、tityemail-ID . 6 6.6 h323IdentityURL-ID 6 6.7 h323IdentitytransportID . 7 6.8 h323IdentitypartyNumber 7 6.9 h323IdentitymobileUIM . 9 6.10 h323IdentityEndpointType . 9 6.11 h323IdentityServiceLevel . 10 7 h323Identity LDIF files 10 8 Using ITU-T H.350 with ITU-T X.500 directories 12 8.1 IMPORTS of I

24、TU-T X.500 ASN.1 12 8.2 h323IdentityASN1.asn . 13 Annex A Indexing profile . 16 Appendix I Electronic attachment . 17 Bibliography. 18 Electronic attachment: Schema configuration file for h323Identity Rec. ITU-T H.350.1 (05/2011) 1 Recommendation ITU-T H.350.1 Directory services architecture for H.3

25、23 1 Scope This Recommendation1describes a lightweight directory access protocol (LDAP) schema to represent ITU-T H.323 endpoints. It is an auxiliary class related to ITU-T H.350 and derives much of its functionality from that architecture. Implementers should review ITU-T H.350 in detail before pro

26、ceeding with this Recommendation. Its attributes include all ITU-T H.323 alias types. These aliases can be downloaded to an endpoint for automatic configuration, accessed by a gatekeeper for call signalling and authorization, and published to white pages to create user dialling directories. The scop

27、e of this Recommendation does not include normative methods for the use of the LDAP directory itself or the data it contains. The purpose of the schema is not to represent all possible data elements in the ITU-T H.323 protocol, but rather to represent the minimal set required to accomplish the desig

28、n goals enumerated in ITU-T H.350. 1.1 Extending the schema The h323Identity classes may be extended as necessary for specific implementations. See the base ITU-T H.350 Recommendation for a discussion on schema extension. 2 References The following ITU-T Recommendations and other references contain

29、provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the po

30、ssibility 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 published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Reco

31、mmendation. ITU-T H.225.0 Recommendation ITU-T H.225.0 (2009), Call signalling protocols and media stream packetization for packet-based multimedia communication systems. ITU-T H.323 Recommendation ITU-T H.323 (2009), Packet-based multimedia communications systems. ITU-T H.350 Recommendation ITU-T H

32、.350 (2011), Directory services architecture for multimedia conferencing. ITU-T X.500 Recommendation ITU-T X.500 (2008) | ISO/IEC 9594-1:2008, Information technology Open Systems Interconnection The Directory: Overview of concepts, models and services. ITU-T X.501 Recommendation ITU-T X.501 (2008) |

33、 ISO/IEC 9594-2:2008, Information technology Open Systems Interconnection The Directory: Models. ITU-T X.509 Recommendation ITU-T X.509 (2008) | ISO/IEC 9594-8:2008, Information technology Open Systems Interconnection The Directory: Public-key and attribute certificate frameworks. _ 1This Recommenda

34、tion includes an electronic attachment containing a text file with the schema configuration file for h323Identify. 2 Rec. ITU-T H.350.1 (05/2011) ITU-T X.511 Recommendation ITU-T X.511 (2008) | ISO/IEC 9594-3:2008, Information technology Open Systems Interconnection The Directory: Abstract service d

35、efinition. ITU-T X.518 Recommendation ITU-T X.518 (2008) | ISO/IEC 9594-4:2008, Information technology Open Systems Interconnection The Directory: Procedures for distributed operation. ITU-T X.519 Recommendation ITU-T X.519 (2008) | ISO/IEC 9594-5:2008, Information technology Open Systems Interconne

36、ction The Directory: Protocol specifications. ITU-T X.520 Recommendation ITU-T X.520 (2008) | ISO/IEC 9594-6:2008, Information technology Open Systems Interconnection The Directory: Selected attribute types. ITU-T X.525 Recommendation ITU-T X.525 (2008) | ISO/IEC 9594-9:2008, Information technology

37、Open Systems Interconnection The Directory: Replication. IETF RFC 4510 IETF RFC 4510 (2006), Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map. IETF RFC 4511 IETF RFC 4511 (2006), Lightweight Directory Access Protocol (LDAP): The Protocol. 3 Definitions This Recommendati

38、on defines the following terms: 3.1 call server: A protocol-specific signalling engine that routes video or voice calls on the network. In ITU-T H.323, this entity is a gatekeeper. In SIP, this entity is a SIP proxy server. Note that not all signalling protocols use a call server. 3.2 commObject: An

39、 LDAP object class defined in ITU-T H.350 that represents generic multimedia conferencing endpoints. 3.3 endpoint: A logical device that provides video and/or voice media encoding/decoding, and signalling functions. Examples include: 1) a group teleconferencing appliance that is located in a confere

40、nce room; 2) an IP telephone; 3) a software program that takes video and voice from a camera and microphone and encodes it and applies signalling using a host computer. Note that from the perspective of most signalling protocols, gateways and MCUs are special cases of endpoints. 3.4 enterprise direc

41、tory: A canonical collection of information about users in an organization. Typically this information is collected from a variety of organizational units to create a whole. For example, Human Resources may provide name and address, Telecommunications may provide the telephone number, Information Te

42、chnology may provide the e-mail address, etc. For the purposes of this architecture, it is assumed that an enterprise directory is accessible via LDAP. 3.5 gateway: A device that translates from one protocol to another. Often gateways translate between the IP network and the public switched voice ne

43、twork to allow integration of the two. 3.6 multipoint control unit (MCU): A device capable of mixing audio/video from multiple endpoints to create a virtual meeting space. Rec. ITU-T H.350.1 (05/2011) 3 3.7 resource: A non-human entity to which an endpoint is associated. For example, an endpoint may

44、 be associated with a conference room, classroom, office, or other physical or virtual location. 3.8 white pages: An application that allows end users to look up the address of another user. 4 Abbreviations This Recommendation uses the following abbreviations: FQDN Fully Qualified Domain Name LDAP L

45、ightweight Directory Access Protocol NOTE This is consistent with IETF RFC 4510. LDIF LDAP Data Interchange Format 5 Conventions In this Recommendation, the following conventions are used: “Shall“ indicates a mandatory requirement. “Should“ indicates a suggested but optional course of action. “May“

46、indicates an optional course of action rather than a recommendation that something takes place. References to clauses, subclauses, annexes and appendices refer to those items within this Recommendation, unless another specification is explicitly listed. 6 Object Class definitions The h323Identity ob

47、ject class represents ITU-T H.323 endpoints. It is an auxiliary class and is derived from the commObject class defined in ITU-T H.350. Note that the following seven alias types are defined in ITU-T H.323 as dialling methods. Each of these alias types are represented below with the corresponding h323

48、Identity definitions. Keep in mind that these are separate fields from other endpoint information in the enterprise directory. For example, email-ID is a separate field than a users email address as represented in the enterprise directory. For implementation purposes, an administrator may set these

49、values equal by direct entry or by referral. * h323-ID * dialedDigits * email-ID * URL-ID * transportID * partyNumber * mobileUIM 6.1 h323Identity OID: 0.0.8.350.1.1.3.2.1 objectclasses: (0.0.8.350.1.1.3.2.1 NAME h323Identity DESC ITU-T h323Identity object SUP top AUXILIARY MAY ( h323IdentityGKDomain $ h323Identityh323-ID $ h323IdentitydialedDigits $ h323Identityemail-ID $ 4 Rec. ITU-T H.350.1 (05/2011) h323IdentityURL-ID $ h323IdentitytransportID