Method for parameter exchange in communication for hydrogen fuel fuel and device using the method

Abstract

A method according to an embodiment of the present invention comprises the steps of: transmitting a first parameter to a communication entity associated with a dispenser, the first parameter comprising one or more of: at least one first hydrogen fueling method compatibility supported by a mobile device, and at least one first physical characteristic; and receive, from a communication entity associated with the dispenser, a response message including a second parameter including one or more of at least one second hydrogen fueling method compatibility supported by the dispenser, at least one second physical characteristic, and a fueling target.

Description

Technical Field

[0001] The present disclosure relates to communication technology for hydrogen fueling of hydrogen fueled mobility, and more specifically to a hydrogen fueling process suitable for enhancing the safety, compatibility, efficiency and reliability of hydrogen fueling, a communication parameter exchange method for the hydrogen fueling process, and an apparatus, device, and / or system for implementing the method. Background Art

[0002] The statements in this section merely provide background information related to the present embodiments and may not constitute prior art.

[0003] A hydrogen vehicle or hydrogen electric vehicle refers to a vehicle that is powered by electricity generated by the reaction of high-pressure hydrogen stored in the vehicle with oxygen in the air and produces little pollution. Most hydrogen electric vehicles are powered by electricity generated by a fuel cell system that uses hydrogen as an energy source. Hydrogen electric vehicles not only emit pure water (H2O) in the process of generating electricity, but also emit a lot of pollutants. 2 O) vapor, and remove ultrafine dust in the air while driving, and thus attract attention as a future environmentally friendly mobile device. Since the fuel (i.e., hydrogen) is abundant on the earth and the energy production process is environmentally friendly, hydrogen electric vehicles are focused on as a technology with the potential for cross-industry utilization.

[0004] Hydrogen fuel mobile devices refer to mobile devices that use hydrogen as an energy source or use hydrogen as a fuel to generate electrical energy to drive an electric motor by electrical energy. In addition to the above-mentioned hydrogen electric vehicles, hydrogen fuel mobile devices may include aerial mobile devices that use hydrogen as a fuel to generate electrical energy and are driven by electrical energy, as well as industrial trucks, trains, ships, and airplanes.

[0005] Hydrogen electric vehicles generate electricity by supplying high-pressure hydrogen safely stored in a hydrogen fuel storage tank and oxygen introduced through an air supply system to a fuel cell stack, and causing an electrochemical reaction between hydrogen and oxygen. The electricity generated in the fuel cell stack is converted into kinetic energy by an electric motor to drive the hydrogen electric vehicle, and the running hydrogen electric vehicle discharges only pure water vapor through an exhaust port.

[0006] A hydrogen fueled car in addition to a hydrogen electric vehicle is also a vehicle that uses hydrogen as fuel. A hydrogen fueled car is driven by an electric motor that rotates by the heat generated by the direct combustion of hydrogen in the engine. The method for refueling / supplying hydrogen to a hydrogen fueled car is not much different from the method for refueling / supplying hydrogen to a hydrogen electric vehicle.

[0007] The control scheme for refueling or supplying hydrogen to hydrogen fuel mobile equipment is intended to control the hydrogen refueling / supply so that the temperature and pressure of the compressed hydrogen storage system (CHSS) on the fuel cell side are maintained below a certain temperature limit and pressure limit to ensure safety.

[0008] The hydrogen fuel filling / supply process, control scheme and its protocol in conventional hydrogen electric vehicles have been specified before the wired / wireless communication or computing technology for control has become mature, and therefore do not utilize the most advanced information and communication technology (ICT) to their full extent. Therefore, the conventional hydrogen fuel filling / supply subsystem in hydrogen electric vehicles is inefficient, slow, and not suitable for large-scale hydrogen fuel filling.

[0009] In particular, regarding hydrogen fuel filling communication, most hydrogen fuel filling control devices use a one-way infrared communication device for wireless communication, and thus still have the limitations and vulnerabilities of one-way communication. Summary of the invention

[0010] Technical issues

[0011] In order to solve the above problems, an exemplary embodiment provides a hydrogen fueling process, a communication parameter exchange method for the hydrogen fueling process, a communication protocol for the fueling protocol of the process, and / or a device for implementing the method, the hydrogen fueling process is used to overcome the limitations and vulnerabilities of traditional one-way communication in the hydrogen fueling process of hydrogen fuel mobile equipment, and enhance the safety, compatibility, efficiency and reliability of hydrogen fueling. An exemplary embodiment provides a two-way communication process for hydrogen fueling, a communication protocol negotiation process considering two-way / one-way communication, and a device for implementing the process, the two-way communication process provides rules and criteria, these rules and criteria enable a mobile device including a fuel cell electric vehicle (FCEV) and a dispenser that supplies hydrogen fuel to the mobile device to fall back to another hydrogen fueling protocol and a communication protocol suitable for the hydrogen fueling protocol, so that the mobile device and the dispenser select a protocol that maximizes interoperability instead of selecting their most preferred fueling protocol and communication protocol.

[0012] Exemplary embodiments provide a two-way communication process for hydrogen fueling, a communication protocol negotiation process considering two-way / one-way communication, and an apparatus for implementing the process, which can control a mobile device and a dispenser to determine an advanced communication medium to effectively achieve a hydrogen fueling goal.

[0013] Technical Solution

[0014] According to one aspect of an exemplary embodiment, a communication parameter exchange method for hydrogen fuel refueling performed by a communication control device of a hydrogen fuel mobile device includes: sending a first parameter to a communication entity associated with a dispenser, the first parameter including one or more of the following items: at least one first hydrogen fuel refueling method compatibility supported by the hydrogen fuel mobile device, and / or at least one first physical characteristic; and receiving a response message including a second parameter from the communication entity associated with the dispenser, the second parameter including one or more of the following items: at least one second hydrogen fuel refueling method compatibility supported by the dispenser, at least one second physical characteristic, and / or a fueling target.

[0015] The first parameter may also include a first monitoring parameter supported by the hydrogen fuel mobile device. The second parameter may also include a second monitoring parameter supported by the dispenser.

[0016] In the communication parameter exchange method for a hydrogen fueling process according to an exemplary embodiment of the present disclosure, the parameter exchange process may be terminated based on a confirmation message (eg, an OK message) included in a response message.

[0017] In the communication parameter exchange method for a hydrogen fueling process according to an exemplary embodiment of the present disclosure, one or more first hydrogen fueling method compatibilities may include one or more of a pressure level and / or a CHSS category of a hydrogen fuel mobile equipment.

[0018] In the communication parameter exchange method for a hydrogen fueling process according to an exemplary embodiment of the present disclosure, at least one first physical characteristic may include one or more of a maximum allowable CHSS pressure, a maximum allowable CHSS temperature, a maximum allowable flow rate, and / or a CHSS volume.

[0019] In the communication parameter exchange method for a hydrogen fuel filling process according to an exemplary embodiment of the present disclosure, the first parameter further includes a parameter related to the acceptability of the hydrogen fuel mobile equipment.

[0020] In the communication parameter exchange method for a hydrogen fueling process according to an exemplary embodiment of the present disclosure, the first monitoring parameter may include one or more of a current CHSS pressure and / or a current CHSS temperature.

[0021] In the communication parameter exchange method for a hydrogen fueling process according to an exemplary embodiment of the present disclosure, at least one second hydrogen fueling method compatibility may include one or more of a fueling delivery temperature of a dispenser and / or a selected fueling table of a dispenser. The selected fueling table may include a sequence table of a selected fueling protocol and may be included in the OK message shown in operation S1330.

[0022] In the communication parameter exchange method for a hydrogen fueling process according to an exemplary embodiment of the present disclosure, at least one second physical characteristic may include one or more of a maximum fuel delivery pressure, a maximum fuel delivery temperature, a minimum fuel delivery temperature, and / or a maximum fuel delivery flow rate.

[0023] In a communication parameter exchange method for a hydrogen fueling process according to an exemplary embodiment of the present disclosure, the fueling target may include one or more of a target SoC, a target final CHSS pressure, a target final CHSS temperature, a target average fueling rate (APR, Average Fueling Rate) and / or an expected fueling duration.

[0024] In the communication parameter exchange method for a hydrogen fueling process according to an exemplary embodiment of the present disclosure, the second parameter may further include a parameter related to the acceptability of the dispenser.

[0025] In the communication parameter exchange method for a hydrogen fueling process according to an exemplary embodiment of the present disclosure, the second monitoring parameter may include one or more of a current fuel delivery temperature and / or an ambient temperature.

[0026] According to another aspect of the exemplary embodiment, a communication control device of a hydrogen fuel mobile device includes: a memory storing at least one program instruction; and a processor executing the at least one program instruction. When executing the at least one program instruction, the processor is caused and / or configured to: send a first parameter to a communication entity associated with a dispenser, the first parameter including one or more of the following items: at least one first hydrogen fuel filling method compatibility supported by the hydrogen fuel mobile device, and / or at least one first physical characteristic; and receive a response message including a second parameter from the communication entity associated with the dispenser, the second parameter including one or more of the following items: at least one second hydrogen fuel filling method compatibility supported by the dispenser, at least one second physical characteristic, and / or a fuel filling target.

[0027] In the communication control device of the hydrogen fuel mobile equipment according to the exemplary embodiment of the present disclosure, the first parameter may further include a first monitoring parameter supported by the hydrogen fuel mobile equipment, and the second parameter may further include a second monitoring parameter supported by the dispenser.

[0028] In the communication control device of the hydrogen fuel mobile equipment according to the exemplary embodiment of the present disclosure, the parameter exchange process may be terminated based on the confirmation message included in the response message.

[0029] In the communication control device of the hydrogen fuel mobile equipment according to the exemplary embodiment of the present disclosure, at least one first hydrogen fuel filling method compatibility may include one or more of a pressure level and / or a CHSS category of the hydrogen fuel mobile equipment.

[0030] In the communication control device of the hydrogen fuel mobile equipment according to the exemplary embodiment of the present disclosure, the at least one first physical characteristic may include one or more of a maximum allowable CHSS pressure, a maximum allowable CHSS temperature, a maximum allowable flow rate and / or a CHSS volume.

[0031] In the communication control device of the hydrogen fuel mobile equipment according to the exemplary embodiment of the present disclosure, at least one second hydrogen fueling method compatibility may include one or more of a fueling delivery temperature of the dispenser and / or a selected fueling table of the dispenser.

[0032] In the communication control device of the hydrogen fuel mobile equipment according to the exemplary embodiment of the present disclosure, the at least one second physical characteristic may include one or more of a maximum fuel delivery pressure, a maximum fuel delivery temperature, a minimum fuel delivery temperature and / or a maximum fuel delivery flow rate.

[0033] In the communication control device of the hydrogen fuel mobile equipment according to an exemplary embodiment of the present disclosure, the fueling target may include one or more of a target SoC, a target final CHSS pressure, a target final CHSS temperature, a target average fueling rate (APR), and / or an expected fueling duration.

[0034] Beneficial Effects

[0035] The communication parameter exchange method for the hydrogen fueling process and the device for implementing the method according to the present disclosure, that is, the hydrogen fueling controller or communication control device, and the communication protocol of the fueling protocol for the process, can overcome the limitations and vulnerabilities of traditional one-way communication in the hydrogen fueling process of hydrogen fuel mobile equipment (including fuel cell electric vehicles (FCEV) or hydrogen fuel engines), and enhance the safety, compatibility, efficiency and reliability of hydrogen fueling.

[0036] Exemplary embodiments of the present disclosure may provide a method for negotiating a communication protocol and exchanging communication parameters for hydrogen refueling and communication protocol fallback rules, in which the mobile device and the dispenser may select a hydrogen refueling protocol and a communication protocol required for the hydrogen refueling protocol based on a use case, while considering priorities based on the preferences of the mobile device or the dispenser, maximizing interoperability between the mobile device and the dispenser, and considering backward compatibility.

[0037] According to exemplary embodiments of the present disclosure, rules and guidelines required for communication protocol negotiation and communication parameter exchange may be provided, enabling mobile devices and dispensers to efficiently and collaboratively determine advanced communication media to effectively achieve hydrogen fueling goals. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 is a diagram of a hydrogen fueling system of a hydrogen electric vehicle (FCEV) suitable for applying a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure;

[0039] Figure 2 yes Figure 1 A partial enlarged view of the physical connection structure between the FCEV and the distributor in the hydrogen fuel filling system;

[0040] Figure 3 It is shown in Figure 1 A graph showing changes in the state of hydrogen fuel occurring during a hydrogen fuel filling process in a hydrogen fuel filling system;

[0041] Figure 4 A framework of functional blocks for executing a series of hydrogen fueling processes according to an exemplary embodiment of the present disclosure is shown, and the series of hydrogen fueling processes may employ a two-way communication process for hydrogen fueling;

[0042] Figure 5 An example of a communication stack related to a use case employed in a bidirectional communication process for hydrogen refueling based on the 7th layer of the Open Systems Interconnection reference model (OSI) according to an exemplary embodiment of the present disclosure is shown;

[0043] Figure 6 is a sequence diagram illustrating a pairing process of a discovery and pairing process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure;

[0044] Figure 7An example of backward compatibility that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure is shown;

[0045] Figure 8 is a table summarizing examples of backward compatibility applicable to a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure;

[0046] Fig. 9 shows a usage classification of communication data (UCDC) applicable in a two-way communication process for hydrogen fueling and backward compatibility in the usage classification of communication data according to an exemplary embodiment of the present disclosure;

[0047] Fig.10 is a sequence diagram showing an authorization process in a communication security process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure;

[0048] Fig.11 is a sequence diagram illustrating a communication protocol negotiation process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure;

[0049] Fig.12 is a sequence diagram illustrating a communication protocol negotiation process that may be employed in a two-way communication process for hydrogen fueling according to another embodiment of the present disclosure;

[0050] Fig.13 is a sequence diagram illustrating a fueling parameter exchange / negotiation process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure;

[0051] Fig.14 is a sequence diagram illustrating a fueling parameter exchange / negotiation process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure;

[0052] Fig.15 is a sequence diagram illustrating a safety check-in process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure;

[0053] Fig.16 is a sequence diagram illustrating a monitoring and control process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure;

[0054] Fig.17 is a sequence diagram illustrating a safety check-out process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure;

