Value-added service communication method based on support provider list and apparatus therefor

Abstract

The present invention provides a communication method for constructing a new VAS environment such that a legacy charger supporting a charging service in V2G communication can provide a support provider list (SPL) to an EV, and an apparatus using the same. The communication method performed by the SECC comprises the steps of: receiving a request message for a service list of a charging service from the EV; providing a service list to the EV, the service list including a first service identifier of a dedicated VAS for providing an SPL for the EMSP; receiving a request message for parameters of the dedicated VAS from the EV; and providing the EV with at least one set of service parameters for the SPL supporting the dedicated VAS.

Description

Technical Field

[0001] This disclosure relates to vehicle-to-grid (V2G) communication technology between vehicles and the power grid, and more specifically, to a communication method for establishing a value-added service (VAS) environment and an apparatus for using the method, which allows conventional chargers providing charging services to road vehicles such as electric vehicles (EVs) to a list of support providers (SPLs) for EVs in V2G communication. Background Technology

[0002] The message sequence between the power grid and the electric vehicle (EV) is predefined between the charger management device or power supply equipment communication controller (SECC) of the charging point operator (CPO) located on the grid side corresponding to the power grid and the electric vehicle communication controller (EVCC) installed on the EV, and is executed in the form of exchanging a pair of request and response messages between the two.

[0003] High-voltage batteries installed in EVs are typically charged using alternating current (AC) or direct current (DC), or using charging methods based on automatic connection device (ACD) or wireless power transfer (WPT).

[0004] On the other hand, some existing chargers, the SECC that controls EV charging, support a feature called the Supported Provider List (SPL). The SPL allows EVs to check the AuthorizationSetupRes message list of electric mobility service providers (eMSPs), and also enables EVs to verify the charger's compatibility with Park-to-Call (PnC) or Plug-and-Charge, and select the appropriate contract certificate issued by the preferred eMSP.

[0005] However, many existing chargers do not yet support SPL functionality, and a method is needed to activate SPL functionality in traditional chargers that do not support this type of SPL feature. Summary of the Invention

[0006] Technical issues

[0007] This disclosure aims to meet the needs of the aforementioned conventional technology. The purpose of this disclosure is to provide a communication method for a Dedicated Value-Added Service (VAS) and an apparatus for using the communication method, which, while maintaining interoperability with conventional chargers, provides a list of support providers (SPL) for the EV from a conventional charger that does not support SPL functionality (e.g., an apparatus related to electric vehicle (EV) charging as defined in ISO 15118-2).

[0008] Another object of this disclosure is to provide a communication method for a dedicated VAS and an apparatus for using the communication method, wherein the dedicated VAS provides SPL information while maintaining interoperability with existing conventional chargers.

[0009] Technical solution

[0010] A communication method according to one aspect of the invention for achieving the above objectives, used for value-added services (VAS) in V2G (vehicle-to-grid) communication, executed by a power supply equipment communication controller (SECC), the communication method comprising: receiving a request message from an electric vehicle (EV) for a service list of charging services; providing the EV with a service list, the service list including a first service identifier of a dedicated VAS used to provide a list of support providers for electric mobility service providers (EMSPs); receiving a request message from the EV for parameters of the dedicated VAS; and providing the EV with at least one set of service parameters for the list of support providers for the dedicated VAS.

[0011] Providing an EV with a list of services including a first service identifier may include sending a service discovery response message to the EV.

[0012] Receiving a request message for parameters of a dedicated VAS from the EV may include receiving a service details request message from the EV.

[0013] Providing at least one set of service parameters to an EV may include sending a service details response message to the EV in response to a service details request message.

[0014] Service discovery response messages may contain service elements, which include a first service identifier, a service name representing a list of supported providers, and a service category representing information about electric vehicle power supply equipment (EVSE).

[0015] The service discovery response message may further include a service element indicating whether the service is free.

[0016] At least one set of service parameters may include a string value of a provider identifier whose parameter name is set to "Provider", with the provider identifier separated by commas.

[0017] Each provider identifier includes the country code from the Mobility Authentication Identifier (EMAID) and the provider ID.

[0018] The list of supported providers may include a list of providers that support PnC (plug and charge / park and charge) licenses.

[0019] The communication method may further include: generating a single set of service parameters that lists all providers in the list of supported providers; or generating multiple sets of service parameters that are classified and listed based on predefined criteria.

[0020] The communication method may further include: receiving a contract certificate chain from the EV via a payment details request message, the contract certificate chain having a Mobility Authentication Identifier (EMAID) supported by a list of supported providers.

[0021] An apparatus according to another aspect of the invention for achieving the above objectives is used for value-added services (VAS) in V2G (Vehicle-to-Grid) communication. The apparatus includes a processor and at least one instruction loaded into the processor. Through the at least one instruction, the processor: receives a request message from an electric vehicle (EV) for a service list of charging services; provides the EV with the service list, the service list including a first service identifier of a dedicated VAS used to provide a list of support providers for Electric Mobility Service Providers (EMSPs); receives a request message from the EV for parameters of the dedicated VAS; and provides the EV with at least one set of service parameters for the list of support providers for the dedicated VAS.

[0022] The processor can be further configured to: generate a single set of service parameters that lists all providers in the supported provider list; or generate multiple sets of service parameters that are classified based on predefined criteria and list all providers in the supported provider list.

[0023] The processor can be further configured to receive a contract certificate chain from the EV via a payment details request message, the contract certificate chain having a Mobility Authentication Identifier (EMAID) supported by a list of supported providers.

[0024] A communication method according to another aspect of the invention for achieving the above objectives, used for value-added services (VAS) in V2G (vehicle-to-grid) communication, is executed by an electric vehicle communication controller (EVCC). The communication method includes: requesting a service list for EV charging services from a power supply equipment communication controller (SECC); receiving the service list from the SECC, the service list including a first service identifier for a dedicated VAS used to provide a list of support providers for electric mobility service providers (EMSPs); requesting parameters for the dedicated VAS from the SECC; and receiving at least one set of service parameters from the SECC for the list of support providers supporting the dedicated VAS.

[0025] Receiving a list of services including the first service identifier may include receiving a service discovery response message from the SECC.

[0026] The parameters for requesting a dedicated VAS may include sending a service details request message to the SECC.

[0027] Receiving at least one set of service parameters may include: receiving a service details response message from SECC in response to a service details request message.

[0028] Service discovery response messages may contain service elements, which include a first service identifier, a service name representing a list of supported providers, and a service category representing information about electric vehicle power supply equipment (EVSE).

[0029] The service discovery response message may further include a service element indicating whether the service is free.

[0030] At least one of the service parameter sets includes at least one string value of a provider identifier whose parameter name is set to "Provider".

[0031] Provider identifiers can be separated by commas.

[0032] Each provider identifier may include the country code and provider ID from the first five characters of the Mobility Authentication Identifier (EMAID).

[0033] The communication method may further include sending a contract certificate chain to the SECC via a payment details request message, the contract certificate chain having a mobile travel authentication identifier (EMAID) supported by a list of supported providers.

[0034] Beneficial effects

