WO2023172672A1

WO2023172672A1 - Systems and methods for determining charging station compatibility

Info

Publication number: WO2023172672A1
Application number: PCT/US2023/014889
Authority: WO
Inventors: Scott Mercer; Alexandra M. PRODANIUK CARPENTER; Jeffrey Kinsey
Original assignee: Volta Charging LLC
Current assignee: Volta Charging LLC
Priority date: 2022-03-10
Filing date: 2023-03-09
Publication date: 2023-09-14
Anticipated expiration: 2024-09-10

Abstract

Systems and methods are provided herein for identifying incompatible vehicles parked at EVCS parking spaces and taking actions to disincentivize users of said incompatible vehicles from blocking the EVCS parking spaces. This may be accomplished by an EVCS detecting a vehicle in a first EVCS parking space and determining a vehicle characteristic (e.g., make, model, etc.) of the vehicle. The EVCS can use the vehicle characteristic to determine if the vehicle is compatible for charging with the EVCS. If the vehicle is not compatible, the EVCS can transmit a notification indicating that an unauthorized vehicle is parked in the EVCS parking space.

Description

SYSTEMS AND METHODS FOR DETERMINING CHARGING STATION COMPATIBILITY

Background

[0001] The present disclosure relates to computer-implemented techniques for charging electric vehicles, and in particular to techniques for allocating parking spaces used for charging electric vehicles.

Summary

[0002] As more consumers transition to electric vehicles, there is an increasing demand for electric vehicle charging stations (EVCSs). These EVCSs usually supply electric energy, either using cables or wirelessly, to the batteries of electric vehicles. For example, a user can connect their electric vehicle via cables of an EVCS and the EVCS supplies electrical current to the user’s electric vehicle. The cables and control systems of the EVCSs can be housed in kiosks that may be placed in areas of convenience, such as in parking lots at shopping centers, in front of commercial buildings, or in other public places.

[0003] The EVCSs allow a driver of an electric vehicle to park the electric vehicle close to the EVCS (e.g., in a parking space designated for the EVCS) and begin the charging process. Incompatible vehicles sometimes use the parking spaces designated for the EVCSs, preventing compatible electric vehicles from charging. An incompatible vehicle may be any vehicle that cannot or does not properly utilize an EVCS. For example, internal combustion engine vehicles that cannot utilize EVCSs may be considered incompatible vehicles. In another example, an electric vehicle (e.g., Nissan Leaf) may be incompatible with certain EVCSs because the EVCSs’ connector (e.g., SAE JI 772 connector) cannot charge said electric vehicle. When incompatible vehicles park in the parking spaces designated for charging, they block compatible electric vehicles from accessing EVCSs, decreasing the efficiency of EVCSs. With more electric vehicles on the road than ever before, there are already situations where the number of electric vehicles requiring a charge outnumbers the available EVCSs. Incompatible vehicles blocking compatible vehicles from charging only add to the scarcity of available EVCSs. The lack of available EVCS parking spaces can result in prolonged wait times, suboptimal charging allocation, electric vehicles running out of charge, and/or an overall poor user experience. In view of these deficiencies, there exists a need for improved systems and methods for reducing the number of incompatible vehicles that block compatible vehicles from using an EVCS.

[0004] Various systems and methods described herein address one or more these problems by identifying incompatible vehicles and taking actions to disincentivize users of incompatible vehicles from blocking EVCS parking spaces. To disincentivize incompatible vehicles from blocking compatible vehicles, an EVCS must first be able to accurately identify incompatible vehicles. As described herein, an EVCS may identify incompatible vehicles using one or more sensors to detect and capture information about a vehicle located in the EVCS’s parking space. For example, these sensors may be image sensors (e.g., one or more cameras), ultrasound sensors, depth sensors, infrared (IR) cameras, Red Green Blue (RGB) cameras, passive IR (PIR) cameras, proximity sensors, radar, tension sensors, near field communication (NFC) sensors, and/or any combination thereof. Once a vehicle enters a first location (e.g., the EVCS’s parking space) the one or more sensors can detect the vehicle and capture information about the vehicle. The EVCS can then use the information captured by the sensors to determine one or more vehicle characteristics (e.g., model, make, color, license plate number, charging status, tire pressure, specifications, condition, etc.). The EVCS can compare the vehicle characteristic with a database of characteristics compatible with the EVCS to determine compatibility. For example, if the vehicle’s make and model corresponded to a vehicle that uses an internal combustion engine, the database would indicate that the vehicle is not compatible with the EVCS.

[0005] If the EVCS determines that the vehicle is not compatible with the EVCS, the EVCS can take actions to disincentivize the user of the vehicle from using the EVCS’s parking space. For example, the EVCS may generate a notification on a display of the EVCS indicating that the vehicle is not authorized to use the EVCS’s parking space. In another example, the EVCS may audibly alert passersby (e.g., the driver of the incompatible vehicle) that the vehicle is not authorized to use the EVCS’s parking space. The EVCS may also notify (e.g., via the display, push notification, etc.) the driver of the incompatible vehicle of other charging stations that are compatible with the vehicle. For example, if the vehicle characteristic indicates that the vehicle is a Nissan Leaf and the EVCS is incompatible with the Nissan Leaf, the EVCS can search for charging stations that are compatible with the vehicle and display said locations for the vehicle. If the incompatible vehicle stays in the EVCS’s parking space for a time period (e.g., more than five minutes), the EVCS may transmit a notification to site security and/or a towing company. The notification may comprise vehicle characteristics, location, and/or similar such information. For example, the notification may comprise the license plate number of the vehicle and the location of the EVCS.

[0006] A vehicle may become incompatible over time. For example, when an electric vehicle arrives at the EVCS’s parking space, the EVCS may determine that the vehicle is a compatible vehicle based on a first vehicle characteristic (e.g., make, model, etc.) of the electric vehicle corresponding to an electric vehicle that can charge using the EVCS. The EVCS may then receive a second vehicle characteristic indicating that the vehicle has been located in the EVCS’s parking space for longer than a time period (e.g., three hours). The EVCS can determine, based on the first vehicle characteristic and the second vehicle characteristic, that the vehicle is no longer compatible. Based on the determination that the vehicle is no longer compatible, the EVCS can take actions to disincentivize the user of the vehicle from using the EVCS’s parking space as referenced above. For example, the EVCS may send a push notification to a device associated with the driver of the incompatible vehicle indicating that the vehicle has passed the allocated time limit for charging. The notification may comprise a warning that if the vehicle is not moved, then higher charging rates will be enforced, the vehicle will be towed, and/or similar such actions.

[0007] The information collected by the EVCS can be used to more efficiently train a machine learning algorithm for identifying vehicle characteristics. For example, training data may be identified using known events (e.g., when the EVCS detects the vehicle in the EVCS’s parking space, when the EVCS begins charging the vehicle, when a user checks in, etc.). Known events are beneficial as the information collected during the known events often contains helpful training data. For example, when the EVCS begins charging an electric vehicle, the data received from a camera of the EVCS will include video of the electric vehicle being charged. The video data containing the electric vehicle can be helpful training data for a machine learning algorithm used for identifying vehicle characteristics. Once the EVCS determines that charging has begun, the EVCS flags the video data received during the charging as data to be used to train the machine learning algorithm to identify compatible vehicle characteristics. In another example, when the EVCS detects a vehicle in the EVCS’s parking space that does not begin charging, the EVCS’s one or more sensors will include video of the vehicle. The video data containing the vehicle may be used to train a machine learning algorithm to identify non-compatible vehicle characteristics. Once the EVCS determines that vehicle is located in the parking space and is not charging, the EVCS flags the video data received during the time the vehicle is parked in the parking space to be used to train the machine learning algorithm.

[0008] The marked data can be used in conjunction with other information determined by the EVCS (e.g., vehicle characteristics) to increase the efficiency of the training of the machine learning process. For example, when an electrical vehicle begins charging (known event), the EVCS can flag the video data received from the camera. Upon connection, the EVCS may also receive the make and model of the electric vehicle using ISO 15118. The EVCS can pair the vehicle characteristic information (e.g., make and model) with the flagged video data, generating training data for the machine learning algorithm. The generated training data comprises images of the compatible electric vehicle and the make and model of the compatible electric vehicle, allowing the machine learning algorithm to be trained more efficiently. In another example, when a vehicle enters the parking space and does not begin charging (known event), the EVCS can flag the video data received from the camera. Using the one or more sensors, the EVCS can determine (e.g., via license plate lookup) the make and model of the vehicle. The EVCS can pair the vehicle characteristic information (e.g., make and model) with the flagged video data, generating training data for the machine learning algorithm. The generated training data comprises images of the incompatible vehicle and the make and model of the incompatible vehicle, allowing the machine learning algorithm to be trained more efficiently.

Brief Description of the Drawings

[0009] The below and other objects and advantages of the disclosure will be apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings, in which:

[0010] FIG. 1 shows an illustrative diagram of a system for identifying incompatible vehicles and taking actions to disincentivize the users of the incompatible vehicles from parking in a parking space, in accordance with some embodiments of the disclosure; [0011] FIGS. 2 A and 2B show another illustrative diagram of a system for identifying incompatible vehicles and taking actions to disincentivize the users of the incompatible vehicles from parking in a parking space, in accordance with some embodiments of the disclosure;

[0012] FIGS. 3A and 3B show another illustrative diagram of a system for identifying incompatible vehicles and taking actions to disincentivize the users of the incompatible vehicles from parking in a parking space, in accordance with some embodiments of the disclosure;

