Draft61850-7-2©1EC:2002 -21-57WG10-12(61850-7-2)R3-00/DraftFD1S The Name class is inherited by the classes LOGICAL-DEVICE,LOGICAL-NODE,DATA,and DataAttribute. EXAMPLE In an implementation the logical device,logical node,data,and data attribute have each an object name (instance name)which is a unique name among classes of the same container they belong to.In addition each of the four has an ObiectReference(path name)which is a concatenation of all obiect names from each con- tainer.The four object names (one per column)can be concatenated: logical device logical node data data attribute object name "Atlanta_HV5” “XCBR1” "Pos” “stVal" description High voltage station 5 circuit breaker 1 position status value 5.3 Overview of the other service models In addition to the models listed above,the ACSI comprise the following models that provide services operating on data,data attributes,and data sets: a)DATA-SET-permits the grouping of data and data attributes.Used for direct access and for reporting and logging. b)Substitution-supports replacement of a process value by another value. c)SETTING-GROUP-CONTROL-BLOCK-defines how to switch from one set of setting values to another one and how to edit setting groups. d) REPORT-CONTROL-BLOCK and LOG-CONTROL-BLOCK-describe the conditions for generating reports and logs based on parameters set by the client.Reports may be trig- gered by changes of process data values (e.g.,state change or deadband)or by quality changes.Logs can be queried for later retrieval.Reports may be send immediately or de- ferred.Reports provide change-of-state and sequence-of-events information exchange e) control blocks for generic substation event(GSE)-supports a fast and reliable sys- tem-wide distribution of input and output data values;peer-to-peer exchange of IED binary status information,e.g.,a trip signal. control blocks for transmission of sampled values-fast and cyclic transfer of sam- ples,e.g.,of instrument transformers. g)control-describes the services to control,e.g.,devices. h)time and time synchronisation-provides the time base for the device and system. i)file transfer-defines the exchange of large data blocks such as programs. An overview of the conceptual service model of the ACSI is shown in Figure 3. 2002-08-23:(16:30)
Draft 61850-7-2 © IEC:2002 – 21 – 57/WG10-12(61850-7-2)R3-00/DraftFDIS 2002-08-23 : (16:30) The Name class is inherited by the classes LOGICAL-DEVICE, LOGICAL-NODE, DATA, and DataAttribute. EXAMPLE In an implementation the logical device, logical node, data, and data attribute have each an object name (instance name) which is a unique name among classes of the same container they belong to. In addition each of the four has an ObjectReference (path name) which is a concatenation of all object names from each container. The four object names (one per column) can be concatenated: logical device logical node data data attribute object name “Atlanta_HV5” “XCBR1” “Pos” “stVal” description High voltage station 5 circuit breaker 1 position status value 5.3 Overview of the other service models In addition to the models listed above, the ACSI comprise the following models that provide services operating on data, data attributes, and data sets: a) DATA-SET – permits the grouping of data and data attributes. Used for direct access and for reporting and logging. b) Substitution – supports replacement of a process value by another value. c) SETTING-GROUP-CONTROL-BLOCK – defines how to switch from one set of setting values to another one and how to edit setting groups. d) REPORT-CONTROL-BLOCK and LOG-CONTROL-BLOCK – describe the conditions for generating reports and logs based on parameters set by the client. Reports may be triggered by changes of process data values (e.g., state change or deadband) or by quality changes. Logs can be queried for later retrieval. Reports may be send immediately or deferred. Reports provide change-of-state and sequence-of-events information exchange. e) control blocks for generic substation event (GSE) – supports a fast and reliable system-wide distribution of input and output data values; peer-to-peer exchange of IED binary status information, e.g., a trip signal. f) control blocks for transmission of sampled values – fast and cyclic transfer of samples, e.g., of instrument transformers. g) control – describes the services to control, e.g., devices. h) time and time synchronisation – provides the time base for the device and system. i) file transfer – defines the exchange of large data blocks such as programs. An overview of the conceptual service model of the ACSI is shown in Figure 3
Draft61850-7-2©1EC:2002 -22-57WG10-12(61850-7-2)R3-00/DraftFDIS ■■■■■■■■■■■■■■■■ 6 SERVER Control Blocks 个4 BUFFERED REPORT- 0. CTRL-BLOCK 0. 1.* 14 ⑧)LOGICAL-DEVICE UNBUFFERED- 0. CTRL-BLOCK 0. 1 14 LOG- 0. 0. CONTROL- 1. BLOCK 0.· ⑨LOGICAL-NODE LOG 1 14 1 13 SETTING- LLNO 1 0.1 CONTROL-Block i0. 1 15 GOOSE- CONTROL-BLOCK 0.° 01 GSSE. 1 0.1 CONTROL-BLOCK 1 16 MULTICAST- 0.1 AMPLED- 1 VALUE-CTRL-B. 0. 16 0. 0.1 VALUE-CTRL-B. 1.* 1 1 1 0. 1 1 1⑩ DATA DataSet ①①1 ⑩ 1 2 Substitution ⑧ DataAttribute Time 0. 1⑦ Control 2⑩ File Figure 3-Conceptual service model of the ACSI NOTE 1 The numbers in the circles point to the respective clauses in this part. NOTE 2 The class diagrams are conceptual.Details are defined in the respective clauses.Comprehensive diagrams are contained in part IEC 61850-7-1.The DATA class may be defined recursively.The operations for sub- stitution and control are restricted to the lowest level in the DATA class.The DataAttributes may be defined recur- sively as well. The logical node is one of the major building blocks that has associations to most of the other information exchange models,e.g.,report control,log control,and setting control. Any other information exchange service model,e.g.,report control,log control,and setting control shall inherit the ObjectName and ObjectReference as depicted in Figure 2. NOTE 3 The class models and services are defined using an object oriented approach allowing to map the class models and services to different application layer and middle ware solutions. 2002-08-23:(16:30)
Draft 61850-7-2 © IEC:2002 – 22 – 57/WG10-12(61850-7-2)R3-00/DraftFDIS 2002-08-23 : (16:30) 1..* DataAttribute LOGICAL-DEVICE SERVER BUFFEREDREPORT- 0..* CTRL-BLOCK LOG 0..1 LOGCONTROLBLOCK 0..* 1 0..* 0..* SETTINGGROUP- 0..1 CONTROL-Block GOOSECONTROL-BLOCK 0..1 GSSECONTROL-BLOCK 0..1 MULTICASTSAMPLEDVALUE-CTRL-B. 0..1 0..1 DataSet 1 0..* 1 0..* 1 0..* 1 0..* 1 0..* 1 0..* 1 0..* 1 1 1 1 1 1 1 1 1 1 0..* 1..* 1 1 1 1..* DATA 1 1..* 11 13 14 14 14 14 15 15 16 16 Substitution 12 Control 17 18 Time 20 File 6 8 9 10 10 LOGICAL-NODE 0..* 1 0..* LLN0 UNICASTSAMPLED VALUE-CTRL-B. UNBUFFEREDREPORTCTRL-BLOCK Control Blocks 1 Figure 3 – Conceptual service model of the ACSI NOTE 1 The numbers in the circles point to the respective clauses in this part. NOTE 2 The class diagrams are conceptual. Details are defined in the respective clauses. Comprehensive diagrams are contained in part IEC 61850-7-1. The DATA class may be defined recursively. The operations for substitution and control are restricted to the lowest level in the DATA class. The DataAttributes may be defined recursively as well. The logical node is one of the major building blocks that has associations to most of the other information exchange models, e.g., report control, log control, and setting control. Any other information exchange service model, e.g., report control, log control, and setting control shall inherit the ObjectName and ObjectReference as depicted in Figure 2. NOTE 3 The class models and services are defined using an object oriented approach allowing to map the class models and services to different application layer and middle ware solutions
Draft61850-7-2©1EC:2002 -23-57WG10-12(61850-7-2)R3-00/DraftFD1S 5.4 Overview of ACSI services The complete list of ACSI classes and their services is shown in Table 1. Table 1-ACSI classes SERVER model (clause 6) LOG-CONTROL-BLOCK model: GetServerDirectory GetLCBValues SetLCBValues ASSOCIATION model (clause 7) QueryLogByTime Associate QueryLogByEntry Abort GetLogStatusValues Release Generic substation event model -GSE(clause 15) LOGICAL-DEVICE model (clause 8) GOOSE GetLogicalDeviceDirectory SendGOOSEMessage GetReference LOGICAL-NODE model (clause 9) GetGOOSEElementNumber GetLogicalNodeDirectory GetGoCBValues GetAllDataValues SetGoCBValues GSSE DATA model (clause 10) SendGSSEMessage GetDataValues GetReference SetDataValues GetGSSEDataOffset GetDataDirectory GetGsCBValues GetDataDefinition SetGsCBValues DATA-SET model (clause 11) Transmission of sampled values model GetDataSetValues (clause 16) SetDataSetValues MULTICAST-SAMPLE-VALUE-CONTROL-BLOCK: CreateDataSet SendMSVMessage DeleteDataSet GetMSVCBValues GetDataSetDirectory SetMSVCBValues UNICAST-SAMPLE-VALUE-CONTROL-BLOCK: Substitution model (clause 12) SendUSVMessage SetDataValues GetUSVCBValues GetDataValues SetUSVCBValues SETTING-GROUP-CONTROL-BLOCK model Control model (clause 17) (clause 13) Select SelectActiveSG SelectWithValue SelectEditSG SetSGValues Cancel Operate ConfirmEditSGValues CommandTermination GetSGValues GetSGCBValues TimeActivatedOperate Time and time synchronisation (clause 18) REPORT-CONTROL-BLOCK and LCB-BLOCK TimeSynchronisation model (clause 14) BUFFERED-REPORT-CONTROL-BLOCK: FILE transfer model (clause 20) Report GetFile GetBRCBValues SetFile SetBRCBValues DeleteFile GetFileAttributeValues UNBUFFERED-REPORT-CONTROL-BLOCK: Report GetURCBValues SetURCBValues 2002-08-23:(16:30)
Draft 61850-7-2 © IEC:2002 – 23 – 57/WG10-12(61850-7-2)R3-00/DraftFDIS 2002-08-23 : (16:30) 5.4 Overview of ACSI services The complete list of ACSI classes and their services is shown in Table 1. Table 1 – ACSI classes SERVER model (clause 6) GetServerDirectory ASSOCIATION model (clause 7) Associate Abort Release LOGICAL-DEVICE model (clause 8) GetLogicalDeviceDirectory LOGICAL-NODE model (clause 9) GetLogicalNodeDirectory GetAllDataValues DATA model (clause 10) GetDataValues SetDataValues GetDataDirectory GetDataDefinition DATA-SET model (clause 11) GetDataSetValues SetDataSetValues CreateDataSet DeleteDataSet GetDataSetDirectory Substitution model (clause 12) SetDataValues GetDataValues SETTING-GROUP-CONTROL-BLOCK model (clause 13) SelectActiveSG SelectEditSG SetSGValues ConfirmEditSGValues GetSGValues GetSGCBValues REPORT-CONTROL-BLOCK and LCB-BLOCK model (clause 14) BUFFERED-REPORT-CONTROL-BLOCK: Report GetBRCBValues SetBRCBValues UNBUFFERED-REPORT-CONTROL-BLOCK: Report GetURCBValues SetURCBValues LOG-CONTROL-BLOCK model: GetLCBValues SetLCBValues QueryLogByTime QueryLogByEntry GetLogStatusValues Generic substation event model – GSE (clause 15) GOOSE SendGOOSEMessage GetReference GetGOOSEElementNumber GetGoCBValues SetGoCBValues GSSE SendGSSEMessage GetReference GetGSSEDataOffset GetGsCBValues SetGsCBValues Transmission of sampled values model (clause 16) MULTICAST-SAMPLE-VALUE-CONTROL-BLOCK: SendMSVMessage GetMSVCBValues SetMSVCBValues UNICAST-SAMPLE-VALUE-CONTROL-BLOCK: SendUSVMessage GetUSVCBValues SetUSVCBValues Control model (clause 17) Select SelectWithValue Cancel Operate CommandTermination TimeActivatedOperate Time and time synchronisation (clause 18) TimeSynchronisation FILE transfer model (clause 20) GetFile SetFile DeleteFile GetFileAttributeValues
Draft61850-7-2©1EC:2002 -24-57WG10-12(61850-7-2)R3-00/DraftFD1S 5.5 Type definitions 5.5.1 Data attribute types Parts IEC 61850-7-2 and IEC 61850-7-3 shall use the types that are defined in the following sub-clauses in order to define the specific data for the application models in part IEC 61850-7- 4 and the control blocks in this part of IEC 61850(e.g.,report control blocks). The data attribute type concept is depicted in Figure 4.The data attribute type (DAType)is a class that has a Name,an indication (Presence)if the attribute is mandatory(present)or op- tional(possibly not-present),and BasicTypes. NOTE 1 The DAType class is an abstract class that is an auxiliary means to construct the primitive and com- posite components. NOTE 2 The formal specification of the DAType class and the use of DATypes to specify the types of data attributes could be found in 10.The class diagram has been introduced in this subclause to depict the context in which the basic types are used. NOTE 3 A comprehensive example is provided in part IEC 61850-7-1. The BasicTypes (e.g.,BOOLEAN and INT8)are used to build PrimitiveComponents and CompositeComponents.PrimitiveComponents shall have a Name,a Presence,and a Ba- sicType (e.g.,Name i,Presence Mandatory,and BasicType INT32).The Composite- Component is constructed by one or more PrimitiveComponents each of BasicType(e.g., Name=vMag of type AnalogueValue comprising two PrimitiveComponents i(of INT32)and f(of FLOAT32)). Common CompositComponents and PrimitiveComponents are defined in the various common DATA classes of part IEC 61850-7-3. DAType 1.n Name CompositeComponent Presence q Quality validity CODED ENUM DetailQual PrimitiveComponent source … cVal Vector vMag AnalogueValue i INT32 vAng AnalogueValue FLOAT32 subEna BOOLEAN vMag AnalogueValue NT32 BasicType FLOAT32 BOOLEAN INT8 FLOAT32 VISIBLE-STRING Attribute Presence not shown in examples! Figure 4-Data attribute type concept 2002-08-23:(16:30)
Draft 61850-7-2 © IEC:2002 – 24 – 57/WG10-12(61850-7-2)R3-00/DraftFDIS 2002-08-23 : (16:30) 5.5 Type definitions 5.5.1 Data attribute types Parts IEC 61850-7-2 and IEC 61850-7-3 shall use the types that are defined in the following sub-clauses in order to define the specific data for the application models in part IEC 61850-7- 4 and the control blocks in this part of IEC 61850 (e.g., report control blocks). The data attribute type concept is depicted in Figure 4. The data attribute type (DAType) is a class that has a Name, an indication (Presence) if the attribute is mandatory (present) or optional (possibly not-present), and BasicTypes. NOTE 1 The DAType class is an abstract class that is an auxiliary means to construct the primitive and composite components. NOTE 2 The formal specification of the DAType class and the use of DATypes to specify the types of data attributes could be found in 10. The class diagram has been introduced in this subclause to depict the context in which the basic types are used. NOTE 3 A comprehensive example is provided in part IEC 61850-7-1. The BasicTypes (e.g., BOOLEAN and INT8) are used to build PrimitiveComponents and CompositeComponents. PrimitiveComponents shall have a Name, a Presence, and a BasicType (e.g., Name = i, Presence = Mandatory, and BasicType = INT32). The CompositeComponent is constructed by one or more PrimitiveComponents each of BasicType (e.g., Name = vMag of type AnalogueValue comprising two PrimitiveComponents i (of INT32) and f (of FLOAT32)). Common CompositComponents and PrimitiveComponents are defined in the various common DATA classes of part IEC 61850-7-3. DAType PrimitiveComponent Name CompositeComponent Presence 1..n BasicType 1 BOOLEAN INT8 FLOAT32 ... VISIBLE-STRING i INT32 f FLOAT32 subEna BOOLEAN ... q Quality validity CODED ENUM DetailQual ... source ... ... cVal Vector vMag AnalogueValue vAng AnalogueValue ... vMag AnalogueValue i INT32 f FLOAT32 ... Attribute Presence not shown in examples! Figure 4 – Data attribute type concept
Draft61850-7-2©1EC:2002 -25-57WG10-12(61850-7-2)R3-00/DraftFDIS 5.5.2 BasicTypes The BasicTypes shall be as listed in Table 2. Table 2-BasicTypes BasicTypes Name Value range Remark Used by BOOLEAN IEC61850-7-3 1EC61850-7-2 INT8 -128to127 IEC61850-7-3 IEC61850-7-2 INT16 -32,768to32,767 IEC61850-7-3 IEC61850-7-2 INT24 -8388608to8388607 for TimeStamp type IEC61850-7-2 INT32 -2,147,483,648to2,147,483,647 IEC61850-7-3 IEC61850-7-2 INT128 -2**127t0(2**127)-1 Required for counters. IEC61850-7-3 INT8U Unsigned integer, IEC61850-7-3 0to255 IEC61850-7-2 INT16U Unsigned integer, IEC61850-7-3 0t065,535 IEC61850-7-2 INT32U Unsigned integer, IEC61850-7-3 0to4,294,967,295 IEC61850-7-2 FLOAT32 Range of values and precision as IEC61850-7-3 specified by IEEE 754 single pre- cision floating point. FLOAT64 Range of values and precision as IEC61850-7-3 specified by IEEE 754 double pre- cision floating point. ENUMERATED Ordered set of values,defined Custom extensions are al- IEC61850-7-3 where type is used. lowed. IEC61850-7-2 CODED ENUM Ordered set of values,defined Custom extensions shall not IEC61850-7-3 where type is used. be allowed.Type shall be IEC61850-7-2 mapped to an efficient en- coding in a SCSM OCTET STRING Max length shall be defined 1EC61850-7-3 where type is used. IEC61850-7-2 VISIBLE STRING Max length shall be defined IEC61850-7-3 where type is used. IEC61850-7-2 2002-08-23:(16:30)
Draft 61850-7-2 © IEC:2002 – 25 – 57/WG10-12(61850-7-2)R3-00/DraftFDIS 2002-08-23 : (16:30) 5.5.2 BasicTypes The BasicTypes shall be as listed in Table 2. Table 2 – BasicTypes BasicTypes Name Value range Remark Used by BOOLEAN IEC 61850-7-3 IEC 61850-7-2 INT8 -128 to 127 IEC 61850-7-3 IEC 61850-7-2 INT16 -32,768 to 32,767 IEC 61850-7-3 IEC 61850-7-2 INT24 - 8388608 to 8388607 for TimeStamp type IEC 61850-7-2 INT32 -2,147,483,648 to 2,147,483,647 IEC 61850-7-3 IEC 61850-7-2 INT128 -2**127 to (2**127)-1 Required for counters. IEC 61850-7-3 INT8U Unsigned integer, 0 to 255 IEC 61850-7-3 IEC 61850-7-2 INT16U Unsigned integer, 0 to 65,535 IEC 61850-7-3 IEC 61850-7-2 INT32U Unsigned integer, 0 to 4,294,967,295 IEC 61850-7-3 IEC 61850-7-2 FLOAT32 Range of values and precision as specified by IEEE 754 single precision floating point. IEC 61850-7-3 FLOAT64 Range of values and precision as specified by IEEE 754 double precision floating point. IEC 61850-7-3 ENUMERATED Ordered set of values, defined where type is used. Custom extensions are allowed. IEC 61850-7-3 IEC 61850-7-2 CODED ENUM Ordered set of values, defined where type is used. Custom extensions shall not be allowed. Type shall be mapped to an efficient encoding in a SCSM IEC 61850-7-3 IEC 61850-7-2 OCTET STRING Max length shall be defined where type is used. IEC 61850-7-3 IEC 61850-7-2 VISIBLE STRING Max length shall be defined where type is used. IEC 61850-7-3 IEC 61850-7-2