[0035] According to this disclosure, a list of support providers (SPLs) for value-added services (VAS) can be provided to existing electric vehicle (EV) chargers and other legacy devices without maintaining interoperability with legacy devices or modifying the architecture or requirements of the legacy devices. Therefore, it is possible to support legacy devices in providing various value-added services to EVs during EV charging.

[0036] Additionally, according to this disclosure, a service specifically designed to provide a list of support providers (SPL) containing information on available providers can be implemented as a value-added service (VAS) as defined by standards such as ISO 15118-2.

[0037] Furthermore, according to this disclosure, value-added services or VAS can be effectively implemented without modifying traditional devices by utilizing the service parameter elements of ServiceDetailRes messages.

[0038] Furthermore, according to this disclosure, the additional VAS communication that must be performed subsequently can be eliminated. Thus, during the service selection process, EVs do not need to be required to select value-added services, thereby ensuring user choice and convenience. Attached Figure Description

[0039] Figure 1 This is an example diagram illustrating an electric vehicle charging method that can be applied to the communication method according to this disclosure.

[0040] Figure 2 This is another example diagram illustrating an electric vehicle charging method to which the communication method according to this disclosure can be applied.

[0041] Figure 3 This is a schematic block diagram illustrating the communication relationship between an electric vehicle communication controller (EVCC), a power supply equipment communication controller (SECC), and an auxiliary participant (SA) to which the communication method according to this disclosure can be applied.

[0042] Figure 4 This is a flowchart illustrating a detailed process of a communication method for value-added services based on a list of supported providers, according to exemplary embodiments of the present disclosure.

[0043] Figure 5 It can be applied to Figure 4 Example diagram of the configuration of the list of providers of communication methods.

[0044] Figure 6 This is a diagram illustrating the configuration of the mobile authentication identifier, used for explanation. Figure 5 Configuration of each provider identifier within the provider list.

[0045] Figure 7 This is a flowchart illustrating a communication method according to other exemplary embodiments of the present disclosure.

[0046] Figure 8 It is used to illustrate the application of the method. Figure 7 Example diagram of detailed items in the service list within the message of the communication method's value-added services.

[0047] Figure 9 It is used to explain the basis Figure 7 An example diagram illustrating the interoperability effects of the communication methods.

[0048] Figure 10 This is a schematic block diagram illustrating a general hardware configuration of an apparatus for providing a list of support providers (SPL) for value-added services (VAS) according to other exemplary embodiments of this disclosure.

[0049] Best practice

[0050] To better understand the features and advantages of this disclosure, exemplary embodiments of the disclosure will be described in detail with reference to the accompanying drawings. However, it should be understood that this disclosure is not limited to the specific embodiments disclosed herein, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of this disclosure. In the drawings, similar or corresponding components may be represented by the same or similar reference numerals.

[0051] The terms used in this specification to describe various components, such as ordinal numbers like "first" and "second," are used to distinguish components from other components but are not intended to limit any particular component. For example, a second component may be referred to as a first component without departing from the scope of this disclosure, and similarly, a first component may be referred to as a second component. The term "and / or" as used herein may include the presence of one or more of the associated listed items and any and all combinations of the listed items.

[0052] When a component is referred to as "connected" or "linked" to another component, the component may be logically or physically directly connected or linked to the other component, or it may be indirectly connected or linked to the other component through an object between them. Conversely, when a component is referred to as "directly connected" or "directly linked" to another component, it should be understood that there is no intermediate object between the components. Other terms used to describe the relationship between components should be interpreted in a similar manner.

[0053] The terminology used herein is for describing specific exemplary embodiments only and is not intended to limit this disclosure. Unless the context clearly specifies otherwise, the singular form also includes the plural reference. Furthermore, the expressions “comprising,” “including,” “construction,” and “configuration” are used to refer to the presence of combinations of said features, numbers, processing steps, operations, elements, or components, but are not intended to exclude the presence or addition of other features, numbers, processing steps, operations, elements, or components.

[0054] Unless otherwise defined, all terms used herein, including technical or scientific terms, shall have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. Terms such as those defined in common dictionaries shall be interpreted as having the same meaning as in the context of the relevant literature, and shall not be construed as having an idealized or overly formal meaning unless expressly defined in this application.

[0055] The terms used in this disclosure are defined as follows.

[0056] "Smart grid": A system that intelligently connects power plants, generator sets, and energy storage systems through network infrastructure to exchange messages based on information and communication technologies.

[0057] “Charging station”: A facility consisting of one or more EVSEs, smart meters and other technical equipment required for charging EVs.

[0058] "Electric Vehicle (EV)": As defined in Title 49, Section 523.3 of the Federal Regulations, an electric vehicle used for road travel is driven by an electric motor that draws current from an onboard energy storage device such as a battery, which can be charged by an external power source (such as a residential or public power service or an onboard fuel cell generator). EVs can include electric vehicles, electric cars, electric road vehicles (ERVs), plug-in vehicles (PVs), and electric drive vehicles (xEVs), and xEVs can be further categorized into plug-in all-electric vehicles (BEVs), pure electric vehicles, plug-in electric vehicles (PEVs), hybrid electric vehicles (HEVs), hybrid plug-in electric vehicles (HPEVs), and plug-in hybrid electric vehicles (PHEVs). "Plug-in Electric Vehicle (PEV)": An electric vehicle that charges its main battery via connection to the power grid.

[0059] "Electric Vehicle Power Supply Equipment (EVSE)": A device that forms part of a charging station, supplies power to electric vehicles via a socket and is connected to a smart meter to measure the amount of electricity transmitted.

[0060] "Wireless Power Charging System (WCS)": A system for wireless power transmission and interactive control, the interaction including alignment and communication operations between the power supply unit (or ground component) and the EV unit (or vehicle component).

[0061] "Wireless Power Transfer (WPT)": Transferring power between power sources (such as utilities, power grids, energy storage devices, fuel cell generators) and EVs through non-contact channels such as electromagnetic induction and resonance.

[0062] "Utilities": A group of systems that provide electricity, including Customer Information Systems (CIS), Advanced Metering Infrastructure (AMI), rate and revenue systems, etc. Utilities can supply electricity to EVs through rate tables and discrete events. In addition, utilities can provide information related to EV certification, power consumption measurement intervals, and electricity pricing.

[0063] "Smart charging": A system in which EVSE and / or EV (including PEV or PHEV) communicate with the grid to optimize EV charging or discharging rates by reflecting grid capacity or usage costs.

[0064] "Interoperability": The state in which system components interact with corresponding system components to perform system target operations. Additionally, information interoperability can refer to the ability of two or more networks, systems, devices, applications, or components to efficiently share and easily use information without causing inconvenience to users.

[0065] "Inductive charging system": A system that transfers energy from a power source to an EV through a two-part air-gap iron-core transformer, wherein the two halves of the transformer, namely the primary coil and the secondary coil, are physically separated from each other. In this disclosure, the inductive charging system can correspond to an EV power transmission system.

[0066] "Inductive coupling": Magnetic coupling between two coils. One of the two coils can refer to the primary coil or GA coil, and the other can refer to the secondary coil or VA coil of a vehicle component.

