Hydrogen fueling communication method and apparatus for error and emergency handling

Abstract

A method according to one embodiment of the present invention comprises the steps of: detecting an error occurring during communication between a moving body and a dispenser supplying hydrogen fuel to the moving body or during supply of hydrogen fuel to the moving body by the dispenser; determining whether the communication or the supply of hydrogen fuel is stopped for the detected error; and performing a subsequent process defined based on the detected error.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to a communication technology for hydrogen fuel refilling of a hydrogen fuel mobile body, and more particularly, to a hydrogen fuel refilling process capable of enhancing the safety, compatibility, efficiency, and reliability of hydrogen fuel refilling, an error handling and emergency handling method for the hydrogen fuel refilling process, and an apparatus using the error handling and emergency handling method. BACKGROUND

[0002] The description in this section merely provides background information of embodiments of the present disclosure and does not intend to designate the prior art of the present disclosure.

[0003] A hydrogen vehicle or a hydrogen electric vehicle refers to a vehicle driven by electric power generated by the reaction of high-pressure hydrogen gas stored in the vehicle and oxygen in the air, and generates little pollution. Most hydrogen electric vehicles are driven by electric power generated by a fuel cell system that uses hydrogen gas as an energy source. The hydrogen electric vehicle not only emits pure water (H2O) vapor in the process of generating electricity, but also removes ultra-fine dust in the air while traveling, and thus attracts attention as an eco-friendly mobile body of the future. Since fuel, i.e., hydrogen, is abundant on the earth, and the energy production process is eco-friendly, the hydrogen electric vehicle has received extensive attention as a technology having potential to be applied to the entire industry.

[0004] A hydrogen fuel mobile body refers to a mobile body that uses hydrogen as an energy source or generates electric power using hydrogen as a fuel to drive an electric motor by the electric power. In addition to the above-described hydrogen electric vehicle, the hydrogen fuel mobile body can include an air mobile body as well as industrial trucks, trains, ships, and airplanes that generate electric power using hydrogen as a fuel and are driven by the electric power.

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

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

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

[0008] The hydrogen refueling / supplying process, control scheme, and its protocol in a conventional hydrogen electric vehicle have been established before wired / wireless communication or computing technology for control became mature, and thus do not take advantage of the latest information and communication technology (ICT) to their full extent. Therefore, the conventional hydrogen refueling / supplying subsystem in a hydrogen electric vehicle is inefficient, slow, and unsuitable for large-scale hydrogen refueling.

[0009] In particular, regarding hydrogen refueling communication, most hydrogen refueling control devices use one-way infrared communication devices for wireless communication, and thus still have the limitations and weaknesses of one-way communication. SUMMARY

[0010] TECHNICAL PROBLEM

[0011] To solve the above problems, one object of exemplary embodiments is to provide a hydrogen refueling process and a communication protocol for the process, a method of negotiating a communication protocol, a fueling protocol, and fueling parameters for the hydrogen refueling process, a monitoring and control method, a safety check-in method, a safety check-out method, and devices for implementing the methods, which overcomes the limitations and weaknesses of conventional one-way communication in a hydrogen refueling process of a hydrogen fuel mobile and enhances the safety, compatibility, efficiency, and reliability of hydrogen refueling.

[0012] Another object of exemplary embodiments is to provide an error handling and emergency handling method for a hydrogen refueling process and a device using the method, which handles errors and / or emergency situations occurring in a communication protocol negotiation, a fueling protocol negotiation, a fueling parameter negotiation, a monitoring and control, a safety check-in, and a safety check-out process for a hydrogen refueling process.

[0013] Another object of exemplary embodiments is to provide a hydrogen refueling two-way communication process, a communication protocol negotiation process considering two-way / one-way communication, and devices for implementing the processes, which allows a hydrogen fuel mobile and a dispenser control to determine whether to use a conventional communication medium or an advanced communication medium to effectively achieve a hydrogen refueling goal.

[0014] TECHNICAL SOLUTION

[0015] According to an aspect of the exemplary embodiments, a communication method for hydrogen fuel refueling, performed by a communication device of a hydrogen fuel mobile body, can include detecting an error occurring in a communication process for preparing hydrogen fuel refueling between the mobile body and a dispenser that supplies hydrogen to the mobile body or in a hydrogen fuel refueling process from the dispenser to the mobile body, determining whether to stop the communication process or the hydrogen fuel refueling process with respect to the detected error, and performing a subsequent process defined based on the detected error.

[0016] In the communication method for hydrogen fuel refueling, performed by a communication device of a mobile body according to the exemplary embodiments of the present disclosure, the determining whether to stop the communication process or the hydrogen fuel refueling process with respect to the detected error can include classifying the detected error as a safety critical error or a non-safety critical error.

[0017] In the communication method for hydrogen fuel refueling, performed by a communication device of a mobile body according to the exemplary embodiments of the present disclosure, the determining whether to stop the communication process or the hydrogen fuel refueling process with respect to the detected error can further include, based on the detected error being a non-safety critical error, classifying the detected error as any one of a communication error, a system error, and a qualitative error.

[0018] In the communication method for hydrogen fuel refueling, performed by a communication device of a mobile body according to the exemplary embodiments of the present disclosure, the performing a subsequent process defined based on the detected error can include, based on the detected error being a safety critical error, performing an emergency handling process.

[0019] In the communication method for hydrogen fuel refueling, performed by a communication device of a mobile body according to the exemplary embodiments of the present disclosure, the determining whether to stop the communication process or the hydrogen fuel refueling process with respect to the detected error can further include, based on the detected error being a non-safety critical error, determining whether to replace a first fuel refueling protocol of the communication process or the hydrogen fuel refueling process with a second fuel refueling protocol using a fallback.

[0020] In the communication method for hydrogen fuel refueling, performed by a communication device of a mobile body according to the exemplary embodiments of the present disclosure, the performing a subsequent process defined based on the detected error can include transmitting a message including whether to stop the communication process or the hydrogen fuel refueling process to the dispenser.

[0021] According to an aspect of an exemplary embodiment, a communication device arranged in a hydrogen fuel mobile body for hydrogen fuel refilling includes a memory storing at least one instruction and a processor executing the at least one instruction. Through the at least one instruction, the processor can detect an error occurring in a communication process between the mobile body and a dispenser supplying hydrogen to the mobile body for preparation of hydrogen fuel refilling or in a hydrogen fuel refilling process from the dispenser to the mobile body, determine whether to stop the communication process or the hydrogen fuel refilling process with respect to the detected error, and perform a subsequent process defined based on the detected error.

[0022] The processor can classify the detected error as a safety critical error or a non-safety critical error when determining whether to stop the communication process or the hydrogen fuel refilling process with respect to the detected error.

[0023] The processor can classify the detected error as any one of a communication error, a system error, and a qualitative error based on the detected error being a non-safety critical error when determining whether to stop the communication process or the hydrogen fuel refilling process with respect to the detected error.

[0024] The processor can perform an emergency handling process based on the detected error being a safety critical error when performing the subsequent process defined based on the detected error.

[0025] The processor can determine whether to replace a first fuel refilling protocol of the communication process or the hydrogen fuel refilling process with a second fuel refilling protocol using a fallback based on the detected error being a non-safety critical error when determining whether to stop the communication process or the hydrogen fuel refilling process with respect to the detected error.

[0026] The processor can transmit a message including whether to stop the communication process or the hydrogen fuel refilling process to the dispenser when performing the subsequent process defined based on the detected error.

[0027] According to an aspect of an exemplary embodiment, a communication device of a dispenser supplying hydrogen fuel to a hydrogen fuel mobile body includes a memory storing at least one instruction and a processor executing the at least one instruction. Through the at least one instruction, the processor can detect an error occurring in a communication process between the dispenser and the mobile body for preparation of hydrogen fuel refilling or in a hydrogen fuel refilling process from the dispenser to the mobile body, determine whether to stop the communication process or the hydrogen fuel refilling process with respect to the detected error, and perform a subsequent process defined based on the detected error.

[0028] According to an aspect of the exemplary embodiments, a communication method for hydrogen fuel refueling, performed by a communication device of a dispenser that supplies hydrogen to a hydrogen fuel mobile body, can include detecting an error that occurs in a communication process between the dispenser and the mobile body for preparing hydrogen fuel refueling, or in a hydrogen fuel refueling process from the dispenser to the mobile body, determining whether to stop the communication process or the hydrogen fuel refueling process with respect to the detected error, and performing a subsequent process defined based on the detected error.

[0029] In the communication method for hydrogen fuel refueling, performed by the communication device of the dispenser according to the exemplary embodiments of the present disclosure, the determining whether to stop the communication process or the hydrogen fuel refueling process with respect to the detected error can include classifying the detected error as a safety critical error or a non-safety critical error.

[0030] In the communication method for hydrogen fuel refueling, performed by the communication device of the dispenser according to the exemplary embodiments of the present disclosure, the determining whether to stop the communication process or the hydrogen fuel refueling process with respect to the detected error can further include, based on the detected error being a non-safety critical error, classifying the detected error as any one of a communication error, a system error, and a qualitative error.

[0031] In the communication method for hydrogen fuel refueling, performed by the communication device of the dispenser according to the exemplary embodiments of the present disclosure, the performing the subsequent process defined based on the detected error can include, based on the detected error being a safety critical error, performing an emergency handling process.

[0032] In the communication method for hydrogen fuel refueling, performed by the communication device of the dispenser according to the exemplary embodiments of the present disclosure, the determining whether to stop the communication process or the hydrogen fuel refueling process with respect to the detected error can further include, based on the detected error being a non-safety critical error, determining whether to replace a first fuel refueling protocol of the communication process or the hydrogen fuel refueling process with a second fuel refueling protocol of a fallback.

[0033] In the communication method for hydrogen fuel refueling, performed by the communication device of the dispenser according to the exemplary embodiments of the present disclosure, the performing the subsequent process defined based on the detected error can include, based on replacing the first fuel refueling protocol of the communication process or the hydrogen fuel refueling process with the second fuel refueling protocol, performing the hydrogen fuel refueling process based on the second fuel refueling protocol.

[0034] In the communication method for hydrogen fuel refueling, performed by the communication device of the dispenser according to the exemplary embodiments of the present disclosure, the performing the subsequent process defined based on the detected error can include transmitting a message including whether to stop the communication process or the hydrogen fuel refueling process to the mobile body.

[0035] In the communication method for hydrogen fuel filling performed by the communication device of the dispenser according to the exemplary embodiment of the present disclosure, if the message including whether to stop the communication process or the hydrogen fuel filling process includes a stop, the message can further include a code corresponding to the reason for the stop.

[0036] Advantages

[0037] According to the communication method for hydrogen fuel filling, the device for implementing the method, i.e., the hydrogen fuel filling controller or the communication controller according to the exemplary embodiment of the present disclosure, can overcome the limitations and weaknesses of the conventional one-way communication for a hydrogen fuel mobile body in the communication protocol of the hydrogen fuel filling process and the fuel filling protocol for the process, and can enhance the safety, compatibility, efficiency, and reliability of hydrogen fuel filling, the hydrogen fuel mobile body including a fuel cell electric vehicle (FCEV) or a hydrogen fuel engine.

[0038] The exemplary embodiment of the present disclosure can provide a method of negotiating a communication protocol for hydrogen fuel filling and exchanging communication parameters for hydrogen fuel filling and a communication protocol fallback rule, in which a mobile body and a dispenser can select a hydrogen fuel filling protocol and a communication protocol required to perform the hydrogen fuel filling protocol according to a use case while considering a priority according to a preference of the mobile body or the dispenser, maximizing interoperability between the mobile body and the dispenser, and considering backward compatibility.

[0039] The exemplary embodiment of the present disclosure can provide rules and procedures required for communication protocol negotiation, fuel filling protocol negotiation, and fuel filling parameter exchange to enable a mobile body and a dispenser to efficiently and cooperatively determine a regular communication medium or an advanced communication medium to effectively achieve a hydrogen fuel filling goal.

[0040] The exemplary embodiment of the present disclosure can provide rules and procedures for monitoring and control, a safety check-in, and a safety check-out process to enable a mobile body and a dispenser to cooperatively and efficiently achieve a hydrogen fuel filling goal.

[0041] The exemplary embodiment of the present disclosure can provide rules and procedures required for a use case in which a monitoring and control, a safety check-in, and a safety check-out process and a communication protocol negotiation, a fuel filling protocol negotiation, and a fuel filling parameter exchange process are linked to each other, thereby enabling a mobile body and a dispenser to cooperatively and efficiently achieve a hydrogen fuel filling goal.

[0042] Exemplary embodiments of the present disclosure can provide rules and procedures required for use cases in which error handling and emergency handling procedures for a hydrogen fuel filling process are linked to each other, the error handling and emergency handling procedures handle errors and / or emergency situations that occur in a communication protocol negotiation, a fuel filling protocol negotiation, a fuel filling parameter negotiation, a monitoring and control, a safety check-in and a safety check-out procedure, thereby enabling a mobile body and a dispenser to cooperatively and effectively achieve a hydrogen fuel filling goal. BRIEF DESCRIPTION OF DRAWINGS

[0043] Figure 1 is a diagram of a hydrogen fuel filling system for a fuel cell electric vehicle (FCEV) suitable for applying a bidirectional communication procedure to a hydrogen fuel filling according to exemplary embodiments of the present disclosure;

[0044] Figure 2 is a partial enlarged view of a physical engagement structure between an FCEV and a dispenser in the hydrogen fuel filling system of Figure 1

[0045] Figure 3 is a graph showing a state change of hydrogen fuel occurring in a hydrogen fuel filling procedure in the hydrogen fuel filling system of Figure 1

[0046] Figure 4 shows a framework of functional blocks for performing a series of hydrogen fuel filling procedures that can employ a bidirectional communication procedure for a hydrogen fuel filling according to exemplary embodiments of the present disclosure;

[0047] Figure 5 shows an example of a communication stack related to use cases employed in a bidirectional communication procedure for a hydrogen fuel filling based on an open systems interconnection reference model (OSI) 7 layer according to exemplary embodiments of the present disclosure;

[0048] Figure 6 is a sequence diagram showing a pairing procedure of a discovery and pairing procedure that can be employed in a bidirectional communication procedure for a hydrogen fuel filling according to exemplary embodiments of the present disclosure;

[0049] Figure 7 shows an example of backward compatibility that can be employed in a bidirectional communication procedure for a hydrogen fuel filling according to exemplary embodiments of the present disclosure;

[0050] Figure 8 is a table summarizing examples of backward compatibility of a bidirectional communication procedure for a hydrogen fuel filling according to exemplary embodiments of the present disclosure;

[0051] Figure 9 ​​Usage classification of communication data (UCDC) in a bidirectional communication procedure for hydrogen fuel refueling according to an exemplary embodiment of the present disclosure is shown, and backward compatibility of the usage classification of communication data is shown;

[0052] Figure 10 is a sequence diagram showing an authorization procedure in a communication security procedure that can be employed in a bidirectional communication procedure for hydrogen fuel refueling according to an exemplary embodiment of the present disclosure;

[0053] Figure 11 is a sequence diagram showing a communication protocol negotiation procedure that can be employed in a bidirectional communication procedure for hydrogen fuel refueling according to an exemplary embodiment of the present disclosure;

[0054] Figure 12 is a sequence diagram showing a fueling protocol negotiation procedure in a bidirectional communication procedure for hydrogen fuel refueling according to an exemplary embodiment of the present disclosure;

[0055] Figure 13 is a sequence diagram showing a fueling parameter exchange / negotiation procedure that can be employed in a bidirectional communication procedure for hydrogen fuel refueling according to an exemplary embodiment of the present disclosure;

[0056] Figure 14 is a conceptual diagram showing a table summarizing parameters transmitted from a mobile body side to a dispenser side in a fueling parameter exchange / negotiation procedure according to an exemplary embodiment of the present disclosure;

[0057] Figure 15 is a conceptual diagram showing a table summarizing parameters transmitted from a dispenser side to a mobile body side in a fueling parameter exchange / negotiation procedure according to an exemplary embodiment of the present disclosure; and

[0058] Figure 16 is a schematic block diagram showing a physical configuration of a general-purpose computing system that can operate as a communication device, a communication controller, and / or an electronic controller for hydrogen fuel refueling, and that can be installed on a hydrogen fuel mobile body, a dispenser, and / or a fueling station, according to an exemplary embodiment of the present disclosure.

[0059] Figure 17 is an operation flowchart of a communication method for hydrogen fuel refueling according to an exemplary embodiment of the present disclosure.

[0060] Figure 18 is an operation flowchart of a communication method for hydrogen fuel refueling according to another exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0061] Other objects and features of the present disclosure will become more apparent from the following description of exemplary embodiments when taken together with the accompanying drawings.

[0062] In order to more clearly understand the features and advantages of the present disclosure, exemplary embodiments thereof will be described in detail with reference to the accompanying drawings. It should be understood, however, that the technical spirit of the present disclosure is not limited to specific embodiments disclosed herein but includes all modifications, equivalents, and alternatives falling within the scope of the present disclosure.

[0063] In the present specification, terms including numerals such as "first" and "second" designated to explain various components are used to distinguish the components from other components, but are not intended to limit the specific components. For example, a second component can be referred to as a first component without departing from the scope of the present disclosure, and similarly, a first component can also be referred to as a second component. As used herein, the term "and / or" can include the presence of one or more associated listed items and any and all combinations of the listed items.

[0064] In the description of the exemplary embodiments of the present disclosure, "at least one of A and B" can mean "at least one of A or B" or "at least one of a combination of one or more of A and B". In addition, in the description of the exemplary embodiments of the present disclosure, "one or more of A and B" can mean "one or more of A or B" or "one or more of a combination of one or more of A and B".

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

[0066] These terms are used herein only to describe specific exemplary embodiments and are not intended to limit the present disclosure. The singular form also includes the plural unless the context clearly dictates otherwise. Also, the expressions "include", "comprise", "constructed", "configured" are used to indicate the presence of a feature, number, processing step, operation, element, or combination of components, but are not intended to exclude the presence or addition of another feature, number, processing step, operation, element, or component.

