How to configure an electric vehicle charging station to enable plug-and-charge functionality

Abstract

Various exemplary embodiments relate to configuring an electric vehicle charging station (102) and a charging station management system (101) such that authentication without user interaction can be enabled in response to a plugged-in electric vehicle (103). A computing device (200), a method (600), a computer readable medium, and a computer program are disclosed.

Description

Technical Field

[0001] This application generally relates to electric vehicle charging stations. In particular, some exemplary embodiments of this application relate to the configuration of the plug & charge function in an electric vehicle charging station.

Background Art

[0002] When a driver of an electric vehicle (EV) desires to start charging at a charging station, the driver is authenticated based on an identity certificate presented by the driver at the charging station.

[0003] It would be beneficial to improve the user experience for starting charging.

Summary of the Invention

[0004] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0005] Exemplary embodiments can enable the configuration of a charging station and a charging station management system to enable automatic authentication. Automatic authentication enables a user to start charging at a charging station such that the user only needs to plug in (insert) the charging cable of the electric vehicle. This configuration is implemented between the charging station and the charging station management system such that data from the charging cable or the vehicle is not required. Further, the interaction required from the user can be minimized.

[0006] According to a first embodiment, a computer implementation method is provided. The method includes the steps of: receiving a first message for authentication from an electric vehicle charging station, the message including an index for an automatic authentication function initiated by the detection of an electric vehicle connected to the electric vehicle charging station, and an identifier for the electric vehicle charging station; rejecting authentication based on the charging station identifier if the identifier is not associated with an authenticated user; receiving a second message for authentication from the electric vehicle charging station, the message including a user identifier; accepting authentication after determining that the user identifier is associated with an authenticated user; determining whether any message for authentication including an index has been rejected within a predetermined interval from an accepted authentication; if a message including an index has been received within a predetermined interval, linking the charging station identifier to an authenticated user associated with the user identifier; and accepting authentication based on the linked authenticated user for any subsequent message for authentication including a charging station identifier having an index.

[0007] In one embodiment, the predetermined interval has a value between 10 seconds and 10 minutes.

[0008] In one embodiment, the computer implementation method further includes, additionally or alternatively, the steps of: sending a request to determine whether the user wishes to enable an automatic authentication function at an electric vehicle charging station in response to the detection of a connected electric vehicle; and, after receiving approval from the user, linking the identifier of the charging station to the authenticated user.

[0009] In one embodiment, the computer implementation method further includes, either additionally or alternatively, the steps of determining a group of charging stations to which an electric vehicle charging station belongs, determining whether automatic authentication is permitted for the charging stations in the group, and, if automatic authentication is permitted for the group, linking the identifier of the charging station to an authenticated user.

[0010] In one embodiment, additionally or alternatively, a request is sent to the user in response to a decision to allow automatic authentication to the group only after receiving approval from the user.

[0011] In one embodiment, the computer implementation method further includes, either additionally or alternatively, the steps of: receiving a startup notification from an electric vehicle charging station; responding to the startup notification by requesting configuration settings from the electric vehicle charging station; determining whether an automatic authentication function, including the use of an electric vehicle charging station identifier with an indicator, is enabled based on the configuration settings; determining whether automatic authentication for a group is permitted to be enabled at startup if automatic authentication is disabled; sending a configuration message to the electric vehicle charging station to enable the automatic authentication function, and, if automatic authentication is permitted, setting an identifier for the charging station having an indicator to be used.

[0012] In one embodiment, the computer implementation method further includes, additionally or alternatively, the steps of sending a request to a user to determine whether the electric vehicle charging station is the user's personal electric vehicle charging station, and, upon receiving verification from the user, removing the electric vehicle charging station from the group.

[0013] According to a second embodiment, a computing device is provided. The computing device comprises at least one processor and at least one memory, wherein at least one memory is executed by at least one processor, and the computing device includes program code configured to cause the computing device to receive a first message for authentication from an electric vehicle charging station, the message including an index for an automatic authentication function initiated by the detection of an electric vehicle connected to the electric vehicle charging station and an identifier for the electric vehicle charging station, and to reject authentication based on the charging station identifier if the identifier is not associated with an authenticated user; to receive a second message for authentication from the electric vehicle charging station, the message including a user identifier, and to accept authentication after determining that the user identifier is associated with an authenticated user; to determine whether any message for authentication including an index has been rejected within a predetermined interval from an accepted authentication; and if a message including an index has been received within a predetermined interval, to link the charging station identifier with an authenticated user associated with the user identifier, and to accept authentication based on the linked authenticated user for any subsequent messages for authentication including a charging station identifier having an index.