[0067] "OEM (Original Equipment Manufacturer)": A server operated by an electric vehicle manufacturer, which may be a root certificate authority (CA) that issues the OEM root certificate.

[0068] "Charging Point Operator (CPO)": A company or organization that has the authority to allow physical access to a charging station location; or a communication node or entity that manages charging stations and uses information and communication technologies to authorize and control the charging process on each individual EVSE.

[0069] "Charging Service Provider (CSP)": An entity responsible for managing and verifying EV user credentials, billing, and providing other value-added services to customers. It can be considered a specific type of Mobility Operator (MO) or implemented as an entity integrated with a MO.

[0070] "Clearing House (CH)": An entity that handles cooperation between MOs, charging service providers (CSPs) and charging station operators (CSOs), and in particular can act as an intermediary to facilitate authorization, billing and settlement procedures related to EV charging service roaming between the two clearing parties.

[0071] "Roaming": A scheme and related exchange of information and terms that allows EV users to access charging services provided by multiple CSPs or CSOs in different mobility networks using a single credential and contractual agreement.

[0072] "Credentials": Physical or digital assets that represent the personal identity of an EV or its owner and may contain encrypted information used to verify identity, such as passwords, public / private key pairs used in public-key encryption algorithms, public key certificates issued by certification authorities, and information related to trusted root certification authorities.

[0073] "Certificate": An electronic document that binds a public key to an identity through digital signature.

[0074] "Service Session": A set of EV charging services provided at a charging point, allocated to customers within a specified time frame, and identified by a unique identifier.

[0075] "Mobility Operator (MO)": A legal entity that establishes contractual relationships with end-users or business entities, which serve as the legal basis for authorizing and paying for charging at charging stations. MO can refer to Electric Mobility Provider (EMP) or Electric Mobility Service Provider (EMSP).

[0076] "Plug and Charge (PnC)": When a user simply plugs their electric vehicle into the EVSE, the process of authentication, authorization, load control, and payment is automatically performed without any additional user interaction. Alternatively, PnC can refer to the identification and authorization mode of such automated processes. PnC can be performed by applying X.509 certificates and transmitting and verifying signatures.

[0077] "Public Key Infrastructure (PKI)": A system for creating, storing, redistributing, and revoking digital signatures used to verify whether a particular public key belongs to a particular individual or entity.

[0078] External Identification Method (EIM): An external method by which any driver can authenticate and authorize themselves at a charging station for a charging session. Examples include cash payment, prepaid cards, credit cards, debit cards, NFC, RFID, and SMS. EIM can be used in conjunction with Point-of-Card (PnC) to form two typical authentication modes.

[0079] "Electricity Sales Price": A function that provides price-related information over time. The electricity sales price can refer to input provided by a mobility operator, enabling the EVCC to calculate charging schedules based on the electricity sales price. The electricity sales price may be a concept designed to incentivize electric vehicles to charge with preferred power levels during specific time periods. A use case related to the electricity sales price could be electricity price information provided by a mobility operator that authenticates a charging session based on a valid contract, in which case the contract could be authenticated by the car-sharing operator to which the driver or vehicle belongs via a contract certificate installed on the electric vehicle.

[0080] Additionally, the term "sales price of electricity" as used in this article can refer to a concept designed to encourage the use of renewable energy, such as electricity generated through solar panels or wind turbines, by providing incentives to electric vehicles that are charged by renewable energy sources during a predictable period of time. In some cases, the sales price of electricity may include not only price information but also the time period associated with that price information.

[0081] "Auxiliary Participants": Entities other than EVCCs or SECCs that participate in the charging process. Auxiliary participants can participate in the charging process by providing information related to it. Examples of auxiliary participants can include charging point operators (CPOs) and mobility operators (MOs).

[0082] "Electric Mobility Account Identifier (EMAID)": A single contract certificate issued for each legal contract between a mobility operator and a customer regarding electric vehicle charging. An EMAID can refer to a unique contract certificate issued for each legal agreement between a mobility operator and a customer regarding electric vehicle charging. EMAIDs may allow for the pseudonymization of personal data and may only be valid for a limited time, such as within the validity period of the legal contract. Unlike a Vehicle Identification Number (VIN), an EMAID may not be used for long-term evaluation of customer or vehicle data. EMAIDs can be used as temporary identifiers and can be assigned to each temporary or short-term contract for private or shared vehicles using different authentication media. An individual may have a separate EMAID for each of the multiple contracts they participate in, allowing the EMAID to be used for purposes other than personally identifiable information.

[0083] The term “vehicle-to-grid (V2G) communication” used in this article is defined in the ISO 15118 standard and can be designed to correspond to the seven layers of the Open Systems Interconnection (OSI) model. OSI can be “a conceptual model for standardizing the communication functions of communication or computing systems, regardless of their internal structure and technology.”

[0084] The ISO 15118 standard is characterized by its aim to establish and implement charging and payment processes for electric vehicles, and it can employ and utilize various information and communication technologies for this purpose. Although the ISO 15118 standard relates to information and communication technology elements mapped to OSI 7 layers, its functionality may be primarily application-specific due to its goal of establishing charging and payment processes for electric vehicles.

[0085] The V2G communication interface specified in the ISO 15118 standard can include IP-based digital protocols. Communication between EVs and EVSEs, as well as communication between EVCCs and SECCs, can be included in the V2G communication interface specified in the ISO 15118 standard.

[0086] The V2G communication interface and the ISO 15118 standard are designed to activate a user-friendly mechanism for performing authentication, authorization, and payment without requiring additional user interaction at the charging station.

[0087] Electric vehicles can be integrated into smart grids to provide flexible load control and valuable grid services without affecting drivers' driving habits. To avoid requiring additional grid components to meet peak power demands caused by drastic load fluctuations, the energy source of electric vehicles can be considered one of the energy sources within the smart grid. Furthermore, appropriate incentives for electric vehicles can be considered to expand the scale of smart grids, thereby enabling them to encourage the production and use of renewable energy in the long term.

[0088] The OSI 5-layer Vehicle-to-Grid Transport Protocol (V2GTP) can essentially be understood as a session wrapper for application layer messages. These application layer messages can be referred to as V2G messages. V2GTP can include definitions for headers and payloads to facilitate efficient classification and processing of V2G messages.

[0089] In the electric vehicle charging system used to implement this disclosure, an electric vehicle (EV) can be connected to a charging station via a wired or wireless link to receive energy from the charging station and can use the received energy to charge an energy storage device such as a battery.

[0090] Figure 1 This is an example diagram illustrating an electric vehicle charging method to which the communication method according to this disclosure can be applied. Figure 2 This is another example diagram illustrating an electric vehicle charging method to which the communication method according to this disclosure can be applied. That is, Figure 1 and Figure 2 Methods for charging electric vehicles using wired and wireless connections are shown respectively.

[0091] Figure 1 This is a conceptual diagram illustrating a wired charging method for an electric vehicle to which the communication method of this disclosure can be applied.

