Vehicle charge sharing and communication

Abstract

Vehicle charge sharing and communication can be enabled (e.g., using computerized tools). For example, a vehicle may include a memory storing computer-executable components including a charge sharing determination component and a communication component, and a processor executing the computer-executable components stored in the memory, the charge sharing determination component determines, based on a charge sharing request from another vehicle different from the vehicle, whether a battery condition of the vehicle satisfies a charge sharing criterion suitable for the charge sharing request, the communication component establishes a communication connection with another vehicle based on a determination that the battery condition satisfies the charge sharing criteria.

Description

Technical Field

[0001] The subject matter of the present disclosure relates to battery-powered vehicles (such as transportation vehicles), and more particularly to vehicle charge sharing and corresponding communication. Background Art

[0002] Electric vehicles are becoming increasingly common worldwide and are expected to become one of the most common means of transportation. Similar to an internal combustion engine-driven vehicle running out of fuel, an electric vehicle may be over-discharged and unable to reach a charging station. However, supplying additional electrical energy to an electric vehicle is more complex than adding additional fuel to an internal combustion engine-driven vehicle. Some electric vehicles have bi-directional energy transfer capabilities, but there is no cooperation in charge transfer between the electric vehicle and / or the charging station.

[0003] The above background art related to electric vehicles is only intended to provide a background overview of some current problems and is not exhaustive. Other background information may become more apparent after reading the following detailed description. Summary of the Invention

[0004] An overview is given below that provides a basic understanding of one or more embodiments of the present invention. This overview is not intended to identify key or important elements, or to define any scope of a particular embodiment or any scope of the claims. Its sole purpose is to present concepts in a simplified form as a prelude to the more detailed description provided later. In one or more embodiments described herein, systems, devices, computer-implemented methods, apparatuses, and / or computer program products that facilitate charge sharing and corresponding communication are described.

[0005] As described above, vehicle charge sharing and corresponding communication can be improved in various ways, and various embodiments are described herein for this and / or other purposes.

[0006] According to one embodiment, a system may include a memory storing computer-executable components and a processor executing the computer-executable components stored in the memory, wherein the computer-executable components may include a charge sharing determination component and a communication component. The charge sharing determination component determines whether the condition of the battery of the vehicle meets the charge sharing standard applicable to the charge sharing request based on a charge sharing request from another vehicle different from the vehicle. The communication component establishes a communication connection with the other vehicle based on determining that the condition of the battery meets the charge sharing standard.

[0007] According to another embodiment, a non-transitory machine-readable medium may include executable instructions that, when executed by a processor, facilitate the performance of an operation that includes determining whether a charge sharing request criterion applicable to a first vehicle has been met and generating a charge sharing request in response to determining that the charge sharing request criterion has been met, the charge sharing request to be sent from the first vehicle to a second vehicle different from the first vehicle.

[0008] According to yet another embodiment, a method may include receiving, by a system including a processor, a charge sharing request from a first vehicle, determining, by the system based on the charge sharing request, a second vehicle that will provide charge to the first vehicle via the system; and initiating, by the system based on determining that a charge sharing criterion has been met, a charge transfer from the second vehicle via the system to the first vehicle. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 A block diagram illustrating an exemplary system in accordance with one or more embodiments described herein.

[0010] Figure 2 A block diagram illustrating an exemplary non-limiting computer-executable component in accordance with one or more embodiments described herein.

[0011] Figure 3 A schematic diagram illustrating an exemplary non-limiting vehicle charge sharing in accordance with one or more embodiments described herein.

[0012] Figure 4 A schematic diagram illustrating an exemplary non-limiting vehicle charge sharing in accordance with one or more embodiments described herein.

[0013] Figure 5 A schematic diagram illustrating an exemplary non-limiting vehicle navigation in accordance with one or more embodiments described herein.

[0014] Figure 6 A flowchart illustrating a process associated with vehicle charge sharing and communication in accordance with one or more embodiments described herein.

[0015] Figure 7 A flowchart illustrating a process associated with vehicle charge sharing and communication in accordance with one or more embodiments described herein.

[0016] Figure 8 A flowchart illustrating a process associated with vehicle charge sharing and communication in accordance with one or more embodiments described herein.

[0017] Figure 9is an exemplary, non-limiting computing environment in which one or more embodiments described herein may be implemented.

[0018] Figure 10 is an exemplary, non-limiting network environment in which one or more embodiments described herein may be implemented. DETAILED DESCRIPTION

[0019] The following detailed description is illustrative only and is not intended to limit the embodiments and / or the application or use of the embodiments. In addition, it is not intended to be bound by any express or implied information provided in the preceding background or summary sections or in the detailed description section.

[0020] One or more embodiments are now described with reference to the accompanying drawings, wherein the same reference numerals are used to refer to the same elements throughout. In the following description, for the purpose of explanation, many specific details are set forth in order to provide a more thorough understanding of the one or more embodiments. However, it is apparent that in various circumstances, the one or more embodiments may be practiced without these specific details.

[0021] It should be understood that when an element is referred to as being "coupled" to another element, it may describe one or more different types of coupling, including, but not limited to, chemical coupling, communication coupling, capacitive coupling, electrical coupling, electromagnetic coupling, inductive coupling, operational coupling, conductive coupling, acoustic coupling, ultrasonic coupling, optical coupling, physical coupling, thermal coupling, and / or another type of coupling. As described herein, an "entity" may include a person, a client, a user, a computing device, a software application, an agent, a machine learning model, an artificial intelligence, and / or another entity. It should be understood that such an entity may facilitate implementation of the present disclosure in accordance with one or more embodiments described herein.

[0022] The computer processing systems, computer-implemented methods, apparatuses, and / or computer program products described herein employ hardware and / or software to solve problems that are highly technical in nature (e.g., facilitating one or more actions related to vehicle charge sharing and corresponding communications) that are not abstract and cannot be performed as a set of mental actions by a human being.

[0023] Now go to Figure 1 , shows an exemplary non-limiting system 100 according to one or more embodiments of the present invention. The system 100 may include a computerized tool that may be configured to perform various operations related to vehicle charge (charge, charge or electrical energy or charging) sharing and communication. According to various exemplary embodiments, the system 100 may be deployed in a vehicle 102 (e.g., Figure 1 on or in the vehicle shown). Figure 1The vehicle 102 is depicted as a car, but the architecture of system 100 is not limited thereto. For example, the system 100 described herein can be implemented with various types of vehicles 102. Exemplary vehicles 102 that can be incorporated with the exemplary system 100 can include, but are not limited to: cars (e.g., autonomous vehicles), airplanes, trains, motorcycles, carts, trucks, semi-trailer trucks, buses, boats, recreational vehicles, helicopters, jets, electric scooters, electric bicycles, charging stations, combinations thereof, and the like. Additionally, note that the system 100 can be implemented in various types of cars, such as battery electric vehicles, hybrid vehicles, plug-in hybrid vehicles, or other suitable types of vehicles.

