Hydrogen fueling communication protocol negotiation method and apparatus using same

Abstract

A method according to an embodiment of the present invention comprises the steps of: transmitting a first message to a communication entity associated with a dispenser, the first message comprising one or more first fueling protocols supported by a mobile device and a list of first communication protocols required to execute the one or more fueling protocols; and receiving, from the communication entity associated with the dispenser, a response message comprising a second fueling protocol selected from the one or more first fueling protocols.

Description

Technical Field

[0001] The present disclosure relates to communication technology for providing hydrogen fueling for hydrogen fueled mobility, and more specifically, to a hydrogen fueling process suitable for enhancing the safety, compatibility, efficiency and reliability of hydrogen fuel, a communication protocol negotiation 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 driven by electric energy 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 driven by electricity generated by a fuel cell system that uses hydrogen as an energy source. Hydrogen electric vehicles not only discharge pure water (H2O) vapor during power generation, but also remove ultrafine dust from the air while driving, and therefore attract attention as an environmentally friendly mobile device of the future. Since the fuel (i.e., hydrogen) is abundant on the earth and the energy production process is environmentally friendly, hydrogen electric vehicles have attracted much attention as a technology potentially used in industry.

[0004] 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 electric energy to drive an electric motor by electric energy. In addition to the above-mentioned hydrogen electric vehicles, hydrogen fuel mobile devices may include air mobile devices and industrial trucks, trains, ships, and airplanes that use hydrogen as a fuel to generate electric energy and are driven by electric energy.