[0013] FIGS. 4 A and 4B show illustrative diagrams of notifications indicating an incompatible vehicle is parked at an electric vehicle charging station, in accordance with some embodiments of the disclosure;

[0014] FIG. 5 shows an illustrative block diagram of an EVCS system, in accordance with some embodiments of the disclosure;

[0015] FIG. 6 shows an illustrative block diagram of a user equipment device system, in accordance with some embodiments of the disclosure;

[0016] FIG. 7 shows an illustrative block diagram of a server system, in accordance with some embodiments of the disclosure;

[0017] FIG. 8 is an illustrative flowchart for identifying incompatible vehicles and taking actions to disincentivize the users of the incompatible vehicles from parking in a parking space, in accordance with some embodiments of the disclosure;

[0018] FIG. 9 is another illustrative flowchart for identifying incompatible vehicles and taking actions to disincentivize the users of the incompatible vehicles from parking in a parking space, in accordance with some embodiments of the disclosure; and

[0019] FIG. 10 is an illustrative flowchart of flagging images for training a machine learning algorithm, in accordance with some embodiments of the disclosure.

Detailed Description

[0020] FIG. 1 shows an illustrative diagram of a system 100 for identifying incompatible vehicles and taking actions to disincentivize the users of incompatible vehicles from parking in a parking space 120, in accordance with some embodiments of the disclosure. In some embodiments, an EVCS 102 may be in communication with a vehicle 104 and/or a user device 108 belonging to a user 106 (e.g., a driver, passenger, owner, renter, or other operator of the vehicle 104) who is associated with the vehicle 104. In some embodiments, the EVCS 102 communicates with one or more devices or computer systems, such as user device 108 or server 110, respectively, via a network 112.

[0021] In the system 100, there can be more than one EVCS 102, vehicle 104, user 106, user device 108, server 110, and network 112, but only one of each is shown in FIG. 1 to avoid overcomplicating the drawing. In addition, a user 106 may utilize more than one type of user device 108 and more than one of each type of user device 108. In some embodiments, there may be paths 114a-d between user devices, EVCSs, servers, and/or vehicles, so that the items may communicate directly with each other via communication paths, as well as other short-range point-to-point communication paths, such as USB cables, IEEE 1394 cables, wireless paths (e.g., Bluetooth, infrared, IEEE 802-1 lx, etc.), or other short-range communication via wired or wireless paths. In an embodiment, the devices may also communicate with each other directly through an indirect path via a communications network. The communications network may be one or more networks including the Internet, a mobile phone network, mobile voice or data network (e.g., a 4G, 5G, or LTE network), cable network, public switched telephone network, or other types of communications networks or combinations of communications networks. In some embodiments, a communication network path comprises one or more communications paths, such as, a satellite path, a fiber-optic path, a cable path, a path that supports Internet communications (e.g., IPTV), free-space connections (e.g., for broadcast or other wireless signals), or any other suitable wired or wireless communications path or combination of such paths. In some embodiments, a communication network path can be a wireless path. Communications with the devices may be provided by one or more communication paths but are shown as single paths in FIG. 1 to avoid overcomplicating the drawing.

[0022] In some embodiments, the EVCS 102 determines whether the vehicle 104 is a compatible vehicle in response to determining that a vehicle (e.g., vehicle 104) has entered a first location (e.g., the parking space 120). In some embodiments, the first location comprises an area larger than the parking space 120 to capture vehicles beginning to park in the parking space 120. For example, the location may comprise an area in front of the parking space 120 that a vehicle may use to back into the parking space 120. To determine if the vehicle 104 has entered the parking space 120, the EVCS 102 can use vehicle information received from one or more sensors. For example, the sensors may be image sensors (e.g., one or more cameras 116), ultrasound sensors, depth sensors, IR cameras, RGB cameras, PIR cameras, thermal IR, proximity sensors, radar, tension sensors, NFC sensors, and/or any combination thereof. In some embodiments, one or more cameras 116 are configured to capture one or more images of an area proximal to the EVCS 102. For example, a camera may be configured to obtain a video or capture images of an area corresponding to the parking space 120 associated with the EVCS 102, a parking space next to the parking space 120 of the EVCS 102, and/or walking paths (e.g., sidewalks) next to the EVCS 102. In some embodiments, the camera 116 may be a wide-angle camera or a 360° camera that is configured to obtain a video or capture images of a large area proximal to the EVCS 102. In some embodiments, the camera 116 may be positioned at different locations on the EVCS 102 than what is shown. In some embodiments, the camera 116 works in conjunction with other sensors. In some embodiments, the one or more sensors (e.g., camera 116) can detect external objects within a region (area) proximal to the EVCS 102.

[0023] In some embodiments, the EVCS 102 uses the vehicle information to determine one or more vehicle characteristics (e.g., model, make, color, license plate number, VIN number, charging status, tire pressure, specifications, condition, etc.) of the vehicle 104. In some embodiments, the EVCS 102 compares a vehicle characteristic with a database of characteristics compatible with the EVCS 102 to determine compatibility. For example, if the vehicle characteristic is a model and the model corresponds to a vehicle 104 that uses an internal combustion engine, the database would indicate that the vehicle 104 is not compatible with the EVCS 102.

[0024] In another example, the EVCS 102 can receive an image of the license plate (i.e., information captured by the one or more sensors) of the vehicle 104 from the camera 116. In some embodiments, the EVCS 102 reads the license plate (e.g., using optical character recognition) and uses the license plate information (i.e., vehicle characteristic) to determine if the vehicle 104 is compatible with the EVCS 102. For example, the EVCS 102 may use a database that comprises entries indicating whether certain license plates correspond to vehicles that are compatible with the EVCS 102. In another example, the EVCS may use a first characteristic (e.g., license plate of the vehicle 104) to determine a second characteristic (e.g., model of the vehicle 104) to determine compatibility. For example, the EVCS 102 may use a database that comprises public records (e.g., public registration information linking license plates to other vehicle characteristics (e.g., make, model, etc.)), collected information (e.g., entries linking license plates to other vehicle characteristics based on data inputted by a user), historic information (entries linking license plates to vehicle characteristics based on the EVCS 102 identifying one or more license plates in the past), and/or similar such information. In some embodiments, using the license plate and the database, the EVCS 102 determines whether the vehicle 104 is compatible with the EVCS 102. [0025] In some embodiments, the EVCS 102 receives a media access control (MAC) address from the vehicle 104, and the EVCS 102 uses the MAC address to determine vehicle characteristics of the vehicle 104 and/or to determine the user 106 associated with the vehicle 104. In some embodiments, the EVCS 102 uses a database to match the received MAC address or portions of the received MAC address to entries in the database to determine vehicle characteristics of the vehicle 104. For example, certain vehicle manufacturers keep portions of their produced vehicle’s MAC addresses consistent. Accordingly, if the EVCS 102 determines that a portion of the MAC address received from the vehicle 104 corresponds to a vehicle manufacturer that makes vehicles compatible with the EVCS 102, the EVCS 102 can determine that the vehicle 104 is compatible. The EVCS 102 can also use a database to match the received MAC address or portions of the received MAC address to entries in the database to determine the user 106 associated with the vehicle 104. For example, the vehicle’s MAC address may correspond to a user profile corresponding to the user 106 associated with the vehicle 104. In some embodiments, the user profile indicates the compatibility of the vehicle 104.

[0026] In some embodiments, the EVCS 102 can use user information to determine the compatibility of the vehicle 104. In some embodiments, the user 106 may have to present some credentials (e.g., password, pin, biometrics, device, item, etc.) when requesting the EVCS 102 to charge their vehicle 104. For example, the user 106 may enter a password on the display 118 of the EVCS 102. In another example, the user 106 may enter a biometric password (e.g., fingerprint) on the user device 108, which is then communicated to the EVCS 102 and/or the server 110 via the network 112. In some embodiments, the credentials may be automatically inputted. For example, the user device 108 may automatically transmit user credentials to the EVCS 102 when the user device 108 is within a threshold distance of the EVCS 102. In some embodiments, the user credentials are associated with a user profile that indicates the compatibility of the vehicle 104 associated with the user 106. In some embodiments, the EVCS 102 can use one or more vehicle characteristics to determine a user profile associated with the vehicle 104.

[0027] In some embodiments, if the EVCS 102 determines that the vehicle 104 is not compatible with the EVCS 102, the EVCS 102 takes one or more actions. In some embodiments, the one or more actions disincentivize the user 106 from using the parking space 120. For example, the EVCS 102 may generate a notification on a display 118 of the EVCS 102 indicating that the vehicle 104 is not authorized to use the parking space 120. In another example, the EVCS 102 may audibly alert passersby (e.g., the user 106 of the incompatible vehicle) that the vehicle 104 is not authorized to use the parking space 120. [0028] In some embodiments, if the EVCS 102 determines that the vehicle 104 is not compatible with the EVCS 102, the EVCS 102 sends a notification (e.g., via the display 118, push notifications on the user device 108, etc.) comprising other parking spaces that are compatible with the vehicle 104. In some embodiments, the EVCS 102 generates the notification by accessing a database of entries associating other parking spaces with vehicle characteristics. For example, the EVCS 102 may determine that the vehicle 104 is an internal combustion engine vehicle and cannot utilize the EVCS 102. In some embodiments, the EVCS 102 can access the database and identify one or more parking spaces available for vehicles with internal combustion engines. In some embodiments, the EVCS 102 displays a location or locations of the identified parking spaces for the vehicle 104 on the display 118. In some embodiments, entries in the database associate parking spaces with more than one vehicle characteristic. For example, the EVCS 102 may determine that the vehicle 104 is a Nissan Leaf, and the EVCS 102 is incompatible with the Nissan Leaf. In some embodiments, the EVCS 102 can access the database and identify one or more parking spaces with access to charging stations that are compatible with the vehicle 104 and/or one more parking spaces available for all vehicles. In some embodiments, the EVCS 102 displays a location or locations for both parking spaces with access to charging stations that are compatible with the vehicle 104 and parking spaces available for all vehicles on the display 118. In some embodiments, the EVCS 102 only displays the location of one or more parking spaces with access to charging stations that are compatible with the vehicle 104. In some embodiments, the EVCS 102 indicates that one or more of the identified parking spaces have compatible charging stations for the vehicle 104 and/or one or more of the identified parking spaces are for all vehicles.

