Communication method and apparatus for monitoring and controlling hydrogen refueling

Abstract

This invention provides a communication method for hydrogen fuel supply that can improve safety, compatibility, efficiency, and reliability in hydrogen refueling for hydrogen fuel mobility. [Solution] The communication method for hydrogen fuel supply according to the present invention includes the steps of: a hydrogen fuel mobility vehicle transmitting a request message to a dispenser containing information relating to an action, including the commencement or cessation of hydrogen fuel supply, based on a fuel supply protocol determined by negotiation between the dispenser and the hydrogen fuel mobility vehicle; and a hydrogen fuel mobility vehicle receiving a response message from the dispenser containing information regarding whether it has processed or is ready to process the action included in the request message.

Description

Technical Field

[0001] The present invention relates to a communication technology for hydrogen fueling of hydrogen fueled mobility, and more particularly, to a hydrogen fueling process that can improve the safety, compatibility, efficiency, and reliability of hydrogen fueling, a monitoring and control method for the hydrogen fueling process, a safety check-in method, a safety check-out method, and an apparatus using the same.

Background Art

[0002] The content described in this section is merely provided as background information for this example and does not provide prior art.

[0003] A hydrogen vehicle or a hydrogen electric vehicle means a pollution-free vehicle that runs on electric energy generated by high-pressure hydrogen stored in the vehicle and air in the atmosphere. A hydrogen electric vehicle is sometimes also called a fuel cell electric vehicle (FCEV). Most hydrogen electric vehicles utilize hydrogen as an energy source and use a fuel cell system to produce electricity and move. In a hydrogen electric vehicle, not only pure water (H2O) is discharged during the process of generating electricity, but it also has a function of removing ultrafine dust in the atmosphere during operation, so it is attracting attention as a mobility friendly to the future environment. As a technology with potential that can be utilized in the entire industry in terms of the fact that hydrogen as a fuel is infinite on the earth and the process of producing energy is environmentally friendly, it has been widely in the spotlight.

[0004] Hydrogen-fueled mobility refers to a type of mobility that uses hydrogen as an energy source or generates electrical energy using hydrogen as fuel, which is then used to drive electric motors. In addition to the aforementioned hydrogen electric vehicles, hydrogen-fueled mobility includes aerial mobility, as well as industrial trucks, trains, ships, and aircraft, and includes devices that generate electrical energy using hydrogen as fuel and use it for propulsion.

[0005] Most hydrogen fuel cell vehicles (HEVs) safely store high-pressure hydrogen in hydrogen fuel storage tanks and supply oxygen through an air supply system to a fuel cell stack, where an electrochemical reaction occurs between hydrogen and oxygen to produce electrical energy. The produced electrical energy is converted into kinetic energy through a drive motor to power the HEV, and while driving, HEVs have the advantage of emitting only pure water through an exhaust port.

[0006] On the other hand, while the concept of a hydrogen fueled car (hydrogen-fueled car) is also a vehicle that uses hydrogen as fuel, a hydrogen fueled car uses a system where hydrogen is directly burned in an engine (ICE, Internal Combustion Engine) to generate heat that drives an electric motor. The method of refueling a hydrogen fueled car with hydrogen is not much different from the method of refueling a hydrogen fueled car with hydrogen.

[0007] Control techniques for supplying hydrogen to vehicles that utilize hydrogen as fuel ultimately aim to control the temperature and pressure of the compressed hydrogen storage system (CHSS) on the fuel cell side to operate under critical temperature and pressure conditions necessary for safe hydrogen refueling.

[0008] Conventional hydrogen refueling processes, control techniques, and protocols for hydrogen-electric vehicles were defined in a time when wired / wireless technologies and computing techniques for control were not yet mature, and do not adequately reflect the latest advancements in information and communication technology (ICT). Consequently, conventional hydrogen refueling technologies for hydrogen-electric vehicles are inefficient, slow, and unsuitable for large-volume hydrogen refueling.

[0009] In particular, in the case of hydrogen refueling communication, most hydrogen refueling control devices utilize unidirectional infrared communication devices, and therefore, even wireless-based hydrogen refueling communication still suffers from the limitations and vulnerabilities of unidirectional communication. [Overview of the Initiative] [Problems that the invention aims to solve]

[0010] The object of the present invention, in order to solve the aforementioned problems, is to provide a hydrogen fueling process for hydrogen fueled mobility, a communication protocol for the process that overcomes the limitations and vulnerabilities of existing unidirectional communication and can improve the safety, compatibility, efficiency and reliability of hydrogen fueling, a communication protocol negotiation method for the hydrogen fueling process, a fueling protocol negotiation method, a fueling parameter negotiation method, a monitoring and control method, a safety check-in method, a safety check-out method, and an apparatus utilizing the same. Another object of the present invention is to provide a hydrogen refueling communication bidirectional process that can be controlled to determine whether a conventional or advanced communication medium is used in order for hydrogen fuel mobility and dispensers to effectively achieve their fueling goal, a communication protocol negotiation process that takes bidirectional / unidirectional communication into consideration, and an apparatus that utilizes the same. [Means for solving the problem]

[0011] A communication method for hydrogen fuel supply according to one embodiment of the present invention for achieving the above objective is a communication method for hydrogen fuel supply (fueling) performed by a communication device of a hydrogen fuel mobility, characterized by comprising the steps of: transmitting a request message to a dispenser that includes information relating to an action including the start or stop of hydrogen fuel supply, based on a fuel supply protocol determined by negotiation between a dispenser that supplies hydrogen to the hydrogen fuel mobility and the hydrogen fuel mobility; and receiving a response message from the dispenser that includes information regarding whether the action included in the request message has been processed or is ready to be processed.

[0012] The request message may include information related to the action of initiating hydrogen fuel supply, and the response message may include information on whether the dispenser is ready to begin hydrogen fuel supply.

[0013] A communication method for hydrogen fuel supply according to one embodiment of the present invention may further include the step of transmitting a second request message containing information related to the hydrogen fuel supply initiation action if the response message indicates that the dispenser is not ready to begin hydrogen fuel supply.

[0014] The request message may include information regarding the action of halting the hydrogen fuel supply, and the response message may include information regarding whether the dispenser has halted the hydrogen fuel supply.

[0015] A communication method for hydrogen fuel supply according to one embodiment of the present invention may further include the step of transmitting a second request message containing information related to the hydrogen fuel supply cessation action if the response message indicates that the dispenser has not completely ceased hydrogen fuel supply.

[0016] A request message may include a monitoring request regarding at least one condition related to the hydrogen fuel supply procedure, and a response message may include information about at least one condition.

[0017] A communication method for hydrogen fuel supply according to one embodiment of the present invention may further include a step of checking in the safety status of the hydrogen fuel mobility or the dispenser by message exchange between the hydrogen fuel mobility and the dispenser before transmitting a request message, after fuel supply parameters based on a fuel supply protocol have been negotiated between the hydrogen fuel mobility and the dispenser.

[0018] A communication method for hydrogen fuel supply according to one embodiment of the present invention may further include a step of checking the safety status on the hydrogen fuel mobility or dispenser side by exchanging messages between the hydrogen fuel mobility and the dispenser before the nozzle is unplugged, if the response message indicates that the hydrogen fuel supply has finished or stopped.

[0019] A communication device for hydrogen fuel mobility according to one embodiment of the present invention includes a memory for storing at least one instruction and a processor for executing at least one instruction, wherein the processor can transmit a request message to a dispenser containing information related to an action, including starting or stopping hydrogen fuel supply, based on a fuel supply protocol determined by negotiation between the dispenser and the hydrogen fuel mobility, and receive a response message from the dispenser containing information regarding whether it has processed or is ready to process the action included in the request message.

[0020] The request message may include information related to the action of initiating hydrogen fuel supply, and the response message may include information on whether the dispenser is ready to begin hydrogen fuel supply.

[0021] If the response message indicates that the dispenser is not ready to start the hydrogen fuel supply, the processor can additionally transmit a second request message containing information related to the action of starting the hydrogen fuel supply.

[0022] The request message can include information regarding the action of stopping the hydrogen fuel supply, and the response message can include information regarding whether the dispenser has stopped the hydrogen fuel supply.

[0023] If the response message indicates that the dispenser has not completely stopped the hydrogen fuel supply, the processor can additionally transmit a second request message containing information related to the action of stopping the hydrogen fuel supply.

[0024] The request message can include a monitoring request regarding at least one or more states related to the hydrogen fuel supply procedure, and the response message can include information on at least one or more states.

[0025] The processor can check in the safety status on the hydrogen fuel mobility or dispenser side through message exchange between the hydrogen fuel mobility and the dispenser before transmitting the request message, in a state where fuel supply parameters based on the fuel supply protocol have been negotiated between the hydrogen fuel mobility and the dispenser.

[0026] When the response message indicates that the hydrogen fuel supply has finished or stopped, the processor can check out the safety status on the hydrogen fuel mobility or dispenser side through message exchange between the hydrogen fuel mobility and the dispenser before the nozzle is unplugged.

[0027] A communication device of a dispenser for supplying hydrogen fuel to a hydrogen fuel mobility according to an embodiment of the present invention includes a memory storing at least one or more instructions and a processor executing at least one instruction. The processor can receive a request message including information related to an action including start or stop of hydrogen fuel supply from the dispenser in a state where fuel supply protocol negotiation between the hydrogen fuel mobility and the dispenser is completed, and transmit a response message including information on whether the action included in the request message has been processed or is ready to be processed to the hydrogen fuel mobility, which is characterized in that.

[0028] A communication method for hydrogen fueling performed by a dispenser for supplying hydrogen fuel to a hydrogen fuel mobility according to an embodiment of the present invention includes receiving a request message including information related to an action including start or stop of hydrogen fuel supply from the dispenser in a state where fuel supply protocol negotiation between the hydrogen fuel mobility and the dispenser is completed completed completed, and transmitting a response message including information on whether the action included in the request message has been processed or is ready to be processed to the hydrogen fuel mobility, which is characterized in that.

[0029] The response message can include information on whether the dispenser is in the process of or has stopped hydrogen fuel supply.

[0030] When the response message indicates that the dispenser has stopped hydrogen fuel supply, the response message can include information on whether the dispenser has stopped hydrogen fuel supply based on the stop action included in the request message of the hydrogen fuel mobility or on whether the hydrogen fuel supply target of the hydrogen fuel mobility has been achieved and the hydrogen fuel supply has ended.

[0031] A request message may include a monitoring request regarding at least one condition related to the hydrogen fuel supply procedure, and a response message may include information about at least one condition.

[0032] A communication method for supplying hydrogen fuel according to one embodiment of the present invention may further include the steps of checking in the safety status of the hydrogen fuel mobility or dispenser by message exchange between the hydrogen fuel mobility and the dispenser before receiving a request message, with fuel supply parameters based on a fuel supply protocol having been negotiated between the hydrogen fuel mobility and the dispenser, and checking in the safety status of the hydrogen fuel mobility or dispenser by message exchange between the hydrogen fuel mobility and the dispenser before the nozzle is unplugged if the response message indicates that the hydrogen fuel supply has been finished or stopped. [Effects of the Invention]

[0033] According to one embodiment of the present invention, a communication method for hydrogen fuel supply and a device utilizing the same, namely a hydrogen refueling control device or communication control device for a vehicle / hydrogen fuel mobility, the limitations and vulnerabilities of existing unidirectional communication can be overcome in the hydrogen fueling process and communication protocol for hydrogen fueled mobility, including fuel cell electric vehicles (FCEVs) and hydrogen fuel engines, thereby improving the safety, compatibility, efficiency, and reliability of hydrogen refueling.

[0034] Furthermore, according to one embodiment of the present invention, it is possible to provide a communication protocol negotiation for hydrogen fuel supply, a fuel supply protocol negotiation, a parameter exchange method, and a communication protocol fallback rule that select the communication protocol required to execute the protocol for hydrogen fuel supply on a use case basis, taking into account the preference of the hydrogen fuel mobility or the dispenser, while maximizing interoperability between the hydrogen fuel mobility and the dispenser and considering backward compatibility.

[0035] Furthermore, according to one embodiment of the present invention, rules and procedures necessary for negotiating communication protocols, negotiating fuel supply protocols, and exchanging fuel supply parameters can be provided to effectively determine whether to use a conventional or advanced communication medium in order for hydrogen fuel mobility and a dispenser to cooperate to effectively achieve a hydrogen refueling goal.

[0036] Furthermore, according to one embodiment of the present invention, rules and procedures necessary for monitoring and control, safety check-in, and safety check-out can be provided for hydrogen fuel mobility and dispensers to cooperate in effectively achieving the fueling goal.

[0037] Furthermore, according to one embodiment of the present invention, it is possible to provide the rules and procedures necessary for use cases in which a hydrogen fuel mobility vehicle and a dispenser cooperate to effectively achieve a hydrogen refueling goal, with monitoring and control, safety check-in, and safety check-out processes linked with communication protocol negotiation, fuel supply protocol negotiation, and fuel supply parameter exchange processes. [Brief explanation of the drawing]

[0038] [Figure 1] This is a conceptual diagram of a hydrogen refueling system for a fuel cell electric vehicle (FCEV) to which a two-way hydrogen refueling communication process according to one embodiment of the present invention can be applied. [Figure 2] Figure 1 is a partially enlarged view illustrating the physical fastening structure between the FCEV and the dispenser in the hydrogen refueling system. [Figure 3] This graph illustrates the changes in the state of hydrogen fuel that occur during the hydrogen refueling process using the hydrogen refueling system shown in Figure 1. [Figure 4] This is a framework for a functional block that performs a series of hydrogen refueling procedures, employing a two-way hydrogen refueling communication process according to one embodiment of the present invention. [Figure 5] This diagram illustrates the communication stacks associated with each use case that can be employed in the hydrogen refueling bidirectional communication process according to one embodiment of the present invention, focusing on the OSI (Open Systems Interconnection Reference Model) 7-layer structure. [Figure 6] This is an illustrative diagram illustrating the pairing process of a discovery and pairing procedure that can be used in a hydrogen refueling communication bidirectional process according to one embodiment of the present invention. [Figure 7] This is an illustrative diagram illustrating backward compatibility that can be adopted in a hydrogen refueling communication bidirectional process according to one embodiment of the present invention. [Figure 8] This is an illustrative diagram illustrating backward compatibility that can be adopted in a hydrogen refueling communication bidirectional process according to one embodiment of the present invention. [Figure 9] This is an illustrative diagram illustrating a communication data usage classification that can be adopted in a hydrogen refueling bidirectional communication process according to one embodiment of the present invention, and backward compatibility between the communication data usage classifications. [Figure 10] This is a flowchart illustrating the authentication process of a communication security procedure that can be used in a hydrogen refueling bidirectional communication process according to one embodiment of the present invention. [Figure 11] This is a flowchart illustrating a communication protocol negotiation procedure that can be used in a two-way hydrogen refueling communication process according to one embodiment of the present invention. [Figure 12] This is a flowchart illustrating the fuel supply protocol negotiation procedure in a two-way hydrogen refueling communication process according to one embodiment of the present invention. [Figure 13] This is a flowchart illustrating the fueling parameter exchange / negotiation procedure that can be used in a hydrogen refueling communication bidirectional process according to one embodiment of the present invention. [Figure 14] This is a conceptual diagram illustrating a table of parameters transmitted from hydrogen fuel mobility to the dispenser side in a fuel supply parameter negotiation / exchange process according to one embodiment of the present invention. [Figure 15] This is a conceptual diagram illustrating a table of parameters transmitted from the dispenser to the hydrogen fuel mobility side in a fuel supply parameter negotiation / exchange process according to one embodiment of the present invention. [Figure 16] This is a conceptual block diagram of the internal structure of a generalized computing system that can be mounted on hydrogen fuel mobility, dispensers, and / or refueling stations as a communication device, communication control device, and / or electronic control device for hydrogen fuel supply according to one embodiment of the present invention. [Modes for carrying out the invention]

[0039] In addition to the aforementioned objectives, other objectives and features of the present invention will be clearly indicated through the description of embodiments with reference to the accompanying drawings.

[0040] While the present invention can be modified in various ways and has many embodiments, specific embodiments will be illustrated and described in detail in the drawings. However, this should not be understood as limiting the present invention to specific embodiments, but rather as including all modifications, equivalents, or substitutes that fall within the spirit and technical scope of the present invention.

[0041] Terms such as First, Second, A, B, etc., may be used to describe various components, but the components should not be limited by such terms. The terms are used solely for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the First component may be named the Second component, and similarly, the Second component may be named the First component. The term "and / or" includes a combination of multiple related described items or any of the multiple related described items.

[0042] In the embodiments of this application, "at least one of A and B" may mean "at least one of A or B" or "at least one of one or more combinations of A and B". Also, in the embodiments of this application, "one or more of A and B" may mean "one or more of A or B" or "one or more of one or more combinations of A and B".

[0043] When it is mentioned that one component is "linked" or "connected" to another component, it should be understood that it may be directly linked or connected to the other component, but there may also be other components in between. Conversely, when it is mentioned that one component is "directly linked" or "directly connected" to another component, it should be understood that there are no other components in between.

[0044] The terminology used in this application is used solely to describe specific embodiments and is not intended to limit the invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, terms such as “includes” or “having” are intended to specify the presence of features, figures, stages, operations, components, parts, or combinations thereof described in the specification, and should be understood not to preemptively exclude the possibility of the presence or addition of one or more other features, figures, stages, operations, components, parts, or combinations thereof.

[0045] Unless otherwise specified, all terms used herein, including technical or scientific terms, have the same meaning as those generally understood by a person of ordinary skill in the art to which this invention pertains. Terms as defined in commonly used dictionaries should be interpreted as having the meaning consistent with their meaning in the context of the relevant art, and not as ideal or overly formal unless expressly defined herein.

[0046] Some terms used in this specification are defined below.

[0047] Hydrogen electric vehicles generally include all hydrogen fuel cell vehicles (FCEVs) that utilize fuel cells, or ICE (internal combustion engine) based vehicles that use hydrogen as fuel. The hydrogen electric vehicles described below may also be simply referred to as FCEVs.

[0048] Although the following embodiments primarily describe hydrogen fuel cell vehicles, other embodiments of the present invention may include ICE-based hydrogen vehicles that utilize hydrogen as fuel. In the following embodiments, hydrogen fueling protocols and / or communication protocols for hydrogen fuel supply are disclosed, mainly for hydrogen fuel cell vehicles, and according to other embodiments of the present invention, the hydrogen fuel supply protocols and / or communication protocols for hydrogen fuel supply disclosed in the following embodiments may also be applied to ICE-based hydrogen vehicles.