[0067] Unless otherwise defined, all terms (including technical or scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. Terms such as those commonly used in dictionaries are to be interpreted as having a meaning that is consistent with their meaning in the context of the relevant literature and are not to be interpreted in an idealized or overly formal sense unless expressly so defined in the present application.

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

[0069] A hydrogen electric vehicle can generally include a hydrogen fuel cell electric vehicle (FCEV) using a fuel cell and a vehicle having an internal combustion engine (ICE) using hydrogen as a fuel. The hydrogen electric vehicle can also be simply referred to as an FCEV.

[0070] Although embodiments related to a hydrogen fuel cell vehicle are described in detail below, an ICE-based hydrogen electric vehicle using hydrogen as a fuel can be employed in another embodiment of the present disclosure. In the following description, a hydrogen fueling protocol and / or a hydrogen fueling communication protocol are described with a focus on a hydrogen fuel cell vehicle. However, the hydrogen fueling protocol and / or the hydrogen fueling communication protocol can also be adapted to an ICE-based hydrogen electric vehicle according to another embodiment of the present disclosure.

[0071] A hydrogen fluid fuel can include a gaseous hydrogen fuel or a liquid hydrogen fuel.

[0072] “Compressed hydrogen storage system (CHSS)”: a device including at least one tank mounted on a vehicle to compress and store hydrogen.

[0073] “Pressure relief device (PRD)”: a device arranged in the CHSS and capable of isolating stored hydrogen from other parts of the fueling system and the environment and venting the hydrogen to the outside.

[0074] “Hydrogen fueling”: a process of supplying high-pressure hydrogen gas from a dispenser of a hydrogen fueling station to a vehicle to accumulate hydrogen in a tank of the vehicle. In terms of supplying hydrogen fuel to a hydrogen electric vehicle, hydrogen fueling can also be referred to as “fueling”. That is, the term “fueling”, “hydrogen fueling”, or “refueling” used herein can mean supplying hydrogen fuel. For example, a fueling protocol can be referred to as a refueling protocol, a fueling session can be referred to as a refueling session, and a fueling method can be referred to as a hydrogen fueling method or a refueling method.

[0075] “Pressure rise rate (PRR)”: an increase rate of the CHSS pressure and measured in mega Pascal per minute (MPa / min).

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

[0077] “Pre-cooling”: The process of cooling hydrogen in a hydrogen fueling station before refueling.

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

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

[0080] “Fueling Session”: A communication session that occurs within the scope of the Hydrogen Fueling Use Case.

[0081] "Interoperability" refers to a state in which components of a system interact with corresponding components of the system to perform operations intended by the system. Additionally, information interoperability may refer to the ability of two or more networks, systems, devices, applications, or components to effectively share and easily use information without causing inconvenience to users.

[0082] The correlation or association process may include a process of establishing a relationship between two peer communicating entities.

[0083] "Command and control communications": communications used to exchange information between a hydrogen dispenser and a hydrogen fuel mobile device to initiate, control, and terminate the hydrogen fueling process.

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

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

[0086] In the following description, hydrogen fuel may include one or more of gaseous hydrogen and liquid hydrogen. Hydrogen fuel basically means compressed hydrogen, but is not limited thereto.

[0087] Further, although the bidirectional communication process for hydrogen fuel refilling is described in terms of a hydrogen electric vehicle (FCEV) for convenience of explanation, the present disclosure is not limited thereto, and the hydrogen fuel refilling bidirectional communication process can also be applied to a hybrid electric vehicle (EV) or an ICE-based vehicle that uses hydrogen as fuel.

[0088] In the following description, some or all of the processes of the communication method, the communication protocol negotiation method, the hydrogen fuel refilling protocol negotiation method, and the hydrogen fuel refilling parameter negotiation method performed by the hydrogen fuel mobile body can be performed by an electronic control unit (ECU), a communication device, or a communication controller of the hydrogen fuel mobile body.

[0089] In the following description, some or all of the processes of the communication method, the communication protocol negotiation method, the hydrogen fuel refilling protocol negotiation method, the hydrogen fuel refilling parameter negotiation method, the hydrogen fuel refilling method, and the hydrogen fuel refilling control method performed by the dispenser can be performed by a controller, an electronic control unit, a communication device, or a communication controller of the dispenser. Alternatively, some of the processes of the above-described methods can be performed by a controller, an electronic control unit, a communication device, or a communication controller of a fueling station associated with the dispenser.

[0090] Meanwhile, one or more conventional components can be included in the configuration of the present disclosure if necessary, and such components will be described herein to the extent that does not obscure the technical idea and concept of the present disclosure. However, if the description of the conventional components can obscure the technical idea and concept of the present disclosure, detailed descriptions of the components can be omitted for simplicity. However, the present disclosure is not intended to require protection of the conventional components, and the conventional components can be included as elements of the apparatus or method of the present disclosure without departing from the concept or spirit of the present disclosure.

[0091] For example, the communication between the dispenser and the vehicle can be implemented using conventional technologies, such as IrDA technology for unidirectional communication, short-range wireless communication technology (such as Bluetooth, WLAN, and UWB) for bidirectional communication, and wired communication technology for unidirectional or bidirectional communication. At least some of the conventional technologies can be used as basic technologies for implementing the present disclosure.

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

[0093] Figure 1 is a diagram of a hydrogen fuel refilling system for a hydrogen electric vehicle (FCEV) adapted to apply a bidirectional communication process to hydrogen fuel refilling according to an example embodiment of the present disclosure. Figure 2 is Figure 1 is a partial enlarged view of a physical engagement structure between an FCEV and a dispenser in the hydrogen fuel refilling system of Figure 3 is a diagram showing a process of determining a communication protocol in a hydrogen fuel refilling system for a hydrogen electric vehicle (FCEV) according to an example embodiment of the present disclosure.Figure 1 a graph of a state change of hydrogen fuel occurring in a hydrogen fuel filling process in a hydrogen fuel filling system.

[0094] Referring to Figure 1 , a hydrogen fuel filling system can generally be configured to include a hydrogen fuel filling station and a hydrogen fueled mobility 100.

[0095] In addition to mechanical devices, electrical devices, electronic devices, and communication devices that are basically required for a vehicle, the hydrogen fueled mobility 100 can be equipped with an electronic controller 110 for hydrogen fuel filling, a vehicle system 120, a vehicle tank 130, and a receptacle 150 for hydrogen fuel filling.

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

[0097] The vehicle system 120 can be connected to the first electronic controller 110 and can be configured to control hydrogen fuel filling or hydrogen discharge of the vehicle tank 130 according to signals or commands from the first electronic controller 110, and monitor the state of the vehicle tank 130. The vehicle system 120 can include or be configured in combination with components that control the operation of a fuel cell system according to the implementation, or perform such a control operation. The vehicle system 120 can perform a vehicle safety function and can be referred to as a vehicle safety system.

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

[0099] Further, the vehicle tank 130 can correspond to a hydrogen storage system installed in a vehicle. In this case, the hydrogen storage system can include a high-pressure hydrogen storage tank, a pressure control device, a high-pressure pipe, and an outer frame. The high-pressure hydrogen storage tank can have a capacity of tens to hundreds of liters, and can have a shape in which small storage tanks are connected in parallel. A boss unit through which hydrogen fuel passes can be coupled to the high-pressure hydrogen storage tank, and thus filling and discharge of hydrogen fuel can be controlled through the boss unit. The boss unit can include a valve, a pressure reducing device, and various sensors for measurement. Such a hydrogen storage system is referred to as a compressed hydrogen storage system (CHSS). For ease of explanation, the term "vehicle tank" used herein can refer to a CHSS.

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

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

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

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

[0104] Each of the first electronic controller 110 and the second electronic controller 210 can be composed of a plurality of electronic control units, and can be configured so that each communication protocol can be executed by a different electronic control unit. Such a configuration can be useful when using fallback to achieve backward compatibility, and when bidirectional communication cannot be used but unidirectional communication can be used. Furthermore, in the case of using a combination of different communication methods, for example, when NFC is used for pairing and WiFi is used for actual fueling, the configuration can be useful.

[0105] The fueling station system 220 can monitor or control the pressure, velocity, and temperature of hydrogen discharged from the hydrogen tank 230 according to signals and / or data from the second electronic controller. To this end, the fueling station system 220 can control the operation of the station box 240 connected to the discharge port or discharge valve of the hydrogen tank 230. The fueling station system 220 can also be referred to as a fueling station safety system.

[0106] In an exemplary embodiment of the present disclosure, the communication entity related to the dispenser 200 for communication with the vehicle / mobile body 100 can be the electronic controller 210 or can be a separate communication device installed on the dispenser 200. Alternatively, the electronic controller or the separate communication device in the fueling station system 220 can communicate with the vehicle / mobile body 100 instead of the dispenser 200.

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

[0108] The hydrogen tank 230 stores hydrogen or compressed hydrogen. The hydrogen tank 230 can discharge the stored hydrogen at a predetermined pressure or velocity under the control of the fueling station safety system 220. The hydrogen tank can also be referred to as a hydrogen storage tank.

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

[0110] The nozzle 250 can be connected to the hydrogen fueling system of the dispenser 200 through a predetermined length of conduit or flexible tube. The nozzle 250 can be provided with a shape and structure that tightly and firmly engages with the socket of the vehicle.

[0111] As Figure 2As shown, the nozzle 250 can be engaged with the receptacle 150. The first sensor 160 installed in the vehicle and the second sensor 260 attached to the nozzle 250 can transmit a signal or information about the coupling state of the nozzle 250 and the receptacle 150 to the first electronic controller or the vehicle safety system and to the second electronic controller or the fueling station safety system.

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

[0113] The dispenser 200 can be responsible for the interface between the hydrogen fueling station and the mobile body 100. The dispenser 200 can be configured to control the target pressure and the injection speed for hydrogen fueling based on information indirectly acquired from the vehicle tank 130 and fueling information of the hydrogen fueling station.

[0114] Generally, there are two methods to transmit information from the mobile body 100 to the dispenser 200: a communication method and a non-communication method. In the case of the communication method, the temperature and pressure values of the vehicle tank 130 of the mobile body 100 are transmitted to the dispenser 200 in a one-way manner, and the dispenser 200 does not actively use this information, but only uses it as a safety reference for, for example, emergency stop at temperature or pressure limits. In addition, the hydrogen fueling protocol for safe and fast fueling is managed by the dispenser 200, which has only a minimum safety management device that automatically releases hydrogen through a pressure release device (PRD) without any active safety management scheme for the vehicle tank 130.

[0115] Meanwhile, in order to cope with the phenomenon of temperature rise of hydrogen gas in the hydrogen fueling process depicted in Figure 3 In order to cope with the phenomenon of temperature rise of hydrogen gas in the hydrogen fueling process depicted in

[0116] The dispenser 200 or the second electronic controller can be equipped with fueling control logic, which can control the hydrogen fueling process based on state information such as the temperature and pressure of the hydrogen fuel supplied to the vehicle or charged in the vehicle tank 130 and fueling state information such as the state of charge (SOC) of the CHSS.

[0117] As described above, the hydrogen refueling process between the hydrogen fuel mobile body 100 and the hydrogen fueling station is controlled by the dispenser 200, and the dispenser 200 can include a protocol for supplying hydrogen fuel to the vehicle according to a prescribed procedure. The hydrogen refueling protocol can also be installed in the vehicle. The protocol installed in the vehicle or the dispenser 200 can include at least some of the communication protocols based on SAE standards, ISO standards, or similar standards.

[0118] For minimum safety requirements, simulations based on thermodynamic modeling can be performed for various cases, and part real-time corrections based on tables or based on MC equations can be performed with parameters derived from the simulations. The minimum safety requirements can include upper limits of temperature and pressure conditions of CHSS and guidelines for fueling rate (SOC).

[0119] In the case where the state values related to hydrogen refueling are not actively controlled in the dispenser 200, the table-based correction has a drawback that can show very low efficiency because the temperature of the pre-cooled hydrogen fuel provided by the fueling station or the temperature of the vehicle tank 130 measured in the mobile body 100 is not utilized, and thus it can be difficult to flexibly respond to changes in surrounding conditions. The MC equation-based correction allows real-time compensation of the temperature of the pre-cooled hydrogen fuel, but the calculation and application of the method are complicated, which can cause limitations in application and make it difficult to expand. Therefore, the conventional communication protocol developed under the main goal of safely completing fueling cannot actively respond to unexpected situations such as excessive pre-cooling or overheating of the vehicle tank 130, and can cause problems such as an increase in operating costs due to over-cooling and a delay in fueling due to overheating.

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

[0121] Meanwhile, the temperature control of the hydrogen refueling process can aim to ensure that the internal temperature of the vehicle tank 130 remains below 85°C at the time of completion of fueling by supplying pre-cooled hydrogen. During the hydrogen refueling process, the temperature of the hydrogen fuel can undergo a change according to Figure 3The temperature of the hydrogen fuel can decrease at a constant rate in phase 1 (P1), which is a pre-cooling phase of the hydrogen fuel filling station, and gradually increase due to the thermal mass of the hydrogen fuel filling station in phase 2 (P2), during which the hydrogen fuel is supplied from the hydrogen fuel filling station to a hydrogen mobile body such as a vehicle. In phase 3 (P3), during which the hydrogen fuel is transferred inside the vehicle to a vehicle tank, the temperature of the hydrogen fuel increases at a higher rate due to the thermal mass of the vehicle. In phase 4 (P4), during which the hydrogen fuel is compressed and stored in the vehicle tank, the temperature of the hydrogen fuel can rapidly increase due to the compression heat.

[0122] According to the present embodiment, the hydrogen fuel filling process can be effectively performed via a bidirectional communication process for hydrogen fuel filling by reflecting the active state variable control of real-time measurement data. In addition, a hydrogen fuel filling protocol for the process can be provided.

[0123] Figure 4 A framework of functional blocks for performing a series of hydrogen fuel filling processes (hereinafter, referred to as "hydrogen fuel filling framework") according to an exemplary embodiment of the present disclosure is illustrated, which can employ a bidirectional communication process for hydrogen fuel filling.

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

[0125] As Figure 4 illustrated, the functional blocks UC1 to UC11 can correspond to time series operations S401 to S411, respectively. In this case, Figure 4 It can also be understood as a flowchart including the time series operations S401 to S411.

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

[0127] The use cases are functional blocks that collectively provide the entire hydrogen fuel filling process of a hydrogen fuel filling system in a consistent manner for safe and reliable fuel filling communication. The vehicle and the dispenser can sequentially perform the use cases in a certain order to achieve hydrogen fuel filling.

[0128] After the nozzle of the dispenser is coupled to the socket of the vehicle, the vehicle and the dispenser can perform the fuel filling communication by performing the use cases in the order shown below. However, if necessary, the vehicle and the dispenser can omit some use cases according to predetermined requirements. Figure 4 The fuel filling communication can be performed by implementing the use cases in the order shown below. However, if necessary, the vehicle and the dispenser can omit some use cases according to predetermined requirements.

[0129] Each of the above use cases can be implemented according to a fuel filling protocol for a hydrogen fuel vehicle, by communication between a dispenser control system that supplies hydrogen as fuel to a hydrogen fuel vehicle and the hydrogen fuel vehicle.

[0130] Meanwhile, the hydrogen fuel vehicle (hereinafter, also simply referred to as "vehicle") and the dispenser that implements the use cases can perform data exchange to identify the vehicle in the use case UC-1. For this purpose, the vehicle can be equipped with a sensor, an electronic control unit (ECU), a transmitter, and a receiver. In the case of bidirectional communication, the receiver can be integrated with the transmitter.

[0131] The dispenser can be configured to receive certain data from the vehicle. The dispenser can store specific data in a programmable logic controller (PLC) of the fuel filling station to store data record data or use in the fuel filling protocol. The data record can refer to a process of collecting data for a certain period of time or data collected by the process to analyze a certain operation state of the hydrogen fuel filling system or record data-based events / operations of the system or network environment. In the case of bidirectional communication, the fuel filling station can be equipped with sensors specified by the fuel filling protocol, and the PLC or electronic control unit of the fuel filling station can acquire measurement values from the sensors and transmit the measurement values to the vehicle. The vehicle or the fuel filling station can use a conventional communication protocol standard for communication, such as infrared communication, WiFi, and Bluetooth.

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

[0133] The discovery and pairing procedure or pairing process can have a precondition that the nozzle of the dispenser is inserted and firmly coupled to the socket port of the vehicle fuel filling socket. The vehicle fuel filling socket can be simply referred to as the vehicle socket or socket.

[0134] Further, the vehicle and dispenser are typically aware of the communication protocol to follow by default. Thus, the communication performed after use case UC-1 can rely only on the communication protocol agreed in the current use case as a post-condition for the discovery and pairing procedure or pairing process. In case a communication protocol outside the agreed range is selected by the vehicle or dispenser, then the selected communication is not performed. That is, even if the pairing process is successfully completed, fueling will not be approved.

[0135] All methods for pairing a vehicle with a dispenser can be configured to not increase the risk of ignition or explosion beyond an acceptable level. For example, all wired pairing methods can be configured to mitigate or prevent the risk of sparking caused by electrostatic discharge.

[0136] In terms of validity of physical pairing, any method for pairing a vehicle with a dispenser can be integrated into the vehicle-dispenser interface, or installed such that proximity between the fueling inlet of the vehicle and the nozzle and hose assembly of the dispenser is maintained. Here, the interface can refer to something physically integrated into the interface between the nozzle and the inlet. Proximity can be defined by hardware associated with the pairing method. For example, a physical geometry for infrared communication can be specified, including an allowed distance between transmitter and receiver. Further, the physical geometry of hydrogen fueling hardware can be predefined, in which case proximity does not include pairing methods that would result in a risk of associating a dispenser with a vehicle that is not physically coupled to the dispenser, for example, long-range wireless communication technologies such as Bluetooth. Infrared communication can be referred to as infrared data association (IrDA) communication, and can include bi-directional infrared (bi-IrDA) communication.

[0137] Referring back to Figure 4 A communication method for hydrogen fueling that can be performed by a communication device of a hydrogen fuel mobile body according to an exemplary embodiment of the present disclosure can include an operation of negotiating a communication protocol with a dispenser that supplies hydrogen to the mobile body (S403), an operation of negotiating a fueling protocol for fueling hydrogen from the dispenser with the dispenser (S404), and an operation of negotiating a fueling parameter based on the fueling protocol with the dispenser (S405).

[0138] A communication method for hydrogen fueling that can be performed by a dispenser that supplies hydrogen to a hydrogen fuel mobile body according to an exemplary embodiment of the present disclosure can include an operation of negotiating a communication protocol with the hydrogen fuel mobile body (S403), an operation of negotiating a fueling protocol for fueling hydrogen to the hydrogen fuel mobile body with the hydrogen fuel mobile body (S404), and an operation of negotiating a fueling parameter based on the fueling protocol with the hydrogen fuel mobile body (S405).

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

[0140] As shown in Figure 5 A communication stack related to use cases of a bidirectional communication process for hydrogen fuel refilling (hereinafter, referred to as a "hydrogen fuel refilling communication stack") can be represented by a set of protocols corresponding to respective layers among the OSI 7 layers including a data link and physical layer, a network layer, a transport layer, a security layer, a session layer, a presentation layer, and an application layer.

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

[0142] Further, the hydrogen fuel refilling communication stack can include an Internet Protocol version 6 (IPv6) protocol 520 as a protocol of the network layer of the OSI 7 layers.

[0143] Further, the hydrogen fuel refilling communication stack can include at least one third protocol 530 selected from a Transmission Control Protocol (TCP), a User Datagram Protocol (UDP), etc. as a protocol of the transport layer of the OSI 7 layers.

[0144] Further, the hydrogen fuel refilling communication stack can include at least one fourth protocol 540 selected from a Transport Layer Security (TLS), a Datagram Transport Layer Security (DTLS), etc. as a protocol of the security layer of the OSI 7 layers. The TLS can include versions such as TLS 1.2 and TLS 1.3, and the DTLS can include versions such as DTLS 1.2 and DTLS 1.3. The TLS can be implemented on a TCP socket, and the DTLS can be implemented on a UDP socket.

[0145] Further, the hydrogen fuel refilling communication stack can include a JSON-based session protocol 550 as a protocol of the session layer of the OSI 7 layers. The JSON-based session protocol 550 can be used for communication in a communication between a vehicle and a dispenser or a data transmission between an electronic control unit of the vehicle and an electronic control unit of a fuel refilling station.

[0146] Further, the hydrogen fuel refilling communication stack can include a Javascript Object Notation (JSON) 560 as a protocol of the presentation layer of the OSI 7 layers. The JSON is one of formats that can be used when data is transmitted from a server to a client. Using the JSON, a protocol message between a vehicle and a dispenser or between an electronic control unit of the vehicle and an electronic control unit of a fuel refilling station can be expressed in a JSON format.

[0147] Further, the hydrogen fueling communication stack can include a hydrogen fueling related fueling protocol FP 570 as a protocol of an application layer of the OSI 7 layers. The fueling protocol 570 can include a first fueling protocol FP1, a second fueling protocol FP2, and an n-th fueling protocol FPn, where "n" can be a natural number greater than or equal to 3.

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

[0149] Communication data items that can be exchanged between the vehicle and the fueling station through the hydrogen fueling communication stack can be summarized as shown in Table 1.

[0150] [Table 1]

[0151]

[0152]

[0153] Meanwhile, the discovery and pairing process use case UC1 enables a device to identify a communication counterpart (i.e., a communication module of a vehicle or dispenser) responsible for controlling a socket or nozzle physically coupled to the device. Further, the use case UC1 can also define an incompatibility identification method and a security device mechanism. In this use case UC1, the vehicle and the dispenser can attempt to find a common communication technology to perform a fueling protocol. The vehicle and the dispenser can discover each other and initiate communication based on a discovery mechanism provided by a data link and physical layer. An additional pairing process can be required to establish a communication channel with a device connected to a fueling hose assembly. In a case where a communication channel cannot ensure correct pairing, for example, in the case of wireless communication, a separate pairing channel can be required to transmit pairing information. However, the communication channel integrated with the hose assembly can be sufficient if pairing is implicitly ensured, for example.

[0154] Table 2 shows Figure 4 The goal, pre-conditions, and post-conditions of the use case UC1 of the discovery and pairing operation (S401) shown.

[0155] [Table 2]

[0156]

[0157]

[0158] Table 3 shows supported communication technologies and related clauses that can be used in the use case UC1 of the discovery and pairing operation (S401) shown in FIG. 1. Figure 4

[0159] [Table 3]

[0160]

[0161] Figure 6 is a sequence diagram showing in detail the operation S401 according to the exemplary embodiment of the present disclosure. Referring to FIG. 4, Figure 6 Figure 4 In the pairing procedure of the discovery and pairing operation (S401) shown in FIG. 1, the vehicle and the dispenser can exchange pairing IDs and discover each other's pairing IDs during pairing at UCDC level 2 and UCDC level 3.

[0162] For example, the vehicle can broadcast a message PAIR_ID_ANNOUNCE containing its pairing ID (PAIR_ID), i.e., vehicle ID (vehicle_id). The dispenser can send a message PAIR_ID_ACK to the vehicle to acknowledge the reception of the vehicle ID from the vehicle. The vehicle can send a message PAIR_ID_CONFIRM to the dispenser to acknowledge the reception of the ACK message from the vehicle.

[0163] Next, the dispenser can broadcast a message PAIR_ID_ANNOUNCE containing its pairing ID, i.e., dispenser ID (dispenser_id). The vehicle can send a message PAIR_ID_ACK to the dispenser to acknowledge the reception of the dispenser ID from the dispenser. The dispenser can send a message PAIR_ID_CONFIRM to the vehicle to acknowledge the reception of the ACK message from the dispenser.

[0164] This transmission-echo-verification method enables the vehicle and the dispenser to use a session-specific random pairing ID. This method helps to address the privacy issue related to the exchange of pairing IDs. That is, the trust in the pairing procedure can be established through a subsequent procedure, and for this purpose, the session-specific pairing ID can be included in the data for establishing the trust.

[0165] ​​At the same time, when supporting secure communication at a particular UCDC level, one or more of the vehicle and the dispenser can verify that the pairing provides sufficient information to secure the communication channel for all methods of pairing the vehicle and the dispenser. For example, the pairing can include an exchange of encryption keys so that the vehicle and the dispenser can secure communications during fueling.

[0166] Note that since UCDC Level 1 does not support bidirectional communication, security of the communication channel cannot be ensured at UCDC Level 1. Pairing of the vehicle and the dispenser at UCDC Level 2 and UCDC Level 3 can be configured to provide sufficient information to secure communications sufficient to meet a particular security level (e.g., IEC 62443 Security Level 3). IEC 62443 Security Level 3 can be a security level for actors with sufficient resources and sufficient motivation.

[0167] Figure 7 An example of backward compatibility that can be employed in a bidirectional communication process for hydrogen fueling is shown in accordance with example embodiments of the present disclosure.

[0168] Reference Figure 7 In consideration of interoperability, a hydrogen fueling device can be designed to have backward compatibility with existing devices. A hydrogen fueling device or a communication device in a hydrogen fueling device can be classified as Type 0, Type 1, Type 2, and Type 3 based on interoperability.

[0169] A Type 0 device can refer to a device that does not support fueling communication or cannot receive relevant communication messages.

[0170] A Type 1 device can refer to a device that supports IrDA communication for fueling. A Type 1 device can fall back to a Type 0 device.

[0171] A Type 2 device can refer to a device that supports Advanced Communication (AC). A Type 2 device can fall back to a Type 0 device.

[0172] A Type 3 device can refer to a device that supports IrDA communication and advanced communication. A Type 3 device can fall back to any one of a Type 0, Type 1, and Type 2 device.

[0173] The advanced communication can refer to communication using specific protocols and media such as wireless local area network (WLAN), Bluetooth (BT), near field communication (NFC), WiFi, ultra wideband (UWB), radio frequency identification (RFID), 4G, and 5G. Further, the advanced communication can include bidirectional IrDA, serial communication, vehicle Ethernet (ETH), high-level communication, etc. The specific protocol can include transmission control protocol / internet protocol (TCT / IP), fueling protocol, etc. The advanced communication can handle all information exceeding that handled via the command and control communication. The data link of the advanced communication can use power line communication (PLC), but the disclosure is not limited thereto.

[0174] The advanced communication can include a hybrid form such as a combination of IrDA communication and wired communication and a combination of IrDA communication and wireless communication. The combination of IrDA communication and wired communication can require modification of the nozzle and the socket.

[0175] That is, the advanced communication can be a wired or wireless bidirectional communication scheme, and the wireless communication scheme can include various communication schemes such as 5G, WLAN, BLE, ETH, UWB, RFID, and NFC. A known protocol such as TCP / IP can be used as a communication protocol of the communication scheme. For example, the wireless communication scheme that can be considered can include Bluetooth, WLAN, WiFi (ISO 15118 for induction / ACD), UWB (IEC limitation consideration for ACD), or NFC.

[0176] In fact, the hydrogen fueling device can be implemented to support different communication schemes. Therefore, the bidirectional communication procedure for hydrogen fueling according to the present embodiment can be configured to maximize interoperability between devices.

[0177] In other words, as shown in FIG. 6, when a type 1 device supporting specification #1 according to a specific standard encounters a type 0 device or a type 2 device, the type 1 device can fall back to type 0 (S610). Figure 7

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

[0179] Further, when a type 3 device supporting specification #2 encounters a type 0 device, the type 3 device can fall back to type 0 (S630). When the type 3 device encounters a type 1 device, the type 3 device can fall back to type 1 (S640). When the type 3 device encounters a type 2 device, the type 3 device can fall back to type 2 (S650).

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

[0181] To support interoperability as described above, the hydrogen fuel dispensing device can perform a connection compatibility check. For example, depending on whether each device supports WLAN as one of the advanced communication schemes, the connection compatibility check can be performed according to the following scenario 1 to scenario 3.

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

[0183] In scenario 2, the dispenser does not support bidirectional WLAN but supports unidirectional IrDA. The dispenser corresponds to a type 1 device. The FCEV approaching the dispenser, which is a type 3 device, cannot scan and discover the dispenser as a type 1 device. When the nozzle attached to the cable of the dispenser is coupled to the socket of the FCEV, IrDA communication can begin between the FCEV and the dispenser.

[0184] In scenario 3, the dispenser can support bidirectional WLAN communication and unidirectional IrDA communication. In this case, the dispenser corresponds to a type 3 device. The FCEV, which is a type 1 device, can be parked near the dispenser. The dispenser also cannot find any WLAN client. When the nozzle attached to the cable of the dispenser is coupled to the socket of the FCEV, IrDA communication can begin between the FCEV and the dispenser.

[0185] Figure 8 Table 1 is a table summarizing examples of backward compatibility of the bidirectional communication procedure for hydrogen fuel dispensing suitable according to exemplary embodiments of the present disclosure.

[0186] Referring to Figure 8 The bidirectional communication procedure for hydrogen fuel dispensing according to the present embodiment can provide rules and principles of fallback when selecting a fuel dispensing method and a communication protocol to maximize interoperability rather than selecting a communication scheme preferred by the FCEV or the dispenser.

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

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

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

[0190] In the above-described configuration, if the vehicle and the dispenser have implementation manners that are common or the same type as each other, the vehicle and the dispenser can select a type supported by both devices, and the type is the best type among the types. When a device that does not have a communication capability (hereinafter, referred to as "non-communication device" or "non-communication device") encounters a device that supports one-way communication (hereinafter, referred to simply as "one-way communication device"), the latter can fall back to the non-communication device that does not support any communication scheme. When two devices that support two-way communication encounter each other, the two devices can maintain the two-way communication scheme as it is. Here, compatibility of the UCDC level can be handled separately. When a device encounters a non-communication device, the device must rely on non-communication. This rule can be applied to all devices that support two-way communication (hereinafter, referred to simply as "two-way communication device").

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

[0192] Regardless of whether or not equipped with one-way communication capability, the above-described two-way communication device can be configured to support a fuel filling method based on one-way communication. The two-way communication device needs to be able to check whether or not the counterpart device supports two-way communication. If the counterpart FCEV (or mobile body) and / or the dispenser does not support two-way communication, the two-way communication device can fall back to a one-way communication device that relies on a one-way communication scheme that can be compatible between devices.

[0193] Figure 9 Usage classification of communication data (UCDC) in a two-way communication process for hydrogen fuel filling according to an exemplary embodiment of the present disclosure is shown, and backward compatibility of the usage classification of communication data.

[0194] As Figure 9As shown, the vehicle and the dispenser can have respective pairing identities (IDs), and the requirements for exchanging IDs can be categorized by using a classification of the communication data (UCDC) level. The UCDC level can have a UCDC level 1 (UCDC-1) 910, a UCDC level 2 (UCDC-2) 920, and a UCDC level 3 (UCDC-3) 930. The UCDC level can also include a UCDC level 0 (UCDC-0) 900.

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

[0196] When pairing is attempted under the UCDC level 1 (UCDC-1) 910, the mobile body can send a pairing ID to the dispenser. Although the data communicated at the UCDC level 1 (UCDC-1) 910 is not used for a safety function, the static data communicated can be used to improve the performance of the fueling protocol, and the dynamic data communicated can be used to reduce the risk of deviation from the process during the fueling protocol.

[0197] The static data communicated under the UCDC level 2 (UCDC-2) 920 can be used for a safety function. The static data of the UCDC level 2 (UCDC-2) 920 can be data added to the static data and dynamic data defined for the UCDC level 1 for allowing use.

[0198] The static data and dynamic data under the UCDC level 3 (UCDC-3) 930 can be used for dynamic control of the protocol or for a safety function. The dynamic data of the UCDC level 3 (UCDC-3) 930 can be data added to the static data and dynamic data defined for the UCDC level 2 for allowing use.

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

[0200] Reference together Figures 4 to 8 ,exist Figure 4 The discovery and pairing operation (S401) may share information related to interoperability and / or compatibility between the vehicle / mobile object and the dispenser. This information may be used in the communication protocol negotiation operation (S403), the fueling protocol negotiation operation (S404), and / or the fueling parameter negotiation operation (S405) described below.

[0201] In another exemplary embodiment of the present disclosure, Figure 4 The information related to interoperability and / or compatibility shared between the vehicle / mobile and the dispenser in the discovery and pairing operation (S401) may be updated or shared again in the communication protocol negotiation operation (S403), the fueling protocol negotiation operation (S404), and / or the fueling parameter negotiation operation (S405). The information related to interoperability and / or compatibility may be updated due to changes in the communication environment, changes in parameters affecting the fueling process, etc.

[0202] In another exemplary embodiment of the present disclosure, Figure 4 The illustrated discovery and pairing operations ( S401 ) may be referred to as a Distributor Discovery Protocol (DDP).

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

[0204] The dispenser can receive a DDP request message DDPRequest and can send a DDP response message DDPResponse in response to the DDPRequest. The DDP response message DDPResponse can include an IP address of the dispenser "IPAddr", a TCP port number of the dispenser "TCPPort", a UDP port number of the dispenser "UDPPort", and a pairing ID of the dispenser "pairing_id".

[0205] Figure 10 is a sequence diagram illustrating an authorization procedure in a communication security procedure (S402) that can be employed in a bidirectional communication procedure for hydrogen fuel refueling according to an example embodiment of the present disclosure.

[0206] Referring to Figure 10 , the hydrogen fuel mobile body can request a list of authorization methods from the dispenser (S1010). The dispenser can send a response message to the request for the list of authorization methods to the hydrogen fuel mobile body (S1020). The response message can include a list of authorization methods related to self-authorization or external authorization such as RFID, credit card, or debit card.

[0207] Next, the hydrogen fuel mobile body can send an authorization request message to the dispenser, the authorization request message including an authorization method selected from the list of authorization methods such as RFID (S1030). The dispenser can send a response message to the authorization request of the hydrogen fuel mobile body to the hydrogen fuel mobile body (S1040). The response message can include information indicating that the authorization by the authorization method selected by the hydrogen fuel mobile body is working.

[0208] Then, the hydrogen fuel mobile body can wait for a response containing an authorization result from the dispenser and can send an authorization result request message (Done?) for the selected authorization method to the dispenser (S1050). If the authorization result is not received or the authorization is not completed, operations S1010 to S1050 can be repeatedly performed. After the authorization is completed, the dispenser can send an authorization completion message ("Done (Success)") to the hydrogen fuel mobile body (S1090).

[0209] According to the above-described procedure, the dispenser can verify whether the hydrogen fuel mobile body is authorized, i.e., whether the user of the hydrogen fuel mobile body has the right to hydrogen fuel refueling, before proceeding with the hydrogen fuel refueling procedure.

[0210] To ensure the security of the authorization process, after the data link and physical layer connection is established between the hydrogen fuel mobile body and the dispenser, the hydrogen fuel refueling device including one or more of the hydrogen fuel mobile body and the dispenser can establish a transport layer (i.e., TCP connection) and then perform a TLS handshake to authenticate and exchange keys, thereby establishing a secure communication channel. In the process of exchanging critical information for security, a user datagram protocol (UDP) communication protected by datagram transport layer security (DTLS) can be used.

[0211] Further, the hydrogen fuel mobile body and the dispenser can perform a discovery and pairing process and establish a connection in the data link and physical layer. Then, certificates required for authentication and key exchange can be prepared. Accordingly, the communication channel between the hydrogen fuel mobile body and the dispenser can be encrypted and protected for integrity. The dispenser can authenticate the hydrogen fuel mobile body, and optionally, the hydrogen fuel mobile body can authenticate the dispenser.

[0212] Meanwhile, during the TLS handshake, the authentication of the hydrogen fuel mobile body can be mandatory, and the authentication of the dispenser can be optional. In this case, the dispenser can act as a client and the hydrogen fuel mobile body can act as a server.

[0213] For the TLS handshake, the hydrogen fuel mobile body and the dispenser must prepare necessary certificates. The hydrogen fuel mobile body and the dispenser can store and maintain a certificate chain, a private key corresponding to its certificate, and a certificate of a trust anchor in a secure storage device to prevent unauthorized access.

[0214] During the TLS handshake, the hydrogen fuel mobile body can transmit a predefined certificate request message to the dispenser to request client authentication from the dispenser. After receiving the certificate request message, the dispenser can transmit a certificate and a certificate verification message to the hydrogen fuel mobile body to provide the hydrogen fuel mobile body with a certificate.

[0215] If the hydrogen fuel mobile body transmits the certificate request message together with a handshake message such as ServerHello, but the dispenser does not transmit the certificate verification message together with the certificate, the hydrogen fuel mobile body can terminate the TLS handshake by transmitting an alert message with an "Certificate_required" alert code.

[0216] According to another exemplary embodiment of the present disclosure, Figure 4 The purpose, preconditions, and postconditions of the illustrated operation S401 can be summarized as shown in Table 4.

[0217] [Table 4]

[0218]

[0219] Figure 11 is a sequence diagram illustrating a communication protocol negotiation operation S403 that can be employed in a hydrogen fuel filling bidirectional communication process according to an example embodiment of the present disclosure. Referring to Figure 11 , the communication protocol negotiation operation S403 can include an operation (S1110) of transmitting, to the dispenser, a message including information related to a first communication protocol applicable to the mobile body; and an operation (S1130) of receiving, from the dispenser, a message including information related to a second communication protocol selected from among common communication protocols applicable to both the mobile body and the dispenser.

[0220] In Figure 11 , the dispenser can receive, from the mobile body, a message including information related to a first communication protocol applicable to the mobile body (S1110), compare the first communication protocol with a communication protocol applicable to the dispenser to select a second communication protocol among common communication protocols applicable to both the mobile body and the dispenser, and transmit, to the mobile body, a message including information related to the selected second communication protocol (S1130).

[0221] Although not illustrated in Figure 11 , the communication protocol negotiation operation can further include an operation of the dispenser requesting, from the mobile body, information including a list of first communication protocols applicable to the mobile body, prior to operation S1110.

[0222] In an alternative example embodiment of the present disclosure, the dispenser can first transmit, to the mobile body, a message including information related to a communication protocol applicable to itself, and the mobile body can select a certain communication protocol among common communication protocols and transmit, to the dispenser, a message including information related to the selected communication protocol.

[0223] In such a case, the communication protocol negotiation operation can further include an operation in which the mobile body requests, from the dispenser, information including a list of applicable communication protocols.

[0224] Table 5 illustrates targets, preconditions, and postconditions of operation S403 according to an example embodiment of the present disclosure.

[0225] [Table 5]

[0226]

[0227]

[0228] Table 6 illustrates contents of a message transmitted or received in operation S1110 according to an example embodiment of the present disclosure.

[0229] [Table 6]

[0230]

[0231] The information related to the first communication protocol can include one or more of an index of the first communication protocol, a name of the first communication protocol, a version of the first communication protocol, and / or a preference for the first communication protocol. According to an exemplary embodiment of the present disclosure, the content of the message transmitted or received in operation S1130 can be summarized as shown in Table 7.

[0232] [Table 7]

[0233]

[0234] The response message including the information related to the second communication protocol can further include information related to whether the negotiation of the communication protocol is successful. After the mobile body and the dispenser discover each other and perform pairing on a compatible communication channel, a communication protocol negotiation procedure is performed to identify the communication protocol to be followed during the hydrogen fueling session. Specifically, in the present embodiment, the dispenser can actively exchange the communication protocol and parameters with the mobile body.

[0235] That is, the communication method according to an exemplary embodiment of the present disclosure can perform operation S401 of performing a discovery and pairing procedure with the dispenser using the first communication technology.

[0236] In the case where the result of the communication protocol negotiation operation S403 is related to the second communication technology, operation S404 of negotiating a fueling protocol and operation S405 of negotiating a fueling parameter (to be described in detail below) can be performed using the second communication technology.

[0237] In operation S401 of performing a discovery and pairing procedure, information related to interoperability and / or compatibility between the mobile body and the dispenser can be shared.

[0238] In the process of performing operations S403 to S405, the information on interoperability and / or compatibility between the mobile body and the dispenser shared in operation S401 of performing a discovery and pairing procedure can be updated in consideration of changes in the communication environment and environmental variables related to hydrogen fueling.

[0239] The communication protocol negotiation procedure can be implemented for all available communication protocols to ensure successful negotiation between different fueling protocols of each communication technology. For example, a fueling protocol using a communication technology such as WLAN can determine a communication protocol for hydrogen fueling used in a bidirectional communication procedure using a protocol commonly supported by the mobile body and the dispenser (hereinafter, referred to as a "common protocol").

[0240] In actual implementations, various combinations can exist between the mobile body and the dispenser according to the hydrogen fueling communication standards, communication modes, fueling methods, communication levels, and other parameters. Here, the hydrogen fueling communication standards can include the SAE J2601 series, ISO 19885-3, and ISO 19885-4 standards. The communication modes can include no communication, IrDA, XYZ (ISO), and the like. The fueling methods can include table-based fueling methods, such as a lookup table-based method and an MC formula-based fueling method. The communication levels can include UCDC levels, and the other parameters can include pressure levels, categories of compressed hydrogen storage systems (CHSS), hydrogen fueling tables, and the like.

[0241] Meanwhile, the mobile body or the dispenser can be configured to perform fallback to a lower type or a lower UCDC level according to the type of the counterpart device and the UCDC level discovered in the communication protocol negotiation process.

[0242] Among the various possible environmental combinations, if incompatibility is identified in the parameters exchanged during the negotiation process for hydrogen fueling (for example, in use cases UC3 to UC5), the mobile body and the dispenser can revert to the communication protocol negotiation process to perform the negotiation process again.

[0243] An example of a communication protocol assigned priority according to an exemplary embodiment of the disclosure is shown in Table 6.

[0244] The dispenser can transmit a response message including a specific protocol (i.e., a selected protocol) selected from the protocol list to the mobile body (S1130). The selected protocol selected by the dispenser can be a common protocol supported by both the dispenser and the mobile body and having the highest priority and preferred by the mobile body, for example, the ISO 19885-3-2023-UCDC-3 protocol in the example of Table 6.

[0245] The common protocol can be a result agreed upon between the mobile body and the dispenser regarding the communication protocol to be used for fueling communication.

[0246] Meanwhile, the mobile body can prioritize the communication protocols supported by the mobile body. The mobile body can include an FCEV. The mobile body can provide the dispenser with the prioritized communication protocols. An example of assigning priority to the communication protocols is shown in Table 8.

[0247] [Table 8]

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

[0249] After the communication protocol is selected in the communication protocol negotiation use case UC3, the mobile and the dispenser can activate their communication protocol implementations and start the fuel dispensing protocol negotiation. The fuel dispensing protocol negotiation is where the mobile and the dispenser discover and agree on a fuel dispensing protocol for a fuel dispensing session. In this operation, the mobile and the dispenser can select the mobile's preferred communication protocol among the protocols that both the mobile and the dispenser support. The communication protocol negotiation method for hydrogen fuel dispensing performed by the communication controller of the hydrogen fuel mobile 100 according to an exemplary embodiment of the present disclosure can include: operation S1110 of transmitting a first message to a communication entity related to the dispenser 200, the first message including a list of one or more first fuel dispensing protocols supported by the mobile and one or more first communication protocols required to perform the one or more first fuel dispensing protocols; and operation S1130 of receiving a response message from the communication entity related to the dispenser 200, the response message including a second fuel dispensing protocol selected from the one or more first fuel dispensing protocols. The communication entity related to the dispenser 200 can be the electronic controller 210 of the dispenser 200 or can be a separate communication device installed on the dispenser 200. Alternatively, the electronic controller or the separate communication device in the fuel dispensing station system 200 can communicate with the vehicle / mobile 100 instead of the dispenser 200.

[0250] The first message can include priority information based on the preferences of the mobile 100 as shown in Table 6. In addition, each message can be defined according to Tables 4 to 6.

[0251] The response message can include a second fuel dispensing protocol selected from the one or more first fuel dispensing protocols according to the priority information based on the preferences. The mobile 100 side or the dispenser 200 side can individually or in cooperation with each other select the second fuel dispensing protocol according to the priority information based on the preferences. The operation of finally transmitting an approval message to the other party to complete the protocol negotiation process can be performed by the mobile 100 side, but can alternatively be performed by the dispenser 200 side. In this case, the dispenser 200 can first transmit a list of supported protocols, and the mobile 100 can feedback the selected protocol.

[0252] The response message can include one or more first fuel dispensing protocols and a second fuel dispensing protocol selected from among protocols commonly included in the one or more first fuel dispensing protocols and protocols supported by the dispenser 200.

[0253] The response message can include a second communication protocol determined by the controller of the dispenser 200 from a plurality of first communication protocols required to perform the first fuel dispensing protocol according to a fallback device type based on interoperability and backward compatibility between the mobile 100 and the dispenser 200.

[0254] According to an exemplary embodiment of the present disclosure, in the absence of a common communication protocol, then a no-communication scheme can be selected as shown in Figures 7 to 9 and a hydrogen fueling protocol according to the no-communication scheme can be selected according to a predetermined rule, so that hydrogen can be supplied according to the selected hydrogen fueling protocol. In this case, the operations S404 to S405 to be described below can be simplified or omitted.

[0255] According to another exemplary embodiment of the present disclosure, if there is no common communication protocol, then the communication between the mobile body 100 and the dispenser 200 can be terminated (S409).

[0256] Figure 12 is a sequence diagram illustrating a communication protocol negotiation operation S404 in a bidirectional communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure.

[0257] Referring to Figure 12 the operation S404 to negotiate a fueling protocol according to an exemplary embodiment of the present disclosure can include an operation S1210 of transmitting a message including information related to a first fueling protocol applicable to the mobile body to the dispenser based on a result of the communication protocol negotiation (S403), and an operation S1230 of receiving a message including information related to a second fueling protocol selected from fueling protocols common to both the mobile body and the dispenser from the dispenser.

[0258] After the second communication protocol is selected as a result of the communication protocol negotiation (S403), a message including information related to one or more available first fueling protocols supporting the selected second communication and applicable to the mobile body can be transmitted to the dispenser (S1210).

[0259] The dispenser can select a fueling protocol common to the fueling protocol supporting the second communication protocol and the one or more available first fueling protocols applicable to the dispenser, and determine one of the selected common protocols as the second fueling protocol. At this time, the second fueling protocol can be determined based on interoperability and / or compatibility. Also, the second fueling protocol can be determined based on a preference set by the mobile body or the dispenser.

[0260] In Figure 12In the illustrated exemplary embodiment, the dispenser can receive a message including information related to one or more available first fueling protocols applicable to the mobile body from the mobile body (S1210), compare the first fueling protocol with a fueling protocol applicable to the dispenser, select a second fueling protocol from among common fueling protocols applicable to both the mobile body and the dispenser, and transmit a message including information related to the selected second fueling protocol to the mobile body (S1130).

[0261] Although not shown in FIG. 11, the operation S1210 can further include an operation in which the dispenser requests information including a list of first fueling protocols applicable to the mobile body from the mobile body, before the operation S1210. Figure 12

[0262] In another exemplary embodiment of the disclosure, the dispenser can first transmit a message including information related to a fueling protocol applicable to the dispenser to the mobile body, and the mobile body can select a specific fueling protocol among common fueling protocols and transmit a message including information related to the selected specific fueling protocol to the dispenser.

[0263] In this case, the operation can further include an operation in which the mobile body requests information including a list of fueling protocols applicable to the dispenser from the dispenser.

[0264] Table 9 shows the target, pre-condition, and post-condition of the operation S404 according to an exemplary embodiment of the disclosure.

[0265] [Table 9]

[0266]

[0267] Table 10 shows the content of a message transmitted or received in the operation S1210 according to an exemplary embodiment of the disclosure.

[0268] [Table 10]

[0269]

[0270]

[0271] The information related to the first fueling protocol can include one or more of an index of the first fueling protocol, a name of the first fueling protocol, a version of the first fueling protocol, a sub-protocol of the first fueling protocol, and a preference for the first fueling protocol. Table 11 shows the content of a message transmitted or received in the operation S1230 according to an exemplary embodiment of the disclosure.

[0272] [Table 11] ​

[0273]

[0274] The message including information related to the second fuel refueling protocol can further include information related to whether negotiation of the fuel refueling protocol is successful. Table 12 shows the content of the message transmitted or received in operation S1210 according to an exemplary embodiment of the present disclosure.

[0275] [Table 12]

[0276] Index Name Revision Sub-Protocol Preference 1 PRHYDE 2023 TYPE3-T - Initial 4 2 PRHYDE 2024 TYPE3-T - Special 3 3 RTR-HFP 2 4 ANN-MPC 5 5 HMC-FAST 1.0 1

[0277] As shown in Table 12, the mobile body can provide the dispenser with parameter information in a table form including a name of a fuel refueling method or a fuel refueling protocol supported by the mobile body, a revision date or year or version, information related to whether a sub-protocol is available, and preference information.

[0278] In an alternative exemplary embodiment, the dispenser can take the initiative in exchanging a communication protocol and parameters with the mobile body. In this case, the dispenser can assign priorities to communication protocols supported by the dispenser to provide the mobile body with information of the prioritized communication protocols.

[0279] In Table 11, PRHYDE (PROtocol for heavy-duty HYDrogEn refueling) is proposed by one of European projects that have developed a heavy-duty mobile body hydrogen fuel refueling protocol, RTR-HFP stands for Real-Time Response Hydrogen Fueling Protocol, and is proposed as a type of protocol concept for improving fuel refueling efficiency based on real-time communication, and ANN-MPC is proposed as a type of protocol concept that collects and analyzes data from a fuel refueling situation and applies predictive control to the fuel refueling situation.

[0280] Tables 13 and 14 show examples of the message transmitted in operation S1230 according to an exemplary embodiment.

[0281] [Table 13]

[0282] Fueling Protocol ID Result Code 2 OK

[0283] As shown in Table 13, the dispenser can select a fuel refueling protocol corresponding to index 2, and transmit a response message including a result code of OK to the mobile body.

[0284] [Table 14]

[0285] Fueling Protocol ID Result Code FAIL_NO_COMMON_PROTOCOL

[0286] As shown in Table 14, when the dispenser fails to find a compatible protocol in the list of mobile body supported fueling protocols received from the mobile body, the dispenser can transmit a response message to the mobile body containing information indicating that there is no common protocol present in the result code field (e.g., FAIL_NO_COMMON_PROTOCOL). The examples shown in Tables 13 and 14 can be similarly applied to Figure 11 The dispenser selects a second communication protocol among the common communication protocols and responds to the mobile body in the illustrated operation S1130.

[0287] Figure 13 is a sequence diagram illustrating a fueling parameter exchange / negotiation operation (S405) that can be employed in a bidirectional communication process for hydrogen fueling according to an example embodiment of the present disclosure.

[0288] The fueling parameter exchange / negotiation operation (S405) can include an operation in which the mobile body and the dispenser exchange detailed parameters required to execute a fueling protocol.

[0289] Referring to Figure 13 , the fueling parameter exchange / negotiation operation (S405) can include an operation (S1310) of transmitting a message including information related to mobile body side fueling parameters required for a second fueling protocol selected as a result of the fueling protocol negotiation operation (S404) to the dispenser and an operation (S1350) of receiving a message including dispenser side compatibility information for the mobile body side fueling parameters from the dispenser side.

[0290] The fueling parameter negotiation operation S405 can include an operation S1330 of receiving a message including information related to dispenser side fueling parameters required for a second fueling protocol selected as a result of the fueling protocol negotiation operation S404 from the dispenser and an operation S1370 of transmitting a message including mobile body side compatibility information for the dispenser side fueling parameters to the dispenser.

[0291] When the mobile body transmits the message including information related to the mobile body side fueling parameters in operation S1310, the mobile body can set an "Accepted" field for each corresponding parameter to <Pending> before transmitting to the dispenser.

[0292] Similarly, when the dispenser transmits the message including information related to the dispenser side fueling parameters in operation S1330, the dispenser can set an "Accepted" field for each corresponding parameter to <Pending> before transmitting to the mobile body.

[0293] When the mobile body transmits a message including information related to the fuel dispensing parameters of the dispenser side in response to the message received in operation S1330, the mobile body can set the "accept" field for each corresponding parameter to "0" before responding to the dispenser <ok>or <true> (S1350).

[0294] When the dispenser transmits a message including information related to the fuel filling parameters of the mobile side in response to the message received in operation S1310, the dispenser can set the "accept" field for each corresponding parameter to "false" before responding to the mobile. <ok>or <true>.

[0295] The mobile and the dispenser can respond by setting an "accept" field for each parameter. The "accept" field can be set to <false> for the parameters for which the negotiation has not reached an agreement.

[0296] The mobile and the dispenser can reach an agreement for all the refueling parameters by repeatedly sending and receiving messages and responding to the received messages.

[0297] The parameters exchanged between the dispenser and the mobile can include parameters for supporting refueling method compatibility, parameters related to physical characteristics, monitoring parameters, and parameters related to acceptability.

[0298] The compatibility-related parameters can include pressure classes and CHSS categories. The physical characteristics-related parameters can include maximum allowable CHSS pressure, maximum allowable CHSS temperature, maximum allowable flow rate, and CHSS volume. The monitoring parameters can include current CHSS pressure and current CHSS temperature. The acceptability-related parameters can include information indicating whether it is accepted, i.e., parameters indicating yes (true) or no (false). Each of the above parameters can include information corresponding to one of predetermined levels or settings and information about the same or different main UCDC levels.

[0299] Meanwhile, the dispenser can transmit information of second parameters (i.e., parameters of the dispenser) supported by the dispenser to the mobile and an OK message indicating that the first parameters are received (S1330, S1370).

[0300] The second parameters related to the refueling protocol exchange / negotiation can include parameters for supporting refueling method compatibility, parameters related to physical characteristics, refueling target parameters (target SoC), monitoring parameters, and parameters related to acceptability.

[0301] The compatibility-related parameters can include refueling delivery temperature and selected refueling table. The physical characteristics-related parameters can include maximum fuel delivery pressure, maximum fuel delivery temperature, minimum fuel delivery temperature, and maximum fuel delivery flow rate. The refueling target parameters can include target SoC, target final CHSS pressure, target final CHSS temperature, target APR, and target or expected refueling duration. The monitoring parameters can include current fuel delivery temperature and ambient temperature. The acceptability-related parameters can include information indicating whether it is accepted. Each of the above parameters can include information corresponding to one of predetermined levels or settings and information about the same or different main UCDC levels.

[0302] As described above, the mobile can provide the dispenser with parameters listed in a table form. The listed parameters can include FCEV parameters compatible with the UCDC level negotiated in the fueling protocol negotiation process.

[0303] As described above, after the communication link is established and the communication protocol and the fueling protocol are selected in the protocol negotiation phase, the mobile and the dispenser can exchange various parameters to determine whether they can perform a compatible fueling process. Here, the information required to perform a safe and efficient fueling process can include compatibility-related parameters, physical property-related parameters, fueling target parameters, and monitoring parameters.

[0304] The compatibility-related parameters can include a fueling protocol category and a fuel delivery temperature. The physical property-related parameters can include a CHSS pressure and a maximum allowable flow rate. The fueling target parameters can include a target SOC and a target CHSS pressure. The monitoring parameters can include a current CHSS temperature and an ambient temperature.

[0305] In a case where compatible parameters cannot be found and fueling cannot continue, the mobile can return to the communication protocol negotiation process to attempt to negotiate another protocol or stop fueling from the dispenser. In the communication protocol negotiation process after the fueling parameter exchange fails, the mobile can propose a set of supported protocols to the dispenser without including the protocol that failed in the fueling parameter exchange process.

[0306] After the fueling protocol is negotiated in the above-described use case UC-4, the mobile and the dispenser can negotiate specific parameters for the fueling protocol, notify static or dynamic states, and exchange detailed fueling parameters to determine a fueling target. In a case where the fueling parameter negotiation fails due to incompatibility of parameters, the dispenser and the mobile can return to use case UC-3 to select another fueling protocol or return to use case UC-1 to select another communication protocol. If use cases UC-3 and UC-1 cannot be properly performed, the dispenser and the mobile can terminate the current communication.

[0307] According to the above-described configuration, some fueling protocols can be performed based on a no-communication scheme. Another fueling protocol can require one-way IrDA communication. Another fueling protocol can require two-way communication. Another fueling protocol can require both two-way communication and one-way IrDA communication.

[0308] Some fueling protocols can require a predetermined UCDC level or a UCDC level higher than the predetermined UCDC level. At least one fueling protocol can be proposed based on the category or type of the hydrogen fuel mobile body and the category or type of the dispenser. The proposed fueling protocols can be assigned different priorities. The communication protocol between the hydrogen fuel mobile body and the dispenser and the fueling protocol can be finally determined based on whether the communication protocol required by the fueling protocol is supported by the hydrogen fuel mobile body and / or the dispenser and considering the priorities of the proposed fueling protocols.

[0309] In another exemplary embodiment of the present disclosure, one of the mobile body or the dispenser can first transmit fueling parameters to the other, and the other can give a response with a message including newly reconfigured fueling parameters by changing parameters not accepted among the received fueling parameters while keeping the accepted parameters.

[0310] In another exemplary embodiment of the present disclosure, the mobile body and the dispenser can perform parameter negotiation step by step. The mobile body and the dispenser can initiate negotiation for some parameters, and perform an exchange / negotiation process for sub-parameters among the parameters for which an agreement has been reached.

[0311] In another exemplary embodiment of the present disclosure, if a response message is not received within a preset message processing time, each message including fueling parameters can be set to be considered as not reaching an agreement.

[0312] Table 15 shows the content of a message including fueling parameters of the mobile body side according to an exemplary embodiment of the present disclosure.

[0313] [Table 15]

[0314] Name Unit Precision Range / Value Type Semantics Pressure Level N / A N / A {H35, H70} Static Tank Pressure Level CHSS Volume Liters 2 decimal places Positive, no maximum Static Tank Volume CHSS Pressure MPa 2 decimal places Positive, no maximum Dynamic Tank Current Pressure Emergency Strategy N / A N / A {Terminate, Backoff} Static Emergency Handling Strategy

[0315] Table 16 shows the content of a message including fueling parameters of the dispenser side according to an exemplary embodiment of the present disclosure.

[0316] [Table 16]

[0317]

[0318] In the fueling parameter negotiation operation (S405), the mobile body and the dispenser can transmit a message including the range or value of the supported fueling parameters to the other device. The parameters can include physical property-related parameters (hereinafter abbreviated as "physical parameters"), monitoring parameters, safety policy-related parameters, and acceptability-related parameters.

[0319] The physical parameters can include a socket type, a pressure level, a CHSS category, a CHSS type, a CHSS capacity, a maximum allowable CHSS pressure, a maximum allowable CHSS temperature, and a maximum allowable flow. The monitoring parameters can include a current CHSS pressure and a current CHSS temperature. The safety policy related parameters can include an emergency policy and a safety enforcement level. The acceptability related parameters can include information indicating whether it is accepted, i.e., a parameter indicating yes (true), no (false), or pending.

[0320] The parameters related to the fueling parameter negotiation can include the physical property related parameters (i.e., physical parameters), the monitoring parameters, the fueling target parameters, the safety policy related parameters, and the acceptability related parameters.

[0321] The physical property related parameters can include a maximum fuel delivery pressure, a maximum fuel delivery temperature, a minimum fuel delivery temperature, and a maximum fuel delivery flow. The monitoring parameters can include a current fuel delivery temperature and an ambient temperature. The fueling target parameters can include a selected fueling table, a target SOC, a target final CHSS pressure, a target final CHSS temperature, a target APR, and a target or expected fueling duration. The acceptability related parameters can include information indicating whether it is accepted. Each of the above parameters can include information corresponding to one of predetermined levels or settings and information about the same or different host UCDC levels.

[0322] The mobile body can provide the dispenser with the listed parameters in a table form. The listed parameters can include FCEV parameters compatible with the UCDC levels negotiated in the fueling protocol negotiation process.

[0323] Meanwhile, if the fueling parameter negotiation request message is received and the received fueling parameters are compatible with the dispenser, the dispenser can respond to the request message with its own fueling parameters by transmitting a fueling parameter negotiation response message with the negotiation result set to "OK" to the mobile body within a prescribed message response time interval.

[0324] If the fueling parameter negotiation request message is received but the received fueling parameters are not compatible with the dispenser, the dispenser can respond to the request message by transmitting a fueling parameter negotiation response message with the negotiation result set to "Fail" to the FCEV to indicate incompatibility with the mobile body (FCEV). The negotiation result can represent a value or information contained in a result code field, and the fail can represent a negotiation failure at a specific time and can be represented by an indication of incompatibility, e.g., "Fail_incompat".

[0325] Meanwhile, if the mobile receives the fueling parameter negotiation request message but finds that the received fueling parameter is not compatible with the mobile, the mobile can notify the dispenser of the incompatibility by sending an error notification message with the "cause" set to a predetermined error code.

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

[0327] Figure 14 is a conceptual diagram illustrating a table summarizing parameters transmitted from the mobile side to the dispenser side in a fueling parameter exchange / negotiation procedure according to an exemplary embodiment of the present disclosure.

[0328] Figure 15 is a conceptual diagram illustrating a table summarizing parameters transmitted from the dispenser side to the mobile side in a fueling parameter exchange / negotiation procedure according to an exemplary embodiment of the present disclosure.

[0329] Referring to Figure 13 and Figure 15 , the method of exchanging parameters for hydrogen fueling through communication according to an exemplary embodiment can include: operation S1310 of transmitting a first parameter to a communication entity related to the dispenser 200, the first parameter including one or more of: one or more first hydrogen fueling method compatibilities supported by the mobile 100, and one or more first physical characteristics; and operation S1330 of receiving a response message including a second parameter from the communication entity related to the dispenser 200, the second parameter including one or more of: one or more second hydrogen fueling method compatibilities supported by the dispenser, one or more second physical characteristics, and a fueling target.

[0330] The communication entity related to the dispenser 200 can be the electronic controller 210 of the dispenser 200 or can be a separate communication device installed on the dispenser 200. Alternatively, the electronic controller or the separate communication device in the fueling station system 200 can communicate with the vehicle / mobile 100 instead of the dispenser 200.

[0331] The first parameter can further include a first monitoring parameter supported by the mobile 100. The second parameter can further include a second monitoring parameter supported by the dispenser 200.

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

[0333] In the communication parameter exchange method for a hydrogen fuel filling process according to an exemplary embodiment of the present disclosure, the one or more first hydrogen fuel filling method compatibilities can include one or more of a pressure rating and a CHSS category of the mobile body 100.

[0334] In the communication parameter exchange method for a hydrogen fuel filling process according to an exemplary embodiment of the present disclosure, the one or more first physical characteristics can include one or more of a maximum allowed CHSS pressure, a maximum allowed CHSS temperature, a maximum allowed flow rate, and a CHSS volume.

[0335] In the communication parameter exchange method for a hydrogen fuel filling process according to an exemplary embodiment of the present disclosure, the first parameters further include parameters related to acceptability of the mobile body 100.

[0336] In the communication parameter exchange method for a hydrogen fuel filling process according to an exemplary embodiment of the present disclosure, the first monitoring parameters can include one or more of a current CHSS pressure and a current CHSS temperature.

[0337] In the communication parameter exchange method for a hydrogen fuel filling process according to an exemplary embodiment of the present disclosure, the one or more second hydrogen fuel filling method compatibilities can include one or more of a fuel filling delivery temperature of the dispenser 200 and a selected fuel filling table. The selected fuel filling table can include a list of selected fuel filling protocols, and can be included in the OK message shown in operation S1330.

[0338] In the communication parameter exchange method for a hydrogen fuel filling process according to an exemplary embodiment of the present disclosure, the one or more second physical characteristics can include one or more of a maximum fuel delivery pressure, a maximum fuel delivery temperature, a minimum fuel delivery temperature, and / or a maximum fuel delivery flow rate.

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

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

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

[0342] In operation S1310, the mobile body 100 can provide the dispenser 200 with the first parameter compatible with the UCDC level negotiated in the protocol negotiation process in the form of a table.

[0343] In operation S1330, the dispenser 200 can provide the mobile body 100 with the second parameter compatible with the UCDC level negotiated in the protocol negotiation process in the form of a table. At this time, the second parameter can be provided together with a message indicating the acceptability of the first parameter provided in operation S1310.

[0344] If the mobile body 100 or the dispenser 200 does not accept the exchanged parameter, the mobile body 100 can perform the protocol negotiation process again. Alternatively, if the mobile body 100 or the dispenser 200 does not accept the exchanged parameter, the mobile body 100 can terminate the fuel filling session.

[0345] In the protocol negotiation process retried due to the failure of the parameter exchange process in which the mobile body 100 or the dispenser 200 does not accept the exchanged parameter, the mobile body 100 can propose a set of supported protocols other than the protocol already provided in the failed parameter exchange process.

[0346] Table 17 illustrates the content of a message including a fuel filling parameter of the mobile body side according to another exemplary embodiment of the present disclosure.

[0347] [Table 17]

[0348]

[0349]

[0350] Table 18 illustrates the content of a message including a fuel filling parameter of the dispenser side according to another exemplary embodiment of the present disclosure.

[0351] [Table 18]

[0352]

[0353]

[0354] The communication method according to one exemplary embodiment of the present disclosure can further include the operation of re-negotiating one or more of the communication protocol and the fueling parameters (S405) in the event that the fueling parameters are incompatible between the mobile body and the dispenser as a result of the fueling parameters negotiation. In such a case, the re-negotiation operation in the communication method according to the exemplary embodiment can include performing the operations S403, S404, and S405 again. For example, the process can return to the operation S403 to perform the re-negotiation in the operation S403 and then perform the operations S404 and S405 again in sequence. In another embodiment, the process can return to the operation S404 to perform the re-negotiation in the operation S404 and then perform the operation S405 again.

[0355] In the communication method according to another exemplary embodiment of the present disclosure, the re-negotiation operation can perform the operations S403, S404, and S405 in a simplified mode or omit some of the processes. Alternatively, the re-negotiation operation can negotiate the communication protocol and the fueling protocol together in conjunction with the operations S403 and S404.

[0356] In the communication method according to another exemplary embodiment of the present disclosure, the re-negotiation operation can be performed based on a list of communication protocols or fueling protocols different from the communication protocol or the fueling protocol selected in the operations S403 and S404, respectively. For example, based on the compatibility and / or interoperability information identified in the operation S401, the communication protocol and the fueling protocol can be negotiated together using a list of protocols including both the communication protocol and the fueling protocol based on common support of the communication protocol and the fueling protocol in the mobile body and the dispenser.

[0357] The communication method according to an exemplary embodiment of the present disclosure can further include the operation of determining a third communication protocol and a third fueling protocol based on a prescribed policy when the fueling parameters are incompatible between the mobile body and the dispenser as a result of the fueling parameters negotiation (S405) and the operation of supplying hydrogen based on the third communication protocol and the third fueling protocol. In this case, a third fueling parameter can be determined based on the third fueling protocol and the operation of supplying hydrogen can be performed based on the third fueling protocol and the third fueling parameter.

[0358] For example, if the communication between the mobile body and the dispenser is not feasible due to a change in the communication environment, the dispenser can return to the no-communication scheme and supply hydrogen using a hydrogen fueling protocol based on the no-communication scheme.

[0359] The communication method according to the exemplary embodiment of the present disclosure can include an operation S409 of terminating the communication between the dispenser and the mobile body when, as a result of the fueling parameter negotiation, the fueling parameters are incompatible between the mobile body and the dispenser.

[0360] Referring back to Figure 4 , according to the exemplary embodiment of the present disclosure, a safety check-in procedure can be employed during the bidirectional communication for hydrogen fueling.

[0361] In the safety check-in operation S406, the dispenser and the mobile body (including itself) can check whether all necessary safety conditions have been satisfied before actual fueling starts.

[0362] After the fueling parameters are exchanged and the mobile body and the dispenser are deemed compatible, the mobile body and the dispenser can perform a safety state check to determine whether fueling can be safely performed. The safety check can be implicitly performed within the fueling protocol according to the fueling protocol. Further, the safety check-in operation S406 can be omitted according to the implementation.

[0363] During the safety check-in operation S406, the mobile body and / or the dispenser can check whether the coupling of the nozzle and the receptacle is locked, check whether there is any leak, and check the last-minute status.

[0364] In the case where the mobile body has received the fueling parameter negotiation response message from the dispenser and the fueling protocol supports the safety check-in function, the mobile body can initiate the safety check-in operation S406 by sending a safety check-in request message to the dispenser within a message sequence setup time interval.

[0365] The mobile body and the dispenser can exchange messages for the coupler check. The mobile body can send a message including information indicating its own coupler check result (e.g., "Mobile: OK") to the dispenser, and the dispenser can send a message including information indicating its own coupler check result (e.g., DP: OK) to the mobile body.

[0366] The mobile and the dispenser can exchange messages related to gas leak checking. During the exchange of messages related to gas leak checking, the dispenser can send information to the mobile indicating that the leak check is in progress ("in progress"). Also, the mobile can send information to the dispenser indicating that the mobile is waiting for the leak check result from the dispenser ("waiting"). When the leak check is completed, the dispenser can send a message to the mobile requesting the measured tank volume and information indicating that the leak check is completed ("completed").

[0367] The dispenser can send messages to the mobile for stationary state checking, and the mobile can send messages to the dispenser indicating that it is ready for state checking.

[0368] If the mobile reports to the dispenser parameters related to the current state or stationary state of the mobile, the dispenser can report to the mobile parameters related to the coupler lock state, the leak check state, and the predicted mobile tank capacity.

[0369] After the safety check-in operation S406 described above is completed, the actual fueling can be started. During the fueling, the mobile and the dispenser can exchange information for monitoring various state parameters to ensure that the fueling is performed safely and efficiently. If necessary, the mobile or the dispenser can send control messages requesting actions from the other party to control the fueling process or respond to safety-related conditions. The parameters and commands to be exchanged can vary depending on the actual fueling protocol.

[0370] Operation S407 represents a monitoring and control process that can be employed in the bidirectional communication process for hydrogen fueling according to example embodiments of the present disclosure.

[0371] In the monitoring and control operation S407, the dispenser and / or the mobile (including itself) can monitor the fueling state and control the fueling process if necessary. The mobile and the dispenser can proceed with the fueling process according to the selected fueling protocol and using parameters while confirming all safety checks. During the fueling, the mobile and the dispenser can exchange various measurement data to determine the fueling state as quickly as possible and detect safety critical events.

[0372] Further, the mobile can send certain commands to the dispenser to control the fueling process, such as the start or termination of fueling. At this time, the mobile can use UDP and DTLS for communication to support black channel communication. Black channel communication can refer to communication that applies the black channel principle to ensure secure communication, although the output characteristics of the communication channel can be insecure or have properties unrelated to the application.

[0373] The monitoring and control operation S407 will be described in more detail. The mobile body can send a message to the dispenser to start the fueling control, and in response, the dispenser can send a message including an acknowledgement to the mobile body (e.g., "OK").

[0374] Further, the mobile body can send a message to the dispenser including information of its own fueling cycle (e.g., x, y, z), and the dispenser can send a message to the mobile body including information of its own fueling cycle (e.g., a, b, c) corresponding to the mobile body's fueling cycle.

[0375] In addition, the mobile body can send a fueling control request message to the dispenser including information for slowing down the fueling or reducing the amount of delivered fuel, and the dispenser can send a response message to the mobile body including information indicating the slowing down of the fueling flow.

[0376] Further, the mobile body can send a fueling control request message to the dispenser to request stopping the fueling. The dispenser can send a fueling status response message to the mobile body including information of the fueling stop or having stopped.

[0377] According to the monitoring and control process, the mobile body and the dispenser can continuously or periodically exchange parameters related to the fueling status. The mobile body can send information such as the current tank temperature, the current tank pressure, etc. to the dispenser, and the dispenser can provide the mobile body with parameters related to the start, stop, ramp-up or ramp-down, current injection pressure, fueling plan, etc. of the fueling.

[0378] The message sent by the mobile body to the dispenser regarding the fueling control request can include information or parameters related to the start, pause, resume, and / or termination, etc. of the fueling. Further, the message related to the report sent by the mobile body to the dispenser can include information or parameters such as the current tank temperature and the current tank pressure.

[0379] The message sent by the dispenser to the mobile body regarding the report can include information or parameters related to, for example, the status information, the current ambient temperature, the current pressure rise rate (PRR), the delivered fuel flow, the current fuel delivery temperature, the pre-cooling temperature, the current fuel delivery pressure, whether full fueling is used, whether a cooled dispenser is used, whether a fallback is used, the reason for the fueling stop, the current amount of hydrogen delivered.

[0380] The message related to the target parameter update sent by the dispenser to the mobile body can include the target final tank pressure, the target final tank temperature, the target fueling APR, the target SOC, the current SOC, and the estimated remaining duration.

[0381] Meanwhile, when using TCP in the monitoring and control operation S407, if the safety check-in response message or the safety check-in procedure according to the fueling protocol is omitted, after receiving the fueling parameter negotiation response message from the dispenser, the mobile body can transmit a fueling cycle request message to the dispenser within a message sequence setup time interval. The request message or the response message related to the fueling cycle can be transmitted through the DTLS message.

[0382] After the hydrogen fueling is completed through the monitoring and control operation S407, before terminating the session and taking the nozzle off from the mobile body, the mobile body and the dispenser can check whether the mobile body and the dispenser satisfy all safety conditions through the safety check-out use case. The safety check-in procedure can be optional, but it is desirable to define a dedicated safety check-in procedure in the fueling protocol in order to ensure the desired safety level in a precise and explicit manner.

[0383] The safety check-out procedure S408 that can be employed in the bidirectional communication procedure for hydrogen fueling according to the exemplary embodiment of the present disclosure can be performed as follows. The mobile body and the dispenser can check that all necessary safety conditions are satisfied before the nozzle of the dispenser is disconnected from the socket of the mobile body through the safety check-out procedure. In other words, the mobile body and the dispenser can verify that it is absolutely safe for the user or the operator to disconnect the nozzle from the mobile body after the fueling is completed.

[0384] For example, if the mobile body receives a fueling cycle response message having a "Result" attribute set to "OK" or a "Status" attribute set to "Complete" from the dispenser, or the mobile body receives a fueling status response message including information to stop fueling, and if the hydrogen fueling protocol supports safety check-out, the mobile body can start the safety check-out and perform the safety check-out operation S408 by transmitting a safety check-out request message to the dispenser within a message sequence setup time period.

[0385] The mobile body and the dispenser can repeatedly report their status to each other until the safety check is verified. If the bidirectional communication procedure for hydrogen fueling does not require such a safety check at the end, the use case for safety check-out can be omitted.

[0386] The safety check-out operation S408 will be described in more detail. The mobile body can transmit a message containing information related to the coupler check result (e.g., "OK") to the dispenser, and the dispenser can transmit a message containing information indicating that the coupler check is in progress (e.g., "In Progress") to the mobile body.

[0387] Further, the mobile body can transmit again to the dispenser a message containing information related to the coupler check result (e.g., "OK"), and the dispenser can transmit to the mobile body a message containing information indicating that the coupler check is completed (e.g., "Done").

[0388] When the coupler check result shows that the coupler check is normally completed, the user or operator can separate the nozzle of the dispenser from the socket of the mobile body.

[0389] In the safety check-out operation S408, the report message transmitted by the dispenser to the mobile body can include information or parameters about the coupler unlock status. The coupler unlock status information can include information of locked, unlocked, frozen, or problem.

[0390] When the fuel filling according to the hydrogen fuel filling protocol is completed and the nozzle is safely separated, or when a non-safety critical problem occurs during another use case, the termination use case UC9 can be executed.

[0391] The termination procedure S409 that can be employed in the bidirectional communication procedure for hydrogen fuel filling according to the exemplary embodiment of the present disclosure can be executed as follows.

[0392] In the termination operation S409 as the last stage of the fuel filling, the mobile body and the dispenser can exchange information about the fuel filling result related to the fuel filling performance and method and / or information related to the cause of the unexpected stop of the fuel filling to complete all operations related to the hydrogen fuel filling. The termination use case can also be configured to handle tasks related to non-safety critical problems when they occur.

[0393] For example, after the mobile body receives the safety check-out response message in which the "result" attribute is set to "complete" or the fuel filling cycle response message in which the "status" attribute is set to "complete" or the information including the stop of the fuel filling from the dispenser, the mobile body can transmit a termination request message to the dispenser to execute the termination operation S409.

[0394] The termination operation S409 will be described in more detail. The mobile body can transmit a message to the dispenser to inquire how much fuel has been filled from the dispenser. The dispenser can transmit a response message including information related to the amount of hydrogen fuel filling (e.g., X grams) to the mobile body in response to the inquiry message.

[0395] Subsequently, the mobile body can transmit a confirmation request message for completing the fuel filling to the dispenser, and the dispenser can transmit a goodbye message to the mobile body as a response message to the confirmation request message.

[0396] After completion of the fueling and performing the safety check, the mobile and the dispenser can exchange at least some bookkeeping information for terminating the fueling session in the hydrogen fueling of the termination operation S409. The mobile and the dispenser can exchange summary information related to the hydrogen fueling session before completion of the termination operation S409.

[0397] The bookkeeping information can include all information related to the hydrogen fueling recorded in the mobile or the dispenser according to a prescribed rule or policy for all fueling sessions for the hydrogen fueling and before completion of the termination operation S409 of the use case UC-9.

[0398] The bookkeeping information or the summary information can include information related to how much fuel is dispensed and what report is generated. In addition, the report message transmitted by the mobile to the dispenser can include information or parameters related to the current tank temperature and the current tank pressure. Meanwhile, the report message transmitted by the dispenser to the mobile can include information related to the final SOC, the final average fueling rate (APR), the final measured tank pressure, the actual fueling time, and the actual amount of hydrogen fueling.

[0399] When all necessary information of the fueling session is stored, the fueling session can be completely terminated.

[0400] Table 19 summarizes an example of the communication data exchanged in some of the use cases UC5 to UC9.

[0401] [Table 19]

[0402]

[0403]

[0404]

[0405] Meanwhile, the error handling use case UC10 is a functional block for handling a case where a safety non-critical error occurs due to a sudden interruption of the closing or communication similar to the normal termination of the fueling process. The error handling operation S410 that can be employed in the bidirectional communication process for the hydrogen fueling according to the exemplary embodiment of the present disclosure can be performed as follows.

[0406] The error handling operation S410 can include the definition of error conditions related to the fueling protocol, the provision of detection criteria, and a response procedure including notification, termination process, and fallback mechanism when an error occurs.

[0407] When a non-safety critical error occurs and further communication is not possible, an error handling operation S410 can be applied. According to the error handling procedure, the mobile and dispenser can handle non-safety critical errors that occur at any time during fuel dispensing. When a non-safety critical error occurs, the mobile and dispenser can immediately stop fuel dispensing, temporarily stop the previously selected and currently operating use case, and then proceed to terminate the use case UC9.

[0408] If the mobile detects an event related to a non-safety critical error, the mobile can inform the dispenser of the termination cause through a termination request message and stop the current fuel dispensing session or communication session. The dispenser can terminate the current communication session in response to the termination request message. The current session can be terminated without additional notification if further communication is not feasible.

[0409] When a non-safety critical error is detected in the mobile and the communication channel maintains an operable condition, the mobile can send a termination request message to the dispenser with an "Action" attribute set to "Stop" and a "Reason" attribute set to an appropriate cause or cause code. Examples of appropriate causes or cause codes can include causes such as "message corrupted."

[0410] The termination request message can be sent in error situations where a non-safety critical communication error, system error, or qualitative error occurs, excluding non-recoverable cases.

[0411] That is, for successful fuel refueling, the communication must convey actions that can be expected according to the protocol, and the fuel dispensing operation needs to be within the acceptable range of the fuel dispensing protocol. However, various abnormal events can occur in practice. While some errors are trivial and can be easily handled, others are non-recoverable and can hinder the progress of fuel dispensing. The error handling operation S410 is able to define non-safety critical error conditions and provide exemplary error conditions and possible responses.

[0412] Examples of communication errors can include instances of communication disconnection, received data that cannot be recognized due to encoding errors or syntax errors, or received data that is outside the allowable range. System errors can include instances where the dispenser or mobile detects a critical system error on its own. Qualitative errors can include instances where the quality of communication performance does not meet the required level or the quality of data integrity or precision does not meet the required level.

[0413] The bidirectional communication procedure for hydrogen fuel dispensing according to the present embodiment can perform the following specific error handling operation S410 as outlined in (1) to (4) for the above error conditions.

[0414] (1) In the case where a non-safety critical error occurs and further communication is not possible, the mobile body and the dispenser can immediately stop fueling, but can take safety actions and terminate the session by stopping communication.

[0415] (2) In the case where a non-safety critical error occurs and fueling is suspended and cannot be completed, the fueling protocol can define a fallback mechanism, for example, by defining a non-communication fueling method.

[0416] (3) In the case where a non-safety critical error is detected in the mobile body and the communication channel is still running, the mobile body can send a termination request message to the dispenser, in which the "action" attribute is set to "stop" and the "cause" attribute is set to an appropriate cause or cause code.

[0417] (4) In the case where a non-safety critical error is detected in the dispenser and the communication channel is still running, the dispenser can immediately stop fueling and send a termination request message to the mobile body, in which the "action" attribute is set to "stop" and the "cause" attribute is set to an appropriate cause or cause code.

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

[0419] Meanwhile, when a safety critical issue occurs during fueling in a hydrogen fueling system, an emergency action / handling can be required.

[0420] An emergency handling procedure S411 that can be employed in the bidirectional communication procedure for hydrogen fueling according to an exemplary embodiment of the present disclosure can be performed as follows.

[0421] The emergency handling operation S411 can define safety critical conditions that require emergency action during fueling, and can include a response procedure to prevent a safety critical accident.

[0422] In order to safely perform fueling, communication must convey actions that are expected according to the protocol, and the fuel refueling operation needs to be within the safety range of the fueling protocol. However, problems can occur during fueling, causing the fueling system to reach a critical state that must be avoided at all costs. The emergency handling operation S411 enables safety critical emergency situations and possible actions to the emergency situations to be defined, and can provide important situations to be considered.

[0423] The fueling protocol can define an emergency situation related to the protocol, provide a detection criterion for the emergency situation and performance requirements of the mobile body or dispenser, and prescribe a response procedure S411 to avoid entering a dangerous situation.

[0424] In more detail, when the mobile body detects a high pressure condition exceeding a predetermined reference value during the hydrogen fueling, the mobile body can transmit a first emergency stop request message including information requesting a fueling stop according to the high pressure (e.g., "Emg: Stop (high pressure)") to the dispenser. The dispenser can transmit a response message including information indicating that the dispenser is processing an emergency fueling stop (e.g., "Emg: Stop") to the mobile body in response to the first emergency stop request message.

[0425] Further, upon receiving the response message or after a preset time has elapsed from receiving the response message, the mobile body can transmit the first emergency stop request message to the dispenser again. After the emergency stop of fueling, the dispenser can transmit a response message including information indicating that the fueling has been stopped (e.g., "Emg: Stop") to the mobile body.

[0426] Meanwhile, if the dispenser detects a hydrogen fuel leakage during the hydrogen fueling, the dispenser can transmit a second emergency stop request message including information indicating that it is processing a fueling stop due to the leakage (e.g., "Emg: Stop (leakage)") to the mobile body. The mobile body can transmit a response message including information indicating an acknowledgement of the second emergency stop request message (e.g., "Emg: Ack") to the dispenser.

[0427] Further, the dispenser can transmit a third emergency stop notification message including information indicating that the fueling has been stopped due to the leakage (e.g., "Emg: Stop (leakage)") to the mobile body. The mobile body can transmit a response message including information indicating an acknowledgement of the third emergency stop notification message (e.g., "Emg: Ack") to the dispenser.

[0428] According to the above-described configuration, when the mobile body or the dispenser detects a critical condition affecting safety, the mobile body and / or the dispenser can immediately take necessary measures to prevent a disaster from occurring and, if possible, transmit an emergency notification message containing information related to the condition to the other party and block communication between the mobile body and the dispenser.

[0429] Upon receiving the emergency notification message, the mobile or the dispenser can immediately respond to the condition indicated in the emergency notification message and terminate the communication without undue delay. The emergency notification message can include a header and a body including the message. The header can include information indicating the emergency notification and the message can include values, information or parameters for the level, type and action of the emergency notification.

[0430] The emergency notification message can be sent through a TLS or DTLS message depending on the technology used for the communication.

[0431] Referring again to Figure 4 , the purpose, pre-conditions and post-conditions of the safety check-in operation (S406) can be shown by Table 20 below.

[0432] [Table 20]

[0433]

[0434]

[0435] As described above, when the fuel dispensing parameter negotiation operation (S405) is successfully performed, the fuel dispensing protocol can support the safety check-in operation (S406).

[0436] In the case where the communication physical layer is defined as requiring a pairing process, the mobile and the dispenser can recheck pairing before dispensing hydrogen in the safety check-in operation (S406).

[0437] Even in the case where the communication physical layer is not defined as requiring a pairing process, the mobile and the dispenser can recheck pairing before dispensing hydrogen in the safety check-in operation (S406).

[0438] Upon receiving a message (e.g., FuelParamNegoRes) indicating completion of operation S405 from the dispenser, when the fuel dispensing protocol supports the safety check-in operation (S406), the mobile can transmit a message (e.g., SafetyCheckInReq) indicating start of the safety check-in operation (S406) to the dispenser within a predetermined time interval (e.g., MessageSequenceTimeout).

[0439] As an alternative exemplary embodiment, in the case where a message indicating completion of operation S405 is transmitted from one of the mobile or the dispenser to the other, the one or the other can transmit a new message indicating start of the safety check-in operation (S406).

[0440] According to an exemplary embodiment of the present disclosure, the messages transmitted and received in the safety check-in operation (S406) can be defined based on the contents of each fueling protocol defined in standards such as ISO 19885-3.

[0441] According to an exemplary embodiment of the present disclosure, the messages transmitted and received in the safety check-in operation (S406) can include a result value for processing a request message as a result element. For example, the result value provided as the result element can include "OK" in the case of success, "FAILED" in the case of failure, and "PENDING" in other cases.

[0442] In the case where all safety conditions are satisfied when the mobile body transmits the SafetyCheckInReq message to the dispenser, the result value of the message can be set to "OK".

[0443] In the case where some safety conditions have not been satisfied when the mobile body transmits the SafetyCheckInReq message to the dispenser, the result value of the message can be set to "PENDING".

[0444] After receiving the SafetyCheckInReq message, the dispenser can respond to the mobile body by including a safety check parameter in the SafetyCheckInRes message within a MessageResponseTimeout time period.

[0445] In the case where all safety conditions are satisfied when the dispenser transmits the SafetyCheckInRes message to the mobile body, the result value of the message can be set to "OK".

[0446] In the case where some safety conditions have not been satisfied when the dispenser transmits the SafetyCheckInRes message to the mobile body, the result value of the message can be set to "PENDING".

[0447] In the case where the mobile body receives the SafetyCheckInRes message in which the result value is set to "PENDING", the mobile body can transmit another SafetyCheckInReq message to the dispenser within a MessageResponseTimeout time interval.

[0448] In the case where the dispenser receives the SafetyCheckInReq message in which the result value is set to "PENDING", the dispenser can transmit another SafetyCheckInReq message to the mobile body within a MessageResponseTimeout time interval.

[0449] In case the mobile or dispenser fails to confirm all safety conditions within a predetermined time (e.g., UC Safety Check In Timeout), an ErrNotifReq message with the "Reason" field set to an appropriate error code can be sent.

[0450] As an alternative exemplary embodiment, the mobile or dispenser can send a request message to the other party indicating the start of the safety check-in, and the other party can respond to the request message for the safety check-in with a response message within a predetermined time interval.

[0451] Referring again to Figure 4 , the purpose, pre-conditions, and post-conditions of the monitoring and control operation (S407) can be illustrated by Table 21 below.

[0452] [Table 21]

[0453]

[0454]

[0455] As previously described, when the safety check-in operation (S406) is successfully performed, the fueling protocol can perform the monitoring and control operation (S407).

[0456] In case the safety check-in operation (S406) is omitted, when the fueling parameter negotiation operation (S405) is successfully performed, the fueling protocol can perform the monitoring and control operation (S407).

[0457] During the monitoring and control operation (S407), the dispenser can perform all necessary steps to supply hydrogen fuel to the mobile.

[0458] When the TCP specification is used in the fueling control and monitoring use case, the mobile can send a message (e.g., Fuel Loop Req message) to the dispenser requesting the start of the monitoring and control operation (S407) within a predetermined time interval (e.g., Message Sequence Timeout) after receiving the SafetyCheckInRes message, or in the exemplary embodiment where the safety check-in operation (S406) is omitted, after receiving the FuelParamNegoRes message.

[0459] When the above black channel is used, the mobile (as a client) and the dispenser (as a server) can initiate session resumption using the NewSessionTicket after sending the SafetyCheckInRes message, or after sending the FuelParamNegoRes message in the exemplary embodiment in which the safety check-in operation (S406) is omitted, and initiate the DTLS 1.3 handshake according to the RFC 9147 specification. In this case, the NewSessionTicket can be received from the dispenser.

[0460] After the DTLS 1.3 handshake is successfully completed, the mobile can send a message (e.g., a FuelLoopReq message) requesting the start of the monitoring and control operation (S407) to the dispenser within a predetermined time interval (e.g., MessageSequenceTimeout).

[0461] In this case, 0-RTT can not be used for the DTLS session resumption.

[0462] The FuelLoopReq message and its corresponding response message (e.g., a FuelLoopRes message) can both be sent according to the DTLS message specification.

[0463] Additional requirements required for the black channel method can be added.

[0464] The FuelLoopReq message can be implemented based on the definition of each fueling protocol.

[0465] The fueling protocol can specify static data or dynamic data to be included in the FuelLoopReq and FuelLoopReq messages, so that the static data or dynamic data can be used to monitor the fueling state and exchange safety-related information.

[0466] Element names included in the FuelLoopReq message can include action, reason, etc., and can be shown in Table 22 below. Elements not shown in Table 22 can be specified according to each fueling protocol specification such as ISO 19885-3.

[0467] [Table 22]

[0468]

[0469] Element names included in the message (e.g., the FuelLoopRes message) transmitted and received in operation S407 can include status, reason, result, etc., and can be shown in Table 23 below. Elements not shown in Table 23 can be specified according to each fueling protocol specification such as ISO 19885-3.

[0470] [Table 23]

[0471]

[0472]

[0473] When a mobile sends a FuelLoopReq message, the dispenser is expected to perform a corresponding action. The mobile can set the "action" to the desired action code and send the message. The action code can be defined according to the hydrogen fueling protocol.

[0474] Upon receiving a FuelLoopReq message (e.g., with "action" set to "start"), when the dispenser is ready to start, the dispenser can start the hydrogen fueling process using the agreed method and respond with a FuelLoopReq message with "result" set to "OK".

[0475] Upon receiving a FuelLoopReq message (e.g., with "action" set to "start"), when the dispenser is not ready to start, the dispenser can respond with a FuelLoopReq message with "result" set to "pending".

[0476] Upon receiving a FuelLoopReq message (e.g., with "action" set to "stop"), when the dispenser is ready to stop, the dispenser can stop the hydrogen fueling process as defined in the hydrogen fueling protocol and respond with a FuelLoopReq message with "result" set to "ongoing".

[0477] Upon receiving a FuelLoopReq message (e.g., with "action" set to "stop"), when the dispenser is ready to stop, the dispenser can immediately stop the hydrogen fueling process and respond with a FuelLoopRes message with "result" set to "OK".

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

[0479] When a received FuelLoopReq message is successfully processed, the dispenser can send a FuelLoopRes message with "result" set to "OK".

[0480] When the received FuelLoopReq message is not successfully processed, the dispenser can send a FuelLoopRes message with "Result" set to "Failure" or another appropriate error code.

[0481] The dispenser can send a FuelLoopRes message with "Status" set to one of the supported codes in Table 23 or specified by the hydrogen fueling protocol.

[0482] When hydrogen fueling is completed (or achieved) and the intended fueling goal is achieved (target SoC is reached), the dispenser can send a FuelLoopRes message with "Status" set to "finished".

[0483] When hydrogen fueling is stopped due to an error-related reason, the dispenser can send a FuelLoopRes message with "Status" set to "stop_error" and "Reason" set to an appropriate reason code.

[0484] When the "Action" of the most recent FuelLoopReq message is set to "stop" and hydrogen fueling has not yet completely stopped, the dispenser can send a FuelLoopReq message with "Status" set to "stop".

[0485] When the "Action" of the most recent FuelLoopReq message is set to "stop" and hydrogen fueling has completely stopped, the dispenser can send a FuelLoopRes message with "Status" set to "stop_request".

[0486] When the mobile has sent a FuelLoopReq message with "Action" set to "stop" and receives a FuelLoopReq message with "Status" set to "stop", the mobile can send a FuelLoopReq message with "Action" set to "stop".

[0487] When the mobile receives a FuelLoopReq message and hydrogen fueling has not yet been completed, the mobile can send a FuelLoopReq message within a predetermined time interval (e.g., MessageSequenceTimeout).

[0488] When a critical safety event occurs, the mobile or the dispenser can immediately send an EmergencyReq message, terminate the hydrogen fueling process, and close the communication.

[0489] The above exemplary embodiments related to operation S407 have been described based on a case where each operation is started upon a request by the mobile body and the dispenser gives a response. However, the concept of the present disclosure is not limited to this. In alternative exemplary embodiments, the mobile body or the dispenser can send a message requesting start of operation S407, and the counterpart can respond to the request, thereby enabling operation S407 to be performed.

[0490] In operation S407, the message sent by the mobile body or the dispenser can include a monitoring request regarding the status of the hydrogen fuel filling process. The response message from the counterpart can include the status information of the requested monitoring subject.

[0491] The status and related parameters of the subject of the monitoring request can include the parameter set exchanged in operation S405. The status and related parameters of the subject of the monitoring request can include the status and parameters of the mobile body or the dispenser. The status and related parameters of the subject of the monitoring request can include the hydrogen fuel filling status and / or related parameters of the mobile body and / or the dispenser that are changed or maintained by the hydrogen fuel filling process.

[0492] Further, the status of the subject of the monitoring request can include the status and / or information of the hydrogen fuel filling process itself performed from the dispenser to the mobile body. For example, the information can include whether the hydrogen fuel filling process is in progress, suspended, completely terminated, and / or if stopped / terminated, whether it is completed due to an error or due to achievement of the intended goal, etc.

[0493] Referring again to Figure 4 , the purpose, preconditions, and postconditions of the safety checkout operation (S408) can be shown in Table 24 below.

[0494] [Table 24]

[0495]

[0496]

[0497] After completion of the fuel filling, a safety checkout operation (S408) can be performed to ensure that the mobile body and the dispenser satisfy safety conditions before terminating the session and pulling the nozzle from the mobile body. Although the safety checkout operation (S408) is optional, a dedicated safety checkout procedure defined by the fuel filling protocol can be strongly recommended in order to ensure the desired level of safety in an accurate and explicit manner.

[0498] When a safety-related event occurs, the information exchange used in the safety checkout operation (S408) can be used for the purpose of diagnosis and liability verification.

[0499] As described above, when the monitoring and control operation (S407) and the related fuel dispensing process are successfully completed, the fuel dispensing protocol can perform a safety check-out operation (S408).

[0500] Regardless of whether the safety check-out is performed, the fuel dispensing protocol conforming to ISO 19885-2 can define a set of safety conditions to be confirmed between the mobile body and the dispenser before the nozzle is pulled out.

[0501] When the FuelLoopRes message in which the "result" is set to "OK" and the "status" is set to a value prefixed with "complete" or "stop" is received, and the fuel dispensing protocol supports the safety check-out, the mobile body can transmit a message (S408) (e.g., SafetyCheckOutReq message) requesting the start of the safety check-out operation to the dispenser via the TLS channel within a predetermined time interval (e.g., MessageSequenceTimeout).

[0502] When the TCP / TLS channel is disconnected, the mobile body can reestablish the TCP / TLS channel with the dispenser. The reestablishment process can be initiated by using the TLS resume handshake using the NewSessionTicket received before the transmission of the SafetyCheckOutReq message.

[0503] As an alternative exemplary embodiment, the message requesting the start of the safety check-out operation (S408) can be transmitted to the other party by the mobile body or the dispenser. The other party can perform the operation S408 by responding to the message requesting the start of the safety check-out operation (S408).

[0504] According to an exemplary embodiment of the present disclosure, the messages transmitted and received in the safety check-out operation (S408) can be defined based on the content of each fuel dispensing protocol as specified in standards such as ISO 19885-3.

[0505] According to an exemplary embodiment of the present disclosure, the messages transmitted and received in the safety check-out operation (S408) can include a result type as a processing result of the request message. In this case, the values that can be provided as the result type can include "OK" in the case of success, "Failure" in the case of failure, and "Pending" in other cases.

[0506] In the case where the mobile body confirms that all the safety conditions are satisfied when the SafetyCheckOutReq message is transmitted to the dispenser, the result value of the message can be set to "OK".

[0507] In the case where the mobile determines that some safety conditions have not been satisfied when sending the SafetyCheckOutReq message to the allocator, the result value of the message can be set to "Pending".

[0508] Upon receiving the SafetyCheckOutReq message, the allocator can respond to the mobile with a SafetyCheckOutRes message including the safety check parameters within a MessageResponseTimeout time period.

[0509] In the case where the allocator confirms that all safety conditions are satisfied when sending the SafetyCheckOutRes message to the mobile, the result value of the message can be set to "OK".

[0510] In the case where the allocator determines that some safety conditions have not been satisfied when sending the SafetyCheckOutRes message to the mobile, the result value of the message can be set to "Pending".

[0511] In the case where the mobile receives the SafetyCheckOutRes message with the result value set to "Pending", the mobile can send another SafetyCheckOutReq message to the allocator within a MessageResponseTimeout time interval.

[0512] In the case where the allocator receives the SafetyCheckOutReq message with the result value set to "Pending", the allocator can send another SafetyCheckOutReq message to the mobile within a MessageResponseTimeout time interval.

[0513] When the mobile or the allocator fails to confirm all safety conditions within a predetermined time (e.g., UCSafetyCheckOutTimeout), the mobile or the allocator can send an ErrNotifReq message with the "Reason" field set to an appropriate error code.

[0514] As an alternative exemplary embodiment, the mobile or the allocator can send a request message to the other party indicating the start of the safety checkout operation (S408), and the other party can respond to the request message of the safety checkout operation (S408) within a predetermined time interval.

[0515] According to an example embodiment of the present disclosure, when a non-safety critical error is found in the monitoring and control operation (S407) and the fuel filling is interrupted before completion, the fuel filling protocol can define a fallback mechanism that ensures downward compatibility among the compatible mechanisms between the mobile body and the dispenser, and the fuel filling to be completed can be resumed based on the fallback mechanism.

[0516] For example, the fallback mechanism can be a non-communication fuel filling method.

[0517] As an alternative example embodiment, when a non-safety critical error is found in the monitoring and control operation (S407) and the fuel filling is interrupted before completion, the mobile body and the dispenser can perform some or all of the communication protocol negotiation operation (S403), the fuel filling protocol negotiation operation (S404), and the fuel filling parameter negotiation operation (S405) again.

[0518] As an alternative example embodiment, the mobile body and the dispenser can reduce the amount of information exchanged in the process of re-executing some or all of the communication protocol negotiation operation (S403), the fuel filling protocol negotiation operation (S404), and the fuel filling parameter negotiation operation (S405) by using the interoperability information obtained in the discovery and pairing operation (S401). For example, when it is determined that the communication state or the fuel filling state does not allow the previously negotiated and selected protocol to be maintained, some or all of the communication protocol negotiation operation (S403), the fuel filling protocol negotiation operation (S404), and / or the fuel filling parameter negotiation operation (S405) can be performed again, excluding the previously selected protocol.

[0519] As an alternative example embodiment, when a non-safety critical error is detected in the monitoring and control operation (S407), such as a change in the communication environment or the fuel filling infrastructure, and the fuel filling is interrupted before completion, the mobile body and the dispenser can perform some or all of the communication protocol negotiation operation (S403), the fuel filling protocol negotiation operation (S404), and the fuel filling parameter negotiation operation (S405) again.

[0520] The change in the communication environment can include a case where the communication channel is disconnected.

[0521] The change in the communication environment can include a case where the received data cannot be identified, or a case where the received data is in an unacceptable range.

[0522] The change in the communication environment can include a case where the quality of the communication performance does not satisfy / achieve a required level.

[0523] The change in the communication environment can include a case where the integrity or accuracy of the data exchanged via the communication does not satisfy / achieve a required level.

[0524] The change in the fuel filling infrastructure can include a case where the fuel filling parameters on the mobile body side are changed or maintained based on the control parameters for fuel filling on the dispenser side, but such change or maintenance of the fuel filling-related parameters on the mobile body side does not satisfy a required level.

[0525] Some safety conditions checked or monitored in the safety check-in operation (S406), the monitoring and control operation (S407), and / or the safety check-out operation (S408) are shown in Table 19, but the following can be additionally or complementarily considered.

[0526] The safety conditions can include elements related to safety of the mobile body and the hydrogen filling station or dispenser for hydrogen filling (fuel filling), and / or elements related to connection state of the nozzles and the sockets on both sides for starting hydrogen fuel filling.

[0527] On the hydrogen mobile body side, the pressure and temperature in the hydrogen tank can also be included.

[0528] On the hydrogen fuel filling station side, the temperature in the cylinder, the filling pressure, and the ambient temperature can be included.

[0529] As the connection between both sides and the safety conditions on the fuel filling path, the nozzle-socket connection state, i.e., whether connected, connection state, and leakage state can be included.

[0530] The nozzle-socket connection state can include information related to whether the state is suitable and / or sufficient to perform the hydrogen fuel filling process.

[0531] In an alternative exemplary embodiment of the Figure 4 When the safety check-in operation (S406) performs checking of safety elements including minimum state confirmation, i.e., whether the nozzles and the sockets are connected, connection state, etc., the safety check-in operation (S406) can be performed before the fuel filling parameter negotiation operation (S405).

[0532] In an alternative exemplary embodiment of the Figure 4 When the safety check-in operation (S406) performs checking of safety elements including minimum state confirmation, i.e., whether the nozzles and the sockets are connected, connection state, etc., the remaining safety elements not checked in the safety check-in operation (S406) can be negotiated and checked in the fuel filling parameter negotiation operation (S405).

[0533] In an alternative exemplary embodiment of the Figure 4 In an alternative example embodiment, when the safety check-in operation (S406) performs a check of safety elements including minimum state confirmation (i.e., whether the nozzle and the receptacle are connected, the state of connection, etc.), the remaining safety elements that are not checked in the safety check-in operation (S406) can be monitored and checked in the monitoring and control operation (S407). The safety elements can be monitored and checked in the monitoring and control operation (S407) regardless of the negotiation and check performed in the fueling parameter negotiation operation (S405).

[0534] In Figure 4 In an alternative example embodiment, a plurality of safety elements including safety elements checked in the safety check-in operation (S406) can be negotiated and checked in the fueling parameter negotiation operation (S405).

[0535] In Figure 4 In an alternative example embodiment, a plurality of safety elements including safety elements checked in the safety check-in operation (S406) can be monitored and checked in the monitoring and control operation (S407). The safety elements can be monitored and checked in the monitoring and control operation (S407) regardless of the negotiation and check performed in the fueling parameter negotiation operation (S405).

[0536] Referring again to Figure 4 When the fueling is successfully completed and optionally all safety conditions are confirmed, a termination use case between the mobile and the dispenser can be performed.

[0537] The objectives, pre-conditions, and post-conditions of the termination operation (S409) can be shown in Table 25 below.

[0538] [Table 25]

[0539]

[0540]

[0541] When the mobile receives a SafetyCheckOutRes message in which the "Result" is set to "Complete" or a FuelLoopRes message in which the "Status" is set to a value prefixed with "Complete" or "Stop" and the safety check-out use case is omitted, the mobile can send a termination request message (e.g., "TerminateReq") to the dispenser.

[0542] Details regarding the termination request message (e.g., "TerminateReq") can be defined in the specification of each fueling protocol. For example, parameters included in the TerminateReq message and exchanged between the mobile and the dispenser can be differently defined depending on the individual fueling protocol.

[0543] Element names included in the TerminateReq message can include tank press, tank temp, amount, soc, reason, etc., and can be shown in Table 26 below. Elements not shown in Table 26 can be specified by the respective fuel dispensing protocol standard, such as ISO 19885-3.

[0544] [Table 26]

[0545]

[0546] When the dispenser receives the TerminateReq message from the mobile, the dispenser can give a response within a predetermined time interval (e.g., MessageResponseTimeout) by a terminate response message (e.g., TerminateRes).

[0547] Details regarding the terminate response message (e.g., TerminateRes) can be defined in the specification of each fuel dispensing protocol. For example, parameters included in the TerminateRes message and exchanged between the mobile and the dispenser can be differently defined depending on the individual fuel dispensing protocol.

[0548] Element names included in the TerminateRes message can include aprr, duration, amount, soc, result, etc., and can be shown in Table 27 below. Elements not shown in Table 27 can be specified by the respective fuel dispensing protocol standard, such as ISO 19885-3.

[0549] [Table 27]

[0550]

[0551] As an alternative exemplary embodiment, a message requesting start of the termination operation (S409) can be transmitted from the mobile or the dispenser to the other party. The other party can perform the termination operation (S409) by giving a response to the message requesting start of the termination operation (S409).

[0552] For successful fuel dispensing, communication is required to provide expected behavior according to the protocol. Fuel dispensing behavior needs to be kept within an acceptable range defined by the fuel dispensing protocol. However, in practice, various abnormal events can occur. Some errors are minor and can be easily handled. However, some errors can be unrecoverable and can hinder the continuation of the fuel dispensing process.

[0553] In this description, the term "error" can refer to an event that can interrupt the ongoing process that occurs during UC1 to UC9 (S401 to S409) or during hydrogen fuel filling.

[0554] In operation S410, conditions for non-safety critical errors, exemplary error conditions, and responses thereto can be defined.

[0555] Referring again to Figure 4 , the goal, preconditions, and postconditions of the error handling operation (S410) can be shown in Table 28 below.

[0556] [Table 28]

[0557]

[0558] Non-safety critical error conditions can include, for example, the following.

[0559] As a communication error, it can include: 1) a case where communication is disconnected; 2) a case where received data cannot be recognized due to an encoding or syntax error; and 3) a case where received data is in an unacceptable range.