[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 exhausts only pure water vapor through an exhaust port.

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

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

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

[0009] Specifically, in hydrogen fuel filling communication, most hydrogen fuel filling control devices use one-way infrared communication devices for wireless communication, and therefore 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 method, a communication protocol negotiation method for a hydrogen fueling process and / or a device for implementing the method, wherein the hydrogen fueling process is used to overcome the limitations and vulnerabilities of conventional one-way communication for hydrogen fueling of hydrogen fuel mobile devices, and is used to enhance the safety, compatibility, efficiency and / or reliability of hydrogen fueling.

[0012] An exemplary embodiment provides a two-way communication process for hydrogen fueling, a communication protocol negotiation process that takes into account two-way / unidirectional communication, and a device for implementing the process, wherein the two-way communication process provides multiple rules and principles that 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 rather than selecting their most preferred fueling protocol and communication protocol.

[0013] Exemplary embodiments provide a two-way communication process for hydrogen refueling, a communication protocol negotiation process that takes into account two-way / one-way communication, and a device for implementing the process, which can control a mobile device and a dispenser to determine an advanced communication medium to effectively achieve hydrogen refueling goals.

[0014] Technical Solution

[0015] According to one aspect of an exemplary embodiment, a communication protocol negotiation method according to an exemplary embodiment of the present disclosure is performed by a communication controller of a hydrogen fuel mobile device, and the method may include: an operation of transmitting a first message to a communication entity associated with a dispenser, the first message including a list of at least one first fueling protocol supported by the hydrogen fuel mobile device and at least one first communication protocol required by at least one first fueling protocol; and an operation of receiving a response message from the communication entity associated with the dispenser, the response message including a second fueling protocol selected from at least one first fueling protocol.

[0016] The first message may include priority information based on a preference of the hydrogen fueled mobile device.

[0017] The response message may include a second fueling protocol selected from the at least one first fueling protocol based on the preferred priority information.

[0018] The response message may include a second fueling protocol selected based on at least one common protocol candidate typically included in the at least one first fueling protocol and at least one fueling protocol supported by the dispenser.

[0019] The response message may include a second fueling protocol selected by the controller of the dispenser from the at least one first fueling protocol.

[0020] The response message may include a second communication protocol required by a second fueling protocol selected by a controller of the dispenser.

[0021] The response message may include a second communication protocol selected by the controller of the dispenser from at least one second communication protocol candidate required for the second fueling protocol.

[0022] The response message may include a second communication protocol selected by the controller of the dispenser from 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 the hydrogen fuel mobile device and the dispenser.

[0023] According to the method for negotiating a hydrogen fueling communication protocol of an exemplary embodiment of the present disclosure, a negotiation request message for negotiating a hydrogen fueling communication protocol between a hydrogen fuel mobile device and a dispenser may be initially transmitted by a communication controller of the hydrogen fuel mobile device to a communication entity associated with the dispenser.

[0024] The method of negotiating a hydrogen fueling communication protocol according to an exemplary embodiment of the present disclosure may further include an operation in which, when a response message is accepted as a response to the negotiation request message, the communication controller of the hydrogen fuel mobile device transmits a confirmation message in response to the response message for negotiation.

[0025] In the operation of sending the first message, the first message may be sent as a negotiation request message to a communication entity associated with the distributor.

[0026] According to another aspect of the exemplary embodiment, the communication control device of the hydrogen fuel mobile device according to the exemplary embodiment of the present disclosure may include a memory storing at least one program instruction and a processor executing at least one program instruction. When executing the at least one program instruction, the processor is capable of: transmitting a first message to a communication entity associated with the dispenser, the first message including at least one first fueling protocol supported by the mobile device for hydrogen fueling and a list of at least one first communication protocol required by the at least one first fueling protocol; and receiving a response message including a second supply protocol from the communication entity associated with the dispenser, the second supply protocol being selected from the at least one first supply protocol.

[0027] In the communication control device of the mobile device supplying hydrogen according to the exemplary embodiment of the present disclosure, the first message may include priority information based on the preference of the mobile device supplying hydrogen.

[0028] In the communication control device of the hydrogen fuel moving device according to the exemplary embodiment of the present invention, the response message may include a second fueling protocol selected from at least one first fueling protocol based on priority information based on preference.

[0029] In the communication control device of the hydrogen fuel mobile device according to an exemplary embodiment of the present invention, the response message may include a second fueling protocol selected according to at least one common protocol candidate generally included in at least one first fueling protocol and at least one fueling protocol supported by the dispenser.

[0030] In the communication control device of the hydrogen fuel moving device according to the exemplary embodiment of the present invention, the response message may include the second fueling protocol selected by the controller of the dispenser from the at least one first fueling protocol.

[0031] In the communication control device of the hydrogen fuel moving device according to the exemplary embodiment of the present invention, the response message may include the second communication protocol required by the second fuel filling protocol of the controller of the dispenser.

[0032] In the communication control device of the hydrogen fuel moving device according to the exemplary embodiment of the present invention, the response message may include the second communication protocol selected by the controller of the dispenser from among at least one second communication protocol candidate required for the second fueling protocol.

[0033] In a communication control device of a mobile device supplying hydrogen fuel according to an exemplary embodiment of the present disclosure, a response message may include a second communication protocol selected by a controller of the dispenser from a plurality of communication protocols required for a second fueling protocol based on a fallback device type determined based on interoperability and / or backward compatibility between the mobile device supplying hydrogen fuel and the dispenser.

[0034] In the communication control device of the mobile device supplying hydrogen according to an exemplary embodiment of the present disclosure, the processor may transmit a negotiation request message for negotiating a communication protocol for supplying hydrogen between the mobile device supplying hydrogen and the dispenser to a communication entity related to the dispenser.

[0035] When accepting the response message as a response to the negotiation request message, the processor may transmit a confirmation message in response to the response message to continue the negotiation.

[0036] The processor may transmit the first message as the negotiation request message to a communication entity associated with the distributor.

[0037] Beneficial Effects

[0038] According to the communication protocol negotiation method of the hydrogen fueling process of the present invention and the device for implementing the method, that is, according to the present invention, the hydrogen fueling controller or the communication controller can overcome the limitations and vulnerabilities of conventional one-way communication for hydrogen fueling of hydrogen fuel mobile devices including fuel cell electric vehicles (FCEV) or hydrogen fuel engines, and improve the safety, compatibility, efficiency and / or reliability of hydrogen fueling.

[0039] Exemplary embodiments of the present disclosure may provide a communication protocol negotiation method for hydrogen fueling and communication protocol fallback rules, wherein a mobile device and a dispenser may select a hydrogen fueling protocol and a communication protocol required for the hydrogen fueling 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.

[0040] According to an exemplary embodiment of the present invention, the rules and principles required for communication protocol negotiation may be provided so that a mobile device and a dispenser can effectively and collaboratively determine an advanced communication medium to effectively achieve hydrogen fueling goals. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 is a diagram of a hydrogen fueling system for a hydrogen electric vehicle (FCEV) according to an exemplary embodiment of the present disclosure, the hydrogen fueling system being adapted to apply a two-way communication process to hydrogen fueling;

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

[0043] 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;

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

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

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

[0047] 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;

[0048] 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;

[0049] Fig. 9 Shows the usage classification of communication data (UCDC) in the two-way communication process of hydrogen fueling according to an exemplary embodiment of the present invention and the backward compatibility of the usage classification of communication data;

[0050] Fig.10 is a sequence diagram showing an authorization process of 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;

[0051] 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;

[0052] 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;

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

[0054] 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;

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

[0056] 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;

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

[0058] Fig.18 is a sequence diagram showing 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;

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

[0060] Fig. 20 A sequence diagram showing 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;

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

[0062] Fig. 22 It is shown that it can be used Fig.21 Block diagram of the software modules of the hydrogen fuel filling device. DETAILED DESCRIPTION

[0063] In order to more clearly understand the features and advantages of the present invention, exemplary embodiments of the present invention 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.

[0064] 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 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.

[0065] In the description of the exemplary embodiments of the present disclosure, “at least one of A and B” may mean “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 mean “one or more of A or B” or “a combination of one or more of A and B”.

[0066] 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. Conversely, 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.

[0067] These terms are used herein only for the purpose of describing specific exemplary embodiments and are not intended to limit the present disclosure. Unless the context clearly dictates otherwise, singular forms also include 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 other features, quantities, processing steps, operations, elements, or parts.

[0068] 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. 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.

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

[0070] Hydrogen electric vehicles may generally include hydrogen fuel cell electric vehicles (FCEVs) using a fuel cell and vehicles having an internal combustion engine (ICE) using hydrogen as fuel. Hydrogen electric vehicles may also be referred to as FCEVs for short.

[0071] Although the embodiments related to hydrogen fuel cell vehicles are described in detail below, 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.

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

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

[0074] “Pressure Release Device (PRD)”: a device arranged in a CHSS and capable of isolating the stored hydrogen from the rest of the fuel filling system and the environment and discharging the hydrogen to the outside.

[0075] "Hydrogen refueling": the process of supplying high-pressure hydrogen gas from a dispenser of a hydrogen refueling station to a vehicle to accumulate the hydrogen gas 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 "filling" as used herein may refer to supplying hydrogen fuel. For example, a refueling protocol may be referred to as a refueling protocol, a refueling period may be referred to as a refueling period, and a refueling method may be referred to as a hydrogen refueling method or a refueling method.

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

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

[0078] “Pre-cooling”: The process of cooling the hydrogen in a hydrogen filling station before fueling.

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

[0080] "Nozzle": a device that is connected to the hydrogen dispensing system of a hydrogen filling station and that can be coupled to a receiver of a hydrogen electric vehicle and supply hydrogen fuel to the hydrogen electric vehicle.

[0081] “Fueling Phase”: Communication sessions that occur within the entire use case scope of hydrogen fueling.

[0082] 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 concept 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 as well as industrial trucks, trains, ships, and airplanes that use hydrogen as a fuel to generate electrical energy and are driven by electrical energy.

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

[0084] In the following description, the hydrogen fuel may include at least one of gaseous hydrogen and liquid hydrogen. The hydrogen fuel basically means compressed hydrogen gas, but is not limited thereto.

[0085] In addition, although the two-way communication process for hydrogen fuel refueling is described in terms of a hydrogen electric vehicle (FCEV) for ease of explanation, the present disclosure is not limited thereto and the hydrogen fuel refueling two-way communication process may also be applied to hybrid electric vehicles (EV) or ICE-type vehicles that use hydrogen as fuel.

[0086] At the same time, if necessary, one or more conventional components may be included in the configuration of the present disclosure, and such 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 conventional components may obscure 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 conventional components, and conventional 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.

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

[0088] Figure 1 is a diagram of a hydrogen fueling system for a hydrogen electric vehicle (FCEV) according to an exemplary embodiment of the present disclosure, the hydrogen fueling system being adapted to apply a two-way communication process to hydrogen fueling. 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 FIG. 1 is a graph showing changes in the state of hydrogen fuel that occur during a hydrogen fueling process in a hydrogen fueling system.

[0089] See also Figure 1 The hydrogen fuel filling system can be generally configured to include a hydrogen fuel filling station and a hydrogen fuel mobile device 100 .

[0090] The hydrogen fuel mobile device 100 may be equipped with an electronic controller 110, a vehicle system 120, a vehicle tank 130, and a container 150 for hydrogen fuel refilling, as well as mechanical devices, electrical devices, electronic devices, and communication devices basically required for a vehicle.

[0091] The electronic controller 110 can send and receive signals and data to and from the hydrogen fuel filling station or the electronic controller 210 of the hydrogen fuel filling station by wired or wireless communication, and process the signals and data to control hydrogen fuel filling on the vehicle side. The electronic controller 110 can be implemented by at least a 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.

[0092] The vehicle system 120 may be connected to the first electronic controller 110 and may be configured to control hydrogen refueling or hydrogen 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. The vehicle system 120 may include a component that controls the operation of the fuel cell system or performs such a control operation according to the implementation, or may be configured to be combined with the component. The vehicle system 120 may be referred to as a vehicle safety system.

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

[0094] 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 of a small storage tank connected in parallel. A boss unit (boss unit) that allows hydrogen fuel to pass through may be coupled to the high-pressure hydrogen storage tank, and therefore the fuel filling and discharge of hydrogen 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.

[0095] The sports facility 100 using hydrogen as fuel 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 a "FCEV," "vehicle," or "mobile device." The terms "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.

[0096] The hydrogen refueling 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 .

[0097] The dispenser 200 can supply hydrogen from the hydrogen tank 230 to the vehicle through a nozzle 250 firmly coupled to the container 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.

[0098] The electronic controller 210 may transmit and receive signals and data to and from 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 filling station side. The electronic controller 210 may exchange prescribed signals and data with the fuel filling station system 220. The electronic controller 210 may also be referred to as a second electronic controller or an electronic control unit #2.

[0099] Each of the first electronic controller 110 and the second electronic controller 210 may include a plurality of electronic control units and may be configured such that each communication protocol may be executed by a different electronic control unit. Such a configuration may be useful when falling back is used for backward compatibility and when bidirectional communication cannot be used and unidirectional communication may be used instead. 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.

[0100] The fuel filling station system 220 may monitor or control the pressure, speed, and temperature of hydrogen gas 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.

[0101] 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.

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

[0103] The hydrogen tank 230 stores hydrogen or compresses 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.

[0104] The station box 240 may be provided with a control valve having an exhaust port connected to the hydrogen tank 230 or an inlet of the exhaust valve and an outlet connected to the dispenser 200 or a nozzle 250 connected 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 gas 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 gas.

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

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

[0107] 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).