[0049] Hydrogen fluid fuels can include gaseous hydrogen fuel or liquid hydrogen fuel.

[0050] A Compressed Hydrogen Storage System (CHSS) may include at least one tank mounted on the vehicle and a device coupled to this tank for compressing and storing hydrogen in the tank.

[0051] A Pressure Relief Device (PRD) is a device installed in the CHSS that can isolate the stored hydrogen from the vehicle's hydrogen refueling system and the surrounding environment, and can release the hydrogen to the outside.

[0052] Hydrogen refueling essentially refers to the process of receiving high-pressure hydrogen from a dispenser at a hydrogen station and compressing and storing it in a vehicle's tank. Hydrogen refueling can be used simply as synonymous with fueling in the context of supplying hydrogen fuel to a hydrogen electric vehicle. That is, in this specification, "fueling" can be used to mean fuel supply, hydrogen refueling, or refueling, and refueling can mean the refueling of hydrogen fuel. For example, a fuel supply protocol may be referred to as a refueling protocol, a fuel supply session may be referred to as a refueling session, and a fuel supply method may be referred to as a hydrogen refueling method or a refueling method.

[0053] The pressure ramp rate (PRR) is expressed in MPa / min and represents the rate of increase in the CHSS pressure.

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

[0055] Pre-cooling basically refers to the process of cooling hydrogen at a hydrogen refueling station before refueling.

[0056] A dispenser is a component that delivers pre-cooled hydrogen to the CHSS (Hydrogen-Suspended Stabilization System). Dispensers are located at hydrogen refueling stations and can perform hydrogen refueling operations between the hydrogen storage tanks at the refueling station and the CHSS in vehicles.

[0057] A nozzle is a device that is connected to a dispenser and coupled to the receptacle of a hydrogen electric vehicle, allowing for the transfer of hydrogen fuel.

[0058] The term "fueling session" can be used to include communication sessions that take place throughout the entire use case for hydrogen fueling.

[0059] Interoperability can refer to the state in which components of relative systems can work together to perform the intended function of the overall system. Information interoperability can refer to the ability of two or more networks, systems, devices, applications, or components to share and use information securely, effectively, and easily with little or no inconvenience to users.

[0060] Correlation / Association can include the procedure for establishing a relationship between two peer communication entities.

[0061] Command and control communication may refer to communication between an electric vehicle hydrogen fuel supply system and a hydrogen electric vehicle that exchanges information necessary for starting, controlling, and ending the hydrogen fuel supply process.

[0062] On the other hand, while the following detailed description illustrates embodiments related to hydrogen electric vehicles or fuel cell electric vehicles (FCEVs), it will be obvious to those skilled in the art that the concept of the present invention can be applied to a wide variety of hydrogen-fueled mobility. Hydrogen-fueled mobility refers to a type of hydrogen-fueled mobility that uses hydrogen as an energy source or generates electrical energy using hydrogen as fuel and uses this to drive an electric motor. In addition to hydrogen electric vehicles, hydrogen-fueled mobility may include aerial mobility, as well as industrial trucks, trains, ships, aircraft, and even devices that produce electrical energy using hydrogen as fuel and use it for propulsion. Furthermore, the bidirectional communication process for hydrogen refueling according to the present invention can be partially applied not only to hydrogen fuel mobility but also to buildings or facilities that use hydrogen as an energy source.

[0063] Furthermore, in the following explanation, hydrogen fuel may include at least one of gaseous hydrogen and liquid hydrogen, and can essentially mean compressed hydrogen, but is not limited to this.

[0064] Furthermore, for the sake of explanation, vehicles utilizing a two-way hydrogen refueling and communication process will primarily be described as fuel cell electric vehicles (FCEVs), but the explanation is not limited to this configuration and can also include hybrid electric vehicles (EVs) and internal combustion engine (ICE) vehicles that use hydrogen as fuel.

[0065] In the following specification, some or all of the processes of communication methods, communication protocol negotiation methods, hydrogen refueling (fueling) protocol negotiation methods, and hydrogen refueling (fueling) parameter negotiation methods performed in hydrogen fuel mobility may be performed by an electronic control unit (ECU), communication device, or communication control device within the hydrogen fuel mobility.

[0066] In the following specification, some or all of the processes of the communication method, communication protocol negotiation method, hydrogen refueling (fueling) protocol negotiation method, hydrogen refueling (fueling) parameter negotiation method, hydrogen refueling (fueling) method, and hydrogen refueling (fueling) control method performed in the dispenser may be performed by the dispenser's controller, electronic control unit, communication device, or communication control device. Furthermore, some of the processes of the said method may be performed by the controller, electronic control unit, communication device, or communication control device of the refueling station associated with the dispenser.

[0067] On the other hand, technologies that were publicly known before the filing date of this invention may be included as part of the structure of this invention as necessary, and such will be explained to the extent that it does not obscure the spirit of this invention. However, in explaining the structure of the present invention, detailed explanations of publicly known technologies that were publicly known before the filing date and that would be obvious to a person skilled in the art may obscure the spirit of this invention, so overly detailed explanations of publicly known technologies will be omitted. Furthermore, the spirit of this invention is not intended to assert rights over these publicly known technologies, and the content of publicly known technologies may be included as part of this invention to the extent that it does not depart from the spirit of this invention.

[0068] For example, in the case of unidirectional communication, IrDA technology can be used, and in the case of bidirectional communication, short-range wireless communication technology (Bluetooth®, WLAN, UWB) can be used. For wired communication technology for unidirectional / bidirectional communication, prior art known before the filing of the present invention can be used, and at least some of these prior arts can be applied as elemental technologies necessary for carrying out the present invention.

[0069] Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0070] Figure 1 is a conceptual diagram of a hydrogen refueling system for a fuel cell electric vehicle (FCEV) to which the hydrogen refueling bidirectional communication process according to one embodiment of the present invention can be applied. Figure 2 is a partially enlarged view illustrating the physical fastening structure between the FCEV and the dispenser in the hydrogen refueling system of Figure 1. Figure 3 is a graph illustrating the state changes of the hydrogen fuel that occur during the hydrogen refueling process using the hydrogen refueling system of Figure 1.

[0071] Referring to Figure 1, the hydrogen refueling system may be configured to include a hydrogen refueling station and a hydrogen electric vehicle 100 in a broad sense.

[0072] In addition to the basic mechanical devices, structural devices, electrical devices, electronic devices, and communication devices required for a vehicle, the hydrogen electric vehicle 100 may be equipped with an electronic control device 110 for hydrogen refueling, a vehicle system 120, a vehicle tank 130, and a receptacle 150.

[0073] The electronic control unit 110 transmits and receives signals and data via wired or wireless means to and from a hydrogen refueling station or the electronic control unit 210 of the hydrogen refueling station, and processes this data to control hydrogen refueling on the vehicle side. The electronic control unit 110 may consist of at least a part of other electronic control units mounted on the vehicle, or vice versa, and may be referred to as the first electronic control unit or electronic control unit #1.

[0074] The vehicle system 120 may be connected to a first electronic control unit 110 and configured to control hydrogen filling and hydrogen release of the vehicle tank 130 based on signals and commands from the first electronic control unit 110, and to monitor the state of the vehicle tank 130. Depending on the implementation, the vehicle system 120 may be configured to control the operation of the fuel cell system, include components that perform such control operations, or be coupled with such components. Such a vehicle system 120 also performs vehicle safety functions and may be referred to as a vehicle safety system in this case.

[0075] The vehicle may be provided with at least one, preferably more than one, vehicle tank 130. The vehicle tank 130 can compress and store hydrogen supplied from the hydrogen refueling station under the control of the vehicle safety system, and can release the stored hydrogen.

[0076] Furthermore, the vehicle tank 130 can accommodate a hydrogen storage system attached to the vehicle. In this case, the hydrogen storage system may consist of a high-pressure hydrogen storage tank, pressure control equipment, high-pressure piping, and an external frame. The high-pressure hydrogen storage tank may have a capacity of several tens to several hundreds of liters and may be configured as a series of smaller storage tanks connected in parallel. A boss unit through which hydrogen fuel can enter and exit may be attached to the high-pressure hydrogen storage tank, and hydrogen filling and release can be controlled through the boss unit. Valves, pressure reduction mechanisms, and sensors for various measurements may be attached to the boss unit. Such a hydrogen storage system is known as a compressed hydrogen storage system (CHSS), and for convenience of explanation, the term "vehicle tank" in this specification may mean a CHSS.

[0077] The aforementioned hydrogen electric vehicle 100 may, but is not limited to, be equipped with a fuel cell system including a fuel cell stack, and for convenience of explanation, may be simply referred to as "FCEV," "vehicle," or hydrogen fuel mobility 100. In the following specification, the subject referred to simply as vehicle or hydrogen fuel mobility may be understood to include not only the hydrogen electric vehicle 100 but also vehicles / mobility that use hydrogen as fuel (hydrogen fueled vehicle / mobility).

[0078] A hydrogen refueling station may be equipped with a dispenser (200), an electronic control unit (210), a refueling station system (220), a hydrogen tank (230), a station box (240), and a nozzle (250).

[0079] The dispenser 200 can supply hydrogen from the hydrogen tank 230 to the vehicle through a nozzle 250 that is firmly connected to the vehicle's receptacle 150, under the control of the filling station system 220. The dispenser 200 may, but is not limited to, include an electronic control unit 210 inside its housing. The nozzle 250 can essentially be installed at the end of a cable that extends for a certain length outside the housing of the dispenser 200.

[0080] The electronic control unit 210 can transmit and receive signals and data via wired or wireless connection to the vehicle's first electronic control unit 110 for hydrogen refueling, process this data, and control hydrogen refueling at the hydrogen refueling station. The electronic control unit 210 can exchange pre-set signals and data with the refueling station system 220. The electronic control unit 210 may also be referred to as the second electronic control unit or electronic control unit #2.

[0081] The aforementioned first electronic control unit 110 and second electronic control unit 210 may each be composed of multiple electronic control units, and may be configured to operate by matching different electronic control units with each other for each communication protocol. In this case, it may be useful when falling back for backward compatibility, and when bidirectional communication is unavailable and unidirectional communication must be used. It may also be useful when combining different communication methods, such as when using Wi-Fi when actually performing charging after pairing with NFC.

[0082] The refueling station system 220 can monitor and regulate the pressure, rate, and temperature of hydrogen released from the hydrogen tank 230 based on signals and / or data from the second electronic control unit. To this end, the refueling station system 220 can control the operation of the station box 240 connected to the discharge port and discharge valve of the hydrogen tank 230. The refueling station system 220 may also be referred to as the refueling station safety system.

[0083] In other embodiments of the present invention, the communication entity associated with the dispenser 200 for communicating with the vehicle / hydrogen fuel mobility 100 may be an electronic control unit 210, a separate communication device mounted on the dispenser 200, or an electronic control unit or separate communication device in the refueling station system 220 may communicate with the vehicle / hydrogen fuel mobility 100 on behalf of the dispenser 200.

[0084] In yet another embodiment of the present invention, the communication control device for communicating with the dispenser 200 side in the vehicle / hydrogen fuel mobility 100 may be the first electronic control device 110, or it may be a separate communication control device.

[0085] The hydrogen tank 230 stores hydrogen or compressed hydrogen. The hydrogen tank 230 can release the stored hydrogen at a predetermined pressure and rate under the control of a safety management module within the filling station system 220. The hydrogen tank may also be referred to as a hydrogen storage tank.

[0086] The station box 240 may be equipped with an adjustment valve whose inlet is connected to the outlet or discharge valve of the hydrogen tank 230 and whose outlet is connected to the dispenser 200 or a nozzle 250 coupled to the dispenser 200. The station box 240 may be equipped with means for adjusting the pressure, velocity, temperature, etc. of the discharged hydrogen, or components that perform functions corresponding to such means. The station box 240 may also be equipped with sensors for measuring the pressure, velocity, temperature, etc. of the discharged hydrogen.

[0087] The nozzle 250 can be connected to the hydrogen fuel supply system of the dispenser 200 through a conduit or flexible pipe of a predetermined length. The nozzle 250 may have a shape and structure that allows it to interlock tightly and securely with the vehicle's receptacle.

[0088] As shown in Figure 2, the nozzle 250 can engage with the receptacle 150. At this time, signals and information regarding the engagement state between the nozzle 250 and the receptacle 150 are transmitted to the first electronic control unit and the vehicle safety system, and can also be transmitted to the second electronic control unit and the filling station safety system, via the first sensor 160 installed on the vehicle and the second sensor 260 attached to the nozzle 250.

[0089] The hydrogen fuel, pre-cooled from the aforementioned hydrogen refueling station, is supplied to the hydrogen electric vehicle 100 via the dispenser 200. At this time, the hydrogen refueling process can be described by parameters including the pressure increase rate (PRR) and / or the mean pressure increase rate (APRR).

[0090] The interface between the hydrogen refueling station and the vehicle 100 can be handled by the dispenser 200. The dispenser 200 may be configured to control the target pressure and injection rate for hydrogen refueling by integrating information indirectly obtained from the vehicle tank 130 and fuel supply information from the hydrogen refueling station.

[0091] In existing technology, there are two methods for transmitting information from vehicle 100 to dispenser 200: a communication method and a non-communication method. When using communication, existing technology simply transmits the temperature and pressure values ​​of vehicle tank 130 of vehicle 100 to dispenser 200 in a unidirectional manner. Dispenser 200 cannot actively utilize this information and simply uses it as a safety standard, such as an emergency stop at the limit temperature and pressure. Furthermore, the hydrogen refueling protocol for safe and rapid refueling is managed by dispenser 200, and it has only minimal safety management devices that automatically release hydrogen through a pressure relief device (PRD) without active safety management of vehicle tank 130.

[0092] On the other hand, to address the phenomenon of rising hydrogen gas temperature during hydrogen refueling (see Figure 3), a hydrogen refueling station may be equipped with a precooler. The precooler can lower the temperature of the hydrogen fuel through pre-cooling. The precooler may be installed in or coupled to at least one of the hydrogen tank 230 and the station box 240. Of course, the precooler may also be installed in or coupled to the piping that transports hydrogen at the hydrogen refueling station.

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

[0094] As mentioned above, the hydrogen refueling process is controlled by a dispenser 200 between the vehicle 100 and the hydrogen refueling station, and such a dispenser 200 may be equipped with a protocol for supplying hydrogen fuel to the vehicle according to a defined procedure. Such a hydrogen refueling protocol may also be installed in the vehicle. The protocols installed in the vehicle and dispenser 200 may include at least a portion of a communication protocol that conforms to SAE standards, ISO standards, etc.

[0095] To meet the minimum safety requirements, simulations can be conducted through thermodynamic modeling under various conditions. The parameters derived from these simulations can then be used to implement table-based or MC-formula-based partial real-time correction methods. These minimum safety requirements may include upper limits on the temperature and pressure conditions of the CHSS (Chemical Heat Storage System) and guidelines for the State of Charge (SOC).

[0096] If the dispenser 200 does not actively control state values ​​related to hydrogen refueling, the conventional table-based method is extremely inefficient and has difficulty responding flexibly to changes in surrounding conditions because it does not utilize the temperature of the pre-cooled hydrogen fuel supplied from the gas refueling station or the temperature of the vehicle tank 130 measured by the vehicle 100. Furthermore, while the conventional MC-Formula-based method corrects the temperature of the pre-cooled hydrogen fuel in real time, its calculation and application methods are complex and have limitations in their application, making it difficult to expand. Thus, because existing communication protocols were developed with the primary goal of safe refueling completion, there are no alternatives that can actively control sudden situations such as excessive pre-cooling or overheating of the vehicle tank 130. As a result, problems such as increased operating costs due to overcooling and refueling delays due to overheating may occur.

[0097] For example, when hydrogen fuel is filled into a vehicle tank (see 130 in Figure 1), the internal temperature of the vehicle tank rises due to the heat of compression, which in turn raises the temperature of the hydrogen fuel inside the vehicle tank. The vehicle tank is constructed so that its dome and body are surrounded by carbon fiber, which has low heat transfer efficiency, in order to block heat exchange between the outside atmosphere and the hydrogen fuel stored inside. Therefore, when the temperature of the hydrogen fuel inside the vehicle tank rises during the filling process, the low heat transfer characteristics of the vehicle tank mean that the temperature rise observed on the surface of the vehicle tank may be negligible compared to the internal temperature rise until the filling is completed.

[0098] On the other hand, the temperature control during the hydrogen refueling process can aim to control the internal temperature of the vehicle tank 130 to 85°C or lower when the final refueling is completed, after receiving the supply of pre-cooled hydrogen gas. In other words, as shown in the characteristic curve for hydrogen temperature during hydrogen refueling in Figure 3, the temperature of the hydrogen fuel decreases at a constant rate in Phase I (P1), which is the pre-cooling stage of the hydrogen refueling station. In Phase II (P2), which is the stage in which hydrogen fuel is supplied to hydrogen fuel mobility such as vehicles at the hydrogen refueling station, the temperature of the hydrogen fuel gradually increases due to the thermal mass of the hydrogen refueling station. In Phase III (P3), which is the stage in which hydrogen fuel is transferred from inside the vehicle to the vehicle tank, the temperature of the hydrogen fuel further gradually increases due to the thermal mass of the vehicle. In Phase IV (P4), which is the stage in which hydrogen fuel is compressed and stored in the vehicle tank, the temperature of the hydrogen fuel can rise rapidly due to the heat of compression.

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

[0100] Figure 4 shows a framework for a functional block that performs a series of hydrogen refueling procedures, employing a two-way hydrogen refueling communication process according to one embodiment of the present invention (hereinafter referred to as the "hydrogen refueling framework").

[0101] Referring to Figure 4, the hydrogen refueling framework consists of use case (UC) functional blocks: discovery and pairing functional block (hereinafter abbreviated as "UC1' or 'UC-1'"), communication security functional block (UC2 or UC-2), communication protocol negotiation functional block (UC3 or UC-3), fueling protocol negotiation functional block (UC4 or UC-4), fueling parameter negotiation functional block (UC5 or UC-5), safety check-in functional block (UC6 or UC-6), monitoring and control functional block (UC7 or UC-7), safety check-out functional block (UC8 or UC-8), termination functional block (UC9 or UC-9), error handling functional block (UC10 or UC-10), and emergency handling functional block. It may be equipped with a handling function block (UC11 or UC-11).

[0102] Each of the UC1 to UC11 functional blocks can correspond to a chronological stage (S401 to S411), as shown in Figure 4. In this case, Figure 4 may be understood as an operation flowchart that includes the chronological stages (S401 to S411).