[0055] Fig.18 is a sequence diagram illustrating a termination process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure;

[0056] Fig.19 is a sequence diagram illustrating an error handling process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure;

[0057] Fig. 20 is a sequence diagram illustrating an emergency handling process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure;

[0058] Fig.21 is a schematic block diagram of an apparatus using a two-way communication process for hydrogen fueling (referred to as a "hydrogen fueling apparatus") according to another exemplary embodiment of the present disclosure;

[0059] Fig. 22 It shows that it can be Fig.21 A block diagram of software modules used in a hydrogen fuel filling device;

[0060] Fig.23 is a conceptual diagram illustrating a table disclosing parameters transferred from a mobile device side to a distributor side in a parameter exchange process according to an exemplary embodiment of the present disclosure; and

[0061] Fig.24 is a conceptual diagram illustrating a table disclosing parameters transferred from a distributor side to a mobile device side in a parameter exchange process according to an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0062] In order to more clearly understand the features and advantages of the present disclosure, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. However, it should be understood that the present disclosure is not limited to the specific embodiments disclosed herein, but includes all modifications, equivalents and replacements that fall within the spirit and scope of the present disclosure. In the accompanying drawings, similar or corresponding parts can be represented by the same or similar reference numerals.

[0063] Terms including ordinal numbers (such as "first" and "second") designated in this specification for explaining various components are used to distinguish components from other components, but are not intended to be limited to specific components. For example, a second component may be referred to as a first component, and, similarly, a first component may also be referred to as a second component without departing from the scope of the present disclosure. As used herein, the term "and / or" may include the presence of one or more associated listed items and any and all combinations of the listed items.

[0064] In the description of the exemplary embodiments of the present disclosure, “at least one of A and B” may refer to “at least one of A or B” or “at least one of a combination of one or more of A and B”. Furthermore, in the description of the exemplary embodiments of the present disclosure, “one or more of A and B” may refer to “one or more of A or B” or “one or more of a combination of one or more of A and B”.

[0065] When a component is referred to as being "connected" or "coupled" to another component, the component may be directly logically or physically connected or coupled to the other component or indirectly connected through an intervening object. In contrast, when a component is referred to as being "directly connected" or "directly coupled" to another component, it should be understood that there are no intervening objects between the components. Other words used to describe relationships between elements should be interpreted in a similar manner.

[0066] The terms used herein are used only for the purpose of describing specific exemplary embodiments and are not intended to limit the present disclosure. Unless the context clearly dictates otherwise, the singular also includes plural referents. Moreover, the expressions "comprises," "comprising," "constructed," and "configured" are used to refer to the presence of the described features, quantities, processing steps, operations, elements, or combinations of parts, but are not intended to exclude the presence or addition of another feature, quantity, processing step, operation, element, or part.

