Two-way hydrogen filling communication process and device using the same

Abstract

A two-way hydrogen filling communication process and an apparatus using the same are provided, which overcome the limitations and weaknesses of one-way communication to improve the safety, efficiency, and reliability of hydrogen filling. [Solution] The hydrogen filling communication two-way process of the present invention includes the steps of transmitting a request message to a dispenser including a protocol list for communication protocols to be used in a hydrogen filling session, and receiving a response message from the dispenser including information on a common protocol selected by the dispenser and best suited to the vehicle, which is commonly supported by both the vehicle and the dispenser, and the vehicle and dispenser reach an agreement on the communication protocol to be used for hydrogen filling communication using the common protocol.

Description

[Technical Field]

[0001] The present invention relates to communication technology for hydrogen fueling of hydrogen fueled mobility, and more particularly to a bidirectional hydrogen fueling communication process and an apparatus using the same that overcomes the limitations and weaknesses of existing one-way communication to improve the safety, efficiency, and reliability of hydrogen fueling. [Background technology]

[0002] A hydrogen vehicle or hydrogen electric vehicle is a pollution-free vehicle that runs on electrical energy generated when high-pressure hydrogen stored in the vehicle mixes with atmospheric air. Most hydrogen electric vehicles use hydrogen as their energy source and generate electricity using a fuel cell system. Hydrogen electric vehicles emit only pure water (H2O) during the electricity generation process and have the function of removing ultrafine dust particles from the atmosphere while in operation, making them garnering attention as an environmentally friendly form of mobility for the future. Given that hydrogen, the fuel, is limitless on Earth and the energy production process is environmentally friendly, hydrogen electric vehicles are attracting attention as a technology with potential for use across industries.

[0003] Hydrogen-fueled mobility refers to mobility that uses hydrogen as an energy source or hydrogen as fuel to generate electrical energy and use it to drive an electric motor. Hydrogen-fueled mobility includes not only the hydrogen electric vehicle mentioned above, but also aerial mobility, industrial trucks, trains, ships, and aircraft, and includes devices that generate electrical energy using hydrogen as fuel and use it to drive.

[0004] Most hydrogen electric vehicles generate electrical energy by transferring high-pressure hydrogen stored safely in a hydrogen fuel storage tank and oxygen supplied through an air supply system to a fuel cell stack, where an electrochemical reaction occurs between the hydrogen and oxygen. The generated electrical energy is converted into kinetic energy by the drive motor to power the hydrogen electric vehicle, and the hydrogen electric vehicle has the advantage of discharging only pure water through the exhaust while in motion.

[0005] On the other hand, the concept of a hydrogen fueled car, which is not a hydrogen electric car, is also a vehicle that uses hydrogen as fuel, but a hydrogen fueled car uses the heat generated by directly burning hydrogen in the engine to drive the electric motor. The method of refueling hydrogen for a hydrogen fueled car is not much different from the method of refueling hydrogen for a hydrogen electric car.

[0006] The ultimate goal of the control technique for supplying hydrogen to vehicles that use hydrogen as fuel is to control the temperature and pressure of the compressed hydrogen storage system (CHSS) on the fuel cell side so that it operates within the limit temperature and limit pressure conditions for safe hydrogen filling.

[0007] The hydrogen refueling process, control techniques, and protocols for conventional hydrogen electric vehicles were established at a time when wired / wireless communication technologies and control computing techniques were not yet mature, and therefore do not accurately reflect the recent advances in information and communications technology (ICT).As a result, conventional hydrogen refueling technologies for hydrogen electric vehicles are inefficient, slow, and not suitable for large-volume hydrogen refueling.

[0008] In particular, in the case of wireless hydrogen filling communication, many hydrogen filling control devices use one-way infrared communication devices, and therefore wireless-based hydrogen filling communication still has the limitations and weaknesses of one-way communication. Summary of the Invention [Problem to be solved by the invention]

[0009] The present invention has been made in view of the above-mentioned problems in the prior art, and an object of the present invention is to provide a hydrogen filling communication two-way process and an apparatus that utilizes the same. [Means for solving the problem]

[0010] In order to achieve the above object, one aspect of the present invention provides a two-way hydrogen filling communication process, which is performed by an electronic control unit of a vehicle, and includes the steps of transmitting a request message to a dispenser, the request message including a protocol list for communication protocols to be used in a hydrogen fueling session, and receiving a response message from the dispenser, the response message including information on a common protocol selected by the dispenser and best suited for the vehicle, which is supported by both the vehicle and the dispenser, and through which the vehicle and the dispenser reach an agreement on the communication protocol to be used in the hydrogen fueling communication.

[0011] The protocol list may be a prioritized list of communication protocols supported by the vehicle. The types of devices that support the common protocol may correspond to the types of devices that the dispenser falls back to for backward compatibility. The hydrogen filling communication two-way process (hereinafter simply referred to as the "two-way process") may further include negotiating with the dispenser a fueling protocol to be used for fueling the vehicle with hydrogen. The two-way process may further include exchanging detailed parameters with the dispenser necessary to implement the fueling protocol. The two-way process may further include a discovery and pairing step that identifies incompatibilities with the communication module of the dispenser responsible for controlling a receptacle physically connected to the nozzle of the dispenser, searches for the dispenser through a search mechanism provided in the data link and physical layers, and begins communication with the dispenser. The two-way process may further include establishing a TCP connection with the dispenser after connecting the data link and physical layer, performing a TLS handshake with the dispenser to authenticate, and exchanging keys with the dispenser to establish a secure communication channel. The two-way process may further include a step of checking safety conditions to ensure that the hydrogen filling is safe after exchanging the detailed parameters or filling parameters to consider compatibility with the dispenser. The two-way process may further include a monitoring and control step for exchanging measurement data with the dispenser to confirm the filling status and control the filling procedure when the hydrogen filling is performed according to a preselected filling protocol using the detailed parameters. The two-way process may further include verifying that necessary safety conditions have been met before separating the dispenser nozzle from the vehicle receptacle. The two-way process may further include exchanging with the dispenser information on the results of the hydrogen filling of the vehicle and at least a portion of the accounting information regarding the hydrogen filling session. The two-way process may further include a step of handling errors that occur during the process of determining the communication protocol, the process of proceeding with hydrogen filling of the vehicle, or the process before completing and terminating the hydrogen filling. The two-way process may further include a step of emergency handling of safety-critical problems that occur during the process of determining the communication protocol, the process of proceeding with hydrogen filling of the vehicle, or the process before completing and terminating the hydrogen filling.

[0012] According to another aspect of the present invention, a bidirectional hydrogen filling communication process is a bidirectional hydrogen filling communication process performed by an electronic control unit of a vehicle, the process including a discovery and pairing step of identifying incompatibility with a communication module of a dispenser that controls a receptacle physically connected to a nozzle of the dispenser that supplies hydrogen fuel to the vehicle, searching for the dispenser using a search mechanism provided in a data link and physical layer, and starting communication with the dispenser; a step of establishing a TCP connection with the dispenser after connecting the data link and physical layer, authenticating the dispenser by performing a TLS handshake with the dispenser, and exchanging keys with the dispenser to establish a secure communication channel; a step of transmitting a request message to the dispenser that includes a protocol list for communication protocols to be used in a fueling session for hydrogen filling of the vehicle; a step of receiving from the dispenser a response message that includes information on a common protocol that is selected by the dispenser and is best suited for the vehicle and commonly supported by both the vehicle and the dispenser; and a step of identifying a fueling protocol used in the communication protocol. Negotiating a protocol with the dispenser and detailed parameters necessary to implement the filling protocol.a monitoring and control step of exchanging measurement data with the dispenser to check the filling status and control the filling procedure when the hydrogen filling is performed according to a preselected filling protocol using the detailed parameters; a step of confirming that necessary safety conditions are met before separating the nozzle of the dispenser from the receptacle of the vehicle; exchanging information on the hydrogen filling result of the vehicle and at least a part of ledger information on the hydrogen filling session with the dispenser; a step of determining the communication protocol, a step of proceeding with hydrogen filling of the vehicle, or a step of completing and terminating the hydrogen filling; and a step of immediately handling a safety-critical problem occurring during the step of determining the communication protocol, a step of proceeding with hydrogen filling of the vehicle, or a step of completing and terminating the hydrogen filling. Reach agreement on the communication protocol to use.

[0013] In order to achieve the above object, one aspect of the present invention provides a hydrogen fueling device for hydrogen-fueled mobility, comprising: a memory for storing at least one instruction; and a processor for executing the at least one instruction. The processor is configured to transmit a request message to a dispenser, the request message including a protocol list for communication protocols to be used in a hydrogen fueling session, according to the at least one instruction; receive from the dispenser a response message including information on a common protocol selected by the dispenser and best suited for the vehicle to be supplied with hydrogen fuel by the dispenser, which is commonly supported by both the vehicle and the dispenser; and reach an agreement with the dispenser on the communication protocol to be used in hydrogen fueling communication using the common protocol.

[0014] The protocol list may be a prioritized list of communication protocols supported by the vehicle. The types of devices that support the common protocol may correspond to the types of devices that the dispenser falls back to for backward compatibility. The hydrogen filling device may further perform, by the processor, a step of negotiating with the dispenser a fueling protocol to be used for fueling the vehicle with hydrogen. The hydrogen filling device may further perform the step of exchanging detailed parameters required to execute the fueling protocol with the dispenser using the processor. The hydrogen filling device may further perform, by the processor, the process of determining the communication protocol, the process of proceeding with hydrogen filling of the vehicle, or the process of handling errors or emergency handling of safety-critical problems that occur during the process before completing and terminating the hydrogen filling. [Effects of the Invention]

[0015] The hydrogen filling bidirectional communication process and the device using the same, i.e., the hydrogen filling device, of the present invention overcomes the limitations and weaknesses of existing one-way communication in communication protocols for hydrogen fueling of hydrogen fueled mobility, including fuel cell electric vehicles (FCEVs), and can improve the safety, efficiency, and reliability of hydrogen filling.

[0016] Furthermore, the present invention provides a hydrogen filling method and communication protocol fallback rules and principles that allow vehicles, including fuel cell electric vehicles (FCEVs), and dispensers that supply hydrogen fuel to vehicles to select a hydrogen filling protocol based on the use case so as to maximize interoperability without having to select their own most preferred method.

[0017] The present invention also provides the necessary rules and procedures for vehicles and dispensers to effectively determine advanced communication media to effectively achieve hydrogen fueling goals. [Brief explanation of the drawings]

[0018] [Figure 1] 1 is a conceptual diagram of a hydrogen filling system for a fuel cell electric vehicle (FCEV) that applies a hydrogen filling communication two-way process according to an embodiment of the present invention. [Figure 2] FIG. 2 is a partially enlarged view illustrating the physical fastening structure between the FCEV and the dispenser in the hydrogen filling system of FIG. 1. [Figure 3] 2 is a graph for explaining changes in the state of hydrogen fuel that occur during the hydrogen filling process using the hydrogen filling system of FIG. 1. [Figure 4]1 is a framework for functional blocks that perform a series of hydrogen filling procedures employing a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 5] 1 is an exemplary diagram illustrating a communication stack related to each use case employed in a hydrogen filling communication two-way process according to an embodiment of the present invention, focusing on the seven layers of the OSI (Open Systems Interconnection reference model). FIG. [Figure 6] 1 is an exemplary diagram illustrating a pairing process of a discovery and pairing procedure employed in a two-way hydrogen filling communication process according to an embodiment of the present invention. [Figure 7] 1 is an exemplary diagram illustrating backward compatibility employed in a hydrogen filling communication two-way process according to an embodiment of the present invention. [Figure 8] 1 is an exemplary diagram illustrating backward compatibility employed in a hydrogen filling communication two-way process according to an embodiment of the present invention. [Figure 9] 1 is an exemplary diagram illustrating a classification of communication data used in a two-way communication process for hydrogen filling according to an embodiment of the present invention and backward compatibility in the classification of communication data. [Figure 10] 1 is a flowchart illustrating an authentication process of a communication security procedure employed in a two-way hydrogen filling communication process according to an embodiment of the present invention. [Figure 11] 4 is a flowchart illustrating a communication protocol negotiation procedure employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 12] 10 is a flowchart illustrating yet another communication protocol negotiation procedure in a hydrogen filling communication two-way process according to another embodiment of the present invention. [Figure 13]4 is a flow chart illustrating a fueling protocol negotiation procedure employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 14] 4 is a flow chart illustrating a fueling parameter negotiation procedure employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 15] 1 is a flowchart illustrating a safety check-in procedure employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 16] 4 is a flow chart illustrating a monitoring and control procedure employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 17] 1 is a flowchart illustrating a safety check-out procedure employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 18] 1 is a flowchart illustrating a termination procedure employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 19] 1 is a flow chart illustrating an error handling procedure employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 20] 4 is a flow chart illustrating an emergency handling procedure employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 21] FIG. 1 is a schematic block diagram of an apparatus (simply "hydrogen filling apparatus") utilizing a hydrogen filling communication two-way process in accordance with yet another embodiment of the present invention. [Figure 22] FIG. 22 is a block diagram for explaining a software module employed in the hydrogen filling device of FIG. 21. DETAILED DESCRIPTION OF THE INVENTION

