WO2017135944A1

WO2017135944A1 - System and method for wireless communication using a parked vehicle

Info

Publication number: WO2017135944A1
Application number: PCT/US2016/016428
Authority: WO
Inventors: Mohannad Hakeem; Hafiz Shafeek KHAFAGY; Steven Joseph Szwabowski; Michael Mcquillen; Khaled ALMAHSHI
Original assignee: Ford Global Technologies, Llc
Priority date: 2016-02-03
Filing date: 2016-02-03
Publication date: 2017-08-10

Abstract

Embodiments provide a wireless system, comprising a communication device associated with a vehicle operator; a third-party device configured to send an anonymous message for the vehicle operator; and a vehicle infrastructure configured to receive the anonymous message from the third-party device and relay the message to the communication device using a pre-established routine for communicating with the vehicle operator. Embodiments also include devices and methods for establishing anonymous communication with a vehicle operator, by prompting, via a user interface, entry of physical characteristic data for a vehicle charging card; identifying, using a processor, an infrastructure provider based on the physical characteristic data; and transmitting, using a wireless unit, an identifier of the vehicle charging card and a user-generated message, to a charging infrastructure associated with the provider, for relay to a vehicle operator associated with the identifier.

Description

SYSTEM AND METHOD FOR WIRELESS COMMUNICATION

USING A PARKED VEHICLE

TECHNICAL FIELD

[0001] This application generally relates to wireless communication and more specifically, to wireless communication using a parked vehicle.

BACKGROUND

[0002] Plug-in hybrid electric vehicles (PHEV) and other electric vehicles (EV) include rechargeable batteries, or other energy storage device, that can be recharged by connecting a vehicle plug to an external power source, such as, for example, a home wall socket, electrical vehicle charging points or stations at residential and public locations, or other connections to the electrical grid. While public charging stations provide convenience and accessibility, the public nature of these stations and, in most areas, the shortage of charging spaces, have given rise to a need for communication between EV operators, and in some cases, between EV operators and non-EV operators.

[0003] For example, a passerby might, knowingly or unknowingly, unplug a charging vehicle from the charging station, thus leaving the EV operator to discover a partially charged vehicle upon returning to his vehicle. Another passerby may have witnessed this occurrence but has no way of contacting the EV operator to inform him of the incident and/or ask him for permission to re-plug the vehicle.

[0004] In other cases, an EV operator may want a passerby to unplug his vehicle for example, once it is done charging to free up the plug for others or avoid paying extra fees. For example, a charging station may offer up to four hours of free charging time, but the electric PATENT vehicle may require only two hours to fully charge the battery. In such cases, other than leaving a hand-written note on his vehicle, the EV operator has no way of requesting this help from passersby.

[0005] As another example, in areas where charging spaces are highly coveted entities, EV operators can become discontent when a non-electric vehicle occupies one of the few "EV-only" parking spaces. However, EV operators currently have no avenue for contacting the non-EV operator to express his discontent and/or request the other operator to move his vehicle to a regular parking space, except, of course, to leave a hand-written note on the parked vehicle.

[0006] While the "hand-written note" method of communication may not be effective for situations that require immediate attention, it has the benefit of maintaining the privacy of both the writer and the recipient. This anonymity can help avoid potentially embarrassing situations, particularly when tensions are high. Further, unlike face-to-face confrontations, the note recipient can easily ignore the note and/or is not forced to take action.

[0007] Accordingly, there is still a need in the art for a communication tool that enables EV operators to communicate with other vehicle operators, including EV operators and non-EV operators, in order to resolve disputes, pass messages, or share other information in parking situations, but also preserves the privacy of both parties to the communication, particularly the non-initiating party.

SUMMARY

[0008] The invention is intended to solve the above-noted and other problems by providing systems and methods for, among other things, establishing an anonymous communication channel between an electric vehicle operator and a second vehicle operator associated with a PATENT parked vehicle, wherein a communication routine is previously established between the second vehicle operator and the parked vehicle or infrastructure associated with the parked vehicle, and the anonymous communication channel is established by using a mobile device of the electric vehicle operator to send a message to the parked vehicle or the infrastructure for relay to the second vehicle owner.

[0009] For example, one embodiment provides a wireless system, comprising a

communication device associated with a vehicle operator; a third-party device configured to send an anonymous message for the vehicle operator; and a vehicle infrastructure configured to receive the anonymous message from the third-party device and relay the message to the communication device using a pre-established routine for communicating with the vehicle operator.

[00010] Another example embodiment provides a method for establishing anonymous communication with a vehicle operator, the method comprising prompting, via a user interface, entry of physical characteristic data for a vehicle charging card; identifying, using a processor, an infrastructure provider based on the physical characteristic data; and transmitting, using a wireless unit, an identifier of the vehicle charging card and a user-generated message, to a charging infrastructure associated with the provider, for relay to a vehicle operator associated with the identifier.

[00011] Yet another example embodiment provides a computing device, comprising a user interface configured to receive a user-generated message and to prompt entry of physical characteristic data for a charging card of a vehicle; and a processor configured to: identify an infrastructure provider based on received physical characteristic data, and transmit the user- PATENT generated message and an identifier of the charging card to a charging infrastructure associated with the provider for relay to a vehicle operator associated with the identifier.

[00012] As will be appreciated, this disclosure is defined by the appended claims. The description summarizes aspects of the embodiments and should not be used to limit the claims. Other implementations are contemplated in accordance with the techniques described herein, as will be apparent to one having ordinary skill in the art upon examination of the following drawings and detail description, and such implementations are intended to within the scope of this application.

BRIEF DESCRIPTION OF THE DRAWINGS

[00013] For a better understanding of the invention, reference may be made to embodiments shown in the following drawings. The components in the drawings are not necessarily to scale and related elements may be omitted, or in some instances proportions may have been exaggerated, so as to emphasize and clearly illustrate the novel features described herein. In addition, system components can be variously arranged, as known in the art. Further, in the drawings, like reference numerals designate corresponding parts throughout the several views.

[00014] FIG. 1 is an illustration of an example environment for establishing anonymous communication between an electric vehicle operator and an operator of a parked vehicle, in accordance with certain embodiments.

[00015] FIGS. 2A and 2B are example charge cards that may be present in the environment shown in FIG. 1, in accordance with certain embodiments.

[00016] FIG. 3 is a block diagram of an example computing device included in a mobile device of the environment shown in FIG. 1, in accordance with certain embodiments. PATENT

[00017] FIG. 4 is a block diagram of an example computing device included in a charging station of the environment shown in FIG. 1, in accordance with certain embodiments.

[00018] FIG. 5 is a block diagram of an example vehicle computing system included in a parked vehicle of the environment shown in FIG. 1, in accordance with certain embodiments.

[00019] FIG. 6 is a flow diagram of an example method for establishing anonymous communication with an operator of a parked vehicle, in accordance with certain embodiments.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

[00020] While the invention may be embodied in various forms, there are shown in the drawings, and will hereinafter be described, some exemplary and non-limiting embodiments, with the understanding that the present disclosure is to be considered an exemplification of the invention and is not intended to limit the invention to the specific embodiments illustrated.

