Communication method and apparatus for monitoring and controlling hydrogen fueling

Abstract

A method according to one embodiment of the present invention comprises the steps of: transmitting, by a moving body, a request message including information related to an action including starting or stopping hydrogen fuel supply to a dispenser on the basis of a fuel supply protocol determined by negotiation between the dispenser and the moving body; and receiving a response message from the dispenser, the response message including information about whether the moving body has processed or is ready to process the action included in the request message.

Description

Technical Field

[0001] The present disclosure relates to a communication technology for refueling a hydrogen fuel mobile body with hydrogen, and more particularly to a hydrogen refueling process for enhancing the safety, compatibility, efficiency, and reliability of hydrogen refueling, a monitoring and control method for the hydrogen refueling process, a safety check-in method, and an apparatus for implementing the process. Background Art

[0002] The description in this section merely provides background information for embodiments of the present disclosure and is not intended to indicate prior art with respect to the present disclosure.

[0003] A hydrogen vehicle or hydrogen electric vehicle refers to a vehicle that is driven by electricity generated by the reaction of high-pressure hydrogen stored in the vehicle with oxygen in the air, and produces very little pollution. Most hydrogen electric vehicles are driven by electricity generated by a fuel cell system that uses hydrogen as an energy source. Hydrogen electric vehicles not only emit pure water (H2O) vapor during the power generation process, but also remove ultrafine dust from the air while driving, and therefore attract attention as future environmentally friendly mobile bodies. Since the fuel (i.e., hydrogen) is abundant on the earth and the energy production process is environmentally friendly, hydrogen electric vehicles have received widespread attention as a technology with the potential to be applied to the entire industry.

[0004] A hydrogen-fueled mobile object refers to a mobile object that uses hydrogen as an energy source or uses hydrogen as fuel to generate electricity and then drives an electric motor with this electricity. In addition to the hydrogen-electric vehicles mentioned above, hydrogen-fueled mobile objects can include aerial mobile objects as well as industrial trucks, trains, ships, and aircraft that use hydrogen as fuel to generate electricity and are driven by this electricity.

[0005] Hydrogen-electric vehicles generate electricity by supplying high-pressure hydrogen safely stored in hydrogen fuel tanks and oxygen introduced through an air supply system to a fuel cell stack, where the hydrogen and oxygen undergo an electrochemical reaction. The electricity generated in the fuel cell stack is converted to kinetic energy by a motor to power the hydrogen-electric vehicle. The operating hydrogen-electric vehicle then emits only pure water vapor through its exhaust port.

[0006] Hydrogen fuel cell vehicles, in addition to hydrogen electric vehicles, are also vehicles that use hydrogen as fuel. These hydrogen fuel cell vehicles are powered by an electric motor that rotates using the heat generated by the direct combustion of hydrogen in the engine. The method for refueling / supplying hydrogen to hydrogen fuel cell vehicles is not much different from that used for hydrogen electric vehicles.

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

[0008] The hydrogen fuel filling / supply process, control scheme, and its protocols in conventional hydrogen electric vehicles were developed before the wired / wireless communication or computing technology for control became mature, and therefore did not take advantage of the latest information and communication technology (ICT) to their full extent. As a result, the conventional hydrogen fuel filling / supply subsystem in hydrogen electric vehicles is inefficient, slow, and unsuitable for large-scale hydrogen fuel filling.

[0009] In particular, regarding hydrogen fuel filling communication, most hydrogen fuel filling control devices use one-way infrared communication devices for wireless communication, and therefore still have the limitations and weaknesses of one-way communication. Summary of the Invention

[0010] Technical issues

[0011] To address the aforementioned issues, an exemplary embodiment provides a hydrogen refueling process and a communication protocol for a refueling protocol for the process; a method for negotiating a communication protocol, a refueling protocol, and refueling parameters for the hydrogen refueling process; a monitoring and control method; a security check-in method; a security check-out method; and an apparatus for implementing the process. The hydrogen refueling process and the communication protocol for the refueling protocol for the process overcome the limitations and weaknesses of conventional one-way communication during the refueling process of a hydrogen fuel mobile object and enhance the safety, compatibility, efficiency, and reliability of hydrogen refueling. Another exemplary embodiment provides a process for hydrogen refueling that allows for bidirectional communication for hydrogen refueling of a hydrogen fuel mobile object; a control for determining whether a conventional communication medium or an advanced communication medium is used to effectively achieve hydrogen refueling goals; a communication protocol negotiation process that takes into account bidirectional / unidirectional communication; and an apparatus for implementing the process.

[0012] Technical Solution

[0013] According to one aspect of an exemplary embodiment, a communication method for hydrogen fuel refueling performed by a hydrogen fuel mobile object includes: sending a request message to a dispenser that supplies hydrogen, based on a fuel refueling protocol determined through negotiation between the hydrogen fuel mobile object and the dispenser, the request message including information related to an operation including starting or stopping hydrogen fuel refueling; and receiving a response message from the dispenser, the response message including information regarding whether the operation included in the request message has been processed or is ready to be processed.

[0014] The request message may include information related to the start of hydrogen fueling. The response message may include information regarding whether the dispenser is ready to start hydrogen fueling.

[0015] The communication method for hydrogen fueling may further include: based on the response message indicating that the dispenser is not ready to start hydrogen fueling, additionally transmitting a second request message including information related to a start operation of hydrogen fueling.

[0016] The request message may include information related to the stop operation of hydrogen fuel filling. The response message may include information on whether the dispenser stops hydrogen fuel filling.

[0017] The communication method for hydrogen fueling may further include: additionally transmitting a second request message including information related to a stop operation of hydrogen fueling based on the response message indicating that the dispenser has not completely stopped hydrogen fueling.

[0018] The request message may include a request for monitoring of at least one status related to the hydrogen fueling process. The response message may include information about the at least one status.

[0019] The communication method for hydrogen fuel refueling may further include: in a state where fuel refueling parameters based on a fuel refueling protocol are negotiated between the hydrogen fuel mobile object and the dispenser, before sending a request message, checking a security status on the hydrogen fuel mobile object side or the dispenser side by exchanging messages between the hydrogen fuel mobile object and the dispenser.

[0020] The communication method for hydrogen fuel refueling may further include checking a safety state on the hydrogen fuel mobile body side or the dispenser side by exchanging messages between the hydrogen fuel mobile body and the dispenser before the nozzle is pulled out based on the response message indicating that hydrogen fuel refueling has been completed or stopped.

[0021] According to another aspect of the exemplary embodiment, a communication device for hydrogen fuel refueling is provided in a mobile hydrogen fuel supply unit. The communication device includes a memory storing at least one instruction and a processor executing the at least one instruction. When executing the at least one instruction, the processor is configured to: send a request message to a dispenser supplying hydrogen based on a fuel refueling protocol determined through negotiation between the mobile hydrogen fuel supply unit and the dispenser, the request message including information related to an operation including starting or stopping hydrogen fuel refueling; and receive a response message from the dispenser including information regarding whether the operation included in the request message has been processed or is ready to be processed.

[0022] The request message may include information related to the start of hydrogen fueling. The response message may include information regarding whether the dispenser is ready to start hydrogen fueling.

[0023] Based on the response message indicating that the dispenser is not ready to begin hydrogen refueling, the processor may additionally send a second request message including information related to the initiation of hydrogen refueling.

[0024] The request message may include information related to the stop operation of hydrogen fuel filling. The response message may include information on whether the dispenser stops hydrogen fuel filling.

[0025] Based on the response message indicating that the dispenser has not completely stopped hydrogen fueling, the processor may additionally send a second request message including information related to the stopping operation of hydrogen fueling.

[0026] The request message may include a request for monitoring at least one status related to the hydrogen fueling process. The response message may include information about the at least one status.

[0027] In a state where fuel filling parameters based on the fuel filling protocol are negotiated between the hydrogen fuel mobile object and the dispenser, the processor can check the security status of the hydrogen fuel mobile object or the dispenser by exchanging messages between the hydrogen fuel mobile object and the dispenser before sending a request message.

[0028] Based on the response message indicating that hydrogen fuel filling has been completed or stopped, the processor may check the safety status of the hydrogen fuel mobile body or the dispenser by exchanging messages between the hydrogen fuel mobile body and the dispenser before the nozzle is pulled out.

[0029] According to another aspect of the exemplary embodiment, a communication device for hydrogen refueling is provided in a dispenser that supplies hydrogen to a hydrogen fuel mobile device. The communication device includes a memory storing at least one instruction and a processor executing the at least one instruction. When executing the at least one instruction, the processor is configured to: receive a request message from the hydrogen fuel mobile device after a fuel refueling protocol negotiation between the hydrogen fuel mobile device and the dispenser is complete, the request message including information related to an operation including starting or stopping hydrogen refueling; and transmit a response message to the hydrogen fuel mobile device, the response message including information regarding whether the operation included in the request message has been processed or is ready to be processed.

[0030] According to another aspect of the exemplary embodiment, a communication method for hydrogen fuel refueling performed by a dispenser that supplies hydrogen to a hydrogen fuel mobile object includes: receiving a request message from the hydrogen fuel mobile object in a state in which a fuel refueling protocol negotiation between the hydrogen fuel mobile object and the dispenser is completed, the request message including information related to an operation including starting or stopping hydrogen refueling; and sending a response message to the hydrogen fuel mobile object, the response message including information regarding whether the operation included in the request message has been processed or is ready to be processed.

[0031] The response message may include information regarding whether the dispenser is currently performing hydrogen fueling or has stopped hydrogen fueling.

[0032] When the response message indicates that the dispenser has stopped hydrogen fueling, the response message may include information about whether the dispenser stopped hydrogen fueling based on a stop operation included in a request message from the hydrogen fuel mobile body, or whether hydrogen fueling was completed because a target for hydrogen fueling of the hydrogen fuel mobile body had been achieved / reached (or whether it was for the reason that a target for hydrogen fueling of the hydrogen fuel mobile body had been achieved / reached).

[0033] The request message may include a request for monitoring at least one status related to the hydrogen fueling process. The response message may include information about the at least one status.

[0034] The communication method for hydrogen fuel refueling may further include: in a state where fuel refueling parameters based on a fuel refueling protocol are negotiated between the hydrogen fuel mobile body and the dispenser, before receiving a request message, checking the safety status of the hydrogen fuel mobile body side or the dispenser side by exchanging messages between the hydrogen fuel mobile body and the dispenser; and based on an indication in the response message that hydrogen fuel refueling has been completed or stopped, checking the safety status of the hydrogen fuel mobile body side or the dispenser side by exchanging messages between the hydrogen fuel mobile body and the dispenser before the nozzle is pulled out.

[0035] Beneficial effects

[0036] According to the communication method for hydrogen fueling and the device for implementing the method, that is, the hydrogen fueling controller or communication controller according to the exemplary embodiment of the present disclosure, the limitations and weaknesses of conventional one-way communication for hydrogen fuel mobile bodies in the hydrogen fueling process and the communication protocol of the fueling protocol used for the process can be overcome, and the safety, compatibility, efficiency and reliability of hydrogen fueling can be enhanced, and the hydrogen fuel mobile body includes a fuel cell electric vehicle (FCEV) or a hydrogen fuel engine.

[0037] Exemplary embodiments of the present disclosure may provide a method for negotiating a communication protocol and exchanging communication parameters for hydrogen refueling, as well as a communication protocol fallback rule, wherein a mobile body and a dispenser may select a hydrogen refueling protocol and a communication protocol required to execute the hydrogen refueling protocol based on a use case, while considering priorities based on the preferences of the mobile body or the dispenser, maximizing interoperability between the mobile body and the dispenser, and taking backward compatibility into consideration.

[0038] Exemplary embodiments of the present disclosure may provide rules and procedures required for communication protocol negotiation, fueling protocol negotiation, and fueling parameter exchange to enable mobiles and dispensers to effectively and collaboratively determine conventional communication media or advanced communication media to effectively achieve hydrogen fueling goals.

[0039] Furthermore, exemplary embodiments of the present disclosure may provide the rules and procedures required for monitoring and control, safety check-in, and safety check-out so that mobile objects and dispensers may collaborate to effectively achieve hydrogen fueling goals.