[0019] The present invention can be modified in various ways and can have various embodiments, and specific embodiments will be illustrated in the drawings and described in detail in the detailed description. However, this is not intended to limit the present invention to the specific embodiments, and it should be understood that the present invention includes all modifications, equivalents, and alternatives within the spirit and technical scope of the present invention. In describing each drawing, like reference numerals are used to refer to like elements.

[0020] Terms such as first, second, A, and B are used to describe various components, but the components should not be limited by the terms. Terms are used only to distinguish one component from another. For example, a first component could be termed a second component, and similarly, the second component could be termed a first component, without departing from the scope of the present invention. The term "and / or" includes a combination of multiple associated listed items or any of multiple associated listed items.

[0021] In the embodiments of the present invention, "at least one of A and B" means "at least one of A or B" or "at least one of a combination of one or more of A and B." Also, in the embodiments of the present invention, "one or more of A and B" means "one or more of A or B" or "one or more of a combination of one or more of A and B."

[0022] When a component is referred to as being "coupled" or "connected" to another component, it should be understood that the component is directly coupled or connected to the other component, but that there may be other components in between. Conversely, when a component is referred to as being "directly coupled" or "directly connected" to another component, it should be understood that there are no other components in between.

[0023] The terms used in this specification are merely used to describe specific embodiments and are not intended to limit the present invention. The singular expressions include the plural expressions unless the context clearly dictates otherwise. In this specification, the terms "comprise" or "have" are intended to specify the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, and should be understood not to preclude the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0024] Unless otherwise defined, all terms used herein, including technical and scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which this invention belongs. Terms as defined in commonly used dictionaries should be interpreted to have a meaning consistent with the meaning they have in the context of the relevant art, and should not be interpreted in an idealized or overly formal sense unless expressly defined herein.

[0025] Some terms used in this specification are defined as follows:

[0026] Hydrogen electric vehicles generally include both fuel cell electric vehicles (FCEVs) that use fuel cells and internal combustion engine (ICE)-based vehicles that use hydrogen as fuel. The hydrogen electric vehicles described below are also simply referred to as FCEVs.

[0027] In the following embodiments, a hydrogen fuel cell vehicle is described as the main embodiment, but other embodiments of the present invention include an ICE-based hydrogen electric vehicle that uses hydrogen as fuel. In the following embodiments, a hydrogen fueling protocol and / or a communication protocol for hydrogen fueling is disclosed mainly for a hydrogen fuel cell vehicle, and according to other embodiments of the present invention, the hydrogen fueling protocol and / or the communication protocol for hydrogen fueling disclosed in the following embodiments is also applied to an ICE-based hydrogen electric vehicle.

[0028] The hydrogen fluid fuel includes gaseous hydrogen fuel or liquid hydrogen fuel.

[0029] A compressed hydrogen storage system (CHSS) includes at least one tank mounted on a vehicle and a device connected to the tank to compress and store hydrogen in the tank.

[0030] A pressure relief device (PRD) is a device that isolates hydrogen stored in a CHSS from the vehicle's hydrogen filling system and the surrounding environment, and releases the hydrogen to the outside.

[0031] Hydrogen filling basically refers to the process of receiving high-pressure hydrogen from a dispenser at a hydrogen station and compressing and storing it in a vehicle tank. Hydrogen filling is simply used synonymously with fueling, referring to the supply of hydrogen fuel to a hydrogen electric vehicle. That is, in this specification, "fueling" means fuel supply or hydrogen filling, or filling, and "filling" means filling hydrogen fuel. For example, a fuel supply protocol is referred to as a filling protocol, a fuel supply session is referred to as a filling session, and a fuel supply method is referred to as a hydrogen filling method or a fueling method.

[0032] The pressure ramp rate (PRR) is expressed in MPa / min and refers to the rate at which the pressure of the CHSS increases.

[0033] Average Pressure Ramp Rate (APRR) means the average value of the pressure increase rate from the start to the end of hydrogen fueling.

[0034] Pre-cooling basically refers to the process of pre-cooling hydrogen at a hydrogen filling station before it is filled.

[0035] The dispenser is a component that delivers pre-cooled hydrogen to the CHSS. The dispenser is installed at the hydrogen filling station and performs hydrogen filling operations between the hydrogen storage tank at the hydrogen filling station and the vehicle's CHSS.

[0036] Nozzle means a device connected to a dispenser and mated to a receptacle in a hydrogen electric vehicle to allow delivery of hydrogen fuel.

[0037] The term "fueling session" is used to encompass communication sessions across use cases for hydrogen fueling.

[0038] While the following detailed description illustrates embodiments related to a hydrogen electric vehicle or a fuel cell electric vehicle (FCEV), it will be apparent to those skilled in the art that the concept of the present invention can be applied to various types of hydrogen-fueled mobility. Hydrogen-fueled mobility refers to a type of mobility that uses hydrogen as an energy source or hydrogen as fuel to generate electrical energy and use it to drive an electric motor. In addition to hydrogen-fueled vehicles, hydrogen-fueled mobility also includes aerial mobility, industrial trucks, trains, ships, aircraft, and devices that generate electrical energy using hydrogen as fuel and use it to drive.

[0039] Additionally, the hydrogen filling communication two-way process of the present invention has application not only to hydrogen fueled mobility, but also to hydrogen-powered buildings or facilities in part.

[0040] In the following description, the hydrogen fuel includes at least one of gaseous hydrogen and liquid hydrogen, and basically means compressed hydrogen, but is not limited to this.

[0041] For the sake of convenience, the vehicle using the hydrogen filling communication two-way process will be described mainly as a hydrogen electric vehicle (FCEV), but it is not limited to this configuration and also includes hybrid electric vehicles (EVs) that use hydrogen as fuel, and internal combustion engine (ICE) vehicles.

[0042] Meanwhile, even technologies that were publicly known before the filing date of the present invention are included as part of the present invention, if necessary, and will be described in this specification to the extent that they do not obscure the spirit of the present invention. However, when describing the spirit of the present invention, detailed descriptions of technologies that were publicly known before the filing date and that would be obvious to a person skilled in the art will be omitted because they may obscure the spirit of the present invention. Furthermore, the spirit of the present invention is not intended to claim rights to such publicly known technologies, and the content of publicly known technologies is included as part of the present invention to the extent that it does not deviate from the spirit of the present invention.

[0043] Hereinafter, specific examples of embodiments of the present invention will be described in detail with reference to the drawings.

[0044] Figure 1 is a conceptual diagram of a hydrogen filling system for a hydrogen electric vehicle (FCEV) that applies a two-way hydrogen filling communication process according to one embodiment of the present invention. Figure 2 is a partially enlarged view illustrating the physical fastening structure between the FCEV and the dispenser in the hydrogen filling system of Figure 1. Figure 3 is a graph illustrating changes in the state of hydrogen fuel that occur during the hydrogen filling process using the hydrogen filling system of Figure 1.

[0045] Referring to FIG. 1, the hydrogen filling system is broadly configured to include a hydrogen filling station and a hydrogen electric vehicle 100 .

[0046] The hydrogen electric vehicle 100 includes an electronic control device 110 for hydrogen filling, a vehicle system 120, a vehicle tank 130, and a receptacle 150, in addition to the mechanical, mechanical, electrical, electronic, and communication devices that are basically required for a vehicle.

[0047] The electronic control unit 110 transmits and receives signals and data via wire or wirelessly to and from a hydrogen filling station or an electronic control unit 210 at the hydrogen filling station, processes the signals, and controls hydrogen filling on the vehicle side. The electronic control unit 110 may be configured as at least a part of another electronic control unit installed in the vehicle, or vice versa, and is referred to as the first electronic control unit or electronic control unit #1.

[0048] The vehicle system 120 is connected to the first electronic control unit 110 and is configured to control the filling and discharging of hydrogen into and from the vehicle tank 130 according to signals and commands from the first electronic control unit 110, and to monitor the status of the vehicle tank 130. Depending on the implementation, the vehicle system 120 may be configured to control the operation of the fuel cell system, or may include or be connected to components that perform such control operations. Such a vehicle system 120 is referred to as a vehicle safety system.

[0049] There is at least one, and preferably a plurality, of vehicle tanks 130. The vehicle tanks 130 compress and store hydrogen supplied from a hydrogen filling station and release the stored hydrogen under the control of the vehicle safety system.

[0050] The vehicle tank 130 corresponds to a hydrogen storage system mounted on a vehicle. In this case, the hydrogen storage system is composed of a high-pressure hydrogen storage tank, a pressure control device, high-pressure piping, and an external frame. The high-pressure hydrogen storage tank has a capacity of tens to hundreds of liters and is configured by connecting small storage tanks in parallel. A boss unit through which hydrogen fuel enters and leaves the high-pressure hydrogen storage tank is attached, and hydrogen filling and release are controlled through the boss unit. A valve, a pressure reducing mechanism, and various sensors for measurement are attached to the boss unit. Such a hydrogen storage system is known as a compressed hydrogen storage system (CHSS), and for the sake of convenience, the term "vehicle tank" in this specification refers to a CHSS.

[0051] The hydrogen electric vehicle 100 described above includes a fuel cell system including a fuel cell stack, but is not limited thereto, and for ease of explanation will be referred to simply as an "FCEV" or "vehicle."

[0052] The hydrogen filling station includes a dispenser 200 , an electronic controller 210 , a filling station system 220 , a hydrogen tank 230 , a station box 240 , and a nozzle 250 .

[0053] Dispenser 200 supplies hydrogen, supplied from hydrogen tank 230 under the control of filling station system 220, to a vehicle through nozzle 250 firmly connected to receptacle 150 of the vehicle. Dispenser 200 includes, but is not limited to, an electronic control unit 210 inside the housing. Nozzle 250 is generally installed at the end of a cable extending a certain length outside the housing of dispenser 200.

[0054] The electronic control unit 210 transmits and receives signals and data via wire or wireless to and from the vehicle's first electronic control unit 110 for hydrogen filling, processes the signals, and controls hydrogen filling at the hydrogen filling station. The electronic control unit 210 exchanges preset signals and data with the filling station system 220. The electronic control unit 210 is also referred to as the second electronic control unit or electronic control unit #2.

[0055] Each of the first electronic control unit 110 and the second electronic control unit 210 is configured to include a plurality of electronic control units, and different electronic control units are matched and operated for each communication protocol. This is useful when fallback is required for backward compatibility, or when one-way communication is required because two-way communication is unavailable. It is also useful when combining different communication methods, such as when using WiFi to perform actual filling after pairing with NFC.

[0056] The filling station system 220 monitors or adjusts the pressure, speed, and temperature of the hydrogen released from the hydrogen tank 230 based on signals and / or data from the second electronic control device. To this end, the filling station system 220 controls the operation of a station box 240 connected to the outlet or release valve of the hydrogen tank 230. The filling station system 220 is also referred to as a filling station safety system.

[0057] The hydrogen tank 230 stores hydrogen or compressed hydrogen and releases the stored hydrogen at a predetermined pressure and speed under the control of the filling station safety system 220. The hydrogen tank is also referred to as a hydrogen storage tank.

[0058] The station box 240 has an inlet connected to the outlet or discharge valve of the hydrogen tank 230 and an outlet connected to the dispenser 200 or a nozzle 250 connected to the dispenser 200. The station box 240 includes a control valve. The control valve has an inlet connected to the outlet or discharge valve of the hydrogen tank 230 and an outlet connected to the dispenser 200 or a nozzle 250 connected to the dispenser 200. The station box 240 includes means for adjusting the pressure, speed, temperature, etc. of the hydrogen being released, and components that perform functions corresponding to such means. The station box 240 also includes sensors for measuring the pressure, speed, temperature, etc. of the hydrogen being released.

[0059] The nozzle 250 is connected to the hydrogen fuel supply system of the dispenser 200 through a length of conduit or flexible pipe. The nozzle 250 is shaped and constructed to tightly and securely mate with a receptacle in the vehicle.

[0060] 2, the nozzle 250 engages with the receptacle 150. At this time, a first sensor 160 installed in the vehicle and a second sensor 260 attached to the nozzle 250 transmit signals and information regarding the engagement state between the nozzle 250 and the receptacle 150 to the first electronic control unit and the vehicle safety system, and also to the second electronic control unit and the filling station safety system.

