ITU-T H 350-2011 Directory services architecture for multimedia conferencing (Study Group 16)《多媒体会议的目录服务体系结构(研究组16)》.pdf

《ITU-T H 350-2011 Directory services architecture for multimedia conferencing (Study Group 16)《多媒体会议的目录服务体系结构(研究组16)》.pdf》由会员分享，可在线阅读，更多相关《ITU-T H 350-2011 Directory services architecture for multimedia conferencing (Study Group 16)《多媒体会议的目录服务体系结构(研究组16)》.pdf（34页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T H.350TELECOMMUNICATION 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 m

2、ultimedia conferencing Recommendation ITU-T H.350 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 aspect

3、s 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 architecture f

4、or 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.519 Mobile mu

5、ltimedia 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-working proce

6、dures 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.729 IPTV mid

7、dleware 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 (05/2011) i Recommenda

8、tion ITU-T H.350 Directory services architecture for multimedia conferencing Summary Recommendation ITU-T H.350 describes a directory services architecture for multimedia conferencing using lightweight directory access protocol (LDAP). Standardized directory services can support the association of p

9、ersons with endpoints, searchable white pages, and clickable dialling. Directory services can also assist in the configuration of endpoints, and user authentication based on authoritative data sources. This Recommendation describes a standardized LDAP schema to represent endpoints on the network and

10、 associate those endpoints with users. It discusses design and implementation considerations for the interrelation of video and voice-specific directories, enterprise directories, call servers and endpoints. This revised version of Recommendation ITU-T H.350 introduces several enhancements and clari

11、fications to the previous version, primarily the addition of ITU-T X.500 directories support and authentication across multiple directories, and clarifications of commPrivate and commOwner. This Recommendation includes an electronic attachment containing two schema configuration files for commURIObj

12、ect and CommObject. History Edition Recommendation Approval Study Group 1.0 ITU-T H.350 2003-08-06 16 1.0 ITU-T H.350 attachment 2003-08-06 16 2.0 ITU-T H.350 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 (05/2011) FOR

13、EWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field 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 studyin

14、g technical, operating and tariff questions and issuing Recommendations on them with a view 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

15、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 areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO

16、and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness 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