[0029] In some embodiments, if the incompatible vehicle 104 stays in the parking space 120 for more than a first time period (e.g., more than five minutes), the EVCS 102 may transmit a notification to site security and/or a towing company. The notification may comprise vehicle characteristics, location, and/or similar such information. For example, the notification may comprise the license plate number of the vehicle 104 and the location of the EVCS 102. [0030] In some embodiments, the EVCS 102 determines that the compatibility of the vehicle 104 changes. For example, when the vehicle 104 arrives at the parking space 120, the EVCS 102 may determine that the vehicle 104 is a compatible vehicle based on a first vehicle characteristic (e.g., make, model, etc.) of the vehicle 104 corresponding to a vehicle that can charge using the EVCS 102. In some embodiments, the EVCS 102 determines that the vehicle 104 has been located in the parking space 120 for longer than a first time period (e.g., three hours). The EVCS 102 can determine, based on the first vehicle characteristic (e.g., make, model, etc.) and the second vehicle characteristic (e.g., being located in the parking space 120 for longer than the first time period), that the vehicle 104 is no longer compatible. Based on the determination that the vehicle 104 is no longer compatible, the EVCS 102 can take actions to disincentivize the user from continuing to use the parking space 120. The EVCS 102 can use any of the actions mentioned above. In some embodiments, the EVCS 102 sends a notification to a device 108 associated with the user 106 of the vehicle 104 indicating that the vehicle 104 has passed the allocated time limit for charging. The notification may comprise a warning that if the vehicle 104 is not moved then higher charging rates will be enforced, the vehicle 104 will be towed, and/or similar such actions. [0031] FIGS. 2 A and 2B show illustrative diagrams of a system for identifying incompatible vehicles and taking actions to disincentivize the users of the incompatible vehicles from parking in a parking space 210, in accordance with some embodiments of the disclosure. In some embodiments, FIGS. 2A and 2B use the same or similar methods and devices described in connection with FIG. 1.

[0032] In some embodiments, the EVCS 202 uses a first sensor (e.g., proximity sensor) to determine whether an object (e.g., vehicle 204) has entered a first location 210. The first sensor may be an image sensor (e.g., one or more cameras 206), ultrasound sensors, depth sensors, IR cameras, RGB cameras, PIR cameras, thermal IR, proximity sensors, radar, tension sensors, NFC sensors, and/or any combination thereof. In some embodiments, the first sensor determines whether an object is within a threshold distance 208 (e.g., ten feet) of the EVCS 202. In some embodiments, the first sensor is calibrated to detect vehicles. For example, the first sensor may be calibrated to detect objects larger than a size threshold. In another example, the first sensor may be calibrated to detect objects that result in a change of inductance corresponding to the presence of a vehicle.

[0033] In some embodiments, once the first sensor determines that an object has entered the first location 210, the EVCS 202 uses a second sensor (e.g., camera 206) to determine whether the object is a compatible vehicle. In some embodiments, the second sensor detects vehicle information, and the EVCS 202 uses the vehicle information to determine one or more vehicle characteristics (e.g., model) of the vehicle 204. In some embodiments, the EVCS 202 uses a machine learning algorithm to process the vehicle information and determine a vehicle characteristic. In some embodiments, the vehicle information captured by the second sensor is a vehicle characteristic. In some embodiments, the first sensor and the second sensor are the same sensor.

[0034] In some embodiments, the EVCS 202 compares a vehicle characteristic corresponding to the vehicle 204 with a database of characteristics compatible with the EVCS 202 to determine compatibility. For example, if the vehicle characteristic is a model and the model corresponds to a vehicle 204 that uses an internal combustion engine, the database would indicate that the vehicle 204 is not compatible with the EVCS 202. In some embodiments, the EVCS 202 uses user information to determine the compatibility of the vehicle 204. For example, the vehicle 204 and/or a user device associated with the vehicle 204 may automatically transmit user credentials to the EVCS 202 when the vehicle 204 and/or user device is within the threshold distance 208 of the EVCS 202. In some embodiments, the user credentials are associated with a user profile that indicates whether the vehicle 204 is compatible with the EVCS 202. In some embodiments, the user profile indicates vehicle characteristics that the EVCS 202 uses to determine whether the vehicle 204 is compatible with the EVCS 202.

[0035] In some embodiments, if the EVCS 202 determines that the vehicle 204 is not compatible with the EVCS 202, the EVCS 202 takes one or more actions. For example, the EVCS 202 can display a message on the display 212 as the vehicle 204 approaches the EVCS 202. In some embodiments, the message displayed on the display 212 of the EVCS 202 indicates that the vehicle 204 may not park in the first location 210. In another example, the EVCS 202 may audibly alert passersby (e.g., the user of the incompatible vehicle 204) that the vehicle 204 is not authorized to use the first location 210 using a speaker 214.

[0036] In some embodiments, if the EVCS 202 determines that the vehicle 204 is not compatible with the EVCS 202 and is parking in the first location 210, as shown in FIG. 2B, the EVCS 202 takes one or more additional actions. In some embodiments, the one or more additional actions comprise any of the actions previously described. In some embodiments, the one or more additional actions increase in severity over time. For example, a first additional action may be to display a message on the display 212 of the EVCS 202 that indicates that the vehicle 204 may not park in the first location 210, and a second additional action may be to send a message to a towing company requesting towing of the vehicle 204. In another example, a first additional action may be to play an alert using the speaker 214 that indicates that the vehicle 204 may not park in the first location 210, and a second additional action may be to charge an account associated with the vehicle 204 a fee for parking in the first location 210. In some embodiments, the fee is based on how long the vehicle 204 is parked in the first location 210.

[0037] FIGS. 3A and 3B show illustrative diagrams of a system for identifying incompatible vehicles and taking actions to disincentivize the users of the incompatible vehicles 304 from parking in a parking space, in accordance with some embodiments of the disclosure. In some embodiments, FIGS. 3A and 3B use the same or similar methods and devices described in FIGS. 1, 2 A, and 2B.

[0038] In some embodiments, the EVCS 302 uses a first sensor (e.g., camera 306) to determine whether an object (e.g., vehicle 304) has entered a first location 310. In some embodiments, the EVCS 302 uses the same or similar methodologies described above to determine whether an object is within a threshold distance 308 (e.g., ten feet) of the EVCS 302 and to determine whether the object within the threshold distance 308 is a compatible vehicle.

[0039] In some embodiments, if the EVCS 302 determines that the vehicle 304 is compatible with the EVCS 302, the EVCS 302 displays a message on the display 312 as the vehicle 304 approaches the EVCS 302. In some embodiments, the message is displayed once the vehicle 304 parks and/or once the vehicle 304 begins charging. In some embodiments, the message displayed on the display 312 of the EVCS 302 indicates that the vehicle 304 may park in the first location 310.

[0040] In some embodiments, the EVCS 302 determines that the vehicle 304 is no longer compatible with the EVCS 302. In some embodiments, when the vehicle 304 arrives at the EVCS 302, the EVCS 302 determines that the vehicle 304 is a compatible vehicle based on a first vehicle characteristic (e.g., model) of the vehicle 304 corresponding to a vehicle that can charge using the EVCS 302. In some embodiments, the EVCS 302 determines the vehicle 304 is a compatible vehicle once it begins charging using the charging connector 316. The EVCS 302 may then receive a second vehicle characteristic indicating that the vehicle 304 has been charging using the charging connector 316 for longer than a first time period (e.g., three hours). In some embodiments, the EVCS 302 determines, based on the first vehicle characteristic and the second vehicle characteristic, that the vehicle 304 is no longer compatible. Based on the determination that the vehicle 304 is no longer compatible, the EVCS 302 can take actions to disincentivize the user of the vehicle 304 from continuing to park the vehicle 304 in the first location 310 using any of the actions described above. For example, the EVCS 302 may send a push notification to a device associated with the driver of the incompatible vehicle 304 indicating that the vehicle 304 has passed the allocated time limit for charging. In some embodiments, the notification comprises a warning indicating that if the vehicle 304 is not moved then higher charging rates will be charged to the user’s account, the vehicle 304 will be towed, and/or similar such actions. In some embodiments, the EVCS 302 sends notifications to the device warning that the allocated time is running out. For example, the EVCS 302 may send a notification when 15 minutes of allocated time remains, notifying the user that their vehicle 304 can only be parked there for 15 more minutes.