[0061] Pre-cooled hydrogen fuel from the hydrogen filling station is supplied to the hydrogen electric vehicle 100 via a dispenser 200. Here, the hydrogen filling process is described by parameters including the pressure rise rate (PRR) and / or the average pressure rise rate (APRR).

[0062] The interface between the hydrogen filling station and the vehicle 100 is handled by the dispenser 200. The dispenser 200 is configured to control the target pressure and injection rate for hydrogen filling by combining information indirectly acquired from the vehicle tank 130 and fuel supply information from the hydrogen filling station.

[0063] In existing technologies, there are two methods for transmitting information from the vehicle 100 to the dispenser 200: a communication method and a non-communication method. When communication is used, the temperature and pressure values ​​of the vehicle tank 130 of the vehicle 100 are simply transmitted unidirectionally to the dispenser 200, and the dispenser 200 does not actively use the information, but only uses it as a safety standard such as an emergency stop at critical temperature and pressure. In addition, the hydrogen filling protocol for safe and quick filling is managed by the dispenser 200, and it only has minimal safety management equipment that automatically releases hydrogen through a pressure relief device (PRD) without active safety management of the vehicle tank 130.

[0064] Meanwhile, to address the phenomenon of the temperature of hydrogen gas rising during hydrogen filling (see FIG. 3), hydrogen filling stations are equipped with a pre-cooler. The pre-cooler lowers the temperature of the hydrogen fuel through pre-cooling. The pre-cooler is installed in or connected to at least one of the hydrogen tank 230 and the station box 240. Of course, the pre-cooler is also installed in or connected to the piping that transports hydrogen at the hydrogen filling station.

[0065] The dispenser 200 or the second electronic control device is equipped with a filling control logic, which is used to control the hydrogen fueling process by utilizing status information such as the temperature and pressure of the hydrogen fuel supplied to the vehicle or filled into the vehicle tank 130, and filling status information such as the filling rate (SOC: State of Charge) of the CHSS.

[0066] As described above, the hydrogen filling process is controlled by the dispenser 200 between the vehicle 100 and the hydrogen filling station, and the dispenser 200 is equipped with a protocol for supplying hydrogen fuel to the vehicle according to a predetermined procedure. Such a hydrogen filling protocol is also installed in the vehicle. The protocol installed in the vehicle and the dispenser 200 includes at least a part of a communication protocol based on the SAE standard, ISO standard, etc.

[0067] Regarding minimum safety requirements, simulations are carried out through thermodynamic modeling for various situations, and parameters derived through these simulations are used to perform table-based or MC-formula-based partial real-time correction. Here, minimum safety requirements include guidelines for the upper limits of temperature and pressure conditions and State of Charge (SOC) for CHSS.

[0068] If the dispenser 200 does not actively control state values ​​related to hydrogen filling, the conventional table-based method is very inefficient and has difficulty responding flexibly to changes in surrounding conditions because it does not utilize the temperature of pre-cooled hydrogen fuel provided at the gas filling station or the temperature of the vehicle tank 130 measured in the vehicle 100. Furthermore, the conventional MC-Formula-based method corrects the temperature of pre-cooled hydrogen fuel in real time, but the calculation and application methods are complex, limiting its applicability and making it difficult to expand. As such, existing communication protocols were developed with the primary goal of completing safe filling, and there is no alternative for actively controlling unexpected situations such as excessive pre-cooling or overheating of the vehicle tank 130, resulting in problems such as increased operating costs due to overcooling and delays in filling due to overheating.

[0069] For example, when hydrogen fuel is being filled into a vehicle tank (see 130 in Figure 1), the internal temperature of the vehicle tank rises due to the heat of compression, which in turn raises the temperature of the hydrogen fuel inside the vehicle tank. The vehicle tank is configured so that the dome and body of the vehicle tank are surrounded by carbon fiber, which has low heat transfer efficiency, to block heat exchange between the external atmosphere and the hydrogen fuel stored inside. Therefore, when the temperature of the hydrogen fuel inside the vehicle tank rises during the filling process, the temperature rise that appears on the surface of the vehicle tank is minimal compared to the internal temperature rise until filling is complete due to the vehicle tank's low heat transfer characteristics.

[0070] Meanwhile, the temperature control during the hydrogen filling process aims to control the internal temperature of the vehicle tank 130 to 85°C or less at the time of final filling completion after receiving the supply of pre-cooled hydrogen gas. That is, as shown in the characteristic curve for hydrogen temperature during hydrogen filling shown in Figure 3, the temperature of the hydrogen fuel decreases at a constant rate in Phase I (P1), which is the pre-cooling stage of the hydrogen filling station, gradually increases due to the thermal mass of the hydrogen filling station in Phase II (P2), which is the stage of supplying hydrogen fuel from the hydrogen filling station to hydrogen mobility such as a vehicle, the temperature of the hydrogen fuel further increases gradually due to the thermal mass of the vehicle in Phase III (P3), which is the stage of transferring hydrogen fuel from inside the vehicle to the vehicle tank, and finally, the temperature of the hydrogen fuel rises rapidly due to the heat of compression in Phase IV (P4), which is the stage of compressing and storing hydrogen fuel in the vehicle tank.

[0071] Therefore, in this embodiment, the hydrogen filling procedure can be effectively carried out through active state variable control that reflects real-time measurement data through the two-way hydrogen filling communication process, and a hydrogen filling protocol for this purpose can be provided.

[0072] FIG. 4 is a framework for functional blocks that perform a series of hydrogen filling procedures employing a hydrogen filling communication two-way process according to one embodiment of the present invention (hereinafter referred to as the "hydrogen filling framework").

[0073] Referring to FIG. 4, the hydrogen filling framework is a function block for each use case (UC), and includes a discovery and pairing function block (hereinafter, simply referred to as "UC1" or "UC-1"), a communication security function block (UC2 or UC-2), a communication protocol negotiation function block (UC3 or UC-3), a fueling protocol negotiation function block (UC4 or UC-4), a fueling parameter negotiation function block (UC5 or UC-5), a safety check-in function block (UC6 or UC-6), a monitoring and control function block (UC7 or UC-7), a safety check-out function block (UC8 or UC-8), a termination function block (UC9 or UC-9), an error handling function block (UC10 or UC-10), an emergency response function block (UC11 or UC-11), an error handling function block (UC12 or UC-12), an error handling function block (UC13 or UC-13), an error handling function block (UC14 or UC-14), an error handling function block (UC15 or UC-15), an error handling function block (UC16 or UC-16), an error handling function block (UC17 or UC-17), an error handling function block (UC18 or UC-18), an error handling function block (UC19 or UC-19), an error handling function block (UC20 or UC-20), an error handling function block (UC21 or UC21), an error handling function block (UC22 or UC22), an error handling function block (UC23 or UC23), an error handling function block (UC24 or UC24), an error handling function block (UC25 or UC25), an error handling function block (UC26 or UC26), an error handling function block (UC27 or UC27), an error handling function block (UC28 or UC28), an error handling function block (UC29 or UC29), an error handling function block (UC30 or UC30), an error handling function block (UC31 or UC31), The UC-11 includes a UC11 or UC-11 handling function block.

[0074] UC10 and UC11 are individually connected to UC3 to UC8 and configured to perform error processing and / or emergency processing in each use case.

[0075] The above use cases are functional blocks that collectively provide the entire hydrogen filling system's fueling procedures in a consistent manner for safe and secure fueling communication. The vehicle and dispenser execute each use case in a specific order to achieve the hydrogen filling goal.

[0076] After the dispenser nozzle is connected to the vehicle receptacle, the vehicle and dispenser perform fuel supply communication by implementing each use case in the order shown in Figure 4. However, the vehicle and dispenser may omit a specific use case if necessary according to predefined requirements.

[0077] Each of the above use cases is realized through communication between a hydrogen-fueled vehicle and a dispenser control system of a dispenser that supplies hydrogen as fuel to the hydrogen-fueled vehicle according to a fuel supply protocol for the hydrogen-fueled vehicle.

[0078] Meanwhile, a hydrogen-fueled vehicle (hereinafter simply referred to as a "vehicle") and a dispenser that implement the above-mentioned use case exchange data for vehicle identification using UC-1. To this end, the vehicle is equipped with sensors, an electronic control unit (ECU), a transmitter, and a receiver. The receiver is integrally connected to the transmitter for two-way communication.

[0079] The dispenser is also configured to receive specific data from the vehicle. The dispenser stores data for data logging or data specified by the filling station PLC (programmable logic controller) for use in the fueling protocol. Data logging refers to the process of collecting data over a period of time to analyze specific operating conditions of the hydrogen filling system or to record data-based events / operations of the system or network environment, or the data collected by this process. In the case of two-way communication, the filling station is equipped with sensors specified by the fueling protocol, and the filling station PLC or electronic controller obtains measurements from the sensors and sends these measurements to the vehicle. The vehicles and filling stations described above use existing communication protocol standards for communication, such as infrared, Wi-Fi, and Bluetooth.

[0080] Additionally, the vehicle and dispenser are physically coupled at a vehicle-dispenser interface to establish a communication channel between the vehicle and dispenser. The pairing process for establishing such a communication channel may be accomplished using wired, optical, or wireless technology.

[0081] The discovery and pairing procedure or pairing processor has a pre-condition that the dispenser nozzle is inserted into and firmly coupled to a vehicle fueling receptacle, referred to simply as a vehicle receptacle or receptacle.

[0082] Furthermore, the vehicle and dispenser essentially know which communication protocol to follow. Therefore, the communication following UC-1 is a post-condition of the discovery and pairing procedure or pairing process, and depends only on the communication protocol agreed upon for the current use case. If a communication protocol outside the agreed upon range is selected by the vehicle or dispenser, the selected communication will not be carried out. In other words, even if the pairing process is successfully completed, authorization for fuel or fuel supply may not be granted.

[0083] All methods used to pair the vehicle and dispenser will be configured so as not to increase the risk of ignition or explosion above an acceptable level. For example, all wired pairing methods will be configured to mitigate or eliminate spark hazards due to static discharge.

[0084] Regarding the effectiveness of physical pairing, all methods used to pair a vehicle and a dispenser are either integrated into the vehicle-dispenser interface or are installed to ensure proximity between the vehicle's fuel supply receptacle and the dispenser's nozzle and hose assembly. Here, the term "interface" refers to being physically integrated into the nozzle and receptacle interface. Proximity is defined by the hardware associated with the pairing method. For example, the physical geometry used for infrared communication, including the allowable distance between the transmitter and receiver, is specified. Furthermore, while the physical shape of the hydrogen filling hardware is specified in advance, proximity does not include pairing methods that risk pairing a vehicle and dispenser that are not physically connected, such as relatively long-range wireless communication technologies like Bluetooth. Infrared communication is referred to as infrared data association (IrDA) communication, including bidirectional infrared (bi-IrDA) communication.

[0085] FIG. 5 is an exemplary diagram illustrating a communication stack related to each use case employed in a two-way hydrogen filling communication process according to an embodiment of the present invention, focusing on the seven layers of the Open Systems Interconnection reference model (OSI).

[0086] As illustrated in Figure 5, the communication stack (simply referred to as the "hydrogen filling communication stack") associated with the use case of the hydrogen filling communication two-way process is expressed as protocol suites corresponding to each of the seven OSI layers: data link and physical layer, network layer, transport layer, security layer, session layer, presentation layer, and application layer.

[0087] That is, the hydrogen filling communication stack includes at least one first protocol 510 selected from bidirectional IrDA (bi-IrDA), WLAN, NFC, etc. as a protocol for the data link and physical layers of the OSI 7 layer.

[0088] The hydrogen filling communication stack also includes the IPv6 (Internet Protocol Version 6) protocol 520 as a protocol for the network layer of the OSI 7 layer.

[0089] The hydrogen filling communication stack also includes at least one third protocol 530 selected from TCP (transmission control protocol), UDP (user datagram protocol), etc. as a protocol of the transmission layer of the OSI 7 layer.

[0090] The hydrogen filling communication stack also includes at least one fourth protocol 540 selected from transport layer security (TLS), datagram transmission layer security (DTLS), etc. as protocols of the OSI 7 security layer. TLS includes versions such as TLS 1.2 and TLS 1.3, and DTLS includes versions such as DTLS 1.2 and DTLS 1.3. TLS is implemented using a TCP socket, and DTLS is implemented using a UDP socket.

[0091] The hydrogen filling communication stack also includes a JSON-based session protocol 550 as a protocol of the session layer of the OSI 7 layer. The JSON-based session protocol 550 is used for communication between a vehicle and a dispenser or for sending data between the electronic control unit of a vehicle and the electronic control unit of a filling station.

