1、 International Telecommunication Union ITU-T H.350.6TELECOMMUNICATION 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、 call forwarding and preferences Recommendation ITU-T H.350.6 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 Sy
3、stems aspects H.230H.239 Communication 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 ar
4、chitecture for audiovisual 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.5
5、19 Mobile multimedia collaboration 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-w
6、orking procedures H.560H.569 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.
7、729 IPTV middleware H.730H.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.6 (05/2011
8、) i Recommendation ITU-T H.350.6 Directory services architecture for call forwarding and preferences Summary Recommendation ITU-T H.350.6 describes a simple lightweight directory access protocol (LDAP) and ITU-T X.500 schemas to represent call forwarding and call preference information in an ITU-T H
9、.350 directory. It is intended to represent addresses to which calls should be forwarded in the case that an endpoint does not answer a call. It can direct calls to simple ITU-T H.320, ITU-T H.323 or session initiation protocol (SIP) addresses, or complex forwarding schemes such as time of day prefe
10、rences, web pages, electronic mail or other applications. Implementers should review Recommendation ITU-T H.350 in detail before proceeding with this Recommendation. This revised version of Recommendation ITU-T H.350.6 introduces some corrections to the previous version, primarily updater of ITU-T X
11、.500 ASN.1 contained in clause 8. This Recommendation includes an electronic attachment containing a schema configuration file for callPreferenceURI. History Edition Recommendation Approval Study Group 1.0 ITU-T H.350.6 2004-03-15 16 1.0 ITU-T H.350.6 attachment 2004-03-15 16 2.0 ITU-T H.350.6 2011-
12、05-14 16 Keywords Directory services, ITU-T H.235.0, ITU-T H.320, ITU-T H.323, ITU-T X.500, LDAP, SIP. ii Rec. ITU-T H.350.6 (05/2011) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication t
13、echnologies (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 telecommunications on a worldwide basis. The World Te
14、lecommunication 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 the procedure laid down in WTSA Resolution 1. In some
15、 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 both a telecommunication administration and a recognized
16、 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 all of these mandatory provisions are met. The words
17、“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 RIGHTS ITU draws attention to the possibility that th
18、e 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 by ITU members or others outside of the Recommendation
19、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 this may not represent the latest information and are t
20、herefore 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. ITU-T H.350.6 (05/2011) iii Table of Contents Page 1 Sco
21、pe 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 URI . 3 6.2 Label . 4 6.3 callPreferenceURIObject object class 4 6.4 callPreferenceURI attribute 4 7 callPreferenceURI LDIF files . 5 8 Using ITU-T H.350 with ITU-T
22、X.500 directories 6 8.1 IMPORTS of ITU-T X.500 ASN.1 6 8.2 ASN.1 representation . 7 Annex A Indexing profile . 9 Appendix I Electronic attachment . 10 Bibliography. 11 Electronic attachment: Schema configuration file for callPreferenceURI Rec. ITU-T H.350.6 (05/2011) 1 Recommendation ITU-T H.350.6 D
23、irectory services architecture for call forwarding and preferences 1 Scope This Recommendation1describes a simple lightweight directory access protocol (LDAP) and ITU-T X.500 schemas to represent call forwarding and call preference information in an ITU-T H.350 directory. It is intended to represent
24、 addresses to which calls should be forwarded in the case that an endpoint does not answer a call. It can direct calls to simple ITU-T H.320, ITU-T H.323 or session initiation protocol (SIP) addresses, or complex forwarding schemes such as time of day preferences, web pages, electronic mail or other
25、 applications. Implementers should review ITU-T H.350 in detail before proceeding with this Recommendation. The scope of this Recommendation does not include normative methods for the use of the LDAP directory itself or the data it contains. 1.1 Extending the schema The callPreferences classes may b
26、e extended as necessary for specific implementations. See the base ITU-T H.350 for a discussion on schema extension. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the ti
27、me 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 possibility of applying the most recent edition of the Recommendations and other references listed below. A
28、 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 Recommendation. ITU-T H.323 Recommendation ITU-T H.323 (2009), Packet-based multimedia communications systems
29、. ITU-T H.350 Recommendation ITU-T H.350 (2011), Directory services architecture for multimedia conferencing. ITU-T H.350.1 Recommendation ITU-T H.350.1 (2011), Directory services architecture for H.323. ITU-T H.350.2 Recommendation ITU-T H.350.2 (2011), Directory services architecture for H.235. IT
30、U-T H.350.3 Recommendation ITU-T H.350.3 (2011), Directory services architecture for H.320. ITU-T H.350.4 Recommendation ITU-T H.350.4 (2011), Directory services architecture for SIP. ITU-T H.350.5 Recommendation ITU-T H.350.5 (2011), Directory services architecture for non-standard protocols. _ 1Th
31、is Recommendation includes an electronic attachment containing a text file with a schema configuration for callPreferenceURI. 2 Rec. ITU-T H.350.6 (05/2011) ITU-T X.500 Recommendation ITU-T X.500 (2008) | ISO/IEC 9594-1:2008, Information technology Open Systems Interconnection The Directory: Overvie
32、w of concepts, models and services. ITU-T X.501 Recommendation ITU-T X.501 (2008) | 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
33、 The Directory: Public-key and attribute certificate frameworks. ITU-T X.511 Recommendation ITU-T X.511 (2008) | ISO/IEC 9594-3:2008, Information technology Open Systems Interconnection The Directory: Abstract service definition. ITU-T X.518 Recommendation ITU-T X.518 (2008) | ISO/IEC 9594-4:2008, I
34、nformation 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 Interconnection The Directory: Protocol specifications. ITU-T X.520 Recommendation ITU-T X.
35、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 Open Systems Interconnection The Directory: Replication. IETF RFC 3261 IETF RFC 3
36、261 (2002), SIP: Session Initiation Protocol. 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 Recommendation defines
37、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 LDAP objec
38、t 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 conference room; 2
39、) an IP telephone; 3) a software program that takes video and voice from a camera and microphone, 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. Rec. ITU-T H.350.6 (05/2011) 3 3.4
40、 enterprise directory: 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 numbe
41、r, Information Technology 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 white pages: An application that allows end users to look up the address of another user. 4 Abbreviations This Recommendation u
42、ses the following abbreviations: LDAP Lightweight Directory Access Protocol NOTE This is consistent 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
43、 optional course of action. “May“ 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 cla
44、ss definitions The callPreferenceURI is a URI consisting of two parts: a URI and a label. Because it is its own unique object class, the directory can be searched for the presence of this attribute. 6.1 URI The URI portion is merely a pointer that points to an address at which can be found the desir
45、ed call forwarding address. In the most basic case, the URI will be an LDAP URI that points to another ITU-T H.350 entry elsewhere in the same ITU-T H.350 directory. For example, if an ITU-T H.323 entry is described by an h323IdentitydialedDigits attribute, its callPreferenceURI may point to another
46、 h323IdentitydialedDigits attribute elsewhere in the same directory. In this case, the URI is an LDAP URI. It is possible to represent more complex call preference behaviour if the URI points to an object outside the ITU-T H.350 directory. For example, the URI could be a mailto: URI of the form mail
47、to:userhost.domain, which would tell a call server to interpret the desired call preference behaviour to initiate an electronic mail message. Similarly, a callPreferenceURI could be a URL pointing to a web page that contains a web form for the calling party to fill out and submit, or even a game to
48、play. A more advanced scenario may be supported if the URL target represents an XML document or call processing language script which describes conditional call preferences. Note that it is the responsibility of the implementer to ensure that the data populating the directory is able to be interpret
49、ed by the call server that will be accessing that data. 4 Rec. ITU-T H.350.6 (05/2011) 6.2 Label The label portion of callPreferenceURI contains an indication of the type of call forwarding for simple forwarding types. Types not defined here may be supported by the implementer. The form of the label is: type:argument where type is a string indicating the type of call forwarding, and argument is a string indicating the time in milliseconds after which