[0014] In one embodiment, at least one memory containing program code, when executed by at least one processor, is further configured to cause a computing device to send a request to determine whether the user wishes to enable an automatic authentication function at an electric vehicle charging station in response to the detection of a connected electric vehicle, and, after receiving approval from the user, to link the identifier of the charging station to the authenticated user.

[0015] In one embodiment, additionally or alternatively, at least one memory containing program code, when executed by at least one processor, is further configured to cause a computing device to determine a group of charging stations to which an electric vehicle charging station belongs, to determine whether automatic authentication is permitted for the charging stations in the group, and, if automatic authentication is permitted for the group, to link the identifier of the charging station with an authenticated user.

[0016] In one embodiment, additionally or alternatively, at least one memory containing program code is further configured, when executed by at least one processor, to cause a computing device to send a request to determine whether an electric vehicle charging station is a user's personal electric vehicle charging station, the request including location information of the electric vehicle charging station to be verified by the user, and upon receiving verification from the user, to remove the electric vehicle charging station from the group.

[0017] In one embodiment, additionally or alternatively, at least one memory containing program code, when executed by at least one processor, is further configured to cause a computing device to determine whether automatic authentication is permitted in a group only after receiving authorization from a user, and to send a request to make that determination if the user wishes to enable the automatic authentication feature at an electric vehicle charging station.

[0018] In one embodiment, additionally or alternatively, at least one memory containing program code, when executed by at least one processor, is further configured to cause a computing device to receive a startup notification from an electric vehicle charging station, to respond to the startup notification by requesting configuration settings for the electric vehicle charging station, to determine whether the use of a first identifier having an auto-authentication function and indicators is enabled based on the configuration settings, to determine, if the auto-authentication setting is disabled, whether auto-authentication for the group is permitted to be enabled at startup, to send a configuration message to the electric vehicle charging station to enable the auto-authentication function, and, if the configuration is permitted, to set a first identifier having indicators for the charging station to be used.

[0019] According to a third aspect, when executed on a computing device, a computer-readable medium is provided that includes program instructions causing the computing device to perform the method of the first aspect.

[0020] According to a fourth aspect, when executed by a computing device, a computer program is provided which includes instructions causing the computing device to perform the method of the first aspect.

[0021] Many of the associated features will be more easily understood by referring to the following detailed explanation, which is considered in conjunction with the attached drawings. [Brief explanation of the drawing]

[0022] The accompanying drawings, included to provide a further understanding of the exemplary embodiments and constituting part of this specification, illustrate the exemplary embodiments and help interpret the principles of the exemplary embodiments together with the description.

[0023] [Figure 1]Shows, from the user's perspective, the process for configuring and enabling Plug&Charge at a charging station according to an exemplary embodiment. [Figure 2] Shows an example of a computing device configured to execute one or more exemplary embodiments. [Figure 3] Shows a message sequence chart between a charging station and a charging station management system for enabling Plug&Charge at a charging station according to an exemplary embodiment. [Figure 4] Shows a message sequence chart between a charging station and a charging station management system for the automatic configuration of a charging station according to an exemplary embodiment. [Figure 5] Shows a message sequence chart between a charging station and a charging station management system for verifying a permitted Plug&Charge operation according to an exemplary embodiment. [Figure 6] Shows a flowchart for configuring a charging station to enable a Plug&Charge operation according to an exemplary embodiment.

[0024] Like reference numerals are used to designate like parts in the accompanying drawings.

Best Mode for Carrying Out the Invention

[0025] Here, reference is made in detail to exemplary embodiments, the examples of which are shown in the accompanying drawings. The detailed description provided below in connection with the accompanying drawings is intended as a description of the examples and is not intended to represent the only form in which the examples are constructed or utilized. This description shows the functions of the examples and the possible order of operations for constructing and operating the examples. However, the same or equivalent functions and orders may be achieved by different examples.

[0026] Electric vehicle charging stations are used to charge electric vehicles (EVs). Charging stations are connected to a charging station management system (CSMS), for example, using OCPP (Open Charge Point Protocol). EV drivers own electric vehicles and charge them at charging stations.

[0027] Authentication at charging stations can be done using an RFID card or a mobile application. However, for EV drivers, starting the authentication process every time they arrive at a charging station can be cumbersome. Furthermore, RFID cards or mobile phones aren't always readily available and can easily be misplaced.

[0028] Technically, each EV driver is identified by a unique identifier, and when an EV driver presents an RFID card or uses a mobile phone to begin charging, the charging station sends this unique identifier to the charging station management system for authentication.

[0029] During the authentication process, the charging station queries the management system to determine if a specific identifier is allowed to begin charging at the charging station. The management system then checks which (if any) EV driver the identifier belongs to and approves or rejects the charging attempt.

[0030] Home charging stations typically use a technology called plug and charge because they are used by only one EV driver at a time (this should not be confused with ISO 15118 plug and charge, which is a different technology for authentication between the EV and the charging station via the EV charging cable).