[0092] like Figure 1 As shown, wired charging of an electric vehicle can be performed by connecting the electric vehicle (hereinafter referred to as "EV") 10 to the power circuit of a charging station via a charging cable 30, for example, by connecting the charging station (see [link to charging station]). Figure 2 (See attached figure 20) Connector 31 at one end of the cable to the inlet of EV 10 to perform this action.

[0093] Here, EV 10 can be defined as a vehicle that receives electricity from a rechargeable energy storage device (such as a battery) as an energy source for its power unit (such as an electric motor). EV 10 can be a hybrid vehicle equipped with both an electric motor and a conventional internal combustion engine.

[0094] Besides automobiles, the EV 10 described above can be replaced with any form of mobility device, such as motorcycles, trucks, scooters, electric bicycles, etc. However, for the sake of clarity, this manual will focus on describing the EV.

[0095] EV 10 may include inlets, plug connectors, sockets, etc., that can be connected to connector 31 of charging cable 30. The inlets provided in EV 10 may support slow charging or fast charging. In this case, EV 10 may support both slow charging and fast charging through a single inlet, or may include multiple inlets that support slow charging and fast charging respectively.

[0096] The EV 10 in this exemplary embodiment may include an on-board charger (OBC) to support slow charging or charging via alternating current (AC) from the general power grid. During slow charging, the OBC can boost the AC power from an external wired power source and convert the boosted AC power into direct current (DC) power to supply the EV 10's built-in battery. Conversely, when the DC power required for fast charging is supplied to the inlet, the DC power can be directly supplied to the battery without passing through the OBC, thereby charging the battery.

[0097] On the other hand, the EV charging cable 30 can be configured to include a charging connector 31, a receptacle connection 33, and an internal control box (ICCB) 32. In this case, the charging connector 31 can be a connector capable of electrically connecting to the EV 10, and the internal control box 32 can communicate with the EV 10 to receive EV status information or control the charging power of the EV 10. The internal control box 32 is illustrated as being included in the EV charging cable 10, but it can also be connected to a power supply circuit (not shown) supplying power to the EV 10 at a location other than the EV charging cable 10 (e.g., at a charging station), or it can be disposed within the power supply circuit. The receptacle connection 33 can be an electrical connection mechanism such as a plug or connector, and can be connected to a receptacle 40 at the charging station.

[0098] On the other hand, socket 40 can refer to the connection point between the power supply unit or charger of the charging station and the EV charging cable 30. Socket 40 can also refer to the connection point between the charger installed in other locations and the EV charging cable 30. For example, in addition to commercial dedicated charging station facilities, socket 40 can also be installed in charging facilities, such as in the parking lot of an EV 10 owner's home, a parking space at a gas station designated for EV charging, or a parking space in a shopping mall or workplace.

[0099] Figure 2 This is a conceptual diagram illustrating a wireless power transmission method for an electric vehicle to which the communication method of this disclosure can be applied.

[0100] like Figure 2 As shown, wireless power transfer (WPT) of an EV can be defined as the transfer of electrical energy from a power supply device to a power consumption device via a magnetic field in a magnetic resonance state, without the need for current flow through a current connection in the power supply network. Wireless power transfer can be used to transfer power from charging station 10 to EV 10, thereby charging EV 10.

[0101] Wireless power transfer can be performed by at least one component of the EV 10 or the charging station 20 to wirelessly transfer power to the EV 10.

[0102] EV 10 may include a receiver plate 11 having a receiving coil for wirelessly receiving magnetic energy from charging station 20. The receiving coil in receiver plate 11 receives magnetic energy from transmitting coil in transmitting plate 21 of charging station 20, for example, via magnetic resonance. The magnetic energy received by EV 10 is converted into an induced current, and the induced current is rectified into direct current to charge battery 12.

[0103] Charging station 20 receives power from commercial power grid 50 or the main power grid and can supply power to EV 10 via transmitter plate 21. Transmitter plate 21 contains transmitting coils. The transmitting coils in transmitter plate 21 generate magnetic flux and provide magnetic energy to EV 10 through magnetic resonance amplification. Charging station 20 can be located in various locations, such as the parking lot of an EV 10 owner's home, an EV charging parking space at a gas station, a shopping mall parking lot, or an office building parking lot.

[0104] Charging station 20 can communicate with the power infrastructure management system or the infrastructure server managing the power grid 50 via wired or wireless communication. Additionally, charging station 20 can also communicate wirelessly with EV 10. This wireless communication can include a wireless local area network (WLAN) based on WiFi conforming to the IEEE 802.11 standard, and can also include point-to-point (P2PS) communication using low-frequency (LF) magnetic field signals and / or low-power excitation (LPE) signals. Furthermore, the wireless communication between charging station 20 and EV 10 can include one or more communication methods, such as Bluetooth, Zigbee, and cellular networks.

[0105] On the other hand, according to the electric vehicle charging communication standard document ISO 15118, EVs and EV charging stations exchange messages to control the entire charging process. That is to say, communication for electric vehicle charging can be carried out via a wireless local area network (LAN) between the Electric Vehicle Communication Controller (EVCC) and the Power Supply Equipment Communication Controller (SECC).

[0106] During communication, EV 10 first verifies the identity of charging station 20 to determine if it is a trusted facility and establishes a secure channel with it to protect communication from unauthorized access. This can be achieved through traditional Transport Layer Security (TLS). After establishing an IP-based communication connection, a TLS session can be established through a TLS handshake procedure.

[0107] Figure 3 This is a schematic block diagram illustrating the communication relationship between an electric vehicle communication controller (EVCC), a power supply equipment communication controller (SECC), and an auxiliary participant (SA) to which the communication method according to this disclosure can be applied.

[0108] like Figure 3 As shown, the EVCC 100 installed on the electric vehicle (EV) 10 can communicate with the SECC 200 located within the charging station 10. The SECC 200 can define and use messages according to a protocol or scheme defined for communication between the SECC 200 and the SA 300. The SA 300 may include an eMSP (mobility service provider) that provides mobile charging services.

[0109] An eMSP is a company, institution, server, or entity that performs the relevant functions and enters into all service contracts with the customer related to the delivery of energy to the EV10. Typically, an eMSP may include other participants, such as electricity suppliers or physical power providers, and may maintain close relationships with distribution system operators and meter operators. OEMs or utilities can also act as eMSPs. An eMSP can verify the EMAID from the customer, which may originate from EMOCH (Electric Mobility Operator Clearing House), other eMSPs, or entity suppliers associated with the customer. For this purpose, the eMSP can issue EMAIDs to customers (e.g., EV owners).

[0110] When the SECC 200 does not support TLS session resumption, the EVCC 100 can establish a separate TLS session for each Value-Added Service (VAS) provided or supported by the SECC. Each VAS can be provided through a dedicated port on the SECC. The firewall running on the SECC 200 can be configured to allow access to the dedicated VAS port.

[0111] Additional communication channels can be opened for VAS using either a full TLS handshake or a restored TLS session. Restoration can be handled based on the TLS context (i.e., the tickets exchanged during the V2G session). TLS session restoration can be performed using pre-configured mechanisms.