[0092] The hydrogen filling communication stack also includes JSON (JavaScript Object Notation) 560 as a protocol in the OSI 7 layer representation hierarchy. JSON is one of the formats used when sending data from a server to a client. Using JSON, protocol messages between a vehicle and a dispenser, or between a vehicle's electronic control unit and a filling station's electronic control unit, can be expressed in JSON.

[0093] The hydrogen filling communication stack also includes hydrogen filling-related fueling protocols (FP) 570 as protocols in the application layer of the OSI 7 layer. The fueling protocols 570 include a first fueling protocol FP1, a second fueling protocol FP2, and an n-th fueling protocol FPn, where n is any natural number equal to or greater than 3.

[0094] In yet another embodiment, the hydrogen filling communication stack described above is configured to use protocols such as programmable logic controller (PLC) and WLAN as protocols for the data link, physical layer, and network layer, TCP and / or IPv6 as protocols for the transmission layer and security layer, binary extensible markup language (XML) as a protocol for the session layer corresponding to the encoding layer, and one of existing protocols used in electric vehicles as a protocol for the representation layer and application layer. The existing protocols used in electric vehicles include at least one protocol for direct current (DC) charging, alternate current (AC) charging, wireless power transfer (WPT), automatic connection device pantograph (ACDP), etc. of electric vehicles.

[0095] The general communication data items exchanged between the vehicle and the filling station through the hydrogen filling communication stack described above are shown in Table 1 below.

[0096] [Table 1]

[0097] Meanwhile, the discovery and pairing procedure use case (UC1) allows a device to identify the communication partner (vehicle or dispenser communication module) responsible for controlling the physically connected receptacle or nozzle. UC-1 also defines a method for identifying incompatibilities and a fail-safe mechanism. In this use case (UC1), the vehicle and dispenser attempt to find a common communication technology to execute the fuel supply protocol. The vehicle and dispenser search for each other and begin communication using the search mechanism provided by the basic data link and physical layers. An additional pairing procedure is required to establish a communication channel with the device connected to the fuel supply hose assembly. If the communication channel does not guarantee correct pairing, such as wireless communication, a separate pairing channel is required to transmit pairing information. If pairing is implicitly guaranteed, for example, a communication channel integrated into the hose assembly is sufficient.

[0098] FIG. 6 is an exemplary diagram illustrating a pairing process of a discovery and pairing procedure employed in a two-way hydrogen filling communication process according to an embodiment of the present invention.

[0099] Referring to FIG. 6, in the pairing process, when pairing is performed at UCDC Level 2 and UCDC Level 3, the vehicle and the dispenser exchange pairing IDs and confirm each other's pairing ID.

[0100] For example, a vehicle broadcasts a message (PAIR_ID_ANNOUNCE) including its pairing ID (PAIR_ID), i.e., a vehicle ID (vehicle_id) (S710). The dispenser transmits a message (PAIR_ID_ACK) to the vehicle, acknowledging that it has received the vehicle ID from the vehicle (S720). The vehicle transmits a message (PAIR_ID_CONFIRM) to the dispenser, acknowledging that the dispenser has successfully received the vehicle ID as an ACK message (S730).

[0101] Next, the dispenser broadcasts a message (PAIR_ID_ANNOUNCE) including its pairing ID, i.e., the dispenser ID (dispenser_id) (S740). The vehicle transmits a message (PAIR_ID_ACK) to the dispenser, acknowledging that it has received the dispenser ID from the dispenser (S750). The dispenser transmits a message (PAIR_ID_CONFIRM) to the vehicle, acknowledging that it has successfully received the dispenser ID as an ACK message (S760).

[0102] This transmission-echo-verification method allows the vehicle and dispenser to use a session-specific randomized pairing ID, which solves the problem of protecting personal information regarding pairing ID exchange. That is, trust in the pairing process is established by a subsequent process, and for this reason, the session-specific pairing ID is included in the data used to establish trust.

[0103] On the other hand, if a particular UCDC level supports secure communications, at least one of the vehicle and the dispenser verifies that for any method used to pair the vehicle and the dispenser, the pairing provides sufficient information to secure the communication channel, for example, pairing may include exchanging encryption keys so that the vehicle and the dispenser can secure communications during fueling.

[0104] For reference, UCDC Level 1 does not support two-way communication and therefore does not allow for communication channel security. Pairing a vehicle and a dispenser at UCDC Level 2 and UCDC Level 3 is configured to provide sufficient information to secure communication to meet a specific security level, such as IEC 62443 Security Level 3. IEC 62443 Security Level 3 is a security level for actors with appropriate resources and appropriate motivation.

[0105] FIG. 7 is an exemplary diagram illustrating backward compatibility employed in a hydrogen filling communication two-way process according to an embodiment of the present invention.

[0106] Referring to Figure 7, hydrogen filling devices are made up of existing devices and backward compatible devices for interoperability. When devices are classified based on interoperability, hydrogen filling devices and their communication devices are classified into Type 0, Type 1, Type 2, and Type 3.

[0107] Type 0 refers to a device that does not support communication for fueling and cannot receive the corresponding communication message.

[0108] Type 1 refers to devices that support IrDA communication for fuel delivery. Type 1 devices fall back to Type 0 devices.

[0109] Type 2 refers to devices that support advanced communication (AC). Type 2 devices fall back to Type 0 devices.

[0110] Type 3 refers to devices that support IrDA and advanced communications. Type 3 devices invoke fallback on one of Type 0, Type 1, and Type 2.

[0111] Advanced communication refers to communication using a medium and specific protocol, such as wireless local area network (WLAN), Bluetooth (BT), near field communication (NFC), WiFi, ultra-wideband (UWB), radio frequency identification (RFID), 4G, or 5G. Advanced communication also includes two-way IrDA, serial communication, vehicular Ethernet (ETH), and high-level communication. Specific protocols include transmission control protocol / internet protocol (TCT / IP) and fueling protocols. High-level communication handles all information beyond that handled by command and control communication. The data link for high-level communication uses, but is not limited to, power line communication (PLC).

[0112] In addition, advanced communication is a hybrid form, including a form that combines IrDA and wired, and a form that combines IrDA and wireless. In the case of a form that combines IrDA and wired, modifications to the nozzle and receptacle are required.

[0113] That is, advanced communication is a wired / wireless bidirectional communication technology, and wireless communication technologies include various communication means such as 5G, WLAN, BLE, ETH, UWB, RFID, and NFC. Known protocols such as TCP / IP can be used as protocols for such communication means. For example, communication means considered to be wireless communication include Bluetooth (registered trademark), WLAN, Wi-Fi (ISO 15118 for inductive / ACD), and UWB (IEC limited consideration for ACD).

[0114] In practice, hydrogen filling devices are implemented to support communication of different technologies, and therefore the hydrogen filling communication two-way process of the present embodiment is configured to maximize interoperability between devices.

[0115] In other words, as shown in FIG. 7, when a Type 1 device supporting Specification #1 according to a predetermined standard meets a Type 0 device or a Type 2 device, the Type 1 device falls back to a Type 0 device (S710).

[0116] Also, when a Type 2 device supporting Specification #2 conforming to a predetermined standard encounters a Type 0 device or a Type 1 device, the Type 2 device falls back to the Type 0 device (S720).

[0117] If a Type 3 device supporting Standard #2 meets a Type 0 device, the Type 3 device falls back to the Type 0 device (S730). If a Type 3 device meets a Type 1 device, the Type 3 device falls back to the Type 1 device (S740). If a Type 3 device meets a Type 2 device, the Type 3 device falls back to the Type 2 device (S750).

[0118] The above-mentioned standard #1 includes the SAE (Society of Automotive Engineers) standard, etc. The above-mentioned standard #2 includes the ISO 19885-3 standard, etc.

[0119] To support the interoperability, the hydrogen filling device performs a connection compatibility check. For example, the hydrogen filling device performs the connection compatibility check as shown in the following scenarios 1 to 3 depending on whether or not WLAN, one of the advanced communications, is supported.

[0120] In Scenario 1, the dispenser prepares an access point (AP), which is a wireless router. The dispenser supports FCEV fuel station beaconing and fuel supply methods at VSE (vehicle supply equipment). An FCEV that is close to a dispenser scans to find the dispenser and establishes a WLAN link with the found dispenser.

[0121] In scenario 2, the dispenser does not support WLAN communication but supports IrDA communication. The dispenser is a Type 1 device. The FCEV close to the dispenser is a Type 3 device and cannot find the dispenser, which is a Type 1 device, by scanning. When the FCEV receptacle is connected to the nozzle attached to the dispenser cable, IrDA communication begins between the FCEV and the dispenser.

[0122] In Scenario 3, the dispenser supports WLAN and IrDA communication. In this case, the dispenser corresponds to a Type 3 device. An FCEV, a Type 1 device, is parked near the dispenser. The dispenser cannot yet find any WLAN clients. When the FCEV's receptacle is connected to the nozzle attached to the dispenser's cable, IrDA communication begins between the FCEV and the dispenser.

[0123] FIG. 8 is an exemplary diagram illustrating backward compatibility employed in a hydrogen filling communication two-way process according to an embodiment of the present invention.

[0124] Referring to FIG. 8, the hydrogen filling communication two-way process of this embodiment provides rules and principles that allow the FCEV and dispenser to not necessarily select the optimal communication method, but rather fall back to a fueling method and communication protocol that maximizes interoperability.

[0125] That is, when one of the vehicles and dispensers meets the other, the device with the higher type or UCDC level is configured to fall back to the type or level of the device with the lower type or level.

[0126] For example, if the vehicle and dispenser are the same type or UCDC level, both devices will maintain their current type or UCDC level. On the other hand, if one device is a Type 1 device and the other is a Type 2 device, both devices will be configured to fall back to a Type 0 device. And if one device is a Type 3 device and the other is not a Type 3 device, the Type 3 device will be configured to fall back to the same type or UCDC level as the other device.

[0127] The above-mentioned standard #1 is a communication protocol based on the SAE standard, and standard #2 is a communication protocol based on the ISO 19885 standard.

[0128] According to the above configuration, when there are two devices with the same implementation, the vehicle and suspension support both and select the best one. When a device with no communication (hereinafter referred to as a "non-communication device") meets a device that supports one-way communication (hereinafter simply referred to as a "one-way communication device"), the latter falls back to the no-communication (No comm) device that does not support the communication method. Also, when two devices that support two-way communication meet, the two devices maintain the two-way communication method. Here, UCDC compatibility is handled separately. Also, when a device meets a non-communication device, it must rely on non-communication. This applies to all devices that support two-way communication (hereinafter simply referred to as a "two-way communication device").

[0129] Also, when a one-way communication device meets a two-way communication device, if the two-way communication device supports both one-way and two-way communication methods, the two-way communication device falls back to the one-way communication method, and if the two-way communication device does not support one-way communication, the two-way communication device falls back to the non-communication method, relying on no communication (No comm).

[0130] The two-way communication device described above is configured to support a fuel supply method using one-way communication regardless of whether one-way communication is used. Such a two-way communication device must confirm that the other party supports two-way communication. If the FCEV or dispenser does not support two-way communication, the two-way communication device falls back to a one-way communication device that uses a compatible one-way communication method.

[0131] FIG. 9 is an exemplary diagram illustrating the classification of communication data used in a two-way communication process for hydrogen filling according to an embodiment of the present invention and backward compatibility in the classification of communication data.

[0132] As shown in Figure 9, vehicles and dispensers possess a pairing identity (ID), but the requirements for exchanging such identity are categorized by use classification of communication data (UCDC) levels. UCDC levels include UCDC Level 1 (UCDC-1) (910), UCDC Level 2 (UCDC-2) (920), and UCDC Level 3 (UCDC-3) (930). UCDC levels also include UCDC Level 0 (UCDC-0) (900).

[0133] UCDC Level 0 (900) refers to communication where no data is transmitted or where data is transmitted but is not used by the fuel supply protocol for dispensing of hydrogen or related safety functions. UCDC Level 0 (900) does not support communication between the vehicle and the dispenser (no communication), so the dispenser cannot transmit the pairing ID to the vehicle during process control or safety functions.

[0134] When pairing at UCDC Level 1 (910), the vehicle transmits the pairing ID to the dispenser. The data transmitted to UCDC Level 1 (910) is not used for safety functions, but the transmitted static data is used to improve the performance of the fuel supply protocol, and the transmitted dynamic data is used to reduce the risk of process deviations within the fuel supply protocol.

[0135] Static data transmitted to UCDC Level 2 (920) is used for safety functions. This UCDC Level 2 (920) static data is in addition to the permitted uses for static and dynamic data defined for UCDC Level 1.

[0136] At UCDC Level 3 (930), static and dynamic data are used for dynamic control within a protocol or safety function. Such UCDC Level 3 (930) dynamic data is in addition to the permitted uses of static and dynamic data defined for UCDC Level 2.