[0067] Unless otherwise defined, all terms (including technical or scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the present disclosure belongs. These terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning consistent with their meaning in the context of the relevant documents, and should not be interpreted as having an ideal or overly formal meaning unless explicitly defined in this application.

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

[0069] Hydrogen electric vehicles can generally include hydrogen fuel cell electric vehicles (FCEVs) using fuel cells and vehicles with internal combustion engines (ICEs) using hydrogen as fuel. Hydrogen electric vehicles can also be simply referred to as FCEVs.

[0070] Although the following describes an embodiment related to a hydrogen fuel cell vehicle in detail, an ICE-based hydrogen electric vehicle using hydrogen as fuel may be used in another embodiment of the present disclosure. In the following description, the hydrogen fuel filling protocol and / or the hydrogen fuel filling communication protocol are described with the hydrogen fuel cell vehicle as the center. However, the hydrogen fuel filling protocol and / or the hydrogen fuel filling communication protocol may also be applied to an ICE-based hydrogen electric vehicle according to another embodiment of the present disclosure.

[0071] The hydrogen fluid fuel may include gaseous hydrogen fuel or liquid hydrogen fuel.

[0072] “Compressed Hydrogen Storage System (CHSS)”: A device comprising at least one tank mounted on a vehicle to compress and store hydrogen.

[0073] “Pressure Relief Device (PRD)”: A device arranged in a CHSS and capable of isolating the stored hydrogen from other parts of the fuel filling system and the environment and discharging the hydrogen to the outside.

[0074] "Hydrogen refueling": the process of supplying high-pressure hydrogen from a dispenser at a hydrogen refueling station to a vehicle to accumulate hydrogen in a tank of the vehicle. Hydrogen refueling may also be referred to as "fueling" in terms of supplying hydrogen fuel to a hydrogen electric vehicle. That is, the terms "refueling," "hydrogen refueling," or "charging" as used herein may refer to supplying hydrogen fuel. For example, a refueling protocol may be referred to as a fuel supply protocol, a refueling session may be referred to as a fuel supply session, and a refueling method may be referred to as a hydrogen refueling method or a fuel supply method.

[0075] “Pressure Ramp Rate (PRR)”: The rate of increase of CHSS pressure and is measured in megapascals per minute (MPa / min).

[0076] “Average Pressure Ramp Rate (APRR)”: The average value of the pressure increase rate from the start to the end of hydrogen fueling.

[0077] "Pre-cooling": The process of cooling hydrogen in a hydrogen fueling station prior to fueling.

[0078] “Dispenser”: A component that supplies pre-cooled hydrogen to a CHSS. The dispenser may be disposed at a hydrogen fueling station to perform a hydrogen fueling operation between a storage tank of the hydrogen fueling station and a CHSS of a vehicle.

[0079] "Nozzle": A device that is connected to the hydrogen dispensing system of a hydrogen fueling station and that can be coupled to the receptacle of a hydrogen electric vehicle and dispense hydrogen fuel into the hydrogen electric vehicle.

[0080] “Fueling Session”: A communication session that occurs within the overall use case scope of Hydrogen Fueling.

[0081] Meanwhile, although embodiments related to hydrogen electric vehicles or fuel cell electric vehicles (FCEVs) are described in detail below, it is apparent to those skilled in the art that the inventive concepts of the present disclosure can be applied to various types of hydrogen fuel mobile devices. A hydrogen fuel mobile device refers to a mobile device that uses hydrogen as an energy source or uses hydrogen as a fuel to generate electrical energy to drive an electric motor by electrical energy. In addition to the above-mentioned hydrogen electric vehicles, hydrogen fuel mobile devices may include aerial mobile devices (Aerial Mobility) that use hydrogen as a fuel to generate electrical energy and are driven by electrical energy, as well as industrial trucks, trains, ships, and airplanes.

[0082] Furthermore, in addition to hydrogen fuel mobile equipment, the two-way communication process for hydrogen fueling of the present disclosure may be partially applied to buildings or facilities that use hydrogen as an energy source.

[0083] In the following description, hydrogen fuel may include at least one of gaseous hydrogen and liquid hydrogen. Hydrogen fuel basically refers to compressed hydrogen, but is not limited thereto.

[0084] In addition, although for ease of explanation, the two-way communication process for hydrogen fuel refueling is described with respect to a hydrogen electric vehicle (FCEV), the present disclosure is not limited to this, and the hydrogen fuel refueling two-way communication process can also be applied to hybrid electric vehicles (EV) or ICE-based vehicles that use hydrogen as fuel.

[0085] At the same time, if necessary, one or more traditional components may be included in the configuration of the present disclosure, and these components will be described herein to the extent that the technical concept and concept of the present disclosure are not obscured. However, if the description of traditional components obscures the technical concept and concept of the present disclosure, the detailed description of these components may be omitted for simplicity. However, the present disclosure is not intended to claim protection for traditional components, and traditional components may be included as elements of the apparatus or method of the present disclosure without departing from the concept or spirit of the present disclosure.

[0086] Exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings.

[0087] Figure 1 is a diagram of a hydrogen fueling system of a hydrogen electric vehicle (FCEV) to which a two-way communication process for hydrogen fueling is applied according to an exemplary embodiment of the present disclosure. Figure 2 yes Figure 1 A partial enlarged view of the physical connection structure between the FCEV and the dispenser in the hydrogen fueling system. Figure 3 It is shown in Figure 1 A graph illustrating changes in the state of hydrogen fuel occurring during a hydrogen fueling process in a hydrogen fueling system.

[0088] refer to Figure 1 The hydrogen fuel filling system may generally be configured to include a hydrogen fuel filling station and a hydrogen fuel mobile equipment 100 .

[0089] The hydrogen fuel mobile device 100 may be equipped with an electronic controller 110 , a vehicle system 120 , a vehicle tank 130 , and a receiving port 150 for hydrogen fuel filling, in addition to mechanical devices, electrical devices, electronic devices, and communication devices that are basically required for a vehicle.

[0090] The electronic controller 110 can send signals and data to and receive signals and data from the hydrogen fuel filling station or the electronic controller 210 of the hydrogen fuel filling station through wired or wireless communication, and process the signals and data to control the hydrogen fuel filling on the vehicle side. The electronic controller 110 can be implemented by at least part of another electronic control unit installed on the vehicle, and can be referred to as a first electronic controller or electronic control unit #1.

[0091] The vehicle system 120 may be connected to the first electronic controller 110 and may be configured to control the hydrogen fuel filling or hydrogen fuel discharge of the vehicle tank 130 according to a signal or command from the first electronic controller 110, and monitor the state of the vehicle tank 130. Depending on the implementation, the vehicle system 120 may include components that control the operation of the fuel cell system or perform such control operations, or may be configured to be combined with these components. The vehicle system 120 may be referred to as a vehicle safety system.

[0092] There may be at least one (preferably, a plurality) vehicle tanks 130 in the vehicle. The vehicle tank 130 may compress and store hydrogen supplied from a hydrogen fuel filling station under the control of a vehicle safety system, and may discharge the stored hydrogen.

[0093] In addition, the vehicle tank 130 may correspond to a hydrogen storage system installed in the vehicle. In this case, the hydrogen storage system may include a high-pressure hydrogen storage tank, a pressure control device, a high-pressure pipe, and an external frame. The high-pressure hydrogen storage tank may have a capacity of tens to hundreds of liters, and may have a shape in which a small storage tank is connected in parallel. A boss unit (boss unit) that allows hydrogen fuel to pass may be coupled to the high-pressure hydrogen storage tank, and thus the filling and discharge of hydrogen fuel may be controlled by the boss unit. The boss unit may include a valve, a pressure reducing device, and various sensors for measuring. This hydrogen storage system is referred to as a compressed hydrogen storage system (CHSS). For ease of explanation, the term "vehicle tank" used herein may refer to a CHSS.

[0094] The hydrogen fuel mobile device 100 may be equipped with a fuel cell system including a fuel cell stack, but the present disclosure is not limited thereto. For ease of explanation, the hydrogen fuel mobile device 100 may be referred to as "FCEV", "vehicle" or "mobile device". The term "vehicle" or "mobile device" used herein may be understood to include a hydrogen fuel vehicle or a hydrogen fuel mobile device that uses hydrogen as fuel in addition to a hydrogen electric vehicle.

[0095] The hydrogen fueling station may include a dispenser 200 , an electronic controller 210 , a fueling station system 220 , a hydrogen tank 230 , a station box 240 , and a nozzle 250 .

[0096] The dispenser 200 can supply hydrogen from the hydrogen tank 230 to the vehicle through a nozzle 250 firmly coupled to the receiving port 150 of the vehicle under the control of the fuel filling station system 220. The dispenser 200 may include an electronic controller 210 inside the housing, but the present disclosure is not limited thereto. The nozzle 250 may be installed at the end of a cable that extends a certain length outside the housing of the dispenser 200.

[0097] The electronic controller 210 can send and receive signals and data to the first electronic controller 110 of the vehicle through wired or wireless communication, and process the signals and data to control hydrogen fueling at the hydrogen fueling station side. The electronic controller 210 can exchange prescribed signals and data with the fueling station system 220. The electronic controller 210 can also be referred to as a second electronic controller or an electronic control unit #2.

[0098] Each of the first electronic controller 110 and the second electronic controller 210 may be composed of a plurality of electronic control units, and may be configured so that each communication protocol may be executed by a different electronic control unit. Such a configuration may be useful when fallback is used to achieve backward compatibility, and when two-way communication cannot be used but one-way communication may be used. In addition, this configuration may be useful in the case of using a combination of different communication methods, for example, when NFC is used for pairing and WiFi is used for actual fueling.

[0099] The fuel filling station system 220 may monitor or control the pressure, velocity, and temperature of hydrogen discharged from the hydrogen tank 230 based on the signal and / or data from the second electronic controller. To this end, the fuel filling station system 220 may control the operation of the station box 240 connected to the discharge port or discharge valve of the hydrogen tank 230. The fuel filling station system 220 may also be referred to as a fuel filling station safety system.

[0100] In an exemplary embodiment of the present disclosure, the communication entity associated with the dispenser 200 for communicating with the vehicle / mobile device 100 may be the electronic controller 210 or may be a separate communication device / equipment installed on the dispenser 200. Alternatively, the electronic controller or a separate communication device / equipment in the fuel filling station system 220 may communicate with the vehicle / mobile device 100 instead of the dispenser 200.

[0101] In another exemplary embodiment of the present disclosure, the communication control device / apparatus in the vehicle / mobile equipment 100 for communicating with the dispenser 200 side may be the first electronic controller 110 or may be a separate communication control device / apparatus.

[0102] The hydrogen tank 230 stores hydrogen or compressed hydrogen. The hydrogen tank 230 may discharge the stored hydrogen at a predetermined pressure or speed under the control of the fuel filling station safety system 220. The hydrogen tank may also be referred to as a hydrogen storage tank.

[0103] The station box 240 may be provided with a control valve having an inlet connected to the discharge port of the hydrogen tank 230 or the discharge valve and an outlet connected to the dispenser 200 or a nozzle 250 coupled to the dispenser 200. The station box 240 may be provided with a device for controlling the pressure, velocity and temperature of the discharged hydrogen or another component that performs such a function. In addition, the station box 240 may be provided with a sensor for measuring the pressure, velocity and temperature of the discharged hydrogen.

[0104] The nozzle 250 may be connected to the hydrogen fuel filling system of the dispenser 200 through a conduit or a flexible pipe of a predetermined length. The nozzle 250 may be provided with a shape and structure that is closely and firmly engaged with a receiving port of a vehicle.

[0105] like Figure 2 As shown, the nozzle 250 may be engaged with the receiving port 150. The first sensor 160 installed in the vehicle and the second sensor 260 attached to the nozzle 250 may send a signal or information about the coupling state of the nozzle 250 and the receiving port 150 to the first electronic controller or the vehicle safety system and to the second electronic controller or the fuel filling station safety system.

[0106] The pre-cooled hydrogen fuel may be supplied from the hydrogen fuel filling station to the hydrogen fuel mobile device 100 through the dispenser 200. At this time, the hydrogen fuel filling process may be described by parameters including a pressure increase rate (PRR) and / or an average pressure increase rate (APRR).

[0107] Dispenser 200 may be responsible for the interface between the hydrogen fuel filling station and mobile device 100. Dispenser 200 may be configured to control a target pressure and an injection speed for hydrogen fuel filling based on information indirectly acquired from vehicle tank 130 and fuel filling information of the hydrogen fuel filling station.

[0108] Generally, there are two methods of sending information from the mobile device 100 to the dispenser 200: a communication method and a non-communication method. In the case of the communication method, the temperature and pressure values ​​of the vehicle tank 130 of the mobile device 100 are sent to the dispenser 200 in a one-way manner, and the dispenser 200 does not actively utilize the information, but only uses the information as a safety reference for, for example, an emergency stop when the temperature or pressure limit is reached. In addition, the hydrogen fueling protocol for safe and fast fueling is managed by the dispenser 200, which has only a minimal safety management device that automatically releases hydrogen through a pressure release device (PRD) without any active safety management scheme for the vehicle tank 130.

[0109] At the same time, in order to cope with Figure 3 In order to reduce the temperature increase of hydrogen during hydrogen refueling as depicted in the above, the hydrogen refueling station may be equipped with a precooler. The precooler may reduce the temperature of the hydrogen fuel by precooling. The precooler may be installed in or combined with at least one of the hydrogen tank 230 and the station box 240. Alternatively, the precooler may be installed in or combined with a pipeline that transports hydrogen in the hydrogen refueling station.

[0110] The dispenser 200 or the second electronic controller may be equipped with a fuel filling control logic that may control the hydrogen fuel filling process based on status information such as the temperature and pressure of the hydrogen fuel supplied to the vehicle or filled in the vehicle tank 130 and fuel filling status information such as the hydrogen storage state (SOC) of the CHSS.

[0111] As described above, the hydrogen fuel filling process between the hydrogen fuel mobile device 100 and the hydrogen fuel filling station is controlled by the dispenser 200, and the dispenser 200 may include a protocol for supplying hydrogen fuel to the vehicle according to a prescribed procedure. The hydrogen fuel filling protocol may also be installed in the vehicle. The protocol installed in the vehicle or the dispenser 200 may include at least some of the communication protocols based on the SAE standard, the ISO standard, or the like.

[0112] For minimum safety requirements, a simulation based on thermodynamic modeling can be performed for various situations, and a table-based or MC-formula-based partial real-time correction can be performed using the parameters derived from the simulation. The minimum safety requirements can include upper limits for temperature and pressure conditions of the CHSS and guidelines for the hydrogen storage state (SOC).

[0113] In the case where the state values ​​related to hydrogen refueling are not actively controlled in the dispenser 200, the table-based correction has disadvantages and may show very low efficiency because the temperature of the pre-cooled hydrogen fuel provided by the refueling station or the temperature of the vehicle tank 130 measured in the mobile device 100 is not utilized, and therefore it may be difficult to flexibly respond to changes in ambient conditions. The correction based on the MC-formula allows real-time compensation for the temperature of the pre-cooled hydrogen fuel, but the calculation and application of this method are complicated, which may cause limitations in application and make it difficult to expand. Therefore, the conventional communication protocol developed with the main goal of safely completing refueling cannot actively respond to unexpected situations (such as excessive pre-cooling or overheating of the vehicle tank 130), and may bring problems such as increased operating costs caused by overcooling and delayed refueling caused by overheating.

[0114] For example, when hydrogen fuel is charged into the vehicle tank 130, the internal temperature of the vehicle tank rises due to compression heat, and thus the temperature of the hydrogen fuel inside the vehicle tank rises. The vehicle tank is designed so that the dome and body of the vehicle tank are wrapped with carbon fiber having low thermal conductivity to block heat exchange between the outside atmosphere and the hydrogen fuel stored in the vehicle tank. Therefore, when the temperature of the hydrogen fuel inside the vehicle tank rises during the fuel filling process, due to the low thermal characteristics of the vehicle tank, until the fuel filling is completed, the temperature rise displayed on the surface of the vehicle tank will be smaller than the internal temperature rise.

[0115] Meanwhile, the temperature control of the hydrogen fueling process may be aimed at ensuring that the internal temperature of the vehicle tank 130 remains below 85° C. when the fueling is completed by supplying pre-cooled hydrogen. During the hydrogen fueling process, the temperature of the hydrogen fuel will experience Figure 3The temperature of the hydrogen fuel decreases at a constant rate in phase 1 (P1), which is the pre-cooling phase of the hydrogen fuel filling station. In phase 2 (P2), during which the hydrogen fuel is supplied from the hydrogen fuel filling station to a hydrogen mobile device such as a vehicle, the temperature of the hydrogen fuel gradually increases due to the thermal mass of the hydrogen fuel filling station. In phase 3 (P3), during which the hydrogen fuel is transferred to the vehicle tank inside the vehicle, the temperature of the hydrogen fuel increases at a higher rate of increase due to the thermal mass of the vehicle. In phase 4 (P4), during which the hydrogen fuel is compressed and stored in the vehicle tank, the temperature of the hydrogen fuel increases rapidly due to the heat of compression.

[0116] According to the present embodiment, the hydrogen refueling process can be efficiently performed via a two-way communication process for hydrogen refueling through active state variable control reflecting real-time measurement data. In addition, a hydrogen refueling protocol for the process can be provided.

[0117] Figure 4 A framework of functional blocks for executing a series of hydrogen fueling processes (hereinafter, referred to as "hydrogen fueling framework") according to an exemplary embodiment of the present disclosure is shown, and the series of hydrogen fueling processes may adopt a two-way communication process for hydrogen fueling.

[0118] refer to Figure 4 The hydrogen fueling framework may include functional blocks for corresponding use cases (UCs), including a discovery and pairing functional block (hereinafter referred to as "UC1" or "UC-1"), a communication safety functional block (UC2 or UC-2), a communication protocol negotiation functional block (UC3 or UC-3), a fueling protocol negotiation functional block (UC4 or UC-4), a fueling parameter negotiation functional block (UC5 or UC-5), a safety check-in functional block (UC6 or UC-6), a fueling control and monitoring functional block (UC7 or UC-7), a safety check-out functional block (UC8 or UC-8), a termination functional block (UC9 or UC-9), an error handling functional block (UC10 or UC-10) and an emergency handling functional block (UC11 or UC-11).

[0119] The use cases UC10 and UC11 may be individually connected to the use cases UC3 to UC8 and may perform error processing and / or emergency processing in each use case.

[0120] The use cases are functional blocks that collectively provide the entire hydrogen refueling process of the hydrogen refueling system in a consistent manner for safe and reliable refueling communication. The vehicles and dispensers can execute the use cases sequentially in a certain order to achieve hydrogen refueling.

[0121] After the nozzle of the dispenser is coupled to the receiving opening of the vehicle, the vehicle and the dispenser can be connected by Figure 4 The order shown in the implementation of the use case to perform fuel filling communication. However, if necessary, the vehicle and the dispenser can omit the occurrence of the use case according to the predetermined requirements.

[0122] Each of the above use cases may be implemented according to a fueling protocol for a hydrogen fuel vehicle through communication between a dispenser control system of a dispenser that supplies hydrogen as fuel to the hydrogen fuel vehicle and the hydrogen fuel vehicle.

[0123] At the same time, the hydrogen fuel vehicle (hereinafter, also referred to as "vehicle") implementing the use case and the dispenser can perform data exchange for identifying the vehicle in the use case UC-1. For this purpose, the vehicle can be equipped with a sensor, an electronic control unit (ECU), a transmitter, and a receiver. In the case of two-way communication, the receiver can be integrated with the transmitter.

[0124] The dispenser may be configured to receive specific data from the vehicle. The dispenser may store specific data in a programmable logic controller (PLC) of a fuel filling station to store data of data logs or use them in a fuel filling protocol. Data logs may refer to a process of collecting data in a certain period of time to analyze a certain operating state of a hydrogen fuel filling system or a data-based event / operation of a recording system or network environment or data collected by the process. In the case of two-way communication, the fuel filling station may be equipped with a sensor specified by the fuel filling protocol, and the PLC or electronic control unit of the fuel filling station may obtain measurements from the sensor and send the measurements to the vehicle. The vehicle or fuel filling station may use conventional communication protocol standards for communication, such as infrared communication, WiFi, and Bluetooth.

[0125] In addition, the vehicle or dispenser can establish a communication channel with the dispenser or vehicle, respectively, which is physically coupled at its vehicle-dispenser interface. The pairing process for establishing such a communication channel can be performed using wired, optical or wireless communication technology.

[0126] The discovery and pairing process or pairing process may have the pre-condition that the nozzle of the dispenser is inserted and securely coupled to the receptacle of a vehicle fueling receptacle. The vehicle fueling receptacle may be referred to simply as a vehicle receptacle or receptacle.

[0127] Furthermore, the vehicle and the dispenser usually know by default the communication protocol to be followed. Therefore, the communication performed following the use case UC-1 can only rely on the communication protocol agreed upon in the current use case as a post-condition of the discovery and pairing process or pairing process. In the event that a communication protocol outside the agreed range is selected by the vehicle or the dispenser, the selected communication will not be performed. That is, even if the pairing process is successfully completed, refueling will not be authorized.

[0128] All methods for pairing a vehicle with a dispenser may be configured to not increase the risk of ignition or explosion beyond acceptable levels. For example, all wired pairing methods may be configured to mitigate or prevent spark hazards caused by electrostatic discharge.

[0129] In terms of the effectiveness of physical pairing, any method for pairing a vehicle with a dispenser may be integrated into the vehicle-to-dispenser interface or installed so as to maintain proximity between the vehicle's fuel filling port and the dispenser's nozzle and hose assembly. Here, the interface may refer to something physically integrated into the interface between the nozzle and the port. Proximity may be defined by hardware associated with the pairing method. For example, physical geometries for infrared communication may be specified, including the allowable distance between a transmitter and a receiver. In addition, the physical geometry of the hydrogen fueling hardware may be predefined, in which case proximity does not include a pairing method that would result in the risk of associating the dispenser to a vehicle that is not physically coupled to the dispenser, such as, for example, a long-range wireless communication technology such as Bluetooth. Infrared communication may be referred to as infrared data association (IrDA) communication, and may include bi-directional infrared (bi-IrDA) communication.

[0130] Figure 5 An example of a communication stack related to a use case employed in a bidirectional communication process for hydrogen refueling based on Open Systems Interconnection Reference Model (OSI) Layer 7 according to an exemplary embodiment of the present disclosure is shown.

[0131] like Figure 5 As shown, the communication stack associated with the use case of a bidirectional communication process for hydrogen refueling (hereinafter, referred to as the "hydrogen refueling communication stack") can be represented by a protocol suite corresponding to the corresponding layers in the OSI 7 layers, and the OSI 7 layers include data link and physical layer, network layer, transport layer, security layer, session layer, presentation layer and application layer.

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

[0133] Additionally, the hydrogen fueling communication stack may include Internet Protocol version 6 (IPv6) protocol 520 as a protocol for the network layer of OSI layer 7.

[0134] Furthermore, the hydrogen fueling communication stack may include at least one third protocol 530 selected from the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), etc. as a protocol of the transport layer of the OSI 7 layer.

[0135] In addition, the hydrogen refueling communication stack may include at least one fourth protocol 540 selected from transport layer security (TLS), datagram transport layer security (DTLS), etc. as a protocol of the security layer of OSI layer 7. TLS may include versions such as TLS1.2 and TLS1.3, and DTLS may include versions such as DTLS1.2 and DTLS1.3. TLS may be implemented on a TCP socket, and DTLS may be implemented on a UDP socket.

[0136] In addition, the hydrogen refueling communication stack may include a JSON-based session protocol 550 as a protocol of the session layer of OSI layer 7. The JSON-based session protocol 550 may be used for communication between a vehicle and a dispenser or for communication in data transmission between an electronic control unit of a vehicle and an electronic control unit of a refueling station.

[0137] In addition, the hydrogen fueling communication stack may include JavaScript Object Notation (JSON) 560 as a protocol of the presentation layer of OSI layer 7. JSON is one of the formats that can be used when sending data from a server to a client. Using JSON, protocol messages between a vehicle and a dispenser or between an electronic control unit of a vehicle and an electronic control unit of a fueling station may be represented in JSON format.

[0138] In addition, the hydrogen fueling communication stack may include a hydrogen fueling related fueling protocol FP570 as a protocol of the application layer of OSI layer 7. The fueling protocol 570 may include a first fueling protocol FP1, a second fueling protocol FP2, and an nth fueling protocol FPn, where "n" may be a natural number greater than or equal to 3.

[0139] In an alternative embodiment, the hydrogen refueling communication stack may include power line communication (PLC) or WLAN as a protocol for the data link and physical and network layers; TCP and / or IPv6 protocols as a protocol for the transport and security layers; a binary extensible markup language (XML) protocol as a session layer protocol; and one of the existing protocols used in electric vehicles as a protocol for the presentation and application layers. The existing protocols used in electric vehicles may include at least one protocol for direct current (DC) charging, alternating current (AC) charging, wireless power transmission (WPT), or automatic connection device pantograph (ACDP) charging of electric vehicles.

[0140] The communication data items that may be exchanged between a vehicle and a fueling station via the hydrogen fueling communication stack may be summarized as shown in Table 1.

[0141] [Table 1]

[0142]

[0143] At the same time, the discovery and pairing process use case UC1 enables the device to identify the communication counterpart (ie, the communication module of the vehicle or dispenser) responsible for controlling the port or nozzle physically coupled to the device. In addition, use case UC1 may also define incompatible identification methods and safety device mechanisms.