[0560] As a system error, it can include a case where the dispenser or mobile body detects a critical system error of itself.

[0561] As a qualitative error, it can include: 1) a case where the communication performance fails to meet a required level; and 2) a case where the quality of data integrity or precision fails to meet a required level.

[0562] When a non-safety critical error occurs and further communication is not possible, the mobile body and the dispenser immediately stop fuel filling, but take safety steps, and stop communication to end the session.

[0563] When a non-safety critical error occurs and fuel filling is interrupted at a point far from completion of fuel filling, a fallback mechanism can be defined, for example, by defining a non-communication fuel filling method.

[0564] When the mobile body detects a non-safety critical error and the communication channel is still running, the mobile body can transmit a TerminateReq message in which "action" is set to "stop" and "reason" is set to an appropriate reason code.

[0565] When the dispenser detects a non-safety critical error and the communication channel is still running, the dispenser can first immediately stop fuel filling, and then transmit a TerminateReq message in which "action" is set to "stop" and "reason" is set to an appropriate reason code.

[0566] The fuel dispensing protocol can define error conditions according to the protocol and can provide prescribed response procedures including detection criteria, notifications, termination procedures, and fallback mechanisms.

[0567] Referring again to Figure 4 , the objectives, preconditions, and postconditions of the emergency handling operation (S411) can be shown in Table 29 below.