[0112] On the other hand, when SECC 200 allows VAS to resume TLS, SECC 200 can be configured to issue TLS session tickets for each VAS provided to EVCC 100. In this case, SECC 200 can provide TCP-level forwarding. Such forwarding can be mapped to a fixed external URI of the local VAS, proxy server, or localhost. For end-to-end secure communication via a proxy server, the proxy server can provide the regular HTTP CONNECT method. When UDP-based VAS is required, the session resumption method can be combined with OpenVPN. For end-to-end secure communication via a fixed external URI, EVCC 100 and the target VAS server can negotiate a separate secure connection, such as a separate TLS session.

[0113] When a certificate chain provided by SECC 200 cannot be traced back to the root certificate in the trusted certificate list, EVCC 100 will only accept the certificate if the certificate chain is successfully verified using an out-of-band verification mechanism. The out-of-band verification mechanism may include a server-based Certificate Verification Protocol (SCVP). EVCC 100 may consider a certificate chain unverified if verification is not performed using the appropriate service, or if the verification result is negative or fails (e.g., due to a missing connection).

[0114] exist Figure 3 In this context, EV 10 refers to a typical vehicle owned by an EV owner, which can be charged at charging station 10 via wired or wireless means. An OEM configuration certificate is installed in the EV 10 during a unique manufacturing process. A contract certificate can be installed in the EV 10 after the completion of the vehicle purchase contract and a contract with a mobility operator (MO). Additionally, a V2G root certificate can be installed in the EV 10.

[0115] Furthermore, the Original Equipment Manufacturer (OEM) server (hereinafter referred to as "OEM") is the root certificate authority (CA) that issues the OEM root certificate and can operate its subordinate certification authorities (OEM SubCA). When manufacturing the EV 10, the OEM can use the OEM intermediate chain certificate (OEM SubCA certificate) to generate an OEM configuration certificate and install the OEM configuration certificate in the EV 10.

[0116] A Mobility Operator (MO) is a service provider that establishes contractual relationships with EV owners regarding charging, authorization, and payment so that the EV 10 can be charged at charging stations. For the EV 10 to receive charging services at the current charging station 20, the current charging station 20 must belong to an MO or support roaming scenarios. The MO can be operated by an energy supplier or wholesaler that sells energy. The MO can also act as a root certificate authority (CA) issuing MO root certificates. An MO certificate chain, consisting of the MO root certificate and intermediate chain certificates generated by lower-level CAs, can be used to generate contract certificates. Additionally, the MO certificate chain can be used to verify contract certificates installed in the EV 10 in both non-roaming and roaming environments. An MO can also be referred to as an Electric Mobility Service Provider (EMSP).

[0117] The Certificate Configuration Service (CPS) provides configuration services to clients such as the EV 10 by providing a chain of contract certificates and encryption keys for certificate transmission and reception when a contract certificate is installed or updated in an EV. The CPS can be equipped with a Leaf Prov cert. and a Prov SubCA. When a contract certificate is installed or updated in an EV 10, the CPS provides the configuration service by providing the public key of each MO, the Diffie-Hellman (DH) public key, and the Mobility Authentication Identifier (eMAID or EMAID) along with the contract certificate chain, enabling the EV 10 to verify the contract certificate chain and confirm the integrity and trustworthiness of the contract certificate.

[0118] During the installation or renewal of contract certificates in EV 10s, the Contract Certificate Pool (CCP) temporarily stores the response messages for the installation or renewal. Given the extremely short and strict time constraints imposed by the ISO 15118 standard on installation and renewal, the response messages can be pre-stored in the CCP and retained until the installation or renewal is fully completed. Since multiple EV 10s may require contract certificate installation or renewal, the response messages can be maintained in a directory format after assigning reference numbers.

[0119] The V2G server can act as the root certificate authority (CA) for the public key infrastructure (PKI) in the EV charging infrastructure. Therefore, the V2G server acts as the root trust anchor, and all auxiliary participants 300 regard the V2G root CA as a trusted organization.

[0120] Charging station 20 actually charges EV 10. Charging station 20 may include at least one wired charger and / or wireless charging point. Charging station 20 may be installed in one or more locations within a commercial dedicated charging facility. Additionally, charging station 20 may be located in various locations, such as parking lots attached to EV owner residences, EV charging parking spaces at gas stations, shopping mall parking lots, or workplace parking lots. Charging station 20 may include or be referred to as a "charging point," "EV charging station," "electric charging point," "charging point," "electronic charging station (ECS)," or "EV power supply equipment (EVSE)."

[0121] Charging service providers (CSPs) manage and verify EV owners' credentials and provide billing and other value-added services to customers. A CSP can be considered a specific type of MO (Mobile Operator) or can be implemented integrated with an MO. Multiple CSPs may exist, each associated with one or more charging station operators. One or more CSPs and charging station operators can form a charging network. EV 10s can obtain plug-and-charge (PnC) based charging services from the CSO (Consumer Station Operator) associated with the CSP associated with the MO, according to a contract, but roaming is required when charging is needed at another CSO. Each CSP can exchange roaming information with other CSPs or CSOs in different networks, and can also exchange information with clearinghouses.

[0122] The Clearing House (CH) handles cooperation between at least one Motor Operator (MO) and at least one Consumer Service Provider (CSP). In other words, the CH acts as an intermediary, facilitating the approval, billing, and settlement processes for EV charging service roaming between the two clearing parties. When an EV owner plans to charge their EV at a charging station not part of a contracted MO network, the CH can support roaming by connecting to the CSO or CSP. Where roaming is required, the CH allows the CSO or CSP to enter into a contract with the MO and transmits approval and charging data records (CDRs) to the MO. The CH may be referred to as the "Contract Clearing House (CCH)," "Mobility Clearing House (MCH)," "Roaming Platform," or "Electric Mobility Clearing House (E-MOCH)."

[0123] The terms “Charging Service Operator (CSO),” “Certificate Configuration Service (CPS),” “Mobility Operator (MO),” “Contract Clearing House (CCH),” and “V2G” may appear to refer to individuals or human organizations, but in this specification, including the claims, these expressions refer to entities implemented in hardware, software, and / or a combination thereof, and are given concise and functional names to enhance readability. In exemplary embodiments, these components may be server devices implemented in a combination of hardware and software, allowing other devices to access them via networks such as the Internet. Because these components are functionally distinguishable, two or more components may be housed and executed in a single physical device or integrated into a single program. Specifically, a single entity may act as both a CSO and a CSP, while another single entity may act as both a CPS and a CCP. One or more of the aforementioned components may be reorganized to have different appearances and names.

[0124] On the other hand, EV charging services and related infrastructure constitute a convergent field, involving multiple industries such as automotive, power grid, energy, transportation, communications, finance, and electronics. Therefore, standardization efforts have been undertaken from multiple perspectives, including standardization work by several international standardization organizations and national-level standardization efforts. Consequently, many similar conceptual terms exist. Specifically, charging station operators (CSOs) and charging point operators (CPOs) are similar in role and function, although there may be minor differences in function or nuances; they may essentially refer to the same entity. Furthermore, charging service providers (CSPs) and mobility operators (MOs) share at least partial similarities in role and function, and these terms may be used interchangeably or even confused. These realities should be taken into account in the interpretation of this specification, including the claims.