[0137] As described above, UCDC levels have a structure in which UCDC level 1 is included in UCDC level 2, and UCDC level 2 is included in UCDC level 3, i.e., higher levels include lower levels. A device that supports a particular UCDC level supports a device with a lower UCDC level. Devices that support different UCDC levels use the highest UCDC level supported by the two devices. It can be said that the above UCDC levels also easily support UCDC level 0.

[0138] FIG. 10 is a flowchart illustrating the authentication process of the communication security procedure employed in the hydrogen filling communication two-way process according to one embodiment of the present invention.

[0139] 10, the FCEV transmits a message requesting a list of authorization methods to the dispenser (S1010). The dispenser transmits a response message to the FCEV in response to the FCEV's authorization method list request (S1020). The response message includes authorization method list information related to external authorization procedures such as RFID (radio frequency identification), credit cards, and debit cards, as well as self-authorization procedures.

[0140] Next, the FCEV transmits an authentication request message including a specific method selected from the authentication method list, such as RFID, to the dispenser (S1030). The dispenser transmits a response message to the FCEV's authentication request (S1040). This response message includes information indicating that the authentication method selected by the FCEV is working.

[0141] Next, the FCEV performs authentication using the authentication method selected previously in response to the dispenser's response and transmits a message requesting confirmation of the authentication completion (Done?) to the dispenser (S1050). If the authentication completion cannot be confirmed or the authentication is not completed, the above series of steps (S1010 to S1050) are repeated. When the authentication is completed, the dispenser transmits an authentication completion (Done(success)) message to the FCEV (S1090).

[0142] According to the above configuration, the dispenser verifies that the FCEV is approved, i.e., that the user of the FCEV has the authority to fill it with hydrogen, before proceeding further with the hydrogen filling process.

[0143] For security during the authentication process, the hydrogen filling device, which includes at least one of a vehicle and a dispenser, establishes a data link and physical layer connection between the vehicle and the dispenser, then establishes a transport layer, i.e., a TCP connection, and then performs a TLS handshake to authenticate and exchange keys to establish a secure communication channel. Furthermore, while security-critical information is exchanged, UDP communication protected by DTLS is used.

[0144] Furthermore, the vehicle and dispenser successfully complete discovery and pairing procedures to establish a data link and physical layer connection. Then, the credentials necessary for authentication and key exchange are prepared. The communication channel between the vehicle and dispenser is encrypted and integrity-protected. The dispenser authenticates the vehicle, and optionally the vehicle authenticates the dispenser.

[0145] Meanwhile, during the above-mentioned TLS handshake, vehicle authentication is mandatory and dispenser authentication is optional, in which case the dispenser acts as the client and the vehicle acts as the server.

[0146] For a TLS handshake, the vehicle and dispenser must prepare the necessary credentials. The vehicle and dispenser store the certificate chain, the corresponding private keys, and the trust anchor certificate in a secure repository that protects them from unauthorized access.

[0147] During the TLS handshake, the vehicle requests client authentication from the dispenser by sending a predefined CertificateRequest message. Upon receiving the CertificateRequest message, the dispenser sends a certificate and a CertificateVerify message to transmit the certificate to the vehicle.

[0148] When a vehicle sends a certificate request message along with a handshake message such as ServerHello, if the dispenser does not send a certificate verification message along with the certificate, the vehicle will send a warning message containing the "certificate_required" warning code and abort the TLS handshake.

[0149] FIG. 11 is a flowchart illustrating the communication protocol negotiation procedure employed in the hydrogen filling communication two-way process according to one embodiment of the present invention.

[0150] Referring to FIG. 11, in the communication protocol negotiation procedure, the FCEV transmits a negotiation request message to the dispenser to start protocol negotiation in order to identify the protocol version of the fuel supply protocol that the FCEV and dispenser will use for the two-way hydrogen filling communication process (S1110).

[0151] Next, the dispenser provides the FCEV with a response message including a protocol list for communication protocols supported by the dispenser in response to the negotiation request message (S1130). The response message includes information on communication protocols supported by SAE standards, ISO standards, etc. SAE standards include the SAE J2601 standard, etc., and ISO standards include the ISO 19885-3 standard, the ISO 19885-4 standard, etc.

[0152] Next, the FCEV selects a specific protocol, for example, the ISO-v1-ucdc-3 protocol, from a protocol list of communication protocols supported by the dispenser, and transmits a protocol selection message including information about the selected communication protocol to the dispenser (S1150).

[0153] Next, the dispenser checks the protocol included in the protocol selection message from the FCEV and transmits a negotiation OK message to the FCEV (S1170).

[0154] The above-described communication protocol negotiation procedure is a procedure for identifying the communication protocol to be followed during a hydrogen fueling session after the vehicle and dispenser discover and pair with each other through a compatible communication channel. In particular, in this embodiment, the dispenser takes the initiative in exchanging communication protocols and parameters with the vehicle.

[0155] The communication protocol negotiation procedure is implemented with all available communication protocols to ensure successful negotiation between different fueling protocols for each communication technology. For example, a fueling protocol using a communication technology such as WLAN uses a protocol commonly supported by the vehicle and dispenser (hereinafter also referred to as a "common protocol") to determine the communication protocol to be used in the hydrogen filling communication two-way process.

[0156] In practice, various combinations of FCEVs and dispensers at each site may occur depending on the hydrogen filling communication-related standards, communication modes, fuel supply methods, communication levels, and other parameters. Here, hydrogen filling communication-related standards include the SAE J2601 series, ISO 19885-3, ISO 19885-4, etc. Communication modes include no comm., IrDA, XYZ (ISO), etc. Fuel supply methods include table-based filling methods such as lookup tables and MC formula-based filling methods. Furthermore, communication levels include UCDC levels, and other parameters include pressure class, compressed hydrogen storage system (CHSS) category, and hydrogen filling tables.

[0157] Meanwhile, the vehicle or dispenser may be further configured to perform a process of falling back to a lower type or UCDC level of the other party depending on the mutual type or UCDC level confirmed in the communication protocol negotiation procedure.

[0158] In addition, in an environment where various combinations can occur, if incompatibility is found in the parameters exchanged while the vehicle and dispenser are performing the hydrogen filling negotiation procedure (UC3 to UC5), they return to the communication protocol negotiation procedure and perform the negotiation procedure again.

[0159] FIG. 12 is a flowchart illustrating yet another communication protocol negotiation procedure in a two-way hydrogen filling communication process according to another embodiment of the present invention.