[0103] UC10 and UC11 may be individually connected to UC3 through UC8, respectively, and configured to perform error handling and / or emergency handling in each use case.

[0104] The aforementioned use cases are functional blocks that collectively provide the entire hydrogen refueling procedure of a hydrogen refueling system in a consistent manner for safe and secure fueling communication. The vehicle and dispenser can sequentially execute each use case in a specific order to achieve the hydrogen refueling objective.

[0105] Furthermore, after the dispenser nozzle is connected to the vehicle receptacle, the vehicle and dispenser can perform fuel supply communication by realizing each use case in the order shown in Figure 4. However, the vehicle and dispenser may omit specific use cases if necessary according to predefined requirements.

[0106] Each of the aforementioned use cases can be realized through communication between the hydrogen fuel vehicle and the dispenser control system of a dispenser that supplies hydrogen as fuel to the hydrogen fuel vehicle using a fuel supply protocol for hydrogen fuel vehicles.

[0107] On the other hand, a hydrogen fuel vehicle (hereinafter simply referred to as "vehicle") and a dispenser that embody the aforementioned use cases can exchange data for vehicle identification using UC-1. For this purpose, the vehicle may be equipped with sensors, an electric control unit (ECU), a transmitter, and a receiver. The receiver may be integrated with the transmitter when bidirectional communication is required.

[0108] The dispenser can be configured to receive specific data from the vehicle. The dispenser can store data for data logging or data specified to the station PLC (programmable logic controller) for use in the fuel supply protocol. Data logging can refer to the process of collecting data over a period of time to analyze specific operating states of the hydrogen refueling system or to record data-based events / operations in the system or network environment, or the data collected by this process. In the case of two-way communication, the station is equipped with sensors specified by the fuel supply protocol, and the station PLC or electronic control unit can obtain measurements from the sensors and send these measurements to the vehicle. The aforementioned vehicle and station can use existing communication protocol standards for communication such as infrared, Wi-Fi, and Bluetooth®.

[0109] Furthermore, a communication channel can be established between the vehicle and the dispenser, which are physically connected via a vehicle-dispenser interface. The pairing process for establishing such a communication channel can be carried out using wired, optical, or wireless technology.

[0110] The discovery and pairing procedures and pairing processor may have preconditions that the dispenser nozzle is inserted into and firmly coupled to the vehicle fueling receptacle. The vehicle fueling receptacle may be simply referred to as the vehicle receptacle or receptacle.

[0111] Furthermore, the vehicle and dispenser essentially know which communication protocol to follow. Therefore, communications following UC-1 are discovery and pairing procedures or post-conditions of the pairing process and can only depend on the communication protocol agreed upon for the current use case. If a communication protocol outside the agreed scope is selected by the vehicle or dispenser, the selected communication will not be performed. In other words, even if the pairing process is successfully completed, approval for fuel or approval for fuel supply may not be granted.

[0112] All methods used to pair the vehicle with the dispenser are configured not to increase the ignition or explosion hazard beyond an acceptable level. For example, all wired pairing methods are configured to mitigate or block the spark hazard due to electrostatic discharge.

[0113] In terms of the effectiveness of physical pairing, all methods used to pair a vehicle with a dispenser may be integrated into a vehicle-dispenser interface or installed to have proximity between the vehicle's fuel supply receptacle and the dispenser's nozzle and hose assembly. Here, the interface may refer to one that is physically integrated into the nozzle and receptacle interface. Proximity may be defined by the hardware associated with the pairing method. For example, the physical geometry used for infrared communication may be specified, including the allowable distance between the transmitter and receiver. The physical shape of the hydrogen refueling hardware may also be specified in advance, but proximity does not include pairing methods that risk pairing a vehicle and dispenser that are not physically connected, such as relatively long-range wireless communication technologies like Bluetooth®. Infrared communication may be referred to as IrDA (infrared data association) communication and may include bi-IrDA communication.

[0114] Referring again to Figure 4, a communication method for hydrogen fuel supply according to one embodiment of the present invention is a communication method for hydrogen fuel supply (fueling) performed by a communication device of a hydrogen fuel mobility vehicle, and includes the steps of: negotiating a communication protocol with a dispenser that supplies hydrogen fuel to the hydrogen fuel mobility vehicle (S403); negotiating a fuel supply protocol with the dispenser for receiving hydrogen fuel from the dispenser (S404); and negotiating fuel supply parameters based on the fuel supply protocol with the dispenser (S405).

[0115] A communication method for hydrogen fuel supply (fueling) performed by a dispenser that supplies hydrogen fuel to a hydrogen fuel mobility vehicle according to one embodiment of the present invention includes the steps of: negotiating a communication protocol with the hydrogen fuel mobility vehicle (S403); negotiating a fuel supply protocol for supplying hydrogen to the hydrogen fuel mobility vehicle with the hydrogen fuel mobility vehicle (S404); and negotiating fuel supply parameters based on the fuel supply protocol with the hydrogen fuel mobility vehicle (S405).

[0116] Figure 5 is an illustrative diagram showing, primarily based on the OSI (Open Systems Interconnection Reference Model) 7 layers, the communication stacks associated with each use case that can be adopted in the hydrogen refueling communication bidirectional process according to one embodiment of the present invention.

[0117] As illustrated in Figure 5, the communication stack related to the use case of a two-way hydrogen refueling communication process (simply put, the "hydrogen refueling communication stack") can be expressed as protocol suites, corresponding to the data link and physical layer, network layer, transport layer, security layer, session layer, presentation layer, and application layer, respectively, which belong to the OSI 7 layers.

[0118] In other words, the hydrogen refueling communication stack may include at least one first protocol 510 selected from bidirectional IrDA (bi-IrDA), WLAN, NFC, etc., as the data link and physical layer protocols of the OSI 7 layer.

[0119] Furthermore, the hydrogen refueling communication stack can include IPv6 (Internet Protocol Version 6) Protocol 520 as a protocol in the OSI 7-layer network hierarchy.

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

[0121] Furthermore, the hydrogen refueling communication stack may include at least one fourth protocol 540 selected from TLS (transport layer security), DTLS (datagram transmission layer security), etc., as a security layer protocol of the OSI 7 layer. TLS may include versions such as TLS 1.2 and TLS 1.3, and DTLS may include versions such as DTLS 1.2 and DTLS 1.3. TLS may be implemented using TCP sockets, and DTLS may be implemented using UDP sockets.

[0122] Furthermore, the hydrogen refueling communication stack may include a JSON-based session protocol 550 as a session layer protocol in the OSI 7-tier hierarchy. The JSON-based session protocol 550 can be used for communication between a vehicle and a dispenser, or for sending data between the vehicle's electronic control unit and the refueling station's electronic control unit.

[0123] Furthermore, the hydrogen refueling communication stack can include JSON (JavaScript Object Notation) 560 as a protocol in the OSI 7-tier representation layer. JSON is one of the formats that can be used when sending data from a server to a client. Using JSON, protocol messages can be expressed in JSON between a vehicle and a dispenser, or between the vehicle's electronic control unit and the refueling station's electronic control unit.

[0124] Furthermore, the hydrogen refueling communication stack may include hydrogen refueling-related fuel supply protocols (FP) 570 as an application layer protocol of the OSI 7 layer. Fuel supply protocols 570 may include a first fuel supply protocol FP1, a second fuel supply protocol FP2, and an nth fuel supply protocol FPn, where n can be any natural number greater than or equal to 3.

[0125] Furthermore, in other embodiments, the aforementioned hydrogen refueling communication stack may be configured to utilize protocols such as PLC (programmable logic controller) and WLAN as the protocols for the data link and physical and network layers, TCP and / or IPv6 as the protocols for the transmission and security layers, Binary XML (binary extensible markup language) as the protocol for the session layer corresponding to the encoding layer, and one of the existing protocols used in electric vehicles as the protocols for the representation and application layers. The existing protocols used in electric vehicles may include at least one protocol for DC (direct current) refueling, AC (alternate current) refueling, wireless power transfer (WPT), automatic connection device pantograph (ACDP), etc.

[0126] Table 1 shows the general communication data items exchanged between the vehicle and the refueling station via the aforementioned hydrogen refueling communication stack.

[0127] [Table 1]

[0128] On the other hand, the use case (UC1) of the discovery and pairing stage (S401) in Figure 4 allows the device to identify the communication partner (vehicle or dispenser communication module) responsible for controlling the physically connected receptacle or nozzle. UC1 can also define a method for identifying incompatibilities and define safety device mechanisms. In such a use case (UC1), the vehicle and dispenser may attempt to explore common communication technologies to execute the fuel supply protocol. The search mechanism provided at the basic data link and physical layer allows the vehicle and dispenser to find each other and initiate communication. Additional pairing procedures are required to establish a communication channel with the device connected to the fuel supply hose assembly. If the communication channel does not guarantee correct pairing, for example in the case of wireless communication, a separate pairing channel to transmit pairing information may be required. If pairing is implicitly guaranteed, for example, the communication channel for communication integrated with the hose assembly may be sufficient.

[0129] Table 2 is a table illustrating the objectives, prerequisites, and subsequent conditions for use case UC1 in the discovery and pairing stage (S401) shown in Figure 4.

[0130] [Table 2]

[0131] Table 3 is a table illustrating the supported communication technologies and their respective clauses that may be used in use case UC1 during the discovery and pairing phase (S401) shown in Figure 4.

[0132] [Table 3]

[0133] Figure 6 is an operation flowchart illustrating in detail a step (S401) according to one embodiment of the present invention. Referring to Figure 6, in the Discovery and Pairing step (S401) of Figure 4, the pairing process allows the vehicle and dispenser to exchange pairing IDs and confirm each other's pairing IDs when pairing at UDC Level 2 and UDC Level 3.

[0134] For example, a vehicle can broadcast a message (PAIR_ID_ANNOUNCE) containing its pairing ID (PAIR_ID), i.e., its vehicle ID (vehicle_id). A dispenser can then send a message (PAIR_ID_ACK) to the vehicle acknowledging receipt of the vehicle ID. The vehicle can then send a message (PAIR_ID_CONFIRM) to the dispenser confirming that it has successfully received the ACK message acknowledging receipt of the vehicle ID.

[0135] Next, the dispenser can broadcast a message (PAIR_ID_ANNOUNCE) containing its pairing ID, i.e., the dispenser ID (dispenser_id). The vehicle can then send a message (PAIR_ID_ACK) to the dispenser acknowledging receipt of the dispenser ID. The dispenser can then send a message (PAIR_ID_CONFIRM) to the vehicle confirming that it has successfully received the ACK message indicating that the vehicle has received the dispenser ID.

[0136] Through this transmission-echo-verification method, vehicles and dispensers can use session-specific randomized pairing IDs. This solves the problem of protecting personal information during pairing ID exchange. In other words, trust in the pairing process is established by a subsequent process, and for this purpose, the session-specific pairing ID is included in the data used to establish that trust.

[0137] On the other hand, when supporting secure communication at a specific UCDC level, at least one of the vehicle and dispenser can verify that the pairing provides sufficient information to protect the communication channel for all methods used to pair the vehicle and dispenser. For example, pairing may include the exchange of encryption keys to ensure communication security while the vehicle and dispenser are supplying fuel.

[0138] For reference, UCDC Level 1 does not support bidirectional communication, so communication channel security may be impossible. Pairing a vehicle and dispenser with UCDC Level 2 and UCDC Level 3 can be configured to provide sufficient information to protect communications in order to satisfy a specific security level, for example, IEC 62443 Security Level 3. IEC 62443 Security Level 3 may be a security level against actors with appropriate resources and appropriate motives.

[0139] Figure 7 is an illustrative diagram illustrating backward compatibility that can be adopted in a hydrogen refueling communication bidirectional process according to one embodiment of the present invention.

[0140] Referring to Figure 7, hydrogen refueling systems can be manufactured using compatible equipment that is backward compatible with existing equipment, taking interoperability into consideration. When classifying equipment based on interoperability, hydrogen refueling systems and their communication devices can be classified into Type 0, Type 1, Type 2, and Type 3.

[0141] Type 0 may refer to a device that does not support or receive communication messages related to fuel supply.

[0142] Type 1 may refer to equipment that supports IrDA communication for fuel supply. Type 1 equipment can fall back to Type 0 equipment.

[0143] Type 2 may refer to equipment that supports advanced communication (AC). Type 2 equipment can fall back to Type 0 equipment.

[0144] Type 3 can refer to equipment that supports IrDA and advanced communications. A Type 3 device can fall back to any one of Type 0, Type 1, or Type 2.

[0145] Advanced communication can refer to communication using mediums (mediums) and specific protocols such as WLAN (wireless local area network), Bluetooth® (BT), NFC (near field communication), Wi-Fi, UWB (ultra-wideband), RFID (radio frequency identification), 4G, and 5G. Advanced communication can also include bidirectional IrDA, serial communication, automotive Ethernet (Ethernet, ETH), and high-level communication. Specific protocols can include TCT / IP (transmission control protocol / internet protocol) and fueling protocols. High-level communication can process all information exceeding that handled by command and control communication. The data link for high-level communication can use, but is not limited to, PLC (Power line communication).

[0146] Furthermore, advanced communication can take a hybrid form, including a combination of IrDA and wired or IrDA and wireless. In the case of a combination of IrDA and wired, modifications to the nozzle and receptacle may be necessary.

[0147] In other words, advanced communication can be a bidirectional communication technology, either wired or wireless, and wireless communication technologies can include a variety of communication methods such as 5G, WLAN, BLE, ETH, UWB, RFID, and NFC. Known protocols such as TCP / IP can be used as protocols for such communication methods. For example, communication methods considered as wireless communication may include Bluetooth, WLAN, Wi-Fi (ISO 15118 for inductive / ACD), UWB (IEC limited consideration for ACD), etc.

[0148] In practice, hydrogen refueling devices can be implemented to support communication between devices using different technologies. Therefore, the two-way hydrogen refueling communication process in this embodiment is configured to maximize interoperability between devices.

[0149] In other words, as shown in Figure 7, when a Type 1 device supporting standard #1, which conforms to a predetermined standard, encounters a Type 0 device or a Type 2 device, the Type 1 device can fall back to the Type 0 device (S610).

[0150] Furthermore, if a Type 2 device supporting standard #2, which conforms to a predetermined standard, encounters a Type 0 device or a Type 1 device, the Type 2 device can fall back to the Type 0 device (S620).

[0151] Furthermore, when a Type 3 device supporting standard #2 encounters a Type 0 device, the Type 3 device can fall back to the Type 0 device (S630). When a Type 3 device encounters a Type 1 device, the Type 3 device can fall back to the Type 1 device (S640). Also, when a Type 3 device encounters a Type 2 device, the Type 3 device can fall back to the Type 2 device (S650).

[0152] Standard #1 mentioned above can include SAE (Society of Automotive Engineers) standards, etc. Standard #2 can include ISO 19885-3 standards, etc.

[0153] Furthermore, to support the aforementioned interoperability, the hydrogen refueling unit can perform a connection compatibility check. For example, the hydrogen refueling unit can perform a connection compatibility check as shown in the following scenarios 1 to 3, depending on whether or not it supports WLAN, which is one of the advanced communication methods.

[0154] In Scenario 1, the dispenser can prepare an access point (AP), which is a wireless router. The dispenser can support fuel supply methods at FCEV fuel station beaconing and VSE (vehicle supply equipment). An FCEV in close proximity to the dispenser can scan for it and establish a WLAN link with the dispenser it finds.

[0155] In Scenario 2, the dispenser can support IrDA communication without supporting WLAN communication. The dispenser corresponds to a Type 1 device. An FCEV adjacent to the dispenser is a Type 3 device and cannot find the dispenser, which is a Type 1 device, through scanning. When the receptacle of the FCEV is connected to the nozzle attached to the cable of the dispenser, IrDA communication may be initiated between the FCEV and the dispenser.

[0156] In Scenario 3, the dispenser can support WLAN and IrDA communication. In this case, the dispenser corresponds to a Type 3 device. An FCEV, which is a Type 1 device, may be parked around the dispenser. The dispenser is not yet able to find any WLAN clients. When the receptacle of the FCEV is connected to the nozzle attached to the cable of the dispenser, IrDA communication may be initiated between the FCEV and the dispenser.

[0157] Figure 8 is an illustrative diagram illustrating backward compatibility that can be adopted in a hydrogen filling communication bidirectional process according to one embodiment of the present invention.

[0158] Referring to Figure 8, the two-way hydrogen refueling communication process of this embodiment does not necessarily select the communication method preferred by the FCEV and dispenser, but rather provides rules and principles that fall back to maximize interoperability between the fueling method and the communication protocol.

[0159] In other words, when one of the vehicles or dispensers meets the other, the device with the relatively higher Type or UCDC level may be configured to fall back to the Type or level of the device with the relatively lower Type or level.

[0160] For example, if a vehicle and a dispenser are of the same type or the same UDC level, both devices can maintain their current type or UDC level. On the other hand, if one device is a type 1 device and the other is a type 2 device, both devices may be configured to fall back to a type 0 device. And if one device is a type 3 device and the other is not a type 3 device, the type 3 device may be configured to fall back to the same level as the other device's type or UDC level.

[0161] The aforementioned standard #1 could be an SAE standard communication protocol, and standard #2 could be an ISO 19885 standard communication protocol.

[0162] According to the configuration described above, if there are two devices with the "same embodiment," the vehicle and the dispenser can both select the best of the two that they support. When a device without communication (hereinafter, "non-communication device") meets a device that supports unidirectional communication (hereinafter, simply referred to as "unidirectional communication device"), the latter can fall back to a no-communication (no comm) device that does not have a communication method to support. Also, when two devices that support bidirectional communication meet, the two devices can maintain their bidirectional communication method. Here, UCDC compatibility may be handled separately. Furthermore, when a device meets a non-communication device, it can rely on non-communication. This can be applied to all devices that support bidirectional communication (hereinafter, simply referred to as "bidirectional communication devices").

[0163] Furthermore, when a unidirectional communication device encounters a bidirectional communication device, if the bidirectional communication device supports both unidirectional and bidirectional communication methods, the bidirectional communication device can fall back to unidirectional communication. If the bidirectional communication device does not support unidirectional communication, the bidirectional communication device can fall back to a no-communication device to rely on no-communication.

[0164] The aforementioned bidirectional communication device may be configured to support a unidirectional fuel supply method, regardless of whether unidirectional communication is available. Such a bidirectional communication device must be able to determine whether the other party supports bidirectional communication. If the FCEV or dispenser does not support bidirectional communication, the bidirectional communication device can fall back to a unidirectional communication device that uses a compatible unidirectional communication method.