[0568] [Table 29]

[0569]

[0570] The fuel dispensing protocol can define emergency situations according to the protocol and can provide prescribed response procedures to avoid entering a dangerous situation by all means, including detection criteria, notifications, termination procedures, and fallback mechanisms.

[0571] When a mobile body or dispenser detects a safety critical situation, the necessary actions to prevent a catastrophic event can be immediately performed. In addition, if possible, an EmergencyNotif message can be sent with information about the event, and the communication can be closed.

[0572] When a mobile body or dispenser receives an EmergencyNotif message, the mobile body or dispenser can immediately respond to the actions indicated in the message and can close the communication without undue delay.

[0573] Depending on the communication technology used, the EmergencyNotif message can be a TLS or DTLS message.

[0574] For the criticality of the message and the efficiency of the transmission, the fuel dispensing protocol can not allow the structure of the EmergencyNotif message to be modified.

[0575] The element names included in the EmergencyNotif message can include levels, types, actions, etc., and can be shown in Table 30 below. Elements not shown in Table 30 can be specified, for example, by each fuel dispensing protocol specification such as ISO 19885-3. For example, each protocol can specify additional emergency reason codes and action codes.

[0576] [Table 30]

[0577]

[0578] Figure 17 is an operational flowchart showing a communication method for hydrogen fuel dispensing according to an exemplary embodiment of the present disclosure.