[0031] In plug-and-charge, EV drivers do not need to use RFID cards / tags or mobile applications for authentication, but there is a fixed identifier (also called idTag) configured for the charging station (e.g., plug-and-charge ID=ABC123). When an EV driver connects a charging cable to a charging station, the charging station automatically sends an authentication request to the CSMS using the fixed identifier. Depending on the protocol used, the request may include, for example, "authentication, idTag=ABC123". The EV driver does not need to use an RFID card or mobile application for authentication. The CSMS then needs to approve this authentication, which is done in the same way as any other identifier (similar to those initiated using RFID or a mobile application). The CSMS system has the same identifier configured for the EV driver account; for example, an EV driver named John Doe is associated with idTAG=ABC123. If the CSMS approves the request, charging automatically begins without the EV driver needing to use an RFID card or mobile application. For example, the CSMS can find the idTag (ABC123) in John Doe's driver account and accept the authentication message.

[0032] For plug-and-charge to function, the same configuration is required for two different locations; the charging station must have a fixed identifier such as an idTag and enable the plug-and-charge configuration; and the CSMS must have the same identifier linked to an authenticated party such as an EV driver account.

[0033] One solution for configuring identifiers for two different locations (charging stations and CSMS) is to have a certain setting in the mobile application that requires the EV driver to log in to an application provided by the CSMS operator. The application has a setting called "Enable Plug & Charge". When the EV driver then enables this setting, the CSMS adds the new identifier to its configuration and sends the same identifier to the charging station configuration to enable Plug & Charge at the charging station.

[0034] This approach may not provide the best customer experience. The main problem is that EV drivers typically have many different applications on their mobile phones. An EV driver might have one application from the charging station manufacturer and another from the CSMS operator, and different applications may have different settings. EV drivers may not even know that there is such a thing as a Plug & Charge function. In addition, EV drivers may not know which application and which setting to look for it in. Finding the right settings from the right application is neither easy nor an optimal solution, especially for those who are not tech-savvy.

[0035] Generally, plug and charge refers to an automated identification and authentication procedure for starting the charging of an electric vehicle, where the only action required from the driver is to plug the charging cable into the EV and / or charging station.

[0036] The objective is to configure precise identifiers for both charging station and CSMS locations in a simple way that enables plug-and-charge functionality and minimizes necessary user interaction.

[0037] The proposed procedure is distinct from ISO 15118, a standard for vehicle-to-grid communication that specifies how a vehicle communicates with a charging station. This standard also defines prerequisites for identification via cable or Wi-Fi, enabling the charging station and backend services to identify the vehicle and its owner when the vehicle is plugged in. In contrast, in this disclosure, identification is based on a fixed identifier of each charging station, and not on information derived from the vehicle, such as a charging cable-based identifier.

[0038] Charging at certain charging stations, such as home charging stations, can be done as easily and automatically as possible using the methods described herein, so that even people with little or no technical knowledge can perform the task. Users may not even need to know how to install a mobile application or how to configure the device from the application.

[0039] In one embodiment, when a user plugs their EV into a charging station for the first time, they can identify themselves using an RFID card obtained from the CSMS operator for use with the charging station. After initial identification, charging begins normally. However, as a new feature, plug and charge can also be automatically enabled without user interaction, so the user does not need to perform any configuration anywhere. Therefore, the next time the user connects the charging cable to the charging station, plug and charge is already working, and an RFID card or mobile application may no longer be required for authentication after the initial charge.

[0040] Figure 1 shows, from the user's perspective, the process of configuring and enabling plug-and-charge in a charging station 102 according to an exemplary embodiment.

[0041] Generally, charging stations designed for home use may have a factory configuration with the Plug & Charge feature enabled. The factory configuration also includes an identifier unique to each charging station.

[0042] When a user 104, such as an EV driver, plugs the EV 103 into the charging station 102 for the first time, the charging station 102 sends a message to the CSMS 101 for authentication based on an identifier. Since the identifier set at the factory default of the charging station 102 is not linked to any EV driver account, the CSMS 101 rejects authentication and charging does not begin. An EV driver account refers to any account associated with the authenticated party. An EV driver account includes user information such as name and payment or billing details.

[0043] Subsequently, the EV driver can present the RFID card 105 linked to their EV driver account to the charging station 102. The charging station 102 can then send a new authentication message to the CSMS 101, where the message includes an identifier determined based on the user's RFID card 105. The CSMS 101 can then accept the authentication message, and charging begins at the respective charging station.

[0044] After authentication, CSMS101 can check whether any authentication messages have been rejected within a predetermined interval using a factory-configured identifier. If such rejected authentication messages are found, CSMS101 links the rejected factory-configured identifier to the same EV driver account to which the accepted identifier belongs.

[0045] Next, when the EV driver connects the charging cable, the charging station 102 again sends an authentication message containing an identifier that was set at the factory for each charging station 102. Here, the identifier can be found in the EV driver account, and the CSMS 101 can accept the authentication message. Thus, charging starts automatically without requiring the use of RFID.

[0046] Instead of the RFID card 105, user 104 can also be authenticated using a mobile application. User 104 can initiate authentication using the mobile application from a mobile device 106, such as user 104's mobile phone. Thus, enabling plug-and-charge functionality can be provided without requiring any complex or difficult configurations found in mobile applications. This configuration functions similarly to the RFID card 105, but instead of showing the RFID card 105, user 104 can log in to the mobile application provided by CSMS 101 and initiate charging from the mobile application. After the initial charge event, the mobile application is no longer required to initiate charging because plug-and-charge is configured and enabled.

[0047] In one embodiment, the CSMS 101 is configured to display a notification to user 104 via a mobile application that plug-and-charge is enabled. Thus, user 104 will know that when they next connect the vehicle to the charging station, charging will start automatically without requiring any further action from user 104.

[0048] Figure 2 shows an example of a computing device 200 configured to perform one or more exemplary embodiments. The computing device 200 includes, for example, a server device, a client device, a mobile phone, a tablet computer, a laptop computer, and so on. Although the computing device 200 is shown as a single device, it is understood that the functions of the computing device 200 may be distributed across multiple devices, where applicable. In one embodiment, the charging station management system 101 includes the computing device 200.

[0049] The computing device 200 includes at least one processor 201. The at least one processor 201 includes one or more of various processing devices, such as a variety of processing devices, such as a coprocessor, microprocessor, controller, digital signal processor (DSP), processing circuitry with or without a DSP, or a variety of other processing devices, such as application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), microcontroller units (MCUs), hardware accelerators, and dedicated computer chips.

[0050] The computing device 200 further includes at least one memory 202. The memory 202 is configured to store, for example, computer program code 203, which runs system software and application software. The memory 202 includes one or more volatile memory devices, one or more non-volatile memory devices, and / or a combination thereof. For example, the memory may be embodied as a magnetic storage device (e.g., a hard disk drive, magnetic tape, etc.), a magneto-optical storage device, or a semiconductor memory (e.g., a mask ROM, a PROM (programmable ROM), an EPROM (erasable PROM), a flash ROM, a RAM (random access memory), etc.).

[0051] The computing device 200 may further include a communication interface 204 configured to enable the transmission and / or reception of information to and from other devices. The communication interface 204 is configured to provide at least one wireless communication connection, such as a 3GPP mobile broadband connection (e.g., 3G, 4G, 5G). However, the communication interface 204 is configured to provide one or more other types of connections, such as a wireless local area network (WLAN) connection, such as those standardized by the IEEE 802.11 series or the Wi-Fi Alliance; a near-field wireless network connection, such as Bluetooth®, NFC (Near Field Communication) or RFID connection; a wired connection, such as a local area network (LAN) connection; a universal serial bus (USB) connection or an optical network connection; or a wired internet connection. The communication interface 204 is configured to include or be coupled to at least one antenna for transmitting and / or receiving radio frequency signals. One or more of the various types of connections are also implemented as separate communication interfaces that are coupled to or configured to be coupled to multiple antennas.

[0052] If the computing device 200 is configured to implement several functions, then, for example, several components and / or more components of the computing device 200, such as at least one processor 201 and / or memory 202, are configured to implement these functions. Furthermore, if at least one processor 201 is configured to implement several functions, these functions are implemented, for example, using program code 203 contained within memory 202.

[0053] The functions described herein are performed, at least in part, by one or more computer program product components, such as software components. According to one embodiment, the computing device 200 includes a processor 201 or processor circuit, such as a microcontroller, configured to perform the described embodiments of operation and function by program code 203 when executed. Alternatively or additionally, the functions described herein are performed, at least in part, by one or more hardware logic components. For example, but not limited to, exemplary types of hardware logic components used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-chip systems (SOCs), complex-programmable logic devices (CPLDs), and graphics processing units (GPUs).

[0054] The computing device 200 comprises means for performing at least one method described herein. In one embodiment, the means comprises at least one processor 201 and at least one memory 202 containing program code 203 configured to cause the computing device 200 to perform the method when executed by the at least one processor 201.

[0055] Figure 3 shows a message sequence chart between the charging station 102 and the charging station management system 101 for enabling plug-and-charge at the charging station 102, according to an exemplary embodiment.

[0056] In the 300, the charging station 102 is configured to have a unique identifier. Furthermore, the charging station 102 is configured to enable plug and charge. When plug and charge is enabled at the charging station, the charging station is configured to send an authentication message containing the unique identifier to the CSMS when it detects that the EV's charging cable has been connected to the charging station. This configuration is set at the factory.