[0040] Furthermore, exemplary embodiments of the present disclosure may provide the rules and processes required for use cases, wherein the processes of monitoring and control, safety check-in and safety check-out, and communication protocol negotiation, fueling protocol negotiation, and fueling parameter exchange are linked so that mobile bodies and dispensers may collaborate to effectively achieve hydrogen fueling goals. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0043] Figure 3 It shows Figure 1 A graph showing changes in the state of hydrogen fuel occurring during a hydrogen fueling process in a hydrogen fueling system;

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

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

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

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

[0048] Figure 8 is a table outlining an example of backward compatibility suitable for a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure;

[0049] Figure 9 FIG. 1 shows a usage classification of communication data (UCDC) in a two-way communication process for hydrogen fuel refueling and backward compatibility of the usage classification of communication data according to an exemplary embodiment of the present disclosure;

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

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

[0052] Figure 12 is a sequence diagram illustrating a fueling protocol negotiation process during a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure;

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

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

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

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

[0057] In addition to the above-mentioned objects, another object and feature of the present disclosure will become more apparent through the description of exemplary embodiments with reference to the accompanying drawings.

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

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

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

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

[0062] These terms are used herein only for the purpose of describing specific exemplary embodiments and are not intended to limit the present disclosure. Unless the context clearly dictates otherwise, singular forms also include plural referents. Moreover, the expressions "comprises," "includes," "constructed," and "configured" are used to indicate the presence of a recited feature, quantity, processing step, operation, element, or combination of parts, but are not intended to exclude the presence or addition of another feature, quantity, processing step, operation, element, or part.

[0063] 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 the present disclosure belongs. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant literature, and should not be interpreted as having an ideal or overly formal meaning unless explicitly defined in this application.

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

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

[0066] Although embodiments related to hydrogen fuel cell vehicles are described in detail below, another embodiment of the present disclosure may employ an ICE-based hydrogen vehicle that uses hydrogen as fuel. The following description focuses on hydrogen fuel cell vehicles to describe the hydrogen refueling protocol and / or hydrogen refueling communication protocol. However, the hydrogen refueling protocol and / or hydrogen refueling communication protocol may also be applicable to an ICE-based hydrogen vehicle according to another embodiment of the present disclosure.

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

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

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

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

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

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

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

[0074] "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.

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

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

[0077] "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.

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

[0079] "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.

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

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

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

[0083] Furthermore, although the bidirectional communication process for hydrogen refueling is described with respect to a hydrogen electric vehicle (FCEV) for ease of illustration, the present disclosure is not limited thereto, and the bidirectional communication process for hydrogen refueling may also be applied to hybrid electric vehicles (EV) or ICE-based vehicles using hydrogen as fuel.

[0084] In the following description, some or all of the processes of the communication method, communication protocol negotiation method, hydrogen fueling protocol negotiation method, and hydrogen fueling parameter negotiation method performed by the hydrogen fuel mobile object may be performed by the electronic control unit (ECU), communication device, or communication controller of the hydrogen fuel mobile object.

[0085] In the following description, some or all of the processes of the communication method, communication protocol negotiation method, hydrogen fueling protocol negotiation method, hydrogen fueling parameter negotiation method, hydrogen fueling method, and hydrogen fueling control method performed by the dispenser may be performed by the dispenser's controller, electronic control unit, communication device, or communication controller. Alternatively, some of the processes of the aforementioned methods may be performed by a controller, electronic control unit, communication device, or communication controller of a fueling station associated with the dispenser.

[0086] At the same time, if necessary, one or more conventional components may be included in the configuration of the present disclosure, and such components will be described herein to the extent that they do not obscure the technical concepts and ideas of the present disclosure. However, if the description of conventional components may obscure the technical concepts and ideas of the present disclosure, a detailed description of such components may be omitted for simplicity. However, the present disclosure is not intended to claim protection for conventional components, and conventional components may be included as elements of the apparatus or method of the present disclosure without departing from the concept or spirit of the present disclosure.

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

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

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

[0090] refer to Figure 1 The hydrogen fuel filling system may generally be configured to include a hydrogen fuel filling station and a hydrogen fueled mobility 100 .

[0091] In addition to mechanical, electrical, electronic, and communication devices that are fundamental to a vehicle, the hydrogen fuel mobile body 100 may be equipped with an electronic controller 110 for hydrogen fuel refueling, a mobile body system 120 , a mobile body tank 130 , and a receptacle 150 .

[0092] Electronic controller 110 can transmit and receive signals and data to and from a hydrogen fueling station or an electronic controller 210 of the hydrogen fueling station via wired or wireless communication, and process the signals and data to control hydrogen fueling on the vehicle side. Electronic controller 110 can be implemented by at least a portion of another electronic control unit installed in the vehicle and can be referred to as a first electronic controller or electronic control unit #1.

[0093] The mobile system 120 may be connected to the first electronic controller 110 and may be configured to control hydrogen refueling or hydrogen discharge of the mobile tank 130 and monitor the status of the mobile tank 130 based on signals or commands from the first electronic controller 110. The mobile system 120 may include components that control the operation of the fuel cell system or perform such control operations, depending on the implementation, or may be configured in combination with such components. The mobile system 120 may perform vehicle safety functions and may be referred to as a vehicle safety system.

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

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

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

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

[0098] Dispenser 200 can supply hydrogen from hydrogen tank 230 to the vehicle through nozzle 250, which is securely coupled to receptacle 150 of the vehicle, under the control of fuel filling station system 220. Dispenser 200 may include electronic controller 210 within the housing, but the present disclosure is not limited thereto. Nozzle 250 may be mounted at the end of a cable that extends a certain length outside the housing of dispenser 200.

[0099] Electronic controller 210 can transmit and receive signals and data to and from first electronic controller 110 of the vehicle via wired or wireless communication, and process the signals and data to control hydrogen fueling at the hydrogen fueling station. Electronic controller 210 can exchange specified signals and data with fueling station system 220. Electronic controller 210 may also be referred to as a second electronic controller or electronic control unit #2.

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

[0101] The fuel filling station system 220 can monitor or control the pressure, rate, and temperature of hydrogen discharged from the hydrogen tank 230 based on signals and / or data from the second electronic controller. To this end, the fuel filling 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 fuel filling station system 220 can also be referred to as a fuel filling station safety system.

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

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

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

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

[0106] The nozzle 250 may be connected to the hydrogen fuel filling system of the dispenser 200 through a conduit or flexible tube of a predetermined length. The nozzle 250 may be provided with a shape and structure that closely and securely engages with the receptacle of the vehicle.

[0107] like Figure 2 As shown, the nozzle 250 can be engaged with the socket 150. The first sensor 160 installed in the vehicle and the second sensor 260 attached to the nozzle 250 can send signals or information about the coupling status of the nozzle 250 and the socket 150 to the first electronic controller or vehicle safety system and to the second electronic controller or fuel filling station safety system.

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

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

[0110] Traditionally, there are two methods for transmitting information from the mobile object 100 to the dispenser 200: a communication method and a non-communication method. In the communication method, the temperature and pressure values ​​of the mobile tank 130 of the mobile object 100 are transmitted to the dispenser 200 in a one-way manner. The dispenser 200 does not actively utilize this information, but rather uses it only as a safety reference for, for example, emergency stops due to temperature or pressure limits. Furthermore, the hydrogen refueling protocol for safe and rapid refueling is managed by the dispenser 200, which has only a minimal safety management device that automatically releases hydrogen via a pressure release device (PRD), without requiring any active safety management scheme for the mobile tank 130.

[0111] At the same time, in order to cope with Figure 3 To address the phenomenon of increased hydrogen gas temperature during hydrogen refueling as depicted in FIG, the hydrogen refueling station may be equipped with a precooler. The precooler can reduce the temperature of the hydrogen fuel by precooling. The precooler may be installed in or integrated with at least one of the hydrogen tank 230 and the station box 240. Alternatively, the precooler may be installed in or integrated with the pipeline that transports hydrogen in the hydrogen refueling station.

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

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

[0114] For minimum safety requirements, thermodynamic modeling-based simulations can be performed for various scenarios, and parameters derived from the simulations can be used to perform partial real-time corrections based on tables or MC formulas. Minimum safety requirements can include upper limits for temperature and pressure conditions of the CHSS and guidelines for the fuel filling rate (SOC).

[0115] Without actively controlling the state values ​​related to hydrogen refueling in the dispenser 200, table-based correction has the disadvantage of being very inefficient because it does not utilize the temperature of the pre-cooled hydrogen fuel provided by the refueling station or the temperature of the mobile tank 130 measured in the mobile body 100, and therefore may be difficult to flexibly respond to changes in ambient conditions. Correction based on the MC formula allows real-time compensation for the temperature of the pre-cooled hydrogen fuel, but the calculation and application of this method are complex, which may cause limitations in application and make it difficult to expand. Therefore, conventional communication protocols developed under the main goal of safely completing refueling cannot actively respond to unexpected situations (such as excessive pre-cooling or overheating of the mobile tank 130) and may bring problems such as increased operating costs caused by overcooling and delayed refueling caused by overheating.

[0116] For example, when hydrogen fuel is supplied to the mobile tank 130, the internal temperature of the tank rises due to the heat of compression, and thus the temperature of the hydrogen fuel inside the tank increases. The tank is designed so that the dome and the tank body are wrapped with carbon fiber having low thermal conductivity to block heat exchange between the external atmosphere and the hydrogen fuel stored in the tank. Therefore, when the temperature of the hydrogen fuel inside the tank increases during the refueling process, due to the low thermal characteristics of the tank, the temperature increase displayed on the surface of the tank is likely to be smaller than the internal temperature increase until refueling is complete.

[0117] Meanwhile, the temperature control of the hydrogen fuel filling process may aim to ensure that the internal temperature of the mobile tank 130 is maintained at 85°C or below when the fuel filling is completed by supplying pre-cooled hydrogen. Figure 3 Changes in the characteristic curve shown. The temperature of the hydrogen fuel can be reduced at a constant rate in phase 1 (P1), which is a pre-cooling phase of the hydrogen fuel filling station. In phase 2 (P2), during which the hydrogen fuel is supplied from the hydrogen fuel filling station to a hydrogen mobile body such as a vehicle, the temperature of the hydrogen fuel gradually increases due to the thermal mass of the hydrogen fuel filling station. In phase 3 (P3), during which the hydrogen fuel is transferred to the vehicle tank inside the vehicle, the temperature of the hydrogen fuel increases at a higher rate of increase due to the thermal mass of the vehicle. In phase 4 (P4), during which the hydrogen fuel is compressed and stored in the vehicle tank, the temperature of the hydrogen fuel may increase rapidly due to the heat of compression.

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

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

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

[0121] like Figure 4 As shown, the function blocks UC1 to UC11 may correspond to the time series operations S401 to S411, respectively. In this case, Figure 4 It can also be understood as a flowchart including time-series operations S401 to S411.

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

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

[0124] After the dispenser nozzle is coupled to the vehicle's receptacle, the vehicle and dispenser can be connected by Figure 4 The order shown implements the use cases to perform fuel refueling communication. However, if necessary, the vehicle and dispenser can omit the use cases according to predetermined requirements.

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

[0126] At the same time, a hydrogen fuel vehicle (hereinafter referred to as a "vehicle") and a dispenser implementing the use case can exchange data to identify the vehicle in use case UC-1. To this end, the vehicle can be equipped with sensors, an electronic control unit (ECU), a transmitter, and a receiver. In the case of bidirectional communication, the receiver can be integrated with the transmitter.

[0127] 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 logging data or use it in the fuel filling protocol. Data logging can refer to the process of collecting data over a certain period of time or the data collected by the process to analyze a certain operating state of the hydrogen fuel filling system or record data-based events / operations of the system or network environment. In the case of two-way 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 obtain measurements from the sensors and send the measurements to the vehicle. The vehicle or fuel filling station can use conventional communication protocol standards for communication, such as infrared communication, WiFi and Bluetooth.

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

[0129] The discovery and pairing procedure or pairing process may pre-condition that the nozzle of the dispenser is inserted into and securely coupled to the receptacle of the vehicle refueling receptacle. The vehicle refueling receptacle may be referred to simply as the vehicle receptacle or receptacle.