[0160] Referring to FIG. 12, during the communication protocol negotiation procedure, the FCEV selects a protocol list (<list of protocols> The communication protocol to which priority is assigned includes protocols having priorities as shown in Table 2.

[0161] The dispenser will run a specific protocol (<selected protocol> The dispenser transmits a response message including the specified protocol to the FCEV (S1230). The specified protocol is a common protocol selected by the dispenser, supported by both the dispenser and the vehicle, and is the highest priority protocol that is optimal for the vehicle, such as the ISO 19885-3-2023-UCDC-3 protocol (see Table 2).

[0162] According to the common protocol, the vehicle and dispenser reach agreement on a communication protocol to use for fueling communication.

[0163] Meanwhile, vehicles assign priorities to the communication protocols they support. Vehicles include FCEVs. The vehicles provide the dispensers with prioritized communication protocols. Examples of prioritized communication protocols are shown in Table 2 below.

[0164] [Table 2]

[0165] Once the communication protocol is selected in the above-mentioned communication protocol negotiation use case (UC3), the vehicle and dispenser activate their respective communication protocol implementations and begin fuel supply protocol negotiation. Fuel supply protocol negotiation is a process in which the vehicle and dispenser search for and agree on the fuel supply protocol to be used in the fuel supply session. At this stage, the vehicle and dispenser select the communication protocol that is best suited to the vehicle from among the protocols that both support.

[0166] FIG. 13 is a flow chart illustrating the fueling protocol negotiation procedure employed in the hydrogen filling communication two-way process according to one embodiment of the present invention.

[0167] The fueling protocol negotiation procedure involves a step in which the vehicle and the dispenser exchange detailed parameters necessary to execute the fueling protocol. The vehicle includes an FCEV.

[0168] Referring to FIG. 13, in the fuel supply protocol negotiation procedure, the FCEV selects the first parameter (<FCEV’s parameter> ) to the dispenser (S1310).

[0169] The first parameters include parameters for supporting fueling method compatibility, parameters for physical characteristics, monitoring parameters, acceptance-related parameters, and the like.

[0170] Here, compatibility support related parameters include pressure class, CHSS category, etc., physical characteristic parameters include maximum allowable CHSS pressure, maximum allowable CHSS temperature, maximum allowable speed, CHSS volume, etc., monitoring parameters include current CHSS pressure, current CHSS temperature, etc., and acceptance related parameters include parameters indicating information indicating whether or not accepted, for example, yes (true) or no (false). The above parameters are set with information for a main UCDC level that is different from or the same as information for one of the pre-specified levels or setting values.

[0171] On the other hand, the dispenser can support a second parameter (<DIS’s parameters> )(briefly<DIS’s params> ) and information about the protocol selected from the first parameter ( <ok>The controller 100 transmits a response message including the information (see reference) to the FCEV (S1330).

[0172] Secondary parameters related to fueling protocol negotiation include parameters to support compatibility of fueling methods, parameters for physical characteristics, parameters related to fueling goals, monitoring parameters, acceptance-related parameters, etc.

[0173] Here, compatibility support related parameters include fuel delivery temperature, selected fueling table, etc., physical characteristic parameters include maximum fuel delivery pressure, maximum fuel delivery temperature, minimum fuel delivery temperature, maximum fuel delivery speed, etc., fuel delivery target related parameters include target state of charge (SOC), target final CHSS pressure, target final CHSS temperature, target average fueling rate (APR), expected fueling duration, etc., monitoring parameters include current fuel delivery temperature, atmospheric temperature, etc., and acceptance related parameters include parameters such as accepted. For the above parameters, information for a main UCDC level that is different from or the same as information for one of the preset levels or set values ​​is set, respectively.

[0174] In this manner, the FCEV provides the dispenser with parameters listed in a table format, including FCEV parameters compatible with the UCDC levels negotiated during the fueling protocol negotiation phase.

[0175] On the other hand, the dispenser can support a second parameter (<DIS’s parameters> )(briefly<DIS’s params> ) and information about the protocol selected from the first parameter ( <ok>The system transmits a response message including the information (see the relevant section) to the FCEV.

[0176] Furthermore, the second parameter related to the fueling protocol can be shown in another form as shown in Table 3.

[0177] [Table 3]

[0178] As shown in Table 3, the dispenser provides the FCEV with parameter information in table format, including reference information such as arbitrarily assigned names for supportable fuel supply methods and fuel supply protocols, revision dates (years), version information, information on whether subprotocols are available, and priority. Furthermore, the dispenser is configured to proactively exchange its own communication protocols and parameters with the vehicle, just like the vehicle, and prioritize the communication protocols it supports before providing them to the vehicle.

[0179] In Table 3, PRHYDE (PROtocol for heavy-duty HYDrogEn refueling) is presented as one of the European projects that has developed a refueling protocol for heavy-duty vehicles, RTR-HFP is presented as a protocol concept that improves refueling efficiency based on real-time communication, and ANN-MPC is presented as a protocol concept that collects and analyzes data from the refueling site and applies predictions to actual refueling conditions.

[0180] In addition, examples of information on the selection protocol related to the fueling protocol transmitted from the dispenser to the FCEV are shown in Tables 4 and 5 below.

[0181] [Table 4]

[0182] As shown in Table 4, the dispenser selects the fuel supply protocol corresponding to index 2 and transmits a response message including a result code OK to the FCEV.

[0183] [Table 5]

[0184] As shown in Table 5, if the dispenser fails to find a compatible protocol in the list of fueling protocols supported by the FCEV received from the FCEV, it transmits a response message to the FCEV containing information indicating that there is no common protocol (e.g., FAIL_NO_COMMON_PROTOCOL) in the ResultCode field. As described above, once a communication link is established and a communication protocol is selected in the protocol negotiation phase, the FCEV and dispenser exchange various parameters to confirm that they can execute a compatible fueling procedure. Here, the information required to execute a safe and efficient fueling procedure includes compatibility parameters, physical characteristics, fueling targets, monitoring parameters, etc.

[0185] Compatibility parameters include, for example, pressure rating, fuel delivery temperature, etc.; physical properties include, for example, maximum CHSS pressure, maximum flow rate, etc.; fuel delivery targets include, for example, target state of charge (SOC), target CHSS pressure, etc.; and monitoring parameters include, for example, current CHSS temperature, ambient temperature, etc.

[0186] If compatible parameters cannot be found and fuel supply cannot proceed, the FCEV returns to the communication protocol negotiation step and attempts to negotiate another protocol, or stops fuel supply to the dispenser. In the communication protocol negotiation step to which the FCEV returns due to a failure in the fuel supply parameter exchange step, the FCEV is configured to propose to the dispenser a supported protocol suite excluding the protocol that failed in the fuel supply parameter exchange step.

[0187] When a fueling protocol is negotiated according to the use case (UC-4) described above, the vehicle and dispenser negotiate specific parameters for the fueling protocol, communicate static or dynamic conditions, and exchange detailed fueling parameters to determine fueling targets. If the fueling parameter negotiation fails due to incompatibility, the vehicle returns to UC-3 to select another fueling protocol or returns to UC-1 to select another communication protocol, and if this fails, the current communication is terminated.

[0188] According to the above configuration, some fueling protocols are performed on a non-communication basis. Some fueling protocols require unidirectional IrDA. Some fueling protocols require bidirectional communication. Some fueling protocols require both bidirectional communication and unidirectional IrDA.

[0189] A certain fuel supply protocol requires a certain UCDC level or a higher UCDC level to be executed. At least one fuel supply protocol is proposed based on the type of hydrogen electric vehicle and the type of dispenser. The proposed fuel supply protocols are proposed with different priorities. Taking into account the priority of the proposed fuel supply protocol, the communication protocol and fuel supply protocol between the hydrogen electric vehicle and the dispenser are finally determined based on whether the communication protocol required by the fuel supply protocol is supported by the hydrogen electric vehicle and / or the dispenser.

[0190] FIG. 14 is a flow chart illustrating the fueling parameter negotiation procedure employed in the hydrogen filling communication two-way process according to one embodiment of the present invention.

[0191] As shown in Figure 14, the vehicle and dispenser determine the detailed parameters necessary to execute the selected fueling protocol with the desired safety level and performance. In other words, once the fueling protocol selection is completed in the fueling protocol negotiation, the vehicle and dispenser exchange the detailed parameters that must be exchanged before executing the corresponding fueling protocol. That is, the FCEV sends the parameter values ​​of the fueling parameters to the dispenser (S1410), and when the dispenser responds with its own parameter values ​​(S1430), the fueling parameter negotiation begins. During the parameter exchange, the vehicle and dispenser determine whether or not the fueling protocol can be executed.

[0192] During fuel supply parameter negotiation, the FCEV and dispenser exchange protocol-specific parameters necessary for proper and efficient hydrogen fueling while maintaining the hydrogen filling system in a safe state one or more times until they reach a protocol-specific agreement. Upon receiving the parameters, the receiver transmits a response message to the sender indicating acceptance of the parameters. Parameter acceptance is indicated by a value of "true" in the "accepted" field; otherwise, acceptance is indicated by a value of "pending" or "false."

[0193] After receiving the fuel supply protocol negotiation response message from the dispenser, the FCEV transmits the fuel supply protocol negotiation response message within a preset message processing time to provide the fuel supply parameters to be set in the dispenser.

[0194] Examples of FCEV parameters are shown in Table 6 below.

[0195] [Table 6]

[0196] The dispenser parameters are shown in Table 7 below. [Table 7]

[0197] As described above, in the fueling parameter negotiation procedure, the FCEV transmits a message having ranges / values ​​for the third parameters (fueling parameters) that it can support to the dispenser (S1410). The third parameters include physical property-related parameters (simply referred to as "physical parameters"), monitoring parameters, safety policy-related parameters, and acceptance-related parameters.

[0198] Here, the physical parameters include receptacle type, pressure class, CHSS category, CHSS type, CHSS capacity, maximum allowable CHSS pressure, maximum allowable CHSS temperature, maximum allowable speed, etc., the monitoring parameters include current CHSS pressure, current CHSS temperature, etc., the safety policy-related parameters include emergency policy, safety enforcement level, etc., and the acceptance-related parameters include parameters indicating information indicating whether accepted or not, such as yes (true), no (false), or pending.

[0199] Meanwhile, the dispenser transmits a message including ranges and values ​​for the fourth parameters (fueling parameters) that it can support to the FCEV (S1430).

[0200] The fourth set of parameters relevant to fueling parameter negotiation includes physical property-related parameters (simply "physical parameters"), monitoring parameters, fueling target-related parameters, safety policy-related parameters, and acceptance-related parameters.

[0201] Here, the physical parameters include fuel delivery temperature, maximum fuel delivery pressure, maximum fuel delivery temperature, minimum fuel delivery temperature, maximum fuel delivery speed, etc., the monitoring parameters include current fuel delivery temperature, ambient temperature, etc., the fuel delivery target-related parameters include selected fueling table, target state of charge (SOC), target final CHSS pressure, target final CHSS temperature, target average fuel delivery rate (APR), expected fuel delivery time, etc., and the acceptance-related parameters include parameters such as accepted. The above parameters are set with information for a main UCDC level that is different from or the same as information for one of the preset levels or set values.

[0202] In this manner, the FCEV provides the dispenser with parameters listed in a table format, including FCEV parameters compatible with the UCDC levels negotiated during the fueling protocol negotiation phase.

[0203] On the other hand, after receiving the fuel supply parameter negotiation request message, if the received fuel supply parameters are compatible with the dispenser, the dispenser responds with its own fuel supply parameters by transmitting a fuel supply parameter negotiation response message with the "Result" set to "OK" to the FCEV within a preset message response time.

[0204] Furthermore, if the dispenser finds that the fuel supply parameters of the vehicle are incompatible after receiving the fuel supply parameter negotiation request message, the dispenser responds by transmitting a fuel supply parameter negotiation response message to the FCEV with the "result" set to "failed" to indicate incompatibility with the corresponding vehicle, the FCEV. The result indicates the value or information contained in the result code field, and the failure is a failure at a specific time and is expressed as an expression indicating incompatibility, such as "fail_incompat."

[0205] In addition, if the FCEV finds that the fuel supply parameters of the dispenser are incompatible after receiving the fuel supply parameter negotiation request message, the FCEV notifies the dispenser of the incompatibility by transmitting an error notification request message to the dispenser along with a "reason" set for each predefined error code.

[0206] Meanwhile, before fueling begins, the vehicle and dispenser verify that all safety conditions have been met through a use case (UC6) for safety check-in. While this step is optional, it is preferable to define a dedicated safety check-in procedure in the fueling protocol to ensure the desired safety level in a precise and explicit manner.

[0207] FIG. 15 is a flow chart illustrating the safety check-in procedure employed in the hydrogen filling communication two-way process according to one embodiment of the present invention.

[0208] A safety check-in procedure ensures that the vehicle, including the FCEV, and the dispenser have met all necessary safety requirements before actual fueling begins.

[0209] Once the fueling parameters have been exchanged and the vehicle and dispenser are deemed compatible, the vehicle and dispenser perform a safety condition check to ensure that fueling is safe. The fueling protocol performs the safety check implicitly within the protocol, and the implementation omits the safety check step.

[0210] Also, during the security check-in procedure, the vehicle and / or dispenser is checked for nozzle-receptacle seating and leaks, and the last-minute status is checked.

[0211] Also, after receiving the fuel supply parameter negotiation response message from the dispenser, if the fuel supply protocol supports safe check-in, the vehicle transmits a safe check-in request message to the dispenser within the message sequence set time to start the safe check-in procedure.

[0212] Specifically, as shown in Figure 15, the vehicle and the dispenser exchange messages for coupler check (S1510, S1520). The vehicle transmits a message including information indicating its own coupler check result (e.g., FCEV: OK) to the dispenser, and the dispenser transmits a message including information indicating its own coupler check result (e.g., DP: OK) to the vehicle.

[0213] The vehicle and dispenser also exchange messages related to a gas leak check (S1530, S1570). During the exchange of leak check-related messages, the dispenser transmits information indicating that a leak check is in progress (ongoing) to the vehicle (S1540). The vehicle then transmits information indicating that it is waiting for the dispenser's leak check results (waiting) to the dispenser (S1560). Once the leak check is complete, the dispenser transmits a message requesting the measured tank volume along with information indicating that the leak check has been completed (Done) to the vehicle (S1570).

[0214] The dispenser also transmits a message to the vehicle for an immobilized status check (S1580), and the vehicle transmits a message to the dispenser informing it that it is ready for the status check (S1590).

[0215] In this way, when the vehicle reports parameters such as the vehicle's current status or immobilization status to the dispenser, the dispenser reports parameters such as coupler lock status, leak check status, predicted FCEV tank capacity, etc. to the vehicle.

[0216] Once the safety check-in procedures described above are passed, fueling begins. During fueling, the vehicle and dispenser exchange information to monitor various status parameters to ensure that fueling is performed safely and efficiently. When necessary, the vehicle or dispenser sends control messages to control the fueling procedure or request action from the other party to address a safety-related condition. The parameters and commands exchanged vary depending on the actual fueling protocol.

[0217] FIG. 16 is a flow chart illustrating the monitoring and control procedures employed in the hydrogen filling communication two-way process according to one embodiment of the present invention.

[0218] In the monitoring and control procedure, the vehicle, including the FCEV, and / or the dispenser monitor the fuel supply status and control the fuel supply as needed. Once all safety checks are confirmed, the vehicle and dispenser begin fuel supply according to the selected fuel supply protocol using given parameters. During fuel supply, the vehicle and dispenser exchange various measurement data to understand the fuel supply status and operate as quickly as possible to safely and critically detect the occurrence of an accident.

[0219] The vehicle also transmits specific commands to the dispenser to control fuel supply procedures, such as starting and stopping fuel supply. At this time, the vehicle uses UDP with DTLS for communication to support black channel communication. Black channel communication refers to communication that applies the black channel principle, in which secure communication must be guaranteed despite the output characteristics of a communication channel that has unprotected attributes or attributes not related to the application.

[0220] To explain the monitoring and control procedure in more detail using an example, as shown in FIG. 16, a vehicle including an FCEV transmits a message to a dispenser to start fueling control (S1610), and in response, the dispenser transmits a message including confirmation information (e.g., OK) to the vehicle (S1620).

[0221] In addition, the vehicle transmits a message including information about its fueling loop (e.g., x, y, z) to the dispenser (S1630), and the dispenser provides the vehicle with a message including information about its fueling loop (e.g., a, b, c) corresponding to the vehicle's fueling loop (S1640).

[0222] The vehicle also transmits a fueling control request message to the dispenser, which includes information to slow down fueling or reduce the amount of fuel supplied (S1660), and the dispenser transmits a response message to the vehicle, which includes information indicating a decrease in the fueling status (e.g., slowing) (S1670).

[0223] In addition, the vehicle transmits a fuel supply control request message to the dispenser requesting the suspension of fuel supply (S1680), and the dispenser transmits a fuel supply status response message to the vehicle including information indicating whether fuel supply is being suspended or has been suspended (stopping / stopped) (S1690).

[0224] Thus, in a monitoring and control procedure, the vehicle and dispenser continuously or periodically exchange parameters related to the fueling state: the vehicle communicates current tank temperature, current tank pressure, etc. to the dispenser, and the dispenser provides the vehicle with parameters related to fueling start, stop, ramping up, ramping down, current injection pressure, subsequent fueling schedule, etc.

[0225] A control-related request message transmitted from a vehicle to a dispenser includes information and parameters for starting, pausing, resuming, terminating, etc. fuel supply. A reporting-related message transmitted from a vehicle to a dispenser includes information and parameters for the current tank temperature, current tank pressure, etc.

[0226] Messages related to reporting transmitted from the dispenser to the vehicle include information and parameters regarding status information, current ambient temperature, current pressure ramp rate (PRR [Mbar / min]), delivery fuel flow rate (deliver fuel flow rate [g / sec]), current fuel delivery temperature, pre-cooling temperature, current fuel delivery pressure, whether full-fill is in use, whether cooling dispenser is in use, whether fallback is in use, reason for refueling stop, current amount of hydrogen supplied, etc.

[0227] The message related to the target parameter update transmitted from the dispenser to the vehicle includes information and parameters regarding the target final tank pressure, target final tank temperature, target average fuel delivery rate (APR), target state of charge (SOC), current state of charge (SOC), estimated remaining duration, etc.

[0228] On the other hand, when TCP is used in the above-mentioned monitoring and control procedure, if the safety check-in response message or the safety check-in step according to the fuel supply protocol is omitted, the vehicle transmits a fueling loop request message to the dispenser within the message sequence setting time after receiving the fueling parameter negotiation response message from the dispenser. The request message and response message related to the fueling loop are transmitted using a DTLS message.

[0229] After hydrogen fueling is completed through the above-described monitoring and control procedures, the vehicle, including the FCEV, and the dispenser verify that all safety conditions are met through a safety check-out use case before the session is terminated and the nozzle is separated from the vehicle. While this safety check-out step is optional, it is preferable to define a dedicated safety inspection procedure in the fueling protocol to ensure the desired safety level in a precise and explicit manner.

[0230] FIG. 17 is a flow chart illustrating the safety check-out procedure employed in the hydrogen filling communication two-way process according to one embodiment of the present invention.

[0231] Vehicles, including FCEVs, and dispensers go through a safety checkout procedure to ensure that all necessary safety conditions are met before the dispenser nozzle is separated from the outlet. In other words, the vehicle and dispenser ensure that it is absolutely safe for a user or worker to separate the nozzle from the vehicle after fueling is complete.

[0232] For example, after the vehicle receives a fuel supply loop response message from the dispenser with the "result" set to "OK," the "status" set to "finished," or the prefix "stopped," if the hydrogen filling protocol supports safety checkout, the vehicle begins safety checkout and transmits a safety checkout request message to the dispenser within the message sequence setting time to perform the safety checkout procedure.

[0233] The vehicle and dispenser will repeatedly report their status to each other until all safety checks are confirmed. If the hydrogen filling communication two-way process does not require such safety confirmation at the end, the use case for safety checkout is omitted.

[0234] To explain the above-mentioned safety checkout procedure in more detail, for example, as shown in Figure 17, the vehicle transmits a message to the dispenser containing information on the coupler check result (e.g., OK) (S1710), and the dispenser transmits a message to the vehicle containing information indicating that the coupler check is in progress (e.g., Ongoing) (S1730).

[0235] The vehicle again transmits a message including coupler inspection result information (eg, OK) to the dispenser (S1750), and the dispenser transmits a message including coupler inspection completion information (eg, Done) to the vehicle (S1770).

[0236] Once it is confirmed that the above-mentioned coupler inspection completion information has been completed normally, the nozzle of the dispenser is separated from the receptacle of the vehicle by the user or worker.

[0237] In the safety checkout procedure described above, the report message transmitted from the dispenser to the vehicle includes information and parameters regarding the coupler unlock status. The coupler unlock status information includes information regarding locked, unlocked, icing, problem, etc.

[0238] When fuel supply is completed according to the hydrogen filling protocol described above and the nozzle is safely separated, or when a safe and non-critical issue occurs during another use case, the termination use case (UC9) is executed.

[0239] FIG. 18 is a flow chart illustrating the termination procedure employed in the hydrogen filling communication two-way process according to one embodiment of the present invention.

[0240] The termination procedure is the final stage of fuel supply, and vehicles including FCEVs and dispensers exchange information on fuel supply results, including fuel supply performance and methods, and / or information on the reasons for unexpected interruptions to fuel supply, completing all procedures for hydrogen filling. The termination use case is also configured to handle work related to safety and non-critical issues if they occur.

[0241] For example, after the vehicle receives a safety checkout response message from the dispenser with the "result" set to "DONE" or a fuel supply loop response message with the "status" set to "finished" or prefixed with "stopped," the vehicle transmits a termination request message to the dispenser to perform the termination procedure.

[0242] To explain the termination procedure in more detail, for example, as shown in Figure 18, a vehicle including an FCEV transmits a message to a dispenser inquiring about how much fuel has been supplied (S1810). In response to the FCEV's inquiry message, the dispenser transmits a response message to the vehicle including information (e.g., X gram) about the amount of hydrogen supplied (S1830).

[0243] In addition, the vehicle transmits a confirmation request message for the completion of fuel supply to the dispenser (S1850), and the dispenser transmits a goodbye message to the vehicle as a response message to the confirmation request message (S1870).

[0244] After the fuel supply is completed and the safety check is confirmed, the vehicle and the dispenser exchange at least some bookkeeping information for the hydrogen filling session in a closing procedure. The vehicle and the dispenser exchange summary information for the hydrogen filling session before completing the closing procedure.

[0245] Book-keeping information includes all hydrogen fueling related information that is recorded in the vehicle and dispenser according to established rules and policies across all fueling sessions and prior to completing the termination procedure for Use Case 9 (UC9).

[0246] The ledger information or summary information includes information on how much fuel has been supplied, what kind of report has been created, etc. In addition, the report message transmitted from the vehicle to the dispenser includes information and parameters on the current tank temperature and current tank pressure, and the report message transmitted from the dispenser to the vehicle includes information on the final state of charge (SOC), the final average fueling rate (APR), the final measured tank pressure, the actual fuel supply time, the amount of hydrogen actually supplied, etc.

[0247] Once all necessary information for the fueling session has been saved, the fueling session is completely terminated.

[0248] Table 8 below shows examples of communication data for some of the use cases (UC5 to UC9) described above.

[0249] [Table 8]

[0250] On the other hand, the error handling use case (UC10) is a function block for handling a situation in which a safe, non-fatal error occurs by terminating the fuel supply procedure as in the normal termination or by suddenly interrupting communication.

[0251] FIG. 19 is a flow chart illustrating the error handling procedure employed in the hydrogen filling communication two-way process according to one embodiment of the present invention.

[0252] The error handling procedures define error conditions associated with the fueling protocol, provide detection criteria, and, if detected, include response procedures including notification, termination procedures, and fallback mechanisms.

[0253] 19, the error handling procedure is applied when a safe, non-fatal error occurs and further communication is not possible. That is, vehicles including FCEVs and dispensers use the error handling procedure to handle the occurrence of a non-safe, fatal error at any time during fuel supply. In other words, the vehicle and dispenser immediately stop fuel supply, pause the previously active use case, and then move to the end use case (UC9).

[0254] If the vehicle detects a non-safety fatal error event (S1910), the vehicle notifies the dispenser of the reason for termination via a terminate request (TerminateReq) message (S1930) and terminates the current fuel supply session and communication session (S1950). The dispenser responds to the terminate request message by terminating the current communication session (S1970). If additional communication is not possible, the current session is terminated without additional notification.

[0255] Additionally, if a safety non-critical error is detected in the vehicle and the communication channel continues to operate, the vehicle sends a TerminateReq message to the dispenser with "action" set to "stop" and "reason" set to an appropriate reason or reason code, such as a message being corrupted.

[0256] The above-mentioned termination request message is transmitted in error situations of safe and non-fatal communication errors, system errors, and qualitative errors, except when recovery is not possible.

[0257] That is, for successful fuel delivery, communications must exhibit behavior expected by the protocol, and fuel delivery behavior must be within the acceptable range of the fuel delivery protocol. However, in practice, a variety of abnormal events occur. Some of these errors are minor and easily handled, while others cannot be recovered and prevent fuel delivery from proceeding. Therefore, the error handling procedure defines safe, non-critical error conditions and provides example error conditions and possible responses.

[0258] Examples of communication errors include communication interruptions, inability to recognize received data due to encoding or syntax errors, or received data that is within an unacceptable range. System errors include cases where a dispenser or vehicle independently detects a significant system error. Qualitative errors include cases where the quality of communication performance does not meet the required standards, or where the quality of data completeness or accuracy does not meet the required standards.

[0259] The hydrogen filling communication two-way process of this embodiment performs the following specific error handling procedures (1) to (4) for the above-mentioned error conditions.

[0260] (1) If a safe, non-fatal error occurs and further communication is not possible, the vehicle and dispenser will immediately stop fueling but will take safe measures to stop communication and end the session.

[0261] (2) If a safe, non-fatal error occurs that interrupts fuel delivery and prevents fuel delivery from being completed, the fuel delivery protocol defines a fallback mechanism, for example, by defining a non-communicating fuel delivery method.

[0262] (3) If a safe, non-critical error is detected in the vehicle and the communication channel is still active, the vehicle transmits a termination request message to the dispenser with the “action” set to “stop” and the “reason” set to the appropriate reason code.

[0263] (4) If a safe, non-critical error is detected by the dispenser and the communication channel is still active, the dispenser first immediately stops fuel delivery and transmits a termination request message to the vehicle with “Action” set to “Abort” and “Reason” set to the appropriate reason or reason code.

[0264] As described above, the hydrogen filling communication two-way process, including the fuel supply protocol, defines error conditions associated with the fuel supply protocol, provides detection criteria, and performs error handling procedures, including notification, termination procedures, and fallback mechanisms, if an error is detected by the detection criteria.

[0265] On the other hand, if a safety-critical problem occurs during fuel supply in a hydrogen filling system, an urgent response is required.

[0266] FIG. 20 is a flow chart illustrating the emergency handling procedures employed in the hydrogen filling communication two-way process according to one embodiment of the present invention.

[0267] Emergency handling procedures define safety-critical conditions that require emergency response during fuel filling and include response procedures to prevent safety-critical incidents.

[0268] For safe fuel delivery, communications must exhibit the behavior expected by the protocol, and fuel delivery operations must be within the safe limits of the fuel delivery protocol. However, problems may occur during fuel delivery, causing the fuel delivery system (or hydrogen filling system) to reach a critical state that must be avoided at all costs. Therefore, emergency handling procedures define safe and important emergency conditions and possible responses to emergency conditions, and provide critical cases that must be considered.

[0269] The fueling protocol defines the emergency conditions associated with the protocol, provides sensing criteria and performance requirements, and prescribes response procedures to ensure harmful situations are not entered into.

[0270] 20, when a vehicle, including an FCEV, detects a high pressure exceeding a preset reference value during a hydrogen filling procedure, the vehicle transmits a first emergency stop request message including information requesting the suspension of fuel supply due to the high pressure (e.g., Emg: Stop (high pressure)) to the dispenser (S2010). The dispenser transmits a response message including information indicating that the emergency suspension of fuel supply is being processed in response to the first emergency stop request message (e.g., Emg: Stopping) to the vehicle (S2020).

[0271] Then, immediately after receiving the response message or after a preset time has elapsed, the vehicle again transmits a first emergency stop request message to the dispenser (S2030). The dispenser transmits a response message to the vehicle including information indicating that fuel supply has been urgently stopped in response to the first emergency stop request message (e.g., Emg:Stopped) (S2040).

[0272] Meanwhile, if the dispenser detects a hydrogen fuel leak during the hydrogen filling procedure, the dispenser transmits a second emergency stop request message including information (e.g., Emg:Stopping(leaking)) notifying the vehicle that it is processing to stop fuel supply due to the leak (S2060). The vehicle transmits a response message to the dispenser including information (e.g., Emg:Confirmed) notifying the vehicle that it has confirmed the second emergency stop request message (S2070).

[0273] The dispenser then transmits a third emergency stop notification message to the vehicle, including information indicating that the fuel supply stop due to leakage has been processed (e.g., Emg:Stopped(leaking)) (S2080). The vehicle then transmits a response message to the dispenser, including information indicating that the third emergency stop notification message has been confirmed (e.g., Emg:Confirmed) (S2090).

[0274] According to the above-mentioned configuration, when a serious situation affecting safety is detected in a vehicle, including an FCEV, or a dispenser, the necessary measures are immediately taken to prevent a disaster from occurring, and if possible, an emergency notification message containing information about the situation is sent to the other party and communication is cut off.

[0275] When an emergency notification message is received, the vehicle or dispenser immediately responds by taking the action indicated in the emergency notification message and terminates the communication without undue delay. The emergency notification message includes a header and a message body linked to the header, where the header includes information indicating that the message is an emergency notification, and the message includes values, information, or parameters for the class, type, and action for the emergency notification.

[0276] The emergency notification message described above is transmitted in a TLS or DTLS message depending on the technology used for communication.

[0277] FIG. 21 is a schematic block diagram of an apparatus (simply "hydrogen filling apparatus") utilizing a hydrogen filling communication two-way process according to yet another embodiment of the present invention. FIG. 22 is a block diagram illustrating software modules employed in the hydrogen filling apparatus of FIG. 21.

[0278] Referring to FIG. 21, the hydrogen filling device 3000 is implemented in the form of a computing device or computing system including a processor 3100 electronically connected to a memory 3200.

[0279] The hydrogen filling device 3000 may be a device that provides hydrogen filling services, or a hydrogen filling control device or hydrogen filling communication device that is provided in such a device. Similarly, the hydrogen filling device 3000 may be a device that receives hydrogen filling services, or a hydrogen filling control device or hydrogen filling communication device that is provided in such a device.

[0280] The hydrogen filling device 3000 also includes a processor 3100, a memory 3200, a transceiver 3300, an input interface device 3400, an output interface device 3500, a storage device 3600, and a bus 3700. The components included in the hydrogen filling device 3000 are connected to each other by the bus 3700 to perform communication.

[0281] The processor 3100 may include a central processing unit (CPU), a graphics processing unit (GPU), or a special purpose processor configured to perform methods according to embodiments of the present invention.

[0282] Each of the memory 3200 and the storage device 3600 is composed of at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory 3200 is composed of at least one of a read only memory (ROM) and a random access memory (RAM).

[0283] The hydrogen filling apparatus 3000 executes at least some of the steps of the hydrogen filling communication two-way process, fuel supply protocol, fuel supply method, hydrogen filling protocol, or hydrogen filling method of the present embodiment described above. To this end, the hydrogen filling apparatus 3000 includes at least one processor 3100 and a memory 3200 that stores instructions that instruct the at least one processor 3100 to perform at least one step. At least some steps of the above-described two-way process or method are executed by the at least one processor 3100 loading and executing instructions from the memory 3200.

[0284] 22, the hydrogen filling device 3000 includes additional function blocks (3110-3180) in addition to the function blocks (UC1-UC11) described with reference to Fig. 4. These function blocks (3110-3180) are mounted on the hydrogen filling device 3000 or at least one processor 3100 of the hydrogen filling device 3000.

[0285] The above-mentioned functional blocks (3110-3180) include a first functional block 3110 for version negotiation, a second functional block 3120 for session allocation, a third functional block 3130 for service negotiation, a fourth functional block 3140 for settlement negotiation, a fifth functional block 3150 for authentication, a sixth functional block 3160 for fuel supply parameter exchange, a seventh functional block 3170 for fuel supply, and an eighth functional block 3180 for abort / pause.

[0286] The first functional block 3110 checks and compares the versions of the communication protocols used in all fueling protocols when performing a handshake. The first functional block 3110 also checks the TLS version, etc.

[0287] The second function block 3120 assigns IP addresses, IPv6 addresses, session identifiers, etc. depending on the vehicle or dispenser.

[0288] The third functional block 3130 negotiates the services to be applied to the hydrogen electric vehicle based on price, user convenience, etc. when there are differences in service items such as filling fees depending on the region, time period, or service provider when filling hydrogen.

[0289] The fourth function block 3140 determines the payment method for hydrogen filling and processes the payment process.

[0290] The fifth function block 3150 processes at least one of user authentication, vehicle authentication, dispenser authentication, and hydrogen filling station authentication. The fifth function block 3150 corresponds to at least a portion of the function blocks of the discovery and pairing use case (UC1).

[0291] The sixth function block 3160 corresponds to at least a portion of the function blocks of the Fueling Parameter Negotiation Use Case (UC5).

[0292] The seventh function block 3170 is a function for monitoring and controlling fuel supply and corresponds to at least a part of the Monitor and Control use case (UC7), and corresponds to at least a part of a combination of the Secure Check-in use case (UC6), the Monitor and Control use case (UC7), the Secure Check-out use case (UC8), and the Termination use case (UC9).

[0293] The eighth function block 3180 is for stopping or temporarily suspending fuel supply, communication, etc. during error processing or emergency processing, and corresponds to at least a part of the combination of the error processing use case (UC10) and the emergency processing use case (UC11).

[0294] The hydrogen filling apparatus 3000 described above also includes various types of computing devices that are mounted on vehicles or dispensers. Examples of such computing devices include a communication-enabled desktop computer, a laptop computer, a notebook computer, a smartphone, a tablet PC, a mobile phone, a smart watch, smart glasses, an e-book reader, a portable multimedia player (PMP), a portable game console, a navigation device, a digital camera, a digital multimedia broadcasting (DMB) player, a digital audio recorder, a digital audio player, a digital video recorder, a digital video player, a personal digital assistant (PDA), and the like.

[0295] Meanwhile, in many of the above-described embodiments, the vehicle's communication protocol and parameters are primarily transmitted from the vehicle to the dispenser, but the present invention is not limited to such a configuration, and it goes without saying that the present invention may be configured to transmit the dispenser's communication protocol and parameters from the dispenser to the vehicle first. In this case, it is obvious that the present invention has substantially the same features as the embodiments, except that the sender becomes the receiver and the receiver becomes the sender.

[0296] The operations of the methods according to the embodiments of the present invention may be embodied as a computer-readable program or code stored in a computer-readable recording medium. The computer-readable recording medium includes all types of storage devices that store information readable by a computer system. The computer-readable recording medium may also be distributed among computer systems connected to a network, so that the computer-readable program or code is stored and executed in a distributed manner.

[0297] Additionally, computer-readable recording media include hardware devices specially configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. Program instructions include not only machine language code, such as produced by a compiler, but also high-level language code that is executed by a computer using an interpreter, etc.

[0298] Although some aspects of the present invention have been described in the context of an apparatus, they may also be described in terms of a corresponding method, where a block or apparatus corresponds to a method step or feature of a method step. Similarly, aspects described in the context of a method may also be described in terms of a corresponding block or item or feature of a corresponding apparatus. Some or all of the method steps may be performed by (or using) a hardware device, such as a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, at least one or more of the most important method steps are performed by such a device.

[0299] In some embodiments, a programmable logic device (e.g., a field programmable gate array) may be used to perform some or all of the functions of the methods described herein. In some embodiments, the field programmable gate array may operate in conjunction with a microprocessor to perform one of the methods described herein. In general, the methods are preferably performed by some hardware device.

[0300] Although the present invention has been described above with reference to preferred embodiments, it will be understood that those skilled in the art can make various modifications and changes to the present invention without departing from the spirit and scope of the present invention as set forth in the claims. [Explanation of symbols]

[0301] 100 Hydrogen Electric Vehicles 110, 210 First and second electronic control devices 120 Vehicle Systems 130 Vehicle Tank 150 receptacles 160, 260 1st and 2nd sensors 200 Dispenser 220 Filling Station System 230 Hydrogen Tank 240 Station Box 250 nozzles 510, 530, 540 1st, 3rd, 4th Protocol 520 IPv6 (Internet Protocol Version 6) Protocol 550 JSON-based session protocol 560 JSON(javascript object notation) 570 Hydrogen Refueling Related Fueling Protocols (FP) 900, 910, 920, 930 UCDC Level 0-3 (UCDC-0-3) 3000 Hydrogen Filling Equipment 3100 processor 3110~3180 1st~8th function blocks 3200 memory 3300 Transmitter / Receiver 3400 Input Interface Device 3500 Output Interface Unit 3600 storage device 3700 Bus< / ok> < / ok>

Claims

1. 1. A hydrogen filling communication two-way process performed by a vehicle electronic control unit, comprising: transmitting a request message to the dispenser, the request message including a protocol list for a communication protocol to be used in a fueling session of the hydrogen filling; receiving a response message from the dispenser, the response message including information on a common protocol selected by the dispenser and best suited for the vehicle, the common protocol being supported by both the vehicle and the dispenser; A hydrogen filling communication two-way process, wherein the common protocol allows the vehicle and the dispenser to reach an agreement on a communication protocol to be used for fueling communication during the hydrogen filling.

2. 2. The hydrogen filling communication two-way process according to claim 1, wherein the protocol list is a prioritized list of communication protocols supported by the vehicle.

3. 2. The hydrogen filling communication two-way process of claim 1, wherein the type of device that supports the common protocol corresponds to the type of device to which the dispenser falls back for backward compatibility.

4. 2. The hydrogen filling communication two-way process of claim 1, further comprising negotiating with the dispenser a fueling protocol to be used for fueling the vehicle with hydrogen.

5. 5. The hydrogen filling communication two-way process of claim 4, further comprising the step of exchanging detailed parameters with the dispenser necessary to implement the fueling protocol.

6. The hydrogen filling communication two-way process of claim 5, further comprising a discovery and pairing step of identifying incompatibility with the communication module of the dispenser responsible for controlling the receptacle physically connected to the nozzle of the dispenser, searching for the dispenser using a search mechanism provided in the data link and physical layers, and beginning communication with the dispenser.

7. The hydrogen filling communication two-way process of claim 6, further comprising the steps of establishing a TCP connection with the dispenser after connecting the data link and physical layer, performing a TLS handshake with the dispenser to authenticate, and exchanging keys with the dispenser to establish a secure communication channel.

8. The hydrogen filling communication two-way process of claim 5, further comprising a step of checking safety conditions to determine whether the hydrogen filling is safe after exchanging the detailed parameters or filling parameters to consider compatibility with the dispenser.

9. 6. The hydrogen filling communication two-way process of claim 5, further comprising a monitoring and control step of exchanging measurement data with the dispenser, confirming the filling status, and controlling the filling procedure when the hydrogen filling is performed according to a preselected filling protocol using the detailed parameters.

10. 10. The hydrogen filling communication two-way process of claim 1, further comprising the step of verifying that necessary safety conditions have been met before separating the dispenser nozzle from the vehicle receptacle.

11. 8. The hydrogen filling communication two-way process of claim 7, further comprising exchanging information regarding the hydrogen filling result of the vehicle and accounting information regarding the hydrogen filling session with the dispenser.

12. 2. The hydrogen filling communication bidirectional process of claim 1, further comprising a step of processing errors that occur during the process of determining the communication protocol, the process of proceeding with hydrogen filling of the vehicle, or the process before completing and terminating the hydrogen filling.

13. 2. The hydrogen filling communication bidirectional process of claim 1, further comprising the step of performing emergency handling of a safety-critical problem occurring during the process of determining the communication protocol, the process of proceeding with hydrogen filling of the vehicle, or the process of completing and prior to the end of the hydrogen filling.

14. 1. A hydrogen filling communication two-way process performed by a vehicle electronic control unit, comprising: a discovery and pairing step of identifying incompatibility with a communication module of a dispenser that controls a receptacle physically connected to a nozzle of the dispenser that supplies hydrogen fuel to the vehicle, and searching for the dispenser by a search mechanism provided in the data link and physical layers to start communication with the dispenser; establishing a TCP connection with the dispenser after connecting the data link and physical layer, performing a TLS handshake with the dispenser to authenticate, and exchanging keys with the dispenser to establish a secure communication channel; transmitting a request message to the dispenser, the request message including a protocol list for a communication protocol to be used in a fueling session for filling hydrogen into the vehicle; receiving a response message from the dispenser, the response message including information on a common protocol selected by the dispenser and best suited for the vehicle, the common protocol being supported by both the vehicle and the dispenser; negotiating with the dispenser a fueling protocol to be used in the communication protocol; exchanging with the dispenser detailed parameters necessary to implement the filling protocol; After exchanging the detailed parameters or filling parameters and considering compatibility with the dispenser, checking safety conditions to determine whether the hydrogen filling is safe; a monitoring and control step of exchanging measurement data with the dispenser to confirm the filling status and control the filling procedure when the hydrogen filling is performed according to a filling protocol preselected using the detailed parameters; verifying that necessary safety conditions have been met before separating the dispenser nozzle from the vehicle receptacle; exchanging information regarding the hydrogen filling result of the vehicle and accounting information regarding the hydrogen filling session with the dispenser; a step of processing an error occurring during the process of determining the communication protocol, the process of filling the vehicle with hydrogen, or the process before completing and terminating the hydrogen filling; and performing emergency handling of a safety-critical problem occurring during the process of determining the communication protocol, the process of filling the vehicle with hydrogen, or the process of completing and before the completion of the hydrogen filling. A hydrogen filling communication two-way process, wherein the common protocol allows the vehicle and the dispenser to reach an agreement on a communication protocol to be used for fueling communication during the hydrogen filling.

15. A hydrogen fueling device for hydrogen-fueled mobility, comprising: a memory for storing at least one instruction; a processor for executing the at least one instruction; The processor, in response to the at least one instruction, Transmitting a request message including a protocol list for a communication protocol used in a fueling session of hydrogen filling to the dispenser; receiving a response message from the dispenser, the response message including information regarding a common protocol supported by both the vehicle and the dispenser, the common protocol being selected by the dispenser and optimal for the vehicle to be supplied with hydrogen fuel by the dispenser; The hydrogen filling device is configured to reach an agreement with the dispenser on a communication protocol used for fueling communication during hydrogen filling using the common protocol.

16. 16. The hydrogen filling device according to claim 15, wherein the protocol list is a list in which priorities are assigned to communication protocols supported by the vehicle.

17. 16. The hydrogen filling device of claim 15, wherein the type of device that supports the common protocol corresponds to the type of device to which the dispenser falls back for backward compatibility.

18. 16. The hydrogen filling device of claim 15, wherein the processor further performs a step of negotiating with the dispenser a fueling protocol to be used for fueling the vehicle with hydrogen.

19. 20. The hydrogen filling device of claim 18, wherein the processor further performs the step of exchanging detailed parameters required to execute the fueling protocol with the dispenser.

20. 16. The hydrogen filling device of claim 15, wherein the processor further performs a process of processing an error or emergency handling of a safety-critical problem that occurs during the process of determining the communication protocol, the process of proceeding with hydrogen filling of the vehicle, or the process of completing and before the hydrogen filling is terminated.

Images