[0125] In EV charging services and related infrastructure, Public Key Infrastructure (PKI) can be used as the foundation for implementing PnC. PKI provides a framework for the authentication of individuals and devices, the activation of secure communications, and the assurance of controlled access to resources.

[0126] Figure 4 This is a flowchart illustrating a detailed process of a Value-Added Service (VAS) communication method based on a list of supported providers according to an exemplary embodiment of this disclosure. Figure 5 It shows that it is applicable to Figure 4 Example diagram of the configuration of the list of providers of communication methods. Figure 6 This is shown for illustration Figure 5 A diagram illustrating the configuration of the mobile authentication identifier for each provider identifier within the provider list.

[0127] like Figure 4As shown, when EVCC 100 and SECC 200 are in a TCP / TLS connection state (S410), EVCC 100 can request a service list from SECC 200 via a service discovery request message (S420). In other words, SECC 200 can receive a request message from EVCC 100 for a service list of electric vehicle charging services.

[0128] Next, SECC 200 can reply to or provide EVCC 100 with a list of Value-Added Services (VAS) containing service identifier information (e.g., a service identifier (ServiceID) with a value of 100) via a ServiceDiscoveryRes message (S430). In this specification, such a service identifier with a specific value like 100 can be referred to as the first service identifier. That is, EVCC 100 can receive a list of VAS services containing the first service identifier from SECC 200.

[0129] Here, the service discovery response message may include service names representing a list of supported providers, service categories representing information originating from Electric Vehicle Power Supply Equipment (EVSE) as service elements, and information about a first service identifier. The service discovery response message may also include service elements indicating free service, such as true or false.

[0130] Next, EVCC 100 can request the parameters of the first service identifier from SECC 200 via a ServiceDetailReq message (S440). In other words, SECC 200 can receive a request message for the parameters of the first service identifier from EVCC 100.

[0131] Next, SECC 200 can reply to or provide multiple service parameter sets corresponding to multiple support providers to EVCC 100 via ServiceDetailRes messages (S450). In other words, EVCC 100 can receive service parameter sets corresponding to multiple support providers from SECC 200.

[0132] The service parameter set can include a service parameter list (SPL). For example... Figure 5 As shown, the service parameter list can be a list of providers, which can be in the form of strings or string values, where the parameter names are consecutively arranged as provider identifiers 510 and 520 indicating the charging service provider. Here, each provider identifier 510 and 520 constituting the string form can be separated by a comma 530.

[0133] Specifically, each provider identifier can consist of a country code and a provider identifier, which are the first five characters of the Mobility Authentication Identifier (EMAID), arranged sequentially from the beginning. For example... Figure 6 As shown, EMAID consists of the following structure connected without spaces: country code 610 represented by two characters, provider identifier 620 represented by three characters, eMA instance represented by a predetermined number of characters, numbers or digits, and check digit represented by a predetermined number of characters, numbers or digits.

[0134] Refer again Figure 4 EVCC 100 can send a payment service selection request message to SECC 200 (S460). Then, EVCC 100 can receive a payment service selection response message from SECC 200 (S470).

[0135] Next, EVCC 100 can send a payment details request message to SECC 200 (S480). Then, EVCC 100 can receive a payment details response message from SECC 200 (S490).

[0136] Here, EVCC 100 can send a contract certificate chain containing the Mobility Account Identifier (EMAID) supported by the SECC 200's provider list via a payment details request message. This contract certificate chain may include a ContractSignatureCertChain. This ContractSignatureCertChain includes the contract certificate and may optionally include subordinate certificates.

[0137] These PnC message elements are provided only when parameters or routine operations need to be changed. The provided message elements can be processed to override existing or other information.

[0138] Therefore, when the SECC 200 supports the SPL feature, a dedicated VAS can be provided in the Service Discovery Res message. Additionally, when the EV 10 plans to use the SPL feature, it can send a Service Detail Req message containing the service identifier assigned to the aforementioned dedicated VAS. The SECC 200 can then reply to the EV 10 with parameters indicating the list of supported providers via a Service Detail Res message. The number of supported providers included in the SPL can be unlimited.

[0139] EV 10 can check if a support provider's contract certificate exists. If a support provider's contract certificate exists, EV 10 can use that certificate to authorize the corresponding support provider. Alternatively, if no support contract certificate exists, EV 10 can leave charging station 20 or repeatedly attempt to access the PnC charging service.

[0140] Based on the above configuration, when selecting PnC charging service for a conventional charger, the EV 10 can select the appropriate contract certificate issued by the mobility service provider without having to choose a specific VAS.

[0141] Additionally, based on the above configuration, this disclosure can facilitate the introduction of a dedicated value-added service (VAS) that provides a list of support providers for charging services to electric vehicles. This list of support providers for such a dedicated VAS can be transmitted using service parameter elements of a ServiceDetailRes message. In this case, additional VAS communication may not be possible.

[0142] Table 1 below shows an example of the service definition for the above-mentioned dedicated VAS.

[0143] Table 1

[0144]

[0145] As shown in Table 1, the SECC can provide an electric vehicle with a list of authorized support providers for PnC-based electric vehicle charging services using conventional chargers via a single message. This message contains a service element where the service identifier is set to 100 and the service name is set to "Provider List". In this exemplary embodiment, the case of selecting 100 as the service identifier is illustrated. However, this disclosure is not limited to this configuration, and the service identifier can be configured to use values ​​other than 100, including values ​​less than or greater than 100, as long as the value does not overlap with other service identifiers.

[0146] Additionally, Table 2 below shows an example of the service parameter definitions for the aforementioned dedicated VAS. That is, for service identifier 100 described in Table 1, the following set of parameters can be added.

[0147] Table 2

[0148] ParameterSetID ParameterName="Providers" describe 1 stringValue=<list of providers> Service Provider List 2 stringValue=<list of providers> Service Provider List … … …

[0149] As shown in Table 2, multiple parameter sets can be distinguished by parameter set identifiers (parameterSetID), such as 1, 2, etc. The parameter name for each parameter set can be called "Provider" or "Supported Provider," and the provider list can be set as a string value consisting of the provider identifiers of the supported providers. For example, the provider list can have the same identifiers as mentioned above. Figure 5 and Figure 6 The same configuration as described above. That is, the provider list can be configured as "KRHMC, FREDF, DESHL, USCHP, NLABB," etc. In one example, "KR" in "KRHMC" could represent the country code for South Korea, and "HMC" could represent the provider identifier for Hyundai Motor Company. Here, the country code and provider identifier can be the same as those included in the Mobility Account Identifier (EMAID). The provider list can contain 255 or more provider identifiers, with adjacent provider identifiers separated by commas.

[0150] Regarding the aforementioned list of providers, SECC may perform a process (e.g., a parameter set generation process) to indicate all supported providers in a single list (i.e., a single parameter set), or it may perform the process to indicate all providers by dividing them into multiple lists (i.e., multiple parameter sets) based on selected criteria.

[0151] Figure 7 This is a flowchart illustrating a communication method according to other exemplary embodiments of the present disclosure.