[0024] As Figure 1 shown, the system 100 can include one or more systems 104, which can include one or more input devices 106, one or more other vehicle electronic systems and / or devices 108, and / or one or more computing devices 110. Additionally, the system 100 can include one or more external devices 112, which can be communicatively and / or operatively coupled to the one or more computing devices 110 of the one or more systems 104 via one or more networks 114 and / or a direct electrical connection (e.g., as Figure 1 shown). In various embodiments, one or more of the system 104, input device 106, vehicle electronic system and / or device 108, computing device 110, external device 112, and / or network 114 can be communicatively or operatively coupled to each other (e.g., via a bus or wireless network) to perform one or more functions of the system 100. It should be noted that the system 104 is not limited to being implemented in a vehicle. For example, in various embodiments, a charging station can include a system 104, which can be communicatively coupled and / or electrically coupled to the vehicle 102.

[0025] The one or more input devices 106 may display one or more interactive graphical entity interfaces ("GUIs") that facilitate access to and / or control of various functions and / or applications of the vehicle 102. The one or more input devices 106 may display one or more interactive GUIs that facilitate access to and / or control of various functions and / or applications. The one or more input devices 106 may include one or more computerized devices, which may include, but are not limited to: personal computers, desktop computers, laptop computers, cellular phones (e.g., smartphones or mobile devices), computerized tablets (e.g., including a processor), smartwatches, keyboards, touchscreens, mice, combinations thereof, and the like. Entities or users of the system 100 may utilize the one or more input devices 106 to input data into the system 100. Additionally, the one or more input devices 106 may include one or more displays that may present one or more outputs generated by the system 100 to an entity. For example, the one or more displays may include, but are not limited to: cathode ray tube displays ("CRT"), light emitting diode displays ("LED"), electroluminescent displays ("ELD"), plasma display panels ("PDP"), liquid crystal displays ("LCD"), organic light emitting diode displays ("OLED"), combinations thereof, and the like.

[0026] For example, the one or more input devices 106 may include a touchscreen that may present one or more graphical touch controls that may respectively correspond to controls of functions, applications, functions of applications, interactive data, data hyperlinks, etc. of the vehicle 102, wherein selections and / or interactions with the graphical touch controls by touching activate the corresponding functions. For example, one or more GUIs displayed on the one or more input devices 106 may include selectable graphical elements, such as buttons or bars corresponding to vehicle navigation applications, media applications, phone applications, rear view camera functions, car settings functions, parking assist functions, and the like. In some embodiments, selecting a button or bar corresponding to an application or function may result in the generation of a new window or GUI that includes other selectable icons or widgets associated with the selected application. For example, selecting one or more selectable options herein may result in the generation of a new GUI or window that includes additional buttons or widgets having one or more selectable options. The type and appearance of the controls may vary. For example, the graphical touch controls may include icons, symbols, widgets, windows, tabs, text, images, combinations thereof, and the like.

[0027] The one or more input devices 106 may include suitable hardware that registers input events in response to touch (e.g., a finger, a stylus, a gloved hand, a pen, etc.). In some embodiments, the one or more input devices 106 may detect the position of an object (e.g., via a finger, a stylus, a gloved hand, a pen, etc.) very close (e.g., a few centimeters) above the touch screen, and the object does not touch the touch screen. As used herein, unless otherwise specified, referring to "on the touch screen" means contact between an object (e.g., a physical finger) and the one or more input devices 106, and referring to "above the touch screen" means positioning the object very close to the touch screen (e.g., at a defined distance from the touch screen) but not touching the touch screen.

[0028] The types of the input devices 106 may be different and may include, but are not limited to: resistive touch screens, surface capacitive touch screens, projected capacitive touch screens, surface acoustic wave touch screens, and infrared touch screens. In various embodiments, the one or more input devices 106 may be positioned on the instrument panel of the vehicle 102, such as in the center stack or on or within the center console of the instrument panel. However, the position of the one or more input devices 106 within the vehicle 102 may be different.

[0029] The one or more other vehicle electronic systems and / or devices 108 may include one or more additional devices and / or systems of the vehicle 102 (e.g., in addition to the one or more input devices 106 and / or computing devices 110), which may be controlled at least in part based on commands issued by the one or more computing devices 110 (e.g., via one or more processing units 116) and / or commands issued by the one or more external devices 112 communicatively coupled thereto. For example, the one or more other vehicle electronic systems and / or devices 108 may include: a media system (e.g., audio and / or video); a rearview camera system; a heating, ventilation, and air conditioning (“HVAC”) system; a lighting system; a cruise control system, a power lock system, a navigation system, an autonomous driving system, a vehicle sensor system, a telecommunications system, combinations thereof, and the like. Other exemplary other vehicle electronic systems and / or devices 108 may include one or more sensors, which may include an odometer, an altimeter, a speedometer, an accelerometer, engine characteristics and / or components, a fuel gauge, a flow meter, a camera (e.g., a digital camera, a thermal camera, an infrared camera, etc.), a laser, a radar system, a lidar system, a microphone, a vibrometer, a humidity sensor, a thermometer, a seatbelt sensor, a wheel speed sensor, combinations thereof, and the like. For example, the speedometer of the vehicle 102 may detect the driving speed of the vehicle 102. In addition, the one or more sensors may detect and / or measure one or more conditions external to the vehicle 102, such as: whether the vehicle 102 is traveling through a rainy environment; whether the vehicle 102 is traveling through winter environmental conditions (e.g., snowy and / or icy environmental conditions); whether the vehicle 102 is traveling through very hot environmental conditions (e.g., desert environmental conditions); and / or similar conditions. Example navigation information may include, but is not limited to: the destination of the vehicle 102, the location of the vehicle 102, the type of the vehicle 102, the speed of the vehicle 102, the environmental conditions around the vehicle 102, the planned route of the vehicle 102, the traffic conditions the vehicle 102 is expected to encounter, the operating state of the vehicle 102, combinations thereof, and the like.

[0030] One or more computing devices 110 may use machine-executable instructions to facilitate the execution and control of one or more operations of vehicle 102, including one or more operations of one or more input devices 106 and one or more other vehicle electronic systems / devices 108. In this regard, embodiments of the systems 100 described herein and other systems may include one or more machine-executable components that are included within one or more machines (e.g., included in one or more computer-readable storage media associated with one or more machines such as computing devices 110). These components, when executed by one or more machines (e.g., processors, computers, virtual machines, etc.), may cause the one or more machines to perform the described operations.

[0031] For example, one or more computing devices 110 may include or be operatively coupled to at least one memory 118 and / or at least one processing unit 116. The one or more processing units 116 may be any of a variety of available processors. For example, dual microprocessors and other multi-processor architectures may also be used as the processing unit 116. In various embodiments, at least one memory 118 may store software instructions embodied as functions and / or applications that, when executed by the at least one processing unit 116, facilitate the performance of operations defined by the software instructions. In the illustrated embodiment, these software instructions may include one or more operating systems 120, one or more computer-executable components 122, and / or one or more other vehicle applications 124. For example, one or more operating systems 120 may be used to control and / or allocate resources of one or more computing devices 110. It should be understood that the claimed subject matter may be implemented with a variety of operating systems or combinations of operating systems.

[0032] The one or more computer-executable components 122 and / or the one or more other vehicle applications 124 may utilize the management of resources by the one or more operating systems 120 through program modules and program data also stored in the one or more memories 118. The one or more computer-executable components 122 may provide various features and / or functions for facilitating vehicle charge sharing and corresponding communication. For example, the other vehicle applications 124 may include, but are not limited to: navigation applications, media player applications, telephone applications, vehicle settings applications, parking assistance applications, emergency road rescue applications, combinations thereof, and the like. The features and functions of the one or more computer-executable components 122 will be discussed in more detail below.