[0165] Figure 9 is an illustrative diagram illustrating the communication data usage classifications that can be adopted in a hydrogen refueling bidirectional communication process according to one embodiment of the present invention, and backward compatibility between the communication data usage classifications.

[0166] As shown in Figure 9, vehicles and dispensers can possess pairing identities (IDs), and the requirements for exchanging such identities can be classified by the use classification of communication data (UCDC) level. UCDC levels can include UCDC level 1 (UCDC-1) (910), UCDC level 2 (UCDC-2) (920), and UCDC level 3 (UCDC-3) (930). UCDC levels can further include UCDC level 0 (UCDC-0) (900).

[0167] UCDC Level 0 (900) may refer to communications where data is not transmitted or, if data is transmitted, are not used by fuel supply protocols for hydrogen dispensing or related safety functions. In UCDC Level 0 (900), there is no communication between the vehicle and the dispenser, so the dispenser cannot transmit the pairing ID to the vehicle during process control or safety functions.

[0168] When pairing in UCDC Level 1 (910), the vehicle can transmit a pairing ID to the dispenser. Although the data transmitted in UCDC Level 1 (910) is not used for safety functions, the transmitted static data may be used to improve the performance of the fuel supply protocol, and the transmitted dynamic data may be used to reduce the risk against process deviations within the fuel supply protocol.

[0169] Static data transmitted under UCDC Level 2(920) may be used for safety functions. Such UCDC Level 2(920) static data may be additional uses beyond those permitted for static and dynamic data as defined for UCDC Level 1.

[0170] Under UCDC Level 3(930), static and dynamic data may be used for dynamic control within a protocol or safety function. Such dynamic data under UCDC Level 3(930) may be additional uses beyond those permitted for static and dynamic data as defined for UCDC Level 2.

[0171] As mentioned above, UCDC levels can take the form of UCDC level 1 being included in UCDC level 2, and UCDC level 2 being included in UCDC level 3, that is, higher levels can include lower levels. Devices supporting a particular UCDC level can support devices supporting even lower UCDC levels. Devices supporting different UCDC levels can use the highest UCDC level supported by both devices. It can be said that the aforementioned UCDC levels also readily support UCDC level 0. It can be seen that UCDC levels are backward compatible. In other embodiments of the present invention, backward compatibility can also be effectively applied to Non-Comm, Uni-directional Comm, Bi-directional Comm, and combinations thereof, regardless of UCDC levels.

[0172] Referring to Figures 4 to 8, information regarding interoperability and / or compatibility between the vehicle / hydrogen fuel mobility and the dispenser may be shared during the discovery and pairing phase (S401) in Figure 4. This interoperability and / or compatibility can then be utilized in the communication protocol negotiation phase (S403), the fuel supply protocol negotiation phase (S404), and / or the fuel supply parameter negotiation phase (S405), which will be described later.

[0173] In another embodiment of the present invention, information regarding interoperability and / or compatibility shared between the vehicle / hydrogen fuel mobility and the dispenser during the discovery and pairing stage (S401) shown in Figure 4 may be updated or reshared during the communication protocol negotiation stage (S403), the fuel supply protocol negotiation stage (S404), and / or the fuel supply parameter negotiation stage (S405). Information regarding interoperability and / or compatibility may be updated due to changes in the communication environment, changes in parameters affecting the fuel supply process, etc.

[0174] In another embodiment of the present invention, at least a portion of the discovery and pairing stage (S401) shown in Figure 4 may be referred to as the Dispenser Discovery Protocol (DDP).

[0175] DDP can be initiated by a DDP request message [DDPRequest] broadcast by the hydrogen fuel mobility. The DDPRequest may include the pairing ID "pairing_id" of the hydrogen fuel mobility.

[0176] A dispenser can receive a DDPRequest and send a DDPResponse in response. The DDPResponse may include the dispenser's IP address ("IPAddr"), the dispenser's TCP port number ("TCPPort"), the dispenser's UDP port number ("UDPPort"), and the dispenser's pairing ID ("pairing_id").

[0177] Figure 10 is a flowchart illustrating the authentication process of a communication security procedure (S402) that can be used in a hydrogen refueling bidirectional communication process according to one embodiment of the present invention.

[0178] Referring to Figure 10, the hydrogen fuel mobility can transmit a message to the dispenser requesting a list of authorization methods (S1010). The dispenser can transmit a response message to the hydrogen fuel mobility in response to the request for a list of authorization methods (S1020). The response message may include information on a list of authorization methods related to external authentication procedures such as RFID (radio frequency identification), credit cards, and debit cards, as well as its own authentication procedures.

[0179] Next, the hydrogen fuel mobility can transmit an authentication request message to the dispenser, including a specific method selected from the list of authentication methods, such as RFID (S1030). The dispenser can transmit a response message to the hydrogen fuel mobility for the authentication request (S1040). This response message may include information indicating that the authentication method selected by the hydrogen fuel mobility is working.

[0180] Next, the hydrogen fuel mobility vehicle performs authentication using the authentication method previously selected based on the dispenser's response and can transmit a confirmation (Done?) request message to the dispenser regarding the completion of authentication (S1050). If confirmation of authentication has not been received or authentication is not complete, the aforementioned series of steps (S1010-S1050) may be repeated. Once authentication is complete, the dispenser can transmit an authentication complete (Done (success)) message to the hydrogen fuel mobility vehicle (S1090).

[0181] According to the configuration described above, the dispenser can verify whether the hydrogen fuel mobility has been approved, that is, whether the user of the hydrogen fuel mobility has the authority to refuel with hydrogen, before proceeding further with the hydrogen refueling process.

[0182] For security during the authentication process, a hydrogen refueling system including at least one of a hydrogen fuel mobility vehicle and a dispenser can perform a TLS handshake to authenticate after establishing a data link and physical layer connection between the hydrogen fuel mobility vehicle and the dispenser, and after setting up the transmission layer, i.e., a TCP connection, and then exchanging keys to establish a secure communication channel. Furthermore, UDP communication protected by DTLS can be used while security-critical information is being exchanged.

[0183] Furthermore, the hydrogen fuel mobility and dispenser can successfully perform discovery and pairing procedures to establish data link and physical layer connections. Next, the credentials necessary for authentication and key exchange can be prepared. This allows the communication channel between the hydrogen fuel mobility and the dispenser to be encrypted and integrity protected. The dispenser can authenticate the hydrogen fuel mobility, and selectively, the hydrogen fuel mobility can authenticate the dispenser.

[0184] On the other hand, during the aforementioned TLS handshake, hydrogen fuel mobility authentication is mandatory, while dispenser authentication may be optional. In this case, the dispenser can act as the client, and the hydrogen fuel mobility can act as the server.

[0185] For a TLS handshake, the hydrogen fuel mobility and dispenser must prepare the necessary credentials. The hydrogen fuel mobility and dispenser can store the certificate chain, the personal key corresponding to the certificate, and the trust anchor certificate in a secure storage location that protects against unauthorized access.

[0186] During the TLS handshake, the hydrogen fuel mobility device can request client authentication from the dispenser by transmitting a predefined CertificateRequest message. Upon receiving the CertificateRequest message, the dispenser can then transmit the certificate and CertificateVerify messages to the hydrogen fuel mobility device to transmit the certificate.

[0187] When a hydrogen fuel mobility device sends a certificate request message along with a handshake message such as ServerHello, if the dispenser does not send a certificate confirmation message along with the certificate, it can abort the TLS handshake by sending a warning message containing a "certificate_required" warning code.

[0188] According to another embodiment of the present invention, the objective, prerequisites, and subsequent conditions of step (S402) can be illustrated by Table 4 below.

[0189] [Table 4]

[0190] Figure 11 is a flowchart illustrating a communication protocol negotiation stage (S403) that can be adopted in a two-way hydrogen refueling communication process according to one embodiment of the present invention. Referring to Figure 11, the communication protocol negotiation stage (S403) may include a stage of transmitting a message containing information for a first communication protocol applicable to hydrogen fuel mobility to a dispenser (S1110), and a stage of receiving a message from the dispenser containing information for a second communication protocol selected from common communication protocols applicable between hydrogen fuel mobility and the dispenser (S1130).

[0191] Referring to the embodiment in Figure 11, the dispenser receives a message from the hydrogen fuel mobility vehicle containing information for a first communication protocol applicable to the hydrogen fuel mobility vehicle (S1110), compares the first communication protocol with the communication protocols applicable to the dispenser, selects a second communication protocol from among the common communication protocols applicable to both the hydrogen fuel mobility vehicle and the dispenser, and transmits a message containing information for the selected second communication protocol to the hydrogen fuel mobility vehicle (S1130).

[0192] At this point, although not shown in Figure 11, the process may further include a step prior to step (S1110) in which the dispenser requests information from the hydrogen fuel mobility vehicle, including a list of first communication protocols applicable to the hydrogen fuel mobility vehicle.

[0193] In another embodiment of the present invention, a dispenser may first transmit a message to the hydrogen fuel mobility vehicle containing information about its applicable communication protocol, and the hydrogen fuel mobility vehicle may select a specific communication protocol from among the common communication protocols and transmit a message to the dispenser containing information about the selected specific communication protocol.

[0194] This could further include a step where the hydrogen fuel mobility vehicle requests information from the dispenser, including a list of applicable communication protocols.

[0195] According to one embodiment of the present invention, the objective, prerequisites, and subsequent conditions of step (S403) can be illustrated by Table 5 below.

[0196] [Table 5]

[0197] According to one embodiment of the present invention, the contents of the messages transmitted and received in step (S1110) can be illustrated by Table 6.

[0198] [Table 6]

[0199] Information for the first communication protocol may include at least one of the following: the index of the first communication protocol, the name of the first communication protocol, the version of the first communication protocol, and the preference for the first communication protocol. According to one embodiment of the present invention, the contents of the response messages transmitted and received in step (S1130) can be illustrated by Table 7 below.

[0200] [Table 7]

[0201] The response message containing information regarding the second communication protocol may further include information on whether the communication protocol negotiation was successful or not. The aforementioned communication protocol negotiation procedure is a procedure for identifying the communication protocol to follow during the hydrogen refueling session, after the vehicle and dispenser have discovered and paired with each other on compatible communication channels. In particular, in this embodiment, the dispenser can take the lead in exchanging the communication protocol and parameters with the vehicle.

[0202] In other words, the communication method according to one embodiment of the present invention can perform the step of discovering and pairing with a dispenser (S401) using the first communication technology.

[0203] If the result of the communication protocol negotiation stage (S403) relates to the second communication technology, the stage of negotiating the fuel supply protocol (S404) and the stage of negotiating the fuel supply parameters (S405), which will be described later, can be carried out using the second communication technology.

[0204] During the discovery and pairing process (S401), information regarding the interoperability and / or compatibility between the hydrogen fuel mobility and the dispenser may be shared.

[0205] During the process of carrying out steps (S403) to (S405) of the present invention, changes in the communication environment and changes in environmental variables related to hydrogen fuel supply may update the information regarding the interoperability and / or compatibility between the hydrogen fuel mobility and the dispenser that was shared in step (S401) of carrying out the discovery and pairing process.

[0206] Communication protocol negotiation procedures can be embodied by all available communication protocols to ensure successful negotiation between different fueling protocols for each communication technology. For example, a fuel supply protocol utilizing a communication technology such as WLAN can use a protocol (hereinafter also referred to as the "common protocol") that is commonly supported by the vehicle and dispenser to determine which communication protocol to use in the two-way hydrogen refueling communication process.

[0207] In practice, hydrogen fuel mobility and dispensers at each site can have a variety of combinations depending on hydrogen refueling communication standards, communication modes, fuel supply methods, communication levels, and other parameters. Here, hydrogen refueling communication standards can include SAE J2601 series, ISO 19885-3, ISO 19885-4, etc. Communication modes can include no communication (No comm.), IrDA, XYZ (ISO), etc. Fuel supply methods can include table-based refueling methods such as lookup tables, MC formula-based refueling methods, etc. Communication levels can include UCDC levels, and other parameters can include pressure class, CHSS (compressed hydrogen storage system) category, and fueling tables.

[0208] On the other hand, hydrogen fuel mobility or dispensers may be configured to further perform a process of falling back to the lower type or lower UDC level of the other party based on the mutual type or UDC level confirmed in the communication protocol negotiation procedure.

[0209] Furthermore, in environments where various combinations are possible, if incompatibility is found in parameters exchanged during the negotiation procedures for hydrogen refueling (UC3-UC5), the hydrogen fuel mobility and dispenser can return to the communication protocol negotiation procedures and resume the negotiation process.

[0210] In one embodiment of the present invention, a communication protocol assigned a priority may include protocols having the priority levels exemplified in Table 6 described later.

[0211] The dispenser selects a specific protocol from the protocol list.<selected protocol> A response message including ) can be transmitted to the hydrogen fuel mobility (S1130). The specific protocol is a common protocol selected by the dispenser that is supported by both the dispenser and the hydrogen fuel mobility and is the highest priority protocol preferred by the hydrogen fuel mobility, for example, the ISO 19885-3-2023-UCDC-3 protocol (see Table 6).

[0212] According to the common protocol, hydrogen fuel mobility and dispensers can reach an agreement on the communication protocol to be used for fueling communication.

[0213] On the other hand, hydrogen fuel mobility can assign priorities to the communication protocols it supports. Hydrogen fuel mobility can provide the dispenser with the assigned priorities for communication protocols. An example of an assigned priorities for communication protocols is shown in Table 8 below.

[0214] [Table 8]

[0215] Once a communication protocol is selected in the aforementioned communication protocol negotiation use case (UC3), the vehicle and dispenser can activate their respective communication protocol implementations to initiate fuel supply protocol negotiation. Fuel supply protocol negotiation is a procedure in which the vehicle and dispenser search for and agree on a fuel supply protocol to use for a fuel supply session. At this stage, the vehicle and dispenser can both select the communication protocol that the vehicle prefers most from among the protocols they support. A hydrogen refueling communication protocol negotiation method according to one embodiment of the present invention is a hydrogen refueling communication protocol negotiation method performed by a communication control device of a hydrogen fuel mobility 100, and includes the steps of: transmitting a first message to a communication entity associated with a dispenser 200 (S1110) including a list of at least one first fueling protocol and at least one first communication protocol required to perform a first fuel supply protocol supported by the hydrogen fuel mobility 100; and receiving a response message from the communication entity associated with the dispenser 200 (S1130) including a second communication protocol selected from at least one first communication protocol. The communication entity associated with the dispenser 200 may be the electronic control unit 210 of the dispenser 200, or a separate communication device mounted on the dispenser 200, or an electronic control unit or separate communication device in the refueling station system 220 may communicate with the vehicle / hydrogen fuel mobility 100 on behalf of the dispenser 200.

[0216] The first message may include priority information based on the preference for hydrogen fuel mobility 100, as shown in Table 6. Furthermore, each message may be defined based on Tables 4 through 6.

[0217] At this time, the response message may include a second communication protocol selected from at least one first communication protocol based on preference-based priority information. The hydrogen fuel mobility 100 or the dispenser 200 can select the second communication protocol based on preference-based priority information either individually or in cooperation with each other. Furthermore, the act of finally transmitting an acknowledgment message to the other party to finish the protocol negotiation process can be mainly performed by the hydrogen fuel mobility 100, but this can be modified so that it can be performed by the dispenser 200. In this case, the dispenser 200 may first send a list of supported protocols, and the hydrogen fuel mobility 100 may provide feedback on the selected protocol.

[0218] The response message may include at least one first communication protocol and a second communication protocol selected from common communication protocols that are included in the protocols supported by the dispenser 200.

[0219] The response message may include a second communication protocol determined by the device type that has been fallbacked based on interoperability and backward compatibility between the hydrogen fuel mobility 100 and the dispenser 200 from among several first communication protocols required by the control device of the dispenser 200 to execute the first fuel supply protocol.

[0220] In this case, according to one embodiment of the present invention, if a common communication protocol does not exist, a No comm. communication standard is selected as shown in Figures 7 to 9, and a hydrogen fuel supply protocol is selected according to the No comm. communication standard based on predetermined rules, and hydrogen can be supplied as fuel. In this case, steps (S404) to (S405) described later can be simplified or omitted.

[0221] According to another embodiment of the present invention, if a common communication protocol does not exist, communication between the hydrogen fuel mobility 100 and the dispenser 200 may be terminated (S409).

[0222] Figure 12 is an operation flowchart illustrating the fuel supply protocol negotiation stage (S404) of the hydrogen refueling communication bidirectional process according to one embodiment of the present invention.

[0223] Referring to Figure 12, the step of negotiating a fuel supply protocol according to one embodiment of the present invention (S404) may include the step of transmitting a message to the dispenser containing information on a first fuel supply protocol applicable to hydrogen fuel mobility based on the results of the communication protocol negotiation (S403) (S1210), and the step of receiving a message from the dispenser containing information on a second fuel supply protocol selected from among fuel supply protocols that are commonly applicable between hydrogen fuel mobility and the dispenser (S1230).

[0224] If a second communication protocol is selected as a result of communication protocol negotiation (S403), a message containing information for at least one first fuel supply protocol applicable to hydrogen fuel mobility may be transmitted to the dispenser as a hydrogen fuel supply protocol supporting the selected second communication protocol (S1210).

[0225] The dispenser can select a hydrogen fuel supply protocol that supports the second communication protocol from among the fuel supply protocols applicable to the dispenser and the first fuel supply protocol that are common to both, and then select a second fuel supply protocol from among the selected common fuel supply protocols. At this time, the second fuel supply protocol may be selected based on interoperability and / or compatibility, or it may be selected based on a preference set by the hydrogen fuel mobility or the dispenser.

[0226] Referring to the embodiment in Figure 12, the dispenser receives a message from the hydrogen fuel mobility vehicle containing information on a first fuel supply protocol applicable to the hydrogen fuel mobility vehicle (S1210), compares the first fuel supply protocol with the fuel supply protocols applicable to the dispenser, selects a second fuel supply protocol from among the common fuel supply protocols applicable to both the hydrogen fuel mobility vehicle and the dispenser, and transmits a message containing information on the selected second fuel supply protocol to the hydrogen fuel mobility vehicle (S1130).

[0227] At this point, although not shown in Figure 12, the process may further include a step in which the dispenser requests information from the hydrogen fuel mobility vehicle, including a list of first fuel supply protocols applicable to the hydrogen fuel mobility vehicle, prior to step (S1210).

[0228] In another embodiment of the present invention, a dispenser may first transmit a message to the hydrogen fuel mobility device containing information about its applicable fuel supply protocol, and the hydrogen fuel mobility device may select a specific fuel supply protocol from among the common fuel supply protocols and transmit a message to the dispenser containing information about the selected specific fuel supply protocol.