[0130] Furthermore, the vehicle and dispenser typically know by default which communication protocol to follow. Therefore, communications subsequent to use case UC-1 can rely solely on the communication protocol agreed upon in the current use case as a post-condition for the discovery and pairing process, or the pairing process. If a communication protocol outside the agreed-upon range is selected by the vehicle or dispenser, the selected communication will not be performed. This means that even if the pairing process successfully completes, refueling will not be authorized.

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

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

[0133] Return Reference Figure 4 According to an exemplary embodiment of the present disclosure, the communication method for hydrogen fuel refueling may include: an operation of negotiating a communication protocol with a dispenser that supplies hydrogen to a mobile body (S403); an operation of negotiating a fuel refueling protocol for refueling hydrogen from the dispenser with the dispenser (S404); and an operation of negotiating fuel refueling parameters based on the fuel refueling protocol with the dispenser (S405).

[0134] The communication method for hydrogen refueling performed by a dispenser that supplies hydrogen to a hydrogen fuel mobile body according to an exemplary embodiment of the present disclosure may include: an operation of negotiating a communication protocol with the hydrogen fuel mobile body (S403); an operation of negotiating a fuel refueling protocol for supplying / refueling hydrogen to the hydrogen fuel mobile body with the hydrogen fuel mobile body (S404); and an operation of negotiating fuel refueling parameters based on the fuel refueling protocol with the hydrogen fuel mobile body (S405).

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

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

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

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

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

[0140] In addition, the hydrogen refueling communication stack may include at least one fourth protocol 540 selected from Transport Layer Security (TLS), Datagram Transport Layer Security (DTLS), etc. as a protocol for the security layer of OSI layer 7. TLS may include versions such as TLS 1.2 and TLS 1.3, and DTLS may include versions such as DTLS 1.2 and DTLS 1.3. TLS may be implemented on a TCP socket, while DTLS may be implemented on a UDP socket.

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

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

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

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

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

[0146] [Table 1]

[0147]

[0148]

[0149] At the same time, the discovery and pairing process use case UC1 enables the device to identify the communication counterpart (i.e., the communication module of the vehicle or dispenser) that is responsible for controlling the socket or nozzle physically coupled to the device. In addition, use case UC1 may also define incompatibility identification methods and safety device mechanisms. In this use case UC1, the vehicle and the dispenser may try to find a common communication technology to execute the fuel filling protocol. The vehicle and the dispenser may discover each other and initiate communication based on the discovery mechanism provided by the data link and physical layers. An additional pairing process may be required to establish a communication channel with the device connected to the fuel filling hose assembly. In cases where the communication channel cannot ensure correct pairing, for example in the case of wireless communication, a separate pairing channel may be required to send the pairing information. However, if pairing is ensured implicitly, a communication channel integrated with the hose assembly may be sufficient, for example.

[0150] Table 2 shows Figure 4 The goals, preconditions and postconditions of the use case UC1 of the discovery and pairing operation (S401) are shown.

[0151] [Table 2]

[0152]

[0153]

[0154] Table 3 shows the Figure 4 The supported communication technologies and related items used in the use case UC1 of the discovery and pairing operation (S401) are shown.

[0155] [Table 3]

[0156]

[0157] Figure 6 is a sequence diagram illustrating operation S401 in detail according to an exemplary embodiment of the present disclosure. Figure 6 ,exist Figure 4 In the pairing process of the discovery and pairing operation ( S401 ) shown, the vehicle and the dispenser may exchange pairing IDs with each other and discover each other's pairing IDs during pairing at UCDC Level 2 and UCDC Level 3 .

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

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

[0160] This transmit-echo-verify method enables vehicles and dispensers to use a session-specific, random pairing ID. This method helps address privacy concerns associated with the exchange of pairing IDs. Specifically, trust in the pairing process can be established later, and to this end, the session-specific pairing ID can be included in the trust-building data.

[0161] Also, when secure communication is supported at a specific UCDC level, at least one of the vehicle and dispenser can verify that the pairing provides sufficient information to secure the communication channel for all methods used to pair the vehicle and dispenser. For example, pairing can include the exchange of encryption keys so that the vehicle and dispenser can securely communicate during refueling.

[0162] It should be noted that UCDC Level 1 does not ensure the security of the communication channel because it does not support bidirectional communication. Pairing vehicles and dispensers at UCDC Level 2 and UCDC Level 3 can be configured to provide sufficient information to ensure communication security sufficient to meet a specific security level (e.g., IEC 62443 Security Level 3). IEC 62443 Security Level 3 may be a security level for actors with sufficient resources and sufficient motivation.

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

[0164] refer to Figure 7 Considering interoperability, the hydrogen fueling device can be designed to have backward compatibility with existing devices. The hydrogen fueling device or the communication device in the hydrogen fueling device can be classified into Type 0, Type 1, Type 2, and Type 3 based on interoperability.

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

[0166] A Type 1 device may refer to a device that supports IrDA communication for fuel refueling. A Type 1 device may fall back to a Type 0 device.

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

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

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

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

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

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

[0173] In other words, Figure 7 As shown, 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 may fall back to type 0 (S610).

[0174] Furthermore, 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 may fall back to type 0 ( S620 ).

[0175] Furthermore, 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 a Type 3 device encounters a Type 1 device, the Type 3 device can fall back to Type 1 (S640). When a Type 3 device encounters a Type 2 device, the Type 3 device can fall back to Type 2 (S650).

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

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

[0178] In Scenario 1, the dispenser can be equipped with an access point (AP), i.e., a wireless router. The access point can beacon a signal, allowing vehicles to access the fuel station and vehicle supply equipment (VSE). FCEVs approaching the dispenser can scan and discover the dispenser and establish a WLAN link with it.

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

[0180] In Scenario 3, the dispenser can support bidirectional WLAN communication and unidirectional IrDA communication. In this case, the dispenser corresponds to a Type 3 device. An FCEV (which is a Type 1 device) can be parked near the dispenser. The dispenser cannot yet find any WLAN clients. When the nozzle of the cable attached to the dispenser is coupled to the socket of the FCEV, IrDA communication can be initiated between the FCEV and the dispenser.

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

[0182] refer to Figure 8 , the bidirectional communication process for hydrogen fueling according to the present embodiment can provide rules and principles for fallback when selecting the fueling method and communication protocol to maximize interoperability, rather than selecting the communication scheme most preferred by the FCEV or dispenser.

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

[0184] For example, if the vehicle and dispenser are of the same type or the same UCDC level, both devices can maintain their current type or UCDC level. On the other hand, if one device is a Type 1 device and the other is a Type 2 device, both devices can be configured to fall back to Type 0. Meanwhile, if one device is a Type 3 device and the other 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.

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

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

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

[0188] Regardless of whether or not a unidirectional communication capability is present, the aforementioned bidirectional communication device can be configured to support a unidirectional communication-based refueling method. The bidirectional communication device must be able to check whether the other device supports bidirectional communication. If the other FCEV (or mobile vehicle) and / or dispenser does not support bidirectional communication, the bidirectional communication device can fall back to a unidirectional communication method that relies on a compatible unidirectional communication scheme between the devices.

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

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

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

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

[0193] Static data transmitted at UCDC Level 2 (UCDC-2) 920 may be used for security functions. The static data of UCDC Level 2 (UCDC-2) 920 may be usable data added to static data and dynamic data defined for UCDC Level 1.

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

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

[0196] Reference together Figures 4 to 8 ,exist Figure 4The 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.

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

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

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

[0200] The distributor may receive a DDP request message DDPRequest and may send a DDP response message DDPResponse in response to the DDPRequest. The DDP response message DDPResponse may include the distributor's IP address "IPAddr", the distributor's TCP port number "TCPPort", the distributor's UDP port number "UDPPort" and the distributor's pairing ID "pairing_id".

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

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

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

[0204] The hydrogen fuel mobile device may then wait for a response containing an authorization result from the dispenser and may send an authorization result request message ("Completed?") for the selected authorization method to the dispenser (S1050). If no authorization result is received or the authorization is not completed, operations S1010 to S1050 may be repeated. After the authorization is completed, the dispenser may send an authorization completion message ("Completed (Success)") to the hydrogen fuel mobile device (S1090).

[0205] According to the method described above, the dispenser can verify whether the hydrogen fuel mobile body is authorized, that is, whether the user of the hydrogen fuel mobile body has the right to hydrogen fuel refueling, before continuing the hydrogen fuel refueling process.

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

[0207] Furthermore, the hydrogen fuel mobile and dispenser can perform a discovery and pairing process, establishing a connection at the data link and physical layers. The necessary certificates for authentication and key exchange can then be prepared. Thus, the communication channel between the hydrogen fuel mobile and dispenser can be encrypted and integrity-protected. The dispenser can authenticate the hydrogen fuel mobile, and optionally, the hydrogen fuel mobile can authenticate the dispenser.

[0208] At the same time, during the TLS handshake, authentication of the hydrogen fuel mobile may be mandatory, while authentication of the dispenser may be optional. In this case, the dispenser may act as a client and the hydrogen fuel mobile may act as a server.

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

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

[0211] If the hydrogen fuel mobile sends a certificate request message and a handshake message (such as ServerHello), but the dispenser does not send a certificate verification message and a certificate, the hydrogen fuel mobile can terminate the TLS handshake by sending an alert message with an alert code of "Certificate_required".

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

[0213] [Table 4]

[0214]

[0215] Figure 11 is a sequence diagram illustrating a communication protocol negotiation operation S403 that may be employed in a bidirectional communication process for hydrogen fuel refueling according to an exemplary embodiment of the present disclosure. Figure 11 , the communication protocol negotiation operation S403 may include an operation of sending a message including information about a first communication protocol applicable to the mobile body to the distributor (S1110); and an operation of receiving a message including information about a second communication protocol selected from common communication protocols commonly applicable to both the mobile body and the distributor from the distributor (S1130).

[0216] exist Figure 11 In the exemplary embodiment shown, the distributor may receive a message including information about a first communication protocol applicable to the mobile body from the mobile body (S1110), compare the first communication protocol with a communication protocol applicable to the distributor to select a second communication protocol from common communication protocols commonly applicable to both the mobile body and the distributor, and send a message including information about the selected second communication protocol to the mobile body (S1130).

[0217] Despite Figure 11 Although not shown in FIG. 1 , the communication protocol negotiation operation may further include an operation in which the distributor requests information including a list of first communication protocols applicable to the mobile body from the mobile body before operation S1110 .

[0218] In another alternative embodiment of the present disclosure, the distributor may first send a message including information about its own communication protocols applicable to the mobile body, and the mobile body may select a certain communication protocol among the public communication protocols and send a message including information about the selected communication protocol to the distributor.

[0219] In this case, the communication protocol negotiation operation may further include an operation in which the mobile requests information including a list of applicable communication protocols from the allocator.

[0220] Table 5 shows the objectives, preconditions, and postconditions of operation S403 according to an exemplary embodiment of the present disclosure.

[0221] [Table 5]

[0222]

[0223]

[0224] Table 6 shows the content of a message transmitted or received in operation S1110 according to an exemplary embodiment of the present disclosure.

[0225] [Table 6]

[0226]

[0227] The information about the first communication protocol may include at least one 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 sent or received in operation S1130 may be summarized as shown in Table 7.

[0228] [Table 7]

[0229]

[0230] The response message including information about the second communication protocol may also include information on whether the communication protocol negotiation was successful. After the mobile and dispenser discover each other and pair on compatible communication channels, a communication protocol negotiation process is performed to identify the communication protocol to be followed during the hydrogen refueling session. Specifically, in this embodiment, the dispenser may proactively exchange communication protocols and parameters with the mobile.

[0231] That is, the communication method according to the exemplary embodiment of the present disclosure may perform operation S401 of performing a discovery and pairing process with a distributor using a first communication technology.

[0232] If the result of the communication protocol negotiation operation S403 is related to the second communication technology, the second communication technology may be used to perform the fueling protocol negotiation operation S404 and the fueling parameter negotiation operation S405 (described in detail below).

[0233] In operation S401 of performing a discovery and pairing process, information regarding interoperability and / or compatibility between a mobile and a distributor may be shared.

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

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