[0579] Figure 18 is an operation flowchart showing a communication method for hydrogen fuel refilling according to another exemplary embodiment of the present disclosure.

[0580] As Figure 18 illustrated, the relationship between operations S401 to S409 of Figure 4 and operations S2010 to S2030 of Figure 17 is shown.

[0581] As Figure 4 , Figure 17 and Figure 18 illustrated, the communication method for hydrogen fuel refilling performed by the communication device of the hydrogen fuel mobile body according to the exemplary embodiment of the present disclosure can include detecting an error occurring in a communication process for preparing hydrogen fuel refilling (operations S403 to S406 or operations S408 to S409) between the mobile body and the dispenser supplying hydrogen to the mobile body or in a process in which the dispenser supplies hydrogen to the mobile body (operation S407) (operation S2010; this can be performed as part of operations S403 to S409), determining whether to stop the communication process (operations S403 to S406 or operations S408 to S409) or the hydrogen fuel refilling process (operation S407) with respect to the detected error (operation S2020; this can be performed as part of operations S410 or S411), and performing a subsequent process defined based on the detected error (operation S2030; this can be performed as part of operations S403 to S411).

[0582] The following exemplary embodiments can be performed in operation S401 of Figure 4 based on interoperability or compatibility information shared between the mobile body and the dispenser. In particular, in operations S403 to S405, negotiation and determination of a communication protocol, a fuel refilling protocol, and fuel refilling parameters can be performed within the scope of the interoperability or compatibility information.