[00021] In this application, the use of the disjunctive is intended to include the conjunctive. The use of definite or indefinite articles is not intended to indicate cardinality. In particular, a reference to "the" object or "a" and "an" object is intended to denote also one of a possible plurality of such objects.

[00022] FIG. 1 illustrates an example environment 100 for establishing anonymous communication between a first operator 102 of an electric vehicle 104 and a second operator 106 of another vehicle 108 that is parked in a charging space 110, in accordance with embodiments. The electric vehicle 104 can be a plug-in hybrid electric vehicle (PHEV), plug-in electric vehicle, or any other type of vehicle that utilizes charging equipment to re-charge a battery of the vehicle. The other vehicle 108 (also referred to herein as "parked vehicle 108") can be any type of vehicle, including an electric vehicle (e.g., like the electric vehicle 104), a non-electric vehicle PATENT

(e.g., a gasoline-powered vehicle), or a non-electric vehicle carrying a high voltage, rechargeable battery for secondary use.

[00023] The charging space 110 can be a parking location that is designated for plug-in electric vehicles and is adjacent to an electric vehicle (EV) charging infrastructure or station 112. As an example, the charging space 110 can be an on-street parking location or a parking space in a public or commercial parking lot (e.g., at a shopping center, airport, hotel, place of employment, etc.). The EV charging station 112 (also referred to herein as a "charging infrastructure") can include equipment for supplying electric energy to an electric vehicle. In some cases, the parked vehicle 108 is a non-electric vehicle that is occupying the charging spot 110. In other cases, the parked vehicle 108 is an electric vehicle that is plugged into, or otherwise utilizing, the EV charging station 112, or is capable of utilizing the station 112 to charge a rechargeable battery (not shown) of the vehicle 108 but is currently unplugged from the station 112.

[00024] Various scenarios may arise in the environment 100 that create a need for communication between the EV operator 102 and the parked vehicle operator 106. For example, the EV operator 102 may want to park in the charging space 110, or otherwise use the charging station 112 but cannot do so because of the parked vehicle 108. If the parked vehicle 108 is an electric vehicle plugged into the charging station 112, the EV operator 102 may want to contact the parked vehicle operator 106 to ask for permission to unplug the parked vehicle 108 and plug- in the electric vehicle 104, or to find out how long the parked vehicle 108 will remain in the space 110. If the parked vehicle 108 is not an electric vehicle, the EV operator 102 may want to ask the parked vehicle operator 106 to move the parked vehicle 108 out of the charging space 110, or otherwise express his discontent for the improper use of the space 110. In either situation, PATENT however, the EV operator 102 typically does not have a way to contact the parked vehicle operator 106 because the operator 106 is unknown to him (e.g., he does not have the contact information of, or know anything else about, the operator 106), except for the parked vehicle 108 before him.

[00025] The systems and methods disclosed herein can use the parked vehicle 108 to provide a communication tool for contacting the parked vehicle operator 106 by capitalizing on a pre- established communication routine between (1) the parked vehicle 108 and the parked vehicle operator 106, or (2) the charging station 112 and the parked vehicle operator 106, where the charging station 112 can identify the parked vehicle operator 106 based on an identification tag of the parked vehicle 108. In embodiments, the communication tool is configured to automatically select one of the two devices (e.g., the parked vehicle 108 or the charging station 112) for contacting the operator 106 based on availability. Moreover, the communication tool is designed to provide anonymity to both parties of the communication by ensuring that the contact information (e.g., name, email address, phone number, etc.) for each operator 102, 106 is not shared. In particular, the communication tool can enable the EV operator 102 to generate a realtime (or near real-time) message to the parked vehicle operator 106 and send the user-generated message to either the parked vehicle 108 or the charging station 112 with an instruction to relay the message to the parked vehicle operator 106. The receiving device (e.g., the vehicle 108 or station 112) can relay the user-generated message to the parked vehicle operator 106 using the pre-established communication routine. This relay technique of the communication tool ensures a wall of privacy between the two unknown parties, while still enabling real-time communication using previously established channels. The following paragraphs describe the components of the PATENT environment 100 that facilitate these and other embodiments of the communication tool and a process (e.g., method 600 in FIG. 6) for implementing the communication tool.

[00026] Referring back to FIG. 1, the charging station 112 can be part of a charging network comprised of a plurality of charging stations (not shown) placed at various locations and owned and/or operated by a charging infrastructure provider 114. In some cases, the charging infrastructure provider 114 is a commercial entity, such as, for example, a private charging infrastructure provider or an electric vehicle manufacturer. In other cases, the charging infrastructure provider 114 is a government entity, such as, for example, a public charging infrastructure provider. In embodiments, the charging infrastructure provider 114 can require an electric vehicle operator to create an account or subscribe to a charging service in order to plug into, receive electric energy from, or otherwise access, the charging station 112. In some embodiments, the electric vehicle operator (e.g., operator 106) can log into the pre-established account use a charging application on a mobile device (e.g., communication device 120) or an interface of the charging station 112.

[00027] In other embodiments, an identification (ID) tag 116 can be placed on the electric vehicle 108 to identify the vehicle as a subscriber or member qualified to use the charging station 112. The ID tag 116 can include identification information, or an identification number, that pairs the vehicle 108 to a payment account or membership with the specific provider 116 of the charging station 112. In some cases, the identification information is embedded in an optically- readable code, such as, for example, a barcode or a QR code. In other cases, the identification information is embedded in an electronic tag, such as, for example, a radio-frequency identification (RFID) tag, a Near Field Communication (NFC) tag, or the like. PATENT

[00028] In embodiments, the environment 100 can include multiple charging infrastructure providers (not shown) and a different set of charging stations (not shown) associated with each provider. In such embodiments, each provider may require use of a unique ID tag 116, or charging card, that is designed to provide access to only the charging stations associated with that provider. In addition, the charging cards for each provider may include unique physical characteristics that help differentiate their cards from other provider's charging cards. For example, in the illustrated embodiment, the ID tag 116 can be included in a charging card that is configured for use with the charging station 112, and any others managed by the charging infrastructure provider 114, and can have differentiating physical characteristics that represent, or otherwise indicate, the provider 114 as being the manufacturer of the charging card. The physical characteristics can include, for example, size, shape, color(s), logo(s), design(s), pattern(s), and any other discernible features or traits of the charging card.

[00029] To illustrate, FIGS. 2 A and 2B show two example charging cards for use with the charging stations of two different charging infrastructure providers. FIG. 2A depicts a rectangular-shaped charging card 200 comprising an ID tag 202 (e.g., similar to the ID tag 1 16), a star-shaped design 204 in a center of the card 200, and a text-based logo 206 positioned within the star-shaped design 204. FIG. 2B depicts a square-shaped charging card 210 comprising an ID tag 212 (e.g., similar to the ID tag 116), a striped background or design 214, and a cloud-shaped logo 216 super-imposed on the background 214. In embodiments, these physical characteristics of the charging cards 200 and 210 can be used to automatically identify the associated charging infrastructure provider, for example, as described with respect to FIG. 6.

