Remerciez-le!

Remerciez @Admin pour avoir partagé cet document gratuitement, de la manière la plus simple, en partageant sur les réseaux sociaux.

ICCP User Guide TR- Final Draft, October 8, 1996 Prepared by KEMA-ECC 7575 Gold

ICCP User Guide TR- Final Draft, October 8, 1996 Prepared by KEMA-ECC 7575 Golden Valley Road, Suite 300 Minneapolis, MN 55427 Principal Investigators T. Saxton D. Ambrose F. Kendall Prepared for Electric Power Research Institute 3412 Hillview Avenue Palo Alto, CA 94304 EPRI Project Manager D. Becker 2 ABSTRACT This Inter-Control Center Communications Protocol (ICCP) User Guide provides important information to ICCP users, both end users and developers. The background and reasoning behind the ICCP protocol (also known as the Telecontrol Application Service Element (TASE.2) are presented. The concepts of ICCP clients and servers, ICCP server and data objects, and other concepts fundamental to understanding ICCP are provided in a tutorial fashion. Help is provided in the use of the ICCP specifications, including many cross references from the guide to the specifications. Many issues facing developers and users of ICCP are also addressed, including most of the areas referred to as “local implementation issues” in the ICCP specifications. This guide is a supplement to rather than a replacement of the ICCP specifications. Table of Contents Usguid5.doc October 8, 1996 Exhibits 6.1.1-1, ICCP Protocol Architecture.....................................................................7 6.1.2-1, Application Program Interface.................................................................8 6.1.4-1, ICCP Client/Server Model with Multiple Associations............................10 6.1.6-1, ICCP Object Models..............................................................................11 8.8.1.3-1, Transfer Account Data Object Model Structure..................................34 8.8.1.3-2, Example of Transfer Account Data Object Use..................................35 Appendix A Answers to Frequently Asked Questions about ICCP Usguid5.doc October 8, 1996 Introduction to User Guide 1.Purpose This User Guide is to provide guidance to users of the Inter-Control Center Communications Protocol (ICCP), otherwise known by its official name of Telecontrol Application Service Element.2 (TASE.2). Throughout this document, the name ICCP will normally be used, except where specific references are made to the IEC standards. In any case, it should be clear that there is only one protocol and set of specifications that may referred to as either ICCP or TASE.2 Although a Draft International Standard (DIS) for ICCP currently exists at the time of this writing, it is by necessity written in the style dictated by the International Electrotechnical Commission (IEC), the standards organization sponsoring the DIS. This style has been developed to specify international standards in a precise and unambiguous way so that all implementers will interpret the standard in the same way and thus ensure interoperability between different vendor’s ICCP products. However, the style of the ICCP DIS is not necessarily as readable for someone not intimately familiar with all the background leading up to the development of ICCP. Furthermore, certain types of information very useful to a user of ICCP but not necessary for specifying the protocol or services provided by ICCP have been omitted. Thus the need for this User Guide. Intended Audience The User Guide is intended for a broad audience of readers from an end user trying to decide if ICCP is appropriate for their data transfer needs to a vendor planning to implement ICCP, with the goal of offering an ICCP product. In particular, this guide should be helpful to the following: 1 An end user, such as an electric utility, with the need to transfer real-time data to another utility or utilities or to another internal control center, who is trying to evaluate which protocol is most appropriate. 2 An end user who already has decided to use ICCP and now needs guidance in how to procure ICCP. 3 An end user who has procured ICCP and now is concerned about exactly how to map their actual data into ICCP data objects. 4 An end user who is looking for conventions and answers to practical questions regarding configuring ICCP software and networks. 5 A vendor with a project to implement the ICCP specification either as a project special or to offer a standard product. 6 Organization of Guide This guide first introduces the background and concepts of ICCP to provide a framework for understanding the ICCP specification. Then the individual server and data objects comprising ICCP are described with cross references into the specification. At this point (i.e., Sections 1-8) the reader should have all the necessary foundation understanding to intelligently use the ICCP specifications. The remainder of the guide (Sections 9-20) address practical issues that arise in connection with the use of ICCP. Appendix A is a collection of Frequently Asked Questions (FAQs) of interest primarily to developers of ICCP products which were originally collected into a preliminary Implementor’s Guide. Usguid5.doc October 8, 1996 ICCP Version Number This version of the ICCP User guide applies to ICCP specifications IEC 870-6-503 and 870-6-802 Version 1996-08. This version of the ICCP specifications is also informally known as ICCP Version 6.1. See the References section 4 for more complete identification of the specifications to which this guide applies. Definitions For the purposes of this User’s Guide, the following definitions apply. These definitions are also found in 870-6-503. Action: An activity performed by the ICCP server under some defined circumstances. Accounting Information: A set of information which describes an account for a utility. See IEC 870- 6-802 for more details. Bilateral Agreement: An agreement between two control centers which identifies the data elements and objects that can be accessed and the level of access permitted. Bilateral Table: The computer representation of the Bilateral Agreement. The representation used is a local matter. Client: An ICCP user which request services or objects owned by another ICCP user acting as a server. The client is a communicating entity which makes use of the VCC for the lifetime of an association via one or more ICCP service requests. Data Set: An object which provides services to group data values for singular operations by an ICCP client. Data Value: An object which represents some alphanumeric quantity that is part of the Virtual Control Center (VCC) which is visible to an ICCP user. Data Values exist as part of the implementation of the control center and represent either real entities within the utility such as current, or derived values calculated in the control center. Data Value objects include services for accessing and managing them. Instance: An implementation of ICCP executed in either the client or the server role. Interchange Schedule: A set of information that specifies how energy is transferred from one system to another. See IEC 870-6-802 for more details. Object: An abstract entity used to implement the ICCP protocol and represent data and optionally provide services for accessing that data within a VCC. Object Model: An abstract representation that is used for real data, devices, operator stations, programs, event conditions, and event enrollments. Operation: An activity which is performed by the ICCP server at the request of the ICCP client. Server: An ICCP user that is the source of data and provides services for accessing that data. An ICCP server behaves as a VCC over the lifetime of an association. Service: An activity which is either an ICCP action or operation. Tagged: The term tagged is derived from the practice of putting a physical tag on a device as it is turned off for servicing or locked out from network access as a safety measure. The ICCP term tagged is used to signal such a condition to the ICCP user. Usguid5.doc October 8, 1996 Time Series: A set of values of a given element that is taken at different times as specified by a single time interval. A time series is implemented through the transfer set mechanism as defined within this specification. Transfer Account: A set of information that associates interchange scheduling information with either hourly or profile data. Transfer Conditions: The events or circumstances under which an ICCP server reports the values of a data set, values in a time series, or all transfer account information. Transfer Set: An object used to control data exchange by associating data values with transmission parameters such as time intervals, for example. There are four types of Transfer Sets: Data Set Transfer Sets, Time Series Transfer Sets, Transfer Account Transfer Sets, and information Message Transfer Sets. User: An implementation of ICCP executed in either the client or the server role. Virtual Control Center (VCC): An abstract representation of a real control center which describes a set of behavior with regards to communication and data management functionality and limitations. VCC is a concept taken from the underlying MMS services. Usguid5.doc October 8, 1996 2.Abbreviations ACSE Association Control Service Element API Application Program Interface BCD Binary Coded Decimal COV Change Of Value DIS Draft International Standard EPRI Electric Power Research Institute HLO Hot line order ICC Inter-Control Center IDEC Inter-utility Data Exchange Consortium IEC International Electrotechnical Commission IP Internet Protocol KQH Kilovar hour readings KWH Kilowatt hour readings LFC Load Following MMS Manufacturing Messaging Specification MOD Motor operated disconnect PDU Protocol Data Unit QOS: Quality of Service RBE Report by Exception ROSE Remote Operations Service Element TAL Time Allowed to Live TASE Tele-control Application Service Element, IEC’s designation of an international standard protocol for utility data exchange. TASE.1 TASE based on the ELCOM-90 protocol. TASE.2 TASE based on the ICCP protocol. TCP Transmission Control Protocol TLE Time Limit uploads/Ingenierie_Lourd/ iccp-guide.pdf