[0583] The interoperability or compatibility information is identified and shared in operation S410, but can be re-identified and shared in an updated state according to the current situation in the subsequent process.

[0584] In the communication method for hydrogen fuel refilling performed by the communication device of the mobile body according to the exemplary embodiment of the present disclosure, the determination of whether to stop the communication process or the hydrogen fuel refilling process with respect to the detected error (operation S2020, which can be performed as part of operations S410 or S411) can include classifying the detected error as a safety-critical error or a non-safety-critical error.

[0585] The following exemplary embodiments can be performed by Figure 17 and Figure 18 the operation S2020 in FIG. 20 performs a process of classifying the detected error as a safety critical error, and can be performed as part of the operation S411 in FIG. 41. Figure 4 the operation S411 in FIG. 41. When the detected error is classified as a safety critical error, the execution of the subsequent process can be performed by the operation S411 in FIG. 41. Figure 17 the operation S2030 in FIG. 20 is performed, and can also be performed as part of the operation S411 in FIG. 41. The error classified as a safety critical error can be considered as an emergency. Figure 18 the operation S2030 in FIG. 20 is performed, and can also be performed as part of the operation S411 in FIG. 41. The error classified as a safety critical error can be considered as an emergency. Figure 4 the operation S2030 in FIG. 20 is performed, and can also be performed as part of the operation S411 in FIG. 41. The error classified as a safety critical error can be considered as an emergency.