[00030] In embodiments, the physical characteristics of each type of charging card can be stored in a database (e.g., infrastructure provider database 307 in FIG. 3) in association with the PATENT name of the corresponding charging infrastructure provider. And the database can be used by the communication tool to identify the charging infrastructure provider based on the physical characteristics of the charging card in a reverse look-up process. For example, the communication tool can prompt the EV operator 102 to input the physical characteristics of the ID tag 116 (e.g., by capturing an image of the tag 116) and upon comparing the received information to the database, can determine that the ID tag 116 is associated with the charging infrastructure provider 114. The communication tool can then send identifying information obtained from the ID tag 116 and the user-generated message to the identified charging infrastructure provider 114, and/or the charging station 112 associated therewith, for relay of the message to the parked vehicle operator 106 using a pre-established communication routine, as described in more detail herein.

[00031] While the environment 100 shown in FIG. 1 depicts only the charging station 112 and the infrastructure provider 114 associated therewith, it will be appreciated that the environment 100 can also include multiple charging stations that are associated with two or more different charging infrastructure providers. In such cases, the communication tool can select which charging station to contact based on the infrastructure provider identified according to the physical characteristic data of the charging card.

[00032] In embodiments, certain components of the environment 100 can be communicatively coupled by a wireless network 118 to form a wireless system 119 for facilitating anonymous communication between the EV operator 102 and the parked vehicle operator 106. The wireless network 118 can include one or more different types of wireless communication networks, including, for example, internet access networks (such as, e.g., Wi-Fi, WLAN, WMAN, WW AN, etc.), wireless personal area networks (WPANs) (such as, e.g., Bluetooth, Zigbee, PATENT infrared, etc.), digital cellular networks (such as, e.g., LTE, LTE- Advanced, GSM, CDMA, GPRS, 3G, etc.), satellite networks, and short-range communication networks (such as, e.g., dedicated short-range communication (DSRC), radio frequency identification (RFID), near field communication (NFC), etc.). In some cases, two or more different types of wireless communication technology may be used to implement the wireless system 119. For example, a first communication network may be used for communication between the charging station 112 and the vehicle 108 and a second communication network may be used for communication between the vehicle 108 and the operator 106.

[00033] As shown in FIG. 1, the parked vehicle operator 106 can be associated with a communication device 120 included in the wireless system 119. The communication device 120 can be any type of electronic computing device, such as, for example, a mobile communications device (e.g., smartphone, tablet, etc.) or a personal computing device (e.g., laptop, PC, etc.). In embodiments, the communication device 120 includes a computing device (such as, e.g., computing device 300 in FIG. 3) comprising a wireless communication module (e.g., wireless communication module 316 in FIG. 3) that is configured to communicate with the wireless network 118.

[00034] In embodiments where the parked vehicle 108 is an electric vehicle, the parked vehicle operator 106 can establish a communication routine, or select a preferred mode of communication, to be used by the EV charging station 112, or the infrastructure provider 114, to contact the parked vehicle operator 106. In the case of multiple infrastructure providers in the environment 100, the parked vehicle owner 106 may established a communication routine with each of the infrastructure providers, so that any given charging station has a way to communicate with the vehicle operator 106, as needed. As an example, the vehicle operator 106 may want to PATENT be notified by the station 112 when the vehicle 108 is done charging, a financial charge is posted to the operator's account, an amount of energy consumed approaches a threshold amount, the vehicle 108 has been unplugged from the charging station 112, or other user-selected notification criteria.