[0236] In an actual implementation, various combinations may exist between the mobile body and the dispenser depending on the hydrogen fueling communication standard, communication mode, fueling method, communication level and other parameters. Here, the hydrogen fueling communication standard may include the SAE J2601 series, ISO 19885-3 and ISO 19885-4 standards. The communication mode may include no communication, IrDA, XYZ (ISO), etc. The fueling method may include a table-based fueling method, such as a lookup table-based method, and an MC formula-based fueling method. The communication level may include a UCDC level, and other parameters may include a pressure level, a category of a compressed hydrogen storage system (CHSS), a hydrogen fueling table, etc.

[0237] Meanwhile, the mobile or the distributor may be configured to perform fallback to a lower type or a lower UCDC level according to the type and UCDC level of the counterpart device discovered during the communication protocol negotiation process.

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

[0239] An example of a communication protocol for assigning priorities according to an exemplary embodiment of the present disclosure is shown in Table 6.

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

[0241] The common protocol may be the result of an agreement between the mobile body and the dispenser on a communication protocol to be used for refueling communications.

[0242] At the same time, the mobile body can prioritize the communication protocols supported by the mobile body. The mobile body may include an FCEV. The mobile body can provide the prioritized communication protocols to the distributor. An example of assigning priorities to communication protocols is shown in Table 8.

[0243] [Table 8]

[0244] 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 3 ISO 19885-3-2023-UCDC-2 2 ISO 19885-3-2023-UCDC-3 1

[0245] After selecting a communication protocol in the communication protocol negotiation use case UC3, the mobile and dispenser can activate their communication protocol implementations and initiate refueling protocol negotiation. Refueling protocol negotiation is the process by which the mobile and dispenser discover and agree on a refueling protocol for the refueling session. In this operation, the mobile and dispenser can select the communication protocol most preferred by the mobile from among the protocols supported by both the mobile and dispenser. A communication protocol negotiation method for hydrogen refueling performed by a communication controller of a hydrogen fuel mobile 100 according to an exemplary embodiment of the present disclosure may include: an operation S1110 of sending a first message including a list of one or more first refueling protocols supported by the mobile and one or more first communication protocols required to execute the one or more first refueling protocols to a communication entity associated with the dispenser 200; and an operation S1130 of receiving a response message including a second refueling protocol selected from the one or more first refueling protocols from the communication entity associated with the dispenser 200. The communication entity associated with the dispenser 200 may be the electronic controller 210 of the dispenser 200 or may be a separate communication device installed on the dispenser 200. Alternatively, an electronic controller or a separate communication device in the fuel filling station system 220 may communicate with the mobile body / mobile body 100 instead of the dispenser 200 .

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

[0247] The response message may include a second refueling protocol selected from one or more first refueling protocols based on preference-based priority information. Mobile 100 or dispenser 200 may independently or collaboratively select the second refueling protocol based on the preference-based priority information. The final operation of sending an approval message to the other party to complete the protocol negotiation process may be performed by mobile 100, but may alternatively be performed by dispenser 200. In this case, dispenser 200 may first send a list of supported protocols, and mobile 100 may respond with the selected protocol.

[0248] The response message may include one or more first fueling protocols and a second fueling protocol selected from protocols commonly included in the one or more first fueling protocols and protocols supported by dispenser 200 .

[0249] The response message may include a second communication protocol determined by the controller of the dispenser 200 according to a fallback device type based on interoperability and backward compatibility between the mobile body 100 and the dispenser 200 from among a plurality of first communication protocols required to execute the first fueling protocol.

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

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

[0252] Figure 12 is a sequence diagram illustrating a communication protocol negotiation operation S404 during a hydrogen fueling two-way communication process according to an exemplary embodiment of the present disclosure.

[0253] refer to Figure 12 , operation S404 of negotiating a fuel filling protocol according to an exemplary embodiment of the present disclosure may include operation S1210 of sending a message including information about a first fuel filling protocol applicable to the mobile body to the dispenser based on a result of the communication protocol negotiation (S403); and operation S1230 of receiving a message including information about a second fuel filling protocol selected from fuel filling protocols commonly applicable to both the mobile body and the dispenser from the dispenser.

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

[0255] The dispenser may select a refueling protocol that is common to a refueling protocol that supports the second communication protocol and is applicable to the dispenser and one or more available first refueling protocols, and determine one of the selected common protocols as the second refueling protocol. In this case, the second refueling protocol may be determined based on interoperability and / or compatibility. Furthermore, the second refueling protocol may be determined based on a preference set by the mobile object or the dispenser.

[0256] exist Figure 12 In the exemplary embodiment shown, the dispenser may receive a message from the mobile body including information about one or more available first fueling protocols applicable to the mobile body (S1210), compare the first fueling protocols with fueling protocols applicable to the dispenser, select a second fueling protocol from common fueling protocols applicable to both the mobile body and the dispenser, and send a message to the mobile body including information about the selected second fueling protocol (S1130).

[0257] Despite Figure 12 Although not shown in the figure, an operation of requesting the dispenser to the mobile body for information including a list of first fueling protocols applicable to the mobile body may be further included before operation S1210.

[0258] In another exemplary embodiment of the present disclosure, the dispenser may first send a message including information about a fuel refueling protocol applicable to the dispenser to the mobile body, and the mobile body may select a specific fuel refueling protocol from public fuel refueling protocols and send a message including information about the selected specific fuel refueling protocol to the dispenser.

[0259] In this case, an operation of the mobile body requesting information including a list of applicable fueling protocols from the dispenser may also be included.

[0260] Table 9 shows the target, preconditions, and postconditions of operation S404 according to an exemplary embodiment of the present disclosure.

[0261] [Table 9]

[0262]

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

[0264] [Table 10]

[0265]

[0266] The information of the first fueling protocol may include at least one 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 the message sent or received in operation S1230 according to an exemplary embodiment of the present disclosure.

[0267] [Table 11]

[0268]

[0269] The message including the information about the second fueling protocol may further include information on whether the negotiation of the fueling 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.

[0270] [Table 12]

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

[0272] As shown in Table 12, the mobile body may provide the dispenser with parameter information in a table form, which includes the name, revision date or year or version, information on whether a sub-protocol is available, and preference information for the fueling method or fueling protocol supported by the mobile body.

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

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

[0275] Examples of messages transmitted in operation S1230 according to exemplary embodiments are shown in Tables 13 and 14.

[0276] [Table 13]

[0277] Fueling Agreement ID Result Codes 2 OK

[0278] As shown in Table 13, the dispenser may select the fueling protocol corresponding to Index 2 and transmit a response message including a result code of OK to the mobile body.

[0279] [Table 14]

[0280] Fueling Agreement ID Result Codes FAIL_NO_COMMON_PROTOCOL

[0281] As shown in Table 14, when the dispenser fails to find a compatible protocol in the list of fueling protocols supported by the mobile body received from the mobile body, the dispenser may send a response message including information indicating that there is no common protocol (e.g., FAIL_NO_COMMON_PROTOCOL) in the result code field to the mobile body. The examples shown in Tables 13 and 14 may be similarly applied to a case where the dispenser selects a second communication protocol from the common communication protocols and responds to the mobile body. Figure 11 The case where the moving object responds in operation S1130 is shown.

[0282] Figure 13 is a sequence diagram illustrating a fueling parameter exchange / negotiation operation ( S405 ) applicable to a hydrogen fueling bidirectional communication process according to an exemplary embodiment of the present disclosure.

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

[0284] refer to Figure 13 , the fuel filling parameter exchange / negotiation operation (S405) can send a message including information about the fuel filling parameters on the mobile body side required by the second fuel filling protocol selected as a result of the fuel filling protocol negotiation operation (S404) to the dispenser (S1310); and receive a message including compatibility information of the dispenser side with the fuel filling parameters on the mobile body side from the dispenser (S1350).

[0285] The fueling parameter negotiation operation S405 may include operation S1330 of receiving a message including information about fueling parameters on the dispenser side required by the second fueling protocol selected as a result of the fueling protocol negotiation operation S404 from the dispenser; and operation S1370 of sending a message including compatibility information of the mobile body side with the fueling parameters on the dispenser side to the dispenser.

[0286] When the mobile transmits a message including information on fuel refueling parameters on the mobile side in operation S1310, the mobile may set an 'Accepted' field for each corresponding parameter to <pending> before transmitting to the mobile.

[0287] Similarly, when the dispenser transmits a message including information on fueling parameters on the dispenser side in operation S1330, the dispenser may set an 'Accept' field for each corresponding parameter to <Pending> before transmitting to the mobile body.

[0288] When the mobile sends a message including information on the fuel filling parameters on the dispenser side in response to the message received in operation S1330, the mobile may set the "Accept" field for each corresponding parameter to "Accept" before responding to the dispenser. <ok>Or <true> (S1350).

[0289] When the dispenser transmits a message including information on the fuel filling parameters on the moving body side in response to the message received in operation S1310, the dispenser may set the "Accept" field for each corresponding parameter to "Accept" before responding to the moving body. <ok>or <true>.

[0290] The mobile and dispatcher may respond by setting the "Accept" field for each parameter. For parameters for which the negotiation has not yet reached an agreement, the "Accept" field may be set to <false>.

[0291] The mobile and dispenser may agree on all fueling parameters by repeatedly sending and receiving messages and responding to received messages.

[0292] Parameters exchanged between the dispenser and the mobile body may include parameters for supporting fueling method compatibility, parameters related to physical properties, monitoring parameters, and acceptance-related parameters.

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

[0294] At the same time, the distributor may transmit information of a second parameter supported by the distributor (ie, the parameter of the distributor) and an OK message indicating that the first parameter is received to the mobile body (S1330, S1370).

[0295] Second parameters related to the fueling protocol exchange / negotiation may include parameters for supporting fueling method compatibility, parameters related to physical characteristics, fueling target (target SoC) parameters, monitoring parameters, and acceptance-related parameters.

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

[0297] As described above, the mobile body may provide the dispenser with parameters listed in a table format. The listed parameters may include FCEV parameters that are compatible with the UCDC level negotiated during the refueling agreement negotiation process.

[0298] As described above, after establishing a communication link and selecting a communication protocol and a refueling protocol during the protocol negotiation phase, the mobile and dispenser can exchange various parameters to determine whether they can perform a compatible refueling process. The information required to perform a safe and efficient refueling process can include compatibility-related parameters, physical property-related parameters, refueling target parameters, and monitoring parameters.

[0299] Compatibility-related parameters can include fueling protocol type and fuel delivery temperature. Physical property-related parameters can include CHSS pressure and maximum allowable flow rate. Fuel target parameters can include target SOC and target CHSS pressure. Monitoring parameters can include current CHSS temperature and ambient temperature.

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

[0301] After negotiating the refueling protocol in the aforementioned use case UC-4, the mobile and dispenser can negotiate specific parameters for the refueling protocol, communicate static or dynamic status, and exchange detailed refueling parameters to determine the refueling destination. If the refueling parameter negotiation fails due to parameter incompatibility, the dispenser and mobile can return to use case UC-3 to select another refueling protocol or return to use case UC-1 to select another communication protocol. If use cases UC-3 and UC-1 cannot be executed normally, the dispenser and mobile can terminate the current communication.

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

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

[0304] In another exemplary embodiment of the present disclosure, one of the mobile body or dispenser may first send the fueling parameters to the other party, and the other party may respond with a message including the newly reconfigured fueling parameters by changing unacceptable parameters among the received fueling parameters while maintaining accepted parameters.

[0305] In another exemplary embodiment of the present disclosure, the mobile and the distributor may perform parameter negotiation step by step. The mobile and the distributor may initiate negotiation for some parameters and perform an exchange / negotiation process for sub-parameters of the parameters that have been agreed upon.

[0306] In another exemplary embodiment of the present disclosure, each message including the fueling parameters may be set to be deemed as not agreed upon if a response message is not received within a preset message processing time.

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

[0308] [Table 15]

[0309] name unit Accuracy Range / Value type Semantics Pressure level N / A N / A {H35, H70} Static Tank pressure level CHSS volume Lift 2 decimal places Positive, no maximum value Static Tank capacity CHSS pressure MPa 2 decimal places Positive, no maximum value dynamic Current pressure of the tank Emergency Strategy N / A N / A {Terminate, rollback} Static Emergency treatment strategy

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

[0311] [Table 16]

[0312]