[0108] Dispenser 200 may be responsible for interfacing between the hydrogen fuel filling station and mobile device 100. Dispenser 200 may be configured to control a target pressure and 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.

[0109] Generally, there are two methods of transmitting 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 utilizes the information as a safety reference, for example, for emergency stops at temperature or pressure limits. 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.

[0110] At the same time, in order to deal with the hydrogen temperature Figure 3 In order to prevent the increase of the hydrogen fuel filling process shown in the figure, the hydrogen fuel filling station may be equipped with a precooler. The precooler can reduce the temperature of the hydrogen fuel by precooling. The precooler may be installed in at least one of the hydrogen tank 230 and the station box 240 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 fuel filling station.

[0111] The dispenser 200 or the second electronic controller may be equipped with a fueling control logic that may control the hydrogen fueling 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 fueling status information such as the state of charge (SOC) of the CHS.

[0112] 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 filling the vehicle with hydrogen fuel 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.

[0113] For minimum safety requirements, simulations based on thermodynamic modeling can be performed for various situations, and table-based or MC formula-based partial real-time corrections can be performed using parameters derived from the simulations. Minimum safety requirements may include upper limits for temperature and pressure conditions of the CHSS and guidelines for fuel filling rate (SOC).

[0114] In the case where the state value related to hydrogen fueling in the dispenser 200 is not actively controlled, the table-based correction has the disadvantage of showing very low efficiency because the temperature of the pre-cooled hydrogen fuel provided by the fuel filling 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 of 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 under the main goal of safely completing fueling 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 fueling caused by overheating.

[0115] For example, when hydrogen fuel is filled 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 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 may be small compared to the internal temperature rise.

[0116] Meanwhile, the temperature control of the hydrogen fuel filling process may be aimed at ensuring that the internal temperature of the vehicle tank 130 remains below 85° C. when the fuel supply is completed by supplying pre-cooled hydrogen. During the hydrogen fuel filling process, the temperature of the hydrogen fuel may undergo a temperature change according to Figure 3The temperature of the hydrogen fuel can be reduced at a constant rate in stage 1 (P1), which is a pre-cooling stage of the hydrogen fuel filling station. In stage 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 stage 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 stage 4 (P4), during which the hydrogen fuel is compressed and stored in the vehicle tank, the temperature of the hydrogen fuel may increase rapidly due to the heat of compression.

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

[0118] 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 that may employ a two-way communication process for hydrogen fueling is shown.

[0119] Reference Figure 4 The hydrogen fueling framework may include functional blocks for corresponding use cases (UC), including a discovery and pairing functional block (hereinafter referred to as "UC1" or "UC-1"), a communication security 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 entry functional block (UC6 or UC-6), a fueling control and monitoring functional block (UC7 or UC-7), a safety check exit functional block (UC8 or UC-8), a terminal 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).

[0120] 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.

[0121] Use cases are functional blocks that collectively provide the entire hydrogen refueling process of a hydrogen refueling system in a consistent manner for safe and secure refueling communications. Vehicles and dispensers can execute use cases sequentially in a certain order to achieve hydrogen refueling.

[0122] After the nozzle of the dispenser is connected to the container of the vehicle, the vehicle and the dispenser can be connected by Figure 4 The order shown in the example above implements the use cases to perform the fuel filling connection. However, if necessary, the vehicle and the dispenser may omit the occurrence of the use cases according to predetermined requirements.

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

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