[0586] In the communication method for hydrogen fuel filling performed by the communication device of the mobile body according to the example embodiment of the present disclosure, the determination of whether to stop the communication process or the hydrogen fuel filling process with respect to the detected error (operation S2020) can further include classifying the detected error as any one of a communication error, a system error, and a qualitative error when the detected error is a non-safety critical error (performed as part of the operation S410).

[0587] In the communication method for hydrogen fuel filling performed by the communication device of the mobile body according to the example embodiment of the present disclosure, the execution of the subsequent process defined based on the detected error when the detected error is a safety critical error (operation S2030) can include at least a part of an emergency handling process (operation S411).

[0588] In the communication method for hydrogen fuel filling performed by the communication device of the mobile body according to the example embodiment of the present disclosure, the determination of whether to stop the communication process or the hydrogen fuel filling process with respect to the detected error (operation S2020) can further include determining whether to replace a first fuel filling protocol of the communication process or the hydrogen fuel filling process with a second fuel filling protocol of a fallback when the detected error is a non-safety critical error.

[0589] In the communication method for hydrogen fuel filling performed by the communication device of the mobile body according to the example embodiment of the present disclosure, the operation of executing the subsequent process defined based on the detected error (operation S2030) can include an operation of transmitting a message including whether to stop the communication process or the hydrogen fuel filling process to the dispenser.

[0590] Various forms of events occurring while the operations S403 to S409 are performed can be detected by the mobile body or the dispenser (operation S2010). The detected events can be classified as errors based on satisfaction of predetermined conditions (operations S2010 and S2020). When the detected error is a non-safety critical error, the error can be processed through the error handling procedure of operation S410 or through operation S2030. When the detected error is a safety critical error, the error can be processed through the emergency handling procedure of operation S411 or through operation S2030.

[0591] In an exemplary embodiment of the present disclosure, the criteria for classifying the detected error as a non-safety critical error or as a safety critical error (emergency) can be predefined through the fueling protocol of operations S403 to S409, and the detected error can be classified through each of operations S403 to S409 upon detection of the error.

[0592] In an alternative exemplary embodiment of the present disclosure, upon detection of an error, the error can be passed to the procedures of operations S410 and / or S411, and each of operations S410 and / or S411 can classify whether the detected error is a non-safety critical error or a safety critical error (emergency). That is, operation S410 can classify whether the error is a non-safety critical error, and when the error is a non-safety critical error, classify whether the error is a communication error, a system error, or a qualitative error. Operation S411 can classify whether the error is a safety critical error.

[0593] Operation S410 can classify the detected error, and can determine whether to stop the fueling process based on the classification result or the state of the error. When it is determined based on the updated interoperability or compatibility information not to stop the fueling process but to continue the fueling process using the fallback fueling protocol, as a result of operation S410, the operations required to continue the fueling process among operations S403 to S409 can be performed again.

[0594] In addition, in operations S410 or S411, when the cause of the error is removed and the normal state is restored, the mobile body or the dispenser can individually or cooperatively return to any one of operations S403 to S409 that has been performed before the error occurred, or enter a subsequent procedure, and can continue the hydrogen fueling process and the communication process.

[0595] The communication method for hydrogen fueling performed by the communication device of the dispenser according to the example embodiment of the present disclosure can include detecting an error occurring in a communication process (operations S403 to S406 or operations S408 to S409) between the dispenser and the mobile body for preparing the hydrogen fueling, or in a process (operation S407) in which the dispenser supplies hydrogen to the mobile body (operation S2010; this can be performed as part of operations S403 to S409), determining whether to stop the communication process (operations S403 to S406 or operations S408 to S409) or the hydrogen fueling process (operation S407) with respect to the detected error (operation S2020; this can be performed as part of operation S410 or S411), and performing a subsequent process defined based on the detected error (operation S2030; this can be performed as part of operations S403 to S411).