[0229] This could further involve the hydrogen fuel mobility requesting information from the dispenser, including a list of applicable fuel supply protocols.

[0230] According to one embodiment of the present invention, the objective, prerequisites, and subsequent conditions of step (S404) are shown in Table 9.

[0231] [Table 9]

[0232] According to one embodiment of the present invention, the contents of the messages transmitted and received in step (S1210) are shown in Table 10.

[0233] [Table 10]

[0234] Information for the first fuel supply protocol may include at least one of the following: the index of the first fuel supply protocol, the name of the first fuel supply protocol, the version of the first fuel supply protocol, the sub-protocol of the first fuel supply protocol, and the preference for the first fuel supply protocol. According to one embodiment of the present invention, the contents of the response messages transmitted and received in step (S1230) are shown in Table 11.

[0235] [Table 11]

[0236] The message containing information regarding the second fuel supply protocol may further include information on whether the fuel supply protocol negotiations were successful or not. The content of the message transmitted in step (S1210) according to one embodiment of the present invention is shown in Table 12.

[0237] [Table 12]

[0238] As shown in Table 12, hydrogen fuel mobility can provide the dispenser with parameter information in table format, which includes an arbitrarily assigned name for the supported fuel supply method or fuel supply protocol, revision date (year) and version information, information on whether or not subprotocols are present, and preference information.

[0239] In another embodiment of the present invention, the dispenser may proactively exchange its own communication protocols and parameters with the hydrogen fuel mobility instead of the hydrogen fuel mobility, and may prioritize and provide the hydrogen fuel mobility with the communication protocols supported by the dispenser.

[0240] Table 11 shows that PRHYDE (Protocol for heavy-duty HYDrogEn refueling) is presented from one of the European projects that has been developing heavy-duty vehicle refueling protocols, RTR-HFP is presented from a type of protocol concept that improves refueling efficiency based on real-time communication, and ANN-MPC may be presented from a type of protocol concept that collects and analyzes data from the refueling site and predicts and applies it to actual refueling conditions.

[0241] Examples of messages transmitted in step (S1230) according to one embodiment of the present invention are shown in Tables 13 and 14 below.

[0242] [Table 13]

[0243] According to Table 13, the dispenser can select the fuel supply protocol corresponding to index 2 and transmit a response message to the hydrogen fuel mobility vehicle including the result code OK.

[0244] [Table 14]

[0245] According to Table 14, if the dispenser fails to find a compatible protocol in the list of fuel supply protocols supported by hydrogen fuel mobility received from the hydrogen fuel mobility, it can transmit a response message to the hydrogen fuel mobility that includes information in the ResultCode field indicating that there is no common protocol (e.g., FAIL_NO_COMMON_PROTOCOL). The examples in Tables 13 and 14 can also be applied when the dispenser responds to the hydrogen fuel mobility by selecting a second communication protocol from the common communication protocols at stage (S1130) in Figure 11.

[0246] Figure 13 is a flowchart illustrating the fueling parameter exchange / negotiation stage (S405) that can be adopted in a hydrogen refueling communication bidirectional process according to one embodiment of the present invention.

[0247] The fuel supply parameter exchange / negotiation phase (S405) may include a phase in which hydrogen fuel mobility and dispensers exchange detailed parameters necessary for implementing the fueling protocol.

[0248] Referring to Figure 13, the step of negotiating fuel supply parameters (S405) may include the step of transmitting a message to the dispenser containing information on the fuel supply parameters on the hydrogen fuel mobility side required by the second fuel supply protocol selected as a result of the fuel supply protocol negotiation (S404) (S1310), and the step of receiving a message from the dispenser containing compatibility information on the dispenser side for the fuel supply parameters on the hydrogen fuel mobility side (S1350).

[0249] The step of negotiating fuel supply parameters (S405) may include receiving a message from the dispenser (S1330) containing information on the dispenser-side fuel supply parameters required by the second fuel supply protocol selected as a result of the fuel supply protocol negotiation (S404), and transmitting a message to the dispenser (S1370) containing compatibility information on the hydrogen fuel mobility side with respect to the dispenser-side fuel supply parameters.

[0250] In step (S1310), the hydrogen fuel mobility system transmits a message containing information about the fuel supply parameters on the hydrogen fuel mobility side, and the Accepted field for the relevant parameters <pending>The settings can be left in place and transmitted to the dispenser.

[0251] Similarly, the dispenser transmits a message containing information about the fuel supply parameters on the dispenser side in step (S1330), and the Accepted field for the relevant parameters <pending>It can be transmitted to hydrogen fuel mobility vehicles while remaining in that setting.

[0252] Hydrogen fuel mobility transmits a message as a response to a message received in stage (S1330), containing information about the fuel supply parameters on the dispenser side, while setting the Accepted field for the relevant parameters. <ok>or <true>It can be set to respond to the dispenser (S1350).

[0253] The dispenser, as a response message to the message received in step (S1310), transmits a message containing information about the fuel supply parameters on the hydrogen fuel mobility side, while setting the Accepted field for the relevant parameters. <ok>or <true>It can be set to respond to hydrogen fuel mobility (S1370).

[0254] At this time, the hydrogen fuel mobility and dispenser can respond by displaying whether each fuel supply parameter is Accepted or not. The Accepted field for unagreed parameters is <false>This may be displayed.

[0255] Hydrogen fuel mobility and dispensers can reach an agreement on all parameters by repeatedly sending and receiving messages and responding to those messages.

[0256] The parameters to be exchanged may include parameters to support fueling method compatibility, parameters for physical characteristics, monitoring parameters, and acceptance-related parameters.

[0257] Here, compatibility support parameters include pressure class, CHSS category, etc., parameters for physical characteristics include maximum allowable CHSS pressure, maximum allowable CHSS temperature, maximum allowable speed, CHSS volume, etc., monitoring parameters include current CHSS pressure, current CHSS temperature, etc., and acceptance-related parameters may include information indicating acceptance or rejection, such as yes (true) or no (false). The aforementioned parameters may each have information for one of the pre-specified levels or settings, and information for UCDC levels that are different from or identical to each other.