[0125] The dispenser may be configured to receive certain data from the vehicle. The dispenser may store specific data in a programmable logic controller (PLC) of the fuel filling station to store data logging data or use in a fuel filling protocol. Data logging may refer to a process of collecting data over 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 sensors specified by the fuel filling protocol, and the PLC or the electronic control unit of the fuel filling station may obtain measurements from the sensors and transmit 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.

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

[0127] The discovery and pairing procedure or pairing process may have as a prerequisite that the nozzle of the dispenser is inserted and securely coupled to the vehicle refueling container. The vehicle refueling container may be referred to simply as the vehicle container or containers.

[0128] 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 the 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.

[0129] 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.

[0130] In terms of the effectiveness of physical pairing, any method for pairing a vehicle with a dispenser may be integrated into the interface between the vehicle and the dispenser or installed so as to maintain proximity between the vehicle's fuel filler container and the nozzle and hose assembly of the dispenser. Here, the interface may refer to something that is physically integrated into the interface between the nozzle and the container. Proximity may be defined by hardware associated with the pairing method. For example, physical geometry for infrared communication may be specified, including the allowed distance between the transmitter and the 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 may result in the risk of associating the dispenser to a vehicle that is not physically connected to the dispenser, 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.

[0131] 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.

[0132] 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 family corresponding to the corresponding layers in the OSI 7 layers, and the OSI 7 layers include a data link layer and a physical layer, a network layer, a transport layer, a security layer, a session layer, a presentation layer, and an application layer.

[0133] 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 a data link and a physical layer of OSI 7 layers.

[0134] 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.

[0135] 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.

[0136] In addition, the hydrogen fuel supply 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.

[0137] In addition, the hydrogen fueling communication stack may include a JSON-based session protocol 550 as a protocol of the session layer of the OS 17 layer. 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 fueling station.

[0138] 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 can be represented in JSON format.

[0139] In addition, the hydrogen fueling communication stack may include a hydrogen fueling related fueling protocol FP570 as a protocol of the application layer of the OS17 layer. 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.

[0140] In an alternative embodiment, the hydrogen fuel supply 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 protocols for the transport and security layers; XML protocols as session layer protocols; and one of the existing protocols used in electric vehicles as protocols 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.

[0141] 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.

[0142] [Table 1]

[0143]

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

[0145] In this use case UC1, the vehicle and the dispenser may try to find a common communication technology to execute the fuel filling protocol. The vehicle and the dispenser may discover each other and initiate communication based on the discovery mechanism 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 fuel filling hose assembly. In cases where the communication channel cannot 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 implicitly ensured, a communication channel integral to the hose assembly, for example, may be sufficient.

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

[0147] refer to Figure 6 , during the pairing process, the vehicle and the dispenser may exchange pairing IDs with each other and discover the pairing IDs of the counterparts during the pairing process at UCDC level 2 and UCDC level 3.

[0148] For example, the vehicle may broadcast a message PAIR_ID_ANNOUNCE containing its pairing ID (PAIR_ID) (ie, vehicle ID) (S710). 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).

[0149] Next, the dispenser may broadcast a message PAIR_ID_ANNOUNCE containing its pairing ID (ie, 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).

[0150] This transmit-echo authentication method enables the vehicle and dispenser to use a session-specific randomized pairing ID. This method 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 for this purpose, the session-specific pairing ID can be included in the data used to establish trust.

[0151] At the same time, when secure communications at a specific UCDC level are 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 keys so that the vehicle and the dispenser can ensure communication during refueling.

[0152] It should be noted that since UCDC Level 1 does not support bidirectional communication, UCDC Level 1 cannot guarantee the security of the communication channel. 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.

[0153] 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.

[0154] Reference Figure 7 In consideration of interoperability, the hydrogen fuel filling device may be designed to have backward compatibility with respect to 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.

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

[0156] A Type 1 device may refer to a device that supports IrDA communications for refueling. A Type 1 device may fall back to a Type 0 device.

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

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

[0159] Advanced communications may refer to communications 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 communications may include two-way IrDA, serial communications, vehicle Ethernet (ETH), advanced communications, and the like. Specific protocols may include transmission control protocol / Internet protocol (TCT / IP), fuel refueling protocol, and the like. Advanced communications may process all information that exceeds that processed by command and control communications. The data link for advanced communications may use power line communications (PLC), but the present disclosure is not limited thereto.

[0160] Advanced communications may include hybrid forms, such as a combination of IrDA communications and wired communications and a combination of IrDA communications and wireless communications. The combination of IrDA communications and wired communications may require modifications to the nozzle and container.

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

[0162] In fact, the hydrogen fuel filling device can be implemented to support different communication protocols. Therefore, the two-way communication process of hydrogen fuel filling according to the present embodiment can be configured to maximize the interoperability between devices.

[0163] 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).

[0164] Furthermore, 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).

[0165] 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).

[0166] 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.

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

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

[0169] In case 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 (which is a Type 1 device). When the nozzle of the cable attached to the dispenser is coupled to the container of the FCEV, IrDA communication can be initiated between the FCEV and the dispenser.

[0170] In case 3, the dispenser can support bidirectional WLAN communication and unidirectional IrDA communication. In this case, the dispenser corresponds to a type 3 device. The FCEV (which 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 connected to the container of the FCEV, IrDA communication can be started between the FCEV and the dispenser.

[0171] 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.

[0172] refer to Figure 8 The two-way communication process for hydrogen fueling according to the present embodiment may provide rules and principles for fallback when selecting a fueling method and communication protocol to maximize interoperability, rather than selecting the communication protocol most preferred by the FCEV or dispenser.

[0173] That is, when a vehicle or dispenser encounters another, 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.

[0174] 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.

[0175] 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 ISO19885 standard.

[0176] Under the above configuration, if the vehicle and the distributor have the same or the same type implementation 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 protocol. When two devices supporting two-way communication meet each other, the two devices can maintain the original two-way communication protocol. 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").

[0177] 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 protocol and the two-way communication protocol, the two-way communication device can fall back to the one-way communication protocol. 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 protocol.

[0178] The above two-way communication device, whether or not it has one-way communication capability, can 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 protocol that is compatible between the devices.

[0179] Fig. 9 The usage classification of communication data (UCDC) in the two-way communication process of hydrogen fuel refueling according to the exemplary embodiment of the present invention and the backward compatibility of the usage classification of communication data are shown.

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

[0181] In the case of UCDC level 0 (UCDC-0) 900, data is not transmitted. Even if data is transmitted, the transmitted 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.

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

[0183] Static data transmitted at UCDC level 2 (UCDC-2) 920 may be used for a safety 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 for permitted use.

[0184] 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 safety 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 for permitted use.

[0185] 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, more advanced functions and / or effects may include lower-level functions and / or effects. A device supporting a certain UCDC level may support a device of a lower UCDC level. Devices capable of supporting different UCDC levels may use the highest UCDC level supported by two devices. The above-mentioned UCDC level can 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 can be effectively applied to each or a combination of no communication protocol (Non-Comm), a unidirectional communication protocol (Uni-directionalComm), and a bidirectional communication protocol (Bi-directionalComm), regardless of the UCDC level.

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

[0187] Reference 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).