[0144] In this use case UC1, the vehicle and the dispenser may attempt to find a common communication technology to execute the fueling protocol. The vehicle and the dispenser may discover each other and initiate communication based on the discovery mechanisms provided by the data link and physical layers. An additional pairing process may be required to establish a communication channel with the device connected to the fueling hose assembly. In cases where the communication channel does not ensure correct pairing, for example, in the case of wireless communication, a separate pairing channel may be required to send pairing information. However, if pairing is ensured implicitly, for example, a communication channel integrated with the hose assembly may be sufficient.

[0145] Figure 6 is a sequence diagram illustrating a pairing process of a discovery and pairing process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure.

[0146] refer to Figure 6 , in the pairing process, the vehicle and the dispenser may exchange pairing IDs with each other and discover each other's pairing IDs during pairing at UCDC Level 2 and UCDC Level 3.

[0147] For example, the vehicle may broadcast a message PAIR_ID_ANNOUNCE (S710) containing its pairing ID (PAIR_ID) (i.e., vehicle ID (vehicle_id)). The distributor may send a message PAIR_ID_ACK to the vehicle to confirm receipt of the vehicle ID from the vehicle (S720). The vehicle may send a message PAIR_ID_CONFIRM to the distributor to confirm receipt of an ACK message from the vehicle (S730).

[0148] Next, the dispenser may broadcast a message PAIR_ID_ANNOUNCE containing its pairing ID (i.e., dispenser ID (dispenser_id)) (S740). The vehicle may send a message PAIR_ID_ACK to the dispenser to confirm receipt of the dispenser ID from the dispenser (S750). The dispenser may send a message PAIR_ID_CONFIRM to the vehicle to confirm receipt of an ACK message from the dispenser (S760).

[0149] This transmit-echo-verify approach enables the vehicle and dispenser to use a session-specific randomized pairing ID. This approach helps address privacy issues associated with the exchange of pairing IDs. That is, trust in the pairing process can be established by subsequent processes, and to this end, the session-specific pairing ID can be included in the data used to establish trust.

[0150] At the same time, when secure communication at a specific UCDC level is supported, at least one of the vehicle and the dispenser can verify that the pairing provides sufficient information to protect the communication channel for all methods used to pair the vehicle and the dispenser. For example, the pairing may include the exchange of encryption keys so that the vehicle and the dispenser can ensure communication during fueling.

[0151] It should be noted that since UCDC Level 1 does not support two-way communication, the security of the communication channel cannot be ensured at UCDC Level 1. Pairing vehicles and dispensers at UCDC Level 2 and UCDC Level 3 can be configured to provide sufficient information to ensure communication security sufficient to meet a specific security level (e.g., IEC 62443 Security Level 3). IEC62443 Security Level 3 can be a security level for actors with sufficient resources and sufficient motivation.

[0152] Figure 7 An example of backward compatibility that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure is shown.

[0153] refer to Figure 7, considering interoperability, the hydrogen fuel filling device may be designed to have backward compatibility with existing devices. The hydrogen fuel filling device or the communication device in the hydrogen fuel filling device may be classified into type 0, type 1, type 2, and type 3 based on interoperability.

[0154] Type 0 devices may refer to devices that do not support fueling communications or are unable to receive related communication messages.

[0155] Type 1 devices may refer to devices that support IrDA communications for fuel refueling. Type 1 devices may return to Type 0 devices.

[0156] Type 2 devices may refer to devices that support Advanced Communications (AC). Type 2 devices may fall back to Type 0 devices.

[0157] Type 3 devices may refer to devices that support IrDA communication and advanced communication. Type 3 devices may fall back to any one of Type 0, Type 1, and Type 2 devices.

[0158] Advanced communication may refer to communication using specific protocols and media, such as wireless local area network (WLAN), Bluetooth (BT), near field communication (NFC), WiFi, ultra-wideband (UWB), radio frequency identification (RFID), 4G and 5G. In addition, advanced communication may include two-way IrDA, serial communication, vehicle Ethernet (ETH), advanced communication, etc. Specific protocols may include transmission control protocol / Internet protocol (TCT / IP), fuel filling protocol, etc. Advanced communication may process all information beyond that processed by command and control communication. The data link of advanced communication may use power line communication (PLC, Power line communication), but the present disclosure is not limited to this.

[0159] Advanced communication may include hybrid forms, such as a combination of IrDA communication and wired communication and a combination of IrDA communication and wireless communication. The combination of IrDA communication and wired communication may require modifications to the nozzle and the receiving port.

[0160] That is, the advanced communication may be a wired or wireless two-way communication scheme, and the wireless communication scheme may include various communication schemes such as 5G, WLAN, BLE, ETH, UWB, RFID, and NFC. Known protocols such as TCP / IP may be used as the communication protocol of the communication scheme. For example, wireless communication schemes that may be considered may include Bluetooth, WLAN, WiFi (ISO 15118 for induction / ACD), UWB (IEC restriction considerations for ACD), or NFC.

[0161] In practice, the hydrogen fueling device may be implemented to support different communication schemes. Therefore, the bidirectional communication process for hydrogen fueling according to the present embodiment may be configured to maximize interoperability between devices.

[0162] In other words, if Figure 7 As shown, when a type 1 device supporting specification #1 according to a specific standard satisfies a type 0 device or a type 2 device, the type 1 device may fall back to type 0 (S610).

[0163] Also, when a type 2 device supporting specification #2 according to a specific standard satisfies a type 0 device or a type 1 device, the type 2 device may fall back to type 0 (S620).

[0164] In addition, when a type 3 device supporting specification #2 satisfies a type 0 device, the type 3 device may fall back to type 0 (S630). When a type 3 device satisfies a type 1 device, the type 3 device may fall back to type 1 (S640). When a type 3 device satisfies a type 2 device, the type 3 device may fall back to type 2 (S650).

[0165] The aforementioned specification #1 may include a specification according to the Society of Automotive Engineers (SAE) standard. Specification #2 may include a specification according to the ISO 19885-3 standard.

[0166] In order to support the interoperability as described above, the hydrogen fuel filling device may perform a connection compatibility check. For example, depending on whether each device supports WLAN, which is one of the advanced communication schemes, a connection compatibility check may be performed according to the following scenarios 1 to 3.

[0167] In scenario 1, the dispenser may be prepared with an access point (AP), i.e., a wireless router. The access point may send a beacon signal so that vehicles can access the fuel filling station and the vehicle supply equipment (VSE). The FCEV approaching the dispenser may scan and discover the dispenser, and may establish a WLAN link with the dispenser.

[0168] In scenario 2, the dispenser does not support bidirectional WLAN, but supports unidirectional IrDA. The dispenser corresponds to a Type 1 device. An FCEV approaching the dispenser (which is a Type 3 device) cannot scan and discover the dispenser as a Type 1 device. When the nozzle of the cable attached to the dispenser is coupled to the receiving port of the FCEV, IrDA communication can be initiated between the FCEV and the dispenser.

[0169] In scenario 3, the dispenser can support bidirectional WLAN communication and unidirectional IrDA communication. In this case, the dispenser corresponds to a type 3 device. An FCEV that is a type 1 device can be parked near the dispenser. The dispenser cannot yet find any WLAN clients. When the nozzle of the cable attached to the dispenser is coupled to the receiving port of the FCEV, IrDA communication can be initiated between the FCEV and the dispenser.

[0170] Figure 8 is a table summarizing examples of backward compatibility applicable to a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure.

[0171] refer to Figure 8 , the bidirectional communication process for hydrogen fueling according to the present embodiment can provide rules and criteria for fallback in selecting fueling methods and communication protocols to maximize interoperability, rather than selecting the communication scheme most preferred by the FCEV or dispenser.

[0172] That is, when either the vehicle or the dispenser encounters the other, a device having a relatively higher type or UCDC level may be configured to fall back to a type or level of a device having a relatively lower type or UCDC level.

[0173] For example, if the vehicle and the dispenser are of the same type or the same UCDC level, the two devices may maintain their current type or UCDC level. On the other hand, if one device is a type 1 device and the other device is a type 2 device, the two devices may be configured to fall back to type 0. Meanwhile, if one device is a type 3 device and the other device is not a type 3 device, the type 3 device may be configured to fall back to the same type or UCDC level as the other device.

[0174] The aforementioned specification #1 may be a communication protocol according to the SAE standard, and specification #2 may be a communication protocol according to the ISO 19885 standard.

[0175] Under the above configuration, if the vehicle and the distributor have implementations of a common or same type as each other, the vehicle and the distributor can select the type supported by the two devices, and the type is the best type among these types. When a device without communication capability (hereinafter referred to as a "non-communication device" or "non-communication device") encounters a device supporting one-way communication (hereinafter referred to as a "one-way communication device"), the latter can fall back to a non-communication device that does not support any communication scheme. When two devices supporting two-way communication meet each other, the two devices can maintain the original two-way communication scheme. Here, the compatibility of the UCDC level can be handled separately. When a device encounters a non-communication device, the device must rely on the non-communication. This rule can be applied to all devices that support two-way communication (hereinafter referred to as "two-way communication devices").

[0176] In addition, when a one-way communication device encounters a two-way communication device, if the two-way communication device supports both the one-way communication scheme and the two-way communication scheme, the two-way communication device can fall back to the one-way communication scheme. When the two-way communication device does not support one-way communication, the two-way communication device can fall back to the non-communication device to rely on the non-communication scheme.

[0177] The above-mentioned two-way communication device, whether or not equipped with a one-way communication capability, is configured to support a fuel filling method based on one-way communication. The two-way communication device needs to be able to check whether the other device supports two-way communication. If the other FCEV or dispenser does not support two-way communication, the two-way communication device can fall back to a one-way communication device that relies on a one-way communication scheme that can be compatible between the devices.

[0178] Fig. 9 A usage classification of communication data (UCDC) applicable in a two-way communication process for hydrogen fueling and backward compatibility in the usage classification of communication data according to an exemplary embodiment of the present disclosure are shown.

[0179] like Fig. 9 As shown, the vehicle and the dispenser may have corresponding pairing identities (IDs), and the requirements for exchanging IDs may be classified by the usage classification of the communication data (UCDC) level. The UCDC level may include UCDC level 1 (UCDC-1) 910, UCDC level 2 (UCDC-2) 920, and UCDC level 3 (UCDC-3) 930. The UCDC level may also include UCDC level 0 (UCDC-0) 900.

[0180] In the case of UCDC level 0 (UCDC-0) 900, data is not communicated. Even if data is communicated, the communicated data is not used for the fueling protocol of dispensing hydrogen or associated with the safety function. In UCDC level 0 (900), since no communication is performed between the vehicle and the dispenser, the dispenser cannot send the pairing ID to the vehicle during the process of process control or safety function.

[0181] The vehicle may send the pairing ID to the dispenser when pairing is attempted at UCDC Level 1 (UCDC-1) 910. Although the data delivered at UCDC Level 1 (UCDC-1) 910 is not used for safety functions, the static data communicated may be used to improve the performance of the fueling protocol, and the dynamic data communicated may be used to reduce the risk of resisting process deviations during the fueling protocol.

[0182] Static data communicated at UCDC level 2 (UCDC-2) 920 may be used for a security function. The static data of UCDC level 2 (UCDC-2) 920 may be data added to static data and dynamic data defined for UCDC level 1 that are allowed to be used.

[0183] The static data and dynamic data at UCDC level 3 (UCDC-3) 930 may be used for dynamic control of the protocol or for a security function. The dynamic data of UCDC level 3 (UCDC-3) 930 may be data added to the static data and dynamic data defined for UCDC level 2 that are allowed to be used.

[0184] As described above, the UCDC level may have a structure in which the functions and / or effects of UCDC level 1 may be included in the functions and / or effects of UCDC level 2, and the functions and / or effects of UCDC level 2 may be included in the functions and / or effects of UCDC level 3, that is, the functions and / or effects of a higher level may include the functions and / or effects of a lower level. A device supporting a certain UCDC level may support a device of a lower UCDC level. A device capable of supporting different UCDC levels may use the highest UCDC level supported by both devices. The above-mentioned UCDC level may also easily support UCDC level 0. It can be seen that the UCDC level is backward compatible. In another embodiment of the present disclosure, backward compatibility may be effectively applied to each or a combination of a non-communication scheme (Non-Comm), a unidirectional communication scheme (Uni-directionalComm), and a bidirectional communication scheme (Bi-directionalComm), regardless of the UCDC level.

[0185] Fig.10is a sequence diagram illustrating an authorization process in a communication security process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure.

[0186] refer to Fig.10 , the FCEV may request a list of authorization methods from the dispenser (S1010). The dispenser may send a response message to the request for the list of authorization methods to the FCEV (S1020). The response message may include a list of authorization methods related to self-authorization or external authorization (such as RFID, credit card, or debit card).

[0187] Next, the FCEV may send an authorization request message including an authorization method (such as RFID) selected from the list of authorization methods to the dispenser (S1030). The dispenser may send a response message to the FCEV's authorization request (S1040). The response message may include information indicating that the authorization of the authorization method selected by the FCEV is working.

[0188] Then, the FCEV may wait for a response containing the authorization result from the distributor, and may send an authorization result request message (Complete?) for the selected authorization method to the distributor (S1050). If no authorization result is received or the authorization is not completed, operations S1010 to S1050 may be repeated. After completing the authorization, the distributor may send an authorization completion message ("Complete (Success)") to the FCEV (S1090).

[0189] According to the above process, the dispenser can verify whether the FCEV is authorized before performing the hydrogen fueling process, that is, whether the user of the FCEV has the right to perform hydrogen fueling.

[0190] To ensure the security of the authorization process, a hydrogen fueling device including at least one of a vehicle and a dispenser may establish a transport layer (i.e., a TCP connection) after establishing a data link and a physical layer connection between the vehicle and the dispenser, and then perform a TLS handshake to authenticate and exchange keys, thereby establishing a secure communication channel. In the process of exchanging critical information for security, a User Datagram Protocol (UDP) communication protected by Datagram Transport Layer Security (DTLS) may be used.

[0191] In addition, the vehicle and the dispenser can perform a discovery and pairing process and establish a connection in the data link layer and the physical layer. Then, the certificates required for authentication and key exchange can be prepared. Thus, the communication channel between the vehicle and the dispenser can be encrypted and integrity protected. The dispenser can authenticate the vehicle, and optionally, the vehicle can authenticate the dispenser.

