Charging Management System and Method

Abstract

This invention relates to a charging management system and method. The system may include at least one first electric vehicle and a charging management server. The at least one first electric vehicle is configured to supply power to at least one second electric vehicle requesting charging services. The charging management server is configured to manage the charging services based on a communication protocol between the first and second electric vehicles. The charging management server may be configured to support payment for the charging services by verifying certificates of the communication protocol used for the charging services.

Description

[0001] Cross-references to related applications

[0002] This application claims priority and benefit to Korean Patent Application No. 10-2024-0199193, filed with the Korean Intellectual Property Office on December 27, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This invention relates to a charging management system and method thereof, and more specifically, to a technology that supports intelligent charging services during vehicle-to-vehicle (V2V) charging. Background Technology

[0004] Electric vehicles (EVs) currently under development utilize batteries to power their electric motors. Consequently, compared to conventional gasoline-powered vehicles, these EVs produce less air pollution (such as exhaust fumes) and noise, have fewer malfunctions, longer lifespans, and are easier to drive. An EV charging system can be broadly defined as a system that uses electricity from a commercial power grid or energy storage device to charge the batteries installed in the EV. Such EV charging systems can take many different forms depending on the type of EV. For example, EV charging systems can include conductive charging systems using cables or contactless wireless power transmission systems.

[0005] Recently, with the increase in the use of electric vehicles, the infrastructure of charging systems has become increasingly useful. Electric vehicles typically use fixed charging stations. For example, electric vehicles wishing to charge can go to an electric vehicle charging station. However, due to the scarcity of electric vehicle charging stations compared to other types of charging stations, there may be location limitations. In particular, there are fewer electric vehicle charging stations in suburban areas, which may cause problems for electric vehicle drivers. This issue may cause anxiety among electric vehicle owners regarding charging.

[0006] To address this issue, vehicle-to-vehicle (V2V) charging service technology is being developed and has been offered in select areas since 2021. This V2V charging service is provided free of charge, thus demonstrating improved user convenience. However, traditional V2V charging services suffer from the problem of not supporting payment services or providing services such as dispatching and management of charging vehicles.

[0007] As mentioned above, in order to meet the rapidly growing demand for electric vehicles and the diverse charging requirements, V2V-based charging technology that provides smart charging services would be useful. Summary of the Invention

[0008] The embodiments of the present invention provide a charging management system and method that can support smart charging services by monitoring customer vehicles and power supply vehicles.

[0009] The embodiments of the present invention provide a charging management system and method that can support charging payment services for customer vehicles.

[0010] The technical objectives of this invention are not limited to those mentioned above, and those skilled in the art can understand other technical objectives not mentioned from the description of the embodiments.

[0011] An embodiment of the present invention provides a charging management system, comprising at least one first electric vehicle and a charging management server. The at least one first electric vehicle is configured to supply power to at least one second electric vehicle requesting charging services. The charging management server is configured to manage the charging services based on the communication protocol of the first and second electric vehicles. The charging management server may be configured to support payment for the charging services by verifying a certificate chain of the communication protocol of the charging services.

[0012] In an exemplary embodiment of the present invention, the communication protocol may support at least one of the Open ChargePoint Protocol (OCPP), ISO 15118, or IEC 61850.

[0013] In an exemplary embodiment of the present invention, the first electric vehicle is configured to include a communication module, a control module, and a charging module. The communication module is configured to support a communication protocol for sending and receiving information with the second electric vehicle and a charging management server. The control module is configured to verify the validity of a certificate chain received from the second electric vehicle. The charging module is configured to perform payment processing when power is supplied to the second electric vehicle in response to the validity of the certificate chain.

[0014] In an exemplary embodiment of the present invention, the communication module may be configured to receive a charging service request message from the charging management server.

[0015] In an exemplary embodiment of the present invention, in response to the charging module being connected to a second electric vehicle, the control module may be configured to determine whether the identifier of the received request message matches the identifier of the certificate chain.

[0016] In an exemplary embodiment of the present invention, in response to the control module determining that the identifier of the received request message matches the identifier of the certificate chain, the communication module may be configured to send the certificate chain to the charging management server, and the charging module may be configured to supply power to the second electric vehicle.

[0017] In an exemplary embodiment of the present invention, in response to the charging module completing power supply, the control module may be configured to generate charging service information, the communication module may be configured to send the charging service information to the charging management server, and receive a payment request message from the second electric vehicle.

[0018] In an exemplary embodiment of the present invention, the charging management server may be configured to include a server communication module, a memory, and a processor. The server communication module is configured to support a communication protocol for sending and receiving information with a first electric vehicle. The memory is configured to store at least one instruction, and the processor is configured to execute at least one instruction. The processor may be configured to verify the validity of a received certificate chain, control the first electric vehicle to supply power based on the verification result, and perform payment processing in response to the completion of power supply.

[0019] In an exemplary embodiment of the present invention, the processor may be configured to generate payment information based on a payment request message received from a first electric vehicle.

[0020] In an exemplary embodiment of the present invention, the server communication module is configured to send charging service information and payment information to an external server in response to receiving a payment request message.

[0021] Another embodiment of the present invention provides a charging management method for a charging management system. The method includes: a first electric vehicle supplying power; a second electric vehicle requesting a charging service and receiving power from the first electric vehicle; a charging management server managing the charging service based on the communication protocol between the first and second electric vehicles; and the charging management server supporting payment for the charging service by verifying the certificate chain of the communication protocol of the charging service.

[0022] In another exemplary embodiment of the invention, the communication protocol may support at least one of the Open Charging Point Protocol (OCPP), ISO 15118, or IEC 61850.

[0023] In another exemplary embodiment of the present invention, power supply may include: a first electric vehicle supporting a communication protocol for sending and receiving information with a second electric vehicle and a charging management server; the first electric vehicle verifying the validity of a certificate chain received from the second electric vehicle; in response to the validity of the certificate chain, the first electric vehicle supplying power to the second electric vehicle; and when power supply is complete, the first electric vehicle receiving a payment request message from the second electric vehicle and performing payment processing.

[0024] In another exemplary embodiment of the present invention, supporting the communication protocol may include: the first electric vehicle receiving a charging service request message from the charging management server.