[0313] During the refueling parameter negotiation operation (S405), the mobile and dispenser may send a message to each other containing supported refueling parameter ranges or values. The parameters may include physical characteristic-related parameters (hereinafter referred to as "physical parameters"), monitoring parameters, security policy-related parameters, and acceptance-related parameters.

[0314] Physical parameters may include vessel type, pressure level, CHSS category, CHSS type, CHSS capacity, maximum allowable CHSS pressure, maximum allowable CHSS temperature, and maximum allowable flow rate. Monitoring parameters may include current CHSS pressure and current CHSS temperature. Security policy-related parameters may include emergency policy and security enforcement level. Acceptance-related parameters may include information indicating whether it is accepted, i.e., parameters indicating yes (true), no (false), or pending.

[0315] Parameters related to the fueling parameter negotiation may include physical characteristic related parameters (ie, physical parameters), monitoring parameters, fueling target parameters, safety policy related parameters, and acceptance related parameters.

[0316] Physical property-related parameters may include maximum fuel delivery pressure, maximum fuel delivery temperature, minimum fuel delivery temperature, and maximum fuel delivery flow rate. Monitoring parameters may include current fuel delivery temperature and ambient temperature. Fueling target parameters may include the selected fueling schedule, target SOC, target final CHSS pressure, target final CHSS temperature, target APR, and target or expected fueling duration. Acceptance-related parameters may include information indicating whether it has been accepted. Each of the above parameters may include information corresponding to one of the predetermined levels or settings, as well as information regarding the same or different master UCDC levels.

[0317] The mobile entity may provide the dispenser with parameters listed in a table format. The listed parameters may include FCEV parameters that are compatible with the UCDC level negotiated during the refueling agreement negotiation process.

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

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

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

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

[0322] Figure 14 is a conceptual diagram illustrating a table summarizing parameters transmitted from a mobile body side to a dispenser side in a fuel filling parameter exchange process according to an exemplary embodiment of the present disclosure.

[0323] Figure 15 is a conceptual diagram illustrating a table summarizing parameters transmitted from a dispenser side to a moving body side in a fuel filling parameter exchange process according to an exemplary embodiment of the present disclosure.

[0324] Reference together Figure 13 and 15 , a method for exchanging parameters for hydrogen refueling through communication according to an exemplary embodiment may include: operation S1310 of sending a first parameter including one or more first hydrogen refueling method compatibilities supported by the mobile body 100 and at least one of one or more first physical characteristics to a communication entity associated with the dispenser 200; and operation S1330 of receiving a response message including a second parameter including one or more second hydrogen refueling method compatibilities supported by the dispenser, one or more second physical characteristics, and at least one of a fueling target from the communication entity associated with the dispenser 200.

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

[0326] The first parameter may further include a first monitoring parameter supported by the mobile object 100. The second parameter may further include a second monitoring parameter supported by the dispenser 200.