[0041] In some embodiments, when the vehicle 304 arrives at the EVCS 302, the EVCS 302 determines that the vehicle 304 is a compatible vehicle based on a first vehicle characteristic (e.g., model) of the vehicle 304. The EVCS 302 may then receive a second vehicle characteristic indicating that the vehicle 304 did not charge within an expected charging time frame. For example, the EVCS 302 may detect that the charging connector 316 was never connected to the vehicle 304 within 10 minutes of detecting a compatible vehicle. In some embodiments, the EVCS 302 determines, based on the first vehicle characteristic and the second vehicle characteristic, that the vehicle 304 is no longer compatible. Based on the determination that the vehicle 304 is no longer compatible, the EVCS 302 can take actions to disincentivize the user of the vehicle 304 from continuing to park the vehicle 304 in the first location 310 using any of the actions described above. For example, the EVCS 302 may play an alert using a speaker 314 of the EVCS 302 that indicates that the vehicle 304 may not park in the first location 310 without charging.

[0042] FIGS. 4 A and 4B show illustrative diagrams of notifications indicating an incompatible vehicle is parked at an EVCS 402, in accordance with some embodiments of the disclosure.

[0043] FIG. 4A shows an illustrative diagram of an EVCS 402 displaying notifications (414a-c) on a display 410, in accordance with some embodiments of the disclosure. In some embodiments, the EVCS 402 comprises a computer that includes one or more processors and memory. In some embodiments, the memory stores instructions for displaying content on the display 410. In some embodiments, the computer is disposed inside the housing 404. In some embodiments, the computer is mounted on a panel that connects the display 410 to the housing 404.

[0044] In some embodiments, a first notification 414a indicates that a parking space is reserved for charging vehicles. In some embodiments, the EVCS 402 displays the first notification 414a after the EVCS 402 determines that a vehicle is not compatible with the EVCS 402. The EVCS 402 can use one or more sensors to determine whether the vehicle is compatible with the EVCS 402. For example, the EVCS 402 may use a camera 406 to determine a vehicle characteristic of a vehicle and then determine whether the vehicle characteristic is associated with a compatible vehicle. In some embodiments, the EVCS 402 plays an alert using a speaker 412 indicating that the vehicle is incompatible and may not park in the EVCS’s parking space.

[0045] The EVCS 402 may display a second notification 414b indicating that the vehicle may be towed. In some embodiments, the EVCS 402 displays the second notification 414b after a vehicle has parked in the EVCS’s parking space. In some embodiments, the EVCS 402 displays the second notification 414b after a first time period (e.g., five minutes) has expired. For example, the EVCS 402 may display the first notification 414a once the EVCS 402 determines that the vehicle is parking or is parked at the EVCS 402 and is not compatible with the EVCS 402. If the EVCS 402 determines that the vehicle is still parked at the EVCS 402 five minutes after displaying the first notification 414a, the EVCS 402 may display the second notification 414b. In another example, the EVCS 402 may be charging the vehicle using the charging connector 408. The EVCS 402 may display the first notification 414a once the EVCS 402 determines that the vehicle has stopped charging using the EVCS 402 or if the vehicle has been charging longer than an allocated charging time. If the EVCS 402 determines that the vehicle is still parked at the EVCS 402 five minutes after displaying the first notification 414a, the EVCS 402 may display the second notification 414b.

[0046] The EVCS 402 may display a third notification 414c indicating an available parking space for the vehicle. In some embodiments, the third notification 414c is displayed along with the first notification 414a and/or the second notification 414b. In some embodiments, the third notification 414c can be selected by the user. For example, the user can select the third notification 414c and access a map directing the user to an available parking space and/or a parking space region. In some embodiments, the EVCS 402 generates the third notification 414c by accessing a database of entries associating parking spaces with vehicle characteristics. For example, the EVCS 402 may determine that the vehicle is an internal combustion engine vehicle and cannot utilize the EVCS 402. In some embodiments, the EVCS 402 accesses the database and identifies one or more parking spaces available for vehicles with internal combustion engines. In some embodiments, the third notification 414c reflects one or more of the identified parking spaces. In some embodiments, the third notification 414c selects a subset of the identified parking spaces based on one or more criteria. In some embodiments, the criteria include distance, availability, cost, etc. In some embodiments, the entries in the database associate parking spaces with more than one vehicle characteristic. For example, the EVCS 402 may determine that the vehicle parked at the EVCS 402 is a Nissan Leaf, and the EVCS 402 is incompatible with the Nissan Leaf. In some embodiments, the third notification 414c displays one or more parking spaces with access to charging stations compatible with the vehicle and/or one more parking spaces available for all vehicles.

[0047] FIG. 4B shows an illustrative diagram of a user device 416 generating notifications (418a-c), in accordance with some embodiments of the disclosure. Although a smartphone is used in this example, a user device 416 may be any device or devices capable of displaying notifications (418a-c) such as televisions, laptops, tablets, smartphones, and/or similar such devices.

[0048] FIG. 4B shows an embodiment where the user device 416 receives one or more notifications (418a-c). In some embodiments, a first notification 418a indicates that a parking space is reserved for charging vehicles. In some embodiments, an EVCS sends the first notification 418a to the user device 416 after the EVCS determines that a vehicle associated with the user device 416 is not compatible with the EVCS. In some embodiments, the EVCS uses a vehicle characteristic to identify a profile associated with the incompatible vehicle. In some embodiments, the profile associates the user device 416 with the vehicle. In some embodiments, the user of the vehicle creates the profile and inputs information related to the vehicle and the user device 416. In some embodiments, the EVCS identifies the user device 416 when the user device 416 is within a first distance of the EVCS. In some embodiments, the EVCS automatically associates the user device 416 with a vehicle that is also within the first distance. If the EVCS determines that the vehicle associated with the user device 416 is not compatible with the EVCS, the EVCS can send the first notification 418a to the user device 416. In some embodiments, when the user device 416 is within a first distance of the EVCS, the EVCS determines a profile associated with the user device 416. In some embodiments, the EVCS determines the compatibility of a vehicle associated with the user device 416 using the profile. For example, the profile may contain one or more vehicle characteristics that the EVCS can use to determine whether the vehicle is compatible with the EVCS.

[0049] The user device 416 may receive a second notification 418b indicating that a vehicle associated with the user device 416 has exceeded the maximum parking time and that penalty parking rates will begin. In some embodiments, the EVCS sends the second notification 418b after a first time period (e.g., 10 minutes) has expired. For example, the EVCS may send the first notification 418a once the EVCS determines that the vehicle associated with the user device 416 is parking or parked at the EVCS and is not compatible with the EVCS. If the EVCS determines that the vehicle is still parked at the EVCS after five minutes, the EVCS may send the second notification 418b. In another example, the EVCS may send the first notification 418a once the EVCS determines that the vehicle associated with the user device 416 has stopped charging using the EVCS. If the EVCS determines that the vehicle is still parked at the EVCS five minutes after sending the first notification 418a, the EVCS may send the second notification 418b.

[0050] The user device 416 may receive a third notification 418c indicating an available parking space for the vehicle. In some embodiments, the third notification 418c is received along with the first notification 418a and/or the second notification 418b. In some embodiments, the third notification 418c provides a link. For example, the user can select the third notification 418c and launch a map application that directs the user to an available parking space and/or a parking space region. In some embodiments, the EVCS generates the third notification 418c by accessing a database of entries associating parking spaces with vehicle characteristics as described above. In some embodiments, the EVCS accesses the database and identifies one or more parking spaces available for vehicles with internal combustion engines. In some embodiments, the third notification 418c reflects one or more of the identified parking spaces. In some embodiments, the third notification 418c selects a subset of the identified parking spaces based on one or more criteria. In some embodiments, the entries in the database associate parking spaces with more than one vehicle characteristic. In some embodiments, the third notification 418c displays one or more parking spaces with access to charging stations compatible with the vehicle associated with user device 416 and/or one more parking spaces available for all vehicles.

[0051] FIG. 5 shows an illustrative block diagram of an EVCS system 500, in accordance with some embodiments of the disclosure. In particular, EVCS system 500 of FIG. 5 may be the EVCSs depicted in FIGS. 1, 2A, 2B, 3A, 3B, and 4A. In practice, and as recognized by those of ordinary skill in the art, items shown separately could be combined and some items could be separated. In some embodiments, not all shown items must be included in EVCS 500. In some embodiments, EVCS 500 may comprise additional items.

[0052] The EVCS system 500 can include processing circuitry 502 that includes one or more processing units (processors or cores), storage 504, one or more network or other communications network interfaces 506, additional peripherals 508, one or more sensors 510, a motor 512 (configured to retract a portion of a charging cable), one or more wireless transmitters and/or receivers 514, and one or more input/output (hereinafter “VO”) paths 516. I/O paths 516 may use communication buses for interconnecting the described components. I/O paths 516 can include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. EVCS 500 may receive content and data via I/O paths 516. The I/O path 516 may provide data to control circuitry 518, which includes processing circuitry 502 and a storage 504. The control circuitry 518 may be used to send and receive commands, requests, and other suitable data using the I/O path 516. The I/O path 516 may connect the control circuitry 518 (and specifically the processing circuitry 502) to one or more communications paths. I/O functions may be provided by one or more of these communications paths but are shown as a single path in FIG. 5 to avoid overcomplicating the drawing.