[0033] One or more computing devices 110 may also include one or more interface ports 126, one or more communication units 128, and a system bus 130 that communicatively couples the various features of one or more computing devices 110 (e.g., one or more interface ports 126, one or more communication units 128, one or more memories 118, and / or one or more processing units 116). One or more interface ports 126 may connect one or more input devices 106 (and other possible devices) and one or more other vehicle electronic systems / devices 108 to one or more computing devices 110. For example, one or more interface ports 126 may include serial ports, parallel ports, game ports, Universal Serial Bus (“USB”), etc.

[0034] One or more communication units 128 may include suitable hardware and / or software that may facilitate the connection of one or more external devices 112 to one or more computing devices 110 (e.g., via a wireless connection and / or a wired connection). For example, one or more communication units 128 may be operatively coupled to one or more external devices 112 via one or more networks 114. One or more networks 114 may include wired and / or wireless networks, including but not limited to a Personal Area Network (“PAN”), a Local Area Network (“LAN”), a cellular network, a Wide Area Network (“WAN”, e.g., the Internet), etc. For example, one or more external devices 112 may communicate with one or more computing devices 110 using almost any desired wired or wireless technology (and vice versa), the technologies including but not limited to: Wireless Fidelity (“Wi-Fi”), Global System for Mobile Communications (“GSM”), Universal Mobile Telecommunications System (“UMTS”), Worldwide Interoperability for Microwave Access (“WiMAX”), Enhanced General Packet Radio Service (“Enhanced “GPRS”), Fifth Generation (“5G”) communication system, Sixth Generation (“6G”) communication system, 3rd Generation Partnership Project (“3GPP”) Long Term Evolution (“LTE”), 3rd Generation Partnership Project 2 (“3GPP2”) Ultra Mobile Broadband (“UMB”), High Speed Packet Access (“HSPA”), Zigbee and other 802.XX wireless technologies and / or traditional telecommunication technologies, Near Field Communication (“NFC”) technology, Session Initiation Protocol (“SIP”), RF4CE protocol, WirelessHART protocol, 6LoWPAN (IPv6-based Low-Power Wireless Area Network), Z-Wave, ANT, Ultra-Wideband (“UWB”) standard protocol, Vehicle-to-Vehicle (V2V), Vehicle-to-Everything (V2E), and / or other proprietary and non-proprietary communication protocols. In this regard, one or more communication units 128 may include software, hardware, or a combination of software and hardware configured to facilitate wired and / or wireless communication between one or more computing devices 110 and one or more external devices 112. Although, for clarity of illustration, one or more communication units 128 are shown as separate units not stored within the memory 118, it should be understood that one or more (software) components of the communication unit may be stored in the memory 118 and include computer-executable components.

[0035] One or more external devices 112 may include any suitable computing device that includes display and input devices (e.g., touchscreen) that may communicate with one or more computing devices 110 included within the system 104 and interface with one or more computer-executable components 122 (e.g., using a suitable Application Programming Interface (“API”)). For example, one or more external devices 112 may include, but are not limited to: mobile phones, smartphones, tablet personal computers (“PCs”), digital assistants (“PDAs”), head-up displays (“HUDs”), virtual reality (“VR”) head-mounted display devices, augmented reality (“AR”) head-mounted display devices, or another type of wearable computing device, desktop computers, laptop computers, tablets, combinations thereof, and the like.

[0036] Figure 2 A block diagram of an exemplary non-limiting computer-executable component 122 that may facilitate charge sharing and corresponding communication in accordance with one or more embodiments described herein is shown. For brevity, a repeated description of similar elements employed in other embodiments described herein is omitted. As Figure 2 shown, one or more computer-executable components 122 may include a charge sharing determination component 202, a communication component 204, a navigation component 206, a charge transfer component 208, and / or a request component 210.