[0188] Next, the FCEV may send an authorization request message including an authorization method selected from a list of authorization methods such as RFID 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.

[0189] Then, the FCEV may wait for a response containing the authorization result from the dispenser, and may send an authorization result request message (Complete?) for the selected authorization method to the dispenser (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 dispenser may send an authorization completion message ("Complete (Success)") to the FCEV (S1090).

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

[0191] To ensure the security of the authorization process, a hydrogen refueling 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.

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

[0193] 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.

[0194] 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.

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

[0196] If the vehicle sends a certificate request message along with a handshake message such as ServerHello but the distributor 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.

[0197] 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.

[0198] Reference Fig.11 During the communication protocol negotiation process, the FECV and the distributor 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 distributor (S1110).

[0199] 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 the SAE standard or the ISO standard, for example. 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.

[0200] 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).

[0201] 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).

[0202] 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.

[0203] 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 for hydrogen refueling during the two-way communication process.

[0204] In actual implementations, various combinations may exist between FCEV and the dispenser according to hydrogen fueling communication standards, communication modes, fueling methods, communication levels, and other parameters. Here, hydrogen fueling communication standards may include SAEJ2601 series, ISO19885-3, and ISO19885-4 standards. Communication modes may include no communication, IrDA, XYZ (ISO), etc. Fueling methods may include table-based fueling methods (e.g., lookup table-based methods) and MC formula-based fueling methods. These communication levels may include UCDC levels, and other parameters may include pressure categories, categories of compressed hydrogen storage systems (CHSS), hydrogen fueling tables, etc.

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

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

[0207] 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.

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

[0209] 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.

[0210] 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.

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

[0212] [Table 2]

[0213] Protocol ID Priority SAE J2601-No communication (No comm.) 7 SAE J2799-IrDA 6 SAE J2601-IrDA 5 ISO 19885-3-2023-UCDC-0 4 ISO 19885-3-2023-UCDC-1 3 ISO 19885-3-2023-UCDC-2 2 ISO 19885-3-2023-UCDC-3 1

[0214] 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 negotiate a fueling protocol for a 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.

[0215] According to an exemplary embodiment of the present disclosure, a method for negotiating a communication protocol for hydrogen fuel refueling performed by a communication controller 100 of a hydrogen fuel mobile device may include: operation S1210, transmitting a first message to a communication entity associated with a dispenser 200, the first message including at least one first fuel refueling protocol supported by the hydrogen fuel mobile device and a list of at least one first communication protocol required for at least one 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.

[0216] 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.

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

[0218] The response message may include a second fueling protocol determined (selected) from at least one first fueling protocol according to the priority information based on the preference. The mobile device 100 side or the dispenser 200 side may determine (select) the second fueling protocol based on the priority information, which is based on the preference, either 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 alternatively be performed by the dispenser 200 side.

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

[0220] 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.

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

[0222] 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.

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

[0224] Refer to Fig.11 and Fig.12 According 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 transmitted by a communication controller of the hydrogen fuel mobile device 100 to a communication entity associated with the dispenser 200.

[0225] 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 controller 100 of the hydrogen fuel mobile device transmits a confirmation message in response to the response message to negotiate.

[0226] 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 .

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

[0228] The fueling protocol negotiation process may include operations in which a mobile device or dispenser exchanges detailed parameters required for a fueling protocol. The mobile device may include a FCEV.

[0229] 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).

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

[0231] The compatibility-related parameters may include pressure classes and CHSS classes. The physical property-related parameters may include maximum allowable CHSS pressure, maximum allowable CHSS temperature, maximum allowable flow rate, and CHSS volume. The monitoring parameters may include current CHSS pressure and current CHSS temperature. The acceptance-related parameters may include information indicating whether it is accepted (i.e., a parameter 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 main UCDC levels.

[0232] 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 in Fig.12 The protocol negotiation shown in the figure handles the case of links between each other, and the dispatcher can use Figure 3 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.

[0233] 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 acceptance related parameters.

[0234] Compatibility-related parameters may include fuel supply delivery temperature and selected fuel supply station. Physical property-related parameters may include maximum fuel delivery pressure, maximum fuel delivery temperature, minimum fuel delivery temperature, and maximum fuel delivery flow rate. Fueling target parameters may include target SOC, target final CHSS pressure, target final CHSS temperature, target APR, and target or expected fueling duration. Monitoring parameters may include current fuel delivery temperature and ambient temperature. Acceptance-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.

[0235] 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.

[0236] The dispatcher may include information about the second parameter supported by the dispatcher and information about the first parameter ( Fig.13 in <ok>”) sends a response message of the information of the parameters selected in the process to the FCEV (S1330).

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

[0238] [Table 3]

[0239] 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

[0240] 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 sub-schema is available, and reference information (such as priority) for the fueling methods or fueling protocols supported by the dispenser.

[0241] Similar to the vehicle, the distributor may be proactive in exchanging the communication protocols and parameters with the vehicle, or may be configured to prioritize the communication protocols supported by the distributor so as to provide information of the prioritized communication protocols to the vehicle.

[0242] In Table 3, PRHYDE (Protocol for Heavy Duty HYDrogEn Refueling) 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 refueling situations.

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

[0244] [Table 4]

[0245] Fuel Protocol ID Result Codes 2 OK

[0246] 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.

[0247] [Table 5]

[0248] Fuel Protocol ID Result Codes FAIL_NO_COMMON_PROTOCOL

[0249] 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.

[0250] 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 can perform a compatible fueling process. Here, the information required to perform a safe and efficient fueling process may include compatibility-related parameters, physical property-related parameters, fueling target parameters, and monitoring parameters.

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

[0252] 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 providing fuel to the dispenser. During the communication protocol negotiation process after a refueling parameter exchange failure, the FCEV may propose a set of supported protocols to the dispenser, excluding the protocol that failed during the refueling parameter exchange process.

[0253] After the refueling protocol is established in the above use case UC-4, the vehicle and the dispenser may establish 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 the 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 cases UC-3 and UC-1 cannot be performed normally, the dispenser and the FCEV may terminate the current communication.

[0254] According to the above configuration, some fuel filling protocols may be executed based on no communication protocol. Another fuel filling protocol may require one-way IrDA communication. Another fuel filling protocol may require two-way communication. Another fuel filling protocol may require both two-way communication and one-way IrDA communication.

[0255] 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.

[0256] 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.

[0257] like Fig.14 As shown, the vehicle and the dispenser may determine the detailed parameters required to execute the selected fueling protocol at 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 negotiation of the fueling parameter begins. During the parameter exchange, the vehicle and the dispenser may determine whether the vehicle and the dispenser can execute the fueling protocol.

[0258] 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 receiving party receiving the parameters from a sending party may send a response message to the sending party 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.

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

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

[0261] [Table 6]

[0262]

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

[0264] [Table 7]

[0265]

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

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

[0268] The compatibility-related parameters may include container type, pressure category, CHSS category, CHSS type, CHSS capacity, maximum allowable CHSS pressure, maximum allowable CHSS temperature, and maximum allowable flow rate. The monitoring parameters may include current CHSS pressure and current CHSS temperature. The safety policy-related parameters may include emergency policy and safety enforcement level. The acceptance-related parameters may include information indicating whether it is accepted, i.e., a parameter indicating yes (true), no (false), or pending.

[0269] 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).