[0053] The control circuitry 518 may be based on any suitable processing circuitry such as the processing circuitry 502. As referred to herein, processing circuitry should be understood to mean circuitry based on one or more microprocessors, microcontrollers, digital signal processors, programmable logic devices, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc., and may include a multi-core processor (e.g., dual-core, quad-core, hexa-core, or any suitable number of cores) or supercomputer. In some embodiments, processing circuitry may be distributed across multiple separate processors or processing units, for example, multiple of the same type of processing units (e.g., two Intel Core i7 processors) or multiple different processors (e.g., an Intel Core i5 processor and an Intel Core i7 processor). The identifying of incompatible vehicles and/or taking actions to disincentivize users of the vehicles from parking at a parking space functionality can be at least partially implemented using the control circuitry 518. The identifying of incompatible vehicles and/or taking actions to disincentivize users of the vehicles from parking at a parking space functionality described herein may be implemented in or supported by any suitable software, hardware, or combination thereof. The identifying of incompatible vehicles and/or taking actions to disincentivize users of the vehicles from parking at a parking space functionality can be implemented on user equipment, on remote servers, or across both.

[0054] The control circuitry 518 may include communications circuitry suitable for communicating with one or more servers. The instructions for carrying out the above- mentioned functionality may be stored on the one or more servers. Communications circuitry may include a cable modem, an integrated service digital network (ISDN) modem, a digital subscriber line (DSL) modem, a telephone modem, Ethernet card, or a wireless modem for communications with other equipment, or any other suitable communications circuitry. Such communications may involve the Internet or any other suitable communications networks or paths. In addition, communications circuitry may include circuitry that enables peer-to-peer communication of user equipment devices, or communication of user equipment devices in locations remote from each other (described in more detail below).

[0055] Memory may be an electronic storage device provided as the storage 504 that is part of the control circuitry 518. As referred to herein, the phrase “storage device” or “memory device” should be understood to mean any device for storing electronic data, computer software, or firmware, such as random-access memory, read-only memory, high-speed random-access memory (e.g., DRAM, SRAM, DDR RAM, or other random-access solid- state memory devices), non-volatile memory, one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, other non-volatile solid-state storage devices, quantum storage devices, and/or any combination of the same. In some embodiments, the storage 504 includes one or more storage devices remotely located, such as database of server system that is in communication with EVCS 500. In some embodiments, the storage 504, or alternatively the non-volatile memory devices within the storage 504, includes a non-transitory computer-readable storage medium.

[0056] In some embodiments, storage 504 or the computer-readable storage medium of the storage 504 stores an operating system, which includes procedures for handling various basic system services and for performing hardware dependent tasks. In some embodiments, storage 504 or the computer-readable storage medium of the storage 504 stores a communications module, which is used for connecting EVCS 500 to other computers and devices via the one or more communication network interfaces 506 (wired or wireless), such as the Internet, other wide area networks, local area networks, metropolitan area networks, and so on. In some embodiments, storage 504 or the computer-readable storage medium of the storage 504 stores a media item module for selecting and/or displaying media items on the display(s) 520 to be viewed by passersby and users of EVCS 500. In some embodiments, storage 504 or the computer-readable storage medium of the storage 504 stores an EVCS module for charging an electric vehicle (e.g., measuring how much charge has been delivered to an electric vehicle, commencing charging, ceasing charging, etc.), including a motor control module that includes one or more instructions for energizing or forgoing energizing the motor. In some embodiments, executable modules, applications, or sets of procedures may be stored in one or more of the previously mentioned memory devices and corresponds to a set of instructions for performing a function described above. In some embodiments, modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of modules may be combined or otherwise re-arranged in various implementations. In some embodiments, the storage 504 stores a subset of the modules and data structures identified above. In some embodiments, the storage 504 may store additional modules or data structures not described above.

[0057] In some embodiments, EVCS 500 comprises additional peripherals 508 such as displays 520 for displaying content, and charging cable 522. In some embodiments, the displays 520 may be touch-sensitive displays that are configured to detect various swipe gestures (e.g., continuous gestures in vertical and/or horizontal directions) and/or other gestures (e.g., a single or double tap) or to detect user input via a soft keyboard that is displayed when keyboard entry is needed.

[0058] In some embodiments, EVCS 500 comprises one or more sensors 510 such as cameras (e.g., camera, described above with respect to FIGS. 1, 2A, 2B, 3A, 3B, etc.), ultrasound sensors, depth sensors, IR cameras, RGB cameras, PIR camera, thermal IR, proximity sensors, radar, tension sensors, NFC sensors, and/or any combination thereof. In some embodiments, the one or more sensors 510 are for detecting whether external objects are within a region proximal to EVCS 500, such as living and nonliving objects, and/or the status of EVCS 500 (e.g., available, occupied, etc.) in order to perform an operation, such as determining a vehicle characteristic, user information, region status, etc.

[0059] FIG. 6 shows an illustrative block diagram of a user equipment device system, in accordance with some embodiments of the disclosure. In practice, and as recognized by those of ordinary skill in the art, items shown separately could be combined and some items could be separated. In some embodiments, not all shown items must be included in device 600. In some embodiments, device 600 may comprise additional items. In an embodiment, the user equipment device 600, is the same user equipment device displayed in FIG. 1. The user equipment device 600 may receive content and data via VO path 602. The VO path 602 may provide audio content (e.g., broadcast programming, on-demand programming, Internet content, content available over a local area network (LAN) or wide area network (WAN), and/or other content) and data to control circuitry 604, which includes processing circuitry 606 and a storage 608. The control circuitry 604 may be used to send and receive commands, requests, and other suitable data using the VO path 602. The VO path 602 may connect the control circuitry 604 (and specifically the processing circuitry 606) to one or more communications paths. I/O functions may be provided by one or more of these communications paths but are shown as a single path in FIG. 6 to avoid overcomplicating the drawing. [0060] The control circuitry 604 may be based on any suitable processing circuitry such as the processing circuitry 606. As referred to herein, processing circuitry should be understood to mean circuitry based on one or more microprocessors, microcontrollers, digital signal processors, programmable logic devices, FPGAs, ASICs, etc., and may include a multi-core processor (e.g., dual-core, quad-core, hexa-core, or any suitable number of cores) or supercomputer. In some embodiments, processing circuitry may be distributed across multiple separate processors or processing units, for example, multiple of the same type of processing units (e.g., two Intel Core i7 processors) or multiple different processors (e.g., an Intel Core i5 processor and an Intel Core i7 processor).

[0061] In client-server-based embodiments, the control circuitry 604 may include communications circuitry suitable for communicating with one or more servers that may at least implement the described allocation of services functionality. The instructions for carrying out the above-mentioned functionality may be stored on the one or more servers. Communications circuitry may include a cable modem, an ISDN modem, a DSL modem, a telephone modem, Ethernet card, or a wireless modem for communications with other equipment, or any other suitable communications circuitry. Such communications may involve the Internet or any other suitable communications networks or paths. In addition, communications circuitry may include circuitry that enables peer-to-peer communication of user equipment devices, or communication of user equipment devices in locations remote from each other (described in more detail below).

[0062] Memory may be an electronic storage device provided as the storage 608 that is part of the control circuitry 604. Storage 608 may include random-access memory, read-only memory, hard drives, optical drives, digital video disc (DVD) recorders, compact disc (CD) recorders, BLU-RAY disc (BD) recorders, BLU-RAY 3D disc recorders, digital video recorders (DVR, sometimes called a personal video recorder, or PVR), solid-state devices, quantum storage devices, gaming consoles, gaming media, or any other suitable fixed or removable storage devices, and/or any combination of the same. The storage 608 may be used to store various types of content described herein. Nonvolatile memory may also be used (e.g., to launch a boot-up routine and other instructions). Cloud-based storage may be used to supplement the storage 608 or instead of the storage 608.

[0063] The control circuitry 604 may include audio generating circuitry and tuning circuitry, such as one or more analog tuners, audio generation circuitry, filters or any other suitable tuning or audio circuits or combinations of such circuits. The control circuitry 604 may also include scaler circuitry for upconverting and down converting content into the preferred output format of the user equipment device 600. The control circuitry 604 may also include digital-to-analog converter circuitry and analog-to-digital converter circuitry for converting between digital and analog signals. The tuning and encoding circuitry may be used by the user equipment device 600 to receive and to display, to play, or to record content. The circuitry described herein, including, for example, the tuning, audio generating, encoding, decoding, encrypting, decrypting, scaler, and analog/digital circuitry, may be implemented using software running on one or more general purpose or specialized processors. If the storage 608 is provided as a separate device from the user equipment device 600, the tuning and encoding circuitry (including multiple tuners) may be associated with the storage 608.

[0064] The user may utter instructions to the control circuitry 604 which are received by the microphone 616. The microphone 616 may be any microphone (or microphones) capable of detecting human speech. The microphone 616 is connected to the processing circuitry 606 to transmit detected voice commands and other speech thereto for processing. In some embodiments, voice assistants (e.g., Siri, Alexa, Google Home, and similar such voice assistants) receive and process the voice commands and other speech.