[0192] Meanwhile, during the TLS handshake, the authentication of the vehicle may be mandatory, while the authentication of the distributor may be optional. In this case, the distributor may act as a client and the vehicle may act as a server.

[0193] For the TLS handshake, the vehicle and the dispenser must prepare the necessary certificates. The vehicle and the dispenser may store and maintain the certificate chain, the private key corresponding to its certificate, and the certificate of the trust anchor in a secure storage device to prevent unauthorized access.

[0194] During the TLS handshake, the vehicle can send a predefined certificate request message to the distributor to request client authentication from the distributor. After receiving the certificate request message, the distributor can send a certificate and a certificate verification message to the vehicle to provide the certificate to the vehicle.

[0195] If the vehicle sends a certificate request message along with a handshake message such as ServerHello, but the dispenser does not send a certificate verify message along with the certificate, the vehicle can terminate the TLS handshake by sending a warning message with a "Certificate_required" warning code.

[0196] Fig.11 is a sequence diagram illustrating a communication protocol negotiation process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure.

[0197] refer to Fig.11 During the communication protocol negotiation process, the FECV and the dispenser may identify the protocol version of the fueling protocol used during the bidirectional hydrogen fueling communication process. To initiate the protocol negotiation, the FCEV may send a negotiation request message to the dispenser (S1110).

[0198] Next, the distributor may provide a response message including a list of communication protocols supported by the distributor to the FCEV as a response to the negotiation request message (S1130). The response message may include information about the communication protocols supported by the distributor and may be based on, for example, the SAE standard or the ISO standard. For example, the SAE standard may include the SAE J2601 standard, and the ISO standard may include the ISO 19885-3 and ISO 19885-4 standards.

[0199] Subsequently, the FCEV may select a protocol (eg, ISO-v1-ucdc-3 protocol) from a list of communication protocols supported by the distributor, and transmit a protocol selection message including information on the selected communication protocol to the distributor (S1150).

[0200] Then, the distributor may discover the protocol included in the protocol selection message from the FCEV and send a negotiation OK message to the FCEV (S1170).

[0201] The communication protocol negotiation process is performed to identify the communication protocol used in the hydrogen fueling session after the vehicle and the dispenser discover each other on the communication channel and perform pairing. Specifically, according to the present embodiment, the dispenser guides the process of exchanging communication protocols and parameters with the vehicle.

[0202] The communication protocol negotiation process may be implemented for all available communication protocols to ensure successful negotiation between different refueling protocols of each communication technology. For example, a refueling protocol using a communication technology such as WLAN may use a protocol commonly supported by the vehicle and the dispenser (hereinafter, referred to as a "common protocol") to determine the communication protocol used in the two-way communication process for hydrogen refueling.

[0203] In actual implementations, various combinations may exist between FCEV and the dispenser, depending on the hydrogen fueling communication standard, communication mode, fueling method, communication level, and other parameters. Here, the hydrogen fueling communication standard may include the SAE J2601 series, ISO 19885-3, and ISO 19885-4 standards. Communication modes may include no communication, IrDA, XYZ (ISO), etc. The fueling method may include a table-based fueling method, such as a lookup table-based method, and a MC formula-based fueling method. These communication levels may include UCDC levels, and other parameters may include pressure levels, categories of compressed hydrogen storage systems (CHSS), hydrogen fueling tables, etc.

[0204] Meanwhile, the vehicle or the dispenser may be configured to perform a fallback to a lower type or a lower UCDC level according to the type and UCDC level of the corresponding device discovered during the communication protocol negotiation process.

[0205] In many possible combinations of circumstances, if incompatibilities are identified in parameters exchanged during the negotiation process for hydrogen refueling (eg, in use cases UC3 through UC5), the vehicle and the dispenser may return to the communication protocol negotiation process to perform the negotiation process again.

[0206] Fig.12 is a sequence diagram illustrating a communication protocol negotiation process that may be employed in a two-way communication process for hydrogen fueling according to another embodiment of the present disclosure.

[0207] refer to Fig.12During the communication protocol negotiation process, the FCEV may send a request message to the allocator, including a list of communication protocols assigned priorities (S1210). Examples of communication protocols assigned priorities are shown in Table 2.

[0208] The distributor may send a response message including a specific protocol (i.e., a selected protocol) selected from the protocol list to the FCEV (S1230). The selected protocol selected by the distributor may be a common protocol supported by both the distributor and the vehicle and having the highest priority and most preferred by the vehicle, for example, the ISO 19885-3-2023-UCDC-3 protocol in the example of Table 2.

[0209] The common protocol may be the result of an agreement between the vehicle and the dispenser regarding a communication protocol to be used for refueling communications.

[0210] At the same time, the vehicle can prioritize the communication protocols supported by the vehicle. The vehicle can include an FCEV. The vehicle can provide the prioritized communication protocols to the distributor. Examples of prioritized communication protocols are shown in Table 2.

[0211] [Table 2]

[0212] Protocol ID Priority SAE J2601-No Communication 7 SAE J2799-IrDA 6 SAE J2601-IrDA 5 ISO19885-3-2023-UCDC-0 4 ISO19885-3-2023-UCDC-1 3 ISO19885-3-2023-UCDC-2 2 ISO19885-3-2023-UCDC-3 1

[0213] After selecting a communication protocol in the communication protocol negotiation use case UC3, the vehicle and the dispenser may activate their communication protocol implementations and begin fueling protocol negotiation. Fueling protocol negotiation is a process in which the vehicle and the dispenser discover and agree upon a fueling protocol for the fueling session. In this operation, the vehicle and the dispenser may select the vehicle's most preferred communication protocol among the protocols that both the vehicle and the dispenser support.

[0214] According to an exemplary embodiment of the present disclosure, a communication protocol negotiation method for hydrogen fuel refueling performed by a communication control device 100 of a hydrogen fuel mobile device may include: operation S1210, sending a first message to a communication entity associated with a dispenser 200, the first message including a list of at least a first fuel refueling protocol supported by the hydrogen fuel mobile device and at least a first communication protocol required by the at least first fuel refueling protocol; and operation S1230, receiving a response message from a communication entity associated with the dispenser 200 including a second fuel refueling protocol determined (selected) from at least one first fuel refueling protocol.

[0215] The communication entity associated with the dispenser 200 may be the electronic controller 210 of the dispenser 200 or may be a separate communication device / equipment installed on the dispenser 200. Alternatively, the electronic controller or a separate communication device / equipment in the fuel filling station system 220 may communicate with the vehicle / mobile device 100 instead of the dispenser 200.

[0216] The first message may include priority information based on the preference of the hydrogen fuel mobile device 100 as shown in Table 2.

[0217] The response message may include a second fueling protocol determined (selected) from at least one first fueling protocol based on the priority information (based on preference). The mobile device 100 side or the dispenser 200 side may determine (select) the second fueling protocol based on the priority information (based on preference) individually or in cooperation with each other. The operation of finally sending an approval (or confirmation) message to the other party to complete the protocol negotiation process may be performed by the mobile device 100 side, but may also be performed by the dispenser 200 side instead.

[0218] The response message may include a second fueling protocol determined (selected) from at least one common protocol candidate commonly included in the at least one first fueling protocol and at least one fueling protocol supported by dispenser 200 .

[0219] exist Fig.12 In the exemplary embodiment shown, the response message may include a second fueling protocol determined (selected) by the controller of dispenser 200 from the at least one first fueling protocol.

[0220] The response message may include a second communication protocol required by a second fueling protocol determined by the controller of dispenser 200 .

[0221] The response message may include the second communication protocol determined (selected) by the controller of dispenser 200 from among at least one second communication protocol candidate required for the second fueling protocol.

[0222] The response message may include a second communication protocol determined by the controller of dispenser 200 from among a plurality of communication protocols required for the second fueling protocol according to a fallback device type determined based on interoperability and / or backward compatibility between hydrogen fuel mobile device 100 and dispenser 200 .

[0223] Reference together Fig.11 and Fig.12According to the communication protocol negotiation method for hydrogen fuel refueling of an exemplary embodiment of the present disclosure, a negotiation request message for negotiating a hydrogen fuel refueling communication protocol between a hydrogen fuel mobile device 100 and a dispenser 200 may be initially sent by a communication control device of the hydrogen fuel mobile device 100 to a communication entity associated with the dispenser 200.

[0224] The communication protocol negotiation method for hydrogen fuel refueling according to an exemplary embodiment of the present disclosure may further include the following operation: when a response message is accepted as a response to the negotiation request message, the communication control device of the hydrogen fuel mobile device 100 sends a confirmation message in response to the response message to negotiate.

[0225] In operation S1210 of sending the first message, the first message may be sent as a negotiation request message to a communication entity related to the distributor 200 .

[0226] Fig.13 is a sequence diagram illustrating a fueling parameter exchange / negotiation process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure.

[0227] The fueling protocol negotiation process may include operations in which mobile devices or dispensers exchange detailed parameters required for the fueling protocol. The mobile device may include a FCEV.

[0228] refer to Fig.13 During the fueling protocol exchange / negotiation process, the FCEV may provide the dispenser with first parameters (ie, parameters of the FCEV) supported by the RCEV (S1310).

[0229] The first parameters may include parameters for supporting fueling method compatibility, parameters related to physical properties, monitoring parameters, and parameters related to acceptability.

[0230] Compatibility-related parameters may include pressure level and CHSS category. Physical property-related parameters may include maximum allowable CHSS pressure, maximum allowable CHSS temperature, maximum allowable flow rate and CHSS volume. Monitoring parameters may include current CHSS pressure and current CHSS temperature. Acceptability-related parameters may include information indicating whether it is accepted, i.e., parameters indicating yes (true) or no (false). Each of the above parameters may include information corresponding to one of the predetermined levels or settings and information about the same or different master UCDC levels.

[0231] At the same time, the distributor may send information of the second parameter supported by the distributor (ie, the parameter of the distributor) and an OK message indicating that the first parameter has been received to the FCEV (S1330). Fig.13 The parameter exchange process shown and Fig.12 In the case where the protocol negotiation processes shown are linked to each other, the allocator can use Fig.13 The OK message shown in operation S1330 in the embodiment sends a response message including information of the protocol selected in the first parameter to the FCEV.

[0232] Second parameters related to the fueling protocol exchange / negotiation may include parameters for supporting fueling method compatibility, parameters related to physical properties, fueling target parameters, monitoring parameters, and parameters related to acceptability.

[0233] Compatibility-related parameters may include a fueling delivery temperature and a selected fueling table. Physical property-related parameters may include a maximum fueling delivery pressure, a maximum fueling delivery temperature, a minimum fueling delivery temperature, and a maximum fueling delivery flow. Fueling target parameters may include a target SOC, a target final CHSS pressure, a target final CHSS temperature, a target APR, and a target or expected fueling duration. Monitoring parameters may include the current fueling delivery temperature and the ambient temperature. Acceptability-related parameters may include information indicating whether it is accepted. Each of the above parameters may include information corresponding to one of the predetermined levels or settings and information about the same or different main UCDC levels.

[0234] The FCEV may provide the dispenser with parameters listed in a table format. The listed parameters may include FCEV parameters that are compatible with the UCDC level negotiated during the fueling protocol negotiation process.

[0235] The allocator may include information about the second parameter supported by the allocator and information about the parameter selected in the first parameter ( Fig.13 in <ok>”) is sent to the FCEV (S1330).

[0236] In addition, the second parameter related to the fueling protocol may be expressed in another form as shown in Table 3.

[0237] [Table 3]

[0238] index name Revision Sub-protocol refer to 1 PRHYDE 2023 TYPE3-T-initial 4 2 PRHYDE 2024 TYPE3-T-Special 3 3 RTR-HFP 2 4 ANN-MPC 5 5 HMC-FAST 1.0 1

[0239] As shown in Table 3, the dispenser may provide parameter information in a table format that includes the name, revision date or year or version, information about whether a subprotocol is available, and reference information (such as priority) for the fueling methods or fueling protocols supported by the dispenser.

[0240] Similar to the vehicle, the distributor may take the lead in exchanging communication protocols and parameters with the vehicle, or may be configured to assign priorities to communication protocols supported by the distributor to provide information of prioritized communication protocols to the vehicle.

[0241] In Table 3, PRHYDE (Heavy Duty Hydrogen Refueling Protocol) was proposed by one of the European projects that has developed a hydrogen refueling protocol for heavy-duty vehicles, RTR-HFP stands for Real-Time Response Hydrogen Refueling Protocol and is proposed as a type of protocol concept for improving refueling efficiency based on real-time communication, and ANN-MPC is proposed as a type of protocol concept for collecting and analyzing data from refueling situations and applying predictive control to the refueling situations.

[0242] Examples of information that may be sent by the dispenser to the FCEV regarding the selection of a protocol related to the fueling protocol are shown in Tables 4 and 5.

[0243] [Table 4]

[0244] Fueling Protocol ID Result Codes 2 OK

[0245] As shown in Table 4, the dispenser may select a fueling protocol corresponding to index 2 and send a response message including a result code OK to the FCEV.

[0246] [Table 5]

[0247] Fueling Protocol ID Result Codes FAIL_NO_COMMON_PROTOCOL

[0248] As shown in Table 5, when the dispenser fails to find a compatible protocol in the list of fueling protocols supported by the FCEV received from the FCEV, the dispenser may send a response message to the FCEV containing information indicating that a common protocol does not exist (eg, FAIL_NO_COMMON_PROTOCOL) in the result code field.

[0249] As described above, after establishing a communication link and selecting a communication protocol in the protocol negotiation phase, the FCEV and the dispenser may exchange various parameters to determine whether they are able to perform a compatible fueling process. Here, the information required to perform a safe and effective fueling process may include compatibility-related parameters, physical property-related parameters, fueling target parameters, and monitoring parameters.

[0250] Compatibility-related parameters may include fueling protocol category and fuel delivery temperature. Physical property-related parameters may include CHSS pressure and maximum allowed flow. Fueling target parameters may include target SOC and target CHSS pressure. Monitoring parameters may include current CHSS temperature and ambient temperature.

[0251] In the event that compatible parameters cannot be found and refueling cannot be performed, the FCEV may return to the communication protocol negotiation process to attempt to negotiate another protocol or stop the dispenser refueling. During the communication protocol negotiation process after a refueling parameter exchange failure, the FCEV may propose to the dispenser a set of supported protocols excluding the protocol that failed during the refueling parameter exchange process.