[0596] In the communication method for hydrogen fueling performed by the communication device of the dispenser according to the example embodiment of the present disclosure, the determining whether to stop the communication process or the hydrogen fueling process with respect to the detected error (operation S2020; this can be performed as part of operation S410 or S411) can include classifying the detected error as a safety critical error or a non-safety critical error.

[0597] In the communication method for hydrogen fueling performed by the communication device of the dispenser according to the example embodiment of the present disclosure, the determining whether to stop the communication process or the hydrogen fueling process with respect to the detected error (operation S2020) can further include, when the detected error is a non-safety critical error, classifying the detected error as any one of a communication error, a system error, and a qualitative error (this can be performed as part of operation S410).

[0598] In the communication method for hydrogen fueling performed by the communication device of the dispenser according to the example embodiment of the present disclosure, the performing a subsequent process defined based on the detected error when the detected error is a safety critical error (operation S2030) can include at least a part of an emergency handling process (operation S411).

[0599] In the communication method for hydrogen fueling performed by the communication device of the dispenser according to the example embodiment of the present disclosure, the determining whether to stop the communication process or the hydrogen fueling process with respect to the detected error (operation S2020) can further include, when the detected error is a non-safety critical error, determining whether to replace a first fueling protocol of the communication process or the hydrogen fueling process with a second fueling protocol of a fallback.

[0600] In a communication method for hydrogen refueling performed by a communication device of a dispenser according to an exemplary embodiment of the present disclosure, executing a subsequent process defined based on a detected error may include: when a second refueling protocol is utilized instead of a first refueling protocol of a communication process or a hydrogen refueling process, executing the hydrogen refueling process based on the second refueling protocol.

[0601] In the event of a communication error, the dispenser may select a second fueling protocol based on the first fueling protocol or predefined rules by applying a predefined fallback, and may perform hydrogen fueling based on the second fueling protocol.

[0602] In the event of a communication error, the mobile or distributor can stop the session as needed.

[0603] In the event of a system error, the mobile or distributor can stop the session as needed. The mobile or distributor can stop the session based on the detected error and send a message to the other party including the stop action and a reason code corresponding to the reason.

[0604] In an alternative embodiment, in the event of a qualitative error, a fallback fueling protocol based on a limited communication protocol or communication environment may be selected based on updated interoperability or compatibility information between the mobile body and the dispenser, and hydrogen fueling may be performed based on the selected fueling protocol.

[0605] In an alternative embodiment, in case of a qualitative error, another fueling protocol may be selected while maintaining the communication protocol between the mobile body and the dispenser. In another alternative embodiment, another communication protocol may be selected while maintaining the fueling protocol between the mobile body and the dispenser.

[0606] In an alternative embodiment, in the event of a qualitative error, a renegotiation may be performed between the mobile body and the dispenser to select a new combination of the communication protocol and the fueling protocol. In such a case, for renegotiation, operations S403 to S405 may be performed again, or renegotiation may be performed within operation S410.

[0607] In an alternative embodiment, even in an emergency, when communications are still available, subsequent processes can be performed while minimizing communications.The mobile or dispenser can fall back on the communications protocol and the fueling protocol.

[0608] In an alternative embodiment, in an emergency situation, fueling and communications may be prioritized over stopping.

[0609] In the communication method for hydrogen fuel filling performed by the communication device of the dispenser according to the exemplary embodiment of the present disclosure, the performing of the subsequent procedure defined based on the detected error can include transmitting a message including whether to stop the communication procedure or the hydrogen fuel filling procedure to the mobile body.

[0610] In the communication method for hydrogen fuel filling performed by the communication device of the dispenser according to the exemplary embodiment of the present disclosure, when the message including whether to stop the communication procedure or the hydrogen fuel filling procedure includes a stop instruction, the message can further include a cause code corresponding to an appropriate cause of the stop.

[0611] In the communication method for hydrogen fuel filling performed by the communication device of the mobile body and / or the dispenser according to an alternative embodiment of the present disclosure, the criticality of the error can be determined based on the UCDC level of the available communication or fuel filling procedure related to the detected error. In addition, whether to stop the fuel filling can be determined based on the UCDC level. The procedure of determining the criticality of the error and / or whether to stop the fuel filling based on the UCDC level can be applied in the case where the error is a qualitative error. However, such an embodiment does not limit the scope of the present disclosure.

[0612] In Figure 4 and Figure 18 In the exemplary embodiments of Figure 4 and Figure 18 , examples related to operations S403 to S409 for operating S2010, S2020, S410, and / or S411 have been shown. In an alternative embodiment of the present disclosure, operations S2010 and S2020 can detect any event occurring in operations S401 to S409 or in the fuel filling procedure, determine whether the event is an error, and classify the error. In addition, in an alternative embodiment of the present disclosure, as part of operations S2010, S2020, and S2030, after operations S410 and S411 are performed, a subsequent procedure can be performed, or when the error is resolved, any one of operations S401 to S409 can be returned to perform an existing procedure and / or a next procedure.

[0613] That is, operations S2010 and S2020 can detect an event, determine whether the event is an error, detect or classify an error occurring in operations S401-UC1: Discovery and Pairing, S402-UC2: Communication Security, S403-UC3: Communication Protocol Negotiation, S404-UC4: Fuel Filling Protocol Negotiation, S405-UC5: Fuel Filling Parameter Negotiation, S406-UC6: Security Check-in, S407-UC7: Fuel Filling Control and Monitoring, S408-UC8: Security Check-out, S409-UC9: Termination, or in a parallel hydrogen fuel filling procedure.

[0614] In addition, after classification and handling of the error in operation S2030, S410, or S411, it is possible to return to operations S401 to S409 or a parallel hydrogen fuel filling process.

[0615] In addition, after handling and resolving the error, it is possible to return to the process being executed before the error occurred or to proceed to the next process, such as operations S401 to S409 or a parallel hydrogen fuel filling process.

[0616] In an alternative embodiment, as a criterion for determining whether the error is safety critical, it is possible to consider whether an event that can occur before, during, or after hydrogen fuel filling causes harm to facilities and / or human life, or causes a fire, explosion, leakage, etc.

[0617] In some cases, a safety critical error can cause communication and fuel filling to stop and / or terminate. In an alternative embodiment, even in the case of a safety critical error, fuel filling can continue when communication is safe or fuel filling is feasible, or when fuel filling is required to continue for reasons such as evacuation from a dangerous place or transportation of a patient.

[0618] In the case of a non-safety critical error, based on the criticality or severity of the error, the available communication environment, the available fuel filling protocol, the UCDC level, and the necessity of communication or fuel filling, communication or fuel filling can be stopped, or communication or fuel filling can be continued.

[0619] In the above exemplary embodiments, constant monitoring of interoperability, updating of interoperability information, and / or updating of a communication / fuel filling protocol combination have been mainly described in the context of being performed by a mobile body or a dispenser. However, it is obvious that these detailed processes can be performed by a mobile body or a dispenser, or through cooperation between a mobile body and a dispenser. In an alternative embodiment of the present disclosure, part of constant monitoring of interoperability, updating of interoperability information, and / or updating of a communication / fuel filling protocol combination can be guided by a mobile body, and the other part can be guided by a dispenser.

[0620] In addition, detection of an error can be performed by a mobile body or a dispenser, and an entity that has detected an error can transmit a message including detection of an error, a detected error, stop of communication or fuel filling based on the error, or a cause code corresponding to a stop cause to the other party.

[0621] Figure 16 is a schematic block diagram showing a physical configuration of a general computing system according to an example embodiment of the present disclosure, which can operate as a communication device, a communication controller, and / or an electronic controller for hydrogen fuel filling, and which can be installed on a hydrogen fuel mobile body, a dispenser, and / or a fuel filling station.

[0622] Although not shown in Figures 1 to 15 , the processor and the memory can be electrically connected to each of the components, so that the operation of each of the components can be controlled or managed by the processor.

[0623] At least some of the processes of the fuel filling communication method according to an example embodiment of the present disclosure can be executed by Figure 16 Figure 16 the computing system 3000.

[0624] The computing system 3000 according to an example embodiment of the present disclosure can include at least one processor 3100 and a memory 3200 storing program instructions instructing the at least one processor 3100 to execute at least one process step. At least some of the operations or process steps of the method according to an example embodiment of the present disclosure can be executed by the at least one processor 3100 loading the program instructions from the memory 3200.

[0625] The processor 3100 executing the program instructions or commands stored in the memory 3200 can include a central processing unit (CPU) or a graphics processing unit (GPU), or can be implemented by another dedicated processor suitable for executing the method of the present disclosure.

[0626] Each of the memory 3200 and the storage 3400 can include one or more of a volatile storage medium or a non-volatile storage medium. For example, the memory 3200 can include one or more of a read-only memory (ROM) or a random access memory (RAM).

[0627] In addition, the computing system 3000 can include a communication interface 3300 performing communication through a wireless communication network.

[0628] Furthermore, the computing system 3000 can further include a storage 3400, an input interface 3500, and an output interface 3600.

[0629] The components of the computing system 3000 can be connected to each other by a system bus 3700 to communicate with each other.

[0630] The device including the processor 3100 according to the example embodiments of the disclosure can be any data processing device capable of communicating over a network, such as a desktop computer, a laptop computer, a notebook PC, a smart phone, a tablet PC, a mobile phone, a smart watch, smart glasses, an e-book reader, a portable multimedia player (PMP), a portable game machine, a navigation device, a digital camera, a digital multimedia broadcasting (DMB) player, a digital audio recorder, a digital audio player, a digital video recorder, a digital video player, and a personal digital assistant (PDA).

[0631] The communication device / equipment for hydrogen fuel refilling according to the example embodiments of the disclosure is installed on a hydrogen fuel mobile body and / or a dispenser to perform communication between the hydrogen fuel mobile body and the dispenser, and can include a processor 3100 that receives at least one instruction from a memory 3200 and executes the at least one instruction.

[0632] The communication control device / equipment of the hydrogen fuel mobile body 100 according to the example embodiments of the disclosure can include a memory 3200 that stores at least one instruction and a processor 3100 that executes the at least one instruction. Through the at least one instruction, the processor 3100 can detect an error occurring in a communication process for preparing hydrogen fuel refilling between a mobile body and a dispenser that supplies hydrogen to the mobile body, or in a hydrogen fuel refilling process from the dispenser to the mobile body, determine whether to stop the communication process or the hydrogen fuel refilling process with respect to the detected error, and perform a subsequent process defined based on the detected error.

[0633] The processor 3100 can classify the detected error as a safety-critical error or a non-safety-critical error when determining whether to stop the communication process or the hydrogen fuel refilling process with respect to the detected error.

[0634] The processor 3100 can classify the detected error as any one of a communication error, a system error, and a qualitative error based on the detected error being a non-safety-critical error when determining whether to stop the communication process or the hydrogen fuel refilling process with respect to the detected error.

[0635] The processor 3100 performs an emergency handling process based on the detected error being a safety-critical error when performing the subsequent process defined based on the detected error.

[0636] The processor 3100 can determine whether to replace a first fuel refilling protocol of the communication process or the hydrogen fuel refilling process with a second fuel refilling protocol using a fallback based on the detected error being a non-safety-critical error when determining whether to stop the communication process or the hydrogen fuel refilling process with respect to the detected error.

[0637] The processor 3100 can transmit a message including whether to stop the communication process or the hydrogen fuel filling process to the dispenser while performing a subsequent process defined based on the detected error.

[0638] A communication device of a dispenser for supplying hydrogen to a hydrogen fuel moving body according to an exemplary embodiment of the present disclosure can include a memory storing at least one instruction, and a processor executing the at least one instruction. Through the at least one instruction, the processor can detect an error occurring in a communication process for preparing hydrogen fuel filling between the dispenser and the moving body, or in a hydrogen fuel filling process from the dispenser to the moving body, determine whether to stop the communication process or the hydrogen fuel filling process with respect to the detected error, and perform a subsequent process defined based on the detected error.

[0639] On the other hand, although most of the embodiments described above focus on a method in which the moving body first transmits a communication protocol or parameter to the dispenser, the present disclosure is not limited thereto, and can be configured such that the dispenser first transmits a communication protocol or parameter of the dispenser to the moving body. Such an embodiment has substantially the same features as the above-described embodiments, except for a change in the transmitter and the receiver.

[0640] The devices and methods according to exemplary embodiments of the present disclosure can be implemented by computer-readable program codes or instructions stored on a computer-readable non-transitory recording medium. The computer-readable recording medium includes all types of recording devices storing data that can be read by a computer system. The computer-readable recording medium can be distributed over a computer system connected through a network, so that the computer-readable program or code can be stored and executed in a distributed manner.

[0641] The computer-readable recording medium can include hardware devices specially configured to store and execute program instructions, such as ROM, RAM, and flash memory. The program instructions can include not only machine language codes generated by a compiler, but also high-level language codes executable by a computer using an interpreter, etc.

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

[0643] In some example embodiments, a programmable logic device, such as a field programmable gate array, can be used to perform some or all of the functionalities of the methods described herein. In some example embodiments, a field programmable gate array can be utilized using a microprocessor in order to perform one of the methods described herein. Generally, the methods are preferably performed by a specific hardware device.

[0644] The description of the present disclosure is merely exemplary in nature and, thus, variations that do not depart from the essence of the present disclosure are intended to be within the scope of the present disclosure. Such variations are not to be regarded as a departure from the spirit and scope of the present disclosure. From the foregoing, it will be appreciated that, in accordance with the present disclosure, various changes in form and detail can be made without departing from the spirit and scope of the disclosure which is defined by the following claims.< / ok> < / ok>

Claims

1. A communication method for hydrogen fuel filling (fuel filling) performed by a hydrogen fuel mobile body, comprising: detecting an error occurring in a communication process between a mobile body and a dispenser supplying hydrogen to the mobile body for preparing hydrogen fuel filling, or in a hydrogen fuel filling process from the dispenser to the mobile body; determining whether to stop (stop) the communication process or the hydrogen fuel filling process for the detected error; and performing a subsequent process defined based on the detected error.

2. The communication method for hydrogen fuel filling according to claim 1, wherein, the determining whether to stop the communication process or the hydrogen fuel filling process for the detected error comprises: classifying the detected error as a safety critical error (safety critical error) or a non-safety critical error (non-safety critical error).

3. The communication method for hydrogen fuel filling according to claim 2, wherein the determining whether to stop the communication process or the hydrogen fuel filling process for the detected error further comprises: based on the detected error being the non-safety critical error, classifying the detected error as any one of a communication error, a system error, and a qualitative error (qualitative error).

4. The communication method for hydrogen fuel filling according to claim 2, wherein the performing a subsequent process defined based on the detected error comprises: based on the detected error being the safety critical error, performing an emergency handling process.

5. The communication method for hydrogen fuel filling according to claim 2, in, the determining whether to stop the communication process or the hydrogen fuel filling process for the detected error further comprises: based on the detected error being the non-safety critical error, determining whether to replace a first fuel filling protocol of the communication process or the hydrogen fuel filling process with a second fuel filling protocol with a fallback.

6. The communication method for hydrogen fuel filling according to claim 1, wherein the performing a subsequent process defined based on the detected error comprises: sending a message including whether to stop the communication process or the hydrogen fuel filling process to the dispenser.

7. A communication device for hydrogen fuel filling, the communication device being arranged in a hydrogen fuel mobile body, the communication device comprising: a memory storing at least one instruction; and a processor executing the at least one instruction, wherein the processor is configured to: detect an error occurring in a communication process between a mobile body and a dispenser supplying hydrogen to the mobile body for preparing hydrogen fuel filling, or in a hydrogen fuel filling process from the dispenser to the mobile body, determine whether to stop (stop) the communication process or the hydrogen fuel filling process for the detected error, and perform a subsequent process defined based on the detected error.

8. The communication device according to claim 7, wherein The processor is further configured to, in the determining whether to stop the communication process or the hydrogen fuel filling process for the detected error, classify the detected error as a safety critical error (safety critical error) or a non-safety critical error (non-safety critical error).

9. The communication device according to claim 8, wherein, The processor is further configured to, in the determining whether to stop the communication process or the hydrogen fuel filling process for the detected error, classify the detected error as any one of a communication error, a system error, and a qualitative error (qualitative error) based on the detected error being the non-safety critical error.

10. The communication device according to claim 8, wherein, The processor is further configured to, in the executing the subsequent process defined based on the detected error, execute an emergency handling process based on the detected error being the safety critical error.

11. The communication device according to claim 8, wherein The processor is further configured to, in the determining whether to stop the communication process or the hydrogen fuel filling process for the detected error, determine whether to replace a first fuel filling protocol of the communication process or the hydrogen fuel filling process with a second fuel filling protocol of a fallback based on the detected error being the non-safety critical error.

12. The communication device according to claim 7, wherein, The processor is further configured to, in the executing the subsequent process defined based on the detected error, transmit a message including whether to stop the communication process or the hydrogen fuel filling process to the dispenser.

13. A communication method for hydrogen fuel filling (fuel filling) executed by a communication device of a dispenser that supplies hydrogen to a hydrogen fuel mobile body, comprising: detecting an error that occurs in a communication process between the dispenser and a mobile body for preparing hydrogen fuel filling, or in a hydrogen fuel filling process from the dispenser to the mobile body; determining whether to stop (stop) the communication process or the hydrogen fuel filling process for the detected error; and executing a subsequent process defined based on the detected error.

14. The communication method for hydrogen fuel filling according to claim 13, in, The determining whether to stop the communication process or the hydrogen fuel filling process for the detected error includes: classifying the detected error as a safety critical error (safety critical error) or a non-safety critical error (non-safety critical error).

15. The communication method for hydrogen fuel filling according to claim 14, wherein The determining whether to stop the communication process or the hydrogen fuel filling process for the detected error further includes: classifying the detected error as any one of a communication error, a system error, and a qualitative error (qualitative error) based on the detected error being the non-safety critical error.

16. The communication method for hydrogen fuel filling according to claim 14, wherein The executing the subsequent process defined based on the detected error includes: executing an emergency handling process based on the detected error being the safety critical error.

17. The communication method for hydrogen fuel filling according to claim 14, wherein, the determining whether to stop the communication process or the hydrogen fuel filling process based on the detected error further comprises: based on the detected error being the non-safety critical error, determining whether to replace a first fuel filling protocol of the communication process or the hydrogen fuel filling process with a second fuel filling protocol that is a fallback.

18. The communication method for hydrogen fuel filling according to claim 17, wherein the performing a subsequent process defined based on the detected error comprises: based on replacing the first fuel filling protocol of the communication process or the hydrogen fuel filling process with the second fuel filling protocol, performing the hydrogen fuel filling process based on the second fuel filling protocol.

19. The communication method for hydrogen fuel filling according to claim 13, wherein, the performing a subsequent process defined based on the detected error comprises: sending a message to the mobile body including whether to stop the communication process or the hydrogen fuel filling process.

20. The communication method for hydrogen fuel filling according to claim 19, wherein based on the message including whether to stop the communication process or the hydrogen fuel filling process including stop, the message further includes a code corresponding to a reason for the stop.

Images