[0270] Fourth parameters related to the fueling parameter negotiation may include physical property related parameters, monitoring parameters, fueling target parameters, safety policy related parameters, and acceptance related parameters.

[0271] Physical property related parameters may include maximum fuel delivery pressure, maximum fuel delivery temperature, minimum fuel delivery temperature, and maximum fuel delivery flow rate. 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. Acceptance 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 stages.

[0272] 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.

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

[0274] 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 represent a value or information contained in a result code field, and the failure may represent a negative failure at a specific time and may be represented by an indication of incompatibility, for example, "Fail_uncompatibil".

[0275] 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 “reason” set to a predetermined error code.

[0276] 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 registration. This operation is optional, but it is desirable to define a dedicated safety check procedure in the fuel filling protocol in order to ensure the desired safety level in a precise and unambiguous way.

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

[0278] During the safety check, the dispenser and the vehicle, including the FCEV, can check whether all necessary safety conditions are met before the actual refueling begins.

[0279] After the fueling parameters are changed and the vehicle and dispenser are deemed compatible, the vehicle and dispenser may perform a safety status check to determine if the fueling can 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 process may be omitted.

[0280] During the safety check process, the vehicle and / or dispenser may check that the engagement of the nozzle and receiver is locked, check for any leaks, and check last minute status.

[0281] In the event that the vehicle has received a Fueling Parameters Negotiation Response message from the dispenser and the fueling protocol supports secure registration, the vehicle may initiate the secure registration process by sending a secure registration request message to the dispenser within a message sequence set time interval.

[0282] 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.

[0283] 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 capacity together with information indicating that the leak check is completed ("completed") to the vehicle (S1570).

[0284] 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).

[0285] 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 connector lock state, leak check state, and predicted FCEV tank capacity to the vehicle.

[0286] After completing the above safety check 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.

[0287] 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.

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

[0289] In addition, the vehicle may send certain commands to the dispenser to control the fuel filling process, such as the start or end of fuel filling. 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 principles to ensure secure communication, although the output characteristics of the communication channel may be unsecure or have attributes that are irrelevant to the application.

[0290] 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).

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

[0292] 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).

[0293] 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 status response message including information that the fuel filling is stopping or has stopped to the vehicle (S1690).

[0294] 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.

[0295] 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.

[0296] 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 rate, current fuel delivery temperature, pre-cooling temperature, current fuel delivery pressure, whether full fueling is used, whether a cooled dispenser is used, whether fallback is used, the reason for the fueling stop, and the amount of hydrogen currently being delivered.

[0297] 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.

[0298] Meanwhile, when TCP is used in the monitoring and control process, if the safety check response message or the safety check process according to the fuel filling protocol is omitted, after receiving the fuel filling parameter negotiation response message from the dispenser, the vehicle may transmit the fuel filling loop request message to the dispenser within the message sequence setting time interval. The request message or response message related to the fuel filling loop may be transmitted through the DTLS message.

[0299] 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 security checkout use case before terminating the session and separating the nozzle from the vehicle. The security check-in process may be optional, but it is desirable to define a dedicated security check-in process in the refueling protocol to ensure the desired level of safety in a precise and unambiguous manner.

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

[0301] The vehicle and dispenser can check that all necessary safety conditions are met before the dispenser's nozzle is disconnected from the vehicle's container through a safety check process. 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.

[0302] For example, if the vehicle receives a fueling loop response message from the dispenser having a "result" attribute set to "OK" or a "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 checks, the vehicle may start the safety check and perform the safety check process by transmitting a safety check request message to the dispenser within a message sequence set time period.

[0303] 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 the safety check may be omitted.

[0304] More specifically, if Fig.17 As shown, the vehicle may send a message containing information about a 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).

[0305] In addition, the vehicle may again send a message containing information about the coupling inspection result (eg, “OK”) to the distributor (S1750), and the distributor may send a message containing information indicating that the coupling inspection is completed (eg, “Completed”) to the vehicle (S1770).

[0306] When the coupling check result shows that the coupling check is completed normally, the user or operator may separate the nozzle of the dispenser from the container of the vehicle.

[0307] During the secure checkout process, the report message sent by the dispenser to the vehicle may include information or parameters about the coupling unlock status. The coupling unlock status information may include information of lock, unlock, ice or problem.

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

[0309] 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.

[0310] 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 reason 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.