17、(to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is 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 wo

18、rds does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL 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 co

19、ncerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether 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

20、 patents, which may be required to implement this Recommendation. However, implementers are cautioned that this 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

21、publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T H.350 (05/2011) iii Table of Contents Page 1 Scope 1 1.1 Design goals . 2 1.2 Extending the schema . 3 2 References. 4 3 Definitions 5 4 Abbreviations 5 5 Conventions 6 6 commURIObject def

22、inition 6 6.1 commURIObject . 6 6.2 commURI . 6 7 CommObject definition 7 7.1 commObject . 7 7.2 commUniqueId . 7 7.3 commOwner . 8 7.4 commPrivate . 8 8 CommObject LDIF files . 9 8.1 LDIF for commURIObject . 9 8.2 LDIF for commObject 10 9 Using ITU-T H.350 with ITU-T X.500 directories 12 9.1 IMPORT

23、S of ITU-T X.500 ASN.1 12 9.2 commObjectASN1.asn . 12 9.3 commURIASN1.asn . 14 Annex A Indexing profile . 16 Appendix I Implementation considerations 17 I.1 Relationship of enterprise directories to commObject directories . 17 Appendix II Call flows 21 II.1 Call flow scenarios . 21 Appendix III Elec

24、tronic attachments: schema configuration files for commURIObject and commObject . 24 Bibliography. 25 Rec. ITU-T H.350 (05/2011) 1 Recommendation ITU-T H.350 Directory services architecture for multimedia conferencing 1 Scope This Recommendation1describes a directory services architecture for multim

25、edia conferencing using lightweight directory access protocol (LDAP). Standardized directory services can support the association of persons with endpoints, searchable white pages, and clickable dialling. Directory services can also assist in the configuration of endpoints, and user authentication b

26、ased on authoritative data sources. This Recommendation describes a standardized LDAP schema to represent endpoints on the network and associate those endpoints with users. It discusses design and implementation considerations for the interrelation of video and voice-specific directories, enterprise

27、 directories, call servers and endpoints. The use of a common, authoritative data source for call server, endpoint, user, authentication and white pages information is an important aspect of large scale multimedia conferencing environments. Without a common data source, service providers must create

28、 separate processes to manage each of these functions. By standardizing the LDAP schema used to represent the underlying data, products from different system vendors can be deployed together to create an overall application environment. For example, a white pages search engine developed by one provi

29、der could serve directory information to IP telephones produced by a second provider, with signalling managed by a call server produced by yet a third provider. Each of these disparate systems can access the same underlying data source, reducing or eliminating the need to coordinate the separate man

30、agement of each system. A significant benefit to the user is that the management of this data can be incorporated into existing customer management tools, allowing for quick and flexible scaling up of applications. Indeed, many technology providers have already incorporated LDAP into their products,

31、 but have been forced to do so without the benefit of a standardized schema. This Recommendation represents an effort to standardize those representations to improve interoperability and performance. While URLs are already standardized for several conferencing protocols, their representation in a di

32、rectory is not. This Recommendation supports a standardized way for URLs to be searched and located. This is a necessary step to support clickable dialling. Management of endpoint configurations can be improved if the correct settings are stored by the service provider in a location that is accessib

33、le to both service provider and endpoint. LDAP provides a convenient storage location that can be accessed by both call server and endpoint; thus it is possible to use the directory to support the endpoint configuration, which is important for simplified operation and supporting user mobility. Note

34、that other technologies also support endpoint configuration, notably the use of SNMP for complete configuration and DNS SRV resource records for obtaining registration server addresses. Therefore, ITU-T H.350 should be viewed not as an authoritative endpoint configuration architecture, but rather on

35、e tool that can assist with this task. Note that the use of ITU-T H.350 has as a feature endpoint specific configuration, where it is desirable that each endpoint have a unique configuration. This architecture uses a generic object class, called commObject, to represent attributes common to any vide

36、o or voice protocol. Auxiliary classes represent specific protocols, such as ITU-T H.323, ITU-T H.235.x, or ITU-T H.320, as described in the ITU-T H.350.x series of Recommendations. Multiple ITU-T H.350.x classes can be combined to represent endpoints that support more than one protocol. For example

37、, endpoints that support ITU-T H.323, ITU-T H.235.x and ITU-T H.320 _ 1This Recommendation includes an electronic attachment containing schema configuration files for commURIObject and commObject. 2 Rec. ITU-T H.350 (05/2011) would include ITU-T H.350, ITU-T H.350.1, ITU-T H.350.2, and ITU-T H.350.3

38、 in their LDAP representations. Furthermore, each entry should contain commObject to serve as the entrys structural object class. There are two basic components in the architecture. The commURI object is a class whose only purpose is to link a person or resource to a commObject. By placing a commURI

39、 pointer in an individuals directory entry, that individual becomes associated with the particular targeted commObject. Similarly, each commObject contains a pointer, called commOwner, which points to the individual or resource that is associated with the commObject. In this way, people or resources

40、 can be associated with endpoints. The only change required to the enterprise directory is the addition of the simple object class commURI. CommObject data may be instantiated in the same or an entirely separate directory, thus allowing flexibility in implementation. 1.1 Design goals Large-scale dep

41、loyments of IP video and voice services have demonstrated the need for complementary directory services middleware. Service administrators need call servers that are aware of enterprise directories to avoid duplication of account management processes. Users need white pages to locate other users wit

42、h whom they wish to communicate. All of these processes should pull their information from canonical data sources in order to reduce redundant administrative processes and ensure information accuracy. The following design criteria are established for this architecture. The architecture will: 1) enab

43、le endpoint information to be associated with people. Alternatively, it enables endpoint information to be associated with resources such as conference rooms or classrooms; 2) enable online searchable “white pages“ where dialling information (e.g., endpoint addresses) can be found, along with other

44、“traditional“ directory information about a user, such as name, address, telephone, e-mail, etc.; 3) enable all endpoint information to be stored in a canonical data source (the Directory), rather than local to the call server, so that endpoints can be managed through manipulations of an enterprise

45、directory, rather than by direct entry into the call server; 4) support the creation of very large scale distributed directories. These include white pages “portals“ that allow searching for users across multiple institutional directories. In this application, each enterprise directory registers its

46、elf with (or is unknowingly discovered by) a directory of directories that is capable of searching across multiple LDAP directories; 5) be able to support multiple instances of endpoints per user or resource; 6) represent endpoints that support more than one protocol, for example, endpoints that are

47、 both ITU-T H.320 and ITU-T H.323; 7) store enough information about endpoint configuration so that correct configuration settings can be documented to end users on a per-endpoint basis, as a support tool, or loaded automatically into the endpoint; 8) be extendable as necessary to allow implementati

48、on-specific attributes to be included; 9) be non-invasive to the enterprise directory, so that support for multimedia conferencing can be added in a modular fashion without significant changes to the enterprise directory. The scope of this Recommendation does not include extensions of functionality

49、to protocols as defined within the protocols themselves. It is not the intent of this Recommendation to add features, but merely to represent existing protocol attributes. The exception to this case is when functionality is implied by the directory itself, such as the commPrivate attribute. Rec. ITU-T H.350 (05/2011) 3 1.2 Extending the schema ITU-T H.350 object classes may be extended as necessary for specific implementations. For example, a class may be extended to support billing reference codes. Extensions to th