WO2024253978A1 - Systèmes et procédés de charge de véhicules électriques avec des stations de charge dans divers modes de connectivité - Google Patents

Systèmes et procédés de charge de véhicules électriques avec des stations de charge dans divers modes de connectivité Download PDF

Info

Publication number
WO2024253978A1
WO2024253978A1 PCT/US2024/032145 US2024032145W WO2024253978A1 WO 2024253978 A1 WO2024253978 A1 WO 2024253978A1 US 2024032145 W US2024032145 W US 2024032145W WO 2024253978 A1 WO2024253978 A1 WO 2024253978A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
user device
check
charging
evse
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2024/032145
Other languages
English (en)
Inventor
Thomas Shaofeng SUN
Li Zhang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
AmpUp Inc
Original Assignee
AmpUp Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by AmpUp Inc filed Critical AmpUp Inc
Publication of WO2024253978A1 publication Critical patent/WO2024253978A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F15/00—Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity
    • G07F15/003—Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity for electricity
    • G07F15/005—Coin-freed apparatus with meter-controlled dispensing of liquid, gas or electricity for electricity dispensed for the electrical charging of vehicles
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60L—PROPULSION OF ELECTRICALLY-PROPELLED VEHICLES; SUPPLYING ELECTRIC POWER FOR AUXILIARY EQUIPMENT OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRODYNAMIC BRAKE SYSTEMS FOR VEHICLES IN GENERAL; MAGNETIC SUSPENSION OR LEVITATION FOR VEHICLES; MONITORING OPERATING VARIABLES OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRIC SAFETY DEVICES FOR ELECTRICALLY-PROPELLED VEHICLES
    • B60L53/00—Methods of charging batteries, specially adapted for electric vehicles; Charging stations or on-board charging equipment therefor; Exchange of energy storage elements in electric vehicles
    • B60L53/60—Monitoring or controlling charging stations
    • B60L53/62—Monitoring or controlling charging stations in response to charging parameters, e.g. current, voltage or electrical charge
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60L—PROPULSION OF ELECTRICALLY-PROPELLED VEHICLES; SUPPLYING ELECTRIC POWER FOR AUXILIARY EQUIPMENT OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRODYNAMIC BRAKE SYSTEMS FOR VEHICLES IN GENERAL; MAGNETIC SUSPENSION OR LEVITATION FOR VEHICLES; MONITORING OPERATING VARIABLES OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRIC SAFETY DEVICES FOR ELECTRICALLY-PROPELLED VEHICLES
    • B60L53/00—Methods of charging batteries, specially adapted for electric vehicles; Charging stations or on-board charging equipment therefor; Exchange of energy storage elements in electric vehicles
    • B60L53/60—Monitoring or controlling charging stations
    • B60L53/63—Monitoring or controlling charging stations in response to network capacity
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60L—PROPULSION OF ELECTRICALLY-PROPELLED VEHICLES; SUPPLYING ELECTRIC POWER FOR AUXILIARY EQUIPMENT OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRODYNAMIC BRAKE SYSTEMS FOR VEHICLES IN GENERAL; MAGNETIC SUSPENSION OR LEVITATION FOR VEHICLES; MONITORING OPERATING VARIABLES OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRIC SAFETY DEVICES FOR ELECTRICALLY-PROPELLED VEHICLES
    • B60L53/00—Methods of charging batteries, specially adapted for electric vehicles; Charging stations or on-board charging equipment therefor; Exchange of energy storage elements in electric vehicles
    • B60L53/60—Monitoring or controlling charging stations
    • B60L53/65—Monitoring or controlling charging stations involving identification of vehicles or their battery types
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60L—PROPULSION OF ELECTRICALLY-PROPELLED VEHICLES; SUPPLYING ELECTRIC POWER FOR AUXILIARY EQUIPMENT OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRODYNAMIC BRAKE SYSTEMS FOR VEHICLES IN GENERAL; MAGNETIC SUSPENSION OR LEVITATION FOR VEHICLES; MONITORING OPERATING VARIABLES OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRIC SAFETY DEVICES FOR ELECTRICALLY-PROPELLED VEHICLES
    • B60L53/00—Methods of charging batteries, specially adapted for electric vehicles; Charging stations or on-board charging equipment therefor; Exchange of energy storage elements in electric vehicles
    • B60L53/60—Monitoring or controlling charging stations
    • B60L53/66—Data transfer between charging stations and vehicles
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60L—PROPULSION OF ELECTRICALLY-PROPELLED VEHICLES; SUPPLYING ELECTRIC POWER FOR AUXILIARY EQUIPMENT OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRODYNAMIC BRAKE SYSTEMS FOR VEHICLES IN GENERAL; MAGNETIC SUSPENSION OR LEVITATION FOR VEHICLES; MONITORING OPERATING VARIABLES OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRIC SAFETY DEVICES FOR ELECTRICALLY-PROPELLED VEHICLES
    • B60L53/00—Methods of charging batteries, specially adapted for electric vehicles; Charging stations or on-board charging equipment therefor; Exchange of energy storage elements in electric vehicles
    • B60L53/60—Monitoring or controlling charging stations
    • B60L53/67—Controlling two or more charging stations
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60L—PROPULSION OF ELECTRICALLY-PROPELLED VEHICLES; SUPPLYING ELECTRIC POWER FOR AUXILIARY EQUIPMENT OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRODYNAMIC BRAKE SYSTEMS FOR VEHICLES IN GENERAL; MAGNETIC SUSPENSION OR LEVITATION FOR VEHICLES; MONITORING OPERATING VARIABLES OF ELECTRICALLY-PROPELLED VEHICLES; ELECTRIC SAFETY DEVICES FOR ELECTRICALLY-PROPELLED VEHICLES
    • B60L53/00—Methods of charging batteries, specially adapted for electric vehicles; Charging stations or on-board charging equipment therefor; Exchange of energy storage elements in electric vehicles
    • B60L53/60—Monitoring or controlling charging stations
    • B60L53/68—Off-site monitoring or control, e.g. remote control
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/02—Reservations, e.g. for tickets, services or events
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/326—Payment applications installed on the mobile devices
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327—Short range or proximity payments by means of M-devices
    • G06Q20/3276—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being read by the M-device
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327—Short range or proximity payments by means of M-devices
    • G06Q20/3278—RFID or NFC payments by means of M-devices
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/40—Business processes related to the transportation industry

