{"id":255358,"date":"2024-10-19T16:52:50","date_gmt":"2024-10-19T16:52:50","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iec-61850-8-22019\/"},"modified":"2024-10-25T12:19:57","modified_gmt":"2024-10-25T12:19:57","slug":"bs-en-iec-61850-8-22019","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iec-61850-8-22019\/","title":{"rendered":"BS EN IEC 61850-8-2:2019"},"content":{"rendered":"
EC 61850-8-2:2018 specifies a method of exchanging data through any kinds of network, including public networks. Among the various kinds of services specified in IEC 61850-7-2, only the client\/server and time synchronization services are considered so far. NOTE Client\/server services of GOOSE and SMV models are mapped as well. For the client\/server services, the principle is to map the objects and services of the ACSI (Abstract Communication Service Interface defined in IEC 61850-7-2) to XML messages transported over XMPP. The mapping description includes mainly three aspects: \u2022 The usage of the XMPP protocol itself, describing in details which features are really used and how they are used by the mapping. \u2022 How to achieve end-to-end secured communications. \u2022 The description of the XML payloads corresponding to each ACSI service thanks in particular to the XML Schema and XML message examples.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
5<\/td>\n | Annex ZA(normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | English CONTENTS <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 1 Scope 1.1 General 1.2 Namespace name and version <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 1.3 Code Component distribution 2 Normative references <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 4 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 5 Overview 5.1 General Figures Figure 1 \u2013 Overview of functionality and profiles <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 5.2 Mapping of client\/server services 5.2.1 General Tables Table 1 \u2013 Services requiring client\/server Communication Profile <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 5.2.2 XML payloads <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 5.2.3 Implementation agreements 5.2.4 XMPP Figure 2 \u2013 Example of XML Payload <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 5.3 Time sync services 6 Usage of XMPP 6.1 Principles 6.2 Connection establishment 6.2.1 General 6.2.2 Usage of TLS and SASL <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 6.2.3 Stream Compression 6.3 Mapping of ACSI services Figure 3 \u2013 Generic structure of client\/server ACSI services <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 6.4 Usage of XMPP presence 6.5 Usage of the Roster 6.6 XMPP extensions 6.6.1 Usage of XMPP PING \u2013 XEP 0199 6.6.2 Usage of Stream Management \u2013 XEP 0198 6.7 Implementation agreements \u2013 XMPP PING \u2013 XEP 0199 <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 7 End-to-end security 8 Payload description 8.1 XSD overview 8.2 Objects of IEC 61850 8.2.1 General <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 8.2.2 Logical Node (LN) Figure 4 \u2013 Algorithm for logical node mapping Table 2 \u2013 Mapping of ACSI classes on MMS concepts <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | Figure 5 \u2013 Ordered list of functional constraints <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Figure 6 \u2013 Example of Logical Node type description <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 8.2.3 Mapping of references of Logical Nodes to VariableAccessSpecifications Figure 7 \u2013 List of the flattened Named Variables corresponding to an LN <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 8.2.4 Mapping of DataObjects reference to VariableAccessSpecifications Figure 8 \u2013 XML mapping of a LNReference with direct access Figure 9 \u2013 XML mapping of a LNReference with alternate access <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 8.2.5 Mapping of DataAttributes (DataAttr) reference to VariableAccessSpecifications 8.2.6 Usage of alternate access for DataObjects and DataAttributes references Figure 10 \u2013 Direct XML mapping of a FCD Figure 11 \u2013 Direct XML mapping of a FCDA <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Figure 12 \u2013 Alternate access without array element <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | Figure 13 \u2013 Alternate access with array element <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | Figure 14 \u2013 Alternate access with flattened variable and array element <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | 8.3 Mapping of IEC 61850-7-2 data attributes 8.3.1 BasicTypes Table 3 \u2013 Mapping of ACSI BasicTypes <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 8.3.2 Additional definitions of BasicType <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | 8.3.3 Common ACSITypes <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | Table 4 \u2013 PhyComAddr structure for Layer 2 communication <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | Table 5 \u2013 PhyComAddr for UPD\/IP communication <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | Table 6 \u2013 GetNameList conflicting IEC 61850 objectClass and objectScope Table 7 \u2013 Service error mappings for ACSI services using GetNameList <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | Table 8 \u2013 Read service error mappings <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | Table 9 \u2013 Write service error mappings <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | Table 10 \u2013 GetFileAttributeValues service error mappings <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | Table 11 \u2013 Encoding of IEC 61850-7-2 TimeQuality <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Table 12 \u2013 Encoding of the TriggerConditions Table 13 \u2013 Encoding of the ReasonForInclusionInReport <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | Table 14 \u2013 Encoding of the ReasonForInclusionInLog Table 15 \u2013 Encoding of the RCBReportOptions Table 16 \u2013 Encoding of the SVMessageOptions <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | 8.3.4 Mapping of quality common data attribute type specified in IEC 61850-7-2 Table 17 \u2013 Encoding of the CheckConditions <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | 8.4 General mapping of data values within XML payloads Table 18 \u2013 Encoding of IEC 61850-7-2 quality <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | 8.5 Extended behaviour for optimization of bandwidth 9 Server class model 9.1 General Table 19 \u2013 Examples of data values encoding <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | 9.2 GetServerDirectory 9.2.1 General Table 20 \u2013 Mapping of ACSI GetServerDirectory (LOGICAL DEVICE) <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Figure 15 \u2013 XML structure of GetServerDirectory-Request (LD) Figure 16 \u2013 XML structure of GetServerDirectory-Response (LD) <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Table 21 \u2013 Mapping of ACSI GetServerDirectory (FILE) <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | 10 Association model 10.1 Association relation to communication profiles Figure 17 \u2013 XML structure of GetServerDirectory-Request (FILE) Figure 18 \u2013 XML structure of GetServerDirectory-Response (FILE) Table 22 \u2013 Association model versus communication profiles <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 10.2 Two party association model for client\/server communication profile 10.2.1 Establishment of a secured end-to-end association 10.2.2 Association services <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Table 23 \u2013 Mapping of ACSI Associate service Table 24 \u2013 Description of Associate request elements <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | Figure 19 \u2013 XML structure of Associate-Request Figure 20 \u2013 XML structure of Associate-Response Table 25 \u2013 Description of Associate response elements <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Table 26 \u2013 Associate ACSI service error mappings <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | 11 Logical device model 11.1 General Table 27 \u2013 Mapping of ACSI Release service Table 28 \u2013 Release service error mappings <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Table 29 \u2013 Mapping of ACSI GetLogicalDeviceDirectory <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | 11.2 Response- Figure 21 \u2013 XML structure of GetLogicalDeviceDirectory-Request Figure 22 \u2013 XML structure of GetLogicalDeviceDirectory-Response <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | 11.3 Extended behaviour Table 30 \u2013 Extended mapping of ACSI GeLogicalDeviceDirectory <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | 12 Logical Node model 12.1 General Figure 23 \u2013 XML structure of extended GetLogicalDeviceDirectory-Request Figure 24 \u2013 XML structure of extended GetLogicalDeviceDirectory-Response Table 31 \u2013 Objectclasses for GetLogicalNodeDirectory service <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | 12.2 GetLogicalNodeDirectory 12.2.1 General <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Figure 25 \u2013 XML structure of GetLogicalNodeDirectory-Request Table 32 \u2013 Mapping of ACSI GetLogicalNodeDirectory <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | 12.2.2 Response- 12.2.3 Extended behaviour Figure 26 \u2013 XML structure of GetLogicalNodeDirectory-Response <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Table 33 \u2013 Extended mapping of ACSI GeLogicalNodeDirectory <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Figure 27 \u2013 XML structure of extended GetLogicalNodeDirectory-Request (step 1) Figure 28 \u2013 XML structure of extended GetLogicalNodeDirectory-Response (step 1) Figure 29 \u2013 XML structure of extended GetLogicalNodeDirectory-Request (step 2) <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | 12.3 GetAllDataValues 12.3.1 General Figure 30 \u2013 XML structure of extended GetLogicalNodeDirectory-Response (step 2) <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Table 34 \u2013 Mapping of ACSI GetAllDataValues <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Figure 31 \u2013 XML structure of GetAllDataValues-Request <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | 13 DataObject, DataAttribute, SubDataAttribute model 13.1 General 13.2 GetDataValues Figure 32 \u2013 XML structure of GetAllDataValues-Response <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Figure 33 \u2013 XML structure of GetDataValues-Request Table 35 \u2013 Mapping of GetDataValues service parameters <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | 13.3 SetDataValues Figure 34 \u2013 XML structure of GetDataValues-Response Table 36 \u2013 Mapping of SetDataValues service parameters <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | 13.4 GetDataDirectory 13.4.1 General Figure 35 \u2013 XML structure of SetDataValues-Request Figure 36 \u2013 XML structure of SetDataValues-Response <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Figure 37 \u2013 XML structure of GetDataDirectory-Request Table 37 \u2013 Mapping of GetDataDirectory service parameters <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | 13.4.2 Response- Figure 38 \u2013 XML structure of GetDataDirectory-Response <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | 13.4.3 Extended behaviour Table 38 \u2013 GetDataDirectory service error mappings <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Figure 39 \u2013 XML structure of extended GetDataDirectory-Request Table 39 \u2013 Extended mapping of ACSI GetDataDirectory <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | 13.5 GetDataDefinition 14 Data set class model 14.1 General Figure 40 \u2013 XML structure of extended GetDataDirectory-Response Figure 41 \u2013 Mapping of reference to persistent data set within logical device <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | 14.2 GetDataSetValues 14.2.1 General Figure 42 \u2013 Mapping of reference to persistent data set ouside logical device Figure 43 \u2013 Mapping of reference to non-persistent data set Table 40 \u2013 Mapping of GetDataSetValues service parameters <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Figure 44 \u2013 XML structure of GetDataSetValues-Request <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | 14.2.2 Response\u2212 Figure 45 \u2013 XML structure of GetDataSetValues-Response <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | 14.3 SetDataSetValues 14.3.1 General Table 41 \u2013 GetDataSetValues error mappings Table 42 \u2013 Mapping of SetDataSetValues service parameters <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | 14.3.2 Response- Figure 46 \u2013 XML structure of SetDataSetValues-Request Figure 47 \u2013 XML structure of SetDataSetValues-Response <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | 14.4 CreateDataSet 14.4.1 General Table 43 \u2013 SetDataSetValues error mappings <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | Figure 48 \u2013 XML structure of CreateDataSet-Request Table 44 \u2013 Mapping of CreateDataSet service parameters <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | 14.4.2 Response\u2212 Figure 49 \u2013 XML structure of CreateDataSet-Response <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | 14.5 DeleteDataSet 14.5.1 General Table 45 \u2013 CreateDataSet service error mappings Table 46 \u2013 Mapping of DeleteDataSet service parameters <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | 14.5.2 Errors Figure 50 \u2013 XML structure of DeleteDataSet-Request Figure 51 \u2013 XML structure of DeleteDataSet-Response <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | 14.6 GetDataSetDirectory 14.6.1 General Table 47 \u2013 DeleteDataSet service error mappings <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | Figure 52 \u2013 XML structure of GetDataSetDirectory-Request Table 48 \u2013 Mapping of GetDataSetDirectory service parameters <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | 14.6.2 Response- Figure 53 \u2013 XML structure of GetDataSetDirectory-Response <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | 15 ServiceTracking model Table 49 \u2013 GetDataSetDirectory service error mappings Table 50 \u2013 Mapping of ACSI ServiceType values <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | Table 51 \u2013 Mapping of ACSI errorCode values Table 52 \u2013 Mapping of CDC LTS <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | 16 Setting group control class model 16.1 Setting group control block definition 16.2 Setting group control class services 16.2.1 SelectActiveSG Table 53 \u2013 Mapping of CDC GTS Table 54 \u2013 Mapping of SGCB <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | Figure 54 \u2013 XML structure of SelectActiveSG-Request Figure 55 \u2013 XML structure of SelectActiveSG-Response+ Figure 56 \u2013 XML structure of SelectActiveSG-Response- <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | 16.2.2 SelectEditSG 16.2.3 SetEditSGValue Figure 57 \u2013 XML structure of SelectEditSG-Request <\/td>\n<\/tr>\n | ||||||
114<\/td>\n | 16.2.4 ConfirmEditSGValues Figure 58 \u2013 XML structure of SetEditSGValue-Request <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | 16.2.5 GetEditSGValue Figure 59 \u2013 XML structure of ConfirmEditSGValues Figure 60 \u2013 XML structure of GetEditSGValue-Request <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | 16.2.6 GetSGCBValues Figure 61 \u2013 XML structure of GetEditSGValue-Response Figure 62 \u2013 XML structure of GetSGCBValues-Request <\/td>\n<\/tr>\n | ||||||
117<\/td>\n | 17 Reporting and logging class model 17.1 Report model \u2013 Report control blocks 17.1.1 Buffered report control block Figure 63 \u2013 XML structure of GetSGCBValues-Response <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | Table 55 \u2013 BRCB structure <\/td>\n<\/tr>\n | ||||||
119<\/td>\n | 17.1.2 Unbuffered report control block Table 56 \u2013 URCB structure <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | 17.2 Reporting services 17.2.1 Report service Table 57 \u2013 Order of AccessResults for Report <\/td>\n<\/tr>\n | ||||||
122<\/td>\n | Figure 64 \u2013 XML structure of Report <\/td>\n<\/tr>\n | ||||||
123<\/td>\n | 17.2.2 GetBRCBValues Table 58 \u2013 Mapping of GetBRCBValues service parameters <\/td>\n<\/tr>\n | ||||||
124<\/td>\n | Figure 65 \u2013 XML structure of GetBRCBValues-Request <\/td>\n<\/tr>\n | ||||||
126<\/td>\n | 17.2.3 SetBRCBValues Figure 66 \u2013 XML structure of GetBRCBValues-Response <\/td>\n<\/tr>\n | ||||||
127<\/td>\n | Table 59 \u2013 Mapping of SetBRCBValues service parameters <\/td>\n<\/tr>\n | ||||||
128<\/td>\n | Figure 67 \u2013 XML structure of SetBRCBValues-Request <\/td>\n<\/tr>\n | ||||||
129<\/td>\n | 17.2.4 GetURCBValues 17.2.5 SetURCBValues 17.3 Log model 17.3.1 Overview Figure 68 \u2013 XML structure of SetBRCBValues-Response <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | Figure 69 \u2013 Relationship of LCB attributes to IEC 61850-7-2 log definitions Table 60 \u2013 LCB structure <\/td>\n<\/tr>\n | ||||||
131<\/td>\n | 17.3.2 Description of LCB attributes 17.3.3 Mapping of log and log control services <\/td>\n<\/tr>\n | ||||||
132<\/td>\n | Table 61 \u2013 Mapping of QueryLogByTime service parameters <\/td>\n<\/tr>\n | ||||||
133<\/td>\n | Figure 70 \u2013 XML structure of QueryLogByTime-Request <\/td>\n<\/tr>\n | ||||||
134<\/td>\n | Figure 71 \u2013 XML structure of QueryLogByTime-Response <\/td>\n<\/tr>\n | ||||||
136<\/td>\n | Figure 72 \u2013 XML structure of QueryLogAfter-Request Table 62 \u2013 ServiceError mappings for Log services Table 63 \u2013 Mapping of QueryLogAfter-Request parameters <\/td>\n<\/tr>\n | ||||||
137<\/td>\n | 17.3.4 Conformance 18 Mapping of the generic substation event model (GSE) \u2013 Generic object oriented substation event (GOOSE) 18.1 GOOSE control definition Table 64 \u2013 Log conformance requirements Table 65 \u2013TypeDescription definition for GoCB structure <\/td>\n<\/tr>\n | ||||||
138<\/td>\n | 18.2 Specialization for Layer 2 GoCB 18.3 Specialization for Routable GOOSE 18.4 GOOSE services 18.4.1 General 18.4.2 GetGoCBValues 18.4.3 SetGoCBValues 19 Transmission of sampled values class model 19.1 Sampled value control block 19.1.1 General 19.1.2 Specialization for Layer 2 Sampled value <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | 19.1.3 Specialization for Routable Sampled value 19.1.4 Specialization for Unicast Sampled value 19.2 Sampled value services 19.2.1 General 19.2.2 GetMSVCBValues 19.2.3 SetMSVCBValues 20 Control class model 20.1 General <\/td>\n<\/tr>\n | ||||||
140<\/td>\n | Table 66 \u2013 Controllable service parameters Table 67 \u2013 Mapping of IEC 61850-7-2 control model to control components <\/td>\n<\/tr>\n | ||||||
141<\/td>\n | 20.2 Overview of control services mapping 20.3 Select Table 68 \u2013 Mapping of control services <\/td>\n<\/tr>\n | ||||||
142<\/td>\n | Figure 73 \u2013 XML structure of Select-Request Table 69 \u2013 Mapping of Select parameters <\/td>\n<\/tr>\n | ||||||
143<\/td>\n | 20.4 SelectWithValue 20.4.1 SelectWithValue service parameter mapping 20.4.2 General mapping of the SelectWithValue service Figure 74 \u2013 XML structure of Select-Response Table 70 \u2013 SelectWithValue service parameter mapping <\/td>\n<\/tr>\n | ||||||
144<\/td>\n | Table 71 \u2013 Mapping of SelectWithValue parameters <\/td>\n<\/tr>\n | ||||||
145<\/td>\n | Figure 75 \u2013 XML structure of SelectWithValue-Request <\/td>\n<\/tr>\n | ||||||
146<\/td>\n | 20.4.3 SelectWithValue response\u2013 20.5 Cancel 20.5.1 Cancel service parameter mapping Figure 76 \u2013 XML structure of SelectWithValue-Response+ Figure 77 \u2013 XML structure of SelectWithValue-Response- Table 72 \u2013 SelectWithValue, Oper and Cancel DataAccessError specification <\/td>\n<\/tr>\n | ||||||
147<\/td>\n | 20.5.2 General mapping of the Cancel service Table 73 \u2013 Cancel service parameter mapping <\/td>\n<\/tr>\n | ||||||
148<\/td>\n | 20.5.3 Cancel response\u2013 Table 74 \u2013 Mapping of the Cancel service <\/td>\n<\/tr>\n | ||||||
149<\/td>\n | 20.6 Operate 20.6.1 Operate service parameter mapping 20.6.2 General mapping of the Operate service Table 75 \u2013 Operate service parameter mapping <\/td>\n<\/tr>\n | ||||||
150<\/td>\n | Table 76 \u2013 Mapping of the Operate service <\/td>\n<\/tr>\n | ||||||
151<\/td>\n | 20.6.3 Operate response\u2013 20.6.4 CommandTermination service parameter mapping 20.6.5 General mapping of the CommandTermination service <\/td>\n<\/tr>\n | ||||||
152<\/td>\n | Table 77 \u2013 Mapping of the CommandTermination service <\/td>\n<\/tr>\n | ||||||
153<\/td>\n | Figure 78 \u2013 XML structure of CommandTermination Request+ <\/td>\n<\/tr>\n | ||||||
155<\/td>\n | 20.7 TimeActivatedOperate 20.7.1 TimeActivatedOperate service parameter mapping 20.7.2 Mapping of the TimeActivatedOperate service 20.8 TimeActivatedOperateTermination service Figure 79 \u2013 XML structure of CommandTermination Request- <\/td>\n<\/tr>\n | ||||||
156<\/td>\n | 20.9 AdditionalCauseDiagnosis in negative control service responses Table 78 \u2013 Definition of LastApplError variable structure <\/td>\n<\/tr>\n | ||||||
157<\/td>\n | Figure 80 \u2013 XML structure of InformationReport with AdditionalCauseDiagnosis <\/td>\n<\/tr>\n | ||||||
159<\/td>\n | 20.10 Tracking of control services 20.10.1 General 20.10.2 Mapping of the Control service tracking (CTS) Table 79 \u2013 Mapping of ACSI AddCause values <\/td>\n<\/tr>\n | ||||||
160<\/td>\n | 21 Time and time synchronization model 22 Naming conventions 23 File transfer 23.1 File transfer model Table 80 \u2013 Mapping of CDC CTS Table 81 \u2013 Mapping of ACSI file class to MMS file object <\/td>\n<\/tr>\n | ||||||
161<\/td>\n | Table 82 \u2013 Reserved file suffixes <\/td>\n<\/tr>\n | ||||||
162<\/td>\n | 23.2 File services 23.2.1 GetFile <\/td>\n<\/tr>\n | ||||||
163<\/td>\n | Figure 81 \u2013 Mapping of ACSI GetFile to FileOpen, FileRead, FileClose <\/td>\n<\/tr>\n | ||||||
164<\/td>\n | Table 83 \u2013 Mapping of ACSI GetFile service <\/td>\n<\/tr>\n | ||||||
165<\/td>\n | Figure 82 \u2013 XML example of FileOpen Request Figure 83 \u2013 XML example of FileOpen Response+ Figure 84 \u2013 XML example of FileRead Request (first) Table 84 \u2013 GetFile service error mappings <\/td>\n<\/tr>\n | ||||||
166<\/td>\n | Figure 85 \u2013 XML example of FileRead Response+ (first) Figure 86 \u2013 XML example of FileRead Request (second) Figure 87 \u2013 XML example of FileRead Response+ (second) Figure 88 \u2013 XML example of FileClose Request Figure 89 \u2013 XML example of FileClose Response <\/td>\n<\/tr>\n | ||||||
167<\/td>\n | Table 85 \u2013 Mappings of ACSI ServiceErrors to FileOpen Service Errors Table 86 \u2013 Mappings of ACSI ServiceErrors to FileRead Service Errors <\/td>\n<\/tr>\n | ||||||
168<\/td>\n | 23.2.2 SetFile Figure 90 \u2013 Mapping of ACSI SetFile service Table 87 \u2013 Mappings of ACSI ServiceErrors to FileClose Service Errors <\/td>\n<\/tr>\n | ||||||
169<\/td>\n | Figure 91 \u2013 XML example of ObtainFile Request Figure 92 \u2013 XML example of ObtainFile Response Table 88 \u2013 Mapping of ACSI SetFile parameters <\/td>\n<\/tr>\n | ||||||
170<\/td>\n | 23.2.3 DeleteFile Table 89 \u2013 Mappings of ACSI ServiceErrors to ObtainFile Service Errors Table 90 \u2013 Mapping of ACSI DeleteFile service <\/td>\n<\/tr>\n | ||||||
171<\/td>\n | 23.2.4 GetFileAttributeValues Figure 93 \u2013 XML example of DeleteFile Request Figure 94 \u2013 XML example of DeleteFile Response Table 91 \u2013 Mappings of ACSI ServiceErrors to DeleteFile Service Errors <\/td>\n<\/tr>\n | ||||||
172<\/td>\n | Figure 95 \u2013 XML example of GetFileAttributeValues Request Table 92 \u2013 Mapping of ACSI GetFileAttributeValues parameters <\/td>\n<\/tr>\n | ||||||
173<\/td>\n | 24 Conformance 24.1 Notation 24.2 PICS 24.2.1 Profile conformance Figure 96 \u2013 XML example of GetFileAttributeValues Response <\/td>\n<\/tr>\n | ||||||
174<\/td>\n | Table 93 \u2013 PICS for A-Profile support Table 94 \u2013 PICS for Time Sync A-Profile support <\/td>\n<\/tr>\n | ||||||
175<\/td>\n | 24.2.2 XML Payload conformance Table 95 \u2013 PICS for T-Profile support Table 96 \u2013 MMS InitiateRequest general parameters <\/td>\n<\/tr>\n | ||||||
176<\/td>\n | Table 97 \u2013 MMS InitiateResponse general parameters Table 98 \u2013 MMS service supported conformance table <\/td>\n<\/tr>\n | ||||||
179<\/td>\n | Table 99 \u2013 MMS Parameter CBB <\/td>\n<\/tr>\n | ||||||
180<\/td>\n | Table 100 \u2013 GetNameList conformance statement Table 101 \u2013 GetCapabilityList conformance statement <\/td>\n<\/tr>\n | ||||||
181<\/td>\n | Table 102 \u2013 GetDomainAttributes conformance statement Table 103 \u2013 Status conformance statement <\/td>\n<\/tr>\n | ||||||
182<\/td>\n | Table 104 \u2013 Cancel conformance statement Table 105 \u2013 Identify conformance statement <\/td>\n<\/tr>\n | ||||||
183<\/td>\n | Table 106 \u2013 AlternateAccess conformance statement Table 107 \u2013 AlternateAccessSelection conformance statement <\/td>\n<\/tr>\n | ||||||
185<\/td>\n | Figure 97 \u2013 VariableSpecification for LDevice\/MHAI1.HA.phsAHar(7).cVal.mag.f <\/td>\n<\/tr>\n | ||||||
186<\/td>\n | Figure 98 \u2013 Shorter VariableSpecification for LDevice\/MHAI1.HA.phsAHar(7).cVal.mag.f <\/td>\n<\/tr>\n | ||||||
187<\/td>\n | Figure 99 \u2013 Non conformant VariableSpecification I <\/td>\n<\/tr>\n | ||||||
188<\/td>\n | Figure 100 \u2013 Non conformant VariableSpecification II <\/td>\n<\/tr>\n | ||||||
189<\/td>\n | Figure 101 \u2013 VariableSpecification for LDevice\/MHAI1.HA.phsAHar(7) [MX] <\/td>\n<\/tr>\n | ||||||
190<\/td>\n | Figure 102 \u2013 Shorter VariableSpecification for LDevice\/MHAI1.HA.phsAHar(7) [MX] Table 108 \u2013 VariableAccessSpecification conformance statement <\/td>\n<\/tr>\n | ||||||
191<\/td>\n | Table 109 \u2013 VariableSpecification conformance statement Table 110 \u2013 Read conformance statement Table 111 \u2013 Write conformance statement <\/td>\n<\/tr>\n | ||||||
192<\/td>\n | Table 112 \u2013 InformationReport conformance statement Table 113 \u2013 GetVariableAccessAttributes conformance statement Table 114 \u2013 DefineNamedVariableList conformance statement <\/td>\n<\/tr>\n | ||||||
193<\/td>\n | Table 115 \u2013GetNamedVariableListAttributes conformance statement Table 116 \u2013 DeleteNamedVariableList conformance statement Table 117 \u2013 ReadJournal conformance statement <\/td>\n<\/tr>\n | ||||||
194<\/td>\n | Table 118 \u2013 EntryContent conformance statement <\/td>\n<\/tr>\n | ||||||
195<\/td>\n | Table 119 \u2013 FileDirectory conformance statement Table 120 \u2013 FileOpen conformance statement Table 121 \u2013 FileRead conformance statement <\/td>\n<\/tr>\n | ||||||
196<\/td>\n | 24.3 PICS Statement 24.3.1 General 24.3.2 Substation configuration language 25 Substation Configuration Language (SCL) Table 122 \u2013 FileClose conformance statement Table 123 \u2013 Allowed P-Type definitions for client\/server addressing <\/td>\n<\/tr>\n | ||||||
197<\/td>\n | Annex A (normative)Communication stack A.1 Overview A.1.1 General <\/td>\n<\/tr>\n | ||||||
198<\/td>\n | A.1.2 XMPP communication profiles A.1.3 Non-XMPP communication profiles Figure A.1 \u2013 Overview of functionality and profiles <\/td>\n<\/tr>\n | ||||||
199<\/td>\n | A.2 Communication stack A.2.1 Overview of the protocol usage A.2.2 Client\/server services and communication profiles Figure A.2 \u2013 OSI reference model and profiles <\/td>\n<\/tr>\n | ||||||
200<\/td>\n | Table A.1 \u2013 Service and protocols for client\/server communication A-Profile Table A.2 \u2013 Service and protocols for client\/server XMPP T-Profile <\/td>\n<\/tr>\n | ||||||
201<\/td>\n | A.2.3 Time sync Table A.3 \u2013 Time sync A-Profile <\/td>\n<\/tr>\n | ||||||
202<\/td>\n | Table A.4 \u2013 Time sync T-Profile <\/td>\n<\/tr>\n | ||||||
203<\/td>\n | Annex B (informative)Deployment of XMPP infrastructure B.1 General B.2 Deployment of XMPP within one XMPP domain B.2.1 Use case facility Figure B.1 \u2013 Facility domain <\/td>\n<\/tr>\n | ||||||
204<\/td>\n | B.2.2 Use case hierarchy within a facility Figure B.2 \u2013 Hierarchical Aggregation at facility <\/td>\n<\/tr>\n | ||||||
205<\/td>\n | B.3 Deployment of XMPP while interconnecting more than one XMPP domain B.3.1 Interconnection of XMPP Domain Figure B.3 \u2013 DER Management System at facility <\/td>\n<\/tr>\n | ||||||
206<\/td>\n | Figure B.4 \u2013 Facility Management integration at DSO <\/td>\n<\/tr>\n | ||||||
207<\/td>\n | Figure B.5 \u2013 Multiple facilities at DSO <\/td>\n<\/tr>\n | ||||||
208<\/td>\n | Figure B.6 \u2013 VPP and contracted DERs <\/td>\n<\/tr>\n | ||||||
209<\/td>\n | Figure B.7 \u2013 indirect control using VPP JIDs Figure B.8 \u2013 VPP direct control using VPP JIDs <\/td>\n<\/tr>\n | ||||||
210<\/td>\n | Figure B.9 \u2013 VPP direct control using DSO JIDs Figure B.10 \u2013 DSO Indirect control with VPP JIDs <\/td>\n<\/tr>\n | ||||||
211<\/td>\n | B.3.2 Definition of a federation communication between XMPP domains Figure B.11 \u2013 DSO direct control <\/td>\n<\/tr>\n | ||||||
212<\/td>\n | B.3.3 Interconnection of Domain with federation Figure B.12 \u2013 Concept of federation in XMPP <\/td>\n<\/tr>\n | ||||||
213<\/td>\n | Figure B.13 \u2013 Federation DSO \u2013 Facility Figure B.14 \u2013 Use of federation with VPP <\/td>\n<\/tr>\n | ||||||
214<\/td>\n | Figure B.15 \u2013 communication with VPP JIDs \u2013 indirect control Figure B.16 \u2013 VPP communication with VPP JIDs \u2013 direct control <\/td>\n<\/tr>\n | ||||||
215<\/td>\n | Figure B.17 \u2013 VPP communication with DSO JIDs <\/td>\n<\/tr>\n | ||||||
216<\/td>\n | B.4 Communication path outage and recovery Figure B.18 \u2013 DSO Communication with VPP JIDs <\/td>\n<\/tr>\n | ||||||
217<\/td>\n | Annex C (informative)Security for DER integration based on XMPP C.1 General Figure C.1 \u2013 Base system for discussion of IT security requirements <\/td>\n<\/tr>\n | ||||||
218<\/td>\n | C.2 Assumptions and boundary conditions C.3 Derivation of security requirements <\/td>\n<\/tr>\n | ||||||
219<\/td>\n | C.4 Mapping of security options to XMPP based integration of DER <\/td>\n<\/tr>\n | ||||||
220<\/td>\n | C.5 Sequence diagrams C.5.1 General C.5.2 XMPP and Stream opening <\/td>\n<\/tr>\n | ||||||
221<\/td>\n | C.5.3 Stream establishment, ROSTER and presence Figure C.2 \u2013 XMPP Stream establishment \u2013 IEC 61850 Server to the XMPP Server Figure C.3 \u2013 XMPP Stream establishment \u2013 IEC 61850 Client to the XMPP Server <\/td>\n<\/tr>\n | ||||||
222<\/td>\n | C.5.4 Communication outage Figure C.4 \u2013 Stream establishment, roster and presence <\/td>\n<\/tr>\n | ||||||
223<\/td>\n | Figure C.5 \u2013 Communication outage \u2013 Loss of link <\/td>\n<\/tr>\n | ||||||
224<\/td>\n | Figure C.6 \u2013 Communication outage \u2013 Presence unavailable <\/td>\n<\/tr>\n | ||||||
225<\/td>\n | C.5.5 Request Response (Clear Transfer) Figure C.7 \u2013 Request response <\/td>\n<\/tr>\n | ||||||
226<\/td>\n | Figure C.8 \u2013 Request \u2013 Abort <\/td>\n<\/tr>\n | ||||||
227<\/td>\n | Annex D (normative)Mapping of services and errors over XMPP stanzas Table D.1 \u2013 ACSI services mapping over XMPP stanzas <\/td>\n<\/tr>\n | ||||||
229<\/td>\n | Table D.2 \u2013 Error mapping over XMPP stanzas <\/td>\n<\/tr>\n | ||||||
230<\/td>\n | Annex E (informative)Intentional deviations from IEC 61850-8-1 SCSM <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Communication networks and systems for power utility automation – Specific Communication Service Mapping (SCSM). Mapping to Extensible Messaging Presence Protocol (XMPP)<\/b><\/p>\n |