[0025] In another exemplary embodiment of the present invention, verifying the validity of the certificate chain may include: the first electric vehicle determining whether the identifier of the received request message matches the identifier of the certificate chain.

[0026] In another exemplary embodiment of the present invention, supplying power to the second electric vehicle includes: the first electric vehicle sending a certificate chain to the charging management server, and the first electric vehicle supplying power to the second electric vehicle.

[0027] In another exemplary embodiment of the present invention, power supply may include: generating charging service information by a first electric vehicle, determining whether the identifier of the received request message matches the identifier of the certificate chain by the first electric vehicle, sending the certificate chain to the charging management server by the first electric vehicle, and supplying power to the second electric vehicle by the first electric vehicle.

[0028] In another exemplary embodiment of the present invention, power supply may further include: the first electric vehicle sending its changed status information to the charging management server.

[0029] In another exemplary embodiment of the present invention, managing the charging service may include: a communication protocol supported by a charging management server for sending and receiving information with a first electric vehicle; the validity of a received certificate chain verified by the charging management server; the first electric vehicle being controlled to supply power based on the verification result by the charging management server; and payment processing being performed by the charging management server in response to the completion of power supply.

[0030] In another exemplary embodiment of the present invention, performing payment processing includes: generating payment information by a charging management server based on a payment request message received from a first electric vehicle, and sending the charging service information and payment information to an external server by the charging management server.

[0031] According to the present invention (e.g., the technology), the convenience of electric vehicle users can be improved by providing smart charging services.

[0032] Furthermore, according to the present invention (e.g., the technology), the problem of location limitations for charging electric vehicles can be solved.

[0033] Furthermore, according to the present invention (e.g., the technology), the reliability of electric vehicle charging payment can be improved.

[0034] In addition, various effects that can be directly or indirectly identified through this specification may be provided. Attached Figure Description

[0035] Figure 1 An exemplary charging management system is shown.

[0036] Figure 2 A block diagram of an exemplary charging management server is shown.

[0037] Figure 3 An exemplary first electric vehicle is shown.

[0038] Figure 4 , Figure 5 , Figure 6 and Figure 7 A flowchart of an exemplary charging management method is shown.

[0039] Figure 8 An example of status information is shown.

[0040] Figure 9 An example of a request for information is shown.

[0041] Figure 10 An example of the response information is shown.

[0042] Figure 11 An example of charging service information is shown.

[0043] Figure 12 A block diagram is shown to illustrate an exemplary computing system. Detailed Implementation

[0044] In the following description, some exemplary embodiments of the invention will be described in detail with reference to the exemplary accompanying drawings. It should be noted that when adding reference numerals to the constituent elements of each drawing, the same constituent elements will include as many identical reference numerals as possible, even if indicated in different drawings. In describing exemplary embodiments of the invention, detailed descriptions of known configurations or functions associated with exemplary embodiments of the invention may be omitted if it is determined that such detailed descriptions would obscure the gist of the invention.

[0045] In describing the constituent elements of exemplary embodiments of the present invention, terms such as first, second, A, B, (a), and (b) may be used. These terms are used to distinguish constituent elements from other constituent elements, and the nature, order, or sequence of constituent elements is not limited by the terms. Furthermore, the terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which the exemplary embodiments of the present invention pertain, unless these terms are defined differently. Terms defined in general dictionaries should be interpreted as having a meaning matching the contextual meaning in the relevant field, and should not be interpreted as having an idealized or overly formal meaning, unless these terms are defined in this specification.

[0046] The term "electric vehicle" as used in this invention can refer to a motor vehicle as defined in Federal Regulations 49 523.3, etc. Electric vehicles are designed for use on highways and are powered by electricity supplied by onboard energy storage devices, such as batteries capable of being recharged from an external power source. The power source may include residential or public power services or an onboard fuel-powered generator.

[0047] Furthermore, such electric vehicles can include hybrid electric vehicles (HEVs) and plug-in hybrid electric vehicles (PHEVs). In this context, an HEV can have an engine as the primary power source and an electric motor as an auxiliary power source. A PHEV can have an electric motor as the primary power source and an engine utilized in response to battery discharge.

[0048] The intelligent charging service of this invention can instruct electric vehicle users to be assigned IDs and provided with services such as charging history, location information of charging devices (e.g., power supply vehicles), information on charging devices (e.g., power supply vehicles), and payment. Hereinafter, the intelligent charging service will be referred to as the charging service.

[0049] In the following text, reference will be made to Figures 1 to 12 Various exemplary embodiments of the present invention are described in detail.

[0050] Figure 1 An exemplary vehicle-to-vehicle (V2V) based charging management system 1 (hereinafter referred to as the charging management system) is shown.

[0051] Reference Figure 1 The charging management system 1 may include: a charging management server 10, a first electric vehicle 20, and a second electric vehicle 30.

[0052] The first electric vehicle 20 (VCS) can be at least one electric vehicle configured to provide electricity. That is, the first electric vehicle 20 (VCS) can be a mobile charging device capable of performing (e.g., all) the functions of a conventional charging device.

[0053] The second electric vehicle 30 (EVC) may be at least one electric vehicle configured to request charging services and receive power from the first electric vehicle 20. The second electric vehicle 30 (EVC) may be configured to recognize the first electric vehicle 20 as a mobile charging device and perform a charging process.

[0054] The charging management server 10 can be configured to manage the charging service by monitoring the first electric vehicle 20 and the second electric vehicle 30.

[0055] For example, the charging management server 10 can be a server for a charging station management system (CSMS) that includes the Open Charge Point Protocol (OCPP) and the Charging Point Operator (CPO).

[0056] CPO can refer to a company or organization authorized to install charging stations and allow physical access to them. Accordingly, the charging management server 10 can be configured to manage the first electric vehicle 20 and to grant permissions for the charging process performed in each electric vehicle using information and communication technologies.

[0057] The charging management server 10 can be configured to schedule the first electric vehicle 20 corresponding to a request from the second electric vehicle 30 based on the status information of the first electric vehicle 20.

[0058] The charging management server 10 can be configured to manage the charging service based on the communication protocol of the first electric vehicle 20 and the second electric vehicle 30. Then, the charging management server 10 can be configured to support payment for the charging service by verifying the certificate of the communication protocol of the charging service.

[0059] In this article, a certificate can refer to an electronic document that binds a public key (PK) to an ID through a digital signature. Public Key Infrastructure (PKI) can refer to a system used to generate, store, redistribute, and revoke digital signatures that are used to verify whether a specific public key belongs to a particular individual or entity.

[0060] A certificate chain can be set up (e.g., injected) into a first electric vehicle 20 and a second electric vehicle 30 by an Original Equipment Manufacturer (OEM). An OEM can refer to a server operated by the electric vehicle manufacturer, or it can refer to the top-level Certificate Authority (CA) that issues the OEM root certificate. For better understanding and ease of description, an OEM-injected certificate chain is described, but the invention is not limited thereto. In this case, the certificate chain can be referred to as a contract certificate chain and can be formed based on signatures. For example, a certificate for an OEM subsidiary can be generated by signing the public key of the OEM subsidiary using the private key of the OEM root certificate. A certificate chain can be created by bundling the OEM root certificate with the certificates of the OEM subsidiary.

[0061] A Mobility Operator (MO) can refer to a server operated by a Charging Business Operator (CBO), and may include a Certificate Provisioning Service (CPS). The CBO can be a business operator that provides charging services through B2C contracts with electric vehicle users. Furthermore, the CBO's server (i.e., the MO) can share information related to the certificate chain with the OEM. Accordingly, the CBO's server (i.e., the MO) can verify the validity of the certificates for the first electric vehicle 20 and the second electric vehicle 30.

[0062] CPS can refer to an entity that provides electric vehicle certificate installation services and plays a role in providing billing and other value-added services to customers. CPS can be a special type of charging service operator's server (i.e., MO), or it can be implemented in combination with a charging service operator's server (i.e., MO).

[0063] In this document, the communication protocol may support at least one of the Open Charging Point Protocol (OCPP), ISO 15118, or IEC 61850. For example, the charging management server 10 and the first electric vehicle 20 may support OCPP (P2). Furthermore, the first electric vehicle 20 and the second electric vehicle 30 may support at least one of ISO 15118 or IEC 61850 (P1).

[0064] ISO 15118 can be a communication protocol between an electric vehicle and a charging device, and can support plug-and-charge (PnC) functionality that requires automatic identification and verification. In this invention, ISO 15118 can be a communication protocol between a first electric vehicle 20 and a second electric vehicle 30.

[0065] PnC can refer to a process in which authentication, authorization, load control, and payment are automatically performed in response to an electric vehicle user simply plugging their electric vehicle into a charging device, without requiring any additional user interaction. Alternatively, PnC can refer to the identification and authorization mode used for such an automated process. PnC enables electric vehicle users to charge their vehicles without the hassle of approval.

[0066] ISO 15118 can utilize Public Key Infrastructure (PKI) on the Internet to achieve standardized verification between electric vehicles and charging devices. Furthermore, in addition to basic authentication, ISO 15118 can also achieve secure transmission of communication data between electric vehicles and charging devices through message encryption.

[0067] The Open Charging Point Protocol (OCPP) is an international open charging communication protocol adopted as a standard by more than 50 countries. OCPP is an open charging communication protocol created by the Open Charge Alliance (OCA), and the current version is 2.0.1. It is an internationally recognized representative protocol for electric vehicle charging infrastructure. In this invention, OCPP can be the communication protocol between the first electric vehicle 20 and the charging management server 10.

[0068] In South Korea, the Ministry of Environment mandated OCPP 1.6 certification for charging device power distribution projects in 2022, making OCPP 1.6 more widely adopted. Compared to previous versions, OCPP 2.0.1 supports enhanced security communication environments. For example, OCPP 2.0.1 can have features more suitable for smart charging technologies such as PnC and wireless charging.

[0069] Recently, there has been a demand for standardization of a "charging communication protocol," which specifies the format and methods for sending / receiving information between charging devices and electric vehicles. A standard protocol is useful for the widespread adoption of electric vehicles, facilitating, for example, the efficient construction of charging infrastructure networks and their integration with the power grid.

[0070] To address these issues, this invention proposes a charging management system 1 that simultaneously supports ISO 15118 and OCPP. Accordingly, the charging management system 1 can provide optimized intelligent charging services.

[0071] Reference Figures 2 to 11 A detailed description of the charging management system 1.

[0072] Figure 2 A block diagram of an exemplary charging management server 10 is shown. Figure 3 An exemplary first electric vehicle 20 is shown.

[0073] Reference Figure 2 The charging management server 10 may include a server communication module 110, a memory 120, and a processor 130.

[0074] Server communication module 110 can be configured to support communication protocols for sending and receiving information with the first electric vehicle 20. For example, server communication module 110 can be configured to support OCPP.

[0075] The memory 120 can be configured to store at least one instruction. Furthermore, the memory 120 can be configured to store data sent and received via the server communication module 110.

[0076] Processor 130 may be configured to (e.g., access memory and) execute at least one instruction. For example, processor 130 may be configured to generate request information based on information related to the second electric vehicle (EVC). In this document, request information may include at least one of the following: a user identifier of the second electric vehicle (EVC), user information, battery information, location information, or a request message. For example, processor 130 may be configured to generate request information in response to server communication module 110 receiving a request message from the second electric vehicle (EVC).

[0077] Processor 130 may be configured to verify the validity of a communication protocol certificate received from the first electric vehicle 20. For example, server communication module 110 may be configured to receive a certificate chain injected into the first electric vehicle 20 according to ISO 15118. Subsequently, processor 130 may be configured to verify the validity of the certificate chain according to ISO 15118. For example, in response to processor 130 determining that the certificate is valid, server communication module 110 may be configured to receive status information from the first electric vehicle 20. Herein, status information may include at least one of the following: an identifier of the first electric vehicle 20, charging device information, location information, price information, communication protocol information, or customer usage information.

[0078] Furthermore, processor 130 can be configured to verify the validity of a certificate chain received from the second electric vehicle (EVC). For example, server communication module 110 can receive a certificate chain injected into the second electric vehicle (EVC) according to ISO 15118. Subsequently, processor 130 can be configured to verify the validity of the certificate chain according to ISO 15118. Processor 130 can be configured to control the first electric vehicle 20 to supply power to the second electric vehicle (EVC) based on the verification result. For example, in response to determining that the certificate is valid, processor 130 can be configured to control the first electric vehicle 20 to supply power to the second electric vehicle (EVC).

[0079] The validity of the certificate chain of the second electric vehicle (EVC) can be determined based on the verification result received from the charging service operator's server (i.e., MO). For example, in response to the server communication module 110 sending the received certificate chain to the charging service operator's server (i.e., MO), the charging service operator's server (i.e., MO) can be configured to perform certificate chain verification. In response to the charging service operator's server (i.e., MO) determining that the certificate chain is valid, the server communication module 110 can receive the result indicating that the certificate chain is valid. Subsequently, the processor 130 can be configured to determine that the certificate chain of the second electric vehicle (EVC) is valid. Furthermore, the validity of the certificate chain of the first electric vehicle 20 can be determined based on the verification result received from the CPO server.

[0080] The processor 130 can be configured to select a first electric vehicle 20 based on request information and status information. Subsequently, the server communication module 110 can be configured to send request information to the selected first electric vehicle 20.

[0081] The processor 130 can be configured to select the first electric vehicle 20 that is closest to the second electric vehicle (EVC) by considering the positions of the first electric vehicle 20 and the second electric vehicle (EVC). For example, the processor 130 can select a candidate group of first electric vehicles 20 that match the request information of the second electric vehicle (EVC) from among a plurality of first electric vehicles 20. In this document, the candidate group can be a group of first electric vehicles 20 that match the request information in terms of status information, charging device information, communication protocol information, etc. That is, the processor 130 can be configured to select a candidate group of first electric vehicles 20 that match the second electric vehicle (EVC) in terms of charging terminals, communication protocols, required charging amount, etc.

[0082] Subsequently, the processor 130 can select the first electric vehicle 20, which is closest to the second electric vehicle (EVC) in the candidate group according to priority. The processor 130 can then be configured to send a request message to the selected first electric vehicle 20 via the server communication module 110. The server communication module 110 can then be configured to receive a response from the first electric vehicle 20 corresponding to the request message. In this case, in response to an accepted response, the processor 130 can be configured to schedule the first electric vehicle 20 to the second electric vehicle (EVC). That is, the processor 130 can be configured to control the first electric vehicle 20 to move to a location for charging the second electric vehicle (EVC). In other words, the charging management server 10 can be configured to support smart charging services by monitoring the first electric vehicle 20 and the second electric vehicle 30.

[0083] Once power supply is complete, processor 130 can be configured to execute payment. Processor 130 can be configured to generate payment information based on a payment request message received from the first electric vehicle 20. In this document, payment information may include payment amount, payment method, customer information, payment request message, etc. For example, in response to receiving a payment request message through server communication module 110, processor 130 can be configured to generate payment information. Subsequently, processor 130 can be configured to send charging service information and payment information to an external server. In this document, the external server may include the server of a charging service operator (i.e., MO) and CPS, etc. That is, charging management server 10 can be configured to support charging payment services for customer vehicles.

[0084] Reference Figure 3 The first electric vehicle 20 may be equipped with a charging management module 200, which may include a communication module 210, a charging module 220 and a control module 230.

[0085] Communication module 210 may support communication protocols for sending and receiving information with the second electric vehicle (EVC) and charging management server 10. For example, communication module 210 may support OCPP in response to sending and receiving information with charging management server 10. In addition, communication module 210 may be configured to support at least one of ISO 15118 or IEC 61850 in response to sending and receiving information with the second electric vehicle (EVC).

[0086] In response to the charging module 220 completing power supply, the communication module 210 can be configured to send charging service information to the charging management server 10. In this document, the charging service information may be an OCPP Service Description Record (SDR) and may include at least one of the following: power supply identifier, charging location information, power supply information, charging communication protocol information, charging rate information, or charging time information. Simultaneously, the communication module 210 can be configured to receive payment request messages from the second electric vehicle (EVC).

[0087] Furthermore, in response to the charging module 220 completing power supply, the communication module 210 can be configured to send the changed status information of the first electric vehicle 20 to the charging management server 10. For example, the communication module 210 can be configured to send the changed information of the first electric vehicle 20 (including the changed battery level, battery status, etc.) to the charging management server 10.

[0088] Charging module 220 can be configured to supply power to a second electric vehicle (EVC). Charging module 220 can also be configured to perform payment for charging services via communication module 210. In this document, the payment method may include the PnC method.

[0089] Control module 230 can be configured to generate response information corresponding to the request information. For example, communication module 210 can be configured to receive request information (including a request message for charging services) from charging management server 10. Here, the request message can be a message sent by a second electric vehicle (EVC) to charging management server 10. Subsequently, control module 230 can be configured to generate response information accepting the request information. Here, the response information can include at least one of a response message, scheduling information, expected charging cost information, or expected charging time information. On the other hand, control module 230 can be configured to generate a rejection message for rejecting the requested information. For example, in response to the existence of another second electric vehicle (EVC) reserved for the first electric vehicle 20, control module 230 can be configured to generate a rejection message, and communication module 210 can send the rejection message to charging management server 10.

[0090] Control module 230 can determine scheduling information based on the location of the second electric vehicle (EVC) that sent the request message. In this document, scheduling information may include expected scheduling time, expected travel distance, and expected travel route. For example, control module 230 can be configured to determine scheduling information based on the location information of the second electric vehicle (EVC) (which is included in the request information) and the current location information of the first electric vehicle 20. The current location information of the first electric vehicle 20 can be received from the Global Navigation Satellite System (GNSS) module 21 equipped in the first electric vehicle 20. Navigation device 22 equipped in the first electric vehicle 20 can guide the driver of the first electric vehicle 20 to the charging location of the second electric vehicle (EVC) based on the determined scheduling information. In this document, the charging location may be the location requested by the second electric vehicle (EVC) or the location provided by the charging management server 10. That is, the charging process can be initiated by scheduling the first electric vehicle 20 to the second electric vehicle 30.

[0091] When the charging module 220 is connected to the second electric vehicle (EVC), the control module 230 can be configured to verify the validity of the certificate chain received from the second electric vehicle (EVC). That is, in response to the connection to the second electric vehicle (EVC), the control module 230 can be configured to determine whether the identifier of the received request message matches the identifier of the certificate chain. For example, in response to the connection of the charging module 220 to the second electric vehicle (EVC), the control module 230 can be configured to receive the certificate chain from the second electric vehicle (EVC) via the communication module 210. Subsequently, the control module 230 can be configured to determine whether the electric vehicle account ID (eMobility Account ID, eMAID) included as an identifier in the request message matches the eMAID included as an identifier in the certificate chain. Here, eMAID can be the identifier of a certificate according to ISO 15118.

[0092] In response to the control module 230 determining that the identifier of the request message matches the identifier of the certificate chain, the communication module 210 can be configured to send the certificate chain along with a message indicating that the communication module 210 is connected to the second electric vehicle (EVC) to the charging management server 10. Subsequently, the charging management server 10 can be configured to verify the validity of the certificate chain of the second electric vehicle (EVC).

[0093] Furthermore, in response to the control module 230 determining that the certificate chain is valid, the charging module 220 can be configured to perform a payment process while supplying power to the second electric vehicle (EVC). In response to the charging module 220 completing power supply, the control module 230 can be configured to generate charging service information. Simultaneously, the communication module 210 can be configured to send the charging service information to the charging management server 10. Then, the communication module 210 can be configured to receive a payment request message from the second electric vehicle (EVC). Subsequently, the communication module 210 can be configured to send the received payment request message to the charging management server 10. In other words, the payment process can be performed by sending a payment request message to the charging management server 10.

[0094] As described above, the charging management system 1 according to the present invention can be configured to provide intelligent charging services, thereby improving the convenience for electric vehicle users. Furthermore, the charging management system 1 can be configured to address the location limitations of electric vehicle charging and improve the reliability of electric vehicle charging payment.

[0095] In addition, the charging management system 1 can be extended to a peer-to-peer (P2P) charging sharing service using the platform.

[0096] Figures 4 to 7 Flowcharts are shown for examples of V2V-based charging management methods. Figures 4 to 7 It can be shown that by Figure 1 The method of operating the charging management system 1. Accordingly, the same or similar configurations are indicated by the same or similar reference numerals, and repeated descriptions may be omitted. Then, for better understanding and ease of description, Figures 4 to 7 The charging management method follows the ISO 15118 protocol and OCCP. However, this is merely an example of the invention, and the invention is not limited thereto.

[0097] Reference Figure 4 In step S400, the first electric vehicle 20 can be configured to send a startup completion message and setting information to the charging management server 10. In this document, the startup completion message can be a message indicating that the first electric vehicle 20 is capable of charging and operating. That is, the startup completion message can be a message indicating that the first electric vehicle 20 is capable of receiving a charging service request from the charging management server 10. The setting information can include setting information of the charging device equipped in the first electric vehicle 20.

[0098] In step S410, the first electric vehicle 20 may be configured to send a certificate chain according to ISO 15118 to the charging management server 10.

[0099] In step S420, the charging management server 10 may be configured to verify the validity of the certificate chain regarding ISO 15118 received from the first electric vehicle 20.

[0100] In response to the charging management server 10 determining that the certificate chain is valid, in step S430, the charging management server 10 can be configured to send a message to the first electric vehicle 20 to enable the charging service. That is, the message to enable the charging service can be a message indicating that the charging management server 10 can schedule the first electric vehicle 20 to the second electric vehicle 30.

[0101] Since the certificate chain of the first electric vehicle 20 is valid, in step S440, the first electric vehicle 20 can be configured to send its real-time status information to the charging management server 10 at any time. For example, the real-time status information can be sent at regular intervals, or it can be sent in response to a change in status information.

[0102] Based on the above process, the first electric vehicle 20 can be configured to initiate the charging process.

[0103] Reference Figure 5 In step S500, the second electric vehicle 30 can be configured to send a charging service request message (eMAID) to the charging management server 10.

[0104] In step S510, the charging management server 10 can be configured to generate request information based on the request message from the second electric vehicle 30.

[0105] In step S520, the charging management server 10 can be configured to select the first electric vehicle 20 based on request information and status information.

[0106] In step S530, the charging management server 10 can be configured to send a request message to the selected first electric vehicle 20.

[0107] In step S540, the first electric vehicle 20 can be configured to accept or reject the request information based on the current state. For example, in response to the existence of another second electric vehicle EVC reserved for the first electric vehicle 20, the first electric vehicle 20 can be configured to reject the request information.

[0108] In response to the rejection request information from the first electric vehicle 20, in step S550, the first electric vehicle 20 may be configured to send a rejection message to the charging management server 10.

[0109] In response to the acceptance of the request information, in step S560, the first electric vehicle 20 can be configured to generate response information including scheduling information based on the location of the second electric vehicle 30. That is, the first electric vehicle 20 can be configured to generate response information corresponding to the request information.

[0110] In step S570, the first electric vehicle 20 can be configured to send response information to the charging management server 10.

[0111] In step S580, the charging management server 10 can be configured to dispatch the selected first electric vehicle 20 to the second electric vehicle 30 based on the response information.

[0112] In response to the completion of scheduling for the first electric vehicle 20, in step S590, the charging management server 10 may be configured to send a request message (eMAID) to the first electric vehicle 20. The request message (eMAID) may include identifier information, therefore the charging management server 10 may be configured to send a request message (eMAID) to the first electric vehicle 20 in response to the completion of scheduling.

[0113] Subsequently, both the first electric vehicle 20 and the second electric vehicle 30 can be moved to the charging position, and in step S600, the first electric vehicle 20 and the second electric vehicle 30 can be connected through the charging terminal.

[0114] Reference Figure 6 In step S600, the first electric vehicle 20 and the second electric vehicle 30 can be connected via a charging terminal.

[0115] In step S610, the second electric vehicle 30 can be configured to send an ISO 15118 charging session to the first electric vehicle 20. Subsequently, in step S620, the first electric vehicle 20 can be configured to send an ISO 15118 charging session to the charging management server 10.

[0116] In step S630, the charging management server 10 can be configured to send a message to the second electric vehicle 30 regarding the installation of a certificate according to ISO 15118. It can be assumed, in this document, that the second electric vehicle 30 does not have a certificate pre-installed. For example, the second electric vehicle 30 can be configured to send a certificate installation request message to the first electric vehicle 20. Subsequently, the first electric vehicle 20 can be configured to send the received certificate installation request message to the charging management server 10. Then, the charging management server 10 can be configured to send a certificate installation response message to the first electric vehicle 20 in response to the certificate installation request message. Finally, the first electric vehicle 20 can be configured to send the received certificate installation response message to the second electric vehicle 30.

[0117] The second electric vehicle 30 can be configured to install a certificate according to ISO 15118, and in step S640, the second electric vehicle 30 can also be configured to have an installed certificate chain according to ISO 15118. Herein, the certificate chain can be generated by a CPS server and can include eMAID as identifier information.

[0118] In step S650, the second electric vehicle 30 may be configured to send a certificate chain to the first electric vehicle 20.

[0119] In step S660, the first electric vehicle 20 may be configured to determine whether the identifier (eMAID) of the received request message matches the identifier (eMAID) of the certificate chain.

[0120] In response to a match between the identifier (eMAID) of the request message and the identifier (eMAID) of the certificate chain, in step S670, the first electric vehicle 20 may be configured to send the certificate chain to the charging management server 10.

[0121] In step S680, the charging management server 10 can be configured to verify the validity of the certificate chain. For example, the charging management server 10 can be configured to send the received certificate chain and identifier (eMAID) to the charging service operator's server (i.e., MO). Subsequently, the charging service operator's server (i.e., MO) can be configured to perform verification of the certificate chain and identifier (eMAID). The charging management server 10 can be configured to verify the validity of the certificate chain based on the verification result received from the charging service operator's server (i.e., MO).

[0122] In response to the charging management server 10 determining that the certificate chain is valid, in step S690, the charging management server 10 may be configured to send a charging start message to the first electric vehicle 20. The charging start message may contain an OCPP transaction.

[0123] In step S700, the first electric vehicle 20 can be configured to supply power to the second electric vehicle 30 based on a charging start message.

[0124] According to the above process, the first electric vehicle 20 can be configured to supply power to the second electric vehicle 30.

[0125] Reference Figure 7 In step S700, the first electric vehicle 20 can be configured to supply power to the second electric vehicle 30 based on a charging start message.

[0126] In step S710, the first electric vehicle 20 can be configured to supply power to the second electric vehicle 30.

[0127] In response to the completion of power supply, in step S720, the second electric vehicle 30 can be configured to send a payment request message to the first electric vehicle 20. Simultaneously, in response to the completion of power supply, the ISO 15118 charging session and OCPP transactions can be terminated.

[0128] In step S730, the first electric vehicle 20 can generate charging service information.

[0129] In step S740, the first electric vehicle 20 can be configured to send the received payment request message and charging service information to the charging management server 10.

[0130] In step S750, the charging management server 10 can be configured to generate payment information based on the payment request message received from the first electric vehicle 20.

[0131] In step S760, the charging management server 10 can send charging service information and payment information to the server of the charging service operator (i.e., MO). Accordingly, the payment process for the charging service can be executed.

[0132] In step S770, the first electric vehicle 20 can be configured to send changed status information to the charging management server 10. For example, the first electric vehicle 20 can be configured to send changed information (including the changed battery level, charge status, etc. of the first electric vehicle 20) to the charging management server 10.

[0133] Based on the above process, the charging management server 10 can be configured to enable the payment process.

[0134] As described above, the V2V-based charging management method according to the present invention can provide intelligent charging services, thereby improving the convenience for electric vehicle users. Furthermore, the charging management method can solve the problem of location limitations for electric vehicle charging and improve the reliability of electric vehicle charging payment.

[0135] Figure 8 An example of status information is shown.

[0136] Reference Figure 8 In this document, the status information may include at least one of the identifier of the first electric vehicle 20, charging device information, location information, price information, communication protocol information, or customer usage information. The charging management server 10 may be configured to schedule the first electric vehicle 20 in response to a request from a second electric vehicle (EVC) based on the status information of the first electric vehicle 20.

[0137] like Figure 8As shown, (a) could be the current recording time. For example, status information can be sent in real time, so it could include information related to the current recording time.

[0138] Continue to refer to Figure 8 The identifier may include the information described in (b) and (c). For example, the identifier may include a charging device identifier and a charging equipment identifier provided in the first electric vehicle 20. (b) may be a charging device identifier. The charging device identifier may include a code for identifying the charging device. (c) may be a charging equipment identifier. For example, it may be a code for identifying the charging device (such as a charging terminal).

[0139] Continue to refer to Figure 8 Customer usage information may include the information described in (d) through (f). For example, (d) is charging device usage information, which may be described as available, charging, or reserved. (e) is the reason for the change in charging device usage information, which may describe the reason for the change. (f) may be reserved customer information.

[0140] Continue to refer to Figure 8 (g) can be the current location. For example, location information can include the current location.

[0141] Continue to refer to Figure 8 The charging device information may include the information described in (h) through (k). (h) may be the battery's State of Charge (SOC). (i) may be the battery's minimum sustaining SOC. (j) may be the battery's charging capacity capable of providing maximum charging service. In this case, the unit of the charging device information may be watt-hours (Wh). (k) may be the maximum driving range based on the battery's charging capacity.

[0142] Continue to refer to Figure 8 (l) can be the schedulable time. For example, the schedulable time can include a range of time that can be scheduled. First, the schedulable time can be determined based on the current state of the driver of the first electric vehicle 20.

[0143] Continue to refer to Figure 8 (m) can be a price tag. For example, price information can include a price list.

[0144] Continue to refer to Figure 8 (n) can be the maximum power or the minimum power. Alternatively, (n) can be the maximum voltage / current or the minimum voltage / current. For example, charging device information may include the maximum power or the minimum power. Alternatively, charging device information may include the maximum voltage / current or the minimum voltage / current.

[0145] Continue to refer to Figure 8 (o) can be the type of charging terminal. For example, charging device information can include the type of charging terminal.

[0146] Continue to refer to Figure 8 (p) can be a charging communication standard protocol. For example, the communication protocol information may include the charging communication standard protocol (e.g., ISO 15118) supported by the first electric vehicle 20.

[0147] Figure 9 An example of a request for information is shown.

[0148] Reference Figure 9 The request information may include at least one of the following: the user identifier of the second electric vehicle (EVC), user information, battery information, location information, or a request message. The charging management server 10 can be configured to generate the request information based on information related to the second electric vehicle (EVC).

[0149] Continue to refer to Figure 9 (a) can be a unique request ID. For example, a request message may include a unique request ID that identifies the user of the second electric vehicle (EVC) making the request.

[0150] Continue to refer to Figure 9 (b) can be the validity period of the request. For example, the request message may include an eMAID and a request validity period.

[0151] Continue to refer to Figure 9 The battery information may include the information described in (c) and (d). (c) may be the charging terminal type of the second electric vehicle (EVC). (d) may be an identifier of the battery charging device of the second electric vehicle (EVC).

[0152] Continue to refer to Figure 9 User information may include the information described in (e) and (f). (e) may be personal user information, and personal user information may include eMAID. (f) may be user group information.

[0153] Continue to refer to Figure 9 (g) could be the location of a charging service request. For example, location information could include the location of a second electric vehicle (EVC) requesting a charging service.

[0154] Continue to refer to Figure 9 , (h) can be the amount of charge required. For example, a request message can contain the requested amount of charge.

[0155] Continue to refer to Figure 9The request message may include the information described in (i) and (j). (i) may be the start time of the charging service. (j) may be the end time of the charging service.

[0156] Continue to refer to Figure 9 (k) can be the maximum power or the minimum power. Alternatively, (k) can be the maximum voltage / current or the minimum voltage / current. For example, battery information may include the maximum power or the minimum power. Alternatively, battery information may include the maximum voltage / current or the minimum voltage / current.

[0157] Figure 10 An example of the response information is shown.

[0158] Reference Figure 10 The response information may include at least one of the following: a response message from the first electric vehicle 20, scheduling information, expected charging cost information, or expected charging time information. The first electric vehicle 20 may be configured to generate response information corresponding to the request information.

[0159] Continue to refer to Figure 10 The response message may include the information described in (a) and (b), where (a) may be a response code and (b) may be detailed response information.

[0160] Continue to refer to Figure 10 (c) could be the expected arrival time. For example, the scheduling information for the first electric vehicle 20 could include the expected scheduling time. Furthermore, the scheduling information could include the expected travel distance and the expected travel route.

[0161] Continue to refer to Figure 10 (d) could be the expected charging cost. For example, expected charging cost information could include the expected charging cost.

[0162] Continue to refer to Figure 10 (e) could be the expected charging time. For example, expected charging time information could include the expected charging time.

[0163] Figure 11 An example of charging service information is shown.

[0164] Reference Figure 11 In this document, the charging service information may include at least one of the following: a power supply identifier between the first electric vehicle 20 and the second electric vehicle 30; charging location information; power supply information; charging communication protocol information; charging rate information; or charging time information. In response to completing power supply to the second electric vehicle (EVC), the first electric vehicle 20 may be configured to generate charging service information. For example, the charging service information may be an OCPP SDR (Service Response Diagram).

[0165] Continue to refer to Figure 11(a) can be a transaction ID. For example, a power supply identifier according to a charging communication standard protocol can include a transaction ID.

[0166] Continue to refer to Figure 11 (b) can be the charging execution location. For example, the charging location information can be the charging execution location.

[0167] Continue to refer to Figure 11 (c) can be the charging device ID. For example, the power supply identifier can include the charging device ID.

[0168] Continue to refer to Figure 11 The power supply information may include the content described in (d) and (e). (d) may be the charging terminal type, and (e) may be the charging power transmission type. For example, (e) may be described as wireless power transmission or wired power transmission type.

[0169] Continue to refer to Figure 11 (f) may be a charging communication standard protocol. For example, the charging communication protocol information may include a charging communication standard protocol (e.g., ISO 15118) that supports charging between the first electric vehicle 20 and the second electric vehicle 30.

[0170] Continue to refer to Figure 11 The charging time information may include the content described in (g) through (j). (g) may be the departure time after scheduling. (h) may be the arrival time at the charging service execution location. (i) may be the charging start time. (j) may be the charging end time.

[0171] Continue to refer to Figure 11 , (k) can be the supplied charging capacity. For example, power supply information may include the supplied charging capacity and the cumulative metering value before and after charging.

[0172] Continue to refer to Figure 11 (l) can be the charging scheduling distance. For example, charging location information can be the charging scheduling distance.

[0173] Continue to refer to Figure 11 , (m) can be a metering value type. For example, charging communication protocol information can include metering value types. Metering value types can include metering values ​​for a charging session or clock time series metering values.

[0174] The charging rate information may include the charging rate determined based on the power supply information mentioned above.

[0175] Figures 8 to 11 The description is illustrative and the invention is not limited thereto.

[0176] Figure 12A block diagram of an exemplary computing system 1000 for displaying a charging management system 1 and / or a charging management server 10 is shown.

[0177] Reference Figure 12 The computing system 1000 includes at least one processor 1100, a memory 1300, a user interface input device 1400, a user interface output device 1500, a storage device 1600, and a network interface 1700 connected via a bus 1200.

[0178] Processor 1100 may be a central processing unit (CPU) or a semiconductor device that executes processing of instructions stored in memory 1300 and / or storage device 1600. Memory 1300 and storage device 1600 may include various types of volatile or non-volatile storage media. For example, memory 1300 may include read-only memory (ROM) and random access memory (RAM).

[0179] Accordingly, the steps of the methods or algorithms described in conjunction with the exemplary embodiments included herein can be implemented (e.g., directly) by hardware, a software module executed by processor 1100, or a combination of both. The software module can reside in a storage medium (e.g., memory 1300 and / or storage device 1600), such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, and CD-ROM.