[0152] like Figure 7 As shown, the SECC can receive a request message for a service list for charging services from the EV (S710). This request message can be a service discovery request message used in the EV charging service process.

[0153] Next, the SECC can provide the EV with a list of services containing service identifiers for dedicated VASs used to provide SPL for the EMSP (S720). In other words, the SECC can provide the EVCC with a list of value-added services (VAS) containing service identifiers (referred to as "first service identifiers") that include a list of support providers for dedicated VASs through a service discovery response message.

[0154] Next, the SECC can receive a message from the EV requesting parameters for the dedicated VAS, namely the parameters for the first service identifier (S730). The message requesting the parameters can be a service details request message used in the EV charging service process.

[0155] Next, SECC can generate at least one set of service parameters indicating all support providers in the Support Provider List (SPL) (S740).

[0156] Next, the SECC can provide the EV with a service parameter set (S750) that supports the dedicated VAS in the SPL. This service parameter set can be referred to as the service parameter set. The SECC can send at least one service parameter set to the EVCC via a service details response message.

[0157] Next, the SECC can receive the contract certificate chain (S760) containing the SPL-supported Mobility Account Identifier (EMAID) from the EV. The SECC can receive the contract certificate chain from the EVCC via a PaymentDetailsReq message.

[0158] As described above, when the EVCC receives a ServiceDetailRes message from the SECC containing the first service identifier (e.g., "ServiceID=100"), the EVCC can determine the contract certificate supported by the SECC. If the SECC supports the contract certificate, the above process (S710 to S760) can continue. On the other hand, if the SECC does not support the contract certificate, the EVCC can terminate the PnC charging service establishment operation.

[0159] Therefore, EVs can check the list of AuthorizationSetupRes messages from Mobility Service Providers (EMSPs). EVs can also check PnC compatibility with the charger and appropriately select a contract certificate issued by the preferred EMSP.

[0160] Based on the above configuration, a list of support providers (SPL) for value-added services (VAS) can be provided while maintaining interoperability with conventional chargers or devices that do not support SPL functionality. In other words, this disclosure can support functions related to the aforementioned list of support providers without compromising interoperability with existing conventional chargers.

[0161] Furthermore, based on the above configuration, a new solution can be provided to deliver the list of supported providers as a value-added service to EVs. In other words, value-added services based on the list of supported providers can be effectively implemented by utilizing the service parameter elements of the ServiceDetailRes message used in existing EV charging service processes.

[0162] Furthermore, according to this disclosure, value-added services based on the list of supported providers do not require subsequent additional value-added service communication. In this case, electric vehicles do not need to select value-added services during the service selection process, thereby maintaining a user-centric service and providing convenience for users.

[0163] Figure 8It is shown that it is used to implement applicable Figure 7 Example diagram of detailed items in the service list within the message of the communication method's value-added services.

[0164] like Figure 8 As shown, the Service Discovery Response (ServiceDiscoveryRes) message can contain the service parameter element 810 of the dedicated VAS in the service list.

[0165] Service parameter element 810 may contain elements of service identifier, service name, service category, and free service.

[0166] The Service Identifier (ServiceID) element can be set to a predefined value, such as 100. The Service Name (ServiceName) element can be set to "SupportedProvidersList". The Service Category (ServiceCategory) element can be set to "EVSEInformation", representing information about electric vehicle power supply equipment. The FreeService (FreeService) element can be set to "true" or "false" to indicate whether the service is free.

[0167] According to this exemplary embodiment, the SECC can provide a list of support providers to electric vehicles through the ServiceName field in the service discovery response message for a specific service identifier (e.g., 100 or a first service identifier).

[0168] Figure 9 It is shown Figure 7 An example diagram illustrating the interoperability effects of the communication methods.

[0169] like Figure 9 As shown, the ServiceDetailRes message may contain a service parameter list 910 for a dedicated VAS corresponding to the first provider identifier. SECC can use the service parameter list 910 to provide electric vehicles with various manufacturers / providers or their service parameter sets (referred to as "parameter sets") by service type. For example, the service parameter list 910 may include a first parameter set 912, a second parameter set 914, and a third parameter set 916.

[0170] In the first parameter set 912, the parameter set identifier (ParameterSetID) element can be set to 1, and the parameter name indicating "Providers" can be set to the string value "KRHMC,FREDF,DESHL,...".

[0171] In the second parameter set 914, the parameter set identifier (ParameterSetID) element can be set to 2, and the parameter name indicating "Providers" can be set to the string value "USCHP,NLABB,...".

[0172] In the third parameter set 916, the parameter set identifier (ParameterSetID) element can be set to 3, and the parameter name indicating "Providers" can be set to a string value consisting of its compressed provider identifiers, each identifier consisting of five characters separated by commas.

[0173] According to this exemplary embodiment, the SECC can be configured to select a parameter set generation procedure that maintains a relatively small number of providers within a single parameter set by utilizing multiple parameter sets, or to generate at least one parameter set. This configuration allows for maintaining interoperability with devices defined in the ISO 15118-2 standard without modifying the architecture or requirements.

[0174] On the other hand, in an exemplary embodiment of this disclosure, when both EVCC and SECC support value-added services from a list of supported providers, EVCC and SECC can exchange messages containing relevant items.

[0175] Figure 10 This is a schematic block diagram illustrating a general hardware configuration of an apparatus for providing a list of support providers (SPL) for value-added services (VAS) according to other exemplary embodiments of the present disclosure.

[0176] like Figure 10 As shown, device 1000 can be installed or coupled to an electric vehicle (EV) and can be at least a functional unit or component of an electric vehicle communication controller (EVCC). In another embodiment, device 1000 can be installed or coupled to an electric vehicle power supply device (EVSE) and can be at least a functional unit or component of a power supply device communication controller (SECC).

[0177] Device 1000 may include processor 1010, and according to embodiments, may also include memory 1020, transceiver 1030, storage device 1040, input interface device 1050, and output interface device 1060. At least some components of device 1000, including processor 1010, may be interconnected via a bus, thereby allowing signal and data exchange.

[0178] Processor 1010 can execute program instructions or software modules stored in memory 1020. Memory 1020 can store program instructions or software modules. Memory 1020 may include volatile memory such as RAM (Random Access Memory) and non-volatile memory such as ROM (Read Only Memory). Memory 1020 can load program instructions stored in storage device 1040 and provide them to processor 1010 so that processor 1010 can execute these instructions.

[0179] The processor 1010 can execute program instructions stored in the memory 1020 and / or storage device 1040. The processor 1010 may include at least one central processing unit (CPU), graphics processing unit (GPU), or other processor capable of executing the communication methods according to this disclosure.

[0180] Storage device 1040 may be a recording medium suitable for storing program instructions and data, and may include, for example, magnetic media such as hard disks, floppy disks and magnetic tapes, optical media such as CD-ROMs (Read-Only Optical Discs) and DVDs (Digital Video Optical Discs), magneto-optical media such as optical disks, and semiconductor memories such as flash memory, EPROMs (Erasable Programmable ROMs) or SSDs based thereon.