[0311] For example, after the vehicle receives a secure checkout response message (wherein the "result" attribute is set to "complete") or a fuel filling loop response message (wherein the "status" attribute is set to "complete") or information including stopping fuel filling from the dispenser, the vehicle may transmit a termination request message to the dispenser to perform the termination process.

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

[0313] 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).

[0314] After completing the fueling and performing the safety checks, the vehicle and the dispenser may exchange at least some bookkeeping information for the fueling phase of the hydrogen fueling in the termination process. Prior to completing the termination process, the vehicle and the dispenser may exchange summary information about the hydrogen fueling phase.

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

[0316] 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 transmitted 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 supplied.

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

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

[0319] [Table 8]

[0320]

[0321]

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

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

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

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

[0326] If the vehicle detects an event related to an unimportant safety 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.

[0327] When a non-critical safety error is detected in the vehicle and the communication channel maintains an operational 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".

[0328] A Terminate Request message may be sent in error situations, which do not include unrecoverable situations such as safety non-critical communication errors, system errors, or qualitative errors.

[0329] 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 can prevent refueling from proceeding. The error handler can define non-trivial safety error conditions and provide exemplary error conditions and possible responses.

[0330] 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 communication performance does not meet a required level or where the quality of data integrity or accuracy does not meet a required level.

[0331] According to the bidirectional communication process for hydrogen fueling of the present embodiment, the following specific error processing procedures as shown in (1) to (4) can be executed for the above-mentioned error conditions.

[0332] (1) In the event that no safety error occurs and further communication is not possible, the vehicle and dispenser may immediately stop refueling, but may take safety actions and terminate the session by ceasing communication.

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

[0334] (3) In the event that a non-critical safety 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.

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

[0336] 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 perform an error handling process including notification, termination process and fallback mechanism when an error is detected according to the detection criteria.

[0337] On the other hand, during the refueling process of the hydrogen refueling system, when a safety problem occurs, emergency action is sometimes required.

[0338] 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.

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

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

[0341] The 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 hazardous situations.

[0342] 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 (e.g., "Emergency: Stop (High Pressure)") including information requesting a fuel filling stop to the dispenser according to the high pressure (S2010). The dispenser may send a response message (e.g., "Emergency: Stop") to the vehicle including information indicating that the dispenser is processing an emergency fuel supply stop in response to the first emergency stop request message (S2020).

[0343] In addition, upon receiving the response message or after a preset time has passed since the response message was received, the vehicle may resend the first emergency stop request message to the dispenser (S2030). After the emergency stop of 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).

[0344] 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 to the dispenser (e.g., "Emergency: Confirmed") (S2070).

[0345] 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).

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

[0347] When receiving the emergency notification message, the vehicle or the 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 category, type, and action of the emergency notification.

[0348] Emergency notification messages can be transported by TLS or DTLS messages, depending on the technology used for communication.

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

[0350] refer to Fig.21 The hydrogen fuel supply 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 .

[0351] 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 also be a device that receives hydrogen fuel filling services, or a hydrogen fuel filling control unit or communication unit included in the device.

[0352] 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.

[0353] 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.

[0354] 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).

[0355] The hydrogen fuel filling device 3000 may perform at least a portion 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 a portion of the steps of the two-way process or method can be performed by at least one processor 3100 loading and executing program instructions from the memory 3200.

[0356] In addition, the hydrogen fuel filling device 3000 may include the following: Figure 4 In addition to the functional modules UC1-UC11 described above, the following Fig. 22 Functional modules 3110 - 3180 are shown. These functional modules 3110 - 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 .

[0357] Functional modules 3110-3180 may include a first functional module 3110 for version negotiation, a second functional module 3120 for session allocation, a third functional module 3130 for service negotiation, a fourth functional module 3140 for payment negotiation, a fifth functional module 3150 for authentication, a sixth functional module 3160 for exchanging fueling parameters, a seventh functional module 3170 for fueling, and an eighth functional module 3180 for stopping / pausing fueling.

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

[0359] The second function block 3120 may allocate an IP address, an IPv6 address, a session identifier, etc. by the vehicle or a distributor.

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

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

[0362] The fifth functional block 3150 may process at least one of user authentication, vehicle authentication, dispenser authentication, and hydrogen filling station authentication. The fifth functional block 3150 may correspond to at least a portion of the functional block of the discovery and pairing use case UC1.

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

[0364] The seventh function block 3170 can monitor and control the fuel filling process, and can correspond to at least a portion 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 registration use case UC6, the monitoring and control use case UC7, the safety registration use case UC8 and the terminal use case UC9.

[0365] 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 a portion of a combination of the error handling use case UC10 and the emergency handling use case UC11.

[0366] In addition, the above-mentioned hydrogen fuel filling device 3000 may be equipped with various types of computing devices installed on a vehicle or a dispenser. The computing device may be any data processing device capable of communicating over 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).

[0367] 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 3200 stores at least program instructions, and the processor 3100 executes the at least program instructions. When executing the at least one program instruction, the processor 3100 may be configured to: transmit a first message to a communication entity associated with the dispenser 200, the first message including at least one first fuel filling protocol supported by the hydrogen fuel mobile device and a list of at least one first communication protocol required by the at least one first fuel filling protocol; and receive a response message including a second fuel filling protocol selected from the at least one first fuel filling protocol from the communication entity associated with the dispenser 200.

[0368] In the communication control device of the mobile device supplying hydrogen according to the exemplary embodiment of the present disclosure, the first message may include priority information based on the preference of the mobile device supplying hydrogen.

[0369] In the communication control device of the hydrogen fuel moving device according to the exemplary embodiment of the present invention, the response message may include a second fueling protocol selected from at least one first fueling protocol based on priority information based on preference.

[0370] In the communication control device of the hydrogen fuel mobile device according to an exemplary embodiment of the present invention, the response message may include a second fueling protocol selected according to at least one common protocol candidate generally included in at least one first fueling protocol and at least one fueling protocol supported by the dispenser 200.

[0371] In the communication control device of the hydrogen fuel moving device according to the exemplary embodiment of the present invention, the response message may include the second fueling protocol selected by the controller of the dispenser 200 from the at least one first fueling protocol.

[0372] In the communication control device of the mobile device supplying hydrogen fuel according to the exemplary embodiment of the present disclosure, the response message may include the second communication protocol for the second fuel filling protocol required by the controller of the dispenser 200 .