[0180] An exemplary storage medium is coupled to processor 1100, which can read information from and write information to the storage medium. Alternatively, the storage medium can be integrated with processor 1100. The processor and storage medium can reside within an application-specific integrated circuit (ASIC). The ASIC can reside within the user terminal. Alternatively, the processor and storage medium can reside as separate components within the user terminal.

[0181] User interface input device 1400 can be configured to include an input device for receiving user input.

[0182] The user interface output device 1500 can be configured to include a display for displaying various information and a speaker for outputting various sounds.

[0183] Network interface 1700 can be configured to include long-range communication modules and / or short-range communication modules for sending and receiving data with external devices such as servers or user terminals. For example, network interface 1700 can indicate communication modules capable of performing wireless Internet communications such as Wireless LAN (WLAN), Wireless Broadband (Wibro), WiFi, World Interoperability for Microwave Access (WiMAX), and High Speed ​​Downlink Packet Access (HSDPA).

[0184] The above description is an illustrative example of the technical concept of the present invention. Those skilled in the art can make various modifications and changes without departing from the features of the present invention.

[0185] Therefore, the exemplary embodiments disclosed in this invention are not intended to limit the technical concept of the invention, but rather to explain it, and the scope of the technical concept of the invention is not limited by these exemplary embodiments. Technical concepts within the equivalent scope should be interpreted as including within the scope of this invention.

Claims

1. A charging management system, comprising: At least one first electric vehicle, the at least one first electric vehicle being configured to supply power to at least one second electric vehicle requesting charging service; as well as A charging management server configured to manage charging services based on the communication protocol between the first electric vehicle and the second electric vehicle; The charging management server is configured to support payment for the charging service by verifying the certificate chain of the communication protocol of the charging service.

2. The charging management system according to claim 1, wherein, The communication protocol supports at least one of the following: Open Charging Point Protocol, ISO 15118, or IEC 61850.

3. The charging management system according to claim 1, wherein, The first electric vehicle is configured to include: A communication module configured to support a communication protocol for sending and receiving information with the second electric vehicle and the charging management server; A control module configured to verify the validity of the certificate chain received from the second electric vehicle; and The charging module is configured to perform payment processing when power supply to the second electric vehicle is completed, provided the certificate chain is valid.

4. The charging management system according to claim 3, wherein, The communication module is configured to receive charging service request messages from the charging management server.

5. The charging management system according to claim 4, wherein, When the charging module is connected to the second electric vehicle, the control module is configured to determine whether the identifier of the received request message matches the identifier of the certificate chain.

6. The charging management system according to claim 5, wherein, When the control module determines that the identifier of the received request message matches the identifier of the certificate chain, The communication module is configured to send a certificate chain to the charging management server. The charging module is configured to supply power to the second electric vehicle.

7. The charging management system according to claim 6, wherein, When the charging module has finished supplying power. The control module is configured to generate charging service information. The communication module is configured to send charging service information to the charging management server and receive payment request messages from the second electric vehicle.

8. The charging management system according to claim 7, wherein: The charging management server is configured to include: The server communication module is configured to support a communication protocol for sending and receiving information with the first electric vehicle. A memory configured to store at least one instruction; and A processor configured to access memory and execute at least one instruction, wherein the at least one instruction includes: Verify the validity of the received certificate chain. Based on the verification results, control the first electric vehicle to supply power. Payment processing will be executed when power is supplied.

9. The charging management system according to claim 8, wherein, The at least one instruction further includes: generating payment information based on a payment request message received from the first electric vehicle.

10. The charging management system according to claim 9, wherein, When a payment request message is received, the server communication module is configured to send charging service information and payment information to an external server.

11. A charging management method, comprising: Powered by the first electric vehicle; The second electric vehicle requests charging service and receives power from the first electric vehicle; The charging service is managed by the charging management server based on the communication protocol between the first electric vehicle and the second electric vehicle. The charging management server supports payment for the charging service by verifying the certificate chain of the communication protocol of the charging service.

12. The charging management method according to claim 11, wherein, The communication protocol supports at least one of the following: Open Charging Point Protocol, ISO 15118, or IEC 61850.

13. The charging management method according to claim 12, wherein, Power supply includes: A communication protocol supported by the first electric vehicle for sending and receiving information with the second electric vehicle and the charging management server; The validity of the certificate chain received from the second electric vehicle is verified by the first electric vehicle; In response to a valid certificate chain, power is supplied from the first electric vehicle to the second electric vehicle. When power supply is complete, the first electric vehicle receives the payment request message from the second electric vehicle. The payment is processed by the first electric vehicle.

14. The charging management method according to claim 13, wherein, Supported communication protocols include: the first electric vehicle receiving a charging service request message from the charging management server.

15. The charging management method according to claim 14, wherein, Verifying the validity of the certificate chain includes: the first electric vehicle determining whether the identifier of the received request message matches the identifier of the certificate chain.

16. The charging management method according to claim 15, wherein, Providing power to the second electric vehicle includes: The first electric vehicle sends the certificate chain to the charging management server; The first electric vehicle supplies power to the second electric vehicle.

17. The charging management method according to claim 13, wherein, Power supply includes: Charging service information is generated by the first electric vehicle; The first electric vehicle determines whether the identifier of the received request message matches the identifier of the certificate chain; The first electric vehicle sends the certificate chain to the charging management server; The first electric vehicle supplies power to the second electric vehicle.

18. The charging management method according to claim 17, wherein, The power supply further includes: the first electric vehicle sending its changed status information to the charging management server.

19. The charging management method according to claim 18, wherein, Managing charging services includes: The charging management server supports a communication protocol for sending and receiving information with the first electric vehicle. The validity of the received certificate chain is verified by the charging management server; The charging management server controls the first electric vehicle to supply power based on the verification results; In response to the completion of power supply, the payment process is executed by the charging management server.

20. The charging management method according to claim 19, wherein, Executing payment processing includes: The charging management server generates payment information based on the payment request message received from the first electric vehicle; The charging management server sends charging service information and payment information to external servers.

Images