[0057] This configuration includes a plug-and-charge characteristic identifier, such as "P&C idTag='PANDC:xxxxxx'", where xxxxx is a unique identifier for each charging station. The unique identifier for a charging station may be accompanied by an affix. In the example above, the affix is ​​represented by the prefix "PANDC:". The affix may consist of, for example, one or more letters, numbers, or a combination of letters and numbers. The affix can be used as an indicator containing an identifier for authentication based on plug-and-charge in a message.

[0058] In 301, the charging station 102 is configured to detect when an EV is plugged into the charging station 102.

[0059] In step 302, the charging station 102 is configured to send a message to the CSMS. The message may be an OCPP message. The message may include, for example, a request for authentication based on the identifier of the charging station 102 (e.g., "Authentication, id-Tag=PANDC:xxxxxx"). The CSMS 101 then receives the message, and in step 303, if the CSMS 101 determines that the identifier (idTag=PANDC:xxxxxx) is not linked to any EV driver account, in step 304, the CSMS 101 rejects authentication. Therefore, in step 305, charging is not started at the charging station 102.

[0060] Subsequently, in 306, the EV driver can present the RFID card linked to their respective EV driver account to the RFID reader of the charging station 102. The charging station 102 can then, in 307, send a new authentication message to the CSMS 101 with a different identifier (for example, idTag=A1B2C3D4, where A1B2C3D4 is the RFID card number). In 308, the CSMS 101 is configured to determine that the received identifier is associated with an EV driver account (for example, the RFID card is owned by John Doe, and the RFID-based identifier is linked to an account of a user named John Doe in the CSMS 101). In 309, the CSMS 101 system can accept the authentication message. In response, in 310, charging is initiated at each charging station 102.

[0061] After authentication, in 311, CSMS101 may check whether any authentication messages having identifiers beginning with a specific metric, such as "PANDC:", have been rejected within a predetermined interval 312. The predetermined interval 312 can be any value between 10 seconds and 10 minutes. For example, CSMS101 may check whether any authentication has been rejected within the past 30 seconds, 60 seconds, 90 seconds, 2 minutes, or 5 minutes. If such a rejected authentication message is found (for example in 304), CSMS101 is configured in operation 313 to link idTag=PANDC:xxxxxx (received in 302) to the same EV driver account to which the accepted idTag A1B2C3D4 (received in 307) belongs.

