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