[0373] In the communication control device of the mobile device for hydrogen supply according to the exemplary embodiment of the present disclosure, the response message may include the second communication protocol selected by the controller of the dispenser 200 from among at least one second communication protocol candidate required for the second supply protocol.

[0374] In the communication control device of the mobile device for supplying hydrogen fuel according to an exemplary embodiment of the present disclosure, the response message may include a second communication protocol selected by the controller of the dispenser 200 from a plurality of communication protocols required for the second fueling protocol based on a fallback device type determined based on the interoperability and / or backward compatibility between the mobile device 100 for supplying hydrogen fuel and the dispenser 200.

[0375] In the communication control device of the mobile device supplying hydrogen according to an exemplary embodiment of the present disclosure, the processor 3100 may transmit a negotiation request message for negotiating a communication protocol for supplying hydrogen between the mobile device 100 supplying hydrogen and the dispenser 200 to a communication entity related to the dispenser 200.

[0376] When the response message is accepted as a response to the negotiation request message, the processor 3100 may send a confirmation message in response to the response message to continue the negotiation.

[0377] The processor 3100 may send the first message as a negotiation request message to a communication entity related to the distributor 200 .

[0378] On the other hand, although most of the above embodiments focus on the method in which the vehicle first transmits 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 transmits the communication protocol or parameters of the distributor to the vehicle. This embodiment has substantially the same features as the above embodiments except for the change of the transmitter and the receiver.

[0379] 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.

[0380] 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 advanced language codes executable by a computer using an interpreter, etc.

[0381] Some aspects of the present invention described above in the context of the device may indicate the corresponding description of the method according to the present invention, and the block or device may correspond to the operation of the method or the feature of the operation. Similarly, some aspects described in the context of the method may be expressed by the feature of a block, project or a device corresponding thereto. Some or all operations of the method may be performed using hardware devices (e.g., microprocessors, programmable computers, or electronic circuits). In some exemplary embodiments, one or more of the most important operations of the method may be performed by such a device.

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

[0383] 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 hydrogen fuel filling communication protocol negotiation method, executed by a communication controller of a hydrogen fuel mobile device, the method comprising: sending a first message to a communication entity associated with a dispenser, the first message including a list of at least one first fueling protocol supported by the hydrogen fuel mobile device and at least one first communication protocol (communication protocol) required by the at least one first fueling protocol (fueling protocol); and A response message is received from the communication entity associated with the dispenser including a second fueling protocol selected from the at least one first fueling protocol.

2. The method according to claim 1, wherein: The first message includes priority information based on a preference of the hydrogen fuel mobile device.

3. The method according to claim 2, wherein: The response message includes the second fueling protocol selected from the at least one first fueling protocol according to the priority information based on the preference.

4. The method according to claim 1, wherein: The response message includes the second fueling protocol selected from at least one common protocol candidate commonly included by the at least one first fueling protocol and at least one fueling protocol supported by the dispenser.

5. The method according to claim 1, wherein: The response message includes the second fueling protocol selected by a controller of the dispenser from among the at least one first fueling protocol.

6. The method according to claim 5, wherein: The response message includes a second communication protocol required by the second fueling protocol selected by the controller of the dispenser.

7. The method according to claim 6, wherein: The response message includes the second communication protocol selected by the controller of the dispenser from among at least one second communication protocol candidate required by the second fueling protocol.

8. The method according to claim 7, wherein: The response message includes the second communication protocol selected by the controller of the dispenser from a plurality of communication protocols required for the second fueling protocol based on a fallback (fallback) device type determined based on one or more of interoperability (interoperability) and backward compatibility (backward compatibility) between the hydrogen fuel mobile device and the dispenser.

9. The method according to claim 1, further comprising: The communication controller of the hydrogen fuel mobile device sends a negotiation request message for negotiating a communication protocol between the hydrogen fuel mobile device and the dispenser to the communication entity associated with the dispenser, and A confirmation message is sent by the communication controller of the hydrogen fuel mobile device in response to the response message to negotiate, wherein the response message is accepted as a response to the negotiation request message.

10. The method according to claim 9, wherein: The first message is sent as the negotiation request message to the communication entity associated with the allocator.

11. 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 message to a communication entity associated with a dispenser, the first message including a list of at least one first fueling protocol supported by the hydrogen fuel mobile device and at least one first communication protocol (communication protocol) required by the at least one first fueling protocol (fueling protocol); and A response message is received from the communication entity associated with the dispenser including a second fueling protocol selected from the at least one first fueling protocol.

12. The communication control device according to claim 11, wherein: The first message includes priority information based on a preference of the hydrogen fuel mobile device.

13. The communication control device according to claim 12, wherein: The response message includes the second fueling protocol selected from the at least one first fueling protocol according to the priority information based on the preference.

14. The communication control device according to claim 11, wherein: The response message includes the second fueling protocol selected from at least one common protocol candidate commonly included by the at least one first fueling protocol and at least one fueling protocol supported by the dispenser.

15. The communication control device according to claim 11, wherein: The response message includes the second fueling protocol selected by a controller of the dispenser from among the at least one first fueling protocol.

16. The communication control device according to claim 15, wherein: The response message includes a second communication protocol required by the second fueling protocol selected by the controller of the dispenser.

17. The communication control device according to claim 16, wherein: The response message includes the second communication protocol selected by the controller of the dispenser from at least one second communication protocol candidate required by the second fueling protocol.

18. The communication control device according to claim 17, wherein: The response message includes the second communication protocol selected by the controller of the dispenser from a plurality of communication protocols required for the second fueling protocol based on a fallback (fallback) device type selected based on one or more of interoperability (interoperability) and backward compatibility (backward compatibility) between the hydrogen fuel mobile device and the dispenser.

19. The communication control device according to claim 11, wherein: The processor is further configured to: A negotiation request message for communication protocol negotiation between the hydrogen fuel mobile device and the dispenser is sent to the communication entity associated with the dispenser, and a confirmation message is sent in response to the response message to negotiate, wherein the response message is accepted as a response to the negotiation request message.

20. The communication control device according to claim 19, wherein: The processor is configured to send the first message as the negotiation request message to the communication entity associated with the allocator.

Images