[0327] In the parameter exchange method for the hydrogen fueling process according to the exemplary embodiment of the present disclosure, the parameter exchange process can be terminated based on the confirmation message (e.g., 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 the exchanged parameters. The parameter exchange process can also be terminated when either party does not accept the exchanged parameters. In the event that either party does not accept the exchanged parameters, the protocol negotiation process can be re-accessed according to the following process, or the fueling session can be terminated.

[0328] In the parameter exchange method through communication of the hydrogen fueling process according to the exemplary embodiment of the present disclosure, the one or more first hydrogen fueling method compatibilities may include one or more of the pressure level and the CHSS category of the mobile body 100 .

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

[0330] In the parameter exchange method through communication of the hydrogen fuel filling process according to the exemplary embodiment of the present disclosure, the first parameter also includes a parameter related to the acceptance of the mobile body 100 .

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

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

[0333] In the parameter exchange method through communication of the hydrogen fueling process according to the exemplary embodiment of the present disclosure, the one or more second physical characteristics may include one or more of a maximum fuel delivery pressure, a maximum fuel delivery temperature, a minimum fuel delivery temperature, and a maximum fuel delivery flow rate.

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

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

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

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

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

[0339] If the mobile 100 or dispenser 200 does not accept the exchanged parameters, the mobile 100 may perform the protocol negotiation process again. Alternatively, if the mobile 100 or dispenser 200 does not accept the exchanged parameters, the mobile 100 may terminate the fueling session.

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

[0341] Table 17 shows the content of a message including fuel filling parameters on the mobile body side according to another exemplary embodiment of the present disclosure.

[0342] [Table 17]

[0343] Physical parameters Container Type ？ Pressure level H35 / H70 CHSS Category A / B / C / D CHSS type 1 / 2 / 3 / 4 CHSS volume ？L Maximum allowable CHSS pressure ? MPa Maximum allowable BHSS temperature ？℃ Maximum allowable flow rate ? g / s Monitoring parameters Current CHSS pressure ? MPa Current CHSS temperature ？℃ Security Policy Emergency Strategy ？ Security Execution Level ？ accept Accepted True / False / Undecided

[0344] Table 18 shows the content of a message including dispenser-side fueling parameters according to another exemplary embodiment of the present disclosure.

[0345] [Table 18]

[0346] Physical parameters Fuel filling delivery temperature T30 Maximum fuel delivery pressure ? MPa Maximum fuel delivery temperature ？℃ Minimum fuel delivery temperature ？℃ Maximum fuel delivery flow rate ? g / s Monitoring parameters Current fuel delivery temperature ？℃ Ambient temperature ？℃ Fueling target Selected fuel filling table D1 Target SoC ？％ Target final CHSS pressure ? MPa Target final CHSS temperature ？℃ Target APR ? MPa / s Expected refueling duration ？℃ Security Policy ？s accept Accepted True / False / Undecided

[0347] The communication method according to an exemplary embodiment of the present disclosure may further include the following operation: when the fuel filling parameters are incompatible between the mobile object and the dispenser as a result of the fuel filling parameter negotiation, at least one of the communication protocol and the fuel filling parameters may be renegotiated (S405). In such a case, the renegotiation operation in the communication method according to the exemplary embodiment may include re-performing operations S403, S404, and S405. For example, the process may return to step S403 for renegotiation, and then sequentially perform steps S404 and S405 again. In another embodiment, the process may return to operation S404 to perform renegotiation in operation S404, and then perform operation S405 again.

[0348] In a communication method according to another exemplary embodiment of the present disclosure, the renegotiation operation may simplify operations S403, S404, and S405 or omit some processing procedures. Alternatively, the renegotiation operation may combine operations S403 and S404 to negotiate the communication protocol and the fueling protocol together.

[0349] In a communication method according to another exemplary embodiment of the present disclosure, a renegotiation operation may be performed based on a list of communication protocols or refueling protocols other than the communication protocol or refueling protocol selected in operations S403 and S404, respectively. For example, based on the compatibility and / or interoperability information identified in operation S401, the communication protocol and refueling protocol may be negotiated together using a protocol list including both the communication protocol and the refueling protocol, the protocol list being based on mutual supportability of the communication protocol and the refueling protocol in the mobile object and the dispenser.

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

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

[0352] The communication method according to the exemplary embodiment of the present disclosure may include operation S409 of terminating communication between the dispenser and the mobile body when the fuel filling parameters are incompatible between the mobile body and the dispenser as a result of the fuel filling parameter negotiation.

[0353] Return Reference Figure 4 , the safety check-in process may be used in the two-way communication process of hydrogen fueling according to an exemplary embodiment of the present disclosure.

[0354] In a safety check-in operation S406 , the dispenser (including the mobile body) and the mobile body may check whether all necessary safety conditions are met before actual fueling begins.

[0355] After the refueling parameters are exchanged and the mobile and dispenser are deemed compatible, the mobile and dispenser can perform a safety status check to determine if refueling can be performed safely. Depending on the refueling protocol, the safety check can be performed implicitly within the protocol. Furthermore, depending on the implementation, the safety check-in operation S406 can be omitted.

[0356] During the safety check-in operation S406 , the mobile body and / or dispenser may check whether the engagement of the nozzle and the container is locked, check whether there are any leaks, and check the last minute status.

[0357] If the mobile has received the fuel filling parameter negotiation response message from the dispenser and the fuel filling protocol supports the safety check-in function, the mobile can initiate the safety check-in operation S406 by sending a safety check-in request message to the dispenser within the message sequence setting time interval.

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

[0359] The mobile object and the dispenser can exchange messages related to gas leak checks. During the exchange of messages related to gas leak checks, the dispenser can send a message to the mobile object indicating that the leak check is in progress ("In Progress"). Furthermore, the mobile object can send a message to the dispenser indicating that the mobile object is awaiting leak check results from the dispenser ("Waiting"). When the leak check is complete, the dispenser can send a message to the mobile object requesting the tank volume to be measured, along with a message indicating that the leak check is complete ("Completed").

[0360] The distributor may send a message for a stationary status check to the mobile, and the mobile may send a message to the distributor indicating that it is ready for a status check.

[0361] If the mobile body reports parameters regarding the current state or fixed state of the mobile body to the dispenser, the dispenser may report parameters regarding the coupler lock state, leak check state, and predicted mobile body tank capacity to the mobile body.

[0362] After completing the aforementioned safety check-in operation S406, actual refueling can begin. During refueling, the mobile and dispenser can exchange information to monitor various status parameters to ensure that refueling is carried out safely and efficiently. If necessary, the mobile or dispenser can send control messages requesting actions from the other to control the refueling process or respond to safety-related conditions. The parameters and commands exchanged can vary depending on the actual refueling protocol.

[0363] Operation S407 represents a monitoring and control process that may be employed in a two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure.

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

[0365] Furthermore, the mobile can send certain commands to the dispenser to control the refueling process, such as starting or stopping refueling. In this case, the mobile can communicate using UDP and DTLS to support black channel communication. Black channel communication refers to communication that applies black channel principles to ensure secure communication, even though the output characteristics of the communication channel may be insecure or have application-irrelevant properties.

[0366] The monitoring and controlling operation S407 will be described in more detail. The mobile body may send a message to the dispenser to start fuel filling control, and in response, the dispenser may send a message including a confirmation (eg, “OK”) to the mobile body.

[0367] In addition, the mobile body can send a message to the dispenser including information about its own fuel filling circuit (e.g., x, y, z), and the dispenser can send a message to the dispenser including information about its own fuel filling circuit (e.g., a, b, c), which corresponds to the fuel filling circuit of the mobile body.

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

[0369] In addition, the mobile body may send a fuel filling control request message requesting to stop fuel filling to the dispenser. The dispenser may send a fuel filling status response message including information that fuel filling is stopped or has been stopped to the mobile body.

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

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

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

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

[0374] Meanwhile, when TCP is used in monitoring and control operation S407, if the security check-in response message or security check-in process according to the fueling protocol is omitted, after receiving the fueling parameter negotiation response message from the dispenser, the mobile body can send a fueling loop request message to the dispenser within the message sequence setting time interval. Request messages or response messages related to the fueling loop can be transmitted using DTLS messages.

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

[0376] The safety checkout process S408, which can be employed in the bidirectional communication process for hydrogen refueling according to an exemplary embodiment of the present disclosure, can be performed as follows. The mobile object and the dispenser can verify that all necessary safety conditions are met before the dispenser's nozzle is disconnected from the mobile object's container through the safety checkout process. In other words, the mobile object and the dispenser can verify that it is absolutely safe for a user or operator to disconnect the nozzle from the mobile object after refueling is completed.

[0377] For example, if the mobile receives a fuel filling loop response message in which the "result" is set to the "OK" attribute or the "status" is set to the "completed" attribute from the dispenser, or the mobile receives a fuel filling status response message including information to stop fuel filling, and if the hydrogen fuel filling protocol supports safety checkout, the mobile can initiate safety checkout and perform safety checkout operation S408 by sending a safety checkout request message to the dispenser within the message sequence set time interval.

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

[0379] The safety checkout operation S408 will be described in more detail. The mobile body may send a message containing information about the coupler check result (e.g., "OK") to the distributor, and the distributor may send a message containing information indicating that the coupler check is in progress (e.g., "In Progress") to the mobile body.

[0380] In addition, the mobile body can send a message containing information about the coupler inspection result (e.g., "OK") to the distributor again, and the distributor can send a message containing information indicating that the coupler inspection is completed (e.g., "Complete") to the mobile body.

[0381] When the coupler inspection result shows that the coupler inspection is completed normally, the nozzle of the dispenser can be separated from the container of the mobile body by the user or operator.

[0382] In the safety checkout operation S408, the report message sent by the dispenser to the mobile object may include information or parameters about the unlocking state of the coupler. The coupler unlocking state information may include information about lock, unlock, ice, or problems.

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

[0384] The termination process S409 that may be employed in the bidirectional communication process of hydrogen fueling according to an exemplary embodiment of the present disclosure may be performed as follows.

[0385] In the termination operation S409, which is the final stage of refueling, the mobile and the dispenser can exchange information about the refueling results related to the refueling performance and method and / or the reason for the unexpected refueling stop, thereby completing all operations related to hydrogen refueling. The termination use case can also be configured to handle tasks related to non-safety-critical issues when they occur.

[0386] For example, after the mobile body receives a safety detection response message (wherein the "result" attribute is set to "complete") or a fuel filling loop response message (wherein the "status" attribute is set to "complete") from the dispenser or information including stopping fuel filling, the mobile body can send a termination request message to the dispenser to perform the termination operation S409.

[0387] The termination operation S409 will be described in more detail. The mobile body may send a message to the dispenser to inquire about how much fuel has been refilled from the dispenser. The dispenser may send a response message including information about the amount of hydrogen fuel (eg, X grams) in response to the inquiry message to the mobile body.

[0388] Subsequently, the mobile body may transmit a confirmation request message for completing fueling to the dispenser, and the dispenser may transmit a bye message to the mobile body as a response message to the confirmation request message.

[0389] After completing the fueling and performing the safety check, in a termination operation S409, the mobile and the dispenser may exchange at least some bookkeeping information for the fueling session of the hydrogen fueling. Before completing the termination operation S409, the mobile and the dispenser may exchange summary information about the hydrogen fueling session.

[0390] The bookkeeping information may include all information related to hydrogen fueling recorded in the mobile body or dispenser according to prescribed rules or policies during all fueling processes for hydrogen fueling and before completing the termination operation S409 of the use case UC-9.

[0391] The bookkeeping information or summary information may include information about how much fuel was dispensed and what reports were generated. Furthermore, the report message sent by the mobile to the dispenser may include information or parameters related to the current tank temperature and the current tank pressure. Furthermore, the report message sent by the dispenser to the mobile may include information about the final SOC, the final average refueling rate (APR), the final measured tank pressure, the actual refueling time, and the actual amount of hydrogen fuel refueled.

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

[0393] Some examples of communication data exchanged in use cases UC5 to UC9 are summarized in Table 19.

[0394] [Table 19]

[0395]

[0396]

[0397] Meanwhile, the error handling use case UC10 is a functional block for handling a situation where an error not critical to safety occurs due to a shutdown of a normally terminated fueling process or a sudden interruption of communication. The error handling process that can be employed in the bidirectional communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure can be performed as follows.

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

[0399] When a non-safety-critical error occurs and further communication is impossible, error handling operation S410 can be applied. Based on this error handling process, the Mobile and Dispenser can handle the occurrence of non-safety-critical errors at any time during refueling. When a non-safety-critical error occurs, the Mobile and Dispenser can immediately stop refueling, temporarily halt the previously selected and currently operating use case, and then proceed with the Termination Use Case UC9.

[0400] If the mobile detects an event related to a non-safety-critical error, the mobile may notify the dispenser of the termination reason via a termination request message and terminate the current fueling session or communication session. The dispenser may terminate the current communication session in response to the termination request message. If further communication is impossible, the current session may be terminated without additional notification.

[0401] When a non-safety-critical error is detected in the mobile and the communication channel remains operational, the mobile may send a terminate request message to the dispatcher with the "action" attribute set to "stop" and the "reason" attribute set to an appropriate reason or reason code. Examples of appropriate reasons or reason codes may include a reason such as "message corrupted."

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

[0403] That is, for a successful refueling, the transmission must convey the expected actions or operations according to the protocol, and the refueling operation needs to be within the acceptable range of the refueling protocol. However, in practice, various abnormal events may occur. While some errors are trivial and can be easily handled, other errors are unrecoverable and can prevent refueling from proceeding. Error handling operation S410 can define non-safety-critical error conditions and provide exemplary error conditions and possible responses.

[0404] Examples of communication errors include disconnection of communication, unrecognizable received data due to coding errors or syntax errors, or received data outside the permissible range. System errors include the dispatcher or mobile independently detecting a critical system error. Qualitative errors include the quality of communication performance not meeting the required level, or the quality of data integrity or accuracy not meeting the required level.

[0405] The two-way communication process for hydrogen fueling according to the present embodiment may perform specific error handling operations S410 as outlined in the following (1) to (4) for the above-mentioned error conditions.

[0406] (1) In the event that a non-safety critical error occurs and further communication is impossible, the mobile and dispenser may immediately stop refueling but may take safety actions and terminate the session by stopping communication.

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

[0408] (3) In case a non-safety critical error is detected in the Mobile and the communication channel is still operational, the Mobile may send a Terminate Request message to the Dispatcher with the "Action" attribute set to "Stop" and the "Reason" attribute set to an appropriate reason or reason code.

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

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

[0411] Meanwhile, during fueling of the hydrogen fueling system, when a safety problem occurs, urgent action / processing may be required.

[0412] The emergency processing procedure S411 that may be employed in the two-way communication process for hydrogen fueling according to an exemplary embodiment of the present disclosure may be performed as follows.

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

[0414] For safe refueling, the communication must convey the actions or operations that are expected according to the protocol, and the refueling operation needs to be within the safe range of the refueling protocol. However, problems may occur during refueling, causing the refueling system to reach a critical state that must be avoided at all costs. Emergency handling operation S411 allows for the definition of safety-critical emergency conditions and possible actions or operations in response to the emergency condition, and can provide important situations to consider.

[0415] The fueling protocol may define emergency situations related to the protocol, provide detection criteria and performance requirements of mobile bodies or dispensers for emergency situations, and prescribe response procedures S411 to avoid entering dangerous situations.

[0416] In more detail, when a high-pressure condition exceeding a predetermined reference value is detected by a mobile body during a hydrogen fueling process, the mobile body may transmit a first emergency stop request message to the dispenser, the first emergency stop request message including information requesting a fueling stop based on the high pressure (e.g., "Emg: Stop (High Pressure)"). The dispenser may transmit a response message to the mobile body in response to the first emergency stop request message, the response message including information indicating that the dispenser is processing an emergency fueling stop (e.g., "Emg: Stopping").

[0417] In addition, upon receiving the response message or after a preset time has passed since receiving the response message, the mobile body may resend the first emergency stop request message to the dispenser. After emergency stopping fuel filling, the dispenser may send a response message to the mobile body including information indicating that fuel filling has been emergency stopped (e.g., "Emg: Stopped").

[0418] Meanwhile, if the dispenser detects a hydrogen fuel leak during the hydrogen fueling process, the dispenser may transmit a second emergency stop request message to the mobile body, the second emergency stop request message including information indicating that it is processing a fuel filling stop due to the leak (e.g., "Emg: Stopping (Leaking)"). The mobile body may transmit a response message to the dispenser, the response message including information indicating confirmation of the second emergency stop request message (e.g., "Emg: Confirmed").

[0419] In addition, the dispenser may transmit a third emergency stop notification message to the mobile body, the third emergency stop notification message including information indicating that fuel filling has been stopped due to leakage (e.g., "Emg: Stopped (Leak)"). The mobile body may transmit a response message to the dispenser, the response message including information indicating confirmation of the third emergency stop notification message (e.g., "Emg: Confirmed").

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

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

[0422] Emergency notification messages can be sent as TLS or DTLS messages, depending on the technology used for communication.

[0423] Table 20 shows the target, preconditions, and postconditions of the security check-in operation S406.

[0424] [Table 20]

[0425]

[0426] After successfully performing the fueling parameter negotiation operation S405, the fueling protocol may perform the security check-in operation S406 as described above.

[0427] In this case, if the communication physical layer is specified to require a pairing process, the mobile and the dispenser may check the pairing again before dispensing hydrogen in the safety check-in operation S406.

[0428] Even if the communication physical layer is not specified to require a pairing process, the mobile and the dispenser may check the pairing again before dispensing hydrogen in the safety check-in operation S406.

[0429] After receiving a message (e.g., a FuelParamNegores message) from the dispenser indicating the completion of operation S405, if the fueling protocol supports the safety check-in operation S406, the mobile body can send a message (e.g., a SafetyCheckInReq) to the dispenser within a predetermined time interval (e.g., a MessageSequenceTimeout) indicating the start of the safety check-in operation S406.

[0430] In an alternative embodiment, if a message indicating completion of operation S405 is sent by one of the mover and the distributor to the other, the one or the other party that has sent the message may send a new message indicating the start of security check-in operation S406 to the other party.

[0431] According to an exemplary embodiment of the present disclosure, the messages transmitted and received in the security check-in operation S406 may be defined based on the contents of each fueling protocol specified in a standard such as ISO 19885-3, for example.

[0432] According to an exemplary embodiment of the present disclosure, the message sent and received in the security check-in operation S406 may include a value indicating the processing result of the request message as a result element. In this case, for example, the result value provided as the result element may include "OK" in the case of success, "FAILED" in the case of failure, and "Pending" in other cases.

[0433] If all safety conditions are met when the mobile sends the SafetyCheckInReq message to the dispatcher, the result value of the message may be set to "OK".

[0434] If some safety conditions are still not met when the mobile sends the SafetyCheckInReq message to the dispatcher, the result value of the message may be set to "pending".

[0435] After the dispatcher receives the SafetyCheckInReq message, the dispatcher may respond to the mobile by sending a SafetyCheckInRes message along with the safety check parameters within the MessageResponseTimeout period.

[0436] If all safety conditions are met when the dispatcher sends the SafetyCheckInRes message to the mobile, the result value of the message may be set to "OK".

[0437] If some safety conditions are still not met when the dispatcher sends the SafetyCheckInRes message to the mobile, the result value of the message may be set to "pending".

[0438] When the mobile receives a SafetyCheckInRes message with a result value set to “pending”, the mobile may send another SafetyCheckInReq message to the dispatcher within the MessageResponseTimeout time interval.

[0439] When the dispatcher receives a SafetyCheckInRes message with a result value set to “pending”, the dispatcher may send another SafetyCheckInReq message to the mobile within the MessageResponseTimeout time interval.

[0440] If a mobile or dispatcher cannot confirm all safety conditions within a certain time period (eg, UCSafetyCheckInTimeout), the mobile or dispatcher may send an ErrNOtifReq message with the Reason field set to an appropriate error code.

[0441] In an alternative embodiment, the mover or dispenser may send a request message indicating the start of security check-in to the counterpart device / entity, and the counterpart device / entity may respond to the request message for security check-in by sending a response message within a specific time period.

[0442] The objectives, preconditions, and postconditions of the monitoring and control operation S407 are shown in Table 21.

[0443] [Table 21]

[0444]

[0445] After successfully performing the security check-in operation S406, the fueling protocol may perform the monitoring and control operations S407 as described above.

[0446] In case the security check-in operation S406 is omitted, after the fueling parameter negotiation operation S405 is successfully performed, the fueling protocol may perform a monitoring and control operation S407.

[0447] While performing the monitoring and controlling operation S407 , the dispenser may perform all necessary operations to supply fuel to the moving body.

[0448] In the case of utilizing the TCP specification in the fuel filling control and monitoring use case, when the mobile receives a SafetyCheckInRes message, or in an embodiment where the safety check-in operation S406 is omitted, when the mobile receives a FuelParamNegoRes message, the mobile can send a message (e.g., a FuelLoopReq message) to the dispenser requesting the start of the monitoring and control operation S407 within a specific time interval (e.g., a MessageSequenceTimeout).

[0449] In the case of utilizing a black channel (described in connection with the above DTLS solution), after sending the SafetyCheckInRes message, or in an embodiment where the security check-in operation S406 is omitted, after sending the FuelParamNegoRes message, the mobile that can act as a client and the dispatcher that can act as a server can use the NewSessionTicket to initiate session resumption and start the DTLS 1.3 handshake according to RFC 9147. In this case, the NewSessionTicket can be received from the dispatcher.

[0450] After successfully completing the DTLS 1.3 handshake, the mobile may send a message (eg, a FuelLoopReq message) requesting to start the monitoring and control operation S407 to the dispatcher within a specific time interval (eg, a MessageSequenceTimeout).

[0451] In this case, 0-RTT may not be used for DTLS session resumption.

[0452] Both the FuelLoopReq message and its response message (eg, the FuelLoopres message) may be sent in accordance with the DTLS message specification.

[0453] Furthermore, additional requirements may be provided for the black channel approach.

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

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

[0456] Elements included in the FuelLoopReq message may include actions (or operations and / or sequences), reasons, etc. as shown in Table 22. Additional elements not included in Table 22 may be specified by, for example, each fueling protocol standard (such as ISO 19885-3).

[0457] [Table 22]

[0458]

[0459] Elements included in the message (eg, FuelLoopRes message) transmitted and received in operation S407 may include status, cause, result, etc. as shown in Table 23. Additional elements not included in Table 23 may be specified by, for example, each fueling protocol standard (such as ISO 19885-3).

[0460] [Table 23]

[0461]

[0462]

[0463] When a mobile sends a FuelLoopReq message, it may expect the dispenser to perform a certain action, operation, and / or sequence. The mobile may set the "action" element to the desired action, operation, and / or sequence code in the message to the dispenser. The action code may be defined by the fueling protocol.

[0464] After the dispenser receives the FuelLoopReq message (e.g., with "Action" set to "Start"), when the dispenser is ready to start, the dispenser can initiate the fueling process using the negotiation method and respond to the FuelLoopReq message by sending a FuelLoopReq message with "Result" set to "OK."

[0465] After a dispenser receives a FuelLoopReq message (eg, with "Action" set to "Start"), if the dispenser is not ready to start, the dispenser may respond with a FuelLoopReq message with "Result" set to "Pending."

[0466] After the dispenser receives a FuelLoopReq message (e.g., with "Action" set to "Stop"), if the dispenser is ready to stop, the dispenser may stop the fueling process as defined in the fueling protocol and respond with a FuelLoopReq message with "Result" set to "ONGOING."

[0467] After the dispenser receives a FuelLoopReq message (eg, with Action set to Stop), if the dispenser is ready to stop, the dispenser may immediately stop the fueling process and respond with a FuelLoopReq message with Result set to OK.

[0468] After the dispatcher receives the FuelLoopReq message, the dispatcher may respond with a FuelLoopReq message within a specific time interval (eg, MessageSequenceTimeout).

[0469] When the FuelLoopReq message is successfully processed, the dispatcher may send a FuelLoopReq message with "Result" set to "OK".

[0470] When processing of a FuelLoopReq message is unsuccessful, the dispatcher may send a FuelLoopReq message with "Result" set to "Failure" or another appropriate error code.

[0471] The dispenser may send a FuelLoopRes message with the Status set to one of the supported codes, such as listed in Table 23 or specified in the fueling protocol.

[0472] When the fueling process is complete (based on the FuelLoopReq message) and the desired fueling target (or target SoC) is achieved / reached, the dispenser may send a FuelLoopRes message with the Status set to Complete.

[0473] When fueling is stopped for an error-related reason, the dispenser may send a FuelLoopRes message with Status set to Stop_Error and Reason set to the appropriate reason code.

[0474] If the most recent FuelLoopReq message had an "Action" element set to "Stop" and fueling has not completely stopped, the dispenser may send a FuelLoopReq message with "Status" set to "Stop."

[0475] If the most recent FuelLoopReq message had an "Action" element set to "Stop" and fueling has completely stopped, the dispenser may send a FuelLoopReq message with "Status" set to "Stop_Request."

[0476] If a mobile sends a FuelLoopReq message with “Action” set to “Stop” and receives a FuelLoopRes message with “State” set to “Stop”, the mobile may send a FuelLoopRes message with “Action” set to “Stop”.

[0477] If the mobile receives the FuelLoopReq message and fueling has not been completed, the mobile may send the FuelLoopReq message within a specific time interval (eg, MessageSequenceTimeout).

[0478] In the event of a safety-critical event, the mobile or dispenser can immediately send an EmergencyReq message, stop the refueling process, and shut down communications.

[0479] The above description related to operation S407 focuses on an embodiment in which the mobile body requests to start each operation and the distributor responds to the request, but the present disclosure is not limited thereto. In an alternative embodiment of the present disclosure, any mobile body or distributor may first send a message requesting to start operation S407, and the counterpart device / entity may respond to the message requesting to start operation S407, thereby performing operation S407.

[0480] In operation S407, the message sent by the mobile object or the dispenser may include a request for monitoring the status of the hydrogen fueling process. A response message to the monitoring request may include information related to the status of the requested monitoring target.

[0481] In this case, the state and related parameters of the monitoring target may include the parameter set exchanged in operation S405. The state and related parameters of the monitoring target may include the state and parameters related to the mobile object or the dispenser. The state and related parameters of the monitoring target may include the fuel filling state and / or related parameters of the mobile object and / or the dispenser that are changed or maintained by the hydrogen fuel filling process.

[0482] Furthermore, the status of the monitoring target may include the status and / or information of the process itself of performing fuel refueling from the dispenser to the mobile object. For example, the information may include whether the refueling process is ongoing, paused, or completely terminated, and / or whether the refueling process was stopped / terminated due to an error or completed due to achieving a refueling target (because a refueling target SoC has been reached).

[0483] Table 24 shows the target, preconditions, and postconditions of the security checkout operation S408.

[0484] [Table 24]

[0485]

[0486] After the refueling is completed and before the session is terminated before the nozzle is removed from the mobile body, a safety checkout operation S408 may be performed to ensure that the mobile body and the dispenser meet safety conditions. The safety checkout operation S408 may be optional, but it is highly recommended that a dedicated safety checkout process be defined by the refueling protocol to ensure that the desired safety level is ensured in a precise and unambiguous manner.

[0487] During safety checkout operations, information exchange can be used for diagnostic purposes and to establish responsibility when safety-related events occur.

[0488] As described above, once the monitoring and control operation S407 and the associated fueling process are successfully completed, the fueling protocol may proceed to a safety checkout operation S408.

[0489] Regardless of whether a safety checkout is performed, a fueling protocol compliant with ISO 19885-2 may define a set of safety conditions to be confirmed between the mobile body and the dispenser before the nozzle is extracted.

[0490] In the case where the fueling protocol supports safety checkout, after the mobile receives the FuelLoopRes message with "Result" set to "OK" and "Status" prefixed with "Complete" or "Stop", the mobile can request the distributor to start the safety checkout operation S408 message (for example, SafetyCheckOutReq message) through the TLS channel within a certain time interval (for example, MessageSequenceTimeout).

[0491] In this case, when the TCP / TLS channel is released, the mobile can re-establish the TCP / TLS channel with the dispatcher. The re-establishment process can be initiated by a TLS resumption handshake using the NewSessionTicket received before sending the SafetyCheckOutReq message.

[0492] As an alternative embodiment, the message requesting to start operation S408 may be sent by one of the mobile body and the distributor to the other. In this case, the other party may perform operation S408 by responding to the message requesting to start operation S408.

[0493] According to an exemplary embodiment of the present disclosure, the messages transmitted and received in the safety checkout operation S408 may be defined based on the contents of each fueling protocol specified in the ISO 19885-3 standard, for example.

[0494] According to an exemplary embodiment of the present disclosure, the message sent and received in the security checkout operation S408 may include a value indicating the processing result of the request message as a result element. In this case, for example, the result value provided as the result element may include "OK" in the case of success, "Failed" in the case of failure, and "Pending" in other cases.

[0495] If the mobile confirms that all safety conditions are met when the mobile sends the SafetyCheckOutReq message to the dispatcher, the result value of the message may be set to "OK".

[0496] If some safety conditions are still not met when the mobile sends the SafetyCheckOutReq message to the dispatcher, the result value of the message may be set to "pending".

[0497] After the dispatcher receives the SafetyCheckOutReq message, the dispatcher may respond to the mobile by sending a SafetyCheckOutRes message along with the safety check parameters within the MessageResponseTimeout period.

[0498] If the dispatcher confirms that all safety conditions are met when the dispatcher sends the SafetyCheckOutRes message to the mobile, the result value of the message may be set to "OK".

[0499] If some safety conditions are still not met when the dispatcher transmits the SafetyCheckOutReq message to the mobile, the result value of the message may be set to "pending".

[0500] If the mobile receives a SafetyCheckOutRes message with a result value set to “pending”, the mobile may send another SafetyCheckOutReq message to the dispatcher within the MessageResponseTimeout time interval.

[0501] If the dispatcher receives a SafetyCheckOutReq message with a result value set to “pending”, the dispatcher may send another SafetyCheckOutReq message to the mobile within the MessageResponseTimeout time interval.

[0502] When a mobile or dispatcher cannot confirm all security conditions within a given time period (eg, UCS AfetyCheckOutTimeout), the mobile or dispatcher may send another ErrNOtifReq message to the other party with the "reason" set to an appropriate error code.

[0503] In an alternative embodiment, the mover or dispatcher may send a request message indicating the start of security checkout to the counterpart device / entity, and the counterpart device / entity may respond to the request message for security checkout by sending a response message within a specific time period.

[0504] According to an exemplary embodiment of the present disclosure, in the event that a non-safety-critical error is discovered in the monitoring and control operation S407 and fueling is interrupted before completion, the fueling protocol can recover and complete fueling based on a fallback mechanism defined as a backward compatibility in a mechanism that ensures compatibility between the mobile body and the dispenser.

[0505] In this case, for example, the fallback mechanism could be a non-communicating refueling method.

[0506] In an alternative embodiment, in the event that a non-safety critical error is discovered in the monitoring and control operation S407 and fueling is interrupted before completion, the mobile body and the dispenser may again perform some or all of the communication protocol negotiation operation S403, the fueling protocol negotiation operation S404, and the fueling parameter negotiation operation S405.

[0507] In an alternative embodiment, the mobile and the dispenser may reduce the information exchanged during the re-execution of some or all of the communication protocol negotiation operation S403, the refueling protocol negotiation operation S404, and the refueling parameter negotiation operation S405 by utilizing the interoperability information obtained in the discovery and pairing operation S401. For example, if the negotiation is completed and the negotiation determines that the communication state or refueling state is suitable for maintaining the selected protocol, some or all of the communication protocol negotiation operation S403, the refueling protocol negotiation operation S404, and / or the refueling parameter negotiation operation S405 may be re-executed without the previously selected protocol.

[0508] As an alternative embodiment, in the event that a change in the communication environment or a change in the fueling infrastructure is detected as a non-safety-critical error in the monitoring and control operation S407, and fueling is interrupted before completion, the mobile body and the dispenser may again perform some or all of the communication protocol negotiation operation S403, the fueling protocol negotiation operation S404, and the fueling parameter negotiation operation S405.

[0509] The change in the communication environment may include a disconnection of a communication channel.

[0510] Changes in the communication environment may include a situation where received data cannot be recognized or a situation where received data is within an unacceptable range.

[0511] Changes in the communication environment may include situations where the quality of communication services does not meet a required level.

[0512] Changes in the communication environment may include situations where the integrity or accuracy of data exchanged in the communication does not meet a required level.

[0513] The change in the fueling infrastructure may include a case where the change or maintenance of the fueling parameters on the mobile body side does not satisfy a required level even if the fueling parameters on the mobile body side are changed or maintained based on the fueling control parameters on the dispenser side.

[0514] Table 19 shows some of the security conditions checked or monitored in the security check-in operation S406, the monitoring and control operation S407 and / or the security check-out operation S408, but the following items may be additionally or supplementally considered.

[0515] The safety condition may include elements related to safety in both the mobile body and the fuel filling station or dispenser for hydrogen fuel filling and / or coupling states with the nozzle and the socket on both sides for starting hydrogen fuel filling.

[0516] On the hydrogen fuel mobile body side, the pressure and temperature inside the hydrogen tank may also be included.

[0517] On the fuel filling station side, it may include the temperature in the cylinder, the fuel filling pressure, the ambient temperature, etc.

[0518] The safety conditions in the coupling of both sides or the fuel filling path may include the coupling state of the nozzle and the socket, that is, whether the nozzle and the socket are coupled, the coupling state, the leakage state, etc.

[0519] The coupling status of the nozzle and the socket may include information related to whether the coupling is suitable and / or sufficient to perform the hydrogen fueling process.

[0520] exist Figure 4 In an alternative embodiment, safety elements including a minimum status check (ie, whether the nozzle and socket are engaged, the engagement status, etc.) may be checked in the safety check-in operation S406, and the safety check-in operation S406 may be performed before the fueling parameter negotiation operation S405.

[0521] exist Figure 4 In an alternative embodiment, safety elements including a minimum status check (i.e., whether the nozzle and socket are engaged, the engagement status, etc.) may be checked in the safety check-in operation S406, and the remaining safety elements not checked in the safety check-in operation S406 may be negotiated and checked in the fueling parameter negotiation operation S405.

[0522] exist Figure 4 In an alternative embodiment, safety elements including a minimum status check (i.e., whether the nozzle and the socket are engaged, the engagement status, etc.) may be checked in the safety check-in operation S406, and the remaining safety elements not checked in the safety check-in operation S406 may be monitored and checked in the monitoring and control operation S407. In this case, the safety elements may be monitored and checked in the monitoring and control operation S407 regardless of (or independently of) being negotiated and checked in the fueling parameter negotiation operation S405.

[0523] exist Figure 4 In an alternative embodiment, a plurality of security elements including the security element checked in the security check-in operation S406 may be negotiated and checked in the fueling parameter negotiation operation S405.

[0524] exist Figure 4 In an alternative embodiment, multiple safety elements including the safety elements checked in the safety check-in operation S406 may be monitored and checked in the monitoring and control operation S407. In this case, the safety elements may be monitored and checked in the monitoring and control operation S407 regardless of (or independently of) being negotiated and checked in the fueling parameter negotiation operation S405.

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

[0526] Despite Figures 1 to 15 Although not shown in the figure, a processor and a memory may be electrically connected to each component so that the operation of each component may be controlled or managed by the processor.

[0527] At least some of the processes of the fuel refueling communication method according to an embodiment of the present disclosure may be performed by Figure 16 Executed by computing system 3000.

[0528] The computing system 3000 according to an embodiment of the present disclosure may include at least one processor 3100 and a memory 3200, wherein the memory 3200 stores program instructions that instruct the at least one processor 3100 to perform at least one processing step. At least some operations or processing steps of the method according to an embodiment of the present disclosure may be performed by the at least one processor 3100 loading the program instructions from the memory 3200.

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

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

[0531] In addition, the computing system 3000 may include a communication interface 3300 that performs communication through a wireless communication network.

[0532] In addition, the computing system 3000 may further include a storage device 3400 , an input interface 3500 , and an output interface 3600 .

[0533] The components of the computing system 3000 may be connected to each other through the system bus 3700 to communicate with each other.

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

[0535] The communication device / equipment for hydrogen fuel refueling according to an exemplary embodiment of the present disclosure may be a device that is installed on a hydrogen fuel mobile body and / or a dispenser and performs communication between the hydrogen fuel mobile body and the dispenser. The communication device / equipment may include a processor 3100 that receives at least one program instruction from a memory 3200 and executes the at least one instruction.

[0536] The communication controller of the hydrogen fuel mobile object 100 according to the exemplary embodiment of the present disclosure may include a memory 3200 storing at least one instruction and a processor 3100 executing the at least one instruction. The processor 3100 may transmit a request message including information related to an action, operation, and / or process including starting or stopping hydrogen fueling to a dispenser that supplies hydrogen to the hydrogen fuel mobile object, based on a fueling protocol negotiated between the hydrogen fuel mobile object and the dispenser, and receive a response message from the dispenser including information regarding whether the action, operation, and / or process included in the request message has been processed or is ready to be processed.

[0537] The request message may include information related to the initiation action, operation, and / or process of hydrogen fueling, and the response message may include information regarding whether the dispenser is ready to begin hydrogen fueling.

[0538] When the response message indicates that the dispenser is not ready to begin hydrogen fueling, processor 3100 may additionally send a second request message including information related to the initiation action, operation, and / or process of hydrogen fueling.

[0539] The request message may include information related to the stopping action, operation, and / or process of hydrogen fueling, and the response message may include information regarding whether the dispenser has stopped hydrogen fueling.

[0540] When the response message indicates that the dispenser has not completely stopped hydrogen fueling, processor 3100 may additionally send a second request message including information related to the stopping action, operation, and / or process of hydrogen fueling.

[0541] The request message may include a monitoring request for at least one status related to the hydrogen fueling process, and the response message may include information about the at least one status.

[0542] In a state where fueling parameters based on the fueling protocol are negotiated between the mobile and the dispenser, the processor 3100 may check a security state on the mobile or dispenser side by exchanging messages between the mobile and the dispenser before sending a request message.

[0543] When the response message indicates that hydrogen fueling has been completed or stopped, the processor 3100 may check a safety status on the moving body side or the dispenser side by exchanging messages between the moving body and the dispenser before the nozzle is pulled out.

[0544] A communication device / apparatus provided in a dispenser for supplying hydrogen to a hydrogen fuel mobile body according to an exemplary embodiment of the present disclosure may include a processor 3100 that receives at least one program instruction from a memory 3200 and executes the at least one instruction. The processor 3100 may receive a request message including information about an action, operation, and / or process for starting or stopping hydrogen fuel supply from the mobile body when a fuel refueling negotiation between the mobile body and the dispenser is completed, and transmit a response message to the mobile body including information about whether the action, operation, and / or process included in the request message has been processed or is ready to be processed.

[0545] On the other hand, although most of the embodiments described above focus on a method in which the vehicle first transmits the communication protocol or parameters to the distributor, the present disclosure is not limited thereto and may be configured such that the distributor first transmits the communication protocol or the parameters of the distributor to the vehicle. Such an embodiment has substantially the same features as the above-described embodiment, except for variations in the transmitter and receiver.

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

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

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

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

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

Claims

1. A communication method for hydrogen fuel refueling (fuel refueling) performed by a hydrogen fuel mobile object, comprising: sending a request message to a dispenser that supplies hydrogen to the hydrogen fuel mobile object based on a fueling agreement determined through negotiation between the hydrogen fuel mobile object and the dispenser, the request message including information related to an operation including starting or stopping hydrogen fueling; as well as A response message is received from the dispatcher, the response message including information on whether the operation contained in the request message has been processed or is ready to be processed.

2. The communication method for hydrogen fueling according to claim 1, wherein: The request message includes information related to a start operation of the hydrogen fueling, and the response message includes information on whether the dispenser is ready to start the hydrogen fueling.

3. The communication method for hydrogen fueling according to claim 2, further comprising: Based on the response message indicating that the dispenser is not ready to begin the hydrogen fueling, a second request message including information related to the initiation of the hydrogen fueling is additionally sent.

4. The communication method for hydrogen fueling according to claim 1, wherein: The request message includes information related to a stop operation of the hydrogen fueling, and the response message includes information on whether the dispenser has stopped the hydrogen fueling.

5. The communication method for hydrogen fueling according to claim 4, further comprising: Based on the response message indicating that the dispenser has not completely stopped the hydrogen fueling, a second request message including information related to the stop operation of the hydrogen fueling is additionally transmitted.

6. The communication method for hydrogen fueling according to claim 1, wherein: The request message includes a request for monitoring of at least one state related to the hydrogen fueling process, and The response message includes information about the at least one status.

7. The communication method for hydrogen fueling according to claim 1, further comprising: In a state where fuel filling parameters based on the fuel filling protocol are negotiated between the hydrogen fuel mobile object and the dispenser, before sending the request message, a safety status on the hydrogen fuel mobile object side or the dispenser side is checked by exchanging messages between the hydrogen fuel mobile object and the dispenser.

8. The communication method for hydrogen fueling according to claim 1, further comprising: Based on the response message indicating that the hydrogen fuel filling has been completed (Complete) or stopped (Stop), before the nozzle is pulled out, the safety status of the hydrogen fuel mobile body or dispenser side is checked by exchanging messages between the hydrogen fuel mobile body and the dispenser.

9. A communication device for hydrogen fuel refueling, the communication device being arranged in a hydrogen fuel mobile object, the communication device comprising: a memory storing at least one instruction; as well as a processor, executing the at least one instruction, Wherein, the processor is configured to: sending a request message to a dispenser that supplies hydrogen to the hydrogen fuel mobile object based on a fueling agreement determined through negotiation between the hydrogen fuel mobile object and the dispenser, the request message including information related to an operation including starting or stopping hydrogen fueling; as well as A response message is received from the dispatcher, the response message including information on whether the operation contained in the request message has been processed or is ready to be processed.

10. The communication device according to claim 9, wherein: The request message includes information related to the start operation of the hydrogen fueling, and The response message includes information about whether the dispenser is ready to start the hydrogen refueling, The processor is further configured to: Based on the response message indicating that the dispenser is not ready to begin the hydrogen fueling, a second request message including information related to the initiation of the hydrogen fueling is additionally sent.

11. The communication device according to claim 9, wherein: The request message includes information related to the stop operation of the hydrogen fueling, and The response message includes information on whether the dispenser has stopped the hydrogen fueling, The processor is further configured to: Based on the response message indicating that the dispenser has not completely stopped the hydrogen fueling, a second request message including information related to the stop operation of the hydrogen fueling is additionally transmitted.

12. The communication device according to claim 9, wherein: The request message includes a request for monitoring of at least one state related to the hydrogen fueling process, and The response message includes information about the at least one status.

13. The communication device according to claim 9, wherein: The processor is further configured to: In a state where fuel filling parameters based on the fuel filling protocol are negotiated between the hydrogen fuel mobile object and the dispenser, before sending the request message, a safety status on the hydrogen fuel mobile object side or the dispenser side is checked by exchanging messages between the hydrogen fuel mobile object and the dispenser.

14. The communication device according to claim 9, wherein The processor is further configured to: Based on the response message indicating that the hydrogen fuel filling has been completed (Complete) or stopped (Stop), before the nozzle is pulled out, the safety status of the hydrogen fuel mobile body or dispenser side is checked by exchanging messages between the hydrogen fuel mobile body and the dispenser.

15. A communication method for hydrogen fuel refueling (fuel refueling) performed by a dispenser for supplying hydrogen to a hydrogen fuel mobile body, the communication method comprising: receiving a request message from the hydrogen fuel mobile object in a state where a fuel refueling protocol negotiation between the hydrogen fuel mobile object and the dispenser is completed, the request message including information related to an operation including starting or stopping hydrogen refueling; as well as A response message is sent to the hydrogen fuel mobile object, the response message including information on whether the operation included in the request message has been processed or is ready to be processed.

16. The communication method for hydrogen fueling according to claim 15, wherein: The request message includes information related to the start operation of the hydrogen fueling, and The response message includes information regarding whether the dispenser is ready to begin the hydrogen fueling.

17. The communication method for hydrogen fueling according to claim 15, wherein: The response message includes information regarding whether the dispenser is performing the hydrogen fueling or has stopped the hydrogen fueling.

18. The communication method for hydrogen fueling according to claim 17, wherein: When the response message indicates that the dispenser has stopped the hydrogen fueling, the response message includes information as to whether the dispenser stopped the hydrogen fueling based on a stop operation included in the request message from the hydrogen fuel mobile object, or whether the hydrogen fueling was completed because a hydrogen fueling target of the hydrogen fuel mobile object had been achieved.

19. The communication method for hydrogen fueling according to claim 15, wherein: The request message includes a request for monitoring of at least one state related to the hydrogen fueling process, and The response message includes information about the at least one status.

20. The communication method for hydrogen fueling according to claim 15, further comprising: In a state where fuel filling parameters based on the fuel filling protocol are negotiated between the hydrogen fuel mobile object and the dispenser, before receiving the request message, checking a safety state on the hydrogen fuel mobile object side or the dispenser side by exchanging messages between the hydrogen fuel mobile object and the dispenser; as well as Based on the response message indicating that the hydrogen fuel filling has been completed (Complete) or stopped (Stop), before the nozzle is pulled out, the safety status of the hydrogen fuel mobile body or dispenser side is checked by exchanging messages between the hydrogen fuel mobile body and the dispenser.

Images