[0252] After the refueling protocol is negotiated in the above use case UC-4, the vehicle and the dispenser may negotiate specific parameters for the refueling protocol, notify the static or dynamic status, and exchange detailed refueling parameters to determine the refueling target. If the refueling parameter negotiation fails due to incompatibility of the parameters, the dispenser and the FCEV may return to the use case UC-3 to select another refueling protocol or return to the use case UC-1 to select another communication protocol. If the use case UC-3 and the use case UC-1 cannot be performed normally, the dispenser and the FCEV may terminate the current communication.

[0253] According to the above configuration, some fueling protocols may be executed on a no-communications basis. Another fueling protocol may require one-way IrDA communication. Another fueling protocol may require two-way communication. Another fueling protocol may require both two-way communication and one-way IrDA communication.

[0254] Some fueling protocols may require a predetermined UCDC level or a higher UCDC level. At least one fueling protocol may be proposed based on the category or type of hydrogen fuel cell vehicle and the category or type of dispenser. The proposed fueling protocols may be assigned different priorities. The communication protocol and the fueling protocol between the hydrogen fuel cell vehicle and the dispenser may ultimately be determined based on whether the communication protocol required for the fueling protocol is supported by the hydrogen fuel cell vehicle and / or the dispenser and taking into account the priority of the proposed fueling protocol.

[0255] Fig.14 is a sequence diagram illustrating a fueling parameter exchange / negotiation process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure.

[0256] like Fig.14 As shown, the vehicle and the dispenser may determine the detailed parameters required to execute the selected fueling protocol with the desired safety and performance levels. When the selection of the fueling protocol is completed according to the fueling protocol negotiation process, the vehicle and the dispenser may exchange the detailed parameters to be exchanged before executing the fueling protocol. In detail, after the FCEV sends the value of the fueling parameter to the dispenser (S1410) and the dispenser responds with its own parameter value (S1430), the fueling parameter negotiation begins. During the parameter exchange, the vehicle and the dispenser may determine whether the vehicle and the dispenser are able to execute the fueling protocol.

[0257] During the refueling parameter negotiation, the FCEV and the dispenser may exchange parameters at least once until an agreement is reached for each protocol required to properly and efficiently refuel the FCEV while maintaining the hydrogen refueling system in a safe state. A receiver receiving the parameters from a sender may send a response message to the sender indicating receipt of the parameters. Acceptance of the parameters may be indicated as true in the acceptance field, while negative acceptance may be indicated as pending or false in the acceptance field.

[0258] After receiving the fueling protocol negotiation response message from the dispenser, the FCEV may send a fueling protocol negotiation response message within a predetermined message processing time to provide the dispenser with fueling parameters to be set.

[0259] An example of parameters sent by the FCEV is shown in Table 6.

[0260] [Table 6]

[0261] name unit Accuracy Range / Value type Semantics Pressure level N / A N / A {H35, H70} Static Tank pressure rating CHSS Volume Lift dichotomy Positive, no maximum Static Tank capacity CHSS Pressure MPa dichotomy Positive, no maximum dynamic Tank current pressure Emergency Strategy N / A N / A {Terminate, rollback} Static Emergency treatment strategy

[0262] An example of the parameters sent by the allocator is shown in Table 7.

[0263] [Table 7]

[0264]

[0265] As described above, during the fueling parameter negotiation process, the FCEV may send a message to the dispenser including a range or value of a third fueling parameter supported by the FCEV (S1410).

[0266] The third parameters may include physical characteristic related parameters, monitoring parameters, security policy related parameters, and acceptability related parameters.

[0267] The compatibility-related parameters may include port type, pressure level, CHSS category, CHSS type, CHSS volume, maximum allowable CHSS pressure, maximum allowable CHSS temperature, and maximum allowable flow. Monitoring parameters may include current CHSS pressure and current CHSS temperature. Security policy-related parameters may include emergency policy and security implementation level. Acceptability-related parameters may include information indicating whether it is accepted, i.e., parameters indicating yes (true), no (false), or pending.

[0268] At the same time, the dispenser may transmit information including a range or value of a fourth fueling parameter supported by the dispenser to the FCEV (S1410).

[0269] Fourth parameters related to the fueling parameter negotiation may include physical property related parameters, monitoring parameters, fueling target parameters, security policy related parameters, and acceptability related parameters.

[0270] Physical property related parameters may include maximum fuel delivery pressure, maximum fuel delivery temperature, minimum fuel delivery temperature, and maximum fuel delivery flow. Monitoring parameters may include current fuel delivery temperature and ambient temperature. Fueling target parameters may include a selected fueling table, target SOC, target final CHSS pressure, target final CHSS temperature, target APR, and target or expected fueling duration. Acceptability related parameters may include information indicating whether it is accepted. Each of the above parameters may include information corresponding to one of the predetermined levels or settings and information about the same or different main UCDC levels.

[0271] The FCEV may provide the dispenser with parameters listed in a table format. The listed parameters may include FCEV parameters that are compatible with the UCDC level negotiated during the fueling protocol negotiation process.

[0272] Meanwhile, if a fuel filling parameter negotiation request message is received and the received fuel filling parameters are compatible with the dispenser, the dispenser may respond to the request message with its own fuel filling parameter by sending a fuel filling parameter negotiation response message with the negotiation result set to "OK" to the FCEV within a predetermined message response time interval.

[0273] If a fueling parameter negotiation request message is received but the received fueling parameter is incompatible with the dispenser, the dispenser may respond to the request message by sending a fueling parameter negotiation response message with a negotiation result set to "failure" to the FCEV to indicate incompatibility with the vehicle (FCEV). The negotiation result may indicate a value or information contained in a result code field, and the failure may indicate a negotiation failure at a specific time and may be indicated by an indication of incompatibility, for example, "Fail_incompat".

[0274] Meanwhile, if the FCEV receives the fuel filling parameter negotiation request message but finds the received fuel filling parameters incompatible with the FCEV, the FCEV may notify the dispenser of the incompatibility by sending an error notification message with a “reason” set to a predetermined error code.

[0275] On the other hand, before starting the fuel delivery, the vehicle and the dispenser can verify that all safety conditions are met through the use case UC6 for safety check-in. This operation is optional, but it is desirable to define a dedicated safety check-in process in the fueling protocol in order to ensure the desired safety level in a precise and unambiguous manner.

[0276] Fig.23 is a conceptual diagram illustrating a table disclosing parameters transferred from a mobile device side to a distributor side in a parameter exchange process according to an exemplary embodiment of the present disclosure.

[0277] Fig.24 is a conceptual diagram illustrating a table disclosing parameters transferred from a distributor side to a mobile device side in a parameter exchange process according to an exemplary embodiment of the present disclosure.

[0278] Together with Fig.13 Reference together Fig.23 and Fig.24 ,exist Fig.23 The first parameter set transferred in operation S1310 is shown in Fig.24 , the second parameter set transferred in operation S1330 is shown.

[0279] According to an exemplary embodiment of the present disclosure, a communication parameter exchange method for hydrogen fuel refueling performed by a communication control device of a hydrogen fuel mobile device, the method may include: operation S1310, sending a first parameter to a communication entity associated with a dispenser 200, the first parameter including one or more of the following items: at least one first hydrogen fuel refueling method compatibility supported by the hydrogen fuel mobile device 100, and / or at least one first physical characteristic; and operation S1330, receiving a response message including a second parameter from the communication entity associated with the dispenser 200, the second parameter including one or more of the following items: at least one second hydrogen fuel refueling method compatibility supported by the dispenser, at least one second physical characteristic, and / or a fueling target (fueling purpose).

[0280] The communication entity associated with the dispenser 200 may be the electronic controller 210 of the dispenser 200 or may be a separate communication device / equipment installed on the dispenser 200. Alternatively, the electronic controller or a separate communication device / equipment in the fuel filling station system 220 may communicate with the vehicle / mobile device 100 instead of the dispenser 200.

[0281] The first parameter may also include a first monitoring parameter supported by the hydrogen fuel mobile device 100. The second parameter may also include a second monitoring parameter supported by the dispenser 200.

[0282] In the communication parameter exchange method for a hydrogen fuel filling process according to an exemplary embodiment of the present disclosure, the parameter exchange process can be terminated based on a confirmation message (e.g., an OK message) included in a response message. When the mobile device 100 and the dispenser 200 accept all exchanged parameters, the parameter exchange process can be terminated. When either party does not accept the exchanged parameters, the parameter exchange process can also be terminated. In the event that either party does not accept the exchanged parameters, the protocol negotiation process can be revisited according to the following process, or the fuel filling session can be terminated.

[0283] In the communication parameter exchange method for a hydrogen fueling process according to an exemplary embodiment of the present disclosure, at least one first hydrogen fueling method compatibility may include one or more of a pressure level and / or a CHSS category of the hydrogen fuel mobile equipment 100 .

[0284] In the communication parameter exchange method for a hydrogen fueling process according to an exemplary embodiment of the present disclosure, at least one first physical characteristic may include one or more of a maximum allowable CHSS pressure, a maximum allowable CHSS temperature, a maximum allowable flow rate, and / or a CHSS volume.

[0285] In the communication parameter exchange method for a hydrogen fuel filling process according to an exemplary embodiment of the present disclosure, the first parameter also includes a parameter related to the acceptability of the hydrogen fuel mobile equipment 100 .

[0286] In the communication parameter exchange method for a hydrogen fueling process according to an exemplary embodiment of the present disclosure, the first monitoring parameter may include one or more of a current CHSS pressure and / or a current CHSS temperature.

[0287] In the communication parameter exchange method for a hydrogen fueling process according to an exemplary embodiment of the present disclosure, at least one second hydrogen fueling method compatibility may include one or more of the fueling delivery temperature of the dispenser 200 and / or a determined (or selected) fueling table. The determined (or selected) fueling table may include a sequence table of a selected fueling protocol, and / or may be included in the OK message shown in operation S1330.

[0288] In the communication parameter exchange method for a hydrogen fueling process according to an exemplary embodiment of the present disclosure, at least one second physical characteristic may include one or more of a maximum fuel delivery pressure, a maximum fuel delivery temperature, a minimum fuel delivery temperature, and / or a maximum fuel delivery flow rate.

[0289] In the communication parameter exchange method for a hydrogen fueling process according to an exemplary embodiment of the present disclosure, the fueling target (or fueling purpose) may include one or more of a target SoC, a target final CHSS pressure, a target final CHSS temperature, a target average fueling rate (APR), and / or an expected fueling duration.

[0290] In the communication parameter exchange method for a hydrogen fuel filling process according to an exemplary embodiment of the present disclosure, the second parameter may further include a parameter related to the acceptability of the dispenser 200 .

[0291] In the communication parameter exchange method for a hydrogen fueling process according to an exemplary embodiment of the present disclosure, the second monitoring parameter may include one or more of a current fuel delivery temperature and / or an ambient temperature.

[0292] In operation S1310 , the mobile device 100 may provide the distributor 200 with first parameters compatible with the UCDC level negotiated during the protocol negotiation process in the form of a table.

[0293] In operation S1330, the distributor 200 may provide the mobile device 100 with a second parameter compatible with the UCDC level negotiated during the protocol negotiation in the form of a table. At this time, the second parameter may be provided together with a message indicating acceptance of the first parameter provided in operation S1310.

[0294] If the exchanged parameters are not accepted by mobile device 100 or dispenser 200, mobile device 100 may perform the protocol negotiation process again. Alternatively, if the exchanged parameters are not accepted by mobile device 100 or dispenser 200, mobile device 100 may terminate the fueling session.

[0295] In a protocol negotiation process that is retried due to a failed parameter exchange process where the mobile device 100 or the distributor 200 does not accept the exchanged parameters, the mobile device 100 may propose a set of supported protocols in addition to the protocols that have been offered in the failed parameter exchange process.

[0296] Fig.15 is a sequence diagram illustrating a safety check-in process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure.

[0297] During the safety check-in process, the dispenser and the vehicle, including the FCEV, can check whether all necessary safety conditions are met before the actual fueling begins.

[0298] After the fueling parameters are exchanged and the vehicle and dispenser are deemed compatible, the vehicle and dispenser may perform a safety status check to determine if the fueling may be performed safely. Depending on the fueling protocol, the safety check may be implicitly performed within the protocol. Additionally, depending on the implementation, the safety check-in process may be omitted.

[0299] During the safety check-in process, the vehicle and / or dispenser may check that the engagement of the nozzle and the receiving opening is locked, check for any leaks, and check last minute status.

[0300] In the event that the vehicle has received a fueling parameter negotiation response message from the dispenser and the fueling protocol supports security check-in, the vehicle may initiate the security check-in process by sending a security check-in request message to the dispenser within a message sequence set time interval.

[0301] In detail, Fig.15 As shown, the vehicle and the distributor may exchange messages for coupling inspection (S1510 and S1520). The vehicle may send a message including information indicating its own coupling inspection result (e.g., "FCEV: OK") to the distributor, and the distributor may send a message including information indicating its own coupling inspection result (e.g., DP: OK) to the vehicle.

[0302] The vehicle and the dispenser may exchange messages related to the gas leak check (S1530 and S1570). During the exchange of messages related to the gas leak check, the dispenser may send information indicating that the leak check is in progress ("in progress") to the vehicle (S1540). Also, the vehicle may send information indicating that the vehicle is waiting for the leak check result from the dispenser ("waiting") to the dispenser (S1560). When the leak check is completed, the dispenser may send a message requesting the measured tank volume together with information indicating that the leak check is completed ("completed") to the vehicle (S1570).

[0303] The dispenser may send a message for a fixed status check to the vehicle (S1580), and the vehicle may send a message indicating that it is ready for a status check to the dispenser (S1590).

[0304] If the vehicle reports parameters regarding the current state or fixed state of the vehicle to the dispenser, the dispenser may report parameters regarding the coupling lock state, leak check state, and predicted FCEV tank capacity to the vehicle.

[0305] After completing the above safety check-in process, the actual fueling can begin. During the fueling, the vehicle and the dispenser can exchange information to monitor various status parameters to ensure that the fueling is performed safely and efficiently. If necessary, the vehicle or the dispenser can send control messages requesting actions from the other party to control the fueling process or respond to safety-related conditions. The parameters and commands to be exchanged can vary depending on the actual fueling protocol.