[0037] In various embodiments, the charge sharing determination component 202 may determine, based on a charge sharing request from another vehicle (e.g., vehicle 102b) different from the vehicle (e.g., vehicle 102a), whether the condition of the battery 132 of the vehicle (e.g., vehicle 102a) meets the charge sharing request (e.g., see Figure 3Scenario 300, which depicts a charge sharing standard for two-way vehicle-to-vehicle charging (e.g., vehicle charge sharing) between vehicles 102 via cable 306. It should be noted that in various embodiments, battery 132 may include a solid-state battery. In additional embodiments, battery 132 may include a solid-state battery pack composed of one or more electrically coupled solid-state battery portions. In further embodiments, battery 132 may include one or more battery cells (e.g., lithium battery cells), and thus battery 132 may include a single-cell battery or a multi-cell battery. In one or more embodiments, such a charge sharing standard herein may include a threshold level of available additional charge or charge available for discharging / sharing (e.g., voltage, current intensity, Coulomb count, ampere-hour, etc.) and / or the ability to regain the corresponding charge (e.g., recharge ability or availability). In another embodiment, the charge sharing standard may include user preferences applicable to battery 132 (e.g., whether the user has enabled the corresponding charge sharing). In other embodiments, the charge sharing standard may include the state of health (SOH) of battery 132 (e.g., whether battery 132 includes a threshold SOH according to a defined SOH metric). In additional embodiments, the charge sharing standard may include the distance applicable to vehicles 102a and 102b (e.g., or other vehicles herein) (e.g., the geographical distance between vehicles 102a and 102b, the travel time between vehicles 102a and 102b, etc.). In another embodiment, the charge sharing standard may be based on the charge sharing compatibility between vehicles 102a and 102b (e.g., vehicle capabilities, cable compatibility, etc.), e.g., whether cable 306 and / or connectors 304a and / or 304b are compatible (or otherwise compatible) with the charging ports 302a and / or 302b of the corresponding vehicles herein.

[0038] In various embodiments, the condition of battery 132 may include the state of charge of battery 132. In this regard, the communication connection herein may include available charge data, which represents the amount of charge available for transfer between vehicles herein (e.g., from vehicle 102a to vehicle 102b). In various embodiments, the amount of charge available for transfer between vehicles herein (e.g., from vehicle 102a to vehicle 102b) may be determined by charge sharing determination component 202, e.g., based on historical driving data applicable to vehicle 102a. In this regard, charge sharing determination component 202 may determine the amount of charge that can be transferred according to the predicted future driving (or travel) applicable to the vehicle that is to share its respective charge (e.g., based on historical driving). In other embodiments, the amount of charge available for transfer between vehicles (e.g., from vehicle 102a to vehicle 102b) may be determined, for example, by charge sharing determination component 202, e.g., based on calendar event data of the user of vehicle 102a and / or vehicle 102b. In this regard, charge sharing determination component 202 may determine the amount of charge available for transfer according to the predicted future driving applicable to the vehicle (and / or its respective user) that is to share its respective charge (e.g., based on one or more calendar events). In additional embodiments, the amount of charge available for transfer between vehicles herein (e.g., from vehicle 102a to vehicle 102b) may be determined, for example, by charge sharing determination component 202 based on the location of vehicle 102a (e.g., a first location) and the location of another vehicle (e.g., vehicle 102b) (e.g., a second location). In this regard, the amount of charge available for transfer between vehicles (e.g., from vehicle 102a to vehicle 102b) may be determined, for example, based on the discharge of battery 132 of vehicle 102a expected by traveling to the location of vehicle 102b.

[0039] In various embodiments, communication component 204 may establish a communication connection with another vehicle (e.g., vehicle 102b) based on the condition of battery 132 being determined to meet the charge sharing criteria. In one or more embodiments, the communication connection may utilize Wi-Fi, GSM, UMTS, WiMAX, enhanced GPRS, 5G, 6G, 3GPP LTE, 3GPP2 UMB, HSPA, Zigbee, and other 802.XX wireless technologies and / or traditional telecommunication technologies, NFC technology, SIP, RF4CE protocol, WirelessHART protocol, 6LoWPAN, Z-Wave, ANT, UWB standard protocol, V2V, V2E, and / or other proprietary and non-proprietary communication protocols. In various embodiments, the communication connection may include payment rate data that represents a payment rate for charge transfer from the vehicle to the other vehicle and / or payment terms for accepting the charge transfer. In additional embodiments, the communication connection may include payment method data that represents a payment method applicable to the charge transfer from the vehicle to the other vehicle. In further embodiments, the communication connection may include charging port connector data that represents the type of charging port or cable that can be used for charge transfer from the vehicle to the other vehicle. In yet further embodiments, the communication connection may include location data that represents the location of vehicle 102a, vehicle 102b, or another vehicle. In additional embodiments, the communication connection may include the amount of charge available for sharing.

[0040] In various embodiments, the navigation component 206 may generate a route from the location of a vehicle (e.g., vehicle 102a) (e.g., a first location) to the location of another vehicle (e.g., vehicle 102b) (e.g., a second location) (e.g., see route 502 on map 500 as shown in Figure 5 response to the establishment of a communication connection (e.g., by communication component 204) between the vehicles (e.g., between vehicle 102a and vehicle 102b). In some embodiments, the route may be presented to the user of vehicle 102a (e.g., via the user interface of vehicle 102a). In other embodiments, vehicle 102a may autonomously navigate to vehicle 102b (e.g., via route 502).

[0041] In various embodiments, the charge transfer component 208 may initiate a charge transfer from vehicle 102a to another vehicle (e.g., vehicle 102b) based on determining that a charge transfer criterion has been met. In various cases, such a charge transfer criterion may include establishing an electrical connection between the vehicles herein (e.g., connecting via charging cable 306). In another embodiment, such a charge transfer criterion may include a successful payment transfer (e.g., between the vehicles herein). In further embodiments, such a charge transfer criterion may include defined security checks and / or user confirmation (e.g., via the user interface of the vehicles herein).

[0042] In another embodiment, the charge sharing determination component 202 may determine whether charge sharing request criteria applicable to a vehicle (e.g., a first vehicle) (e.g., vehicle 102a) are met. Such charge sharing request criteria may include, for example, determining (e.g., by the charge sharing determination component 202) that the vehicle herein is not within the driving range of a charging station (e.g., based on remaining charge and / or other suitable factors). In a further embodiment, such charge sharing request criteria may include user input and / or user confirmation (e.g., via a user interface of the vehicle herein). In this regard, the request component 210 may generate a charge sharing request from the first vehicle (e.g., vehicle 102a) to the second vehicle (e.g., vehicle 102b) in response to determining that the charge sharing request criteria are met. In various embodiments, the communication component 204 may send the charge sharing request from the first vehicle (e.g., vehicle 102a) to the second vehicle (e.g., vehicle 102b). In one or more embodiments, the charge sharing request may include location information applicable to the first vehicle (e.g., vehicle 102a). In additional embodiments, the charge sharing request may include payment rate data representing a payment rate for charge transfer from the second vehicle (e.g., vehicle 102b) to the first vehicle (e.g., vehicle 102a). In additional embodiments, the charge sharing request may include charge port connector data representing the type of charge port (e.g., charge port 302a or 302b) or cable (e.g., cable 306) available for charge transfer from the second vehicle (e.g., vehicle 102b) to the first vehicle (e.g., vehicle 102a). In additional embodiments, the charge sharing request may include the amount of charge requested by the first vehicle (e.g., vehicle 102a).

[0043] In another embodiment, the communication component 204 may receive a charge sharing request from a vehicle (e.g., a first vehicle) (e.g., Figure 4 vehicle 102c in). In this regard, Figure 4 Scenario 400 of depicts bidirectional charging via a bidirectional charging station 402 that may be electrically coupled to one or more vehicles herein (e.g., vehicles 102c, 102d, 102e, and / or 102f) via multiple cables (e.g., cables 404c, 404d, 404e, and / or 404f). Then, the charge sharing determination component 202 may determine, based on the charge sharing request, the second vehicle (e.g., Figure 4of the vehicle 102d). Then, based on determining that the charge sharing criteria are met, the charge transfer component 208 can initiate a charge transfer from the second vehicle (e.g., vehicle 102d) to the first vehicle (e.g., vehicle 102c) (e.g., via the bi-directional charging station 402). In a further embodiment, the charge transfer component 208 can initiate a second charge transfer from a third vehicle (e.g., vehicle 102e) to the first vehicle (e.g., vehicle 102c) (e.g., via the bi-directional charging station 402) while the above charge transfer is taking place based on determining that a second charge sharing criteria is met. In various embodiments, the charge sharing criteria herein (e.g., the first charge sharing criteria and / or the second charge sharing criteria) can be based on the vehicles herein including a threshold level of (e.g., shareable) remaining charge.

[0044] Figure 6 FIG. 4 shows a flowchart of a process 600 associated with vehicle charge sharing and communication in accordance with one or more embodiments described herein. At 602, the process 600 can include determining (e.g., via the charge sharing determination component 202) whether the condition of the battery 132 of the vehicle 102a meets the charge sharing criteria applicable to the charge sharing request based on a charge sharing request from another vehicle (e.g., vehicle 102b) different from the vehicle (e.g., vehicle 102a). At 604, if the charge sharing criteria are met (e.g., “yes” at 604), the process can proceed to 606. If the charge sharing criteria are not met at 604 (e.g., “no” at 604), the process can return to 602. At 606, the process 600 can include establishing (e.g., via the communication component 204) a communication connection with another vehicle (e.g., vehicle 102b) based on the condition of the battery 132 being determined to meet the charge sharing criteria.

[0045] Figure 7FIG. 700 is a flowchart showing a process associated with vehicle charge sharing and communication according to one or more embodiments described herein. At 702, process 700 may include determining (e.g., by charge sharing determination component 202) whether a charge sharing request criterion applicable to a first vehicle (e.g., vehicle 102a) is met. At 704, if the charge sharing request criterion is met (e.g., “yes” at 704), the process may proceed to 706. If the charge sharing request criterion is not met at 704 (e.g., “no” at 704), the process may return to 702. At 706, process 700 may include generating (e.g., by request component 210) a charge sharing request in response to determining that the charge sharing request criterion is met, the request to be sent from the first vehicle (e.g., vehicle 102a) to a second vehicle different from the first vehicle (e.g., vehicle 102b).

[0046] Figure 8 FIG. 800 is a flowchart showing a process associated with vehicle charge sharing and communication according to one or more embodiments described herein. At 802, process 800 may include receiving (e.g., via communication component 204) from a first vehicle (e.g., vehicle 102c) a charge sharing request by a system including a processor (e.g., bidirectional charging station 402). At 804, process 800 may include determining (e.g., by charge sharing determination component 202) by the system (e.g., bidirectional charging station 402) a second vehicle (e.g., vehicle 102d) based on the charge sharing request, from which charge is to be supplied to the first vehicle (e.g., vehicle 102c) via the system. At 806, if the charge sharing criterion is met (e.g., “yes” at 806), the process may proceed to 808. If the charge sharing request criterion is not met at 806 (e.g., “no” at 806), the process may return to 804. At 808, process 800 may include initiating (by charge transfer component 208) by the system (e.g., bidirectional charging station 402) a charge transfer from the second vehicle (e.g., vehicle 102d) via the system (e.g., bidirectional charging station 404) to the first vehicle (e.g., vehicle 102c) based on determining that the charge sharing criterion is met.

[0047] The systems described herein can be coupled (e.g., communicatively, electrically, operationally, optically, inductively, acoustically, etc.) to one or more local or remote (e.g., external) systems, sources, and / or devices (e.g., electronic control units (ECUs), classical and / or quantum computing devices, communication devices, etc.). For example, system 100 (or other systems, controllers, processors, etc.) can be coupled to one or more local or remote (e.g., external) systems, sources, and / or devices using a data cable (e.g., high-definition multimedia interface (HDMI), recommended standard (RS), Ethernet cable, etc.) and / or one or more wired networks described below (e.g., communicatively, electrically, operationally, optically, etc.).

[0048] In some embodiments, the systems herein can be coupled via a network (e.g., communicatively, electrically, operationally, optically, inductively, acoustically, etc.) to one or more local or remote (e.g., external) systems, sources, and / or devices (e.g., electronic control units (ECUs), classical and / or quantum computing devices, communication devices, etc.). In these embodiments, such a network can include one or more wired and / or wireless networks, including, but not limited to, cellular networks, wide area networks (WANs) (e.g., the Internet) and / or local area networks (LANs). For example, system 100 can communicate with one or more local or remote (e.g., external) systems, sources, and / or devices, such as computing devices using such a network, which can include almost any desired wired or wireless technology, including, but not limited to: powerline Ethernet, VHF, UHF, AM, wireless fidelity (Wi-Fi), fiber optic communication, global system for mobile communications (GSM), universal mobile telecommunications system (UMTS), worldwide interoperability for microwave access (WiMAX), enhanced general packet radio service (“enhanced” GPRS), 3rd Generation Partnership Project (“3GPP”) long term evolution (“LTE”), 3rd Generation Partnership Project 2 (“3GPP2”) ultra mobile broadband (“UMB”), high speed packet access (“HSPA”), Zigbee and other 802.XX wireless technologies and / or legacy telecommunications technologies, session initiation protocol (“SIP”), RF4CE protocol, WirelessHART protocol, L-band voice or data messaging, 6LoWPAN (IPv6-based low power wireless personal area network), Z-Wave, ANT, ultra-wideband (“UWB”) standard protocol, and / or other proprietary and non-proprietary communication protocols. In this example, system 100 can thus include hardware (e.g., central processing unit (CPU), transceiver, decoder, antenna (e.g., ultra-wideband (UWB) antenna, Low energy (BLE) antennas, etc.), quantum hardware, quantum processors, etc.), software (e.g., a set of threads, a set of processes, executing software, quantum pulse scheduling, quantum circuits, quantum gates, etc.) or a combination of hardware and software to facilitate information communication between the systems herein and remote (e.g., external) systems, sources, and / or devices (e.g., computing and / or communication devices such as smartphones, smartwatches, wireless earphones).

[0049] The systems herein may include one or more computer and / or machine-readable, writable, and / or executable components and / or instructions that, when executed by a processor (e.g., processing unit 116 which may include a classical processor, a quantum processor, etc.), may facilitate the execution of operations defined by these components and / or instructions. Additionally, in many embodiments, as described herein, regardless of whether reference is made to the various figures of the present disclosure, any component associated with the systems herein may include one or more computer and / or machine-readable, writable, and / or executable components and / or instructions that, when executed by a processor, may facilitate the execution of operations defined by these components and / or instructions. Thus, according to many embodiments, the systems herein and / or any component associated therewith disclosed herein may use a processor (e.g., processing unit 116) to execute such computer and / or machine-readable, writable, and / or executable components and / or instructions to facilitate the execution of one or more operations described herein with reference to the systems herein and / or with reference to any such component associated therewith.

[0050] The systems herein may include any type of system, device, machine, apparatus, component, and / or instrument that includes a processor and / or can communicate with one or more local or remote electronic systems and / or one or more local or remote devices via a wired and / or wireless network. All such embodiments are contemplated. For example, a system (e.g., system 100 or any other system or device described herein) may include a computing device, a general-purpose computer, a field-programmable gate array, an AI accelerator application-specific integrated circuit, a special-purpose computer, an on-board computing device, a communication device, an on-board communication device, a server device, a quantum computing device (e.g., a quantum computer), a tablet computing device, a handheld device, a server-class computer machine and / or database, a laptop, a notebook computer, a desktop computer, a wearable device, an Internet of Things device, a phone, a smartphone, a consumer appliance and / or instrument, an industrial and / or commercial device, a digital assistant, a multimedia Internet phone, a multimedia player, and / or another type of device.

[0051] To provide additional background for the various embodiments described herein, Figure 9The following discussion is intended to provide a brief, general description of a suitable computing environment 900 in which various embodiments of the embodiments described herein may be implemented. While the embodiments have been described above in the general context of computer-executable instructions that may run on one or more computers, those skilled in the art will recognize that these embodiments may also be implemented in conjunction with other program modules and / or as a combination of hardware and software.

[0052] Generally, program modules include routines, programs, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In addition, those skilled in the art will understand that the various methods may be practiced with other computer system configurations, including single-processor or multi-processor computer systems, minicomputers, mainframe computers, Internet of Things (IoT) devices, distributed computing systems, and personal computers (e.g., ruggedized personal computers), field programmable gate arrays, handheld computing devices, microprocessor-based or programmable consumer electronics, etc., each of which may be operatively coupled to one or more associated devices.

[0053] The embodiments shown herein may also be implemented in a distributed computing environment where certain tasks are performed by remote processing devices linked through a communications network. In a distributed computing system, program modules may be located in both local and remote memory storage devices.

[0054] Computing devices generally include a variety of media, which may include computer-readable storage media, machine-readable storage media, and / or communication media, the two terms being used in different ways herein as described below. Computer-readable storage media or machine-readable storage media can be any available storage media accessible by a computer, including volatile and non-volatile media, removable and non-removable media. By way of example and not limitation, computer-readable storage media or machine-readable storage media can be implemented in conjunction with any method or technology for storing information (e.g., computer-readable or machine-readable instructions, program modules, structured data, or unstructured data).

[0055] A computer-readable storage medium may include, but is not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other storage technologies, compact disc read-only memory (CDROM), digital versatile disc (DVD), Blu-ray disc (BD) or other optical disc storage devices, magnetic tape cartridges, magnetic tape, magnetic disk storage or other magnetic storage devices, solid state drives or other solid state storage devices, or other tangible and / or non-transitory media that can be used to store the desired information. In this regard, the terms "tangible" or "non-transitory" as applied to storage devices, memories or computer-readable media herein shall be understood to exclude only propagating transient signals per se as a modifier, and do not relinquish rights to all standard storage devices, memories or computer-readable media that do not only propagate transient signals themselves.

[0056] The computer-readable storage medium can be accessed by one or more local or remote computing devices, for example, via an access request, query or other data retrieval protocol, for performing various operations on the information stored on the medium.

[0057] A communication medium typically embodies computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal (e.g., a modulated data signal such as a carrier wave or other transmission mechanism), and includes any information delivery or transmission medium. The term "(one or more) 'modulated data signal'" refers to a signal in which one or more of its characteristics are set or changed in order to encode information in one or more signals. By way of example and not limitation, communication media include wired media such as a wired network or a direct wired connection, and wireless media such as acoustic, RF, optical, infrared and other wireless media.

[0058] Referring again to Figure 9 , an example environment 900 for implementing various embodiments of the aspects described herein includes a computer 902, which includes a processing unit 904, a system memory 906, and a system bus 908. The system bus 908 couples system components including, but not limited to, the system memory 906 to the processing unit 904. The processing unit 904 can be any of a variety of commercially available processors, field programmable gate arrays, application specific integrated circuits for AI accelerators or other suitable processors. Dual microprocessors and other multiprocessor architectures can also be used as the processing unit 904.

[0059] The system bus 908 can be any of several types of bus structures, which can also be interconnected to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory 906 includes a ROM 910 and a RAM 912. The basic input / output system (BIOS) can be stored in non-volatile memory such as ROM, erasable programmable read-only memory (EPROM), EEPROM, and the BIOS contains basic routines that help transfer information between components within the computer 902, such as during startup. The RAM 912 can also include high-speed RAM, such as static RAM for caching data. It is worth noting that a unified extensible firmware interface can be used herein.

[0060] The computer 902 also includes an internal hard disk drive (HDD) 914 (e.g., EIDE, SATA), one or more external storage devices 916 (e.g., a floppy disk drive (FDD) 916, a memory stick or flash drive reader, a memory card reader, etc.), and an optical disc drive 920 (e.g., which can read from or write to a disk 922 such as a CD-ROM disc, a DVD, a BD, etc.). Although the internal HDD 914 is shown as being located within the computer 902, the internal HDD 914 can also be configured for external use in a suitable rack (not shown). Additionally, although not shown in the environment 900, a solid-state drive (SSD) can be used in addition to or instead of the HDD 914. The HDD 914, the external storage device 916, and the optical disc drive 920 can be connected to the system bus 908 via an HDD interface 924, an external storage device interface 926, and an optical disc drive interface 928, respectively. The interface 924 for external drive implementations can include at least one or both of the universal serial bus (USB) and the Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external drive connection technologies are also contemplated within the embodiments described herein.

[0061] The drives, along with their associated computer-readable storage media, provide non-volatile storage of data, data structures, computer-executable instructions, etc. For the computer 902, the drives and storage media are capable of storing any data in a suitable digital format. Although the above description of computer-readable storage media refers to the corresponding types of storage devices, those skilled in the art should understand that other types of storage media that are computer-readable, whether currently existing or developed in the future, can also be used in the exemplary operating environment. Additionally, any such storage media can contain computer-executable instructions for performing the methods described herein.

[0062] Many program modules can be stored in the drive and RAM 912, including an operating system 930, one or more application programs 932, other program modules 934, and program data 936. All or part of the operating system, application programs, modules, and / or data can also be cached in RAM 912. The systems and methods described herein can be implemented using various commercially available operating systems or combinations of operating systems.

[0063] Computer 902 can optionally include emulation technology. For example, a hypervisor (not shown) or other intermediary can simulate the hardware environment of operating system 930, and the simulated hardware can optionally be different from Figure 9 the hardware shown therein. In such an embodiment, operating system 930 can include one of a plurality of virtual machines (VMs) hosted on computer 902. Additionally, operating system 930 can provide a runtime environment, such as a Java runtime environment or a.NET framework, for application programs 932. A runtime environment is a consistent execution environment that allows application programs 932 to run on any operating system that includes the runtime environment. Similarly, operating system 930 can support containers, and application programs 932 can be in the form of containers, which are lightweight, independent, executable software packages that include, for example, code, runtime, system tools, system libraries, and application settings.

[0064] Furthermore, computer 902 can enable a security module, such as a Trusted Platform Module (TPM). For example, for a TPM, the boot component hashes the boot component in a timely manner before loading the next boot component and waits for the result to match a security value. This process can occur at any layer in the code execution stack of computer 902, for example, applied at the application execution level or the operating system (OS) kernel level, thereby achieving security in code execution at any level.

[0065] The user can input commands and information into computer 902 through one or more wired / wireless input devices, such as a keyboard 938, a touch screen 940, and a pointing device such as a mouse 942. Other input devices (not shown) can include a microphone, an infrared (IR) remote control, a radio frequency (RF) remote control or other remote controls, a joystick, a virtual reality controller and / or a virtual reality head-mounted display device, a gamepad, a stylus, an image input device (such as a camera), a gesture sensor input device, a vision motion sensor input device, an emotion or face detection device, a biometric input device (such as a fingerprint or iris scanner), etc. These and other input devices are typically connected to the processing unit 904 through an input device interface 944 that can be coupled to the system bus 908, but can also be connected through other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR interface, Interfaces and the like.

[0066] A monitor 946 or other type of display device can also be connected to the system bus 908 via an interface (such as a video adapter 948). In addition to the monitor 946, a computer typically includes other peripheral output devices (not shown), such as speakers, printers, and the like.

[0067] The computer 902 can operate in a networked environment using logical connections via wired and / or wireless communication to one or more remote computers, such as the remote computer 950. The remote computer 950 can be a workstation, server computer, router, personal computer, portable computer, microprocessor-based entertainment device, peer device, or other common network node, and generally includes many or all of the elements described with respect to the computer 902, but for the sake of brevity, only the memory / storage device 952 is shown. The depicted logical connections include wired / wireless connections to a local area network (LAN) 954 and / or a larger network, such as a wide area network (WAN) 956. Such LAN and WAN network environments are common in offices and companies and facilitate enterprise-wide computer networks, such as intranets, all of which can be connected to a global communication network, such as the Internet.

[0068] When used in a LAN network environment, the computer 902 can be connected to the local network 954 via a wired and / or wireless communication network interface or adapter 958. The adapter 958 can facilitate wired or wireless communication to the LAN 954, which can also include a wireless access point (AP) disposed thereon for communicating with the adapter 958 in a wireless mode.

[0069] When used in a WAN network environment, the computer 902 can include a modem 960, or can be connected to a communication server on the WAN 956 in other ways for establishing communication via the WAN 956, such as via the Internet. The modem 960 can be an internal or external wired or wireless device and can be connected to the system bus 908 via the input device interface 944. In a network environment, program modules depicted with respect to the computer 902 or portions thereof can be stored in the remote memory / storage device 952. It should be understood that the network connections shown are examples, and other ways of establishing communication links between computers can be used.

[0070] When used in a LAN or WAN network environment, computer 902 can access a cloud storage system or other network-based storage systems as an addition to or an alternative to the external storage device 916 described above. Generally, the connection between computer 902 and the cloud storage system can be established through LAN 954 or WAN 956, for example, through adapter 958 or modem 960 respectively. After connecting computer 902 to the associated cloud storage system, the external storage device interface 926 can, with the help of adapter 958 and / or modem 960, manage the storage devices provided by the cloud storage system in the same way as other types of external storage devices. For example, the external storage device interface 926 can be configured to provide access to cloud storage sources as if these sources were physically connected to computer 902.

[0071] Computer 902 can be operable to communicate with any wireless device or entity operatively disposed in wireless communication, such as a printer, scanner, desktop and / or portable computer, portable data assistant, communication satellite, any device or location associated with a wirelessly detectable tag (e.g., kiosk, newsstand, store shelf, etc.) and a telephone. This can include Wi-Fi and wireless technologies. Thus, the communication can be of a predefined structure like a traditional network or an ad hoc communication between at least two devices.

[0072] Now referring to Figure 10 , a schematic block diagram of a computing environment 1000 in accordance with the present specification is shown. System 1000 includes one or more clients 1002 (e.g., computers, smartphones, tablets, cameras, PDAs). The clients 1002 can be hardware and / or software (e.g., threads, processes, computing devices). For example, the clients 1002 can accommodate small text files (cookies) and / or associated context information by adopting a specification.

[0073] System 1000 also includes one or more servers 1004. The servers 1004 can also be hardware or a combination of hardware and software (e.g., threads, processes, computing devices). The servers 1004 can accommodate threads to perform the conversion of media items by adopting aspects of the present disclosure. A possible communication between the clients 1002 and the servers 1004 can be in the form of data packets suitable for transmission between two or more computer processes, where the data packets can include encoded analysis top spaces and / or inputs. For example, the data packets can include small text files and / or associated context information. System 1000 includes a communication framework 1006 (e.g., a global communication network such as the Internet), which can be used to facilitate communication between the clients 1002 and the servers 1004.

[0074] Communication can be facilitated through wired (including fiber optic) and / or wireless technologies. Client 1002 is operatively connected to one or more client data storage devices 1008, which can be used to store information local to client 1002 (such as small text files and / or associated background information). Similarly, server 1004 is operatively connected to one or more server data storage devices 1010, which can be used to store information local to server 1004. Additionally, client 1002 can be operatively connected to one or more server data storage devices 1010.

[0075] In an exemplary embodiment, client 1002 can transmit an encoded file (e.g., an encoded media item) to server 1004. Server 1004 can store the file, decode the file, or send the file to another client 1002. It should be noted that, according to the present disclosure, client 1002 can also transmit an uncompressed file to server 1004 and server 1004 can compress the file and / or convert the file. Similarly, server 1004 can encode information and transmit the information to one or more clients 1002 via communication framework 1006.

[0076] The aspects shown in the present disclosure can also be implemented in a distributed computing environment where certain tasks are performed by remote processing devices linked by a communication network. In a distributed computing system, program modules can be located in both local and remote memory storage devices.

[0077] The above description includes non-limiting examples of various embodiments. Of course, it is not possible to describe every possible combination of components or methods for the purpose of describing the disclosed subject matter, and those skilled in the art will recognize that other combinations and permutations of various embodiments are possible. The disclosed subject matter is intended to cover all such changes, modifications, and variations that fall within the spirit and scope of the appended claims.

[0078] Regarding the various functions performed by the above components, devices, circuits, systems, etc., unless otherwise specified, the terms used to describe these components (including references to "means") are intended to also include any structure that performs the specified function of the component (e.g., a functional equivalent), even if not structurally equivalent to the disclosed structure. Additionally, although a particular feature of the disclosed subject matter may be disclosed only with respect to one of several embodiments, such feature can be combined with one or more other features of other embodiments, which may be desirable and advantageous for any given or particular application.

[0079] As used herein, the terms "exemplary" and / or "illustrative" are intended to mean serving as an example, instance, or illustration. To avoid doubt, the subject matter disclosed herein is not limited by these examples. Additionally, any aspect or design described herein as "exemplary" and / or "illustrative" is not necessarily to be construed as preferred or more advantageous than other aspects or designs, nor does it imply the exclusion of equivalent structures and techniques known to those skilled in the art. Further, in instances where the terms "comprising," "having," "including," and other similar words are used in the detailed description or claims, these terms are intended to be inclusive in a manner similar to the open transitional word "including" and do not exclude any additional or other elements.

[0080] The term "or" as used herein is intended to mean an inclusive "or" rather than an exclusive "or". For example, the phrase "A or B" is intended to include instances of A, B, and both A and B. Additionally, quantities in this application and the appended claims that are not qualified by a numerical modifier should generally be construed to mean "one or more" unless otherwise specified or clearly indicated as singular in context.

[0081] The term "set" as used herein does not include the empty set, i.e., a set with no elements. Thus, "sets" in this disclosure include one or more elements or entities. Similarly, the term "group" as used herein refers to an aggregation of one or more entities.

[0082] The description of the embodiments shown in this disclosure provided herein, including the description in the abstract, is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. While specific embodiments and examples are described herein for purposes of illustration, those skilled in the art will recognize that various modifications can be made within the scope of these embodiments and examples. In this regard, while the subject matter is described herein in connection with various embodiments and the corresponding drawings, it is understood that, where applicable, other similar embodiments can be used, or modifications and additions can be made to the described embodiments to perform the same, similar, alternative, or substitute functions of the disclosed subject matter without departing from the disclosed subject matter. Accordingly, the disclosed subject matter should not be limited to any single embodiment described herein but should be construed in breadth and scope in accordance with the following appended claims.

[0083] Other aspects of the invention are provided by the subject matter of the following clauses.

[0084] 1. A vehicle, comprising:

[0085] a memory storing computer-executable components; and

[0086] a processor executing the computer-executable components stored in the memory, wherein the computer-executable components include:

[0087] A charge sharing determination component that determines whether the condition of the battery of the vehicle meets a charge sharing standard applicable to the charge sharing request based on a charge sharing request from another vehicle different from the vehicle; and

[0088] A communication component that establishes a communication connection with the other vehicle based on determining that the condition of the battery meets the charge sharing standard.

[0089] 2. The vehicle according to any preceding clause, wherein the computer-executable component further comprises:

[0090] A navigation component that generates a route from a first location of the vehicle to a second location of the other vehicle in response to establishing a communication connection with the other vehicle.

[0091] 3. The vehicle according to any preceding clause, wherein the communication connection includes payment rate data, and the payment rate data represents a payment rate for charge transfer from the vehicle to the other vehicle.

[0092] 4. The vehicle according to any preceding clause, wherein the communication connection includes payment method data, and the payment method data represents a payment method applicable to charge transfer from the vehicle to the other vehicle.

[0093] 5. The vehicle according to any preceding clause, wherein the communication connection includes charging port connector data, and the charging port connector data represents the type of charging port or cable that can be used for charge transfer from the vehicle to the other vehicle.

[0094] 6. The vehicle according to any preceding clause, wherein the condition of the battery includes the charge state of the battery, and wherein the communication connection includes available charge data, and the available charge data represents the amount of charge available for transfer from the vehicle to the other vehicle.

[0095] 7. The vehicle according to any preceding clause, wherein the amount of charge available for transfer from the vehicle to the other vehicle is determined by the charge sharing determination component based on historical driving data applicable to the vehicle.

[0096] 8. The vehicle according to any preceding clause, wherein the amount of charge available for transfer from the vehicle to the other vehicle is determined by the charge sharing determination component based on calendar event data of a user applicable to the vehicle.

[0097] 9. The vehicle according to any preceding clause, wherein the amount of electric charge available for transfer from the vehicle to the other vehicle is determined by the charge sharing determination component based on the first position of the vehicle and the second position of the other vehicle.

[0098] 10. The vehicle according to any preceding clause, wherein the computer-executable component further comprises:

[0099] A charge transfer component that initiates a charge transfer from the vehicle to the other vehicle based on determining that a charge transfer criterion has been met.

[0100] 11. The vehicle described in clause 1 above, having any combination set of the vehicles described in clauses 2-10 above.

[0101] 12. A non-transitory machine-readable medium comprising executable instructions that, when executed by a processor, facilitate the execution of operations, the operations including:

[0102] Determining whether a charge sharing request criterion applicable to a first vehicle has been met; and

[0103] Generating a charge sharing request in response to determining that the charge sharing request criterion has been met, the charge sharing request to be sent from the first vehicle to a second vehicle different from the first vehicle.

[0104] 13. The non-transitory machine-readable medium according to any preceding clause, wherein the operations further include:

[0105] Sending the charge sharing request from the first vehicle to the second vehicle.

[0106] 14. The non-transitory machine-readable medium according to any preceding clause, wherein the charge sharing request includes location information applicable to the first vehicle.

[0107] 15. The non-transitory machine-readable medium according to any preceding clause, wherein the charge sharing request includes payment rate data, the payment rate data representing the payment rate for a charge transfer from the second vehicle to the first vehicle.

[0108] 16. The non-transitory machine-readable medium according to any preceding clause, wherein the charge sharing request includes charging port connector data, the charging port connector data representing the type of charging port or cable available for charge transfer from the second vehicle to the first vehicle.

[0109] 17. The non-transitory machine-readable medium according to any of the preceding clauses, wherein the charge sharing request includes the amount of charge requested by the first vehicle.

[0110] 18. The non-transitory machine-readable medium of clause 12 above, having any combination set of the non-transitory machine-readable media of clauses 13-17 above.

[0111] 19. A method, comprising:

[0112] Receiving, by a system including a processor, a charge sharing request from a first vehicle;

[0113] Based on the charge sharing request, determining, by the system, a second vehicle to supply charge to the first vehicle via the system; and

[0114] Initiating, by the system, a charge transfer from the second vehicle to the first vehicle via the system based on determining that the charge sharing criteria are met.

[0115] 20. The method according to any of the preceding clauses, wherein the charge transfer includes a first charge transfer, wherein the charge sharing criteria includes a first charge sharing criteria, and wherein the method further comprises:

[0116] Initiating, by the system, a second charge transfer from a third vehicle to the first vehicle via the system simultaneous with the first charge transfer based on determining that a second charge sharing criteria is met.

[0117] 21. The method according to any of the preceding clauses, wherein the system includes a bi-directional charging station.

[0118] 22. The method according to any of the preceding clauses, wherein the charge sharing criteria is based on the second vehicle including a threshold level of remaining charge.

[0119] 23. The method of clause 19 above, having any combination set of the methods of clauses 20-22 above.

Claims

1. A means of transport, comprising: a memory storing computer executable components; and a processor that executes the computer-executable components stored in the memory, wherein the computer-executable components include: a charge sharing determination component that determines, based on a charge sharing request from another vehicle different from the vehicle, whether a condition of the battery of the vehicle satisfies a charge sharing criterion applicable to the charge sharing request; and A communication component establishes a communication connection with the other vehicle based on determining that the condition of the battery satisfies the charge sharing criteria.

2. The vehicle of claim 1, wherein the computer executable components further comprise: A navigation component generates a route from a first location of the vehicle to a second location of the other vehicle in response to establishing a communication connection with the other vehicle.

3. The vehicle of claim 1, wherein the communication connection includes payment rate data indicating a payment rate for charge transfer from the vehicle to the other vehicle.

4. The vehicle of claim 1, wherein the communication connection includes payment method data indicating a payment method applicable to the charge transfer from the vehicle to the other vehicle.

5. The vehicle of claim 1, wherein the communication connection includes charging port connector data indicating a type of charging port or cable that can be used to transfer charge from the vehicle to the other vehicle.

6. The vehicle of claim 1, wherein the condition of the battery comprises a state of charge of the battery, and wherein the communication connection comprises available charge data representing an amount of charge available for transfer from the vehicle to the other vehicle.

7. The vehicle according to claim 6, wherein: An amount of charge available for transfer from the vehicle to the other vehicle is determined by the charge sharing determination component based on historical driving data applicable to the vehicles.

8. The vehicle according to claim 6, wherein: An amount of charge available for transfer from the vehicle to the other vehicle is determined by the charge share determination component based on calendar event data applicable to users of the vehicles.

9. The vehicle according to claim 6, wherein: An amount of charge available for transfer from the vehicle to the other vehicle is determined by the charge share determination component based on a first position of the vehicle and a second position of the other vehicle.

10. The vehicle of claim 1, wherein the computer executable components further comprise: A charge transfer component initiates a transfer of charge from the vehicle to the other vehicle based on a determination that a charge transfer criterion is satisfied.

11. A non-transitory machine-readable medium comprising executable instructions that, when executed by a processor, facilitate performance of operations comprising: determining whether charge sharing request criteria applicable to the first vehicle have been met; and A charge share request is generated in response to determining that the charge share request criteria are met, the charge share request to be sent from the first vehicle to a second vehicle different from the first vehicle.

12. The non-transitory machine-readable medium of claim 11, wherein the operations further comprise: The charge sharing request is sent from the first vehicle to the second vehicle.

13. The non-transitory machine-readable medium of claim 11, wherein the charge share request includes location information applicable to the first vehicle.

14. The non-transitory machine-readable medium of claim 11, wherein: The charge sharing request includes payment rate data indicating a payment rate for charge transfer from the second vehicle to the first vehicle.

15. The non-transitory machine-readable medium of claim 11, wherein the charge sharing request includes charge port connector data indicating a type of charge port or cable that can be used to transfer charge from the second vehicle to the first vehicle.

16. The non-transitory machine-readable medium of claim 11, wherein the charge share request comprises an amount of charge requested by the first vehicle.

17. A method comprising: receiving, by a system including a processor, a charge sharing request from a first vehicle; determining, by the system, a second vehicle that supplies charge to the first vehicle via the system based on the charge sharing request; and Based on determining that the charge sharing criteria are met, a charge transfer is initiated by the system from the second vehicle to the first vehicle via the system.

18. The method according to claim 17, wherein: The charge transfer comprises a first charge transfer, wherein the charge sharing criterion comprises a first charge sharing criterion, and wherein the method further comprises: Based on determining that a second charge sharing criterion is satisfied, a second charge transfer is initiated by the system from a third vehicle to the first vehicle via the system concurrently with the first charge transfer.

19. The method of claim 17, wherein the system comprises a bidirectional charging station.

20. The method of claim 17, wherein the charge sharing criteria is based on the second vehicle comprising a threshold level of remaining charge.

Images