[0065] The user equipment device 600 may optionally include an interface 610. The interface 610 may be any suitable user interface, such as a remote control, mouse, trackball, keypad, keyboard, touch screen, touchpad, stylus inputjoystick, or other user input interfaces. A display 612 may be provided as a stand-alone device or integrated with other elements of the user equipment device 600. For example, the display 612 may be a touchscreen or touch-sensitive display. In such circumstances, the interface 610 may be integrated with or combined with the microphone 616. When the interface 610 is configured with a screen, such a screen may be one or more of a monitor, a television, a liquid crystal display (LCD) for a mobile device, active matrix display, cathode ray tube display, lightemitting diode display, organic light-emitting diode display, quantum dot display, or any other suitable equipment for displaying visual images. In some embodiments, the interface 610 may be HDTV-capable. In some embodiments, the display 612 may be a 3D display. The speaker (or speakers) 614 may be provided as integrated with other elements of user equipment device 600 or may be a stand-alone unit. In some embodiments, the display 612 may be outputted through speaker 614.

[0066] FIG. 7 shows an illustrative block diagram of a server system 700, in accordance with some embodiments of the disclosure. Server system 700 may include one or more computer systems (e.g., computing devices), such as a desktop computer, a laptop computer, and a tablet computer. In some embodiments, the server system 700 is a data server that hosts one or more databases (e.g., databases of images or videos), models, or modules or may provide various executable applications or modules. In practice, and as recognized by those of ordinary skill in the art, items shown separately could be combined and some items could be separated. In some embodiments, not all shown items must be included in server system 700. In some embodiments, server system 700 may comprise additional items.

[0067] The server system 700 can include processing circuitry 702 that includes one or more processing units (processors or cores), storage 704, one or more network or other communications network interfaces 706, and one or more I/O paths 708. I/O paths 708 may use communication buses for interconnecting the described components. I/O paths 708 can include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Server system 700 may receive content and data via I/O paths 708. The I/O path 708 may provide data to control circuitry 710, which includes processing circuitry 702 and a storage 704. The control circuitry 710 may be used to send and receive commands, requests, and other suitable data using the I/O path 708. The I/O path 708 may connect the control circuitry 710 (and specifically the processing circuitry 702) to one or more communications paths. I/O functions may be provided by one or more of these communications paths but are shown as a single path in FIG. 7 to avoid overcomplicating the drawing.

[0068] The control circuitry 710 may be based on any suitable processing circuitry such as the processing circuitry 702. As referred to herein, processing circuitry should be understood to mean circuitry based on one or more microprocessors, microcontrollers, digital signal processors, programmable logic devices, FPGAs, ASICs, etc., and may include a multi-core processor (e.g., dual-core, quad-core, hexa-core, or any suitable number of cores) or supercomputer. In some embodiments, processing circuitry may be distributed across multiple separate processors or processing units, for example, multiple of the same type of processing units (e.g., two Intel Core i7 processors) or multiple different processors (e.g., an Intel Core i5 processor and an Intel Core i7 processor).

[0069] Memory may be an electronic storage device provided as the storage 704 that is part of the control circuitry 710. Storage 704 may include random-access memory, read-only memory, high-speed random-access memory (e.g., DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices), non-volatile memory, one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, other non-volatile solid- state storage devices, quantum storage devices, and/or any combination of the same. [0070] In some embodiments, storage 704 or the computer-readable storage medium of the storage 704 stores an operating system, which includes procedures for handling various basic system services and for performing hardware dependent tasks. In some embodiments, storage 704 or the computer-readable storage medium of the storage 704 stores a communications module, which is used for connecting the server system 700 to other computers and devices via the one or more communication network interfaces 706 (wired or wireless), such as the Internet, other wide area networks, local area networks, metropolitan area networks, and so on. In some embodiments, storage 704 or the computer-readable storage medium of the storage 704 stores a web browser (or other application capable of displaying web pages), which enables a user to communicate over a network with remote computers or devices. In some embodiments, storage 704 or the computer-readable storage medium of the storage 704 stores a database for storing information on electric vehicle charging stations, their locations, media items displayed at respective electric vehicle charging stations, a number of each type of impression count associated with respective electric vehicle charging stations, user profiles, and so forth.

[0071] In some embodiments, executable modules, applications, or sets of procedures may be stored in one or more of the previously mentioned memory devices and corresponds to a set of instructions for performing a function described above. In some embodiments, modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of modules may be combined or otherwise re-arranged in various implementations. In some embodiments, the storage 704 stores a subset of the modules and data structures identified above. In some embodiments, the storage 704 may store additional modules or data structures not described above.

[0072] FIG. 8 is an illustrative flowchart of a process 800 for identifying incompatible vehicles and taking actions to disincentivize the users of the incompatible vehicles from parking in a parking space, in accordance with some embodiments of the disclosure. Process 800 may be performed by physical or virtual control circuitry, such as control circuitry 518 of EVCS 500 (FIG. 5). In some embodiments, some steps of process 800 may be performed by one of several devices (e.g., user device 600, server 700, etc.).

[0073] At step 802, control circuitry detects a vehicle in a location using one or more sensors, wherein the location is associated with an EVCS. In some embodiments, the one or more sensors are coupled to the EVCS. In some embodiments, the sensors may be image (e.g., optical) sensors (e.g., one or more cameras), ultrasound sensors, depth sensors, IR cameras, RGB cameras, PIR cameras, thermal IR, proximity sensors, radar, tension sensors, NFC sensors, and/or any combination thereof. In some embodiments, the location comprises a parking space of an EVCS. In some embodiments, the location comprises an area larger than the parking space. For example, the location may comprise an area in front of the parking space that a vehicle may use to back into the parking space. To determine if a vehicle is in the location, the control circuitry can use information received from the one or more sensors. In some embodiments, the one or more sensors are calibrated to detect vehicles. For example, a first sensor may be calibrated to detect objects larger than a size threshold. In another example, a sensor may be calibrated to detect objects that result in a change of inductance corresponding to the presence of a vehicle.

[0074] At step 804, control circuitry determines a vehicle characteristic related to the vehicle in the location. In some embodiments, the control circuitry uses the information collected from the one or more sensors during step 802 to determine one or more vehicle characteristics (e.g., model, make, color, license plate number, VIN number, charging status, tire pressure, specifications, condition, etc.) of the vehicle. In some embodiments, the control circuitry uses information collected from the one or more sensors after the vehicle was detected. In some embodiments, the sensor that detects the vehicle and the sensor that collects the information for determining the vehicle characteristic are different sensors. In some embodiments, the control circuitry uses a machine learning algorithm to process the information collected by the one or more sensors to determine a vehicle characteristic. For example, the control circuitry may receive an image from a sensor and determine the model of the vehicle captured in the image. In another example, the control circuitry may receive a MAC address corresponding to the vehicle from a sensor and determine the make of the vehicle. In some embodiments, the control circuitry uses user information to determine a vehicle characteristic of the vehicle. For example, the vehicle and/or a user device associated with the vehicle may automatically transmit user credentials to a sensor when the vehicle and/or user device is within a threshold distance of the sensor. In some embodiments, the user credentials are associated with a user profile that indicates a vehicle characteristic.

[0075] At step 806, control circuitry determines whether the vehicle characteristic, determined in step 804, corresponds to a vehicle compatible with the electric vehicle charging station. In some embodiments, the control circuitry compares the vehicle characteristic to a database of characteristics compatible with the EVCS to determine compatibility. For example, if the vehicle characteristic is a model and the model corresponds to a vehicle that uses an internal combustion engine, the database would indicate that the vehicle characteristic is not compatible with the EVCS. In another example, if the vehicle characteristic is a make and the make corresponds to a vehicle that can charge using the EVCS, the database would indicate that the vehicle characteristic is compatible with the EVCS. If the vehicle characteristic corresponds to a compatible vehicle, the process 800 continues to step 810 where the control circuitry charges the vehicle using the EVCS. If the vehicle characteristic does not correspond to a compatible vehicle, the process 800 continues to step 808. In some embodiments, the control circuitry uses more than one vehicle characteristic when determining whether the vehicle is a compatible vehicle. In some embodiments, the control circuitry attributes confidence scores to vehicle characteristics determined in step 804 and uses the confidence scores to weight the vehicle characteristics. In some embodiments, the weighted vehicle characteristics are used to calculate whether the vehicle is a compatible vehicle.

[0076] At step 808, control circuitry transmits a notification indicating that the vehicle is not compatible for charging with the electric vehicle charging station. In some embodiments, this notification is displayed on the EVCS and/or on a user device associated with the vehicle. In some embodiments, the notification is played on a speaker of the EVCS. In some embodiments, the notification is sent to site security and/or a towing company. The notification may comprise vehicle characteristics, location, and/or similar such information. For example, the notification may comprise the license plate number of the vehicle and the location of the EVCS. In some embodiments, the notification includes a location or locations where the vehicle is authorized to park. For example, the control circuitry may access a database and identify one or more parking spaces that are compatible with the vehicle and include the one or more parking spaces along with the notification. In some embodiments, the notification displays directions on how to travel to the location or locations.

[0077] FIG. 9 is another illustrative flowchart of a process 900 for identifying incompatible vehicles and taking actions to disincentivize users of the incompatible vehicles from parking in a parking space, in accordance with some embodiments of the disclosure. Process 900 may be performed by physical or virtual control circuitry, such as control circuitry 518 of EVCS 500 (FIG. 5). In some embodiments, some steps of process 900 may be performed by one of several devices (e.g., user device 600, server 700, etc.).

[0078] At step 902, control circuitry determines whether a vehicle is in a location associated with an EVCS. In some embodiments, the control circuitry uses one or more sensors to determine whether a vehicle is in the location associated with the EVCS. In some embodiments, step 902 uses the same or similar methodologies to do so as described in step 802 above. If the control circuitry determines that a vehicle in the location associated with the EVCS, the process 900 continues to step 904. If the control circuitry determines that a vehicle is not in the location associated with the EVCS, the process 900 ends.

