{"id":408164,"date":"2024-10-20T05:29:19","date_gmt":"2024-10-20T05:29:19","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iec-63110-12022\/"},"modified":"2024-10-26T09:58:32","modified_gmt":"2024-10-26T09:58:32","slug":"bs-en-iec-63110-12022","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iec-63110-12022\/","title":{"rendered":"BS EN IEC 63110-1:2022"},"content":{"rendered":"
This part of IEC 63110, as a basis for the other parts of IEC 63110, covers the definitions, use cases and architecture for the management of electric vehicle charging and discharging infrastructures. It addresses the general requirements for the establishment of an e-mobility eco-system, therefore covering the communication flows between different e-mobility actors as well as data flows with the electric power system. This document covers the following features: – management of energy transfer (e.g., charging session), reporting, including information exchanges related to the required energy, grid usage, contractual data, and metering data; – asset management of EVSE, including controlling, monitoring, maintaining, provisioning, firmware update and configuration (profiles) of EVSE; – authentication\/authorization\/payment of charging and discharging sessions, including roaming, pricing, and metering information; – the provision of other e-mobility services; – cybersecurity.<\/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 | ||||||
6<\/td>\n | Blank Page <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | English CONTENTS <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 3 Terms, definitions, and abbreviated terms 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 3.1.14 Constraints <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 3.1.40 Session <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 3.1.41 Transaction <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 3.2 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 4 Actors and architecture model 4.1 Actors 4.2 Architecture model Figures Figure 1 \u2013 Actor’s interactions <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 4.3 IEC 63110 metamodel Figure 2 \u2013 Architecture model of the component layer <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | Figure 3 \u2013 IEC 63110 metamodel <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 4.4 Actors and system view Figure 4 \u2013 IEC 63110 top-level architecture Figure 5 \u2013 Actors <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | Figure 6 \u2013 Generic communication architecture \u2013 System view <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 4.5 Implementation examples 5 Roles, actors, domains descriptions 5.1 General 5.2 Uses cases type descriptions Figure 7 \u2013 Charging site with two charging site zones controlled by a CSMS <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 5.3 Description of the business roles 5.4 Description of the system actors 5.5 Domain description 5.5.1 General Tables Table 1 \u2013 Business roles of the e-mobility domain Table 2 \u2013 System actors of the e-mobility domain <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 5.5.2 Deliver energy transfer services <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 5.5.3 Deliver e-mobility services 5.5.4 Manage charging station <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 6 Events, loops and sessions 6.1 General <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 6.2 Sessions and transactions description Figure 8 \u2013 Example of service session <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 7 General requirements 7.1 Generalities 7.2 Communication protocol requirements 7.2.1 General 7.2.2 Data transfer Figure 9 \u2013 Example of simultaneous service sessions <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 7.3 Communication architecture requirements 7.4 User specific requirements 7.5 CSMS implementation requirements 7.6 Interface requirements between CEM, RM and CSMS <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 7.7 Grid specific requirements 7.8 DSO requirements 7.9 Cybersecurity requirements 7.9.1 General 7.9.2 Security considerations for information <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Table 3 \u2013 Security considerations by information <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 7.9.3 Threat analysis <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 7.9.4 Security requirements <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 7.9.5 Relation with use cases 7.10 Safety requirements 8 Use cases 8.1 Generalities <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 8.2 Energy domain use cases 8.2.1 General 8.2.2 Use case list of the energy domain <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | 8.2.3 Smart charging management Table 4 \u2013 List of use cases of the energy domain <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 8.2.4 Charging with demand response Figure 10 \u2013 Smart charging sequence diagram <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 8.2.5 CSMS \u2013 RM exchange of information at the initiative of the CSMS <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 8.2.6 CSMS \u2013 RM exchange of information at the initiative of the RM <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 8.2.7 Power variation triggered by DSO <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | 8.2.8 Actors’ relations during a V2G session <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | 8.2.9 Information exchange required to ensure a dynamic energy transfer control <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | 8.2.10 Providing frequency regulation service by means of decentralized frequency measurements <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | 8.3 Manage CS domain use cases 8.3.1 General 8.3.2 Use case list of the manage CS domain Table 5 \u2013 List of use cases of the manage CS domain <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 8.3.3 Discover CS configuration <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | 8.3.4 Update a CS component properties <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | 8.3.5 Monitor a CS <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | 8.3.6 Update the firmware of a CS <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | 8.3.7 Reboot a CS <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | 8.3.8 The CSMS sets the information to be presented to the user <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | 8.3.9 The CSMS sets log criteria <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | 8.3.10 Retrieve log information from the CS <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | 8.3.11 Fault-code provisioning <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | 8.3.12 Information deletion triggered to CSMS by an SA <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | 8.3.13 CS deregistration <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | 8.3.14 Migration of the CS <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | 8.3.15 Onboarding the CS <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | 8.3.16 CA certificate provisioning <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | 8.3.17 ISO 15118 OCSP response messages <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | 8.3.18 Install CS certificate <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | 8.3.19 Install the certificate of the local CSMS <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | 8.3.20 Install CS certificate with key pairs created outside <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | 8.3.21 Certificate revocation <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | 8.4 Deliver e-mobility services domain use cases 8.4.1 General <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | 8.4.2 Use case list for deliver e-mobility service domain 8.4.3 Reservation of an EVSE Table 6 \u2013 List of use cases of the e-mobility domain <\/td>\n<\/tr>\n | ||||||
125<\/td>\n | 8.4.4 Authorization with locally presented credentials <\/td>\n<\/tr>\n | ||||||
127<\/td>\n | 8.4.5 Authorization by external means <\/td>\n<\/tr>\n | ||||||
129<\/td>\n | 8.4.6 Inform EVU about tariff during charging session <\/td>\n<\/tr>\n | ||||||
131<\/td>\n | 8.4.7 Inform EVU about tariff during operation <\/td>\n<\/tr>\n | ||||||
133<\/td>\n | 8.4.8 SDR information production <\/td>\n<\/tr>\n | ||||||
134<\/td>\n | 8.4.9 ISO 15118 contract certificate installation\/update <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | Annex A (informative)Implementation examples A.1 General A.2 A simple home example or a single EVSE at kerbside A.3 A more complex home with one or more CSs Figure A.1 \u2013 A simple home with one CS <\/td>\n<\/tr>\n | ||||||
140<\/td>\n | Figure A.2 \u2013 Complex home with one CS Figure A.3 \u2013 Complex home with two charging stations <\/td>\n<\/tr>\n | ||||||
141<\/td>\n | A.4 Parking lots or high-power CS example A.5 A CS with local production and storage Figure A.4 \u2013 Parking lot example <\/td>\n<\/tr>\n | ||||||
142<\/td>\n | Figure A.5 \u2013 CS with local production and battery storage <\/td>\n<\/tr>\n | ||||||
143<\/td>\n | Annex B (informative)Requirements used for selecting the transport technology B.1 Message specific timeouts shall be supported B.2 Transport foundation shall be IP based \u2013 with IPv4 and IPv6 support B.3 It shall be possible to transport encrypted and\/or signed message payload sub-elements <\/td>\n<\/tr>\n | ||||||
144<\/td>\n | B.4 The communication between a CSC and a CSMS shall be encrypted (transport layer) B.5 Bidirectional communication shall be possible B.6 Long messages shall not block urgent messages B.7 Message payload encoding shall be memory and CPU efficient B.8 Message priority shall be under the control of the application layer <\/td>\n<\/tr>\n | ||||||
145<\/td>\n | B.9 Asynchronous message transfer shall be supported B.10 Authentication with related session mechanism shall be supported B.11 Multicast messages should be supported B.12 Addressing scheme needs to be supported B.13 Coordinated time at CS level shall be supported <\/td>\n<\/tr>\n | ||||||
146<\/td>\n | B.14 Message encoding shall support non-standard payload elements B.15 Message encoding shall support versioning B.16 Communication shall be delay tolerant B.17 The communication technology should have a high reliability in payload delivery <\/td>\n<\/tr>\n | ||||||
147<\/td>\n | B.18 The selected communication technology should not have a single point of failure B.19 Technology shall have proven implementations B.20 Technology shall not have intellectual property restrictions B.21 The communication technology shall be stable <\/td>\n<\/tr>\n | ||||||
148<\/td>\n | B.22 Fine grained authorization shall be supported B.23 Communication layer shall be supported by at least two operating systems and embedded platforms for CS and CSMS B.24 Interoperability with conventional information models used in power industry <\/td>\n<\/tr>\n | ||||||
149<\/td>\n | B.25 Communication layer shall support IEC 63110’s multi-level architecture for CSMS <\/td>\n<\/tr>\n | ||||||
150<\/td>\n | B.26 Efficient support for binary payload B.27 Communication layer shall support request\/response and publish\/subscribe patterns <\/td>\n<\/tr>\n | ||||||
151<\/td>\n | Annex C (informative)Example of a complex service session C.1 Visual representation C.2 Description Figure C.1 \u2013 Example of a complex service session <\/td>\n<\/tr>\n | ||||||
153<\/td>\n | Annex D (informative)Classification of use cases impacts Table D.1 \u2013 Use case classification of the energy domain <\/td>\n<\/tr>\n | ||||||
154<\/td>\n | Table D.2 \u2013 Use case classification for the manage CS domain Table D.3 \u2013 Use case classification of the deliver e-mobility services domain <\/td>\n<\/tr>\n | ||||||
155<\/td>\n | Annex E (informative)Security use case sequence Figure E.1 \u2013 Security use case sequence <\/td>\n<\/tr>\n | ||||||
156<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Protocol for management of electric vehicles charging and discharging infrastructures – Basic definitions, use cases and architectures<\/b><\/p>\n |