[0306] Fig.16 is a sequence diagram illustrating a monitoring and control process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure.

[0307] During the monitoring and control process, the dispenser and / or the vehicle including the FCEV can monitor the fueling status and control the fueling process when necessary. According to the selected fueling protocol and using parameters, the vehicle and the dispenser can continue the fueling process while confirming all safety checks. During the fueling, the vehicle and the dispenser can exchange various measurement data to determine the fueling status and detect safety-critical events as quickly as possible.

[0308] In addition, the vehicle may send certain commands to the dispenser to control the refueling process, such as the start or end of refueling. At this time, the vehicle may use UDP with DTLS for communication to support black channel communication. Black channel communication may refer to communication that applies black channel criteria to ensure secure communication, although the output characteristics of the communication channel may be unsecure or have attributes that are irrelevant to the application.

[0309] More specifically, if Fig.16 As shown, the vehicle may send a message to the dispenser to start fuel filling control (S1610), and in response, the dispenser may send a message including a confirmation (eg, "OK") to the vehicle (S1620).

[0310] In addition, the vehicle can send a message including information of its own fuel filling cycle (e.g., x, y, z) to the dispenser (S1630), and the dispenser can send a message including information of its own fuel filling cycle (e.g., a, b, c) corresponding to the vehicle's fuel filling cycle to the vehicle (S1640).

[0311] In addition, the vehicle may send a fuel filling control request message to the dispenser, the fuel filling control request message including information for slowing down fuel filling or reducing the amount of fuel delivered (S1660), and the dispenser may send a response message to the vehicle, the response message including information indicating the slowing down of the fuel filling flow (S1670).

[0312] In addition, the vehicle may send a fuel filling control request message requesting to stop the fuel filling to the dispenser (S1680). The dispenser may send a fuel filling state response message including information that the fuel filling is stopped or has been stopped to the vehicle (S1690).

[0313] According to the monitoring and control process, the vehicle and the dispenser can continuously or periodically exchange parameters related to the state of fuel filling. The vehicle can send information such as current tank temperature, current tank pressure, etc. to the dispenser, and the dispenser can provide the vehicle with parameters related to the start, stop, ramp up or ramp down of fuel filling, current injection pressure, fuel filling schedule, etc.

[0314] The message sent by the vehicle to the dispenser regarding the fuel filling control request may include information or parameters related to the start, pause, resume and termination of fuel filling. In addition, the message related to the report sent by the vehicle to the dispenser may include information or parameters such as the current tank temperature and the current tank pressure.

[0315] For example, the report message sent by the dispenser to the vehicle may include information or parameters related to status information, current ambient temperature, current pressure ramp rate (PRR), delivered fuel flow, current fuel delivery temperature, pre-cooling temperature, current fuel delivery pressure, whether full fueling is used, whether a cooling dispenser is used, whether fallback is used, the reason for the fueling stop, and the amount of hydrogen currently being delivered.

[0316] Messages sent by the dispenser to the vehicle related to target parameter updates may include target final tank pressure, target final tank temperature, target fueling APR, target SOC, current SOC, and estimated duration remaining.

[0317] Meanwhile, when TCP is used in the monitoring and control process, if the security check-in response message or the security check-in process according to the fuel filling protocol is omitted, after receiving the fuel filling parameter negotiation response message from the dispenser, the vehicle may send a fuel filling cycle request message to the dispenser within the message sequence setting time interval. The request message or response message related to the fuel filling cycle may be sent through a DTLS message.

[0318] After hydrogen refueling is completed through the monitoring and control process, the vehicle and dispenser can check whether all safety conditions are met by the vehicle and dispenser through the safety checkout use case before terminating the session and removing the nozzle from the vehicle. The safety check-in process may be optional, but it is desirable to define a dedicated safety check-in process in the refueling protocol in order to ensure the desired safety level in a precise and unambiguous manner.

[0319] Fig.17 is a sequence diagram illustrating a safety checkout process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure.

[0320] The vehicle and dispenser can check through the safety checkout process whether all necessary safety conditions are met before the nozzle of the dispenser is disconnected from the receiving port of the vehicle. In other words, the vehicle and dispenser can verify that it is absolutely safe for the user or operator to disconnect the nozzle from the vehicle after completing the fuel filling.

[0321] For example, if the vehicle receives a fueling cycle response message from the dispenser with the "result" attribute set to "OK" or the "status" attribute set to "completed", or the vehicle receives a fueling status response message including information to stop fueling, and if the hydrogen fueling protocol supports safety checkout, the vehicle can start safety checkout and perform the checkout process by sending a safety checkout request message to the dispenser within the message sequence set time period.

[0322] The vehicle and the dispenser may repeatedly report their status to each other until the safety check is verified. If the bidirectional communication process for hydrogen refueling does not require such a safety check at the end, the use case for safety checkout may be omitted.

[0323] More specifically, if Fig.17 As shown, the vehicle may send a message containing information about the coupling inspection result (eg, "OK") to the distributor (S1710), and the distributor may send a message containing information indicating that the coupling inspection is in progress (eg, "In Progress") to the vehicle (S1730).

[0324] In addition, the vehicle may again send a message containing information about the coupling inspection result (e.g., "OK") to the distributor (S1750), and the distributor may send a message containing information indicating that the coupling inspection is completed (e.g., "Complete") to the vehicle (S1770).

[0325] When the coupling inspection result shows that the coupling inspection is completed normally, the user or operator may separate the nozzle of the dispenser from the receiving port of the vehicle.

[0326] During the safety check-out process, the report message sent by the dispenser to the vehicle may include information or parameters about the coupling unlocking status. The coupling unlocking status information may include information of lock, unlock, ice or problem.

[0327] The termination use case UC9 may be executed when fueling according to the hydrogen fueling protocol is complete and the nozzle is safely detached, or when a safety non-critical issue occurs during another use case.

[0328] Fig.18 is a sequence diagram illustrating a termination process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure.

[0329] During the termination process as the final stage of refueling, the vehicle and the dispenser may exchange information about the refueling results of the refueling performance and method and / or information about the reasons for the unexpected stop of refueling to complete all processes of hydrogen refueling. The termination use case may also be configured to handle tasks related to safety non-critical issues when they occur.

[0330] For example, after the vehicle receives a safety checkout response message (wherein the "result" attribute is set to "complete") or a fuel filling cycle response message (wherein the "status" attribute is set to "complete") or information including stopping fuel filling from the dispenser, the vehicle can send a termination request message to the dispenser to perform the termination process.

[0331] For example, Fig.18 As shown, the vehicle may send a message to the dispenser to inquire how much fuel has been refilled from the dispenser (S1810). The dispenser may send a response message including information about the amount of hydrogen fuel refilled (e.g., X grams) to the vehicle in response to the query message (S1830).

[0332] Subsequently, the vehicle may transmit a confirmation request message for completing fuel filling to the dispenser (S1850), and the dispenser may transmit a bye message to the vehicle as a response message to the confirmation request message (S1870).

[0333] After completing the fueling and performing the safety check, the vehicle and the dispenser may exchange at least some bookkeeping information for terminating the fueling session of the hydrogen fueling in progress. Prior to completing the termination process, the vehicle and the dispenser may exchange summary information about the hydrogen fueling session.

[0334] The bookkeeping information may include all information about hydrogen refueling recorded in a vehicle or dispenser, according to specified rules or policies, throughout all refueling sessions for hydrogen refueling and before completing the termination process of use case UC-9.

[0335] The bookkeeping information or summary information may include information about how much fuel was dispensed and what reports were generated. In addition, the reporting message sent by the vehicle to the dispenser may include information or parameters related to the current tank temperature and the current tank pressure. At the same time, the reporting message sent by the dispenser to the vehicle may include information about the final SOC, the final average fueling rate (APR), the final measured tank pressure, the actual fueling time, and the actual amount of hydrogen fueled.

[0336] When all necessary information for the fueling session is stored, the fueling session may be completely terminated.

[0337] Examples of communication data exchanged in some use cases UC5 to UC9 are summarized in Table 8.

[0338] [Table 8]

[0339]

[0340]

[0341] Meanwhile, the error handling use case UC10 is a functional block for handling a case where a safety non-critical error occurs due to a shutdown like a normally terminated fuel filling process or a sudden interruption of communication.

[0342] Fig.19 is a sequence diagram illustrating an error handling process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure.

[0343] The error handling process may include the definition of error conditions related to the fueling protocol, the provision of detection criteria, and the response process including notification, termination procedures and fallback mechanisms when errors occur.

[0344] refer to Fig.19 , when a safety non-critical error occurs and further communication is not possible, an error handling process can be applied. According to the error handling process, the vehicle and the dispenser can handle safety non-critical errors that occur at any time during refueling. When a safety non-critical error occurs, the vehicle and the dispenser can immediately stop refueling, temporarily stop the use case that was previously selected and currently operating, and then continue to terminate the use case UC9.

[0345] If the vehicle detects an event related to a safety non-critical error (S1910), the vehicle may notify the dispenser of the termination reason through a termination request message (S1930) and stop the current fuel filling session or communication session (S1950). The dispenser may terminate the current communication session in response to the termination request message (S1970). If further communication is not possible, the current session may be terminated without additional notification.

[0346] When a safety non-critical error is detected in the vehicle and the communication channel maintains an operable condition, the vehicle may send a termination request message to the distributor with an "action" attribute set to "stop" and a "reason" attribute set to an appropriate reason or reason code. Examples of appropriate reasons or reason codes may include a reason such as "message corrupted".

[0347] A Terminate Request message may be sent in the event of an error such as a safety non-critical communication error, a system error, or a qualitative error, excluding unrecoverable situations.

[0348] That is, for successful refueling, the communication must convey the actions that can be expected according to the protocol, and the refueling operation needs to be within the acceptable range of the refueling protocol. However, in practice, various abnormal events may occur. While some errors are trivial and can be easily handled, others are unrecoverable and will prevent refueling from proceeding. The error handling process can define safety non-critical error conditions and provide exemplary error conditions and possible responses.

[0349] Examples of communication errors may include instances where the communication is disconnected, where the received data cannot be recognized due to a coding error or syntax error, or where the received data is outside of an allowable range. System errors may include instances where the dispenser or the vehicle itself detects a critical system error. Qualitative errors may include instances where the quality of the communication performance does not meet the required level, or where the quality of the data integrity or accuracy does not meet the required level.

[0350] According to the two-way communication process for hydrogen fueling of this embodiment, the following specific error handling processes as shown in (1) to (4) can be performed for the above-mentioned error conditions.

[0351] (1) In the event of a safety non-critical error and no further communication is possible, the vehicle and dispenser may immediately stop refueling, but may take safety action and terminate the session by ceasing communications.

[0352] (2) In the event that a safety non-critical error occurs and refueling is suspended without completion, the refueling protocol may define a fallback mechanism, for example by defining a non-communication refueling method.

[0353] (3) In the event that a safety non-critical error is detected in the vehicle and the communication channel is still operational, the vehicle may send a terminate request message to the distributor with the "Action" attribute set to "Stop" and the "Reason" attribute set to the appropriate reason or reason code.

[0354] (4) In the event that the dispenser detects a safety non-critical error and the communication channel is still operational, the dispenser may immediately stop refueling and send a terminate request message to the vehicle with the "Action" attribute set to "Stop" and the "Reason" attribute set to the appropriate reason or reason code.

[0355] As described above, the bidirectional communication process for hydrogen fueling including the fueling protocol can define error conditions related to the fueling protocol, provide detection criteria, and when an error is detected according to the detection criteria, perform an error handling process including notification, termination process and fallback mechanism.

[0356] Meanwhile, during refueling of the hydrogen refueling system, when a critical safety issue occurs, urgent action may be required.

[0357] Fig. 20 is a sequence diagram illustrating an emergency process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure.

[0358] The emergency handling procedures may define safety critical conditions requiring emergency actions during fueling and may include response procedures to prevent safety critical accidents.

[0359] For safe refueling, the communication must convey the actions that can be expected according to the protocol, and the refueling operation needs to be within the safety range of the refueling protocol. However, problems can occur during refueling, causing the refueling system to reach a critical state that must be avoided at all costs. The emergency handling process can define safety-critical emergency conditions and possible actions for emergency conditions, and can provide important situations to be considered.

[0360] A fueling protocol may define emergency conditions associated with the protocol, provide detection criteria for emergency conditions and vehicle or dispenser performance requirements, and prescribe response procedures to avoid entering a hazardous situation.

[0361] like Fig. 20 As shown, when the vehicle detects a high pressure condition exceeding a predetermined reference value during the hydrogen fuel filling process, the vehicle may send a first emergency stop request message including information requesting a fuel filling stop according to the high pressure (e.g., "Emergency: Stop (High Pressure)") to the dispenser (S2010). The dispenser may send a response message including information indicating that the dispenser is processing an emergency fuel filling stop (e.g., "Emergency: Stop") to the vehicle in response to the first emergency stop request message (S2020).

[0362] In addition, upon receiving the response message or after a preset time has passed since receiving the response message, the vehicle may again send the first emergency stop request message to the dispenser (S2030). After emergency stopping the fuel filling, the dispenser may send a response message including information indicating that the fuel filling has been emergency stopped (e.g., "Emergency: Stop") to the vehicle (S2040).

[0363] Meanwhile, if the dispenser detects a hydrogen fuel leak during the hydrogen fuel filling process, the dispenser may send a second emergency stop request message to the vehicle, the second emergency stop request message including information indicating that it is processing a fuel filling stop due to the leak (e.g., "Emergency: Stop (Leak)") (S2060). The vehicle may send a response message including information indicating confirmation of the second emergency stop request message (e.g., "Emergency: Confirm") to the dispenser (S2070).

[0364] In addition, the dispenser may send a third emergency stop notification message to the vehicle (S2080), the third emergency stop notification message including information indicating that fuel filling has been stopped due to leakage (e.g., "Emergency: Stop (Leak)"). The vehicle may send a response message including information indicating confirmation of the third emergency stop notification message (e.g., "Emergency: Confirmed") to the dispenser (S2090).

[0365] According to the above configuration, when a vehicle or dispenser detects a critical situation that affects safety, the vehicle and / or dispenser can immediately take necessary measures to prevent a disaster from occurring and, if possible, send an emergency notification message containing information about the situation to the other party and block communication between the vehicle and the dispenser.