[0079] At step 904, control circuitry receives vehicle information related to the vehicle in the location. In some embodiments, the control circuitry receives the vehicle information from the one or more sensors used in step 902. In some embodiments, the vehicle information is collected after the vehicle is detected. In some embodiments, the control circuitry uses user information to receive vehicle information related to the vehicle from a server. For example, the user of the vehicle may have to present some credentials (e.g., password, pin, biometrics, device, item, etc.) when requesting the EVCS to charge the vehicle. The credentials may be associated with a profile comprising vehicle information associated with the vehicle of the user. In some embodiments, the vehicle and/or a user device associated with the vehicle may automatically transmit user credentials to a sensor when the vehicle and/or user device is within a threshold distance of the sensor. In some embodiments, the user credentials are associated with a user profile that indicates vehicle information. In some embodiments, the control circuitry uses the vehicle information to determine one or more vehicle characteristics. In some embodiments, the control circuitry uses a machine learning algorithm to process the vehicle information to determine a vehicle characteristic. In some embodiments, the vehicle information is a vehicle characteristic. [0080] At step 906, control circuitry determines whether the vehicle is charging using the EVCS. If the control circuitry determines that the vehicle is charging using the EVCS, the process 900 continues to step 908. If the control circuitry determines that the vehicle is not charging using the EVCS, the process 900 continues to step 910. In some embodiments, the control circuitry uses a sensor on the EVCS to determine if the EVCS is charging the vehicle. In some embodiments, the sensor is the same sensor or sensors used in step 902. In some embodiments, the control circuitry determines whether current is flowing from the EVCS to the vehicle to make the determination in step 906. In some embodiments, step 906 occurs after a time frame (e.g., 10 minutes) has passed. For example, the control circuitry may have a grace period allowing the user of the vehicle 10 minutes to begin charging their electric vehicle before the process 900 continues to step 910.

[0081] At step 908, control circuitry determines whether the vehicle has been charging using the EVCS for more than an allocated time period (e.g., three hours). In some embodiments, the allocated time period begins once the EVCS begins charging the vehicle. If the control circuitry determines that the vehicle has been charging using the EVCS for more than the allocated time period, the process 900 continues to step 910. If the control circuitry determines that the vehicle has not been charging using the EVCS for more than the allocated time period, the process 900 returns to step 902.

[0082] At step 910, control circuitry transmits a notification indicating that the vehicle is not compatible with the EVCS. In some embodiments, the notification is transmitted to a user device associated with the vehicle. In some embodiments, the notification is displayed on a display of the EVCS or played through a speaker housed in the EVCS. In some embodiments, the notification comprises a warning that increased charging rates will occur if the vehicle is not moved. In some embodiments, the notification comprises a warning that the vehicle will be towed if the vehicle is not moved. In some embodiments, the notification is sent to site security and/or a towing company. The notification may comprise vehicle characteristics, location, and/or similar such information. In some embodiments, the notification includes a location or locations where the vehicle is permitted to park. For example, the control circuitry may access a database and identify one or more parking spaces that are compatible with the vehicle and include the one or more parking spaces along with the notification. In some embodiments, the notification displays directions on how to travel to the location or locations.

[0083] FIG. 10 is an illustrative flowchart of a process 1000 for flagging images for training a machine learning algorithm, in accordance with some embodiments of the disclosure. Process 1000 may be performed by physical or virtual control circuitry, such as control circuitry 518 of EVCS 500 (FIG. 5). In some embodiments, some steps of process 1000 may be performed by one of several devices (e.g., user device 600, server 700, etc.). [0084] At step 1002, control circuitry detects a vehicle in a location corresponding to an EVCS using one or more sensors. In some embodiments, step 1002 uses the same or similar methodologies to do so as described in step 802 above. In some embodiments, the control circuitry also collects vehicle information and/or determines a vehicle characteristic related to the vehicle in the location.

[0085] At step 1004, control circuitry determines whether the vehicle is charging using the electric vehicle charging station. If the control circuitry determines that the vehicle is charging using the EVCS, the process 1000 continues to step 1006. If the control circuitry determines that the vehicle is not charging using the EVCS the process 1000 continues to step 1008. In some embodiments, the control circuitry uses a sensor on the EVCS to determine if the EVCS is charging the vehicle. In some embodiments, the sensor is the same sensor or sensors used in step 1002. In some embodiments, the control circuitry determines whether current is flowing from the EVCS to the vehicle to make the determination in step 1004. In some embodiments, step 1004 occurs after a time frame (e.g., 10 minutes) has passed.

[0086] At step 1006, control circuitry receives a first plurality of images of the vehicle during a first time period. In some embodiments, the first plurality of images of the vehicle is captured using a sensor coupled to the EVCS. In some embodiments, the first plurality of images comprises images of the vehicle from different angles. For example, the first plurality of images may be taken using different cameras. In some embodiments, the first time period begins once the vehicle begins charging using the EVCS. In some embodiments, the first time period begins once the vehicle is detected in step 1002. In some embodiments, the first time period spans the length of time that the vehicle charges using the EVCS. In some embodiments, the first time period is only a few seconds (e.g., five seconds). In some embodiments, the first time period continues until one or more acceptable images are captured. For example, after a first image is captured, the control circuitry may determine (e.g., using image recognition software) whether the quality of the one or more images exceeds a threshold. If the image quality does not exceed the threshold, the first time period may continue until one or more images with quality exceeding the threshold are captured. In some embodiments, the control circuitry flags the first plurality of images with a first identifier indicating that the first plurality of images comprises a compatible vehicle.

[0087] At step 1008, control circuitry receives a second plurality of images of the vehicle during a second time period. In some embodiments, the second plurality of images of the vehicle is captured using a sensor coupled to the EVCS. In some embodiments, the second plurality of images comprises images of the vehicle from different angles. In some embodiments, the second time period begins after the control circuitry determines in step 1004 that the vehicle is not charging using the EVCS. In some embodiments, the second time period begins once the vehicle is detected in step 1002. In some embodiments, the second time period spans the length of time that the vehicle is in the location corresponding to the EVCS. In some embodiments, the second time period is only a few seconds (e.g., five seconds). In some embodiments, the second time period continues until one or more acceptable images are captured. For example, after a first image is captured, the control circuitry may determine (e.g., using image recognition software) whether the quality of image exceeds a threshold. If the quality of image does not exceed the threshold, the second time period may continue until one or more images exceeding the threshold are captured. In some embodiments, the control circuitry flags the second plurality of images with a second identifier indicating that the second plurality of images comprises an incompatible vehicle. [0088] At step 1010, control circuitry trains a machine learning algorithm using the received images. For example, the control circuitry may use the first plurality of images to train the machine learning algorithm to identify vehicles that are compatible with the EVCS. In another example, the control circuitry may use the second plurality of images to train the machine learning algorithm to identify vehicles that are incompatible with the EVCS. In some embodiments, the first and second plurality of images can be used in conjunction with other information determined by the EVCS (e.g., vehicle information and/or vehicle characteristics collected in step 1002) to increase the efficiency of the training of the machine learning process. For example, when the vehicle begins charging, the control circuitry receives the first plurality of images. The control circuitry may also receive the make and model (i.e., vehicle characteristics) of the vehicle using ISO 15118 when the vehicle begins charging. The control circuitry can pair the vehicle characteristic information (e.g., make and model) with the first plurality of images to generate training data for the machine learning algorithm. The generated training data comprises images of a compatible vehicle and the make and model of the compatible vehicle, allowing the machine learning algorithm to associate the make and model with compatible vehicles. In another example, when the vehicle is detected in the first location and does not begin charging, the control circuitry can receive the second plurality of images. The control circuitry may receive the make and model of the vehicle using user information. For example, the control circuitry may detect a user device associated with a profile that comprises the make and model of the vehicle. The control circuitry can pair the vehicle characteristic information (e.g., make and model) with the second plurality of images to generate training data for the machine learning algorithm. The generated training data comprises images of the incompatible vehicle and the make and model of the incompatible vehicle, allowing the machine learning algorithm to associate the make and model of the vehicle with incompatible vehicles.

[0089] It is contemplated that some suitable steps or suitable descriptions of FIGS. 8-10 may be used with other suitable embodiments of this disclosure. In addition, some suitable steps and descriptions described in relation to FIGS. 8-10 may be implemented in alternative orders or in parallel to further the purposes of this disclosure. For example, some suitable steps may be performed in any order or in parallel or substantially simultaneously to reduce lag or increase the speed of the system or method. Some suitable steps may also be skipped or omitted from the process. Furthermore, it should be noted that some suitable devices or equipment discussed in relation to FIGS. 1-7 could be used to perform one or more of the steps in FIGS. 8-10. [0090] The processes discussed above are intended to be illustrative and not limiting. One skilled in the art would appreciate that the steps of the processes discussed herein may be omitted, modified, combined, and/or rearranged, and any additional steps may be performed without departing from the scope of the invention. More generally, the above disclosure is meant to be exemplary and not limiting. Only the claims that follow are meant to set bounds as to what the present invention includes. Furthermore, it should be noted that the features and limitations described in any one embodiment may be applied to any other embodiment herein, and flowcharts or examples relating to one embodiment may be combined with any other embodiment in a suitable manner, done in different orders, or done in parallel. In addition, the systems and methods described herein may be performed in real time. It should also be noted that the systems and/or methods described above may be applied to, or used in accordance with, other systems and/or methods.

