9.3 Plug-In Electrical Charging Vehicles and power feed in home scenario

9.3.1 Description

The aim of the Plug-In Electric Vehicle (PEV) Charging and Power feed use case is to show the interaction between the different actors that can be involved in the charging of Electric Vehicle in home scenario. The scenario includes engagement of various actors:

• Electricity-Network Service Provider (Electricity-N/W-SP),
• Dedicated Electric Vehicle Charging SP (EVC-SP) who takes care of special functions like the Demand Response (DR) enablement (cost effective PEV Charging and Power Feed),
• PEV-SP in charge of functions related to PEV service and maintenance (providing a data connection for PEV health purposes such as managing Power Feed cycles, PEV-SW upgrading & remote fault analysis, etc.)
• PEV manufacturer in charge of replacing faulty parts for the PEV

PEV can be considered as a load and also as power storage (DER resource). In the latter case, a Power Feed from the PEV's battery into the Electricity-N/W is required.

The Electricity-N/W-SP is responsible for the residential homes (smart) metering. Depending on local laws, the metering for the (Electrical Vehicle Charging Equipment) EVCE may be independent and might be a physical part of the EVCE.

Depending on the PEV's brand, a parallel wired data connection may be included in the EVCE charging plug to enable the PEV's controller to access its agreed service and maintenance provider (PEV-SP). In case of no wired connection (high data rate, e.g. Ethernet), a short reach link, e.g. via ZigBee® or even Bluetooth® may be established (medium data rate ~2 Mb/s). This connection will then be routed via the EVCE's mobile broadband link to the PEV-SP's control centre in parallel to the charging and power feed control data, which is routed to the EVC-SP's control centre.

Related Standard activities:

• TC 69 committee: working on [i.7] ISO/ IEC 15118 parts 1-4, vehicle to grid communication; currently under development EU standardisation Mandate 486 to CEN, CENELEC and ETSI (for further information refer to [i.8] Mandate 486)
• Open 2G: using [i.9] DIN specification 70121 and [i.7] IEC 15118
• DIN specification [i.9] 70121 defines the requirements for the communications between the electric vehicle (EV) and the charging EVCE).

9.3.2 Source

oneM2M-REQ-2012-0059R02 Plug-In Electric Vehicle Charging (PEV)

Note

from [i.2] ETSI TR 102 935 v2.1.1

9.3.3 Actors

• Electricity Network service provider (Electricity N/W-SP/DSO) is responsible for the residential homes smart metering.
• Electricity vehicle charging service provider (EVC-SP) takes care of special functions like the Demand Response (DR) enablement (cost effective PEV Charging and Power Feed)
• PEV service provider (PEV SP) offering functions in conjunction with PEV service and maintenance (PEV health check and management such as management of power feed cycles, PEV-SW upgrading & remote fault analysis, etc.)
• Communication operator /provider provide the public wireless data service to PEV-SP and EVC SP control centres.

9.3.4 Pre-conditions

Connection from PEV to EVCE through a wired EVCE plug (data communication) or wirelessly (ZigBee or Bluetooth) or any short range technology.

Public communication network from EVCE to PEV SP and EVCE SP control centres.

Public communication between EVCE metering and El. N/W SP

9.3.5 Triggers

Control and pricing announcements from El. N/W SP to for example balance the power N/W

Control and pricing trigger/initiate PEV being charged at a particular time with a specific power feed cycle that is appropriate for consumer (cheaper) and for El. N/W SP (balance power system).

PEV health management through PEV control link to EVCE

e.g. PEV SP initiates health check when PEV is plugged into EVCE for charging; if there is a problem detected or a PEV part status is over a certain limit, this will trigger a corrective measure according to health check result (e.g. PEV SP place an order for a part replacement to PEV manufacturer, or SW upgrade, etc.)

EVCE SP will control and manage EVCE through EVCE control link;

9.3.6 Normal Flow

An example flow to show the interaction between PEV SP (PEV health check), PEV manufacturer (PEV defect part replacement) and EVC SP (metering/charging):

• Red colour to refer to flow related to EVC charging application
• Green colour refer to flow related to PEV SP application
• Blue colour refer to flow related to PEV manufacturer application

Figure 9.3.6-1 PEV Normal Flow

• 1) PEV management application and EVC metering/charging application subscribe to information related to PEV.
• 2)
  • 2a) PEV is plugged to EVCE
  • 2b) PEV related information (e.g. PEV1) is sent to communication operator
  • 2c) PEV charging related information (e.g. .charging period)
• 3) Information sent in step 2 are sent to system operator which trigger the notification in step 4
• 4) Notifications are sent to the subscribed applications.
• 5) PEV charging parameters pulled/pushed to the EVC-SP
• 6) PEV management application sent an initiation of health check message to system operator
• 7) Initiation message is sent by system operator through communication operator to PEV to start the health check
• 8.) - 9) A PEV part defect is detected and a message is sent to the system operator, which triggers the notification of the PEV SP
• 10) System operator is sent a defect Notification to PEV SP application of the car part.
• 11) Which in turn send an order of the defected part to system operator
• 12) System operator sends the order to a PEV manufacturer

9.3.7 Alternative Flow

None

9.3.8 Post-conditions

None

9.3.9 High Level Illustration

Figure 9.3.9-1 PEV Charging High Level Illustration

9.3.10 Potential Requirements

1. Secure communication of the following transactions:
   • i. SW upgrade by PEV manufacturer,
   • ii. Collecting PEV status info for health check will trigger control or command (e.g. order new part, trigger to do a car service) to another SP
   • iii. Collecting charging information (metering) from EVCE i.e. power feed cycle and time and charging period to the EVC-SP control centre (the metering could be home owned smart meter or Utility owned)
   • iv. Collection metering info from EVCE (PEV considered as a load or resource), to Electric N/W provider for billing purposes. Controlling EVCE e.g. SW upgrade, part order
   • v. Pricing info from Electricity Network SP to EVC SP
   • vi. Fleet management control centre to collect location information of PEV
2. Potential requirements are similar to those of WAMS:
   • i. Data collection and reporting capability/function including data delivery to multiple applications
   • ii. Remote control of M2M Devices
   • iii. Data store and share
   • iv. Authentication of M2M system with M2M devices/ /collectors
   • v. Authentication of M2M devices with M2M applications
   • vi. Data integrity
   • vii. Prevention of abuse of network connection
   • viii. Privacy
   • ix. Security credential and software upgrade at the Application level.