《CEA-860-A-2002.pdf》由会员分享，可在线阅读，更多相关《CEA-860-A-2002.pdf（104页珍藏版）》请在三一文库上搜索。
1、 CEA STANDARD Device Plug-in Interface to EIA/CEA-709.1 Network Tools CEA-860-A December 2002 CONSUMER ELECTRONICS ASSOCIATION CEA-860-A Copyright Consumer Electronics Association Provided by IHS under license with CEA Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/30/2007 2
2、0:32:03 MDTNo reproduction or networking permitted without license from IHS -,-,- NOTICE CEA Standards, Bulletins and other technical publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and
3、 improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his particular need. Existence of such Standards, Bulletins and other technical publications shall not in any respect preclude any member or nonmember of CEA from manufacturing
4、or selling products not conforming to such Standards, Bulletins or other technical publications, nor shall the existence of such Standards, Bulletins and other technical publications preclude their voluntary use by those other than CEA members, whether the standard is to be used either domestically
5、or internationally. Standards, Bulletins and other technical publications are adopted by CEA in accordance with the American National Standards Institute (ANSI) patent policy. By such action, CEA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties
6、 adopting the Standard, Bulletin or other technical publication. This CEA Standard is considered to have International Standardization implication, but the International Electrotechnical Commission activity has not progressed to the point where a valid comparison between the CEA Standard and the IEC
7、 document can be made. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of reg
8、ulatory limitations before its use. (From Project Number 2010, formulated under the cognizance of the CEA R7.1 Plug Ins.) Published by CONSUMER ELECTRONICS ASSOCIATION 2002 Technology Phone 800-854-7179; Fax 303-397-2740; Internet: http:/; Email: COM Standard: The Component Object Model (COM) Speci
9、fication, Draft Version 0.9, October 24, 1995, Microsoft Corporation and Digital Equipment Corporation, Copyright 1992-95 Microsoft Corporation, One Microsoft Way, Redmond, WA, 98052-6399; Internet: http:/ IEC Standards: Global Engineering Documents, World Headquarters, 15 Inverness Way East, Englew
10、ood, CO USA 80112-5776; Phone 800-854-7179; Fax 303-397-2740; Internet: http:/; Email: IEC Central Office, 3, rue de Varembe, PO Box 131, CH-1211 Geneva 20, Switzerland; Phone +41 22 919 02 11; Fax +41 22 919 03 00; Internet http:/www.iec.ch; Email pubinforiec.ch LonMark Interoperability Associatio
11、n: LonMark Interoperability Association, 550 Meridian Ave, San Jose, CA 95126-3422; Phone: +1-408- 938-5266; Fax: +1-408-790-3838; Internet: http:/www.lonmark.org; E-mail: infolonmark.org Copyright Consumer Electronics Association Provided by IHS under license with CEA Licensee=IHS Employees/1111111
12、001, User=Wing, Bernie Not for Resale, 03/30/2007 20:32:03 MDTNo reproduction or networking permitted without license from IHS -,-,- CEA-860-A 2 Echelon Corporation: Echelon Corporation, 550 Meridian Ave, San Jose, CA 95126-3422; Phone: +1-408-938-5200; Fax: +1-408-790-3800; Internet: http:/; E-mail
13、: MSDN, MSDN Online: Microsoft Corporation, One Microsoft Way, Redmond, WA, 98052-6399; Internet: http:/ E-mail: 3 Document Overview This document contains both normative and informative information compiled during the development of a specification for device plug-in interfaces to ANSI/EIA-709.1-
14、B-2002 network tools. The majority of this document consists of the technical definitions of the software interfaces required to allow third party network tools and device plug-ins to interoperate on a users computer. In addition to the technical definitions, this document also contains background m
15、aterial for the rationale of the specified interfaces including usage scenarios. The interface design architecture and the requirements it was derived from are also included. This background and other informative material can be found in this documents annexes. The following sections describe the ma
16、jor areas of this document and their purpose and contents. 3.1 Section 4: Definitions and Symbols This section identifies terminology and acronyms that are used throughout the document. Terms are defined either in their general context or in their context specific to this specification. 3.2 Section
17、5: Overview of Device Plug-in Interface Components This section describes the software architecture encompassed by the interfaces specified in this document. A system architecture diagram shows the visual relationship of the software and hardware components affected by this specification. Many of th
18、e systems components are also described. 3.3 Section 6: Device Plug-in Creation Process This section describes the software method that a tool will use to create device plug-in objects at runtime. The different types of plug-ins that can be found and invoked are described and the interface specifica
19、tion for this method is defined. 3.4 Section 7: Device Plug-in Naming Conventions This section describes the areas in which naming conventions must be adhered to when implementing the interfaces in this specification. The naming conventions and their use is defined in this section. 3.5 Section 8: De
20、vice Plug-in Control Interface This section contains the definition of the software interfaces required to allow the network tool to determine the feature set of the plug-in from the device plug-in software component. It begins with a discussion of the role of the interface set and provides a quick
21、reference to the high level details of the interfaces. It follows with a detailed definition of the interfaces properties and methods including syntax and examples of their implementation. The last area of this section describes the Interface Definition Language (IDL) file provided with this standar
22、d for the set of interfaces comprising the Control Interface. 3.6 Section 9: Device Plug-in Services Interface This section contains the definition of the software interfaces required to allow a device plug-in software component to use the ANSI/EIA-709.1 network services of the network tool. It begi
23、ns with a discussion of the role of the interface set and provides a quick reference to the high level details of the interfaces. It Copyright Consumer Electronics Association Provided by IHS under license with CEA Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/30/2007 20:32
24、:03 MDTNo reproduction or networking permitted without license from IHS -,-,- CEA-860-A 3 follows with a detailed definition of the interfaces properties and methods including syntax and examples of their implementation. The last area of this section describes the Interface Definition Language (IDL)
25、 file provided with this standard for the set of interfaces comprising the Services Interface. 3.7 Section 10: Installation Specification This section describes the way a device plug-in must be installed to ensure interoperability with the network tool while the tool is running. Naming conventions a
26、nd software registration specifications are identified. 3.8 Section 11: Error Codes This section serves as a reference for the developer of device plug-ins and network tools when handling errors during integration at runtime. 3.9 Support Documentation This document also provides a bibliography and s
27、ome informative material intended to assist users of this specification with background and supportive documentation. Section 12: Annexes provides a list of the annexes found at the end of the document. Section 13 contains this documents Bibliography. The annex sections follow the bibliography and a
28、re summarized in this section. 3.9.1 Annex A: Objectives and Benefits This section contains a description of the background rationale for developing a specification for interfaces between network tools and device plug-ins. It contains an overview of the objectives and a statement of purpose for the
29、effort. It also comments on software architectures, interfaces, and upgrades. Finally, it lists the specific objectives this specification addresses for tools and device plug-ins in the field. 3.9.2 Annex B: Usage Scenarios This section provides background information describing the target users of
30、this specification. The target users are described in the context of usage scenarios for this specification. It breaks down the users into their roles as plug-in developers and network tool developers and describes their perspectives and objectives satisfied by implementing to this specification. 3.
31、9.3 Annex C: Support Files This section provides a table describing the files accompanying this specification. This section is a normative reference and several of the files described and included with this standard are substantive in support of the content of this document. The table names and desc
32、ribes each of the files including their context in support of this specification. 4 Definitions and Symbols 4.1 Use of Terms The following section introduces the basic terminology employed throughout this document. Most of it is commonly used and the terms have the same meaning in both the general a
33、nd the EIA-709 Device Plug- in context. For terms that have subtle differences, those differences are noted. 4.2 Definitions ActiveX Object: Software packages using the OLE Automation and COM technology to expose their features and functions to other software packages known as ActiveX clients. In th
34、e context of this standard, the device plug-ins are ActiveX objects and the tools that run them and access their properties Copyright Consumer Electronics Association Provided by IHS under license with CEA Licensee=IHS Employees/1111111001, User=Wing, Bernie Not for Resale, 03/30/2007 20:32:03 MDTNo
35、 reproduction or networking permitted without license from IHS -,-,- CEA-860-A 4 and methods are the objects clients. ActiveX objects are often called Servers, COM Servers, or ActiveX Servers. ActiveX Client: Software package that invokes and accesses the features and functions of other software pac
36、kages, specifically ActiveX Objects, using OLE Automation and COM technology. The client is the package that creates the ActiveX object from a component library. In the context of this standard, network tools are the ActiveX Clients to the device plug-in ActiveX objects. COM Program ID, COMProgID: T
37、he user-friendly string ID registered in the Windows registry with the Globally Unique Identifier (GUID) of an ActiveX object. The ID contains the name of the software program that the object is contained in, the name of the class component from which the object is created, and the version number of
38、 the component. The IDs are listed in the registry as “HKEY_CLASSES_ROOT/CLSID” entries and each ActiveX Objects GUID is paired with an associated COM Program ID. COMProgID is the abbreviation used in this standard and its interfaces as an abbreviation for COM Program ID. Compare: An optional featur
39、e that a device plug-in may support that will allow the tool to force the plug-in instance to compare its properties with another provided device or plug-in instance of the same type. This feature causes the plug-in to run a comparison of the contents of one device with another. Either of the device
40、 plug-in instances may contain persisted or live device properties. The implementation of the Compare feature would be contained solely in the plug-in and the call would come from the tool or the plug-in user. The plug-in may reflect the results of the compare in its user interface components. This
41、feature would be used, for example, by a user wishing to determine the difference between a persisted and a live device. Configuration: The non-volatile information used by the devices to customize their operation. There is configuration data for the correct operation of the protocol in each device,
42、 and optionally, for application operation. This document refers only to the application configuration information that is application specific. Control Interface: The set of COM Interfaces shared by the tool and the device plug-in that allow the tool to identify the plug-in by descriptive informati
43、on, as well as the features the plug-in supports. The implementation of the Control Interface methods and properties exist in the plug-in and the tool will make the calls to the plug-in to expose the details of the plug-in to the user. The control interface allows the user to control the plug-in thr
44、ough the network tool. Download: The act of sending configuration data to a device that may cause the device to change its operation, settings, or operation limits. Download is a feature supported by the device plug-in Control Interface that allows the tool to force the plug-in to prepare and send i
45、ts current data down to the device. The device plug-in Services Interface contains the call the plug-in uses to make the actual device download command through the tool. The plug-in contains the data and can initiate its own download through the Services Interface, as well. Extensibility: The charac
46、ter of a set of COM interfaces which allow them to be broadened in the future to enhance the softwares capabilities without causing the previous components to become inoperable. Extensible interface definitions imply that base properties and methods required to run a feature set already exist and th
47、at new functions and properties will merely enhance the base behavior. Factoring: The design goal of identifying and defining a set of software interfaces that implies a focused responsibility for those interfaces. Factoring interfaces involves removing the interfaces to their own component allowing
48、 them to become more easily reusable as a collection. Unrelated interfaces are removed from the set so the set of interfaces can retain uniqueness and focused scope. Factory Method: In general, an interface which has the responsibility of creating an object, but which allows other classes to determine which object to instantiate. In the context of this standard, the factory method of the device plug-in interface is called by the network tool with a COM Program ID of a device plug-in object the too