[0062] Next, when the EV driver connects the charging cable (in 314), the charging station 102 sends an authentication message again in 315, such as "Authentication, idTag=PANDC:xxxxxx", which includes an index and an identifier for the charging station 102. Here, in 316, the CSMS 101 is configured to determine that idTag=PANDC:xxxxxx was found from the EV driver account (for example, John Doe's account). As a result, in 317, the CSMS 101 is configured to accept the authentication message received in 315. Thus, in 318, the charging station receives the acceptance and can automatically start charging without the need to use RFID.

[0063] Instead of using an RFID card in 306, the user-associated identifier can be received, for example, via a mobile application or the user interface of the charging station. If a mobile application is used, the charging station identifier is linked to the same EV driver account that logged into the mobile application. In one embodiment, the charging station 102 includes means for receiving a user identifier manually entered by the user. The charging station identifier is then linked to the EV driver account linked to the identifier entered by the user.

[0064] In one embodiment, the mobile application may prompt the user after operation 311 whether they wish to enable the plug-and-charge function. If the user used an RFID card for identification, the prompt will appear the next time the user opens the mobile application. In one embodiment, the CSMS 101 is configured to proceed to operation 313 after receiving approval from the user via the mobile application. The advantage of this is that it provides a little more control over the configuration while maintaining ease of use, and the EV driver does not need to find the settings to configure plug-and-charge somewhere in the mobile application.

[0065] In one embodiment, the charging station is pre-configured at the factory. Therefore, when the charging station is shipped for deployment, it already includes the correct configuration (e.g., Plug & Charge = Enabled, idTag = PANDC:xxxxxx). However, many charging stations are shipped with a default configuration where Plug & Charge is disabled.

[0066] Figure 4 shows a message sequence chart between a charging station and a charging station management system for automatic configuration of a charging station according to an exemplary embodiment. In one embodiment, the charging station management system is configured to automatically configure the charging station upon restart so that factory commissioning or manual configuration is not required in order to enable automatic authentication for starting charging of plugged-in electric vehicles at each charging station.

[0067] In 400, the charging station 102 is configured at the factory to have the plug-and-charge function disabled. That is, the charging station is not configured to automatically send an authentication message in response to a detected connection of an EV. The charging station does not have to include any identifiers associated with the indicators of the plug-and-charge function.

[0068] In 401, the CSMS 101 is configured to form one or more groups of one or more charging stations. The charging station 102 may be added to a group such as a group of home charging stations. Each group may have a setting for the plug-and-charge configuration at restart, which can be set to either allow (Yes) or not allow (No).

[0069] In 402, the CSMS 101 can receive a BootNotification message when the charging station 102 restarts / starts. Upon receiving the message, in 403, the CSMS 101 is configured to determine what the plug-and-charge configuration setting is for the group to which the charging station belongs when it restarts.

[0070] If configuration is permitted, in 404, the CSMS 101 is configured to send a message (such as OCPP GetConfiguration) to the charging station 102 to obtain the current configuration for plug and charge. In 405, the charging station 102 responds with its configuration information. Based on the received configuration information, in 406, the CSMS 101 may determine that plug and charge is disabled at the charging station 102. In response to this, in 407, the CSMS 101 is configured to send a message (e.g., OCPP ChangeConfiguration) to the charging station 102 to change the configuration to one with plug and charge = enabled, idTag = PANDC:xxxxxx (where xxxxxx is the identifier of the charging station 102).

[0071] Following the new configuration in 408, including a valid and accurate setting for plug-and-charge, the charging station 102 can detect that an electric vehicle has been plugged in at 301. Here, the charging station 102 is configured to send an authentication message containing a plug-and-charge identifier at 302. Subsequently, the CSMS 101 and the charging station 102 are configured to perform the configuration and verification steps 303-318 of Figure 3. Therefore, the description of the operation will not be repeated herein.

[0072] Figure 5 shows a message sequence chart between a charging station and a charging station management system for verifying an authorized plug-and-charge operation, according to an exemplary embodiment.

[0073] In 500, the CSMS 101 is configured to form one or more groups of charging stations. The CSMS 101 can add charging station 102 to a group that has settings to allow plug and charge (yes), not allow (no), or allow only after user approval (ask). The group includes, for example, a charging station shown as a home charging station. This group corresponds to the same group of charging stations as operation 401 in Figure 4. Thus, the group of charging stations is configured by the CSMS 101 for both verifying permission to perform plug and charge operations and configuring the plug and charge settings upon restart.

[0074] The charging station 102 may include a plug-and-charge setting, which may be set at the factory (in 300) or configured upon reboot (in 408). After the charging station 102 detects that the electric vehicle has been plugged in (in 301), the system, including the charging station 102 and the CSMS 101, may perform operations 302–312 as described in Figure 3.

[0075] After operation 311, the CSMS 101 is configured to determine in 501 what group the charging station 102 belongs to and what the group setting for plug and charge is.

[0076] If the setting is no, plug and charge is not enabled for each EV driver at charging station 102. If the setting is yes, CSMS 101 proceeds to operation 313 and is configured to link the identifier of charging station 102 with the user account associated with the identifier received in 307. If the initial inquiry from the user is required for the setting, CSMS 101 is configured to send an authorization request to user 104 in 502. User 104 can receive the request, for example, via an application running on a mobile phone, and respond with authorization to CSMS 101 in 503. After authorization is received by CSMS 101, CSMS 101 is configured to proceed to operation 313. Subsequently, in 314-318, any subsequent requests for authentication in response to an electric vehicle plugged into charging station 102 are automatically verified by CSMS 101 as already described in Figure 3.

[0077] In the example above, the charging station could have been linked to an EV driver account by the CSMS. However, if a new charging station is shipped from the factory with default settings, it may not be linked to any EV driver account, and it may be unclear which user owns the charging station. Therefore, the CSMS may not know which user should receive notifications via the mobile application.

[0078] In one embodiment, a charging station is linked to an EV driver account upon initial charging at the charging station, based on an identifier received via at least one of an RFID card or a mobile application. The charging station is added by the CSMS to a group, such as a group of home charging stations, in its factory default settings. The user can identify themselves at the charging station upon initial charging, for example, by using an RFID card to initiate charging. Thus, after authentication is performed based on the RFID card, charging can be successfully initiated. The CSMS is configured to send notifications to the user via a mobile application running on the user's mobile device. The correct recipient of the notification is determined by the CSMS based on the identifier received for authentication.

[0079] The notification is configured to initiate a user interaction that asks the user whether the charging station is a home charging station, what the POI (point-of-interest) data associated with the charging station (such as its location on a map) is, and / or whether the user wishes to enable the plug-and-charge function. If the user acknowledges that the charging station is a home charging station, the CSMS is configured to remove the respective charging station from the group to avoid further group-specific configuration (e.g., settings to allow plug-and-charge, or configurations for plug-and-charge on restart as described in Figures 4 and 5). Furthermore, the mobile application can display a map view to the user that allows the user to point and modify the coordinates of the charging station. In addition, the user can add different POI data for the charging station, such as name, photo, or other data. If the user chooses to enable plug-and-charge, the CSMS can configure the charging station to automatically authenticate when an EV is plugged in at the charging station, as previously mentioned in Figure 3, by linking the charging station identifier with the EV user account associated with the user identifier.

[0080] Figure 6 shows a flowchart of Method 400 for configuring a charging station to enable plug-and-charge operation, according to an exemplary embodiment.

[0081] In 601, the method comprises receiving a first message for authentication from an electric vehicle charging station, the message comprising an index for an automatic authentication function initiated by the detection of an electric vehicle connected to the electric vehicle charging station, and an identifier for the electric vehicle charging station.

[0082] In 602, the method includes refusing authentication based on a charging station identifier if that identifier is not associated with an authenticated user.

[0083] In 603, the method includes receiving a second message for authentication from an electric vehicle charging station, the message including a user identifier.

[0084] In 604, the method includes determining that the user's identifier is associated with the authenticated user, and then accepting the authentication.

[0085] In 605, the method includes determining whether any message for authentication, including an indicator, was rejected within a predetermined interval from an accepted authentication.

[0086] In 606, the method may include linking a charging station identifier with an authenticated user associated with a user identifier when a message containing an indicator is received within a predetermined interval.

[0087] In 607, the method includes accepting authentication based on a linked authenticated user for any subsequent message for authentication that includes an identifier for a charging station having an indicator.

[0088] As technology advances, it will be apparent to those skilled in the art that the basic concepts of the present invention can be implemented in various ways. Therefore, the present invention and its embodiments are not limited to the above-described examples, but rather vary within the scope of the claims.

[0089] Any range or device value given herein may be extended or modified without loss of the desired effect. Furthermore, any embodiment may be combined with another embodiment unless expressly prohibited.

[0090] While the subject matter is described in language specific to structural features and / or behaviors, it should be understood that the subject matter defined in the attached claims is not necessarily limited to the specific features or behaviors described above. Rather, the specific features and behaviors described above are disclosed as examples of implementing the claims, and other equivalent features and behaviors are intended to be within the scope of the claims.

[0091] It should be understood that the benefits and advantages described above relate to one embodiment or to multiple embodiments. Embodiments are not limited to those that solve any or all of the described problems, or that have any or all of the described benefits and advantages. Furthermore, it should be understood that references to “one,” “at least one,” and “one or more” items refer to one or more of those items, or more of those items.

[0092] The operations of the methods described herein can be performed in any suitable order or, if necessary, simultaneously. Furthermore, individual blocks may be removed from any of the methods without departing from the scope of the subject matter described herein. Any aspect of the embodiments described above may be combined with any aspect of any other embodiment described to form further embodiments without losing the desired effect.

[0093] The term “contains” is used herein to mean including the specified method, block or element, but such block or element does not include an exclusive list, and the method or apparatus may include additional blocks or elements.

[0094] The objects may be referred to as the "first" or "second" object, but this does not necessarily indicate the order or importance of the objects. Rather, such attributes are used solely for the purpose of indicating differences between objects.

Claims

1. A step of receiving a first message for authentication from an electric vehicle charging station, wherein the first message includes an index for an automatic authentication function that is initiated by the detection of an electric vehicle connected to the electric vehicle charging station, and an identifier for the electric vehicle charging station. If the identifier is not associated with an authenticated user, the authentication based on the first message including the identifier of the electric vehicle charging station is rejected. A step of receiving a second message for authentication from the electric vehicle charging station, wherein the second message includes a user identifier. The steps include: accepting authentication based on the second message after determining that the user's identifier is associated with the authenticated user; A step of determining whether an arbitrary first message for authentication, including the aforementioned indicator, was rejected within a predetermined interval from the accepted authentication. If the first message including the indicator is received within the predetermined interval, the steps include linking the identifier of the electric vehicle charging station with the authenticated user associated with the user's identifier, A step of accepting authentication based on the authenticated user linked to any subsequent message for authentication including the identifier of the electric vehicle charging station having the aforementioned indicator. Computer implementation methods, including those mentioned above.

2. The computer implementation method according to claim 1, wherein the predetermined interval has a value between 10 seconds and 10 minutes.

3. Steps include: in response to the detection of a connected electric vehicle, sending a request to determine whether the user wishes to enable the automatic authentication function at the electric vehicle charging station; After receiving approval from the user, the steps include linking the identifier of the electric vehicle charging station to the authenticated user. The computer implementation method according to claim 1, further comprising:

4. The steps include determining the group of electric vehicle charging stations to which the aforementioned electric vehicle charging station belongs, A step of determining whether automatic authentication is permitted for the electric vehicle charging station of the group, If the aforementioned automatic authentication is permitted for the group, the steps include linking the identifier of the electric vehicle charging station with the authenticated user. The computer implementation method according to claim 1, including the method described in claim 1.

5. A step in which, in response to the detection of a connected electric vehicle, the user sends a request to determine whether they wish to enable the automatic authentication function at the electric vehicle charging station, and the request is sent to the user in response to the decision to allow automatic authentication for the group only after receiving approval from the user, After receiving approval from the user, the steps include linking the identifier of the electric vehicle charging station to the authenticated user. The computer implementation method according to claim 4, further comprising:

6. The steps include receiving a startup notification from the aforementioned electric vehicle charging station, The steps include: responding to the aforementioned startup notification by requesting the configuration settings of the electric vehicle charging station, A step of determining whether the automatic authentication function, which includes the use of the identifier of the electric vehicle charging station having the aforementioned indicator, is enabled based on the configuration settings, The steps include determining whether the automatic authentication for the group is permitted to be enabled at startup if automatic authentication is disabled, The steps include sending a configuration message to the electric vehicle charging station in order to enable the automatic authentication function, and setting the identifier of the electric vehicle charging station having the identifier to be used if the automatic authentication is permitted. The computer implementation method according to claim 4, further comprising:

7. The steps include sending a request to the user to determine whether the electric vehicle charging station is the user's personal electric vehicle charging station, Upon receiving verification from the user, the step of removing the electric vehicle charging station from the group is to The computer implementation method according to claim 4 or 6, further comprising:

8. A computing device comprising at least one processor and at least one memory, wherein when the at least one memory is executed by the at least one processor, the computing device has A first message for authentication is received from an electric vehicle charging station, the first message including an index for an automatic authentication function that is initiated by the detection of an electric vehicle connected to the electric vehicle charging station, and an identifier for the electric vehicle charging station. If the identifier is not associated with an authenticated user, the authentication based on the first message containing the identifier of the electric vehicle charging station is rejected. The electric vehicle charging station receives a second message for authentication, and the second message includes a user identifier. After determining that the user's identifier is associated with the authenticated user, the user accepts authentication based on the second message. Determine whether an arbitrary first message for authentication, including the aforementioned indicator, was rejected within a predetermined interval from the accepted authentication. If the first message containing the indicator is received within the predetermined interval, the identifier of the electric vehicle charging station is linked to the authenticated user associated with the user's identifier. Allow authentication to be accepted based on the linked authenticated user for any subsequent message for authentication that includes the identifier of the electric vehicle charging station having the aforementioned indicator. A computing device containing program code configured in such a way.

9. When the at least one memory containing program code is executed by the at least one processor, the computing device, In response to the detection of a connected electric vehicle, the system causes the user to send a request to determine whether they wish to enable the automatic authentication function at the electric vehicle charging station. After receiving approval from the user, the identifier of the electric vehicle charging station is linked to the authenticated user. The computing device according to claim 8, further configured as follows.

10. When the at least one memory containing program code is executed by the at least one processor, the computing device, Determine the group of electric vehicle charging stations to which the aforementioned electric vehicle charging station belongs. The system determines whether automatic authentication is permitted for the electric vehicle charging station of the group. If the aforementioned automatic authentication is permitted for the group, the identifier of the electric vehicle charging station is linked to the authenticated user. The computing device according to claim 8, further configured as follows.

11. The computing device according to claim 10, wherein a request is sent to the user if it is determined that automatic authentication should be permitted for the group only after approval has been received from the user.

12. When the at least one memory containing program code is executed by the at least one processor, the computing device, The electric vehicle charging station receives a startup notification, In response to the aforementioned startup notification, the system requests the configuration settings for the electric vehicle charging station. The automatic authentication function, which includes the use of the identifier of the electric vehicle charging station having the aforementioned indicator, determines whether it is enabled based on the configuration settings. Determine whether the automatic authentication for the group is permitted to be enabled at startup if automatic authentication is disabled. To enable the automatic authentication function, a configuration message is sent to the electric vehicle charging station, and if the automatic authentication is permitted, the identifier of the electric vehicle charging station having the identifier to be used is set. The computing device according to claim 10, further configured as follows.

13. When the at least one memory containing program code is executed by the at least one processor, the computing device, The user is instructed to send a request to determine whether the electric vehicle charging station is the user's personal electric vehicle charging station. Upon receiving verification from the aforementioned user, the electric vehicle charging station is removed from the group. A computing device according to claim 10 or 12, further configured as follows.

14. A computer-readable medium, when executed on a computing device, containing program instructions that cause the computing device to perform the method according to claim 1.

15. A computer program, when executed by a computing device, that includes instructions causing the computing device to perform the method according to claim 1.

Images