{"id":417129,"date":"2024-10-20T06:14:30","date_gmt":"2024-10-20T06:14:30","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bsi-pd-iec-tr-61850-90-52012-2\/"},"modified":"2024-10-26T11:36:28","modified_gmt":"2024-10-26T11:36:28","slug":"bsi-pd-iec-tr-61850-90-52012-2","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bsi-pd-iec-tr-61850-90-52012-2\/","title":{"rendered":"BSI PD IEC\/TR 61850-90-5:2012"},"content":{"rendered":"
This part of IEC 61850 provides a way of exchanging synchrophasor data between PMUs, PDCs WAMPAC (Wide Area Monitoring, Protection, and Control), and between control center applications. The data, to the extent covered in IEEE C37.118-2005, are transported in a way that is compliant to the concepts of IEC 61850 .<\/p>\n
However, given the primary scope and use cases, this document also provides routable profiles for IEC 61850-8-1 GOOSE and IEC 61850-9-2 SV packets. These routable packets can be utilized to transport general IEC 61850 data as well as synchrophasor data.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
4<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 4 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 5 Use cases 5.1 General 5.2 Wide area applications utilizing synchrophasors <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 5.3 Synchro-check Figures Figure 1 \u2013 Use case diagram for Synchro-check <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 5.4 Adaptive relaying <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | Figure 2 \u2013 Use case diagram for adaptive relaying <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 5.5 Out-of-step (OOS) protection Figure 3 \u2013 Use case diagram for out-of-step (OOS) protection <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 5.6 Situational awareness <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | Figure 4 \u2013 Use case diagram for situational awareness <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 5.7 State estimation and on-line security assessment Figure 5 \u2013 Use case diagram for state estimation <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 5.8 Archive data (event & continuous) Figure 6 \u2013 Use case diagram for archiving data <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 5.9 Wide area controls 5.9.1 General 5.9.2 Special protection schemes <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | Figure 7 \u2013 Use case diagram for wide area controls <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 5.9.3 Predictive dynamic stability maintaining system Figure 8 \u2013 Use case diagram for predictive dynamic stability <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 5.9.4 Under voltage load shedding <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | Figure 9 \u2013 Use case diagram for under voltage load shedding <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 5.9.5 Phenomenon assumption type WAMPAC <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Figure 10 \u2013 Use case diagram for WAMPAC <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 5.9.6 Phasor Data Concentrator (PDC) <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Figure 11 \u2013 Use case diagram for phasor data concentrator <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 6 Modelling considerations 6.1 General <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | 6.2 System hierarchy Figure 12 \u2013 Basic IEC\u00a061850 model of WAMPAC functions <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 6.3 PMU model Figure 13 \u2013 System hierarchy <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | 6.4 Phasor Data Concentrators (PDCs) 6.4.1 General 6.4.2 Substation PDC model Figure 14 \u2013 PMU object model Figure 15 \u2013 Substation PDC model with legacy PMUs <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | 6.4.3 Regional or system level PDC 6.4.4 Quality Figure 16 \u2013 Regional PDC object model <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 7 Communication requirements 7.1 General 7.2 Direct connection with tunnelling or R-SV service <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Figure 17 \u2013 Synchrophasor communication modelling for direct connection <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | 7.3 The gateway approach Figure 18 \u2013 PDC as phasor concentrator and (proxy) gateway <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 7.4 Requirement summary <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | 7.5 TCP use 8 Security model 8.1 General Figure 19 \u2013 Application locality and time scale <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | Figure 20 \u2013 End-to-end cryptographic integrity for IEC\u00a061850-9-2 implementations <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 8.2 Key management and cryptographic support <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | Figure 21 \u2013 State transitions for key usage <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | 8.3 Key Distribution Center (KDC) 9 Services 9.1 General <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | 9.2 Command service 9.2.1 General 9.2.2 Control blocks Tables Table 1 \u2013 Equivalent commands <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | Table 2 \u2013 R-MSVCB class definition <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | Table 3 \u2013 R-GoCB definition <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Table 4 \u2013 Current PHYCOMADDR structure Table 5 \u2013 UDPCOMADDR structure <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | 9.3 Configuration request service 9.3.1 General 9.3.2 CFG-1 Type of configuration data \u2013 Capabilities 9.3.3 CFG-2 or CFG-3 Type of configuration data \u2013 Measurements 9.3.4 Online access to CFG-1 configuration information 9.3.5 Offline access to CFG-2 and CFG-3 configuration information 9.4 Header information service <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | 9.5 Data transmission service 9.5.1 General 9.5.2 General 9.5.3 Coding synchrophasors data 9.6 Specific data mapping 9.7 Common data fields <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | 9.8 Time synchronization 9.9 Redundancy <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | 10 IEC logical node modelling for synchrophasor measurements <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | Table 6 \u2013 Extension to ClcMth to allow P-Class and M-Class <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 11 Synchrophasor profile mappings 11.1 General overview 11.2 A-Profiles Figure 22 \u2013 General service mappings <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | 11.3 A-Profile GOOSE, SV, and management A-Profile 11.3.1 Application layer Figure 23 \u2013 IEC\/TR\u00a061850-90-5 A-Profiles <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | 11.3.2 Session layer Figure 24 \u2013 General byte ordering of session protocol <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Figure 25 \u2013 Structure of IEC\/TR 61850-90-5 session protocol <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | Table 7 \u2013 Example encodings of SPDU length <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Figure 26 \u2013 Encoding of TimetoNextKey <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | 11.3.3 Payload <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Figure 27 \u2013 IEEE 802.3 frame format for SV and GOOSE Table 8 \u2013 IEC\u00a061850 Ethertype values <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | 11.3.4 Signature Figure 28 \u2013 Virtual LAN Tag <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | 11.3.5 ITU X.234 A-Profile options Table 9 \u2013 Allowed values for MAC signature value calculations <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | 11.4 KDC Profile 11.4.1 Signature Hash algorithm <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | 11.4.2 Identification payload Table 10 \u2013 RFC-3547 assigned Hash identifiers Table 11 \u2013 RFC-3547 assigned payload identifiers <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | Figure 29 \u2013 General format for IEC\/TR\u00a061850-90-5 payload extensions Table 12 \u2013 IEC\/TR\u00a061850-90-5 assigned payload identifiers <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | 11.4.3 Payload identification <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | 11.4.4 Policy response Figure 30 \u2013 Policy response frame <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | 11.4.5 Key download payload Table 13 \u2013 RFC-3547 key download type identifiers Table 14 \u2013 IEC\/TR 61850-90-5 key download type identifiers <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | Figure 31 \u2013 Key download response payload definition <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | 11.5 Internet group management protocol version 3 A-Profile 11.6 T-Profiles 11.6.1 General <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | 11.6.2 T-Profile to support GOOSE and SV A-Profile over Ethernet Figure 32 \u2013 A-Profile association to various T-Profiles <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Figure 33 \u2013 From RFC 768 Table 15 \u2013 UDP field implementation requirements <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | 11.6.3 T-Profile to support KDC (TCP and UDP) 11.6.4 T-Profile to support IGMPv3 11.6.5 Common T-Profile standards Table 16 \u2013 Network protocol conformance implementation statement (PICS)for IPv4 based T-Profiles <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | Figure 34 \u2013 Format of IP header Figure 35 \u2013 ToS byte field definition RFC-2474 and RFC-3168 <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | 12 Effects on IEC\u00a061850-5 Figure 36 \u2013 Security field definition from RFC 1108 <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | 13 Effects on the IEC\u00a061850-6 (SCL) 13.1 General 13.2 SCL extensions to support IEC\/TR\u00a061850-90-5 defined profiles <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | 13.2.1 General engineering process 13.2.2 Control block extensions <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | Figure 37 \u2013 Extension to tSampledValueControl Figure 38 \u2013 Extension to agSmvOpts <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | Figure 39 \u2013 Extension of tGSEControl Figure 40 \u2013 Definition of tPredefinedTypeOfSecurityEnum <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | 13.2.3 KDC access point Figure 41 \u2013 AccessPoint SCL production indicating a KDC function <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | 13.2.4 Addressing extensions Figure 42 \u2013 IED SCL XSD indicating the KDC(s) to be used Figure 43 \u2013 SCL tKDC type <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | Figure 44 \u2013 Extension to tPredefinedPTypeEnum Figure 45 \u2013 tP_IPbase extension for IPv6 addresses <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | 13.3 SCL extensions to support the configuration of IEEE C37.118.2 Figure 46 \u2013 Definition of tP_DNSName Figure 47 \u2013 Definition tp_ C37-118-IP-Port <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | 13.3.1 The underlying protocol 13.3.2 The data values <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | 13.3.3 SCL example 14 Effect on IEC\u00a061850-7-2 15 Effect on IEC\u00a061850-7-4 15.1 General 15.2 Namespace definition <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | 15.3 Extension of ClcMth 15.4 Addition of rate of change of frequency (ROCOF) DataObject 15.5 Modifications to the LTIM logical node class <\/td>\n<\/tr>\n | ||||||
114<\/td>\n | 15.6 Modifications to the LTMS logical node class Table 17 \u2013 Addition of TmLeaps in LTIM <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | Table 18 \u2013 Addition of TmLok in LTMS <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | Annex A (informative) Full SCL example for C37.118.2 configuration Figure A.1 \u2013 Single line for SCL example <\/td>\n<\/tr>\n | ||||||
124<\/td>\n | Annex B (informative) SCL examples for direct PMU and PDC-oriented communication <\/td>\n<\/tr>\n | ||||||
137<\/td>\n | Annex C (informative) Migration from IEEE C37.118 to IEC 61850 <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | Table C.1 \u2013 Migration steps from C37.118 to IEC\u00a061850 <\/td>\n<\/tr>\n | ||||||
140<\/td>\n | Annex D (informative) Open system interconnect (OSI) model Figure D.1 \u2013 Tasks of the OSI model layers Figure D.2 \u2013 Comparison between OSI model and Internet models <\/td>\n<\/tr>\n | ||||||
141<\/td>\n | Figure D.3 \u2013 Visualizing adding layer headers Figure D.4 \u2013 Peer-to-peer data exchange in the OSI model <\/td>\n<\/tr>\n | ||||||
142<\/td>\n | Figure\u00a0D.5 \u2013 Relationship of OSI services to protocol data units (PDUs) <\/td>\n<\/tr>\n | ||||||
143<\/td>\n | Figure D.6 \u2013 OSI model addressing <\/td>\n<\/tr>\n | ||||||
144<\/td>\n | Annex E (informative) IPv6 <\/td>\n<\/tr>\n | ||||||
146<\/td>\n | Annex F (informative) Edge authentication <\/td>\n<\/tr>\n | ||||||
147<\/td>\n | Annex G (informative) Example of A-Profile encodings Figure G.1 \u2013 Example encoding of GOOSE A-Profile <\/td>\n<\/tr>\n | ||||||
148<\/td>\n | Annex H (informative) Improving reliability of R-SV transmissions <\/td>\n<\/tr>\n | ||||||
149<\/td>\n | Annex I (informative) Guidance on HMAC and truncation <\/td>\n<\/tr>\n | ||||||
150<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Communication networks and systems for power utility automation – Use of IEC 61850 to transmit synchrophasor information according to IEEE C37.118<\/b><\/p>\n |