[0258] On the other hand, the dispenser has parameters that can be supported (<DIS’s parameters> (In a simplified way)<DIS’s params> An OK message indicating that information regarding the hydrogen fuel mobility and parameters for the hydrogen fuel mobility have been received and accepted can be transmitted to the hydrogen fuel mobility (S1330, S1370).

[0259] Secondary parameters related to fuel supply parameter exchange / negotiation may include parameters to support fuel supply method compatibility, parameters for physical characteristics, parameters related to fueling goals, monitoring parameters, and acceptance-related parameters.

[0260] Here, compatibility support-related parameters include fuel delivery temp., selected fueling table, etc., parameters for physical characteristics include maximum fuel delivery pressure, maximum fuel delivery temperature, minimum fuel delivery temperature, maximum fuel delivery velocity, etc., fuel delivery target-related parameters include target SOC, target final CHSS pressure, target final CHSS temperature, target APR, expected fueling duration, etc., monitoring parameters include current fuel delivery temperature, ambient temperature, etc., and acceptance-related parameters may include parameters such as "accepted". The aforementioned parameters may each have information set for one of the pre-set levels or set values, and information for UCDC levels that are different from or identical to each other.

[0261] In this way, hydrogen fuel mobility can provide the dispenser with parameters listed in a table format. The listed parameters include FCEV parameters that are compatible with UCDC levels, which are discussed during the fuel supply protocol negotiation phase.

[0262] As mentioned above, once the communication link is established and the communication and fuel supply protocols are selected during the protocol negotiation phase, hydrogen fuel mobility and dispensers can exchange various parameters to verify whether they can perform mutually compatible fuel supply procedures. Here, the information necessary to perform safe and efficient fuel supply procedures may include compatibility parameters, physical characteristics, fuel supply targets, and monitoring parameters.

[0263] The interchangeability parameters include, for example, pressure ratings, fuel supply transmission temperature, etc., the physical characteristics include, for example, maximum CHSS pressure, maximum flow rate, etc., the fuel supply targets include target SOC, target CHSS pressure, etc., and the monitoring parameters can include the current CHSS temperature, ambient temperature, etc.

[0264] If it is impossible to find interchangeable media variables and the fuel supply cannot proceed, the FCEV can return to the communication protocol negotiation stage to attempt other protocol negotiations or operate to stop fuel supply to the dispenser. And in the communication protocol negotiation stage that returns due to the failure in the fuel supply parameter exchange stage, the FCEV can be configured to propose to the dispenser a set of protocols that are supported except for the protocol that failed in the fuel supply parameter exchange stage.

[0265] When the fuel supply protocol is negotiated according to the above-described use case (UC-4), the vehicle and the dispenser can negotiate specific parameters for the fuel supply protocol, notify the static or dynamic state, and exchange detailed fuel supply parameters to determine the fuel supply target. Here, if the fuel supply parameter negotiation fails due to non-interchangeability, it can return to UC-3 to select another fuel supply protocol or return to UC-1 to select another communication protocol, and if these are not successfully performed, the current communication can be terminated.

[0266] According to the above-described configuration, certain fueling protocols can be performed on a non-communication (Non Comm.) basis. One-way IrDA may be required for certain fueling protocols to be performed. Two-way communication may be required for certain fueling protocols to be performed. All of two-way communication and one-way IrDA may be required for certain fueling protocols to be performed.

[0267] To perform a certain fuel supply protocol, a predetermined UCDC level or an even higher UCDC level may be required. At least one or more fuel supply protocols may be proposed based on the type or kind of the hydrogen electric vehicle and / or the type or kind of the dispenser. The proposed fuel supply protocols may be proposed with different priorities. Considering the priorities of the proposed fuel supply protocols, the communication protocol required by the fuel supply protocol and the communication protocol between the hydrogen electric vehicle and the dispenser may be finally determined based on whether the communication protocol is supported by the hydrogen electric vehicle and / or the dispenser.

[0268] In another embodiment of the present invention, either the hydrogen fuel mobility or the dispenser may first transmit the fuel supply parameters to the other party, and the other party may maintain the parameters that are accepted among the received fuel supply parameters and respond with a message including the newly reconfigured fuel supply parameters after changing the parameters that are not accepted.

[0269] In another embodiment of the present invention, the hydrogen fuel mobility and the dispenser may perform parameter negotiation step by step. The hydrogen fuel mobility and the dispenser may first negotiate a part of the parameters and then perform an exchange / negotiation process for the sub-parameters of the parameters for which an agreement has been derived.

[0270] In another embodiment of the present invention, each message including the fuel supply parameters may be set such that if a response message cannot be received within a preset message processing time, it is considered that no agreement has been reached.

[0271] The following Table 15 illustrates the content of the message including the fuel supply parameters on the hydrogen fuel mobility side according to an embodiment of the present invention.

[0272] [Table 15]

[0273] Table 16 below shows the contents of a message including fuel supply parameters on the dispenser side according to one embodiment of the present invention.

[0274] [Table 16]

[0275] During the fuel supply parameter negotiation phase (S405), hydrogen fuel mobility and dispensers can generate and communicate messages to the other party containing ranges / values ​​for fueling parameters. These parameters may include physical properties (simply put, "physical parameters"), monitoring parameters, safety policy parameters, and acceptance parameters.

[0276] Here, physical parameters include receptacle type, pressure class, CHSS category, CHSS type, CHSS capacity, maximum allowable CHSS pressure, maximum allowable CHSS temperature, and maximum allowable speed; monitoring parameters include current CHSS pressure and current CHSS temperature; safety policy-related parameters include emergency policy and safety enforcement level; and acceptance-related parameters may include information indicating acceptance or rejection, such as yes, false, or pending.

[0277] Parameters related to fuel supply parameter negotiations may include physical characteristics-related parameters (simply put, "physical parameters"), monitoring parameters, fuel supply target-related parameters, safety policy-related parameters, and acceptance-related parameters.

[0278] Here, physical parameters include fuel delivery temp., maximum fuel delivery pressure, maximum fuel delivery temperature, minimum fuel delivery temperature, and maximum fuel delivery velocity; monitoring parameters include current fuel delivery temperature and ambient temperature; fuel delivery target-related parameters include selected fueling table, target SOC, target final CHSS pressure, target final CHSS temperature, target APR, and expected fuel delivery time; and acceptance-related parameters may include parameters such as "accepted." The aforementioned parameters may each have information set for one of the pre-set levels or set values, and information for UCDC levels that are different from or identical to each other.

[0279] In this way, FCEV can provide the dispenser with parameters listed in a table format. The listed parameters include FCEV parameters that are compatible with UCDC levels discussed during the fuel supply protocol negotiation phase.

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

[0281] Also, after receiving a fuel supply parameter negotiation request message, if the dispenser discovers that it is not compatible with the vehicle's fuel supply parameters, the dispenser can transmit a fuel supply parameter negotiation response message with "result" set to "failure" to the FCEV to indicate incompatibility for the corresponding vehicle. The result indicates the value or information included in the result code field, and failure means a failure at a specific time and can be expressed as an expression indicating incompatibility such as "fail_incompat".

[0282] Also, after receiving a fuel supply parameter negotiation request message, if the FCEV discovers that the fuel supply mediation variables of the dispenser are not compatible, the FCEV can transmit an error notification request message with "reason" set to each predefined error code to the dispenser to indicate incompatibility to the dispenser.

[0283] On the other hand, before starting fuel supply, the vehicle and the dispenser can confirm whether all safety conditions are met through the use case (UC6) for safety check-in. This step is optional, but it is preferable to define a dedicated safety check-in procedure in the fuel supply protocol to ensure the desired safety level in an accurate and explicit manner.

[0284] FIG. 14 is a conceptual diagram illustrating a table of parameters transmitted from the hydrogen fuel mobility to the dispenser side in the fuel supply parameter negotiation / exchange process according to an embodiment of the present invention.

[0285] FIG. 15 is a conceptual diagram illustrating a table of parameters transmitted from the dispenser to the hydrogen fuel mobility side in the fuel supply parameter negotiation / exchange process according to an embodiment of the present invention.

[0286] Referring together to Figures 13 and 15, a communication-based fuel supply parameter exchange method for hydrogen refueling according to one embodiment of the present invention is a communication-based parameter exchange method for hydrogen refueling performed by a communication control device of a hydrogen fuel mobility 100, and includes the steps of: transmitting a first parameter (S1310) to a communication entity associated with a dispenser 200, the first parameter including at least one of at least one first hydrogen refueling method compatibility and at least one first physical characteristics supported by the hydrogen fuel mobility 100; and receiving a response message (S1370) from the communication entity associated with the dispenser 200, the second parameter including at least one of at least one second hydrogen refueling method compatibility, at least one second physical characteristic, and a fueling goal supported by the dispenser 200.

[0287] The communication entity associated with the dispenser 200 may be the electronic control unit 210 of the dispenser 200, or a separate communication device mounted on the dispenser 200, or an electronic control unit or separate communication device in the refueling station system 220 may communicate with the vehicle / hydrogen fuel mobility 100 on behalf of the dispenser 200.

[0288] In this case, the first parameter may further include a first monitoring parameter supported by the hydrogen fuel mobility 100. The second parameter may further include a second monitoring parameter supported by the dispenser 200.

[0289] In one embodiment of the present invention, a method for exchanging communication parameters for hydrogen refueling, the parameter exchange process may be terminated based on an acknowledgment message (OK message) included in the response message. The parameter exchange process may be terminated when the hydrogen fuel mobility 100 and the dispenser 200 accept all the exchanged parameters, or it may be terminated if either party does not accept the exchanged parameters. If acceptance is not achieved, the protocol negotiation process may be revisited or the refueling session may be terminated through a process described later.

[0290] In one embodiment of the present invention, a communication parameter exchange method for hydrogen refueling may include at least one of the following: pressure class and refueling tank category of hydrogen fuel mobility 100.

[0291] In a communication parameter exchange method for hydrogen refueling according to one embodiment of the present invention, at least one of the following first physical characteristics may be at least one of the following: Maximum allowed CHSS pressure, Maximum allowed CHSS temperature, Maximum allowed flow rate, and CHSS volume.

[0292] In one embodiment of the present invention, a method for exchanging communication parameters for hydrogen refueling, the first parameter may further include acceptance-related parameters of the hydrogen fuel mobility 100.

[0293] In one embodiment of the present invention, a communication parameter exchange method for hydrogen refueling, the first monitoring parameter may include at least one of the following: current refueling tank pressure (Current CHSS Pressure) and current refueling tank temperature (Current CHSS Temperature).

[0294] In a communication parameter exchange method for hydrogen refueling according to one embodiment of the present invention, at least one second refueling method interchangeability may include at least one of the following: the fueling delivery temperature of the dispenser 200 and the selected fueling table. The selected fueling table may include a sequence table of the refueling protocol selected during the protocol negotiation process and may be included in the OK message of S1330.

[0295] In one embodiment of the present invention, a method for exchanging communication parameters for hydrogen refueling, at least one of the following second physical characteristics may be at least one of the following: Max Fuel Delivery Pressure, Max Fuel Delivery Temperature, Min Fuel Delivery Temperature, and Max Fuel Delivery Flow Rate.

[0296] In a communication parameter exchange method for hydrogen refueling according to one embodiment of the present invention, the refueling target may include at least one of the following: Target SoC, Target Final CHSS Pressure, Target Final CHSS Temperature, Target Average Fueling Rate (APR), and Expected Fueling Duration.

[0297] In one embodiment of the present invention, a method for exchanging communication parameters for hydrogen refueling, the second parameter may further include acceptance-related parameters of the dispenser 200.

[0298] In one embodiment of the present invention, a communication parameter exchange method for hydrogen refueling may include at least one of the following: current fuel delivery temperature and ambient temperature.

[0299] Hydrogen fuel mobility 100 can provide first parameters in a table format in stages (S1310) that are compatible with the UCDC levels negotiated during the protocol negotiation process.

[0300] Dispenser 200 can provide a second set of parameters compatible with the UCDC level negotiated during the protocol negotiation process in a table format, in stages (S1330). At this time, the second set of parameters may include a message indicating acceptance of the first set of parameters provided in stage (S1310).

[0301] If hydrogen fuel mobility 100 or dispenser 200 does not accept the exchanged parameters, hydrogen fuel mobility 100 may resume the protocol negotiation process. Alternatively, if hydrogen fuel mobility 100 or dispenser 200 does not accept the exchanged parameters, hydrogen fuel mobility 100 may terminate the refueling session.

[0302] In a protocol negotiation process that is carried out again following a parameter exchange process that failed because the hydrogen fuel mobility 100 or dispenser 200 did not accept the exchanged parameters, the hydrogen fuel mobility 100 can propose a set of supported protocols other than the protocols provided in the failed parameter exchange process.

[0303] Table 17 illustrates the contents of a message including fuel supply parameters on the hydrogen fuel mobility side according to another embodiment of the present invention.

[0304] [Table 17]

[0305] Table 18 illustrates the content of a message including fuel supply parameters on the dispenser side according to another embodiment of the present invention.

[0306] [Table 18]

[0307] A communication method according to one embodiment of the present invention may further include a step of renegotiating at least one of the communication protocol and fuel supply parameters if, as a result of fuel supply parameter negotiation (S405), the fuel supply parameters are incompatible between the hydrogen fuel mobility and the dispenser. In this case, the renegotiation step in the communication method according to one embodiment of the present invention can be repeated, with steps (S403), (S404), and (S405) being performed again. For example, one can go back at step (S403) and perform renegotiation from step (S403), and then perform steps (S404) and (S405) sequentially again. In yet another embodiment, one can go back at step (S404) and perform renegotiation from step (S404), and then perform steps (S405) sequentially again.

[0308] The renegotiation step in the communication method according to another embodiment of the present invention may simplify steps (S403), (S404), and (S405) or omit some processes. Alternatively, steps (S403) and (S404) may be combined to negotiate both the communication protocol and the fuel supply protocol.

[0309] The step of renegotiating using a communication method according to another embodiment of the present invention may be carried out based on the remaining list of communication protocols and fuel supply protocols, excluding the communication protocol or fuel supply protocol selected in steps (S403) and (S404). For example, based on the compatibility and / or interoperability information obtained in step (S401), the communication protocol and fuel supply protocol may be negotiated together based on a protocol list that includes both the communication protocol and the fuel supply protocol, depending on whether or not there is mutual support between the communication protocol and the fuel supply protocol.

[0310] A communication method according to one embodiment of the present invention may further include the steps of determining a third communication protocol and a third fuel supply protocol based on a predetermined policy if the fuel supply parameters are incompatible between the hydrogen fuel mobility and the dispenser as a result of fuel supply parameter negotiation (S405), and supplying hydrogen based on the third communication protocol and the third fuel supply protocol. In this case, the third fuel supply parameters may be determined based on the third fuel supply protocol, and the step of supplying hydrogen may be carried out based on the third fuel supply protocol and the third fuel supply parameters.

[0311] For example, if communication between the hydrogen fuel vehicle and the dispenser becomes impossible due to changes in the communication environment, the dispenser can fall back to No Communication mode and supply hydrogen fuel using a No Communication-based hydrogen fuel supply protocol.

[0312] In one embodiment of the present invention, if the fuel supply parameters are incompatible between the hydrogen fuel mobility and the dispenser as a result of fuel supply parameter negotiation, the communication method can perform the step (S409) of terminating communication between the dispenser and the hydrogen fuel mobility.

[0313] Referring again to Figure 4, a safety check-in step (S406) that can be adopted in a hydrogen refueling communication bidirectional process according to one embodiment of the present invention is illustrated.

[0314] During the safety check-in phase (S406), hydrogen fuel mobility, including hydrogen fuel vehicles and dispensers, can verify that all necessary safety conditions have been met before actual fuel supply begins.

[0315] Once the fuel supply parameters are swapped and the hydrogen fuel mobility and dispenser are deemed compatible, the hydrogen fuel mobility and dispenser can perform a safety check to confirm that the fuel supply is safe. The safety check may be implicitly performed within the fuel supply protocol, and the safety check-in stage (S406) may be omitted in implementation.

[0316] Furthermore, during the safety check-in phase (S406), the hydrogen fuel mobility and / or dispenser can check whether the nozzle-receptacle is secured, check for leaks, and check the last-minute status.

[0317] Furthermore, if the fuel supply protocol assists with safety check-in after receiving a fuel supply parameter negotiation response message from the dispenser, the hydrogen fuel mobility can initiate the safety check-in phase (S406) by transmitting a safety check-in request message to the dispenser within the message sequence setting time.

[0318] Hydrogen fuel mobility vehicles and dispensers can exchange messages for coupler checks. The hydrogen fuel mobility vehicle can send a message to the dispenser containing information indicating the result of its own coupler check (e.g., Hydrogen Fuel Mobility: OK), and the dispenser can send a message to the hydrogen fuel mobility vehicle containing information indicating the result of its own coupler check (e.g., DP: OK).

[0319] Furthermore, the hydrogen fuel mobility vehicle and the dispenser can exchange messages related to gas leak checks. During this exchange of leak check-related messages, the dispenser can transmit information to the hydrogen fuel mobility vehicle indicating that a leak check is in progress (ongoing). The hydrogen fuel mobility vehicle can then transmit information to the dispenser indicating that it is waiting for the leak check results (waiting). Once the leak check is complete, the dispenser can transmit a message to the hydrogen fuel mobility vehicle requesting the measured tank volume along with information indicating that the leak check is complete (Done).

[0320] Furthermore, the dispenser can transmit messages to the hydrogen fuel mobility for immobilized status checks, and the hydrogen fuel mobility can transmit messages to the dispenser indicating that it is ready for a status check.

[0321] In this way, when a hydrogen fuel mobility device reports parameters such as its current state or immobilization status to the dispenser, the dispenser can report parameters such as the coupler lock status, leak check status, and predicted hydrogen fuel mobility tank capacity to the hydrogen fuel mobility device.

[0322] Once the aforementioned safety check-in phase (S406) is completed, fuel supply may commence. During fuel supply, the hydrogen fuel mobility and dispenser can exchange information and monitor various state parameters to ensure that fuel supply is carried out safely and efficiently. If necessary, the hydrogen fuel mobility or dispenser can control the fuel supply phase (S406) or send control messages requesting the other party to take action to address safety-related conditions. The parameters and commands exchanged may vary depending on the actual fuel supply protocol.

[0323] Step (S407) is a monitoring and control step that can be used in a hydrogen refueling communication bidirectional process according to one embodiment of the present invention.

[0324] During the monitoring and control phase (S407), the hydrogen fuel mobility and / or dispenser can monitor the fuel supply status and control fuel supply as needed. Once all safety checks are confirmed, the hydrogen fuel mobility and dispenser can begin fuel supply using the selected fuel supply protocol with the given parameters. While refueling, the hydrogen fuel mobility and dispenser can exchange various measurement data to understand the fuel supply status and operate to detect critical accidents as quickly and safely as possible.

[0325] Furthermore, hydrogen fuel mobility can transmit specific commands to the dispenser to control fuel supply stages (S407), such as starting and ending fuel supply. In this case, hydrogen fuel mobility can use UDP with DTLS to support black channel communication. Black channel communication may refer to communication that applies the black channel principle, where secure communication must be guaranteed despite the output characteristics of the communication channel having unsecured attributes or attributes unrelated to the application.

[0326] To explain this in more detail using the monitoring and control phase (S407) as an example, the hydrogen fuel mobility can transmit a message to the dispenser to start fuel supply control, and in response, the dispenser can transmit a message to the hydrogen fuel mobility that includes confirmation information (e.g., OK).

[0327] Furthermore, the hydrogen fuel mobility vehicle can transmit a message to the dispenser containing information about its own fuel supply loop (e.g., x, y, z), and the dispenser can provide the hydrogen fuel mobility vehicle with a message containing information about its own fuel supply loop corresponding to the hydrogen fuel mobility vehicle's fuel supply loop (e.g., a, b, c).

[0328] Furthermore, hydrogen fuel mobility can transmit fuel control request messages to the dispenser, which may contain information to slow down or reduce fuel supply, and the dispenser can transmit response messages to the hydrogen fuel mobility that contain information indicating a decrease in fuel status (e.g., slowing).

[0329] Furthermore, the hydrogen fuel mobility vehicle can transmit a fuel supply control request message to the dispenser requesting a halt (stop) in fuel supply, and the dispenser can transmit a fuel supply status response message to the hydrogen fuel mobility vehicle that includes information indicating whether or not fuel supply has been halted (stopping / stopped).

[0330] Thus, during the monitoring and control phase (S407), the hydrogen fuel mobility and the dispenser can continuously or periodically exchange parameters related to the fuel supply status. The hydrogen fuel mobility transmits the current tank temperature, current tank pressure, etc., to the dispenser, and the dispenser can provide the hydrogen fuel mobility with parameters related to fuel supply start, stop, increase (ramping up), decrease (ramping down), current injection pressure, subsequent fuel supply plan, etc.

[0331] Control-related request messages transmitted from hydrogen fuel mobility to the dispenser may include information and parameters regarding the start, pause, resume, and terminate of fuel supply. Reporting-related messages transmitted from hydrogen fuel mobility to the dispenser may also include information and parameters regarding the current tank temperature, current tank pressure, etc.

[0332] Messages related to reporting transmitted from the dispenser to the hydrogen fuel mobility may include information and parameters such as status information, current ambient temperature, current pressure ramp rate (PRR [Mbar / min]), deliver fuel flow rate (g / sec], current fuel delivery temperature, pre-cooling temperature, current fuel delivery pressure, whether the vehicle is fully refueled, whether the cooling dispenser is in use, whether fallback is in use, reason for fuel supply interruption, and the amount of hydrogen currently supplied.

[0333] Furthermore, messages related to target parameter updates transmitted from the dispenser to the hydrogen fuel mobility may include information and parameters such as target final tank pressure, target final tank temperature, target fuel supply APR, target SOC, current SOC, and estimated remaining duration.

[0334] On the other hand, when TCP is used in the aforementioned monitoring and control phase (S407), if the safety check-in phase by safety check-in response message or fuel supply protocol is omitted, the hydrogen fuel mobility can transmit a fueling loop request message to the dispenser within the message sequence setting time after receiving a fuel supply parameter negotiation response message from the dispenser. Request and response messages related to the fueling loop can be transmitted as DTLS messages.

[0335] After completing the hydrogen fuel supply through the aforementioned monitoring and control phase (S407), and before ending the session and separating the nozzle from the hydrogen fuel mobility, the hydrogen fuel mobility and dispenser can verify through a safety check-out use case that the quantity and each dispenser meet all safety requirements. While such a safety check-out phase is optional, it is preferable to define a dedicated safety check phase (S407) in the fuel supply protocol to ensure the desired level of safety in a precise and explicit manner.

[0336] A safety check-out step (S408) that can be adopted in a hydrogen refueling communication bidirectional process according to one embodiment of the present invention may be carried out as follows: The hydrogen fuel mobility and dispenser can verify through the safety check-out step (S408) that all necessary safety conditions have been met before separating the dispenser nozzle from the outlet. In other words, the hydrogen fuel mobility and dispenser can verify that it is absolutely safe for the user or operator to separate the nozzle from the hydrogen fuel mobility after fuel supply is complete.

[0337] For example, after a hydrogen fuel mobility vehicle receives a fuel supply loop response message from a dispenser in which the "result" is set to "OK", the "status" is set to "finished", or the prefix is ​​"stopped", if the hydrogen refueling protocol supports safe checkout, the hydrogen fuel mobility vehicle can initiate safe checkout and transmit a safe checkout request message to the dispenser within the message sequence setting time to perform the safe checkout stage (S408).

[0338] Hydrogen fuel mobility and dispensers can repeatedly report their respective statuses to each other until all safety checks are confirmed. If the two-way hydrogen refueling communication process does not ultimately require such safety checks, the use case for safety checks may be omitted.

[0339] To explain the aforementioned safety checkout stage (S408) in more detail with an example, the hydrogen fuel mobility can transmit a message to the dispenser containing information about the coupler check result (e.g., OK), and the dispenser can transmit a message to the hydrogen fuel mobility containing information indicating that the coupler check is in progress (e.g., Ongoing).

[0340] Furthermore, the hydrogen fuel mobility vehicle can transmit a message containing coupler inspection result information (e.g., OK) back to the dispenser, and the dispenser can transmit a message containing coupler inspection completion information (e.g., Done) back to the hydrogen fuel mobility vehicle.

[0341] Once the aforementioned coupler inspection completion information is confirmed to be successfully completed, the dispenser nozzle can be separated from the hydrogen fuel mobility receptacle by the user or operator.

[0342] During the aforementioned safety checkout phase (S408), the report message transmitted by the dispenser to the hydrogen fuel mobility may include information and parameters regarding the coupler unlock status. Coupler unlock status information may include information regarding locked, unlocked, icing, problem, etc.

[0343] The termination use case (UC9) can be performed if fuel delivery is completed and the nozzle is safely separated using the aforementioned hydrogen refueling protocol, or if a non-safely critical issue occurs during another use case.

[0344] A termination step (S409) that can be used in a hydrogen refueling communication bidirectional process according to one embodiment of the present invention can be carried out as follows.

[0345] The termination phase (S409) is the final stage of refueling, in which the hydrogen fuel mobility, including the hydrogen fuel mobility, and the dispenser can exchange information on the refueling results regarding refueling performance and methods, and / or information on the reasons for any unexpected interruptions in refueling, thereby completing all stages (S409) of hydrogen refueling. The termination use case may also be configured to handle any issues that are not safety-critical if they occur.

[0346] For example, after a hydrogen fuel mobility vehicle receives a safety checkout response message from a dispenser with the "result" set to "DONE," or a fuel supply loop response message with the "status" set to "finished" or prefixed with "stopped," the hydrogen fuel mobility vehicle can perform the termination phase (S409) by transmitting a termination request message to the dispenser.

[0347] To explain the final stage (S409) in more detail with an example, the hydrogen fuel mobility can send a message to the dispenser asking how much fuel has been supplied. In response to the hydrogen fuel mobility's question message, the dispenser can send a response message to the hydrogen fuel mobility that includes information (e.g., an X gram) about the amount of hydrogen supplied.

[0348] Furthermore, the hydrogen fuel mobility vehicle can transmit a confirmation request message to the dispenser upon completion of fuel supply, and the dispenser can transmit a goodbye message to the hydrogen fuel mobility vehicle as a response to the confirmation request message.

[0349] On the other hand, after fuel supply is complete and safety checks are confirmed, the hydrogen fuel mobility and the dispenser can exchange at least some book-keeping information for the hydrogen refueling session at the end stage (S409). The hydrogen fuel mobility and the dispenser can exchange summary information for the hydrogen refueling session before completing the end stage (S409).

[0350] Book-keeping information may include all information related to hydrogen refueling that is recorded in hydrogen fuel mobility and dispensers in accordance with established rules and policies, across all fueling sessions for hydrogen refueling and prior to the completion of the termination phase (S409) of Use Case 9 (UC9).

[0351] Bookkeeping or summary information may include information on how much fuel was supplied and what kind of reports were created. Report messages transmitted from hydrogen fuel mobility to the dispenser may include information and parameters on the current tank temperature and current tank pressure, while report messages transmitted from the dispenser to hydrogen fuel mobility may include information on the final SOC, the final average fueling rate (APR), the final measured tank pressure, the actual fuel supply time, and the actual amount of hydrogen supplied.

[0352] Once all the necessary information for the fuel supply session has been saved, the fuel supply session can be completely terminated.

[0353] Table 19 shows examples of communication data from some of the use cases mentioned above (UC5 to UC9).

[0354] [Table 19]

[0355] On the other hand, the error handling use case (UC10) is a functional block for handling situations where a non-fatal error has occurred, such as terminating the fuel supply procedure in the same way as a normal termination or abruptly interrupting communication. An error handling step (S410) that can be adopted in a hydrogen refueling communication bidirectional process according to one embodiment of the present invention can be carried out as follows.

[0356] The error handling stage (S410) may define error conditions related to the fuel supply protocol, provide detection criteria, and include response processes including notification, termination, and fallback mechanisms if an error is detected.

[0357] The error handling phase (S410) may be applied when a non-safe, non-fatal error occurs and further communication is impossible. In other words, the hydrogen fuel mobility and dispenser can handle non-safe, fatal errors occurring at any time during fuel supply in the error handling phase (S410). In other words, the hydrogen fuel mobility and dispenser can immediately interrupt fuel supply and move to the termination use case (UC9) after pausing the previously operating use case.

[0358] If a hydrogen fuel mobility system detects an event related to a non-safe fatal error, it can notify the dispenser of the reason for termination via a terminate request (TerminateReq) message and stop the current fuel supply session or the comm. session. The dispenser can respond to the terminate request message by terminating the current comm. session. If further communication is not possible, the current session may be terminated without further notification.

[0359] Furthermore, if a non-safety-critical error is detected in the hydrogen fuel mobility and the communication channel continues to operate, the hydrogen fuel mobility can send a TerminateReq message to the dispenser with the “action” set to “stop” and the “reason” set to an appropriate reason or reason code. An appropriate reason or reason code may include reasons such as “message is corrupted.”

[0360] The aforementioned termination request message may be transmitted in the event of non-critical communication errors, system errors, and qualitative errors, except in cases where recovery is not possible.

[0361] In other words, for successful fuel supply, communication must exhibit the behavior expected by the protocol, and fuel supply operation must be within the acceptable range of the fuel supply protocol. However, in reality, a variety of abnormal events can occur. Some of these errors are minor and can be easily handled, but some others cannot be recovered from and prevent fuel supply from proceeding. Therefore, in the error handling stage (S410), error conditions that are not critical to safety are defined and exemplary error conditions and possible responses are provided.

[0362] Examples of communication errors include disconnections, inability to recognize received data due to encoding or syntax errors, or received data being outside the acceptable range. System errors may include situations where the dispenser or hydrogen fuel mobility system independently detects a critical system error. Qualitative errors may include situations where the quality of communication performance fails to meet the required standards, or where the quality of data integrity or precision fails to meet the required standards.

[0363] The hydrogen refueling communication bidirectional process of this embodiment can perform the following specific error handling steps (S410) in response to the aforementioned error conditions: (1) to (4).

[0364] (1) If a non-safe error occurs and further communication becomes impossible, the hydrogen fuel mobility and dispenser may take safe measures to terminate communication and end the session, but will immediately stop fuel supply.

[0365] (2) If a non-fatal error occurs and the fuel supply is interrupted and the fuel supply is not completed, the fuel supply protocol may define a fallback mechanism, for example, by defining a non-communication fuel supply method.

[0366] (3) If a non-safety-critical error is detected in the hydrogen fuel mobility and the communication channel is still operational, the hydrogen fuel mobility may transmit a termination request message to the dispenser with “action” set to “stop” and “reason” set to an appropriate reason code.

[0367] (4) If a non-safety-critical error is detected by the dispenser and the communication channel is still operational, the dispenser may first immediately stop the fuel supply and transmit a termination request message to the hydrogen fuel mobility with “Operation” set to “Terminate” and “Reason” set to an appropriate reason or reason code.

[0368] As described above, the hydrogen refueling communication bidirectional process, including the fuel supply protocol, defines error conditions related to the fuel supply protocol, provides detection criteria, and if an error is detected by the detection criteria, an error handling stage (S410) including notification, termination stage (S410), and fallback mechanism can be performed.

[0369] On the other hand, a critical safety issue may occur during fuel supply in a hydrogen refueling system, requiring an emergency response.

[0370] An emergency handling step (S411) that can be adopted in a hydrogen refueling communication bidirectional process according to one embodiment of the present invention can be carried out as follows.

[0371] The emergency response phase (S411) may include response processes to prevent essential safety accidents by defining essential safety conditions requiring emergency response during refueling.

[0372] For safe fuel supply, communications must indicate the expected behavior according to the protocol, and fuel supply operations must remain within the safe limits of the fuel supply protocol. However, problems may occur during fuel supply, potentially leading the fuel supply system (or hydrogen refueling system) to reach a critical state that must be avoided at any cost. Therefore, the emergency handling phase (S411) can define safety-critical emergency conditions and possible responses to those conditions, and provide important cases to consider.

[0373] The fuel supply protocol can define emergency conditions related to the protocol, provide sensing criteria and performance requirements, and specify response stages (S411) to ensure that no hazardous situation is encountered.

[0374] Specifically, if the hydrogen fuel mobility system detects a high-pressure condition exceeding a previously set standard value during the hydrogen refueling phase (S411), the hydrogen fuel mobility system can transmit a first emergency stop request message to the dispenser, which includes information requesting the cessation of fuel supply due to the high pressure (e.g., Emg:Stop(high pressure)). The dispenser can then transmit a response message to the hydrogen fuel mobility system, which includes information indicating that it is processing an emergency fuel supply cessation in response to the first emergency stop request message (e.g., Emg:Stopping).

[0375] Furthermore, immediately after receiving the response message, or after a predetermined period of time has elapsed, the hydrogen fuel mobility vehicle may transmit the first emergency stop request message back to the dispenser. The dispenser may transmit a response message to the hydrogen fuel mobility vehicle that includes information indicating that the fuel supply has been urgently stopped by the first emergency stop request message (e.g., Emg:Stopped).

[0376] On the other hand, if the dispenser detects a hydrogen fuel leak during the hydrogen refueling phase (S411), the dispenser can transmit a second emergency stop request message to the hydrogen fuel mobility vehicle, which includes information indicating that it is processing a fuel supply interruption due to the leak (e.g., Emg:Stopping(leaking)). The hydrogen fuel mobility vehicle can transmit a response message to the dispenser, which includes information indicating that it has received the second emergency stop request message (e.g., Emg:Confirmed).

[0377] Furthermore, the dispenser can transmit a third emergency stop notification message to the hydrogen fuel mobility vehicle, which includes information indicating that it has handled the fuel supply interruption due to a leak (e.g., Emg:Stopped(leaking)). The hydrogen fuel mobility vehicle can transmit a response message to the dispenser, which includes information indicating that it has acknowledged the third emergency stop notification message (e.g., Emg:Confirmed).

[0378] According to the configuration described above, if a critical situation affecting the safety of hydrogen fuel mobility or a dispenser is detected, it can immediately take necessary measures to prevent a disaster, and, where possible, transmit an emergency notification message containing information about the situation to the other party and cut off communication.

[0379] When an emergency notification message is received, the hydrogen fuel mobility or dispenser can respond immediately with the action indicated in the emergency notification message, and the communication can be terminated without excessive delay. An emergency notification message consists of a header and a body attached to the header. The header contains information indicating that it is an emergency notification, and the message may contain values, information, or parameters for the class, type, and action of the emergency notification.

[0380] The aforementioned emergency notification message can be transmitted via TLS or DTLS messages, depending on the technology used for communication.

[0381] Referring again to Figure 4, the objectives, prerequisites, and subsequent conditions of the safety check-in stage (S406) can be illustrated by Table 20.

[0382] [Table 20]

[0383] As previously mentioned, if the fuel supply parameter negotiation phase (S405) is successfully carried out, the fuel supply protocol can proceed to the safety check-in phase (S406).

[0384] If the communication physical layer is specified to require a pairing procedure, the hydrogen fuel mobility and dispenser can re-check the pairing before dispensing hydrogen during the safety check-in phase (S406).

[0385] Even if the communication physical layer is not specified to require a pairing procedure, the hydrogen fuel mobility and dispenser can re-check the pairing before dispensing hydrogen during the safety check-in phase (S406).

[0386] After receiving a message from the dispenser indicating the completion of stage (S405) (e.g., FuelParamNegoRes), if the fuel supply protocol assists with the safety check-in stage (S406), the hydrogen fuel mobility can transmit a message to the dispenser within a predetermined time interval (e.g., MessageSequenceTimeout) indicating the start of the safety check-in stage (S406) (e.g., SafetyCheckInReq).

[0387] As an alternative embodiment, if a message indicating the completion of stage (S405) is transmitted to the other by either the hydrogen fuel mobility or the dispenser, either party may transmit a message indicating the start of the safety check-in stage (S406).

[0388] According to one embodiment of the present invention, messages transmitted and received during the safety check-in phase (S406) may be defined based on the content of each fuel supply protocol as specified in a standard such as ISO 19885-3.

[0389] According to one embodiment of the present invention, messages transmitted and received during the security check-in phase (S406) may include a result element containing the result value obtained by processing the request message. In this case, the result value provided by the result element may include, for example, "OK" if successful, "FAILED" if unsuccessful, and "PENDING" otherwise.

[0390] If all safety conditions are met when the hydrogen fuel mobility vehicle transmits the SafetyCheckInReq message to the dispenser, the result value of that message may be set to "OK".

[0391] If, by any chance, a hydrogen fuel mobility vehicle transmits a SafetyCheckInReq message to the dispenser, and several safety conditions have not yet been met, the result value of that message may be set to "PENDING".

[0392] After the dispenser receives the SafetyCheckInReq message, it can respond to the hydrogen fuel mobility with a SafetyCheckInRes message along with safety check parameters within the MessageResponseTimeout time interval.

[0393] If, by any chance, all safety conditions are met when the dispenser transmits the SafetyCheckInRes message to the hydrogen fuel mobility vehicle, the result value of that message may be set to "OK".

[0394] If, by any chance, certain safety conditions are not yet met when the dispenser transmits a SafetyCheckInRes message to a hydrogen fuel vehicle, the result value of that message may be set to "PENDING".

[0395] If a SafetyCheckInRes message with a result value set to "PENDING" is received, the hydrogen fuel mobility system can transmit another SafetyCheckInReq message to the dispenser within the MessageResponseTimeout period.

[0396] If a SafetyCheckInReq message with a result value set to "PENDING" is received, the dispenser can transmit other SafetyCheckInReq messages to the hydrogen fuel mobility within the MessageResponseTimeout period.

[0397] If a hydrogen fuel mobility vehicle or dispenser fails to confirm all safety conditions within a specified time (e.g., UCSafetyCheckInTimeout), it may transmit an ErrNotifReq message with the "reason" field set to the appropriate error code.

[0398] As an alternative implementation, a hydrogen fuel mobility vehicle or dispenser can transmit a request message to the other party indicating the commencement of a safety check-in, and the other party can respond with a response message to the safety check-in request message within a predetermined time interval.

[0399] Referring again to Figure 4, the objectives, prerequisites, and subsequent conditions for the monitoring and control phase (S407) can be illustrated by Table 21.

[0400] [Table 21]

[0401] As previously mentioned, once the safety check-in phase (S406) is successfully completed, the fuel supply protocol can proceed to the monitoring and control phase (S407).

[0402] If the safety check-in phase (S406) is omitted, and the fuel supply parameter negotiation phase (S405) is successfully completed, the fuel supply protocol can proceed to the monitoring and control phase (S407).

[0403] While the monitoring and control phase (S407) is being carried out, the dispenser can perform all the necessary steps to refuel the hydrogen fuel mobility.

[0404] When the TCP standard is used in fuel supply control and monitoring use cases, after receiving a SafetyCheckInRes message or, in embodiments where the safety check-in phase (S406) is omitted, the hydrogen fuel mobility can transmit a message (e.g., a FuelLoopReq message) to the dispenser requesting the start of the monitoring and control phase (S407) within a predetermined time interval (e.g., MessageSequenceTimeout).

[0405] When the aforementioned black channel is used, after transmitting the SafetyCheckInRes message or, in embodiments where the safety check-in stage (S406) is omitted, transmitting the FuelParamNegoRes message, the hydrogen fuel mobility (as the client) and the dispenser (as the server) can initiate a DTLS 1.3 handshake in accordance with RFC 9147 with a session resumption using NewSessionTicket. At this time, NewSessionTicket may be received from the dispenser.

[0406] After the DTLS 1.3 handshake is successfully completed (finished), the hydrogen fuel mobility can transmit a message (e.g., a FuelLoopReq message) to the dispenser requesting the start of the monitoring and control phase (S407) within a predetermined time interval (e.g., MessageSequenceTimeout).

[0407] In this case, 0-RTT does not need to be used for DTLS session resumption.

[0408] FuelLoopReq messages and their response messages (e.g., FuelLoopRes messages) can all be transmitted in accordance with the DTLS message standard.

[0409] In addition, further requirements may be necessary for the black channel method.

[0410] The FuelLoopReq message can be implemented based on the definition of each fuel supply protocol.

[0411] The fuel supply protocol allows static or dynamic data contained within FuelLoopReq and FuelLoopRes to be identified so that fuel supply status can be monitored and safety-related information can be exchanged.

[0412] The element names included in the FuelLoopReq message may include action, reason, etc., and can be illustrated in Table 22 below. Elements not illustrated in Table 22 below can be identified by their respective fuel supply protocol standards, such as ISO 19885-3.

[0413] [Table 22]

[0414] The element names included in the messages sent and received in stage S407 (e.g., FuelLoopRes messages) may include status, reason, result, etc., and can be illustrated in Table 23 below. Elements not illustrated in Table 23 below may be identified by their respective fuel supply protocol standards, such as ISO 19885-3.

[0415] [Table 23]

[0416] When a hydrogen fuel mobility device transmits a FeulLoopReq message, the dispenser can be expected to perform an action. The hydrogen fuel mobility device can transmit the message with the desired action code set to "action." This action code may be defined by the fuel supply protocol.

[0417] After receiving a FuelLoopReq message (for example, with "action" set to "start"), when the dispenser is ready to start, it can use the negotiated method to initiate the fuel supply procedure and respond with a FuelLoopRes message with "result" set to "OK".

[0418] If the dispenser is not ready to start after receiving a FuelLoopReq message (for example, with "action" set to "start"), the dispenser can respond with a FuelLoopRes message with "result" set to "pending".

[0419] After receiving a FuelLoopReq message (for example, with "action" set to "stop"), if the dispenser is ready to abort, it can abort the fuel supply procedure as defined in the fuel supply protocol and respond with a FuelLoopRes message with "result" set to "ONGOING".

[0420] After receiving a FuelLoopReq message (for example, with "action" set to "stop"), if the dispenser is ready to abort, it can immediately abort the fuel supply procedure and respond with a FuelLoopRes message with "result" set to "OK".

[0421] After receiving a FuelLoopReq message, the dispenser can respond with a FuelLoopRes message within a predetermined time interval (e.g., MessageSequenceTimeout).

[0422] If the dispenser has successfully processed the received FuelLoopReq message, it can transmit a FuelLoopRes message with "result" set to "OK".

[0423] If the dispenser was not successfully processed by the received FuelLoopReq message, it may transmit a FuelLoopRes message with the "result" set to "FAILED" or another appropriate error code.

[0424] The dispenser can transmit FuelLoopRes messages where "status" is set using one of the supported codes specified in Table 23 or the fuel supply protocol.

[0425] The dispenser can transmit a FuelLoopRes message with "status" set to "finished" once fuel delivery is complete (done) and the intended fuel delivery target has been achieved.

[0426] The dispenser can transmit a FuelLoopRes message when fuel supply is interrupted due to an error, with "status" set to "stop_error" and "reason" set to the appropriate reason code.

[0427] The dispenser can transmit a FuelLoopRes message with the status set to "stopping" if the "action" of the most recent FuelLoopReq message is set to "stop" and the fuel supply has not been completely stopped.

[0428] The dispenser can transmit a FuelLoopRes message with the status set to "stopped_requested" if the "action" of a recent FuelLoopReq message has been set to "stop" and fuel supply has been completely stopped.

[0429] When a hydrogen fuel mobility vehicle transmits a FuelLoopReq message with "action" set to "stop" and receives a FuelLoopRes message with "status" set to "stopping", the hydrogen fuel mobility vehicle can transmit a FuelLoopRes message with "action" set to "stop".

[0430] If a hydrogen fuel vehicle receives a FuelLoopRes message and fuel supply is not finished, the hydrogen fuel vehicle can transmit a FuelLoopReq message within a predetermined time interval (e.g., MessageSequenceTimeout).

[0431] In the event of a safety-critical incident, the hydrogen fuel mobility or dispenser can immediately transmit an EmergencyReq message, halting the fuel supply procedure and closing communications.

[0432] The embodiments related to step S407 described above have mainly focused on embodiments in which the hydrogen fuel mobility requests the start of each step and the dispenser responds, but the concept of the present invention is not limited thereto. In alternative embodiments of the present invention, either the hydrogen fuel mobility or the dispenser may transmit a message requesting the start of step S407 first, and the other party may perform step S407 by responding to the message requesting the start of step S407.

[0433] In stage S407, a message transmitted by either the hydrogen fuel mobility or the dispenser may include a request for monitoring regarding the status of the hydrogen fuel supply procedure. The response message sent by the other party may include the requested monitoring status information.

[0434] At this time, the conditions and related parameters that may be subject to a monitoring request may include a set of parameters that are exchanged in stage (S405). The conditions and related parameters that may be subject to a monitoring request may include the conditions and parameters of the hydrogen fuel mobility or dispenser. The conditions and related parameters that may be subject to a monitoring request may include the fuel supply conditions and / or related parameters of the hydrogen fuel mobility and / or dispenser that are changed or maintained by the hydrogen fuel supply procedure.

[0435] Furthermore, the conditions that may be subject to monitoring requests may include the status and / or information of the procedure itself in which fuel is supplied from the dispenser to the hydrogen fuel mobility. For example, this may include information such as whether the fuel supply procedure is ongoing, paused, or terminated, and / or, if stopped / terminated, whether it was stopped due to an error or finished due to achieving the target.

[0436] Referring again to Figure 4, the objectives, prerequisites, and subsequent conditions of the safe checkout stage (S408) can be illustrated by Table 24.

[0437] [Table 24]

[0438] A safety checkout stage (S408) may be performed to ensure that the hydrogen fuel mobility and dispenser meet safety conditions before terminating the session and unplugging the nozzle from the hydrogen fuel mobility. Although this stage (S408) is optional, it is strongly recommended that a dedicated safety checkout procedure be defined by the fuel supply protocol to ensure the desired level of safety in a precise and explicit manner.

[0439] The information exchange used in the safety checkout step may be used for the purpose of diagnosis and accountability in the event of a safety-related incident.

[0440] As previously mentioned, once the monitoring and control phase (S407) and associated fuel supply procedures are successfully completed (finished), the fuel supply protocol can proceed to the safe checkout phase (S408).

[0441] Regardless of whether a safe checkout is performed, a fuel supply protocol compliant with ISO 19885-2 can define a set of safety conditions that are confirmed between the hydrogen fuel mobility and the dispenser before the nozzle is unplugged.

[0442] After receiving a FuelLoopRes message with "Result" set to "OK" and "status" set to a prefixed value of "finished" or "stopped", and the fuel supply protocol assists with safe checkout, the hydrogen fuel mobility can transmit a message to the dispenser via the TLS channel within a predetermined time interval (for example, a MessageSequenceTimeout message requesting the start of the safe checkout phase (S408), e.g., SafetyCheckOutReq).

[0443] At this time, if the TCP / TLS channel connection is broken, the hydrogen fuel mobility can re-establish the TCP / TLS channel with the dispenser. The re-establishment process can be initiated by a TLS-resumption handshake using a NewSessionTicket received before transmitting the SafetyCheckOutReq message.

[0444] As an alternative embodiment, a message requesting the commencement of stage (S408) may be transmitted to the other party by either the hydrogen fuel mobility or the dispenser. In this case, stage (S408) may be performed by the other party responding to the message requesting the commencement of stage (S408).

[0445] According to one embodiment of the present invention, the messages transmitted and received during the safe checkout phase (S408) may be defined based on the content of the respective fuel supply protocol as specified in a standard such as ISO 19885-3.

[0446] According to one embodiment of the present invention, the message transmitted and received in the secure checkout stage (S408) may include a result value in the result type that is the result of processing the request message. In this case, the result value that may be provided in the result type may include, for example, "OK" if successful, "FAILED" if unsuccessful, and "PENDING" otherwise.

[0447] If, when a hydrogen fuel vehicle transmits a SafetyCheckOutReq message to the dispenser, it confirms that all safety conditions are met, the result value of that message may be set to "OK".

[0448] If, by any chance, a hydrogen fuel mobility vehicle transmits a SafetyCheckOutReq message to the dispenser, and several safety conditions have not yet been met, the result value of that message may be set to "PENDING".

[0449] After the dispenser receives the SafetyCheckOutReq message, it can respond to the hydrogen fuel mobility with a SafetyCheckOutRes message along with safety check parameters within the MessageResponseTimeout time interval.

[0450] If the dispenser confirms that all safety conditions are met when it transmits the SafetyCheckOutRes message to the hydrogen fuel mobility vehicle, the result value of that message may be set to "OK".

[0451] If, by any chance, certain safety conditions are not yet met when the dispenser transmits a SafetyCheckOutRes message to a hydrogen fuel vehicle, the result value of that message may be set to "PENDING".

[0452] If a SafetyCheckOutRes message with a result value set to "PENDING" is received, the hydrogen fuel mobility system can transmit further SafetyCheckOutReq messages to the dispenser within the MessageResponseTimeout time interval.

[0453] If a SafetyCheckOutReq message with a result value set to "PENDING" is received, the dispenser can transmit other SafetyCheckOutReq messages to the hydrogen fuel mobility within the MessageResponseTimeout time interval.

[0454] If a hydrogen fuel mobility vehicle or dispenser fails to confirm all safety conditions within a specified time (e.g., UCSafetyCheckOutTimeout), it may transmit an ErrNotifReq message with the "reason" field set to the appropriate error code.

[0455] As an alternative implementation, either the hydrogen fuel mobility or the dispenser can transmit a request message to the other party indicating the commencement of a safe checkout, and the other party can respond with a response message to the safe checkout request message within a predetermined time interval.

[0456] According to one embodiment of the present invention, if a non-fatal error is detected during the monitoring and control phase (S407) and fuel supply is interrupted before fuel supply is completed, the fuel supply protocol can define a fallback mechanism that ensures backward compatibility among mutually compatible mechanisms between the hydrogen fuel mobility and the dispenser, and restart and terminate fuel supply based on the fallback mechanism.

[0457] In this case, the fallback mechanism could be, for example, a non-communication fueling method.

[0458] As an alternative embodiment, if a non-fatal error is detected in the monitoring and control phase (S407) and fuel supply is interrupted before fuel supply is completed, the hydrogen fuel mobility and dispenser may restart some or all of the communication protocol negotiation phase (S403), fuel supply protocol negotiation phase (S404), and fuel supply parameter negotiation phase (S405).

[0459] As an alternative embodiment, the hydrogen fuel mobility and the dispenser can reduce the amount of information exchanged in the process of repeating some or all of the communication protocol negotiation stage (S403), fuel supply protocol negotiation stage (S404), and fuel supply parameter negotiation stage (S405) using the interoperability information obtained in the discovery and pairing stage (S401). For example, if a communication or fuel supply state is identified in which it is not possible to maintain a protocol that has already been negotiated and selected, some or all of the communication protocol negotiation stage (S403), fuel supply protocol negotiation stage (S404), and fuel supply parameter negotiation stage (S405) may be repeated, excluding the previously selected protocol.

[0460] As an alternative embodiment, if changes in the communication environment and fuel supply infrastructure are detected as safe, non-fatal errors during the monitoring and control phase (S407), and fuel supply is interrupted before completion, the hydrogen fuel mobility and dispenser may restart some or all of the communication protocol negotiation phase (S403), fuel supply protocol negotiation phase (S404), and fuel supply parameter negotiation phase (S405).

[0461] Changes in the communication environment can include situations where the communication channel connection is broken (disconnected).

[0462] Changes in the communication environment may include cases where the received data cannot be recognized, and cases where the received data is in an unacceptable range.

[0463] Changes in the communication environment may include situations where the required level of communication performance cannot be met.

[0464] Changes in the communication environment may include situations where the integrity or precision of data exchanged through communication cannot meet the required standards.

[0465] Changes in the fuel supply infrastructure may cause changes or maintenance of fuel supply parameters on the hydrogen fuel mobility side based on control parameters for fuel supply on the dispenser side, but may also include cases where the changes or maintenance of fuel supply-related parameters on the hydrogen fuel mobility side fail to meet the required level.

[0466] Some of the safety conditions checked or monitored during the safety check-in phase (S406), monitoring and control phase (S407), and safety check-out phase (S408) are illustrated in Table 19 above, but the following may be considered in addition or in addition to the above:

[0467] Safety conditions may include safety-related elements on both sides of the hydrogen fuel mobility and the hydrogen refueler or dispenser for hydrogen refueling (fuel supply), and / or the fastening condition of the nozzles and receptacles on both sides for initiating hydrogen fuel supply.

[0468] On the hydrogen fuel mobility side, factors such as the pressure and temperature inside the hydrogen tank may also be included.

[0469] At the hydrogen refueling station, this could include factors such as cylinder temperature, refueling pressure, and ambient temperature.

[0470] Safety conditions on both sides of the connection and fuel supply path may include nozzle-receptacle connection status—that is, whether or not it is connected, the state of connection, and the leakage status.

[0471] The nozzle-receptacle connection status may include information on whether it is in a suitable and / or sufficient condition to carry out the hydrogen fuel supply procedure.

[0472] In one of the alternative embodiments shown in Figure 4, if the safety check-in stage (S406) performs minimal condition checks, i.e., checks of safety elements including whether or not the nozzle-receptacle is fastened and the fastening status, the safety check-in stage (S406) may be performed prior to the fuel supply parameter negotiation stage (S405).

[0473] In one of the alternative embodiments shown in Figure 4, if the safety check-in stage (S406) performs minimal condition checks, i.e., checks of safety elements including whether or not the nozzle-receptacle is fastened and the fastening status, then any remaining safety elements not checked in the safety check-in stage (S406) can be negotiated and checked in the fuel supply parameter negotiation stage (S405).

[0474] In one of the alternative embodiments shown in Figure 4, if the safety check-in stage (S406) performs minimal condition checks, i.e., checks of safety elements including whether or not there is a connection between the nozzle and the receptacle, and the condition of the connection, then any remaining safety elements not checked in the safety check-in stage (S406) can be monitored and checked in the monitoring and control stage (S407). In this case, the safety elements can be monitored and checked in the monitoring and control stage (S407) independently of (or regardless of) being negotiated and checked in the fuel supply parameter negotiation stage (S405).

[0475] In one of the alternative embodiments shown in Figure 4, multiple safety elements, including those checked in the safety check-in phase (S406), can be negotiated and checked in the fuel supply parameter negotiation phase (S405).

[0476] In one of the alternative embodiments shown in Figure 4, multiple safety elements, including those checked in the safety check-in phase (S406), may be monitored and checked in the monitoring and control phase (S407). In this case, the safety elements may be monitored and checked in the monitoring and control phase (S407) independently of (or separately from) those negotiated and checked in the fuel supply parameter negotiation phase (S405).

[0477] Figure 16 is a conceptual block diagram of the internal structure of a generalized computing system that can be installed in a hydrogen fuel mobility vehicle, dispenser, and / or refueling station as a communication device, communication control device, and / or electronic control device for hydrogen refueling according to one embodiment of the present invention.

[0478] Although not shown in the drawings of the embodiments in Figures 1 to 15, the processor and memory are electronically connected to each component, and the operation of each component can be controlled or managed by the processor.

[0479] At least a portion of the charging communication method for electric vehicle charging according to one embodiment of the present invention can be performed by the computing system 3000 shown in Figure 16.

[0480] A computing system 3000 according to one embodiment of the present invention may include at least one processor 3100 and a memory 3200 that stores instructions that the at least one processor 3100 perform at least one step. At least some steps of the method according to one embodiment of the present invention may be performed by the at least one processor 3100 loading and executing instructions from the memory 3200.

[0481] The processor 3100 may mean a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which the method according to an embodiment of the present invention is performed.

[0482] Each of the memory 3200 and the storage device 3400 may consist of at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory 3200 may consist of at least one of a read-only memory (ROM) and a random access memory (RAM).

[0483] Furthermore, the computing system 3000 may include a communication interface 3300 that performs communication over a wireless network.

[0484] Furthermore, the computing system 3000 may further include a storage device 3400, an input interface device 3500, an output interface device 3600, and the like.

[0485] Furthermore, each component included in the computing system 3000 can be connected by the bus 3700 to perform communication.

[0486] An apparatus including the processor 3100 according to one embodiment of the present invention may be, for example, a communicative desktop computer, laptop computer, notebook computer, smartphone, tablet PC, mobile phone, smart watch, smart glasses, e-book reader, PMP (portable multimedia player), portable game console, navigation device, digital camera, DMB (digital multimedia broadcasting) player, digital audio recorder, digital audio player, digital video recorder, digital video player, PDA (Personal Digital Assistant), etc.

[0487] A communication device for supplying hydrogen fuel according to one embodiment of the present invention is a device mounted on a hydrogen fuel mobility and / or dispenser that performs communication between the hydrogen fuel mobility and the dispenser, and includes a processor 3100 that receives and executes at least one instruction from a memory 3200.

[0488] A communication control device for a hydrogen fuel mobility 100 according to one embodiment of the present invention includes a memory 3200 for storing at least one instruction, and a processor 3100 for executing at least one instruction. The processor 3100 can transmit a request message to a dispenser containing information related to an action, including starting or stopping hydrogen fuel supply, based on a fuel supply protocol determined by negotiations between the dispenser that supplies hydrogen to the hydrogen fuel mobility and the hydrogen fuel mobility, and can receive a response message from the dispenser containing information regarding whether it has processed or is ready to process the action included in the request message.

[0489] The request message may include information related to the action of initiating hydrogen fuel supply, and the response message may include information on whether the dispenser is ready to begin hydrogen fuel supply.

[0490] If the response message indicates that the dispenser is not ready to begin supplying hydrogen fuel, the processor 3100 may transmit an additional second request message containing information related to the hydrogen fuel supply initiation action.

[0491] The request message may include information regarding the action of halting the hydrogen fuel supply, and the response message may include information regarding whether the dispenser has halted the hydrogen fuel supply.

[0492] If the response message indicates that the dispenser has not completely stopped supplying hydrogen fuel, the processor 3100 may transmit an additional second request message containing information related to the hydrogen fuel supply cessation action.

[0493] A request message may include a monitoring request regarding at least one condition related to the hydrogen fuel supply procedure, and a response message may include information about at least one condition.

[0494] The processor 3100 can check the safety status of the hydrogen fuel mobility or the dispenser through message exchange between the hydrogen fuel mobility and the dispenser before transmitting a request message, provided that fuel supply parameters based on a fuel supply protocol have been negotiated between the hydrogen fuel mobility and the dispenser.

[0495] The processor 3100 can check the safety status on the hydrogen fuel mobility or dispenser side through message exchange between the hydrogen fuel mobility and the dispenser before the nozzle is unplugged if the response message indicates that the hydrogen fuel supply has finished or stopped.

[0496] A communication device for a dispenser that supplies hydrogen fuel to a hydrogen fuel mobility vehicle according to one embodiment of the present invention includes a memory 3200 for storing at least one instruction and a processor 3100 for executing at least one instruction, wherein the processor 3100 can receive a request message from the dispenser containing information related to an action, including starting or stopping hydrogen fuel supply, after a fuel supply protocol negotiation has been completed between the hydrogen fuel mobility vehicle and the dispenser, and can transmit a response message to the hydrogen fuel mobility vehicle containing information regarding whether the action contained in the request message has been processed or is ready to be processed.

[0497] On the other hand, while most of the embodiments described above focused on a method in which the dispenser first transmits the communication protocol and parameters of the hydrogen fuel mobility, the present invention is not limited to specific embodiments, and it is of course possible to configure the dispenser to first transmit the dispenser's communication protocol and parameters to the hydrogen fuel mobility. In this case, it is obvious that the present invention has substantially the same characteristics, except that the sender becomes the receiver and the receiver becomes the sender in the relevant embodiment.

[0498] The operation of the method according to the embodiment of the present invention can be embodied in a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes all types of recording devices on which information readable by a computer system is stored. Furthermore, computer-readable recording media can be distributed across a network of connected computer systems, and computer-readable programs or code can be stored and executed in a distributed manner.

[0499] Furthermore, computer-readable recording media can include hardware devices specially configured to store and execute program instructions, such as ROM, RAM, and flash memory. Program instructions can include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like.

[0500] Some aspects of the present invention have been described in the context of apparatus, but they can also be described by corresponding methods, where blocks or apparatus correspond to method steps or features of method steps. Similarly, aspects described in the context of methods can also be described by corresponding blocks or items or features of corresponding apparatus. Some or all of the method steps may be carried out by (or utilizing) hardware devices such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, at least one or more of the most important method steps may be carried out by such devices.

[0501] In embodiments, a programmable logic device (e.g., a field-programmable gate array) may be used to perform some or all of the functions of the methods described herein. In embodiments, a field-programmable gate array may operate in conjunction with a microprocessor to perform one of the methods described herein. Generally, it is preferable that the methods be performed by some hardware device.

[0502] While preferred embodiments of the present invention have been described above, those skilled in the art will understand that the present invention can be modified and altered in various ways without departing from the spirit and scope of the invention as described in the following claims. [Explanation of Symbols]

[0503] 100 Hydrogen electric vehicles, hydrogen fuel mobility 110 Electronic control unit 120 Vehicle Systems 130 Vehicle Tank 150 receptacles 160 First Sensor 200 dispensers 210 Electronic control unit 220 Filling Station System 230 hydrogen tanks 240 Station Box 250 nozzles 260 Second Sensor 3000 Computing Systems 3100 Processor 3200 memory 3300 Communication Interface 3400 storage devices 3500 Input Interface Device 3600 Output Interface Device 3700 bus< / false> < / true> < / ok> < / true> < / ok> < / pending> < / pending>

Claims

1. A communication method for hydrogen fuel supply (fueling) carried out by hydrogen fuel mobility, A step of transmitting a request message to the dispenser, which supplies hydrogen to the hydrogen fuel mobility, based on a fuel supply protocol determined through negotiations between the dispenser and the hydrogen fuel mobility, including information related to an action including the commencement or cessation of hydrogen fuel supply, and The step of receiving a response message from the dispenser that includes information on whether it has processed or is ready to process the action included in the request message, A communication method for supplying hydrogen fuel, characterized by including the following:

2. The aforementioned request message includes information related to the action of initiating hydrogen fuel supply. Communication method for hydrogen fuel supply according to claim 1, wherein the response message includes information regarding whether the dispenser is ready to begin supplying hydrogen fuel.

3. If the response message indicates that the dispenser is not ready to begin supplying hydrogen fuel, the device then transmits a second request message containing information related to the hydrogen fuel supply initiation action. A communication method for supplying hydrogen fuel according to claim 2, further comprising:

4. The aforementioned request message includes information regarding the action to discontinue hydrogen fuel supply. The communication method for hydrogen fuel supply according to claim 1, wherein the response message includes information regarding whether the dispenser has stopped supplying hydrogen fuel.

5. If the response message indicates that the dispenser has not completely stopped supplying hydrogen fuel, the step is to transmit an additional second request message containing information related to the action of stopping the supply of hydrogen fuel. A communication method for supplying hydrogen fuel according to claim 4, further comprising:

6. The aforementioned request message includes a monitoring request regarding at least one condition related to the hydrogen fuel supply procedure, The communication method for supplying hydrogen fuel according to claim 1, wherein the response message includes information on at least one of the states.

7. In a stage where fuel supply parameters based on the fuel supply protocol have been negotiated between the hydrogen fuel mobility and the dispenser, and before transmitting the request message, the safety status of the hydrogen fuel mobility or the dispenser is checked through message exchange between the hydrogen fuel mobility and the dispenser. A communication method for supplying hydrogen fuel according to claim 1, further comprising:

8. If the response message indicates that the hydrogen fuel supply has finished or stopped, the safety status of the hydrogen fuel mobility or the dispenser is checked through message exchange between the hydrogen fuel mobility and the dispenser before the nozzle is unplugged. A communication method for supplying hydrogen fuel according to claim 1, further comprising:

9. A communication device for supplying hydrogen fuel to a hydrogen fuel mobility vehicle, Memory for storing at least one instruction, Includes a processor that executes at least one of the aforementioned instructions, The processor, by at least one instruction, Based on a fuel supply protocol determined through negotiations between the dispenser that supplies hydrogen to the hydrogen fuel mobility and the hydrogen fuel mobility, a request message containing information related to actions including the commencement or cessation of hydrogen fuel supply is transmitted to the dispenser. A communication device characterized by receiving a response message from the dispenser that includes information on whether the action included in the request message has been processed or is ready to be processed.

10. The aforementioned request message includes information related to the action of initiating hydrogen fuel supply. The response message includes information regarding whether the dispenser is ready to begin supplying hydrogen fuel. If the response message indicates that the dispenser is not ready to begin supplying hydrogen fuel, the processor transmits an additional second request message containing information relating to the start action of supplying hydrogen fuel, according to claim 9.

11. The aforementioned request message includes information regarding the action to discontinue hydrogen fuel supply. The response message includes information regarding whether the dispenser has stopped supplying hydrogen fuel. If the response message indicates that the dispenser has not completely stopped supplying hydrogen fuel, the processor transmits an additional second request message containing information relating to the action of stopping the supply of hydrogen fuel, according to claim 9.

12. The aforementioned request message includes a monitoring request regarding at least one condition related to the hydrogen fuel supply procedure, The communication device according to claim 9, wherein the response message includes information on at least one of the states.

13. The aforementioned processor, The communication device according to claim 9, wherein, with fuel supply parameters based on the fuel supply protocol negotiated between the hydrogen fuel mobility and the dispenser, the safety status of the hydrogen fuel mobility or the dispenser is checked by message exchange between the hydrogen fuel mobility and the dispenser before transmitting the request message.

14. The aforementioned processor, The communication device according to claim 9, wherein, if the response message indicates that the hydrogen fuel supply has been finished or stopped, the device checks out the safety status of the hydrogen fuel mobility or the dispenser by exchanging messages between the hydrogen fuel mobility and the dispenser before the nozzle is unplugged.

15. A communication method for hydrogen fuel supply (fueling) performed by a dispenser that supplies hydrogen fuel to hydrogen fuel mobility, The steps include: a stage in which, after negotiations on a fuel supply protocol have been completed between the hydrogen fuel mobility and the dispenser, a request message is received from the dispenser containing information related to an action, including the commencement or cessation of hydrogen fuel supply; and A step of transmitting a response message to the hydrogen fuel mobility that includes information on whether the action included in the request message has been processed or is ready to be processed, A communication method for supplying hydrogen fuel, characterized by including the following:

16. The aforementioned request message includes information related to the action of initiating hydrogen fuel supply. Communication method for hydrogen fuel supply according to claim 15, wherein the response message includes information regarding whether the dispenser is ready to begin supplying hydrogen fuel.

17. Communication method for hydrogen fuel supply according to claim 15, wherein the response message includes information regarding whether the dispenser is in the process of supplying hydrogen fuel or has stopped supplying it.

18. If the response message indicates that the dispenser has stopped supplying hydrogen fuel, Communication method for hydrogen fuel supply according to claim 17, wherein the response message includes information on whether the dispenser has stopped supplying hydrogen fuel based on a cessation action included in the request message of the hydrogen fuel mobility, or whether the hydrogen fuel supply target of the hydrogen fuel mobility has been achieved and the hydrogen fuel supply has been terminated.

19. The aforementioned request message includes a monitoring request regarding at least one condition related to the hydrogen fuel supply procedure, The communication method for supplying hydrogen fuel according to claim 15, wherein the response message includes information on at least one of the states.

20. With fuel supply parameters based on the fuel supply protocol negotiated between the hydrogen fuel mobility and the dispenser, the safety status of the hydrogen fuel mobility or the dispenser is checked in by message exchange between the hydrogen fuel mobility and the dispenser before receiving the request message, and If the response message indicates that the hydrogen fuel supply has finished or stopped, the safety status of the hydrogen fuel mobility or the dispenser is checked through message exchange between the hydrogen fuel mobility and the dispenser before the nozzle is unplugged. A communication method for supplying hydrogen fuel according to claim 15, further comprising:

Images