[00035] The communication routine can be pre-established, or set up, by the parked vehicle operator 106 at the time of registering with the charging infrastructure provider 114 by indicating a preferred communication device, such as, e.g., the communication device 120, and a preferred communication method, such as, for example, via email, text, phone, social media (e.g., Facebook Messenger, What's App, Instagram, Twitter, Snapchat, etc.), or other communication tool (e.g., a chat interface or mobile application for electric vehicle owners or operators). In some embodiments, the pre-established communication routine provides for uni-directional communication from the parked vehicle 108 to the parked vehicle operator 106. In other embodiments, the pre-established communication routine provides for bi-directional communication between the parked vehicle 108 and the parked vehicle operator 106.

[00036] In some cases, the pre-established communication routine includes multiple options for contacting the vehicle operator and selection preferences for ranking the options, for example, to indicate which contact option is most preferred or least preferred and/or which contact option to use during a certain time of day. As an example, the pre-established communication routine can include send an email to an email address accessible via the communication device 120, send a text, voice, video, and/or photo message to a telephone number associated with the communication device 120, and/or send a message to a chat interface or other communication tool accessible via the communication device 120. PATENT

[00037] In embodiments, the EV charging station 112 can include a computing device (such as, e.g., infrastructure computing device 400 in FIG. 4) comprising a memory for storing the pre- established communication routine (e.g., data storage device 404 in FIG. 4). The computing device of the charging station 112 can also include a data processor (e.g., data processor 402) for facilitating retrieval of the routine from the memory and a wireless communication module (e.g., communication module 410) to carry out the routine. The wireless communication module can interact with one or more components of the wireless system 119 and/or different networks within the wireless network 118 depending on the communication method included in the pre- established routine. For example, in embodiments, the wireless communication module can include one or more short-range transceiver(s) (e.g., short-range transceiver(s) 412) to facilitate WPAN communications (e.g., Bluetooth, Zigbee, etc.), a wireless transceiver (e.g., wireless transceiver 414) to facilitate WLAN communications (e.g., WiFi, etc.), and/or a cellular transceiver to facilitate cellular communications (e.g., LTE, 3G, etc.). In embodiments, the charging station 112 can also be communicatively coupled to the charging infrastructure provider 114, or a remote server (not shown) associated therewith, via the wireless network 118, to facilitate aspects of the techniques disclosed herein.

[00038] The EV charging station 112 can store the pre-established communication routine in association with data identifying the parked vehicle operator 106. For example, in some embodiments, the computing device of the charging station 112 includes a subscription database (e.g., EV database 406 in FIG. 4) comprising information for the various electric vehicles that are subscribers of, registered with, or otherwise associated with, the charging station 112 and/or the charging infrastructure 114. In addition to the pre-established communication routine, the subscription database can include, for example, basic account information (e.g., name, address, PATENT phone number, etc.), payment information (e.g., credit card information, bank account information, etc.), vehicle information (e.g., license plate number, vehicle maker and model, etc.), ID tag information (e.g., a identification number associated with the ID tag 116, etc.), and account history information for each vehicle or vehicle operator registered with the provider 114. In other embodiments, the subscription database can be stored remotely, for example, on the remote server of the charging infrastructure provider 114 and accessed by the charging station 112 via the wireless network 118 as needed, for example, to look up a pre-established communication routine for a given ID tag number. In embodiments that include multiple infrastructure providers, each charging station can store a subscriber database for the infrastructure provider associated with that station.

[00039] In other embodiments, instead of a direct communication link between the charging station 112 and the communication device 120 of the parked vehicle operator 106, the charging station 112 is configured to indirectly communicate with the vehicle operator 106 via the vehicle 108. In such embodiments, the vehicle 108 can include a telematics control unit (TCU) 122 configured to enable wireless communication with each of the charging station 112 and the communication device 120 via the wireless network 118. In some cases, the TCU 122 requires access to different wireless communication networks in order to communicate with the charging station 112, which, for example, may be linked to a WPAN, or other short-range network, and the communication device 120, which, for example, may be accessible via an internet access network, a cellular network, or other long-range network. For example, the TCU 122 can include a wireless modem (e.g., wireless modem 514 in FIG. 5) configured to communicate over WLAN or Wi-Fi to facilitate communication between the vehicle 108 and the communication device 120. And the TCU 122 can include one or more short-range transceivers (e.g., short-range PATENT transceiver(s) 516 in FIG. 5) configured to communicate over Bluetooth, Zigbee, or other short- range network to facilitate communication between the vehicle 108 and the charging station 112.

[00040] As shown in FIG. 1, the wireless system 119 can include one or more third-party devices that are associated with the EV operator 102 and are configured to enable the EV operator 102 to establish communication with the parked vehicle operator 106 via the charging station 112 and to send an anonymous message to the operator 106. In embodiments, the third- party devices include a mobile electronic device 124 comprising a user interface (e.g., user interface 308 in FIG. 3) configured to enable the EV operator 102 to generate a message to the parked vehicle operator 106. The mobile electronic device 124 can be any type of mobile computing device, including, for example, a smartphone, a tablet, a personal digital assistant, etc. and can include a computing device, such as the computing device 300 in FIG. 3

[00041] In some embodiments, the mobile electronic device 124 can include a wireless communication module (e.g., wireless communication module 316 in FIG. 3) configured to facilitate communication with the charging station 112 over the wireless network 118. For example, the wireless communication module of the mobile electronic device 124 can include one or more short-range transceivers (e.g., short-range transceiver(s) 318) for enabling communication over a short-range network (e.g., Bluetooth, Zigbee, etc.) with the charging station 112, and/or a wireless transceiver (e.g., wireless transceiver 319) for enabling communication over WLAN with the charging station 112.

[00042] In other embodiments, the third-party devices further include a telematics control unit (TCU) 126 of the electric vehicle 104, and the TCU 126 can be configured to receive the user- generated message, or other communication from the mobile electronic device 124, for conveyance to the parked vehicle owner 106 via the charging station 112. For example, in some PATENT cases, the charging station 112 can be configured to only communicate with vehicle TCUs. In such cases, the TCU 126 can comprise a wireless communication module (e.g., wireless communication module 514 in FIG. 5) that comprises appropriate transceivers and/or wireless modems to enable communication with the charging station 112 and the mobile electronic device 124, similar to the wireless communication module of the TCU 122 of the parked vehicle 108.

[00043] According to embodiments, the mobile electronic device 124 (also referred to herein as "mobile device") can include a communication tool for, among other things, enabling the EV operator 102 to enter, select, or generate a message to the parked vehicle operator 106, via the user interface of the device 124, and providing the message to the charging station 112 for relay to the vehicle operator 106. In embodiments, the communication tool can be implemented as a mobile application (e.g., vehicle communication application 306 in FIG. 3) stored in a memory (e.g., data storage device 304) and executed by a processor (e.g., data processor 302) of the mobile device 124.

[00044] The communication tool can be configured to enable the user to enter text, record a video, capture an image, record a voice message, compose an email, and/or generate other types of messages to the parked vehicle operator 106 using the user interface of the mobile device 124. For example, the user interface of the mobile electronic device 124 can include one or more input devices (e.g., input devices 312) and cameras (e.g., camera 314) to facilitate creation of the message to the operator 106. The mobile application can also be configured to convert the user- generated message to an anonymous message before sending the message to the charging station 112. For example, the mobile application can be configured to remove any identifying information (e.g., name, IP address, phone number, metadata, digital tags, etc.) from the message, so as to not reveal an identity of the EV operator 102, the electric vehicle 104, and/or PATENT the mobile electronic device 124. In some cases, the EV operator 102 can choose a desired level of anonymity for the user-generated message, for example, by selecting whether to include a name, a callback number, or an email address.

[00045] In some embodiments, the mobile application can be included in, or added to, an existing charging station application that is associated with or maintained by the charging infrastructure provider 114 and available to the subscribers or members of the provider 114. In such cases, the EV operator 102 can obtain access to the mobile application, and therefore, the charging station 112, by registering the electric vehicle 104 with the provider 114. In other cases, the mobile application can be included in, or added to, an existing vehicle application of the mobile electronic device 124, the vehicle application being configured to interface with the vehicle computing system (e.g., vehicle computing system 500 in FIG. 5), or vehicle infotainment system (such as, e.g., FORD SYNC), of the electric vehicle 104. In such cases, the vehicle application may have a pre-established communication channel with the charging station 112 (e.g., if the provider 114 is the vehicle manufacturer) or may have access to the charging station subscription information or ID tag 116 information that is required to established the communication channel. In still other embodiments, the mobile application can be a stand-alone communication application that is downloaded and stored on the mobile electronic device 102 for the purpose of communicating with other vehicles in accordance with the techniques disclosed herein. In such cases, the mobile application can be configured to interface with existing charging station applications for the various infrastructure providers, and/or with the providers themselves, to relay the user-generated message to the parked vehicle operator 106.

[00046] In some situations, the charging station 112 is not an available communication resource for the communication tool, for example, because the parked vehicle 108 is not an PATENT electric vehicle, is not registered with the infrastructure provider 114, and/or does not have identifying information that can be associated with the parked vehicle operator 106 by the charging station 112. In such cases, the communication tool can be configured to communicate the user-generated message to the parked vehicle 108, and the parked vehicle 108 can utilize a pre-established communication routine (e.g., communication routine 512 in FIG. 5) stored in a memory (e.g., data storage device 504 in FIG. 5) of the vehicle 108 to relay the message to the parked vehicle operator 106. In some embodiments, the communication tool can be configured to interface with the parked vehicle 108 directly, for example, through a wireless modem (e.g., wireless modem 518 in FIG. 5) included in the TCU 122 of the parked vehicle 108. In such cases, the TCU 122 can be configured to send the user-generated message to the communication device 120 of the operator 108 using the pre-established communication routine stored in the parked vehicle 108.

[00047] In other embodiments, the communication tool can be configured to interface with the parked vehicle 108 indirectly, for example, through the TCU 126 of the electric vehicle 104, the TCU 126 sending the message to the TCU 122 of the vehicle 108 for relay to the parked vehicle operator 106 via the communication device 120. In such cases, the TCU 122 and TCU 126 can use dedicated short-range communication (DSRC) to transmit messages over a DSRC network included in the wireless network 118. For example, each of the TCUs 122 and 126 can include a DSRC transceiver (e.g., short-range transceiver 516 in FIG. 5) to facilitate use of the DSRC technology.

[00048] In some embodiments, the TCUs 122 and 126 can be configured to communicate messages directly to each other using point-to-point, or vehicle-to-vehicle (V2V), communication. In other cases, the wireless system 119 further includes a DSRC infrastructure PATENT

128 (e.g., roadside unit or communication tower) that can be configured to receive messages broadcast by the electric vehicle 104, the parked vehicle 108, and/or any other nearby vehicles or infrastructure (not shown) and relay the messages to their intended destinations using vehicle-to- infrastructure (V2I) and/or infrastructure-to-vehicle (I2V) communications. In such cases, the TCU 126 of the electric vehicle 104 can send the user-generated message to the DSRC infrastructure 128 and indicate the intended recipient as being the parked vehicle 108. The DSRC infrastructure 128 can then forward the received message to the TCU 122 of the parked vehicle 108 for relay to the parked vehicle operator 108 via the pre-established communication routine stored in the vehicle 108.

[00049] Referring now to FIG. 3, shown is an example computing device 300 that can be included in one or more mobile devices of the environment 100, such as, for example, the communication device 120 and/or the mobile device 124, in accordance with embodiments. As shown, the computing device 300 can include data processor 302 and data storage device 304. The data storage device 304 (e.g., electronic memory) can store one or more software program modules or software instructions, including, for example, vehicle communication application 306, for execution by the data processor 302. As shown, the data storage device 304 can also store infrastructure provider database 307.

[00050] In embodiments, the communication tool can be configured for implementation on the computing device 300 and can include at least the vehicle communication application 306 and the infrastructure provider database 307. For example, the vehicle communication application 306 can be configured to access the infrastructure provider database 307 to retrieve infrastructure provider information and/or compare physical characteristic data for a given charging card to identify the associated provider. In some embodiments, both the communication PATENT device 120 and the mobile device 124 can include the vehicle communication application 306 and the database 307, and/or other components of the communication tool. In other embodiments, only the mobile device 124 may include the application 306 and the database 307, and/or other components of the communication tool.

[00051] According to embodiments, the user interface 308 can be configured for enabling user interaction with the computing device 300 and for presenting information to the user (e.g., EV operator 102 or parked vehicle operator 106). The user interface 308 can be configured to interact with other components of the computing system 300, including the data storage device 304 and/or the data processor 302, in order to provide information or inputs received via the user interface 308 to an appropriate component of the computing system 300 and to present, to the user, information or outputs received from other components of the system 300. The user interface 308 can comprise one or more displays or display screens 310, input devices 312, and cameras 314, as well as various other devices for inputting, entering, receiving, capturing, displaying, or outputting data associated with the computing system 300, and/or the techniques disclosed herein. In some embodiments, the one or more displays 310 can include a touchscreen configured to receive touch inputs. The input devices 312 can include, for example, one or more of a keyboard, keypad, pointing device (e.g., electronic or optical mouse), button or push button, slider, switch, knob, dial, touch input device, microphone, and any other type of input device. The one or more camera(s) 314 can include a video camera, a still camera, a digital camera, a stereo camera, or any other image capturing device.

[00052] In embodiments, the user interface 308 can be used by the EV operator 104 to enter, select, or generate a message to the parked vehicle operator 106, using one or more of the input devices 312 and/or the camera(s) 314. In addition, the user interface 308 can be used by the EV PATENT operator 104 to enter, input, or capture ID tag information for identifying the provider 114. In some cases, the EV operator 104 can use the camera 314 to capture an image of the ID tag 116, and the data processor 304 and/or the vehicle communication application 306 can identify the provider 114 based on physical characteristics data extracted from the captured image. In other cases, the EV operator 104 may enter or input the provider name using the input devices 312.

[00053] As shown, the computing device 300 further includes a wireless communication module 316 for enabling wireless communications with one or more components of the wireless system 119 in the environment 100. The communication module 316 can include one or more antennas, radios, modems, receivers, and/or transmitters (not shown) for connecting to, or interfacing with, one or more of the wireless networks 118, such as, for example, WiFi, cellular, Bluetooth, NFC, RFID, satellite, and/or infrared. In embodiments, the wireless communication module 316 can include a tag reader 317 configured to read data stored on the ID tag 116, and one or more short-range transceivers 318 for wirelessly communicating with the charging station 112, the vehicle 104, and/or the vehicle 108 over one or more short-range network(s), such as, e.g., RFID, NFC, infrared, Bluetooth, Zigbee, or other WPANs. In addition, the wireless communication module 316 can include a wireless transceiver 319 for communicating over an 802.11 network (e.g., WiFi), a WiMax network, and other internet access networks, and a cellular transceiver 320 for wirelessly communicating over a cellular network (e.g., GSM, GPRS, LTE, 3G, 4G, CDMA, etc.).

[00054] In embodiments, the wireless communication module 316 receives external data from the charging station 112, the vehicle 104, or the vehicle 108, and/or a remote server associated with the charging infrastructure provider 114, and provides the external data to the data processor 302 for processing the data according to instructions included in the vehicle PATENT communication application 306 and/or for storing the received data in the data storage device 304. The external data can include a reply message from the parked vehicle operator 106 received via the charging station 112, the vehicle 104, and/or the vehicle 108. In addition, the wireless communication module 316 transmits internal data received from and/or generated by the data processor 302, for example, while executing the vehicle communication application 306, to the charging station 112, the vehicle 104, and/or the vehicle 108. The internal data can include a message to the parked vehicle operator 106 generated using the vehicle communication application 306 and received from the user interface 308, ID tag data obtained from the tag reader 317, and/or data retrieved from the data storage device 304.

[00055] The data storage device 304 can comprise one or more of electronic memory, nonvolatile random access memory (e.g., RAM), flip-flops, a computer-writable or computer- readable storage medium, a magnetic or optical data storage device, a magnetic or optical disc drive, a hard disk drive, or other electronic device for storing, retrieving, reading, or writing data. The data processor 302 can comprise one or more of a microprocessor, a microcontroller, a programmable logic array, an application-specific integrated circuit, a logic device, or other electronic device for processing, inputting, outputting, manipulating, storing, or retrieving data. In some embodiments, the computing device 300 can comprise a general purpose computer that is programmed with various programming instructions or modules stored in the data storage device 304 (such as, e.g., the vehicle communication application 306) or elsewhere. Though not shown, the computing device 300 may include a data bus, one or more input devices, and one or more output devices for facilitating operation of, or communication between, the data processor 302, the data storage device 304, the user interface 308, and/or the wireless communication module 316. PATENT

[00056] Referring now to FIG. 4, shown is an example infrastructure computing device 400 that may be included in the charging station or infrastructure 112 associated with the provider 114, another charging infrastructure in the environment 100 associated with another infrastructure provider, and/or the DSRC infrastructure 128, in accordance with embodiments. Components of the computing device 400 can be similar to those of the computing device 300. For example, the computing device 400 includes a data processor 402 and a data storage device 404 that can be at least functionally similar to the data processor 302 and data storage device 304 in FIG. 3. However, depending on the type of infrastructure, the data storage device 404 can store different types of information and/or software program modules or software instructions for execution by the data processor 402.

[00057] In embodiments where the computing device 400 is included in the charging infrastructure 112 or another charging station of the environment 100, the data storage device 404 can store an EV database 406 comprising subscription information for each of the electric vehicles that are registered with the provider 114. For example, the database 406 can include, for each vehicle registered with the infrastructure provider associated with the charging infrastructure, basic account information, payment information, vehicle information, ID tag information, account history information, and a pre-established communication routine for contacting a designated operator or owner of the vehicle. The pre-established communication routine can include, for example, contact information (e.g., phone number, email address, social media login, etc.), a preferred communication format (e.g., email, text, voice message, chat message, etc.), and other notification preferences previously selected by the vehicle owner or operator. In other embodiments, the EV database 406 can be stored remotely, for example, on the remote server of the charging infrastructure provider 114 and accessed by the computing device PATENT

400 via the wireless network 118 as needed, for example, to look up a pre-established communication routine.

[00058] As shown, the computing device 400 further includes a wireless communication module 410 for enabling wireless communications with one or more components of the wireless system 119 in the environment 100. The communication module 410 can be at least functionally similar to the wireless communication module 316 in FIG. 3. However, depending on the type of infrastructure, the communication module 410 can include different transceivers and other communication units. For example, when the computing device 400 is included in the DSRC infrastructure 128, the wireless communication module 410 can include a DSRC transceiver 416 for enabling communication over the DSRC network.

[00059] As another example, when the computing device 400 is included in the charging infrastructure 112, the wireless communication module 410 can include a tag reader 411 configured to read data stored on the ID tag 116, and one or more short-range transceivers 412 for wirelessly communicating with the charging station 112, the vehicle 104, and/or the vehicle 108 over one or more short-range networks, such as, e.g., RFID, NFC, infrared, Bluetooth, Zigbee, or other WPANs. In addition, the wireless communication module 410 can include a wireless transceiver 414 for communicating over an 802.11 network (e.g., WiFi), a WiMax network, and other internet access networks, and in some cases, a cellular transceiver (not shown) for wirelessly communicating over a cellular network (e.g., GSM, GPRS, LTE, 3G, 4G, CDMA, etc.).

[00060] In embodiments, the wireless communication module 410 of the charging station 112 can receive external data from the vehicle 104, the vehicle 108, the communication device 120, or the mobile device 124, and/or a remote server associated with the charging infrastructure PATENT provider 114, and can provide the external data to the data processor 402 for processing the data according to instructions included in data storage device 404 and/or for storing the received data therein. The external data can include a user-generated message for the parked vehicle operator 106 and/or ID tag data received from the vehicle 104 and/or the mobile device 124, and/or ID tag data received from the vehicle 108. In addition, the wireless communication module 410 transmits internal data received from and/or generated by the data processor 402, such as, e.g., the pre-established communication routine or other data from the EV database 406, to the vehicle 108 and/or the communication device 120. The internal data can include a data associated with the pre-established communication routine, such as, for example, login information or other code to enable the user-generated message to be sent to the parked vehicle operator 106 in accordance with the pre-established communication routine.

[00061] Referring now to FIG. 5, shown is an example vehicle computing system (VCS) 500 that may be included in the electric vehicle 104 and/or the parked vehicle 108, for example, as part of a vehicle electronics system or an infotainment system of the vehicle. In some cases, the VCS 500 may be an infotainment system such as the SYNC® system manufactured by FORD MOTOR COMPANY®. Other embodiments of the VCS 500 can include different, fewer, or additional components than those described below and shown in FIG. 5.

[00062] As illustrated, the VCS 500 comprises a data processor 502 (e.g., an electronic data processor), a data storage device 504, and a vehicle data bus 506. The VCS 500 can further include various electronic control units (ECUs) responsible for monitoring and controlling the electrical systems or subsystems of the vehicle. Each ECU may include, for example, one or more inputs and outputs for gathering, receiving, and/or transmitting data, a memory for storing the data, and a processor for processing the data and/or generating new information based PATENT thereon. In the illustrated embodiment, the ECUs of the VCS 500 include a telematics control unit 508 and a human machine interface (HMI) or user interface 510. Though not shown, the VCS 500 may include other ECUs, such as, for example, a body control module (BCM) for controlling and monitoring various electronic accessories in a body of the vehicle and a powertrain control module for controlling and monitoring an engine and transmission of the vehicle.

[00063] The ECUs of the VCS 500 are interconnected by the vehicle data bus 506 (such as, e.g., a controller area network (CAN) bus or an automotive Ethernet bus), which passes data to and from the various ECUs, as well as other vehicle and/or auxiliary components in communication with the VCS 500. Further, the data processor 502 can communicate with any one of the ECUs and the data storage device 504 via the data bus 506 in order to carry out one or more functions, including the functions associated with a pre-established communication routine 512. The data processor 502 can comprise one or more of a microprocessor, a microcontroller, a programmable logic array, an application-specific integrated circuit, a logic device, or other electronic device for processing, inputting, outputting, manipulating, storing, or retrieving data. In embodiments, the VCS 500 can comprise a general purpose computer that is programmed with various programming instructions or modules stored in the data storage device 504 or elsewhere.

[00064] The data storage device 504 can comprise one or more of electronic memory, nonvolatile random access memory (e.g., RAM), flip-flops, a computer-writable or computer- readable storage medium, a magnetic or optical data storage device, a magnetic or optical disc drive, a hard disk drive, or other electronic device for storing, retrieving, reading, or writing data. As shown, in some cases, the data storage device 504 stores ID tag data 513 comprising an PATENT identification number included or embedded in the ID tag 116. In such cases, the data processor 502 can be configured to retrieve the ID tag data 513 from the data storage device 504 upon receiving a verification request from the charging station 112 (e.g., to verify that the vehicle is authorized for or registered with the provider 114). The data storage device 504 can also store the pre-established communication routine 512 for contacting a designated operator or owner of the vehicle. The routine 512 can include contact information (e.g., phone number, email address, social media login, etc.), a preferred communication format (e.g., email, text, voice message, chat message, etc.), and other notification preferences previously entered by the vehicle owner or operator. In addition, the data storage device 504 stores one or more software program modules or software instructions for execution by the data processor 502.

[00065] The telematics control unit (TCU) 508 can be an ECU for enabling the vehicle to connect to one or more wireless networks, such as, for example, WiFi, cellular, Bluetooth, NFC, RFID, satellite, DSRC, and infrared. In embodiments, the TCU 508 includes a wireless communication module 514 comprising one or more antennas, radios, modems, receivers, and/or transmitters (not shown) for connecting to, or interfacing with, the various wireless networks. In embodiments, the wireless communication module 514 includes one or more short-range transceivers 516 for wirelessly communicating with the DSRC infrastructure 128 and/or other vehicles over the DSRC network, or for other communicating with the charging station 112, the communication device 120, and/or the mobile device 124 over another short-range network (e.g., Bluetooth, infrared, RFID, NFC, Zigbee, etc.). The wireless communication module 514 can also include a wireless modem 518 for facilitating communication over an 802.11 network (e.g., WiFi), a WiMax network, or other internet access networks. In embodiments, the wireless communication module 514 can also include a mobile communication unit (not shown) for PATENT wirelessly communicating over a cellular network (e.g., GSM, GPRS, LTE, 3G, 4G, CDMA, etc.), and/or a satellite network.

[00066] In embodiments, the TCU 508 receives external data from one or more components of the wireless system 119 via the wireless communication module 514, and provides the external data to the data processor 502, the data storage device 504, the user interface 510, or any other appropriate component of the VCS 500. In one embodiment, when the TCU 508 receives a user-generated message intended for the vehicle operator 106, the TCU 508 provides the message to the data processor 502, via the vehicle data bus 506, for processing. The data processor 502 retrieves the pre-established communication routine 512 from the data storage device 504 and converts the message into the communication format included in the routine 512 (e.g., generates an email or text message comprising the user-generated message, depending on the pre-established format). The data processor 502 then sends the formatted message and the contact information for reaching the operator 106 to the TCU 508. The TCU 508 uses the contact information to send the formatted message to the communication device 120 of the operator 106.

[00067] In addition, the TCU 508 can transmit internal data to components of the wireless system 119, such as, e.g., the charging station 112, via the wireless communication module 514. The TCU 508 may receive the internal data from the data processor 502, the data storage device 504, the user interface 510, or other component of the computing device 500. For example, the processor 502 can retrieve ID tag information 513 stored in the data storage device 504 and provide it to the TCU 508 for transmission to the charging station 112 in response to a verification request from the charging station 112.

[00068] According to embodiments, the user interface 510 (also known as a human-machine interface (HMI)) can be an ECU for enabling user interaction with the vehicle and for presenting PATENT vehicle information to the vehicle operator or driver. The user interface 510 can be configured to interact with other ECUs of the vehicle, including the TCU 508, the data storage device 504, and/or the data processor 502, via the data bus 506, in order to provide information or inputs received via the user interface 510 to an appropriate component of the VCS 500 and to present, to the vehicle operator, information or outputs received from the various components of the VCS 500. The user interface 510 can comprise one or more displays or display screens, audio speakers, and input devices, as well as various other devices for inputting, entering, receiving, capturing, displaying, or outputting data associated with the vehicle computing system 500, and/or the techniques disclosed herein. In some embodiments, the user interface 510 includes an instrument panel (IP) (not shown) positioned in a dashboard of the vehicle for housing instrumentation and controls for operation of the vehicle. In embodiments, the user interface 510 can be used by the vehicle operator to enter or configure the pre-established communication routine 512 and/or the ID tag data 513.

[00069] FIG. 6 illustrates an example method 600 for establishing anonymous communication with the operator of a parked vehicle, using the parked vehicle itself or nearby infrastructure, in accordance with embodiments. The method 600 can be carried out by a mobile communication device, such as the mobile device 124 shown in FIG. 1, or more specifically, a computing system therein, such as the computing system 300 shown in FIG. 3. Further, the mobile device can interact with one or more components of the environment 100 shown in FIG. 1, such as the charging station 112 associated with the provider 114, another charging station associated with another infrastructure provider, the TCU 122, and/or the TCU 124, to carry out the operations of the method 600. In one embodiment, the method 600 is implemented, at least in part, by the data PATENT processor 302 executing software stored in the data storage device 304, such as the vehicle communication application 306, as shown in FIG. 3.

[00070] The method 600 can begin at step 602, where the processor prompts entry of physical characteristic data for a charging card (e.g., ID tag 116) of a parked vehicle via a user interface (e.g., user interface 308 in FIG. 3) of the mobile device. For example, the user interface can prompt the user to take a picture of the vehicle charging card, and the processor can be configured to extract physical characteristics data for the charging card from the captured image (e.g., a color, shape, design, logo, or other key feature or trait of the card).

[00071] At step 604, the processor identifies a charging infrastructure provider based on the physical characteristic data received at step 602. For example, the processor can access a provider identification database (e.g. infrastructure provider database 307) stored in the memory of the mobile device and perform a reverse look-up to associate the received physical characteristic data with a provider listed in the database as having those same characteristics.

[00072] In embodiments, the method 600 further includes, at step 606, retrieving an identification (ID) number (also referred to herein as "identifier") of the identification tag. In some embodiments, a tag reader (e.g., tag reader 317) or other antenna can be configured to read the identification number from the charging card and provide the number to the processor, for example, where the ID tag is an RFID tag or other wireless tag. In other embodiments, the ID number can be retrieved from the image captured at step 602, for example, where the ID number is a QR code, bar code, or other optically-readable tag.

[00073] At step 608, the method 600 includes prompting entry of a message to the parked vehicle owner via the user interface. For example, the user can type a message, speak a message, PATENT capturing an image as part of the message, or use any other available format for generating the message through the user interface.

[00074] In some embodiments, the method 600 includes, at step 610, providing the identification number of the vehicle charging card to the identified provider, or a charging infrastructure associated therewith, to establish a communication link with that provider/station. In other embodiments, the ID number is transmitted at step 612 with the user-generated message.

[00075] At step 612, the method 600 includes transmitting the user-generated message, using a wireless unit (e.g., wireless communication module 316), to a charging infrastructure (e.g., charging station 112) associated with the charging infrastructure provider identified at step 604, or the infrastructure provider itself (e.g., provider 114), using the communication link for relay to a vehicle operator (e.g., parked vehicle operator 106) associated with the identification number. The charging infrastructure and/or provider can relay the message to the parked vehicle operator using a communication routine pre-established by the vehicle operator. For example, upon receiving the identification number and message, the charging infrastructure and/or provider can access an electric vehicle database (e.g., EV database 406) to identify the vehicle operator that is associated with the received identification number and to locate the pre-established communication routine that is associated with the identified operator. The charging infrastructure and/or provider can then use the pre-established communication routine to relay the user- generated message to the identified operator.

[00076] In some embodiments, the method 600 further includes, at step 614, receiving a reply message from the vehicle operator via the charging infrastructure provider. The reply message can be sent to the originating vehicle operator (e.g., EV operator 104) through the same communication channel established in steps 610 and 612 but in reverse, for example, if the pre- PATENT established communication routine provides for bi-directional communication. For example, the reply message may be sent from the communication device (e.g., communication device 120) of the parked vehicle operator to the charging infrastructure and then to the mobile device of the user (e.g., EV operator 104). The reply message can be displayed on the user interface of the mobile device for viewing by the user. In some embodiments, the method 600 may end after step 614. In other embodiments, the two vehicle operators may exchange multiple rounds of messages, and the method 600 may end once communication has ceased.

[00077] In some embodiments, physical characteristic data may not be received at step 602, for example, because the parked vehicle does not have an ID tag, charging card, or other identifying information on the vehicle. In such cases, the method 600 continues from step 602 to step 616 to determine whether physical characteristic data has been received. If the data is received, the method 600 continues to step 604 as described above. If the data is not received, the method 600 begins searching for alternative routes for establishing a communication link with the parked vehicle operator.

[00078] For example, at step 618, the method 600 can include searching for a DSRC network via a vehicle associated with the mobile device, such as, e.g., the electric vehicle 102. At step 620, the method 600 includes determining whether the electric vehicle 102 is communicatively coupled to the DSRC network. If the DSRC network is found, the method 600 continues to step 622, which includes establishing a DSRC -based communication link with the parked vehicle (e.g., vehicle 108). In some cases, the DSRC -based communication link can be vehicle-to- vehicle (V2V) communication, where the electric vehicle (e.g., vehicle 104) is directly linked to the parked vehicle (e.g., vehicle 108) via DSRC. In other cases, the DSRC -based communication link can be vehicle-to-infrastructure (V2I) communication, where the vehicles communicate with PATENT each other through a DSRC infrastructure (e.g., DSRC infrastructure 128). Once the DSRC communication link is established, the method 600 continues to step 608 to prompt entry of a message to the parked vehicle owner, and at steps 610 and 612, the ID number and user- generated message can be transmitted through the DSRC communication link established at step 622.

[00079] If a DSRC network is not found at step 620, the method 600 can continue to step 624 to search for a wireless modem (e.g., wireless modem 518) of the parked vehicle. At step 626, the processor can determine whether the wireless modem has been found. If no modem is found, the method 600 may end. If a modem is found at step 626, the method 600 can move onto step 608 to prompt entry of a message, and the ID number and user-generated message can be transmitted to the wireless modem at steps 610 and 612 for relay to the parked vehicle operator.

[00080] In some embodiments, if no communication route is available for contacting the parked vehicle operator, or if the pre-established communication routine fails for any reason, the method 600 can include sending the user-generated message to an infrastructural recipient (e.g., local parking attendant, parking enforcement entity, or a representative of the infrastructure provider), via the charging station, in order to inform said recipient of a parking violation, file a complaint, or otherwise report a problem (e.g., if the parked vehicle is a non-electric vehicle parked in an charging space), to request assistance from said recipient (e.g., if the EV operator would like someone to unplug, or re-plug, the operator's electric vehicle), or to convey any other message generated by the EV operator using the communication tool described herein. In the case of a parking attendant or parking enforcement entity, the infrastructural recipient can be associated with the charging station, the infrastructure provider, or the parking lot in which the charging station is located. In some cases, this option is available only for one-way PATENT communication from the EV operator to the attendant or entity, for example, if the EV operator is not registered with the charging station. In other cases, this option is available for two-way communication between the EV operator and the attendant or entity, for example, if the EV operator is a registered user of the charging station. In such cases, the reply message may be generated by and received from the infrastructural recipient.

[00081] In certain embodiments, the process descriptions or blocks in the figures, such as FIG. 6, can represent modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Any alternate implementations are included within the scope of the embodiments described herein, in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those having ordinary skill in the art.

[00082] It should be emphasized that the above-described embodiments, particularly, any "preferred" embodiments, are possible examples of implementations, merely set forth for a clear understanding of the principles of the invention. Many variations and modifications may be made to the above-described embodiment(s) without substantially departing from the spirit and principles of the techniques described herein. All such modifications are intended to be included herein within the scope of this disclosure and protected by the following claims.

Claims

PATENT CLAIMS

1. A wireless system, comprising:

a communication device associated with a vehicle operator;

a third-party device configured to send an anonymous message for the vehicle operator; and

a vehicle infrastructure configured to receive the anonymous message from the third- party device and relay the anonymous message to the communication device using a pre- established routine for communicating with the vehicle operator.

2. The wireless system of claim 1, wherein the pre-established routine includes sending an email to an email address accessible via the communication device.

3. The wireless system of claim 1, wherein the pre-established routine includes sending a message to a telephone number associated with the communication device.

4. The wireless system of claim 1, further comprising a vehicle in communication with the vehicle infrastructure and configured to communicate with the communication device according to the pre-established routine, the vehicle infrastructure being configured to relay the anonymous message to the communication device via the vehicle.

5. The wireless system of claim 4, wherein the vehicle is an electric vehicle, and the vehicle infrastructure is a vehicle charging station capable of supplying electrical energy to the vehicle.

6. The wireless system of claim 5, wherein the third-party device is a mobile device with a user interface for generating the anonymous message. PATENT

7. The wireless system of claim 4, wherein the vehicle infrastructure is a dedicated short- range communication infrastructure.

8. The wireless system of claim 7, further comprising a mobile device with a user interface for generating the anonymous message, wherein the third-party device is a second vehicle telematics unit configured to receive the anonymous message from the mobile device.

9. The wireless system of claim 1, wherein the third-party device is a mobile device with a user interface for generating the anonymous message, and the vehicle infrastructure is a vehicle charging station configured to: receive the anonymous message from the mobile device using short-range wireless communication and relay the anonymous message to the communication device via a wireless communication network.

10. The wireless system of claim 1, further comprising a mobile device with a user interface for generating the anonymous message, wherein the third-party device is a second vehicle telematics unit configured to receive the anonymous message from the mobile device.

11. A method for establishing anonymous communication with a vehicle operator, comprising:

prompting, via a user interface, entry of physical characteristic data for a vehicle charging card;

identifying, using a processor, an infrastructure provider based on received physical characteristic data; and

transmitting, using a wireless unit, an identifier of the vehicle charging card and a user- generated message, to a charging infrastructure associated with the provider, for relay to a vehicle operator associated with the identifier. PATENT

12. The method of claim 11, wherein the charging infrastructure relays the user-generated message to the vehicle operator using a communication routine pre-established by the vehicle operator.

13. The method of claim 11, wherein the physical characteristic data is entered by capturing an image of the vehicle charging card.

14. The method of claim 13, wherein the identifier is obtained from the captured image of the vehicle charging card.

15. The method of claim 11, further comprising obtaining the identifier from the vehicle charging card using an antenna.

16. The method of claim 15, wherein the vehicle charging card includes a radio-frequency identification tag.

17. The method of claim 11, further comprising receiving a reply message from the vehicle operator via the charging infrastructure.

18. A computing device, comprising:

a user interface configured to receive a user-generated message and to prompt entry of physical characteristic data for a charging card of a vehicle; and

a processor configured to: identify an infrastructure provider based on received physical characteristic data, and transmit the user-generated message and an identifier of the charging card to a charging infrastructure associated with the provider for relay to a vehicle operator associated with the identifier. PATENT

19. The computing device of claim 18, further comprising a tag reader for obtaining the identifier from an identification tag of the charging card.

20. The computing device of claim 18, wherein the user interface includes a camera for capturing an image of the charging card, the captured image including the physical characteristic data.

21. The computing device of claim 20, wherein the captured image further includes the identifier.

22. The computing device of claim 18, further comprising a wireless unit configured to communicate with the charging infrastructure.

23. The computing device of claim 22, wherein the charging infrastructure relays the user- generated message to the vehicle operator using a communication routine pre-established by the vehicle operator.

24. The computing device of claim 22, wherein the wireless unit is further configured to communicate with a vehicle telematics unit, and wherein the processor is further configured to, if physical characteristic data is not received, instruct the vehicle telematics unit to relay the user- generated message to the vehicle operator.

25. The computing device of claim 24, wherein the vehicle telematics unit is configured to communicate with a second telematics unit included in the vehicle to relay the user-generated message to the vehicle operator using a communication routine pre-established by the vehicle operator.