This specification discloses embodiments which include, but are not limited to, the following:

1. A non-transitory computer-readable medium having instructions encoded thereon that when executed by control circuitry causes the control circuitry to: detect a vehicle in a location corresponding to an electric vehicle charging station using a first sensor of the electric vehicle charging station; determine a vehicle characteristic related to the vehicle in the location using information collected by a second sensor of the electric vehicle charging station; determine that the vehicle in the location is not compatible for charging with the electric vehicle charging station using the vehicle characteristic; and transmit a notification indicating that the vehicle in the location is not compatible for charging with the electric vehicle charging station in response to determining that the vehicle in the location is not compatible for charging with the electric vehicle charging station.

2. The non-transitory computer-readable medium of item 1, wherein the notification is transmitted to a towing company. 3. The non-transitory computer-readable medium of item 1, wherein the notification is transmitted to a user device associated with the vehicle.

4. The non-transitory computer-readable medium of item 1, wherein the control circuitry is further caused to display the notification on a display of the electric vehicle charging station.

5. The non-transitory computer-readable medium of item 1, wherein the control circuitry is further caused to generate an audible alert corresponding to the notification using a speaker of the electric vehicle charging station.

6. The non-transitory computer-readable medium of item 1, wherein the vehicle characteristic corresponds to the make or model of the vehicle.

7. The non-transitory computer-readable medium of item 1, wherein the control circuitry is further caused to determine a second electric vehicle charging station that is compatible with the vehicle using the vehicle characteristic and include the location of the second electric vehicle charging station with the transmitted notification.

8. A method comprising: detecting, by an electric vehicle charging station, a vehicle in a location corresponding to the electric vehicle charging station; receiving, by the electric vehicle charging station, vehicle information related to the vehicle in the location; determining, by the electric vehicle charging station, that the electric vehicle charging station is not charging the vehicle in the location for more than a first time period, wherein the determination is made using the vehicle information; receiving, by the electric vehicle charging station, a plurality of images from one or more sensors during the first time period; in response to determining that the electric vehicle charging station is not charging the vehicle in the location for more than a first time period, flagging, by the electric vehicle charging station, the plurality of images received during the first time period; and training a machine learning algorithm using the flagged images. 9. The method of item 8, further comprising: determining, by the electric vehicle charging station, a characteristic of the vehicle using the vehicle information; and including, by the electric vehicle charging station, the characteristic of the vehicle with the flagged images.

10. The method of item 9, wherein the machine learning algorithm is trained using the flagged images and the characteristic of the vehicle.

11. The method of item 9, wherein the characteristic of the vehicle corresponds to the model of the vehicle.

12. An apparatus comprising: control circuitry; and at least one memory including computer program code for one or more programs, the at least one memory and the computer program code configured to, with the control circuitry, cause the apparatus to perform at least the following: detect a vehicle in a location corresponding to an electric vehicle charging station; receive vehicle information related to the vehicle in the location; determine that the electric vehicle charging station is not charging the vehicle in the location for more than a first time period, wherein the determination is made using the vehicle information; receive a plurality of images from one or more sensors during the first time period; flag the plurality of images received during the first time period in response to determining that the electric vehicle charging station is not charging the vehicle in the location for more than a first time period,; and train a machine learning algorithm using the flagged images.

13. The apparatus of item 12, wherein the apparatus is further caused to: determine a characteristic of the vehicle using the vehicle information; and include the characteristic of the vehicle with the flagged images. 14. The apparatus of item 13 wherein the machine learning algorithm is trained using the flagged images and the characteristic of the vehicle.

15. The apparatus of item 13, wherein the characteristic of the vehicle corresponds to the model of the vehicle.

16. A non-transitory computer-readable medium having instructions encoded thereon that when executed by control circuitry causes the control circuitry to: detect a vehicle in a location corresponding to an electric vehicle charging station; receive vehicle information related to the vehicle in the location; determine that the electric vehicle charging station is not charging the vehicle in the location for more than a first time period, wherein the determination is made using the vehicle information; receive a plurality of images from one or more sensors during the first time period; flag the plurality of images received during the first time period in response to determining that the electric vehicle charging station is not charging the vehicle in the location for more than a first time period,; and train a machine learning algorithm using the flagged images.

17. The non-transitory computer-readable medium of item 16, wherein the control circuitry is further caused to: determine a characteristic of the vehicle using the vehicle information; and include the characteristic of the vehicle with the flagged images.

18. The non-transitory computer-readable medium of item 17, wherein the machine learning algorithm is trained using the flagged images and the characteristic of the vehicle.

19. The non-transitory computer-readable medium of item 17, wherein the characteristic of the vehicle corresponds to the model of the vehicle.

20. A method comprising: detecting, by an electric vehicle charging station, a vehicle in a location corresponding to the electric vehicle charging station; receiving, by the electric vehicle charging station, vehicle information related to the vehicle in the location using a sensor of the electric vehicle charging station; determining, by the electric vehicle charging station, that the vehicle in the location is not charging using the electric vehicle charging station for more than a first time period, wherein the determination is made using the vehicle information; and in response to determining that the vehicle in the location is not charging using the electric vehicle charging station for more than the first time period, transmitting, by the electric vehicle charging station, a notification indicating that the vehicle in the location is not charging using the electric vehicle charging station for more than the first time period.

21. An apparatus comprising: control circuitry; and at least one memory including computer program code for one or more programs, the at least one memory and the computer program code configured to, with the control circuitry, cause the apparatus to perform at least the following: detect a vehicle in a location corresponding to an electric vehicle charging station; receive vehicle information related to the vehicle in the location using a sensor of the electric vehicle charging station; determine that the vehicle in the location is not charging using the electric vehicle charging station for more than a first time period, wherein the determination is made using the vehicle information; and transmit a notification indicating that the vehicle in the location is not charging using the electric vehicle charging station for more than the first time period in response to determining that the vehicle in the location is not charging using the electric vehicle charging station for more than the first time period.

22. A non-transitory computer-readable medium having instructions encoded thereon that when executed by control circuitry causes the control circuitry to: detect a vehicle in a location corresponding to an electric vehicle charging station; receive vehicle information related to the vehicle in the location using a sensor of the electric vehicle charging station; determine that the vehicle in the location is not charging using the electric vehicle charging station for more than a first time period, wherein the determination is made using the vehicle information; and transmit a notification indicating that the vehicle in the location is not charging using the electric vehicle charging station for more than the first time period in response to determining that the vehicle in the location is not charging using the electric vehicle charging station for more than the first time period.

Claims

What is claimed is:

1. A method comprising: detecting, by an electric vehicle charging station, a vehicle in a location corresponding to the electric vehicle charging station using a first sensor of the electric vehicle charging station; determining, by the electric vehicle charging station, a vehicle characteristic related to the vehicle in the location using information collected by a second sensor of the electric vehicle charging station; determining, by the electric vehicle charging station, that the vehicle in the location is not compatible for charging with the electric vehicle charging station using the vehicle characteristic; and in response to determining that the vehicle in the location is not compatible for charging with the electric vehicle charging station, transmitting, by the electric vehicle charging station, a notification indicating that the vehicle in the location is not compatible for charging with the electric vehicle charging station.

2. The method of claim 1, wherein the notification is transmitted to a towing company.

3. The method of claim 1, wherein the notification is transmitted to a user device associated with the vehicle.

4. The method of claim 1, further comprising, displaying, by the electric vehicle charging station, the notification on a display of the electric vehicle charging station.

5. The method of claim 1, further comprising, generating, by the electric vehicle charging station, an audible alert corresponding to the notification using a speaker of the electric vehicle charging station.

6. The method of claim 1, wherein the vehicle characteristic corresponds to the make or model of the vehicle.

7. The method of claim 1, further comprising determining, by the electric vehicle charging station, a second electric vehicle charging station that is compatible with the vehicle using the vehicle characteristic and including the location of the second electric vehicle charging station with the transmitted notification.

8. An apparatus comprising: control circuitry; and at least one memory including computer program code for one or more programs, the at least one memory and the computer program code configured to, with the control circuitry, cause the apparatus to perform at least the following: detect a vehicle in a location corresponding to an electric vehicle charging station using a first sensor of the electric vehicle charging station; determine a vehicle characteristic related to the vehicle in the location using information collected by a second sensor of the electric vehicle charging station; determine that the vehicle in the location is not compatible for charging with the electric vehicle charging station using the vehicle characteristic; and transmit a notification indicating that the vehicle in the location is not compatible for charging with the electric vehicle charging station in response to determining that the vehicle in the location is not compatible for charging with the electric vehicle charging station.

9. The apparatus of claim 8, wherein the notification is transmitted to a towing company.

10. The apparatus of claim 8, wherein the notification is transmitted to a user device associated with the vehicle.

11. The apparatus of claim 8, wherein the apparatus is further caused to display the notification on a display of the electric vehicle charging station.

12. The apparatus of claim 8, wherein the apparatus is further caused to generate an audible alert corresponding to the notification using a speaker of the electric vehicle charging station.

13. The apparatus of claim 8, wherein the vehicle characteristic corresponds to the make or model of the vehicle.

14. The apparatus of claim 8, wherein the apparatus is further caused to determine a second electric vehicle charging station that is compatible with the vehicle using the vehicle characteristic and include the location of the second electric vehicle charging station with the transmitted notification.