[0366] When an emergency notification message is received, the vehicle or dispenser may immediately respond to the situation indicated in the emergency notification message and terminate the communication without excessive delay. The emergency notification message may include a header and a body (including the message). The header may include information indicating the emergency notification, and the message may include values, information, or parameters for the level, type, and action of the emergency notification.

[0367] Emergency notification messages may be sent via TLS or DTLS messages, depending on the technology used for the communications.

[0368] Fig.21 1 is a schematic block diagram of an apparatus using a two-way communication process for hydrogen fueling (referred to as “hydrogen fueling apparatus” for short) according to another exemplary embodiment of the present disclosure. Fig. 22 It shows that it can be Fig.21 Block diagram of the software modules used in the hydrogen fuel filling device.

[0369] refer to Fig.21 , the hydrogen fuel filling device 3000 may be implemented in the form of a computing device or a computing system including a processor 3100 electrically connected to a memory 3200 .

[0370] The hydrogen fuel filling device 3000 may be a device that provides hydrogen fuel filling services, or a hydrogen fuel filling control unit or communication unit included in such a device. Similarly, the hydrogen fuel filling device 3000 may be a device that receives hydrogen fuel filling services, or a hydrogen fuel filling control unit or communication unit included in such a device.

[0371] The hydrogen fuel filling device 3000 may be configured to include a processor 3100, a memory 3200, a transceiver 3300, an input interface 3400, an output interface 3500, a storage device 3600, and a bus (3700). The components of the hydrogen fuel filling device 3000 may be connected to each other through the bus 3700 to communicate with each other.

[0372] The processor 3100 may include a central processing unit (CPU), a graphics processing unit (GPU), or another dedicated processor suitable for executing the methods of the present disclosure.

[0373] Each of the memory 3200 and the storage device 3600 may include at least one of a volatile storage medium and a nonvolatile storage medium. For example, the memory 3200 may include at least one of a read-only memory (ROM) and a random access memory (RAM).

[0374] The hydrogen fuel filling device 3000 may perform at least part of the two-way communication process for hydrogen fuel filling, the fuel filling protocol, the fuel filling method, the hydrogen fuel filling protocol, or the hydrogen fuel filling method according to the above-mentioned embodiment. To this end, the hydrogen fuel filling device 3000 may include at least one processor 3100 and a memory 3200 storing program instructions instructing at least one processor 3100 to perform at least one step. At least part of the steps of the two-way process or method can be performed by at least one processor 3100 loading and executing the program instructions from the memory 3200.

[0375] In addition, the hydrogen fuel filling device 3000 has the following features: Figure 4 In addition to the functional blocks UC1 to UC11 described above, the following may also be included: Fig. 22 Function blocks 3110 to 3180 are shown. These function blocks 3110 to 3180 may be installed on the hydrogen fuel filling device 3000 or on at least one processor 3100 of the hydrogen fuel filling device 3000.

[0376] Functional blocks 3110 to 3180 may 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 payment negotiation, a fifth functional block 3150 for authentication, a sixth functional block 3160 for exchanging fueling parameters, a seventh functional block 3170 for fueling, and an eighth functional block 3180 for stopping / pausing fueling.

[0377] When performing handshake, the first functional block 3110 can check and compare the version of the communication protocol that can be used for any fuel filling protocol. In addition, the first functional block 3110 can check the TLS version and the like.

[0378] The second functional block 3120 may allocate an IP address, an IPv6 address, a session identifier, etc. through a vehicle or a distributor.

[0379] When there are differences in hydrogen fueling services (such as fueling rates) according to regions, time zones, or service providers, the third function block 3130 may negotiate services to be applied to each hydrogen fuel mobile equipment based on fueling rates and user convenience, etc.

[0380] A fourth functional block 3140 may determine a payment method for hydrogen fueling and handle the payment process.

[0381] The fifth functional block 3150 may process at least one of user authentication, vehicle authentication, dispenser authentication, and hydrogen fueling station authentication.The fifth functional block 3150 may correspond to at least part of the functional blocks of the discovery and pairing use case UC1.

[0382] The sixth functional block 3160 may correspond to at least a portion of the functional blocks of the Fueling Parameters Negotiation Use Case UC5.

[0383] The seventh function block 3170 can monitor and control the fuel filling process, and can correspond to at least part of the monitoring and control use case UC7. In addition, the seventh function block 3170 can correspond to at least some of the combinations of the safety check-in use case UC6, the monitoring and control use case UC7, the safety check-out use case UC8 and the termination use case UC9.

[0384] The eighth function block 3180 may stop or temporarily suspend the fuel filling process or fuel filling communication during error handling or emergency handling, and may correspond to at least part of a combination of the error handling use case UC10 and the emergency handling use case UC11.

[0385] In addition, the above-mentioned hydrogen fuel filling device 3000 can be equipped with various types of computing devices installed on the vehicle or dispenser. The computing device can be any data processing device capable of communicating through a network, such as a desktop computer, a laptop computer, a notebook PC, a smart phone, 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, and a personal digital assistant (PDA).

[0386] The communication control device of the hydrogen fuel mobile device according to the exemplary embodiment of the present disclosure may include a memory 3200 and a processor 3100, the memory stores at least one program instruction, and the processor executes the at least one program instruction. When executing at least one program instruction, the processor 3100 is configured and / or caused to:

[0387] A first parameter is sent to a communication entity associated with a dispenser, the first parameter including one or more of the following: compatibility with at least one first hydrogen refueling method supported by a hydrogen refueling mobile device, and / or at least one first physical characteristic; and a response message is received from a communication entity associated with the dispenser including a second parameter, the second parameter including one or more of the following: compatibility with at least one second hydrogen refueling method supported by the dispenser, at least one second physical characteristic, and / or a refueling target (or refueling purpose).

[0388] In the communication control device of the hydrogen fuel mobile equipment according to the exemplary embodiment of the present disclosure, the first parameter may further include a first monitoring parameter supported by the hydrogen fuel mobile equipment, and the second parameter may further include a second monitoring parameter supported by the dispenser.

[0389] In the communication control device of the hydrogen fuel mobile equipment according to the exemplary embodiment of the present disclosure, the parameter exchange process may be terminated based on the confirmation message included in the response message.

[0390] In the communication control device of the hydrogen fuel mobile equipment according to the exemplary embodiment of the present disclosure, at least one first hydrogen fuel filling method compatibility may include one or more of a pressure level and / or a CHSS category of the hydrogen fuel mobile equipment.

[0391] In the communication control device of the hydrogen fuel mobile equipment according to the exemplary embodiment of the present disclosure, the at least one first physical characteristic may include one or more of a maximum allowable CHSS pressure, a maximum allowable CHSS temperature, a maximum allowable flow rate and / or a CHSS volume.

[0392] In the communication control device of the hydrogen fuel mobile equipment according to the exemplary embodiment of the present disclosure, at least one second hydrogen fueling method compatibility may include one or more of the fueling delivery temperature of the dispenser and / or the determined (or selected) fueling table.

[0393] In the communication control device of the hydrogen fuel mobile equipment according to the exemplary embodiment of the present disclosure, the at least one second physical characteristic may include one or more of a maximum fuel delivery pressure, a maximum fuel delivery temperature, a minimum fuel delivery temperature and / or a maximum fuel delivery flow rate.

[0394] In the communication control device of the hydrogen fuel mobile equipment according to the exemplary embodiment of the present disclosure, the fueling target (or fueling purpose) may include one or more of a target SoC, a target final CHSS pressure, a target final CHSS temperature, a target average fueling rate (APR) and / or an expected fueling duration.

[0395] On the other hand, although most of the above embodiments focus on the method in which the vehicle first sends the communication protocol or parameters to the distributor, the present disclosure is not limited thereto, and the present disclosure may be configured so that the distributor first sends the communication protocol or parameters of the distributor to the vehicle. Except for the change of the transmitter and the receiver, this embodiment has substantially the same features as the above embodiments.

[0396] The apparatus and method according to the exemplary embodiments of the present disclosure can be implemented by computer-readable program codes or instructions stored on a computer-readable intangible recording medium. Computer-readable recording media include all types of recording devices that store data that can be read by a computer system. Computer-readable recording media can be distributed on computer systems connected via a network so that computer-readable programs or codes can be stored and executed in a distributed manner.

[0397] Computer readable recording media may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, and flash memory. Program instructions may include not only machine language codes generated by a compiler, but also high-level language codes executable by a computer using an interpreter or the like.

[0398] Some aspects of the disclosure described above in the context of the device can indicate the corresponding description according to the method of the present disclosure, and a block or device can correspond to the operation of the method or the feature of the operation. Similarly, some aspects described in the context of the method can be expressed by the feature of a block, project or a device corresponding thereto. Some or all operations of the method can be performed by using a hardware device (e.g., a microprocessor, a programmable computer or an electronic circuit). In some exemplary embodiments, one or more of the most important operations of the method can be performed by such a device.

[0399] In some exemplary embodiments, a programmable logic device such as a field programmable gate array can be used to perform some or all of the functions of the methods described herein. In some exemplary embodiments, the field programmable gate array can be operated using a microprocessor to perform one of the methods described herein. Typically, the method is preferably performed by a hardware device.

[0400] The description of the present disclosure is essentially only exemplary, and therefore, variations that do not deviate from the essence of the present disclosure are intended to fall within the scope of the present disclosure. These changes should not be considered as departing from the spirit and scope of the present disclosure. Thus, it will be understood by those of ordinary skill in the art that various changes in form and detail may be made without departing from the spirit and scope defined by the appended claims.< / ok>

Claims

1. A method for exchanging communication parameters for hydrogen fuel refueling performed by a communication control device of a hydrogen fuel mobile device, the method comprising: sending a first parameter to a communication entity associated with a dispenser, the first parameter comprising one or more of: at least one first hydrogen refueling method compatibility supported by the hydrogen refueling mobile device, and at least one first physical characteristic; and A response message is received from the communication entity associated with the dispenser including a second parameter including one or more of: at least one second hydrogen fueling method compatibility supported by the dispenser, at least one second physical characteristic, and a fueling target.

2. The method according to claim 1, wherein: The first parameter also includes a first monitoring parameter supported by the hydrogen fuel mobile device, Wherein, the second parameter also includes a second monitoring parameter supported by the distributor.

3. The method according to claim 1, wherein: The parameter exchange procedure is terminated based on a confirmation message included in the response message.

4. The method according to claim 1, wherein: The one or more first hydrogen refueling method compatibilities include one or more of a pressure rating of the hydrogen refueling equipment (Pressure Rating) and a category of a compressed hydrogen storage system (CHSS Category).

5. The method according to claim 1, wherein: The at least one first physical characteristic includes one or more of a maximum allowable compressed hydrogen storage system pressure, a maximum allowable compressed hydrogen storage system temperature, a maximum allowable flow rate, and a volume of the compressed hydrogen storage system.

6. The method according to claim 1, wherein: The first parameters also include parameters related to the receptivity (receptivity) of the hydrogen fuel mobile equipment.

7. The method according to claim 2, wherein: The first monitoring parameter includes one or more of a current compressed hydrogen storage system pressure and a current compressed hydrogen storage system temperature.

8. The method according to claim 1, wherein: The at least one second hydrogen fueling method compatibility includes one or more of a fueling delivery temperature of the dispenser (Fueling Delivery Temperature) and a selected fueling schedule of the dispenser (Selected Fueling Schedule).

9. The method according to claim 1, wherein: The at least one second physical characteristic includes one or more of a maximum fuel delivery pressure, a maximum fuel delivery temperature, a minimum fuel delivery temperature, and a maximum fuel delivery flow rate.

10. The method according to claim 1, wherein: The fueling target includes one or more of a target hydrogen storage state (target SoC), a target final compressed hydrogen storage system pressure, a target final compressed hydrogen storage system temperature, a target average fueling rate, and an expected fueling duration (expected fueling duration).

11. The method according to claim 1, wherein: The second parameters also include parameters related to the receptivity (receptivity) of the dispenser.

12. The method according to claim 2, wherein: The second monitored parameter includes one or more of a current fuel delivery temperature and an ambient temperature (ambient temperature).

13. A communication control device for a hydrogen fuel mobile device, comprising: A memory storing at least one program instruction; as well as a processor, executing the at least one program instruction, Wherein, the processor is configured to: sending a first parameter to a communication entity associated with a dispenser, the first parameter comprising one or more of: at least one first hydrogen refueling method compatibility supported by the hydrogen refueling mobile device, and at least one first physical characteristic; and A response message is received from the communication entity associated with the dispenser including a second parameter including one or more of: at least one second hydrogen fueling method compatibility supported by the dispenser, at least one second physical characteristic, and a fueling target.

14. The communication control device according to claim 13, wherein: The first parameter also includes a first monitoring parameter supported by the hydrogen fuel mobile device, Wherein, the second parameter also includes a second monitoring parameter supported by the distributor.

15. The communication control device according to claim 13, wherein: The parameter exchange procedure is terminated based on a confirmation message included in the response message.

16. The communication control device according to claim 13, wherein: The at least one first hydrogen fueling method compatibility includes one or more of a pressure rating of the hydrogen fuel moving equipment (Pressure Rating) and a category of a compressed hydrogen storage system (CHSS Category).

17. The communication control device according to claim 13, wherein: The at least one first physical characteristic includes one or more of a maximum allowable compressed hydrogen storage system pressure, a maximum allowable compressed hydrogen storage system temperature, a maximum allowable flow rate, and a volume of the compressed hydrogen storage system.

18. The communication control device according to claim 13, wherein: The at least one second hydrogen fueling method compatibility includes one or more of a fueling delivery temperature of the dispenser (Fueling Delivery Temperature) and a selected fueling schedule of the dispenser (Selected Fueling Schedule).

19. The communication control device according to claim 13, wherein: The at least one second physical characteristic includes one or more of a maximum fuel delivery pressure, a maximum fuel delivery temperature, a minimum fuel delivery temperature, and a maximum fuel delivery flow rate.

20. The communication control device according to claim 13, wherein: The fueling target includes one or more of a target hydrogen storage state (target SoC), a target final compressed hydrogen storage system pressure, a target final compressed hydrogen storage system temperature, a target average fueling rate, and an expected fueling duration (expected fueling duration).

Images