[0181] The operation of the method according to exemplary embodiments of this disclosure can be implemented as a computer-readable program or code stored in a computer-readable recording medium. The computer-readable recording medium includes all types of recording devices that store information readable by a computer system. The computer-readable recording medium may also include computer-readable programs or code stored and executed in a distributed manner among computer systems connected via a network. The distributed manner may include a secure distributed architecture using blockchain.

[0182] Computer-readable recording media may also include hardware devices specifically configured for storing and executing program instructions, such as ROM, RAM, and flash memory. Program instructions may include machine code created by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or similar means. More broadly, program instructions may also include artificial intelligence or artificial neural networks.

[0183] Some aspects of this disclosure are described in the context of an apparatus, but may also represent a corresponding method description, wherein blocks or components correspond to method steps or features of method steps. Similarly, aspects described in the context of a method may also represent corresponding blocks, items, or features of an apparatus. Some or all of the method steps may be performed by (or using) hardware devices (e.g., microprocessors, programmable computers, or electronic circuits). In some exemplary embodiments, at least one of the most critical method steps may be performed by such devices.

[0184] In exemplary embodiments, programmable logic devices (such as field-programmable gate arrays (FPGAs)) may be used to perform some or all of the functions of the methods described herein. In exemplary embodiments, the FPGA may operate in conjunction with a microprocessor to perform one of the methods described herein. Typically, these methods are preferably performed by hardware devices.

[0185] Although this disclosure has been described with reference to preferred embodiments, those skilled in the art will understand that various modifications and changes may be made without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A communication method for value-added services (VAS) in vehicle-to-grid (V2G) communication, executed by a power supply equipment communication controller (SECC), the communication method comprising: Receive a request message from an electric vehicle (EV) for a list of services related to charging. A service list is provided to the EV, the service list including a first service identifier of a dedicated VAS, the dedicated VAS being used to provide a list of support providers for the Electric Mobility Service Provider (EMSP); Receive a request message for parameters of the dedicated VAS from the EV; as well as Provide the EV with at least one set of service parameters for a list of support providers that support the dedicated VAS.

2. The communication method according to claim 1, wherein, Providing the EV with the service list including the first service identifier includes: Send a service discovery response message to the EV, and The service discovery response message contains service elements, which include the first service identifier, a service name representing the list of supported providers, and a service category representing information about the Electric Vehicle Power Supply Equipment (EVSE).

3. The communication method according to claim 2, wherein, The request message received from the EV for the parameters of the dedicated VAS includes: Receive a service details request message from the EV, and The service discovery response message further includes a service element indicating whether the service is free.

4. The communication method according to claim 1, wherein, Providing the at least one set of service parameters to the EV includes: In response to the service details request message, a service details response message is sent to the EV, and The at least one set of service parameters includes a string value whose parameter name is set to the provider identifier of the provider, the provider identifier being separated by commas.

5. The communication method according to claim 4, wherein, Each of the provider identifiers includes the country code and provider ID derived from the Mobility Authentication Identifier EMAID.

6. The communication method according to claim 1, wherein, The list of supported providers includes a list of providers that support plug-and-charge / park-and-charge PnC licenses.

7. The communication method according to claim 1, further comprising: Generate a single set of service parameters that lists all providers in the supported provider list; or Generate multiple service parameter sets based on predefined standard classifications and listing all providers in the supported provider list.

8. The communication method according to claim 1, further comprising: A contract certificate chain is received from the EV via a payment details request message. The contract certificate chain has a mobility authentication identifier EMAID supported by the list of supported providers.

9. An apparatus for value-added services (VAS) in vehicle-to-grid (V2G) networks, the apparatus comprising: processor; as well as At least one instruction loaded into the processor, Wherein, through the at least one instruction, the processor: Receive a request message from an electric vehicle (EV) for a list of services related to charging. A service list is provided to the EV, the service list including a first service identifier of a dedicated VAS, the dedicated VAS being used to provide a list of support providers for the Electric Mobility Service Provider (EMSP); Receive a request message from the EV for parameters of the dedicated VAS; and Provide the EV with at least one set of service parameters for a list of support providers that support the dedicated VAS.

10. The apparatus according to claim 9, wherein, Providing the EV with the service list including the first service identifier includes: Send a service discovery response message to the EV, and The service discovery response message contains service elements, which include the first service identifier, a service name representing the list of supported providers, and a service category representing information about the Electric Vehicle Power Supply Equipment (EVSE).

11. The apparatus according to claim 10, wherein, The request message received from the EV for the parameters of the dedicated VAS includes: Receive a service details request message from the EV, and The service discovery response message further includes a service element indicating whether the service is free.

12. The apparatus according to claim 9, wherein, Providing the at least one set of service parameters to the EV includes: In response to the service details request message, a service details response message is sent to the EV, and The at least one set of service parameters includes a string value whose parameter name is set to the provider identifier of the provider, the provider identifier being separated by commas.

13. The apparatus according to claim 12, wherein, Each provider identifier includes the country code and provider ID derived from the first five characters of the Mobility Authentication Identifier EMAID, and The list of supported providers includes a list of providers that support plug-and-charge / park-and-charge PnC licenses.

14. The apparatus according to claim 9, wherein, The processor further: Generate a single set of service parameters listing all providers in the supported provider list; or Generate multiple service parameter sets based on predefined standard classifications and listing all providers in the supported provider list.

15. The apparatus according to claim 9, wherein, The processor further: A contract certificate chain is received from the EV via a payment details request message. The contract certificate chain has a mobility authentication identifier EMAID supported by the list of supported providers.

16. A communication method for value-added services (VAS) in vehicle-to-grid (V2G) communication, executed by an electric vehicle communication controller (EVCC), the communication method comprising: Request a list of services for EV charging services from the power supply equipment communication controller (SECC); Receive a service list from the SECC, the service list including a first service identifier of a dedicated VAS used to provide a list of support providers for the Electric Mobility Service Provider (EMSP); Request the parameters of the dedicated VAS from the SECC; as well as Receive at least one set of service parameters from the SECC for the list of support providers that support the dedicated VAS.

17. The communication method according to claim 16, wherein, Receiving the service list including the first service identifier includes: Receive service discovery response message from the SECC, and The service discovery response message contains service elements, which include the first service identifier, a service name representing the list of supported providers, and a service category representing information about the Electric Vehicle Power Supply Equipment (EVSE).

18. The communication method according to claim 17, wherein, The parameters requested for the dedicated VAS include: Send a service details request message to the SECC. The receipt of the at least one set of service parameters includes receiving a service details response message from the SECC in response to the service details request message, and The service discovery response message further includes a service element indicating whether the service is free.

19. The communication method according to claim 16, wherein, At least one of the at least one service parameter set includes a string value whose parameter name is set to a provider identifier, the provider identifier being separated by commas. Each of the provider identifiers includes the country code and provider ID derived from the first five characters of the mobile travel authentication identifier EMAID.

20. The communication method according to claim 16, further comprising: A contract certificate chain with a mobile travel authentication identifier EMAID supported by the list of supported providers is sent to the SECC via a payment details request message.

Images