| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 42151.72-2024 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Communication networks and systems for power utility automation - Part 7-2: Basic information and communication structure - Abstract communication service interface(ACSI)
| Valid |
GB/T 42151.72-2024
|
PDF similar to GB/T 42151.72-2024
Basic data | Standard ID | GB/T 42151.72-2024 (GB/T42151.72-2024) | | Description (Translated English) | Communication networks and systems for power utility automation - Part 7-2: Basic information and communication structure - Abstract communication service interface(ACSI) | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | F21 | | Classification of International Standard | 29.240.10 | | Word Count Estimation | 210,234 | | Date of Issue | 2024-12-31 | | Date of Implementation | 2025-07-01 | | Issuing agency(ies) | State Administration for Market Regulation, China National Standardization Administration | GB/T 42151.72-2024: Communication networks and systems for power utility automation - Part 7-2: Basic information and communication structure - Abstract communication service interface(ACSI)
---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
ICS 29.240.10
CCSF21
National Standard of the People's Republic of China
Power automation communication network and system
Part 7-2.Basic information and communication structure abstraction
Communications Services Interface (ACSI)
(IEC 61850-7-2.2020, IDT)
Released on 2024-12-31
2025-07-01 Implementation
State Administration for Market Regulation
The National Standardization Administration issued
Table of Contents
Preface IX
Introduction Ⅹ
1 Scope 1
1.1 General 1
1.2 Namespaces and Versions 1
1.3 Code Component Distribution 1
2 Normative references 2
3 Terms and definitions 3
4 Abbreviations 4
5 ACSI Overview and Basic Concepts 5
5.1 IEC 61850 conceptual model 5
5.2 Meta-Metamodel 6
5.3 Metamodel 6
5.4 Domain Type Model 11
5.5 Data Instance Model 11
5.6 Conditions for the existence of elements 12
5.7 Functional Constraints (FcKind) 15
5.8 Trigger Option 18
6 Type Definition 19
6.1 Overview 19
6.2 Data Model Type 21
6.3 ACSI---Service Parameter Type 39
7 GenServerClass (Generic Server Class) Model 41
7.1 GenServerClass Definition 41
7.2 Server Class Services 42
8 Application Association Model 43
8.1 Introduction 43
8.2 The concept of application association 43
8.3 TWO-PARTY-APPLICATION-ASSOCIATION (TPAA) Class Model 44
8.4 MULTICAST-APPLICATION-ASSOCIATION (MCAA) Class 47
10.1 Definition of GenLogicalNodeClass 49
10.2 GenLogicalNodeClass Service 51
11 Generic Data Object Class Model 53
11.1 GenDataObjectClass Figure 53
11.2 GenDataObjectClass Syntax 54
11.3 GenDataObjectClass Service 55
12 Common Data Class Model 58
12.1 Overview 58
12.2 GenCommonDataClass 58
12.6 Referencing Data Objects and Their Components 63
13 DATA-SET Class Model 65
13.1 Overview 65
13.2 DATA-SET Class Definition 66
13.3 DATA-SET Class Services 67
14 Service Tracking 70
14.1 Overview 70
14.2 Control Block Service Tracking 71
14.3 Controlling Service Tracking 72
15 Control Block Class Modeling 72
15.1 Overview 72
15.2 Control Block Class Model 72
16 SETTING-GROUP-CONTROL-BLOCK Class Model 73
16.1 Overview 73
16.2 SGCB Class Definition 74
16.3 SGCB services 75
17 REPORT-CONTROL-BLOCK (report control block) and LOG-CONTROL-BLOCK (log control block)
Class Model 79
17.1 Overview 79
17.2 REPORT-CONTROL-BLOCK Class Model 81
17.3 LOG-CONTROL-BLOCK Class Model 101
18 Generic Substation Event (GSE) Class Model 109
18.1 Overview 109
18.2 GOOSE-CONTROL-BLOCK (GoCB) Class 110
19 Sampled value transmission model 116
19.1 General 116
19.2 Transmission of Sampled Values Using Multicast 117
19.3 Using Unicast Sample Value Transmission 122
19.4 Sample value format 126
20 CONTROL (control) class model 127
20.1 Introduction 127
20.2 General security controls 130
20.3 Enhanced Security Control 134
20.4 Time Activation Operation 138
20.5 CONTROL Class Service Definition 139
21 Time and Time Synchronization Models 146
21.1 General 146
21.2 Information requirements 147
22 Naming Rules 148
22.1 Class Naming and Class Exceptions 148
22.2 Referencing Class Instances 148
22.3 Scope 150
23 File Transfer Model 150
23.1 File Class 150
23.2 File Services 151
Appendix A (Normative) ACSI Conformity Statement 153
A.1 Introduction 153
A.2 ASCI basic conformity statement 153
A.3 ACSI Model Conformance Statement 154
A.4 ACSI Service Conformance Statements 155
Appendix B (Normative) SCL Enumeration 160
Appendix C (Informative) General Substation Status Event (GSSE) Control Block (GsCB) 161
C.1 Overview 161
C.2 GsCB Class Definition 161
C.3 General Substation Status Event (GSSE) Control Block Class Attributes 162
C.4 GSSE service definition 163
Appendix D (Normative) Quality Instructions 169
D.1 Refine the relationship between quality labeling and invalid or questionable quality 169
D.2 Quality in a Client/Server Context 169
D.3 Relationships between quality identifiers 170
Appendix E (Normative) Notes on RCB Reservation 172
E.1 Introduction 172
E.2 Cache Report Control Block 172
E.3 Non-cached report control block 180
Appendix F (Normative) Compatibility between different versions of IEC 61850-7-2 188
F.1 Overview 188
F.2 List of modifications made for backward/forward compatibility 188
F.3 Special compatibility rules 193
References 195
Figure 1 Summary of the IEC 61850 conceptual model 6
Figure 2 ACSI basic conceptual class model 7
Figure 3 ACSI conceptual service model 8
Figure 4 Core and relationships of the conceptual metamodel11
Figure 5 Data instance model (conceptual) 12
Figure 6 P_Timestamp 24
Figure 7 Time Accuracy 25
Figure 8 Overview of GetDirectory and GetDefinition services 42
Figure 9 Normal operation 44
Figure 10 Abnormal termination 44
Figure 11 Principles of multicast application association 47
Figure 12 Basic concept model of GenLogicalNodeClass 50
Figure 13 GenDataObjectClass basic concept class model 53
Figure 14 GenDataObjectClass service excerpt 55
Figure 15 GenCommonDataClass class diagram 58
Figure 16 GenCommonDataClass conceptual class diagram 59
Figure 18 Relationship between TrgOp and report 61
Figure 20 Type of relationship (example) 64
Figure 21 Data object example 65
Figure 22 Dynamically create a data set instance 66
Figure 23 Control block service mapping 71
Figure 24 Basic model of fixed value model 73
Figure 25 Basic components of reports and logs 80
Figure 26 BRCB state machine 83
Figure 27 General queue 84 reporting processor entries
Figure 28 Cache time 85
Figure 29 State machine for sequence number generation 86
Figure 30 General call logic state machine 87
Figure 31 Report example. Use of sequence numbers 92
Figure 32.Discarding an entry in the enabled state does not cause a loss of information indication 93
Figure 33 Indication of missing information due to resource constraints in the enabled state 93
Figure 34 Dataset members and reports 94
Figure 35 Report Example 95
Figure 36 Log model overview 102
Figure 37 GoCB model 110
Figure 38 Sample value transmission model 117
Figure 39 Control model principle 128
Figure 40 State machine of conventional safety direct control 131
Figure 41 Direct control of conventional safety 132
Figure 42 State machine of conventional safe SBO control 133
Figure 43 State machine for enhanced safety direct control 135
Figure 44 State machine of SBO control for enhanced security 136
Figure 45 Enhanced safety operation pre-selection control---affirmative situation 137
Figure 46 Enhanced safety operation pre-selection control --- negation situation (no state change) 137
Figure 47 Time activation operation 139
Figure 48 Time model and time synchronization (principle) 147
Figure 49 Special case 148
Figure 50 Object name and object reference 149
Figure C.1 GsCB model 161
Figure D.1 Quality indicators in a single client-server relationship 169
Figure D.2 Quality indicators in multiple client-server relationships 170
Figure D.3 Interaction using substitution and validity in the proxy model (CL = client, Se = server) 171
Figure E.1 BRCB instantiation from SCL and reservation scheme 172
Figure E.2 BRCB reservation scheme 174
Figure E.3 BRCB cancellation reservation scheme 176
Figure E.4 BRCB reservation and context termination 178
Figure E.5 URCB instantiation from SCL and retention scheme 180
Figure E.6 URCB Retention Scheme 182
Figure E.7 URCB cancellation reservation scheme 184
Figure E.8 URCB reservation and association termination 186
Table 1 Class instantiation example 7
Table 2 ACSI model classes and related services 9
Table 3 Conditions for the existence of elements in the context 12
Table 4 Functional constraints (FcKind) 15
Table 5 Trigger options 19
Table 6 Type definition overview 19
Table 7 Using IEC 61850-6b Type 20
Table 8 P_Timestamp attributes 25
Table 9 TimeQuality attributes 26
Table 10 Attributes of P_Quality 27
Table 11 DetailQual attributes 28
Table 12 P_TriggerConditions attributes 30
Table 13 P_RCBReportOptions attributes 30
Table 14 P_LCBLogEntryOptions Attribute 31
Table 15 P_SVMessageOptions Attribute 31
Table 16 P_CheckConditions Attributes 32
Table 17 S_Originator attributes 32
Table 18 ServiceNameKind enumeration item 32
Table 19 ServiceStatusKind enumeration item 34
Table 22 SamplingModeKind enumeration item 37
Table 23 Enumeration item 38 of StepControlKind
Table 24 DpStatusKind enumeration item 38
Table 25 SourceKind enumeration item 38
Table 26 ValidityKind enumeration item 39
Table 29 ACSIClassKind enumeration item 41
Table 30 GenServerClass definition 41
Table 31 GetServerDirectory service parameters 43
Table 32 Bilateral Application Association (TPAA) Class Definition 44
Table 33 Two-party-application-association service 45
Table 34 Associate service parameters 45
Table 35 Termination Service Parameters 46
Table 36 Release service parameters 47
Table 37 MULTICAST-APPLICATION-ASSOCIATION (MCAA) class definition 48
Table 38 GenLD class definition 48
Table 39 Get logical device directory service parameters 49
Table 40 GenLogicalNodeClass definition 50
Table 41 GenLogicalNodeClass Service 51
Table 43 GetAlDataValues service parameters 52
Table 44 GenDataObjectClass definition 54
Table 45 GenDataObjectClass service 55
Table 46 GetDataValues service parameters 56
Table 47 SetDataValues service parameters 56
Table 48 GetDataDirectory service parameters 57
Table 49 GetDataDefinition service parameters 57
Table 50 GenCommonDataClass definition 59
Table 54 DATA-SET (DS) Class Definition 66
Table 55 DATA-SET service 68
Table 56 Parameters of the GetDataSetValues service 68
Table 57 Parameters of SetDataSetValues service 69
Table 58 Parameters of the CreateDataSet service 69
Table 59 Parameters of the DeleteDataSet service 70
Table 60 Parameters of the GetDataSetDirectory service 70
Table 61 CB Class Definition 72
Table 62 SGCB Class Definition 74
Table 63 SGCB Services 75
Table 64 SelectActiveSG service parameters 76
Table 65 SelectEditSG service parameters 76
Table 66 SetEditSGValue service parameters 77
Table 67 ConfirmEditSGValues service parameters 78
Table 68 GetEditSGValue service parameters 78
Table 69 GetSGCBValues service parameters 79
Table 70 BRCB Class Definition 81
Table 71 BRCB Service 90
Table 72 Report service parameters 90
Table 73 ReportFormat Specification 91
Table 74 GetBRCBValues service parameters 97
Table 75 SetBRCBValues service parameters 98
Table 76 Unbuffered Report Control Block (URCB) Class Definition 99
Table 77 URCB Service 101
Table 78 LCB Class Definition 103
Table 79 LCB Services 104
Table 80 GetLCBValues service parameters 104
Table 81 SetLCBValues service parameters 105
Table 82 LOG class definition 105
Table 83 LOG service 107
Table 84 QueryLogByTime service parameters 107
Table 85 QueryLogAfter service parameters 108
Table 86 GetLogStatusValues service parameters 109
Table 87 GOOSE control block class definition 110
Table 88 GoCB Service 112
Table 89 SendGOOSEMessage service parameters 113
Table 90 GetGoReference service parameters 113
Table 92 GetGoCBValues service parameters 114
Table 93 SetGoCBValues service parameters 115
Table 94 GOOSE message definition 115
Table 95 MSVCB class definition 118
Table 96 MSVCB Service 119
Table 97 SendMSVMessage service parameters 120
Table 98 GetMSVCBValues service parameters 120
Table 99 SetMSVCBValues service parameters 121
Table 100 GetMsvReference service parameters 121
Table 101 GetMSVElementNumber service parameters 122
Table 102 USVCB Class Definition 122
Table 103 USVCB Services 124
Table 104 SendUSVMessage service parameters 124
Table 105 GetUSVCBValues service parameters 125
Table 106 SetUSVCBValues service parameters 125
Table 107 Sample value (SV) format definition 126
Table 108 Common Actions and Negative Responses 129
Table 109 Control Service 139
Table 110 Control Service Parameters 140
Table 111 File class definition 150
Table 112 File Service 151
Table 113 GetFile service parameters 151
Table 114 SetFile service parameters 151
Table 115 DeleteFile service parameters 152
Table A.1 Basic conformance statement 153
Table A.2 ACSI model conformance statements 154
Table A.3 ACSI service conformance statements 155
Table C.1 GSSE control block class definition 161
Table C.2 GsCB services 163
Table C.3 SendGSSEMessage parameter table 163
Table C.4 GetGsReference parameter table 164
Table C.5 GetGSSEDataOffset parameter table 165
Table C.6 GetGsCBValues parameter table 166
Table C.7 SetGsCBValues parameter table 167
Table C.8 GSSE message definition 168
Table D.1 Relationship between detailed quality identifiers and invalid or questionable quality 169
Foreword
This document is in accordance with the provisions of GB/T 1.1-2020 "Guidelines for standardization work Part 1.Structure and drafting rules for standardization documents"
Drafting.
This document is part 7-2 of GB/T 42151 "Electric Power Automation Communication Networks and Systems". GB/T 42151 has been published for the following
part.
--- Part 3.General requirements;
--- Part 4.System and project management;
--- Part 5.Communication requirements for functional and device models;
--- Part 6.Communication configuration description language for power automation systems related to intelligent electronic devices;
--- Part 7-1.Basic communication structure principles and models;
--- Part 7-2.Basic information and communication structure Abstract Communication Service Interface (ACSI);
--- Part 7-7.IEC 61850 related data model machine processable format for tools;
--- Part 8-1.Specific Communication Service Mapping (SCSM) Mapping to MMS (ISO 9506-1 and ISO 9506-2) and
ISO /IEC 8802-3.
This document is equivalent to IEC 61850-7-2.2020 "Electric power automation communication networks and systems Part 7-2.Basic information and communication
Abstract Communication Service Interface (ACSI).
Please note that some of the contents of this document may involve patents. The issuing organization of this document does not assume the responsibility for identifying patents.
This document was proposed by the China Electricity Council.
This document is under the jurisdiction of the National Technical Committee for Standardization of Power System Management and Information Exchange (SAC/TC82).
This document was drafted by. China Electric Power Research Institute Co., Ltd., State Grid Electric Power Research Institute Co., Ltd., State Grid Corporation of China
National Electric Power Dispatching and Control Center, China Southern Power Grid Electric Power Dispatching and Control Center, Tianjin Jingui Huihai Technology Development Co., Ltd., State Grid
Zhejiang Electric Power Co., Ltd., Beijing Sifang Relay Protection Automation Co., Ltd., Xuji Group Co., Ltd., State Grid Jibei Electric Power Co., Ltd.,
State Grid Nanjing Automation Co., Ltd., State Grid Jiangsu Electric Power Co., Ltd., Jicheng Electronics Co., Ltd., State Grid Tianjin Electric Power Co., Ltd.
China Southern Power Grid Co., Ltd., Changyuan Shenrui Relay Protection Automation Co., Ltd., Nanjing NARI Relay Protection Electric Co., Ltd., Dongfang
Electronics Co., Ltd., State Grid Beijing Electric Power Company, State Grid Hunan Electric Power Co., Ltd., State Grid Liaoning Electric Power Co., Ltd., State Grid
Shandong Electric Power Company Electric Power Research Institute, Shanghai Siyuan Hongrui Automation Co., Ltd.
The main drafters of this document are. Li Wenzhuo, Li Jinsong, Zhou Bin, Chang Naichao, Li Jin, Shen Jian, Tang Yongjian, Du Qiwei, Ren Yanming, Liao Zeyou,
Wang Changrui, Sun Dan, Zhang Jinhu, Zhao Jishuang, Shi Lin, Sun Fanen, Ruan Lixiang, Chen Jian, Feng Shanqiang, Zhang Qibing, Wang Yongfu, Li Yalei, Qian Gang, Li Qiang,
Xie Wenjun, Wei Jieru, Wang Zhihua, Wang Peiqi, Chen Haiyang, Li Long, Wang Wenhua, Li Ang, Liang Zhengtang, Zhang Chunxiao.
Introduction
GB/T 42151 "Electric Power Automation Communication Network and System" aims to provide interoperability for all devices in the electric power automation system.
It consists of the following parts.
--- Part 1.Introduction. The purpose is to introduce the overview of this document.
--- Part 2.Terminology. The purpose is to list the terms and definitions used in this document.
--- Part 3.General requirements. The purpose is to introduce the overall requirements of communication networks, with an emphasis on quality requirements.
--- Part 4.System and project management. The purpose is to describe the requirements for system and project management processes and the requirements for engineering and testing
Dedicated support tools required.
--- Part 5.Communication requirements for functions and device models. The purpose is to specify the communication requirements for various functions of the power automation system.
--- Part 6.Communication configuration description language for power automation systems related to intelligent electronic devices. The purpose is to provide a compatible
exchange of intelligent electronic device capability descriptions in a way that allows for the exchange of power automation system capabilities between tools provided by different manufacturers
describe.
--- Part 7.Basic communication structure of power automation system. The purpose is to define a hierarchical class model and the services provided by these classes.
services to enable communication between devices.
--- Part 8.Specific communication service mapping SCSM. The purpose is to provide substation control layer and bay layer and station control layer and
Communication mapping between bay layers.
--- Part 9.Specific communication service mapping SCSM. The purpose is to provide substation bay layer and process layer and bay layer and
Communication mapping between process layers.
--- Part 10.Conformance testing. The purpose is to specify the standard technology for implementing conformance testing and to use when proposing performance parameters
specific measurement techniques.
This document is part of a set of definitions that describe a hierarchical power automation communication architecture. This architecture provides abstract definitions of classes and services.
The definition is independent of specific protocol stacks, implementations, and operating systems.
IEC 61850 provides interoperability between various devices.
devices, logical nodes, data, data sets, report controls, or logs) and the services provided by these classes (e.g., read, write, report, define, delete)
To achieve communication between these devices.
This document defines the Abstract Communication Service Interface (ACSI) for use in power automation applications where intelligent
Real-time collaboration of electronic devices. The Abstract Communication Service Interface (ACSI) is defined to be independent of the underlying communication system.
The Specific Communication Service Mapping 1) (SCSM) is specified in IEC 61850-9-x.
1) ACSI is independent of specific mappings. Mapping to standard application layer or middleware technologies is possible.
This document defines the abstract communication service interface in the following three aspects.
--- A hierarchical class model of all information accessible through a communication network;
---Services that operate on these classes;
---Parameters related to each service.
The technology described by ACSI is abstracted from all the different ways of implementing various devices to work together.
This document does not provide comprehensive tutorial material. It is recommended to read IEC 61850-5, IEC 61850-7-3 before reading this document and IEC 61850-7-3.
IEC 61850-7-1.
NOTE 1 For definitions of general terms, see IEC 60050.
NOTE 2 Abstraction in ACSI has two meanings. First, only real devices (e.g. circuit breakers) or real functions are modeled, which are visible through the communication network and
This abstraction results in the hierarchical class model and their behavior defined in this document, IEC 61850-7-3, and IEC 61850-7-4.
The ACSI abstracts from the specific definition of how devices exchange information and only defines the conceptual coordination work. Finally, the specific information exchange is in SCSM
(Specific Communication Service Mapping).
Note 3.The examples use the class names defined in IEC 61850-7-3 and IEC 61850-7-4 (e.g. logical node class name XCBR). The standardized names are only used in
Defined in IEC 61850-7-4 and IEC 61850-7-3.
Power automation communication network and system
Part 7-2.Basic information and communication structure abstraction
Communications Services Interface (ACSI)
1 Scope
1.1 General
This document is used for ACSI communication in power automation. ACSI provides the following abstract communication service interface.
a) An abstract interface used to describe the communication between a client and a remote server. It is used to.
---Real-time data access and acquisition;
---Equipment control;
---Event reports and logs;
---Setting group control;
---Self-description of the device (device data dictionary);
---Data typing and data type discovery;
---File transfer.
b) Abstract interfaces are used to communicate quickly and reliably between applications in one device and multiple remote applications in other devices within the system.
Row event distribution (publisher/subscriber) and sample value transmission (publisher/subscriber).
1.2 Namespaces and versions
This clause is mandatory for any IEC 61850 namespace (as defined in IEC 61850-7-1).
The parameters used to identify the namespace version are.
---Namespace version..2007;
--- Namespace revision. B;
--- Namespace name. IEC 61850-7-2.2007B;
---Namespace release version. 3;
--- Namespace release date..2019-10-02.
The following table provides an overview of released versions of this namespace.
Version Release Date IEC Web Store Namespace
Version 1.0.2003-05 IEC 61850-7-2.2003 IEC 61850-7-2.2003
Version 2.0.2010-10 IEC 61850-7-2.2010 IEC 61850-7-2.2007
Amendment 1 to Version 2.0 2020-02 IEC 61850-7-2.2010/AMD1.2020 IEC 61850-7-2.2007B
Version 2.1 2020-02 IEC 61850-7-2.2010 AMD1.2020CSV IEC 61850-7-2.2007B
1.3 Code Component Distribution
The code components are divided into two versions. simplified version and complete version.
---The complete version contains the definitions of all basic types defined in this document and related documents, and is only available to purchasers of this document;
|