Definitions

  • the disclosure generally relates to fields pertaining to charging of electric vehicles.
  • EVSE electric vehicle service equipment
  • chargers typically rely upon connected/online operations, in order to operate smoothly with respect to initiating and/or completing charging sessions.
  • flaws inherent to locations of EVSE unit installation can produce operational inefficiencies and poor user experiences, associated with poor connectivity and other factors.
  • there is a need in the field of electric vehicle charging for improved systems and methods for providing reliable, robust, and secure charging of electric vehicles.
  • FIGS. 1A-1B depict flowcharts and schematics of embodiments of a method for electric vehicle charging in different connectivity modes.
  • FIGS. 2A-2C depict variations of check-in request operations associated with a method and system for electric vehicle charging in different connectivity mode.
  • FIGURES 3A-3D depict an example of a workflow for initiating charging with respect to different connectivity modes of a user device involved in the charging process.
  • FIGURES 4A-4C depict variations of method steps involved in initiating a charging session when connectivity is below a threshold level.
  • FIGURE 5 depicts an embodiment of a system for electric vehicle charging in different connectivity modes.
  • FIGURE 6 depicts an embodiment of a computer system involved in executing a method for electric vehicle charging in different connectivity modes.
  • the invention(s) provide a mechanism for charging session initiation and/or completion for chargers that are subject to low connectivity or are otherwise offline (e.g., in underground garages or sites, in geographic locations having low cellular signal, etc.), thereby streamlining charging operations and providing an improved user experience.
  • the invention(s) can provide solutions to users of applications for charging electric vehicles, where such users may encounter issues with charging stations, such as hardware faults, internet connectivity issues, and/ or mismatches between plugs and chargers/EVSE units. These issues may cause inconvenience and reduce the effectiveness of the charging process.
  • the invention(s) provide users with mechanisms for easily reporting any issues with charging stations/EVSE units, quickly resolving hardware faults, receiving notifications about connectivity with telecommunications networks, and selecting a correct charging plug to avoid charging errors.
  • the invention(s) also provide a mechanism for energy output/use optimization and load management for a set of chargers/EVSE units at a site associated with low connectivity of offline operations.
  • the invention(s) provide solutions that support broader charging infrastructure adoption and while enabling participation in utility demand response programs by site and/or charger managers.
  • the invention(s) provide charging architecture, with software and hardware components, for utilities companies to properly distribute load and/or shed load in response to spikes in demand, non-uniform demand (e.g., in relation to time of day, in relation to seasons, in relation to weather-related events, etc.), increases in demand due to additional vehicles, systems, and devices requiring power, and/or other factors, even when chargers are offline or are operating in low connectivity modes.
  • non-uniform demand e.g., in relation to time of day, in relation to seasons, in relation to weather-related events, etc.
  • increases in demand due to additional vehicles, systems, and devices requiring power, and/or other factors, even when chargers are offline or are operating in low connectivity modes.
  • the invention(s) also include systems and methods for management of load distribution and shedding, with subsystems configured to properly incentivize end users to behave in manners that reduce demand under various circumstances.
  • the invention(s) also include architecture for generation of training and test data, for training of models, in various phases, to optimize control of load distribution and shedding in response to a wide range of demand events, and/or in relation to offline charger modes.
  • the invention(s) also support green initiatives, with respect to demand shedding, adoption of clean electricity sources, and implementation of protocols to promote use of clean electricity and improved user behaviors to reduce carbon emissions.
  • the invention(s) can additionally or alternatively include electronic elements with associated software and/or firmware architecture for prevention of hacking and/or forms of cyber attacks against utilities companies and infrastructures.
  • invention(s) can additionally or alternatively provide other suitable benefits.
  • Methods and systems described can additionally or alternatively be implemented and/or integrated with embodiments, variations, and examples of invention(s) described in U.S. App. No. 16/983,175, which is herein incorporated in its entirety by this reference.
  • an embodiment of a method 100 for charging an electric vehicle at an Electric Vehicle Service Equipment (EVSE) unit comprises: receiving a check-in request at the EVSE unit by a user associated with the electric vehicle S110, wherein the check-in request comprises a communication between the EVSE unit and a user device of the user, the communication comprising a set of identifying parameters; upon verification of the set of identifying parameters of the checkin request, initiating charging, through a cable coupled between the EVSE unit and the electric vehicle S120.
  • EVSE Electric Vehicle Service Equipment
  • the method 100 can include supporting offline operation modes associated with either or both the EVSE unit and the user device (e.g., modes where signal strength for communications with a wireless network are below a threshold level).
  • the user device associated with Steps S110 and S120 can be linkable to a wireless network (e.g., telecommunications network) and operate in an online mode and in an offline mode, where linking with the wireless network is involved in relation to verification of the set of identifying parameters of the check-in request.
  • a wireless network e.g., telecommunications network
  • the user device In the online mode, the user device is connected to the wireless network, and in the offline mode, the user device is attempting communication with the wireless network, with signal strength below a threshold level.
  • Transitioning to the offline mode can occur when the user is in a cellular dead zone (e.g., in an underground parking garage), when there is a disruption in connectivity caused by components of the wireless network, when the user device is switched to the offline mode (e.g., in "Airplane mode"), or in another suitable manner.
  • a cellular dead zone e.g., in an underground parking garage
  • the offline mode e.g., in "Airplane mode”
  • Embodiments of the method 100 function to provide a mechanism for charging session initiation and/or completion for chargers that are subject to low connectivity or are otherwise offline (e.g., in underground garages or sites, in geographic locations having low cellular signal, etc.), thereby streamlining charging operations and providing an improved user experience.
  • Embodiments of the method 100 also function to provide a mechanism for energy output/ use optimization and load management for a set of chargers/EVSE units at a site associated with low connectivity of offline operations.
  • the invention(s) provide solutions that support broader charging infrastructure adoption and while enabling participation in utility demand response programs by site and/ or charger managers.
  • the method too functions to provide charging architecture solutions, with software and hardware components, for utilities companies to properly distribute load and/ or shed load in response to spikes in demand, non-uniform demand (e.g., in relation to time of day, in relation to seasons, in relation to weather-related events, etc.), increases in demand due to additional vehicles, systems, and devices requiring power, and/ or other factors, even when chargers are offline or are operating in low connectivity modes.
  • non-uniform demand e.g., in relation to time of day, in relation to seasons, in relation to weather-related events, etc.
  • Step Sno recites: receiving a check-in request at the EVSE unit by a user associated with the electric vehicle Siio, wherein the check-in request comprises a communication between the EVSE unit and a user device of the user.
  • Step Sno functions to detect a check-in request at the EVSE unit for a scheduled charging session (e.g., a reservation for a charging station at the location in advance) or an ad-hoc charging session, in order to initiate charging in a user-focused manner (e.g., user-friendly manner) in subsequent steps of the method 100.
  • Step Sno can include receiving a check-in request during offline connectivity modes and/or during online connectivity modes of either or both the EVSE unit and the user device of the user, where offline connectivity modes characterize operational states of user devices and/or EVSE units that have signal strength for connecting to a telecommunications network or other wireless/ wired network below a threshold level.
  • Charging sites that are subject to low connectivity or are otherwise offline can be associated with one or more of: underground garages or sites, sites having shielding objects (e.g., walls, high buildings, etc.) in the vicinity of such sites, geographic locations having low cellular signal, offline modes (e.g., Airplane mode, standalone mode, flight mode, etc.) of user devices, low-battery charge operation modes of user devices involving reduced functionality of such user devices, disturbances to telecommunications networks hardware and/ or software components, shielding of user devices, and/ or other factors.
  • underground garages or sites sites having shielding objects (e.g., walls, high buildings, etc.) in the vicinity of such sites, geographic locations having low cellular signal, offline modes (e.g., Airplane mode, standalone mode, flight mode, etc.) of user devices, low-battery charge operation modes of user devices involving reduced functionality of such user devices, disturbances to telecommunications networks hardware and/ or software components, shielding of user devices, and/ or other factors.
  • shielding objects
  • the EVSE unit can still be structured to communicate with the platform for electric vehicle charging, through the telecommunications network (or other wireless/wired network), using hardware components (e.g., Ethernet, a router) that have a cellular Subscriber Identity Module (SIM) component wired to a location with suitable signal strength (i.e., signal strength above a threshold level).
  • hardware components e.g., Ethernet, a router
  • SIM Subscriber Identity Module
  • Step Sno charging can be initiated and executed according to embodiments, variations, and examples of methods described in one or more of: U.S. Patent Application No. 16/983,175 filed on August 3, 2020, and U.S. Patent Application No. 17/163,638 filed on February 1, 2021, each of which is incorporated herein in its entirety by this reference.
  • the method 100 can still be executed according to methods described herein.
  • the check-in request can involve radio-frequency identification (RFID) elements and communication protocols by which the EVSE unit and the user device operate to transmit and receive digital data.
  • Step S110 can include promoting communication between a radio-frequency identification (RFID) element of the user device of the user, and the EVSE unit.
  • RFID radio-frequency identification
  • the RFID element(s) can include a transponder, a receiver, and a transmitter, where an RFID tag of a user device is structured to transmit digital data in response to being triggered by an interrogation pulse of a reader (e.g., of the EVSE unit/ charger).
  • an RFID tag of an EVSE unit/ charger can be structured to transmit digital data in response to being triggered by an interrogation pulse of a reader (e.g., of the user device).
  • RFID tags implemented can include passive tags that are powered by interrogating radio waves of readers, and/or active tags that are coupled to a power source (e.g., battery), with capability for greater range communications.
  • RFID tags implemented can be read-only, or have read/ write functionality.
  • RFID systems associated with the check-in request of Step S110 can be passive reader active tag (PRAT) systems, active reader passive tag (ARPT), or active reader active tag (ARAT) systems.
  • RFID systems can operate in low frequency bands (e.g., 120-150 kHz), high frequency bands (e.g., 13.56 MHz), ultrahigh frequency bands (e.g., greater than 100 MHz), microwave bands (e.g., greater than 2000 MHz), mm-wave bands, teraherz bands (e.g., as in teraherz frequency identification).
  • Exemplary RFID elements can be incorporated into user devices and objects, including one or more of: employee badges (e.g., a fleet employee badge, a badge associated with a fleet operation), credit cards, driver’s licenses, public transportation passes, other cards, stickers, identification objects (e.g., ID cards, passports, etc.), electronic devices (e.g., mobile devices), keys (e.g., lodging key such as a hotel key, car key), fobs, clothing, or other objects (e.g., implanted RFID elements).
  • employee badges e.g., a fleet employee badge, a badge associated with a fleet operation
  • identification objects e.g., ID cards, passports, etc.
  • electronic devices e.g., mobile devices
  • keys e.g., lodging key such as a hotel key, car key
  • fobs clothing
  • implanted RFID elements implanted RFID elements
  • the check-in request can involve near-field communication (NFC) elements and communication protocols by which the EVSE unit and the user device operate to transmit and receive digital data.
  • receiving the check-in request in Step S110 can include promoting communication between a near-field communication (NFC) element of the user device of the user, and the EVSE unit.
  • NFC near-field communication
  • the NFC elements can include inductive coupling elements (e.g., antennas) between NFC-enabled EVSE units and NFC-enabled user devices, operating according to ISO/IEC 18092 / ECMA-340 standards, ISO/IEC 21481 / ECMA-352 standards, ISO/IEC 14443 standards, FeliCa standards, or other standards.
  • the check-in request at the EVSE unit can involve a communication between an active initiator device and either a passive target device that can modulate an incident carrier field of the initiator device, or an active target device that can generate its own field.
  • active NFC devices such NFC devices can include NFC card emulation functionality, NFC reader/writer functionality, and NFC peer-to-peer functionality for ad hoc communications.
  • the check-in request can involve entry of a code corresponding to the set of identifying parameters, a user account, and/ or a charging session of the user, where entry of the code can be provided at a user interface (e.g., key pad, touch screen, etc.) of the EVSE unit and/or the user device (e.g., through user interface described below).
  • a user interface e.g., key pad, touch screen, etc.
  • the check-in request can involve tag scanning, where exemplary tags can include quick response (QR) codes or other barcodes that are machine-readable (e.g., optical images) that encode information.
  • QR quick response
  • Encoded information can include data for identifiers, where the identifiers can point to platform applications or websites to perform a process.
  • Barcodes can be structured to encode according to numeric, alphanumeric, byte/binary, and/ or kanji modes.
  • one or more barcodes can be coupled to the EVSE unit, which can be scanned by a camera or other reader of the user device, as a step to initiate charging after verifying identifying parameters of the check-in request, through the platform, according to Step S120 (described in further detail below).
  • the check-in request communication between devices can include a set of identifying parameters.
  • Exemplary identifying parameters can include one or more of: an identifier (e.g., international mobile equipment identity (IMEI), serial number, serial code, etc.) of the EVSE unit and/or the user device; parameters of signals transmitted between an RFID transmitter and a receiver; parameters of signals transmitted between an NFC transmitter and a receiver; EVSE unit station identifiers (e.g., in relation to a charging site, etc.); parameters of the intended charging session (e.g., date, time, duration, user, electric vehicle, etc.); parameters of the electric vehicle being charged, private keys of the EVSE unit and public keys for authentication of a charging session, where private and public keys are related by a hashing function; an electronic product code (EPC); or other identifying parameters.
  • an identifier e.g., international mobile equipment identity (IMEI), serial number, serial code, etc.
  • IMEI international mobile equipment identity
  • serial code serial code
  • Identifying parameters can be static, or can be dynamically changing for enhanced security of charging sessions.
  • receiving the check-in request can include providing a user interface S112, which can function to provide users with means to communicate with a platform for coordinating charging sessions between EVSE units and users through associated user devices, and/or otherwise using reservation requests, check-in requests, payment, authentication, and/ or other suitable processes.
  • the user interface provided in Step S112 can also be used to initiate the check-in request from the user device (e.g., by scanning a barcode through a camera of the user device according to permissions granted to the user interface, by positioning RFID elements/NFC elements of the user device in proximity to the EVSE unit, etc.)
  • Providing a user interface in step S112 can include providing a user interface via a mobile application for a user device, but one or more user devices can additionally or alternatively be provided through any suitable applications and/ or for any suitable devices.
  • Providing the user interface in Step S112 can include providing a means (e.g., graphical map, list, etc.) for viewing EVSEs and/or charging locations on a map (e.g., where reservation requests can be submitted for such EVSEs and/or charging locations; where information can be provided to the user regarding the EVSEs and/or charging locations; etc.).
  • a means e.g., graphical map, list, etc.
  • Step S112 can include providing a user interface at a mobile application for a user device, where the user interface includes a set of charging location indicators (e.g., graphical indicators on a graphical map; any suitable indicators; etc.) associated with a set of EVSEs including the EVSE, where the reservation request is associated with a charging location indicator of the set of charging location indicators, where the charging location indicator is associated with the EVSE.
  • User account aspects such as linked objects (e.g., RFID objects, NFC objects), payment methods, charging sessions (e.g., reserved charging sessions), demand response events, user groups (e.g., employee groups, fleet groups, etc.) and/or other aspects can also be accessed and/or modified through the user interface.
  • providing one or more user interfaces in Step S112 can be performed in another suitable manner, embodiments, variations, and examples of which are provided in Applications incorporated by reference above.
  • Step S120 recites: upon verification of the set of identifying parameters of the check-in request, initiating charging, through a cable coupled between the EVSE unit and the electric vehicle.
  • Step S120 functions to initiate a charging session in a user-focused manner (e.g., user-friendly manner), with functionality for enabling charging sessions even when the user attempts to check-in request during offline connectivity modes of either or both the EVSE unit and the user device of the user, where offline connectivity modes characterize operational states of user devices and/or EVSE units that have signal strength for connecting to a telecommunications network or other wireless/ wired network below a threshold level (e.g., modes where a level of wireless connectivity with a network is below a threshold).
  • verification of the set of identifying parameters in Step S120 can be executed with verification when the user device returns to a second location providing a second level of connectivity with the network above the threshold.
  • charging can initiate when the user/ user device is in proximity to the EVSE unit during the verification process, or when the user/user device is not in proximity to the EVSE unit during the verification process (e.g., when the user device returns to an environment/second locatoin or the user device is transitioned to a state where communication with the telecommunications network or other wireless/ wired network has an associated signal strength above a threshold level).
  • Exemplary offline or low connectivity modes can include modes in which wireless connectivity with a network is below “4 bars”, “3 bars”, “2 bars”, “1 bar”. Exemplary offline or low connectivity modes can include modes in which SOS is indicated for the network. Exemplary offline or low connectivity modes can include modes that are 2G, 3G, or 4G. Exemplary offline or low connectivity modes can include modes in which packet or other data transmission is less than 70%, less than 60%, less than 50%, less than 40%, less than 30%, less than 20%, less than 10%, less than 5%, less than 4%, less than 3%, less than 2%, less than 1% or less than a maximum specified data or packet transmission capacity of network systems involved.
  • the check-in request can be received at a first time point or within a first time window (e.g., when the user device is used to check-in with the EVSE), and initiating charging can be performed at a second time point or time window (e.g., later than the first time point or time window).
  • the attempt for initiating charging at the second time point or time window can be performed automatically (e.g., initiating charging is automatically attempted at a frequency or with a time lag).
  • the attempt for initiating charging can occur once the level of connectivity satisfies a threshold condition.
  • verification of the set of identifying parameters of the check-in request can be accomplished by the charging platform while the user/user device is at (e.g., in proximity to) the EVSE unit, given direct communication of parameters using the RFID elements, and for an EVSE unit that is in communication with the platform through a connection (e.g., Subscriber Identity Module (SIM) component with a wired connection to an area with suitable signal strength/ a level of connectivity above the threshold) through the network.
  • SIM Subscriber Identity Module
  • Verification of the set of identifying parameters of the check-in request can thus include communicating the set of identifying parameters through the network using a Subscriber Identity Module (SIM) component with a wired connection to a second location having a level of connectivity to the network above the threshold, or using another functionally identical or similar component.
  • SIM Subscriber Identity Module
  • initiation of charging can be executed proximal in time to when the user checks in at the EVSE unit for a charging session, even when the user device and the EVSE unit are both in locations providing a level of connectivity below a threshold.
  • verification of the set of identifying parameters of the check-in request can be accomplished by the charging platform while the user/user device is at (e.g., in proximity to) the EVSE unit, given direct communication of parameters using the NFC elements, and for an EVSE unit that is in communication with the platform through a connection (e.g., SIM component with a wired connection to an area with suitable signal strength).
  • initiation of charging can be executed proximal in time to when the user checks in at the EVSE unit for a charging sessions.
  • Verification of the set of identifying parameters of the check-in request can thus include communicating the set of identifying parameters through the network using a Subscriber Identity Module (SIM) component with a wired connection to a second location having a level of connectivity to the network above the threshold, or using another functionally identical or similar component.
  • SIM Subscriber Identity Module
  • initiation of charging can be executed proximal in time to when the user checks in at the EVSE unit for a charging session, even when the user device and the EVSE unit are both in locations providing a level of connectivity below a threshold.
  • the set of identifying parameters is communicated using manual code entry (e.g., manual entry of an authentication code) at a user interface of the user device and/ or the EVSE unit
  • verification of the set of identifying parameters of the check-in request can be accomplished by the charging platform while the user is at (e.g., in proximity) the EVSE unit, given direct communication of parameters by manual code entry, and for an EVSE unit that is in communication with the platform through a connection (e.g., SIM component with a wired connection to an area with suitable signal strength).
  • a connection e.g., SIM component with a wired connection to an area with suitable signal strength
  • Verification of the set of identifying parameters of the check-in request can thus include communicating the set of identifying parameters through the network using a Subscriber Identity Module (SIM) component with a wired connection to a second location having a level of connectivity to the network above the threshold, or using another functionally identical or similar component.
  • SIM Subscriber Identity Module
  • initiation of charging can be executed proximal in time to when the user checks in at the EVSE unit for a charging session, even when the user device and the EVSE unit are both in locations providing a level of connectivity below a threshold.
  • the set of identifying parameters is communicated through the network upon scanning a tag (e.g., QR code, other barcode) coupled to the EVSE unit
  • verification of the set of identifying parameters of the check-in request can be accomplished by the charging platform when the user/user device is away from (e.g., no longer in proximity to) the EVSE unit and the user device is again in communication with the telecommunications network or other wireless/ wired network.
  • the user device can be in an online mode and connected to the telecommunications network or other wireless/ wired network, with signal strength above a threshold level for communications.
  • the online mode can be associated with one or more of: a return to an above-ground area with adequate cellular signal strength, a transition of the user device out of an offline mode (e.g., Airplane mode, flight mode, sleep mode, on- mode, etc.), a transition of the user device out of a low-power mode having reduced functionality (e.g., upon charging, upon transitioning between power mode settings), a return of the telecommunications network to an operational state (e.g., after a disruption), a transition to a wireless network connection, or another scenario.
  • an offline mode e.g., Airplane mode, flight mode, sleep mode, on- mode, etc.
  • a transition of the user device out of a low-power mode having reduced functionality e.g., upon charging, upon transitioning between power mode settings
  • a return of the telecommunications network to an operational state e.g., after a disruption
  • a transition to a wireless network connection e.g., a wireless network connection, or another scenario
  • Step S120 can involve buffering of the scan of the barcode (e.g., QR code, other barcode), where the user device, by way of the user interface (e.g., charging mobile application) executing on the user device continues to buffer and reattempt verification of parameters for charging activation by the EVSE unit, with successful verification and initiation of charging once the user device is transitioned out of an offline mode to a connected mode (e.g., with signal strength above a threshold level, characterized by connection with the network) with respect to a cellular network, a WiFi network, or other network.
  • a connected mode e.g., with signal strength above a threshold level, characterized by connection with the network
  • FIGURE 3A through FIGURE 3D A specific example of the fourth variation is shown in FIGURE 3A through FIGURE 3D, where, upon scanning of a barcode (FIGURE 3A) using the user interface of the mobile application executing on the user device, upon detection that the user device is in an offline mode (and presentation of a notification to the user, through the user device, that the user device is in an offline mode), the mobile application comprises architecture for presenting the user with the option to initiate charging automatically once the user device is in an online mode again (FIGURE 3B).
  • the user device with mobile application for charging, then continues to buffer the scan of the barcode, and when the user device has returned to an online mode with signal strength above a threshold level, charging is initiated according to Step S120 through a cable connected between the EVSE unit and the electric vehicle associated with the user, and the user device presents a notification that charging has initiated (FIGURE 3C).
  • the mobile application in the example includes functionality for presenting parameters of the charging session (e.g., charging location, charger type, duration of charging, charging cost to current time point, projected charging cost, power flow characteristics, total power output, rate of charge, and estimations of range added), with notifications/reminders to retrieve the electric vehicle at the end of the charging session, and with the option to end the charging session, as shown in FIGURE 3D.
  • parameters of the charging session e.g., charging location, charger type, duration of charging, charging cost to current time point, projected charging cost, power flow characteristics, total power output, rate of charge, and estimations of range added
  • verification of the set of identifying parameters can thus occur when the user device is at a second location having suitable connectivity, and the EVSE unit is at a first location having unsuitable connectivity. In relation to the embodiments, variations, and examples described, verification of the set of identifying parameters can thus additionally or alternatively occur when the user device and the EVSE unit are at a first location having unsuitable connectivity. In relation to the embodiments, variations, and examples described, verification of the set of identifying parameters can thus additionally or alternatively occur when the user device and the EVSE unit are at a second location having suitable connectivity.
  • Initiating charging in Step S120 can involve charging with load distribution and management aspects (e.g., in relation to demand response events, in relation to fleet charging operations, in relation to group charging operations, in relation to pricing structures, etc.), charging session duration aspects, charging session price aspects, charging session power output (total output, rate, etc.) aspects, charging session range aspects (e.g., range for mission, range for route determined with vehicle telematics, etc.), and other aspects, embodiments, variations, and examples of which are described in Applications incorporated by reference.
  • Charging can be performed with devices described in PCT Application No. PCT/US22/32272 filed on June 3, 2022 and titled “Systems and Methods for Enabling Reliable and Secure Charging of Electric Vehicles", which is incorporated in its entirety herein by this reference.
  • Step S120 involving buffering of operations (e.g., buffering scanned barcodes and processing of scanned barcodes) for verification and initiation of charging, the method 100 can include steps that provide a positive user experience.
  • the method 100 can include buffering the processing operation at the user device at a first frequency S124, in order to prevent excessive drain of battery charge state of the user device.
  • the first frequency can be a frequency of: once every second, once every 30 seconds, once every minute, once every 5 minutes, once every 10 minutes, etc.).
  • the first frequency can alternatively be a non-constant frequency.
  • the method can include: increasing the frequency of buffering in response to detection of movement of the user device (e.g., through motion sensors, such as accelerometer components of the user device); and upon verification according to Step S120, initiating charging.
  • sensors e.g., motion sensors, GPS systems, RFID transmissions/data receipts with other RFID objects, etc.
  • the method can include: increasing the frequency of buffering in response to detection of movement of the user device (e.g., through motion sensors, such as accelerometer components of the user device); and upon verification according to Step S120, initiating charging.
  • the method 100 can include performing a check of signal strength between the user device and the telecommunications network (or other wireless/ wired network) at a second frequency prior to buffering the processing operation S126, in order to prevent excessive drain of battery charge state of the user device (by checking signal strength before buffering).
  • the second frequency can be a frequency of: once every second, once every 30 seconds, once every minute, once every 5 minutes, once every 10 minutes, etc.).
  • the first frequency can alternatively be a non-constant frequency.
  • the method can include: increasing the frequency of checks of signal strength in response to detection of movement of the user device; and upon verification according to Step S120, initiating charging.
  • sensors e.g., motion sensors, GPS systems, RFID transmissions/data receipts with other RFID objects, etc.
  • the method can include: increasing the frequency of checks of signal strength in response to detection of movement of the user device; and upon verification according to Step S120, initiating charging.
  • the method 100 can include buffering the processing operation in response to a transition between operational modes of the user device S128, where the operational modes can include one or more of: an Airplane mode/flight mode/offline mode; a low-power mode; a non-low-power mode; a WiFi on/connected mode; a WiFi off mode; a BluetoothTM on mode; a BluetoothTM off mode; a charging mode; or another suitable mode.
  • the operational modes can include one or more of: an Airplane mode/flight mode/offline mode; a low-power mode; a non-low-power mode; a WiFi on/connected mode; a WiFi off mode; a BluetoothTM on mode; a BluetoothTM off mode; a charging mode; or another suitable mode.
  • Steps S124, S126, S128 can be combined with each other and/or with other suitable steps.
  • an exemplary method can include: at the user device, performing a check for signal strength; buffering the processing operation upon detection of at least one of signal strength above a threshold level and movement of the user device; and initiating charging of the electric vehicle in response to verification of parameters according to Step S120.
  • Variations of the method can further include controlling operational states of the user device (e.g., transitioning the user device from a first mode with a lower degree of connectivity to a second mode with a higher degree of connectivity to initiate charging, and then back to the lower degree of connectivity to conserve battery use).
  • Additional method steps can include one or more of:
  • the tool can include a button or other input region at a detail page (e.g., station detail page) of the user interface, which allows users to select a reason for the issue and to report it to the platform.
  • a detail page e.g., station detail page
  • the software network provider can take remote action to troubleshoot the unit, in order to restore it to working operational mode.
  • Variations of the method 100 can include other suitable steps.
  • Embodiments, variations, and examples of the methods 100 described can provide solutions to low connectivity or offline modes of EVSE units and/ or user devices, in a manner that still allows for energy optimization and load management of charging associated with a set of EVSE units at a site, any EVSE unit, or any group of EVSE units. As such, the methods described can continue to provide solutions for energy optimization in response to demand response events and/or other situations, described in Applications incorporated by reference.
  • One embodiment of load management an energy optimization can include: establishing an interface with a management entity (e.g., site host of a set of chargers) of an electric power distribution system, the electric power distribution system in communication with a set of outlets of utility-facing devices providing access to the electric power distribution system Sno; returning a demand assessment from a demand model characterizing anticipated demand upon the one or more portions of the electric power distribution associated with the set of outlets S120; and executing an action for adjustment of load distribution through the management entity, based upon the demand assessment S130.
  • a management entity e.g., site host of a set of chargers
  • the method 100 can, however, include other suitable steps to promote proper load distribution in response to various events.
  • an embodiment of a system 200 for charging includes: a platform 210 for charging, comprising a charging session processing subsystem 212 and a load distribution subsystem 214; a user device 220; an EVSE unit 230; and a telecommunications network 240 connecting the user device 220 to the platform 210.
  • the telecommunications network 240 can also connect the EVSE unit 230 to the platform.
  • the system 200 is configured to execute one or more portions of the methods 100 described in Sections 2.1-2.4 above, and/or other suitable methods. Aspects of the system 200 are described in Applications incorporated by reference. [0073] The system 200 can, however, include other suitable elements configured to enable charging sessions in offline modes of the user device and/ or EVSE unit.
  • FIGURE 6 shows a computing and control subsystem 301 that is programmed or otherwise configured to, for example, facilitate charging of an electric vehicle, according to methods described.
  • the computing and control subsystem 301 includes architecture for regulating various aspects of detecting a check-in request and verification of parameters of the check-in request, in order to enabling charging of an electric vehicle, according to functionalities of the present disclosure described.
  • the computing and control subsystem 301 can be an electronic device of a user or a computer system that is remotely located with respect to the electronic device.
  • the electronic device can be a mobile electronic device.
  • the computing and control subsystem 301 includes a central processing unit (CPU, also “processor” and “computer processor” herein) 305, which can be a single core or multi core processor, or a plurality of processors for parallel processing.
  • the computing and control subsystem 301 also includes memory or memory location 310 (e.g., randomaccess memory, read-only memory, flash memory), electronic storage unit 315 (e.g., hard disk), communication interface 320 (e.g., network adapter) for communicating with one or more other systems, and peripheral devices 325, such as cache, other memory, data storage and/or electronic display adapters.
  • the memory 310, storage unit 315, interface 320 and peripheral devices 325 are in communication with the CPU 305 through a communication bus (solid lines), such as a motherboard.
  • the storage unit 315 can be a data storage emit (or data repository) for storing data.
  • the computer system 301 can be operatively coupled to a computer network (“network”) 330 with the aid of the communication interface 320.
  • the network 330 can be the Internet, an internet and/or extranet, or an intranet and/or extranet that is in communication with the Internet.
  • the network 330 is a telecommunication and/or data network.
  • the network 330 can include one or more computer servers, which can enable distributed computing, such as cloud computing.
  • one or more computer servers may enable cloud computing over the network 330 (“the cloud”) to perform various aspects of facilitating charging of an electric vehicle, with desired security, authentication, and locking functionalities associated with various types of charging sessions and/or different users.
  • cloud computing may be provided by cloud computing platforms such as, for example, Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform, and IBM cloud.
  • the network 830 with the aid of the computer system 601, can implement a peer-to-peer network, which may enable devices coupled to the computer system 101 to behave as a client or a server.
  • the CPU 305 can include one or more computer processors and/or one or more graphics processing units (GPUs).
  • the CPU 305 can execute a sequence of machine- readable instructions, which can be embodied in a program or software.
  • the instructions may be stored in a memory location, such as the memory 310.
  • the instructions can be directed to the CPU 305, which can subsequently program or otherwise configure the CPU 305 to implement methods of the present disclosure. Examples of operations performed by the CPU 305 can include fetch, decode, execute, and writeback.
  • the CPU 305 can be part of a circuit, such as an integrated circuit.
  • One or more other components of the computing and control subsystem 301 can be included in the circuit.
  • the circuit is an application specific integrated circuit (ASIC).
  • ASIC application specific integrated circuit
  • the storage unit 315 can store files, such as drivers, libraries and saved programs.
  • the storage unit 315 can store user data, e.g., user preferences and user programs.
  • the computer system 301 can include one or more additional data storage units that are external to the computer system 301, such as located on a remote server that is in communication with the computer system 301 through an intranet or the Internet.
  • the computing and control subsystem 301 can communicate with one or more remote computer systems through the network 330.
  • the computer system 601 can communicate with a remote computer system of a user.
  • remote computer systems include personal computers (e.g., portable PC), slate or tablet PC’s (e.g., Apple® iPad, Samsung® Galaxy Tab), telephones, Smart phones (e.g., Apple® iPhone, Android-enabled device, Blackberry®), smart watches, or personal digital assistants.
  • the user can access the computer system 601 via the network 330.
  • Methods as described herein can be implemented by way of machine (e.g., computer processor) executable code stored on an electronic storage location of the computing and control subsystem 301, such as, for example, on the memory 310 or electronic storage unit 315.
  • the machine executable or machine-readable code can be provided in the form of software.
  • the code can be executed by the processor 305.
  • the code can be retrieved from the storage unit 315 and stored on the memory 310 for ready access by the processor 305.
  • the electronic storage unit 315 can be precluded, and machine-executable instructions are stored on memory 310.
  • the code can be pre-compiled and configured for use with a machine having a processer adapted to execute the code, or can be compiled during runtime.
  • the code can be supplied in a programming language that can be selected to enable the code to execute in a pre-compiled or as-compiled fashion.
  • Embodiments of the systems and methods provided herein can be embodied in programming.
  • Various aspects of the technology may be thought of as “products” or “articles of manufacture” typically in the form of machine (or processor) executable code and/ or associated data that is carried on or embodied in a type of machine readable medium.
  • Machine-executable code can be stored on an electronic storage unit, such as memory (e.g., read-only memory, randomaccess memory, flash memory) or a hard disk.
  • “Storage” type media can include any or all of the tangible memory of the computers, processors or the like, or associated modules thereof, such as various semiconductor memories, tape drives, or disk drives, which may provide non-transitory storage at any time for the software programming. All or portions of the software may at times be communicated through the Internet or various other telecommunication networks. Such communications, for example, may enable loading of the software from one computer or processor into another, for example, from a management server or host computer into the computer platform of an application server.
  • another type of media that may bear the software elements includes optical, electrical and electromagnetic waves, such as used across physical interfaces between local devices, through wired and optical landline networks and over various air-links.
  • a machine readable medium such as computer-executable code
  • a tangible storage medium such as computer-executable code
  • Non-volatile storage media include, for example, optical or magnetic disks, such as any of the storage devices in any computer(s) or the like, such as may be used to implement the databases, etc. shown in the drawings.
  • Volatile storage media include dynamic memory, such as main memory of such a computer platform.
  • Tangible transmission media include coaxial cables; copper wire and fiber optics, including the wires that comprise a bus within a computer system.
  • Carrier-wave transmission media may take the form of electric or electromagnetic signals, or acoustic or light waves such as those generated during radio frequency (RF) and infrared (IR) data communications.
  • RF radio frequency
  • IR infrared
  • Common forms of computer-readable media therefore include for example: a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD or DVD-ROM, any other optical medium, punch cards paper tape, any other physical storage medium with patterns of holes, a RAM, a ROM, a PROM and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave transporting data or instructions, cables or links transporting such a carrier wave, or any other medium from which a computer may read programming code and/ or data.
  • Many of these forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to a processor for execution.
  • the computing and control subsystem 301 can include or be in communication with an electronic display 335 that comprises a user interface (UI) 340 for providing, for example, a visual display indicative of statuses associated with charging of an electric vehicle, security information, verification information, and other information.
  • UIs include, without limitation, a graphical user interface (GUI) and webbased user interface.
  • Methods and systems of the present disclosure can be implemented by way of one or more algorithms.
  • An algorithm can be implemented by way of software upon execution by the central processing unit 305.
  • the algorithm can, for example, facilitate charging of an electric vehicle, with desired security, verification, and other functionalities associated with various types of charging sessions and/or different users.
  • the computing and control subsystem 801 can include architecture with programming to execute other suitable methods.
  • Embodiments of the invention(s) described can include every combination and permutation of the various system components and the various method processes, including any variants (e.g., embodiments, variations, examples, specific examples, figures, etc.), where portions of embodiments of the method 100 and/ or processes described herein can be performed asynchronously (e.g., sequentially), concurrently (e.g., in parallel), or in any other suitable order by and/ or using one or more instances, elements, components of, and/or other aspects of the system 200 and/or other entities described herein.
  • any of the variants described herein e.g., embodiments, variations, examples, specific examples, figures, etc.
  • any portion of the variants described herein can be additionally or alternatively combined, aggregated, excluded, used, performed serially, performed in parallel, and/or otherwise applied.
  • Portions of embodiments of the invention(s) can be embodied and/or implemented at least in part as a machine configured to receive a computer-readable medium storing computer-readable instructions.
  • the instructions can be executed by computer-executable components that can be integrated with embodiments of the system(s).
  • the computer-readable medium can be stored on any suitable computer- readable media such as RAMs, ROMs, flash memory, EEPROMs, optical devices (CD or DVD), hard drives, floppy drives, or any suitable device.
  • the computer-executable component can be a general or application specific processor, but any suitable dedicated hardware or hardware/firmware combination device can alternatively or additionally execute the instructions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Mechanical Engineering (AREA)
  • Transportation (AREA)
  • Power Engineering (AREA)
  • Theoretical Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Accounting & Taxation (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Tourism & Hospitality (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Human Resources & Organizations (AREA)
  • Primary Health Care (AREA)
  • Development Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Charge And Discharge Circuits For Batteries Or The Like (AREA)

Abstract

L'invention concerne un système et un procédé de charge d'un véhicule électrique dans des emplacements à faible connectivité, le procédé comprenant : lorsqu'au moins l'une d'une unité EVSE et d'un dispositif utilisateur d'un utilisateur se trouve dans un premier emplacement fournissant un premier niveau de connectivité avec un réseau au-dessous d'un seuil : à un premier instant, la réception d'une demande d'enregistrement au niveau de l'unité EVSE par l'utilisateur associé au véhicule électrique, la demande d'enregistrement comprenant une communication entre l'unité EVSE et un dispositif utilisateur de l'utilisateur, la communication comprenant un ensemble de paramètres d'identification ; lors de la vérification de l'ensemble de paramètres d'identification de la demande d'enregistrement, initier la charge du véhicule électrique, par l'intermédiaire d'un câble couplé entre l'unité EVSE et le véhicule électrique, à un second instant ultérieur au premier instant.
PCT/US2024/032145 2023-06-04 2024-05-31 Systèmes et procédés de charge de véhicules électriques avec des stations de charge dans divers modes de connectivité Ceased WO2024253978A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363506135P 2023-06-04 2023-06-04
US63/506,135 2023-06-04

Publications (1)

Publication Number Publication Date
WO2024253978A1 true WO2024253978A1 (fr) 2024-12-12

Family

ID=93796121

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/032145 Ceased WO2024253978A1 (fr) 2023-06-04 2024-05-31 Systèmes et procédés de charge de véhicules électriques avec des stations de charge dans divers modes de connectivité

Country Status (1)

Country Link
WO (1) WO2024253978A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140289082A1 (en) * 2013-03-19 2014-09-25 Kt Corporation Electric charging management of electric vehicle
US20160137087A1 (en) * 2014-11-17 2016-05-19 Siemens Industry, Inc. Evse-based energy automation, management, and protection systems and methods
KR101738447B1 (ko) * 2012-03-13 2017-06-09 주식회사 케이티 간소화된 벤딩 머신형 충전 설비를 통한 전기 자동차 충전용 휴대형 연결 장치
US20210213846A1 (en) * 2020-01-13 2021-07-15 NAD Grid Corp Methods and systems for facilitating charging sessions for electric vehicles, with improved user interface operation modes
KR20220020485A (ko) * 2020-08-11 2022-02-21 한국전력공사 차량의 충전 방법 및 인증서 제공 시스템

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101738447B1 (ko) * 2012-03-13 2017-06-09 주식회사 케이티 간소화된 벤딩 머신형 충전 설비를 통한 전기 자동차 충전용 휴대형 연결 장치
US20140289082A1 (en) * 2013-03-19 2014-09-25 Kt Corporation Electric charging management of electric vehicle
US20160137087A1 (en) * 2014-11-17 2016-05-19 Siemens Industry, Inc. Evse-based energy automation, management, and protection systems and methods
US20210213846A1 (en) * 2020-01-13 2021-07-15 NAD Grid Corp Methods and systems for facilitating charging sessions for electric vehicles, with improved user interface operation modes
US20230331110A1 (en) * 2020-01-13 2023-10-19 NAD Grid Corp Methods and systems for facilitating charging sessions for electric vehicles, with improved user interface operation modes
KR20220020485A (ko) * 2020-08-11 2022-02-21 한국전력공사 차량의 충전 방법 및 인증서 제공 시스템

Similar Documents

Publication Publication Date Title
US10380849B2 (en) Payment processing with automatic no-touch mode selection
KR101375820B1 (ko) 배터리 온 및 배터리 오프 모드들에서 ｎｆｃ 보안 애플리케이션 지원을 제공하기 위한 시스템들 및 방법들
US20140148095A1 (en) Multiple antenna arrangement for near field communications
CN113497641B (zh) 通信装置和操作方法
US9888442B2 (en) Electronic device for wirelessly receiving power from power supply apparatus
US20150029532A1 (en) Image forming apparatus and near field communication (nfc) device supporting nfc function and method of performing authentication thereof cross-reference to related applications
US20120149357A1 (en) Remote control method and system for smart card
US10482458B2 (en) User equipment, service providing device, payment system comprising the same, control method thereof and non-transitory computer-readable storage medium storing computer program recorded thereon
EP2779021A2 (fr) Procédé de syntonisation autonome pour améliorer la performance de fréquence radio
CN113170376B (zh) 用于装置集群管理的系统和方法
US11423387B2 (en) Processing payments
CN105099514B (zh) 由nfc‑b读取器发现多个nfc‑b设备的方法以及对应的nfc‑b读取器
WO2024253978A1 (fr) Systèmes et procédés de charge de véhicules électriques avec des stations de charge dans divers modes de connectivité
WO2019009803A1 (fr) Traitement de paiements
CN102160062A (zh) 针对通信系统的安全初始化过程
CN204808375U (zh) 具有端口依赖功能的rfid标签
CN117835200A (zh) 近场通信装置的控制方法、电子设备、车辆及存储介质
KR101773913B1 (ko) 듀얼 모드를 구비한 ｎｆｃ 태그
KR20160007926A (ko) 모바일 디바이스의 보안 어플리케이션 실행 방법
KR101453450B1 (ko) 카드 발급 시스템 및 방법, 그 장치 및 이를 위한 기록 매체
KR20140030619A (ko) 금융 거래 서비스 제공 시스템 및 방법, 그 장치, 이를 위한 기록 매체
JP6399681B2 (ja) 通信装置、処理方法及びプログラム
CN102027729A (zh) 一种在系统中用户身份标示的管理方法
CN104202715A (zh) 满足国军标协议的rfid无线绑定式通信方法
KR20070003950A (ko) 단말기 동작 강화를 위한 검출기 로직 및 무선 인식 장치및 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24819822

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE