Bidirectional communication method and apparatus for hydrogen fuel supply

Abstract

A method according to one embodiment of the present invention includes the steps of: broadcasting a DDP (Dispenser Discovery Protocol) request message via a communication network including a dispenser that supplies hydrogen fuel to a mobility device; receiving a DDP response message from the dispenser that includes identification information of the dispenser on the communication network; and performing authentication for pairing between the mobility device and the dispenser using the identification information of the dispenser in the DDP response message.

Description

TECHNICAL FIELD

[0001] The present invention relates to a communication technology for hydrogen fueling from a filling station / dispenser to a hydrogen fueled mobility, and more specifically, to a hydrogen fueling process capable of improving the safety, compatibility, efficiency and reliability of hydrogen fueling, a bidirectional communication method for the hydrogen fueling process, and an apparatus using the same (METHOD AND APPARATUS FOR BIDIRECTIONAL COMMUNICATION FOR HYDROGEN FUELING PROCESS).

BACKGROUND ART

[0002] The content described in this section merely provides background information for the present embodiment, and does not constitute prior art.

[0003] A hydrogen vehicle or a hydrogen electric vehicle refers to a non-polluting vehicle that operates on electric energy generated by the reaction between high-pressure hydrogen stored in the vehicle and air from the atmosphere. A hydrogen electric vehicle is also called a Fuel Cell Electric Vehicle (FCEV). Most hydrogen electric vehicles use hydrogen as an energy source, and generate electricity using a fuel cell system to operate. Hydrogen electric vehicles not only discharge only pure water (H2O) during the process of generating electricity, but also have the function of removing ultrafine dust present in the atmosphere during operation, and thus are attracting attention as an eco-friendly future mobility. Given that hydrogen, the fuel, is infinitely available on Earth, and that the process of producing energy is eco-friendly, this technology is widely spotlighted as a technology with potential for application across all industries.

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

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

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

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

[0008] The hydrogen fuel supply processes, control techniques, and protocols for conventional hydrogen fuel cell vehicles were defined in a time when wired and wireless communication technologies and computing techniques for control were not yet mature, and therefore do not accurately reflect recent advancements in information and communication technology (ICT). Consequently, conventional hydrogen fuel supply technologies for hydrogen fuel cell vehicles are inefficient, slow, and unsuitable for supplying large volumes of hydrogen fuel.

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

[0010] The object of the present invention, in order to solve the aforementioned problems, is to provide a hydrogen fueling process for hydrogen fueled mobility, a communication protocol for the process, a method for negotiating a communication protocol for the hydrogen fueling process, a method for negotiating a fueling protocol, a method for negotiating fueling parameters, a monitoring and control method, a safety check-in method, a safety check-out method, and an apparatus utilizing the same.

[0011] Another object of the present invention relates to error handling and emergency handling methods and apparatus for a hydrogen fuel supply process, which handle errors and / or emergencies occurring during communication protocol negotiation, fueling protocol negotiation, fuel supply parameter negotiation, monitoring and control, safety check-in, and safety check-out processes for a hydrogen fuel supply process.

[0012] Another object of the present invention is to provide a two-way hydrogen fuel supply communication process, a communication protocol negotiation process that takes two-way / one-way communication into consideration, and an apparatus that utilizes the same, which can control hydrogen fuel mobility and dispensers to determine a conventional or advanced communication medium in order to effectively achieve a hydrogen fuel supply goal.

[0013] Another object of the present invention is to propose and provide a process related to the Dispenser Discovery Protocol (DDP) performed between hydrogen fuel mobility and a dispenser. [Means for solving the problem]

[0014] A communication method for hydrogen fuel supply according to one embodiment of the present invention for achieving the above objective is performed by a communication device of hydrogen fueled mobility and includes the steps of: broadcasting a Dispenser Discovery Protocol (DDP) request message via a communication network including a dispenser that supplies hydrogen fuel to mobility; receiving a DDP response message from the dispenser including identification information of the dispenser on the communication network; and performing authentication for pairing between mobility and dispenser using the identification information of the dispenser in the DDP response message.

[0015] A communication method for hydrogen fueling, performed by a mobility communication device according to one embodiment of the present invention, may further include, prior to the step of broadcasting a DDP request message, the step of determining the IP address of the mobility used in the communication network including the dispenser, and the mobility connecting to the communication network via a communication channel based on that IP address.

[0016] In a communication method for hydrogen fuel supply, performed by a mobility communication device according to one embodiment of the present invention, the IP address of the mobility device can be generated based on a random number.

[0017] In a communication method for hydrogen fuel supply performed by a mobility communication device according to one embodiment of the present invention, the DDP request message may include a mobility pairing identifier (ID), and the dispenser identification information included in the DDP response message may include a dispenser pairing identifier (ID).

[0018] During the authentication phase for pairing between the mobility device and the dispenser, the pairing identifier of the mobility device and the pairing identifier of the dispenser can be used to perform the authentication for pairing between the mobility device and the dispenser.

[0019] During the authentication phase for pairing between the mobility device and the dispenser, the pairing identifier of the mobility device and the pairing identifier of the dispenser can be used to perform authentication for pairing between the mobility device and the dispenser via a pairing channel different from the communication channel to which the mobility device is connected to the communication network.

[0020] The authentication process for pairing a mobility device with a dispenser may include the steps of binding a pairing channel for pairing a mobility device with a communication channel using the pairing identifier of the mobility device and the pairing identifier of the dispenser, and performing authentication for pairing a mobility device with a dispenser within the pairing channel using the pairing identifier of the mobility device and the pairing identifier of the dispenser.

[0021] In a communication method for hydrogen fuel supply performed by a mobility communication device according to one embodiment of the present invention, the dispenser identification information included in the DDP response message may include the dispenser's IP address, the dispenser's TCP port number, or the dispenser's UDP port number.

[0022] A communication method for hydrogen fueling, performed by a mobility communication device according to one embodiment of the present invention, may further include a step of negotiating a communication protocol or fuel supply protocol between the mobility and the dispenser after pairing between the mobility and the dispenser has been performed.

[0023] A communication method for hydrogen fueling, performed by a mobility communication device according to one embodiment of the present invention, may further include the step of establishing a secure channel between the mobility and the dispenser in order to negotiate a communication protocol or fuel supply protocol between the mobility and the dispenser, after pairing between the mobility and the dispenser has been performed.

[0024] In a communication method for hydrogen fuel supply performed by a mobility communication device according to one embodiment of the present invention, the step of negotiating a communication protocol or fuel supply protocol between the mobility and the dispenser may include the steps of negotiating a communication protocol between the mobility and the dispenser, negotiating a fuel supply protocol between the mobility and the dispenser based on the communication protocol, and negotiating fuel supply parameters between the mobility and the dispenser based on the fuel supply protocol.

[0025] A communication method for hydrogen fuel supply, performed by a communication device of a dispenser supplying hydrogen fuel to a hydrogen fuel mobility vehicle according to one embodiment of the present invention, may include the steps of: receiving a Dispenser Discovery Protocol (DDP) request message broadcast from the mobility vehicle via a communication network including the dispenser; sending a DDP response message containing the identification information of the dispenser on the communication network to the mobility vehicle; and performing authentication for pairing between the mobility vehicle and the dispenser using the identification information of the dispenser in the DDP response message.

[0026] In the communication method for hydrogen fueling, which is performed by the communication apparatus of the dispenser according to an embodiment of the present invention, the DDP request message may include the pairing identifier (ID, Identification) of the mobility, and the identification information of the dispenser included in the DDP response message may include the pairing identifier (ID, Identification) of the dispenser.

[0027] In the step of performing authentication for pairing between the mobility and the dispenser, the pairing identifier of the mobility and the pairing identifier of the dispenser may be used to perform the authentication for pairing between the mobility and the dispenser.

[0028] In the step of performing authentication for pairing between the mobility and the dispenser, the pairing identifier of the mobility and the pairing identifier of the dispenser may be used to perform the authentication for pairing between the mobility and the dispenser via a pairing channel different from the communication channel through which the mobility is connected to the communication network.

[0029] In the communication method for hydrogen fueling, which is performed by the communication apparatus of the dispenser according to an embodiment of the present invention, the identification information of the dispenser included in the DDP response message may include the IP address of the dispenser, the TCP port number of the dispenser, or the UDP port number of the dispenser.

[0030] The communication method for hydrogen fueling, which is performed by the communication apparatus of the dispenser according to an embodiment of the present invention, may further include a step of negotiating a communication protocol or a fueling protocol between the mobility and the dispenser after pairing between the mobility and the dispenser is performed, and a step of monitoring and controlling the process in which the dispenser supplies hydrogen fuel to the mobility, which is performed based on the fueling protocol.

[0031] A communication device for hydrogen fuel mobility according to one embodiment of the present invention includes a memory for storing at least one instruction and a processor for executing at least one instruction, wherein the processor can broadcast a Dispenser Discovery Protocol (DDP) request message via a communication network that includes a dispenser that supplies hydrogen fuel to the mobility by at least one instruction, and can receive a DDP response message from the dispenser that includes identification information of the dispenser on the communication network, and in the communication device for hydrogen fuel mobility according to one embodiment of the present invention, authentication for pairing between the mobility and the dispenser can be performed using the identification information of the dispenser in the DDP response message.

[0032] In a communication device for hydrogen fuel mobility according to one embodiment of the present invention, the IP address of the mobility used in the communication network including the dispenser is determined before the DDP request message is broadcast, and the mobility can connect to the communication network via a communication channel based on the mobility's IP address.

[0033] In a communication device for hydrogen fuel mobility according to one embodiment of the present invention, a DDP request message may include a mobility pairing identifier (ID, Identification), and the dispenser identification information included in the DDP response message may include a dispenser pairing identifier (ID, Identification).

[0034] In a communication device for hydrogen fuel mobility according to one embodiment of the present invention, when authentication for pairing between mobility and a dispenser is performed, the authentication for pairing between mobility and a dispenser can be performed using the pairing identifier of the mobility and the pairing identifier of the dispenser.

[0035] In a communication device for hydrogen fuel mobility according to one embodiment of the present invention, when authentication for pairing between mobility and a dispenser is performed, the authentication for pairing between mobility and a dispenser can be performed via a pairing channel different from the communication channel to which the mobility is connected to the communication network, using the pairing identifier of the mobility and the pairing identifier of the dispenser.

[0036] In a communication device for hydrogen fuel mobility according to one embodiment of the present invention, the dispenser identification information included in the DDP response message may include the dispenser's IP address, the dispenser's TCP port number, or the dispenser's UDP port number.

[0037] A communication device for a dispenser that supplies hydrogen fuel to a hydrogen fuel mobility vehicle according to one embodiment of the present invention includes a memory for storing at least one instruction and a processor for executing at least one instruction, wherein the processor can receive a Dispenser Discovery Protocol (DDP) request message broadcast from the mobility vehicle via a communication network including the dispenser by at least one instruction, can send a DDP response message to the mobility vehicle including identification information of the dispenser on the communication network, and can perform authentication for pairing between the mobility vehicle and the dispenser using the identification information of the dispenser in the DDP response message. [Effects of the Invention]

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

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

[0040] Furthermore, according to one embodiment of the present invention, rules and procedures necessary for negotiating communication protocols, fuel supply protocols, and exchanging fuel supply parameters to effectively determine whether a conventional or advanced communication medium is used for mobility and dispensers to cooperate in effectively achieving a hydrogen fueling goal can be provided.

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

[0042] Furthermore, according to one embodiment of the present invention, rules and procedures necessary for use cases in which the processes of monitoring and control, safety check-in, and safety check-out are linked with the processes of communication protocol negotiation, fuel supply protocol negotiation, and fuel supply parameter exchange, in order for mobility and dispensers to cooperate to effectively achieve a hydrogen fueling goal can be provided.

[0043] Furthermore, according to one embodiment of the present invention, rules and procedures necessary for use cases in which communication protocol negotiation, fueling protocol negotiation, fueling parameter negotiation, monitoring and control, safety check-in, safety check-out, error handling for the hydrogen fuel supply process, and emergency handling process are linked in order for mobility and dispensers to cooperate to effectively achieve a hydrogen fuel supply goal.

[0044] Furthermore, according to one embodiment of the present invention, it is possible to provide the rules and procedures necessary to implement the processes related to DDP (Dispenser Discovery Protocol) that take place between hydrogen fuel mobility and a dispenser. [Brief explanation of the drawing]

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

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

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

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

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

[0050] When it is mentioned that one component is “connected” or “linked” to another component, it should be understood that it may be directly connected to or linked to the other component, but that other components may be in between. On the other hand, when it is mentioned that one component is “directly connected” or “directly linked” to another component, it should be understood that there are no other components in between.

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

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

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

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

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

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

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

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

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

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

[0061] The Average Pressure Ramp Rate (APRR) represents the average value of the pressure increase rate from the start to the end of hydrogen fuel supply.

[0062] Pre-cooling essentially refers to the process of cooling hydrogen at a hydrogen refueling station before it is supplied as fuel.

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

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

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

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

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

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

[0069] On the other hand, while the following detailed description illustrates embodiments related to hydrogen electric vehicles or fuel cell electric vehicles (FCEVs), the concept of the present invention may be applied to a variety of hydrogen-fueled mobility. This will be obvious to those skilled in the art. Hydrogen-fueled mobility refers to a type of mobility that uses hydrogen as an energy source or generates electrical energy using hydrogen as fuel, and uses this to drive an electric motor. In addition to hydrogen electric vehicles, hydrogen-fueled mobility may also include aerial mobility, as well as industrial trucks, trains, ships, and aircraft that produce electrical energy using hydrogen as fuel and use it for propulsion.

[0070] Furthermore, the bidirectional communication process for hydrogen fuel supply of the present invention may be partially applied not only to hydrogen fuel mobility but also to buildings or facilities that use hydrogen as an energy source.

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

[0072] Furthermore, while we will primarily describe hydrogen fuel cell electric vehicles (FCEVs) as examples of vehicles utilizing a two-way hydrogen fuel supply communication process for convenience, the explanation is not limited to this configuration and can also include hybrid electric vehicles (EVs) and internal combustion engine (ICE) vehicles that use hydrogen as fuel.

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

[0074] In the following specification, some or all of the processes of the communication method, communication protocol negotiation method, hydrogen fuel supply (fueling) protocol negotiation method, hydrogen fuel supply (fueling) parameter negotiation method, hydrogen fuel supply (fueling) method, and hydrogen fuel supply (fueling) control method performed in a dispenser may be performed by a controller, electronic control unit, communication device, or communication control device of the dispenser. Furthermore, some processes of the said methods may be performed by a controller, electronic control unit, communication device, or communication control device of a filling station associated with the dispenser.

[0075] On the other hand, even technologies that were publicly known before the filing date of this invention may be included as part of the structure of the present invention as necessary, and such will be described herein to the extent that it does not impair the spirit of the present invention. However, in describing the structure of the present invention, detailed explanations of publicly known technologies that were publicly known before the filing date and that would be obvious to a person skilled in the art may impair the spirit of the present invention, so explanations of publicly known technologies that are excessively detailed will be omitted. Furthermore, the spirit of this invention is not to assert rights over such publicly known technologies, and the content of publicly known technologies may be included as part of the present invention to the extent that it does not depart from the spirit of the present invention.

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

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

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

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

[0080] In addition to the mechanical devices, structural devices, electrical devices, electronic devices, and communication devices that are basically necessary for a vehicle, the hydrogen electric vehicle 100 may be equipped with an electronic control device 110 for hydrogen fuel supply, a vehicle system 120, a vehicle tank 130, and a receptacle 150.

[0081] The electronic control unit 110 can send and receive signals and data via wired or wireless means to a hydrogen refueling station or a second electronic control unit 210 of the hydrogen refueling station for hydrogen fuel supply, and process these signals to control hydrogen fuel supply on the vehicle side. The electronic control unit 110 can be configured as at least part of other electronic control units mounted on the vehicle, or vice versa, and can be referred to as the first electronic control unit or electronic control unit #1.

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

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

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

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

[0086] The hydrogen refueling station may be equipped with a dispenser 200, a second electronic control unit 210, a refueling station system 220, a hydrogen tank 230, a station box 240, and a nozzle 250.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0101] Fuel supply control logic may be installed inside the dispenser 200 or in the second electronic control unit, and this fuel supply control logic can be used to control the hydrogen fueling process by utilizing state information such as the temperature and pressure of the hydrogen fuel supplied to the vehicle or to the vehicle tank 130, and fuel supply state information such as the CHSS filling rate (SOC, State of Charge).

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

[0103] To meet the minimum safety requirements, simulations can be performed through thermodynamic modeling under various conditions, and the parameters derived from these simulations can be used to implement partial real-time correction methods based on the tethered or MC-formula. Here, the minimum safety requirements may include upper limits on the temperature and pressure conditions of the CHSS and guidelines for the state of charge (SOC).

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

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

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

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

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

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

[0110] The UC1 to UC11 functional blocks can correspond to chronological stages (S401 to S411), as illustrated in Figure 4. In this case, Figure 4 may be understood as an operation flowchart including the chronological stages (S401 to S411).

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

[0112] The aforementioned use cases are functional blocks that collectively provide the entire hydrogen fuel supply system's fueling procedures in a consistent manner for safe and secure fueling communication. The vehicle and dispenser can sequentially execute each use case in a specific order to achieve the hydrogen fuel supply objective.

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

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

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

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

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

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

[0119] Furthermore, the vehicle and dispenser essentially know what communication protocol they will follow. Therefore, any communication following UC-1 is a discovery and pairing procedure or post-conditions of the pairing process, and can only rely on the communication protocol agreed upon for the current use case. If the vehicle or dispenser selects a communication protocol outside the agreed scope, the selected communication will not be performed. In other words, even if the pairing process is successfully completed, approval for hydrogen fuel or approval for hydrogen fuel supply may not be granted.

[0120] All methods used to pair the vehicle with the dispenser are configured not to increase the risk of ignition or explosion beyond an acceptable level. For example, all wired pairing methods are configured to mitigate or prevent the risk of sparks due to electrostatic discharge.

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

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

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

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

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

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

[0127] Furthermore, the hydrogen fuel supply communication stack may include IPv6 (Internet Protocol Version 6) Protocol 520 as a protocol in the OSI 7-tier network layer.

[0128] Furthermore, the hydrogen fuel supply communication stack may include at least one third protocol 530 selected from TCP (transmission control protocol), UDP (user datagram protocol), etc., as a transmission layer protocol of the OSI 7 layer.

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

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

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

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

[0133] Furthermore, the aforementioned hydrogen fuel supply communication stack may be configured in other embodiments to use protocols such as PLC (programmable logic controller) and WLAN as protocols for the data link and physical and network layers, TCP and / or IPv6 as protocols for the transmission and security layers, Binary XML (Binary Extensible Markup Language) as a protocol for the session layer corresponding to the encoding layer, and one of the existing protocols used in electric vehicles as protocols for the representation and application layers. The existing protocols used in electric vehicles may include at least one protocol for DC (direct current) fuel supply, AC (alternate current) fuel supply, Wireless Power Transfer (WPT), Automatic Connection Device Pantograph (ACDP), etc.

[0134] The general communication data items that can be sent and received between the vehicle and the refueling station via the aforementioned hydrogen fuel supply communication stack are shown in Table 1 below.

[0135] [Table 1]

[0136] On the other hand, use case UC1 in the discovery and pairing stage (S401) of Figure 4 allows the device to identify the communication partner (vehicle or dispenser communication module) responsible for controlling the receptacle or nozzle to which it is physically connected. UC1 can also define a method for identifying incompatibilities and define safety device mechanisms.

[0137] In use case UC1, the vehicle and dispenser can look for a common, general communication technology to execute the fuel supply protocol. The search mechanisms provided at the basic data link and physical layers allow the vehicle and dispenser to find each other and initiate communication. Additional pairing procedures are required for the device connected to the fuel supply hose assembly and for a communication channel to be established. If the communication channel does not guarantee correct pairing, for example in the case of wireless communication, a separate pairing channel to transmit pairing information may be required. If pairing is implicitly guaranteed, for example, the communication channel integrated with the hose assembly may suffice.

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

[0139] [Table 2-1] [Table 2-2]

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

[0141] [Table 3]

[0142] Figure 6 is an operation flowchart illustrating in detail a step (S401) according to one embodiment of the present invention.

[0143] Referring to Figure 6, in the Discovery and Pairing stage (S401) of Figure 4, when pairing is performed at UDC Level 2 and UDC Level 3, the vehicle and dispenser exchange pairing IDs and can confirm the other party's pairing ID.

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

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

[0146] Through this transmission-echo-verification method, vehicles and dispensers can use session-specific randomized pairing IDs. This solves the personal information protection issues related to pairing ID exchange. Specifically, trust in the pairing process is established by a subsequent process, and for this purpose, the session-specific pairing ID is included in the data used to establish that trust.

[0147] On the other hand, when supporting secure communications at a specific UCDC level, at least one of the vehicle and dispenser can verify that the pairing provides sufficient information to protect the communication channel for all methods used to pair the vehicle and dispenser. For example, the pairing may include the exchange of encryption keys so that the vehicle and dispenser can protect communications during refueling.

[0148] Incidentally, UCDC Level 1 does not support bidirectional communication, making it impossible to secure the communication channel. Pairing a vehicle and dispenser with UCDC Level 2 and UCDC Level 3 can be configured to provide sufficient information to protect the communication in order to satisfy a specific security level, such as IEC 62443 Security Level 3. IEC 62443 Security Level 3 may be a security level against actors with appropriate resources and appropriate motivations.

[0149] Figure 7 is an illustrative diagram illustrating backward compatibility that can be adopted in a two-way hydrogen fuel supply communication process according to one embodiment of the present invention.

[0150] Referring to Figure 7, hydrogen fuel supply systems can be manufactured as compatible devices with backward compatibility with existing devices, taking interoperability into consideration. When classifying devices based on interoperability, hydrogen fuel supply systems and their communication devices can be classified into Type 0, Type 1, Type 2, and Type 3.

[0151] Type 0 may refer to a device that does not support or receive communications for fuel supply.

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

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

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

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

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

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

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

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

[0160] Furthermore, when a Type 2 device supporting standard #2, which conforms to a predetermined standard, is connected to a Type 0 device or a Type 1 device, the Type 2 device can fall back to a Type 0 device (S620).

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

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

[0163] Furthermore, to support the aforementioned interoperability, the hydrogen fuel supply unit can perform connection compatibility checks. For example, depending on whether or not it supports WLAN, one of the advanced communication methods, the hydrogen fuel supply unit can perform connection compatibility checks in the following scenarios 1 to 3.

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

[0165] In Scenario 2, the dispenser does not support WLAN communication but can support IrDA communication. The dispenser corresponds to a Type 1 device. An FCEV adjacent to the dispenser, as a Type 3 device, cannot detect the dispenser, which is a Type 1 device, by scanning. When the FCEV's receptacle is connected to the nozzle attached to the dispenser's cable, IrDA communication may be initiated between the FCEV and the dispenser.

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

[0167] Figure 8 is an illustrative diagram illustrating backward compatibility that can be adopted in a two-way hydrogen fuel supply communication process according to one embodiment of the present invention.

[0168] Referring to Figure 8, the two-way hydrogen fuel supply communication process of this embodiment does not necessarily select the communication method preferred by the FCEV and dispenser, and can provide rules and principles for the fueling method and communication protocol to fall back to maximize interoperability in order to maximize interoperability.

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

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

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

[0172] According to the configuration described above, if there are two devices having the "same embodiment," the vehicle and the dispenser can both select the best of the two that they support. When a device without communication (hereinafter, "non-communication device") connects to a device that supports unidirectional communication (hereinafter, simply referred to as "unidirectional communication device"), the latter can fall back to a no-communication (No comm) device that does not support any communication method. Also, when two devices that support bidirectional communication are connected, the two devices can maintain their bidirectional communication method. UCDC compatibility may be handled separately here. Furthermore, if a device encounters a non-communication device, it can fall back to no-communication mode. This may also apply to all devices that support bidirectional communication (hereinafter, simply referred to as "bidirectional communication devices").

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

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

[0175] Figure 9 is an illustrative diagram illustrating a communication data usage classification that can be adopted in a two-way hydrogen fuel supply communication process according to one embodiment of the present invention, and backward compatibility in the communication data usage classification.

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

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

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

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

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

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

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

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

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

[0185] DDP can be initiated by a DDP request message [DDPRequest] broadcast by the mobility. The DDPRequest may include the mobility's pairing ID "pairing_id".

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

[0187] Figure 10 is a flowchart illustrating the authentication process of a communication security procedure (S402) that can be adopted in a two-way communication process for hydrogen fuel supply according to one embodiment of the present invention.

[0188] Referring to Figure 10, the mobility device can send a message to the dispenser requesting a list of authorization methods (S1010). The dispenser can send a response message to the mobility device in response to the mobility device's request for a list of authorization methods (S1020). The response message may include information on a list of authorization methods related to procedures such as RFID (radio frequency identification), credit cards, debit cards, or self-authentication procedures.

[0189] Next, the mobility device may send an authentication request message to the dispenser, including a specific method selected from the authentication method list, such as RFID (S1030). The dispenser may send a response message to the mobility device for the authentication request (S1040). This response message may include information indicating that the authentication method selected by the mobility device is working.

[0190] Next, the mobility device may perform authentication using the authentication method previously selected based on the dispenser's response and send a confirmation (Done?) message to the dispenser regarding the successful completion of authentication (S1050). If confirmation of successful authentication has not been received or authentication is not complete, the aforementioned series of steps (S1010 to S1050) may be repeated. Once authentication is complete, the dispenser may send a successful authentication (Done (success)) message to the mobility device (S1090).

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

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

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

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

[0195] In the case of a TLS handshake, the mobility and dispenser must prepare the necessary credentials. The mobility and dispenser can store the certificate chain, the personal key corresponding to the certificate, and the trust anchor certificate in secure storage protected from unauthorized access.

[0196] During the TLS handshake, Mobility can request client authentication from the dispenser by sending a predefined certificate request message. Upon receiving the certificate request message, the dispenser can send a certificate and a CertificateVerify message to Mobility to send the certificate.

[0197] When Mobility sends a certificate request message along with a handshake message such as ServerHello, if the dispenser does not send a certificate verification message along with the certificate, it can abort the TLS handshake by sending a warning message containing a "certificate_required" warning code.

[0198] According to another embodiment of the present invention, the objective, prerequisites, and subsequent conditions of step (S402) may be shown in Table 4 below.

[0199] [Table 4]

[0200] Figure 11 is a flowchart illustrating the communication protocol negotiation stage (S403) that can be adopted in a two-way hydrogen fuel supply communication process according to one embodiment of the present invention.

[0201] Referring to Figure 11, the stage of negotiating a communication protocol (S403) may include the stage of sending a message to the dispenser containing information about a first communication protocol applicable to the mobility (S1110), and the stage of receiving a message from the dispenser containing information about a second communication protocol selected from common communication protocols applicable to both the mobility and the dispenser (S1130).

[0202] Referring to the embodiment in Figure 11, the dispenser receives a message from the mobility device containing information about a first communication protocol applicable to the mobility device (S1110), compares the first communication protocol with the communication protocols applicable to the dispenser, selects a second communication protocol from among the communication protocols that are commonly applicable between the mobility device and the dispenser, and transmits a message to the mobility device containing information about the selected second communication protocol (S1130).

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

[0204] In another embodiment of the present invention, the dispenser first transmits a message to the mobility device containing information about a communication protocol applicable to it, the mobility device selects a specific communication protocol from the common communication protocols, and transmits a message to the dispenser containing information about the selected specific communication protocol.

[0205] The process may further include the step in which the mobility requests information from the dispenser, including a list of applicable communication protocols for the dispenser.

[0206] According to one embodiment of the present invention, the objective, prerequisites, and subsequent conditions of step (S403) may be shown in Table 5 below.

[0207] [Table 5]

[0208] According to one embodiment of the present invention, the content of the messages transmitted and received in step (S1110) may be shown in Table 6 below.

[0209] [Table 6]

[0210] Information regarding the first communication protocol may include at least one of the following: the index of the first communication protocol, the name of the first communication protocol, the version of the first communication protocol, and the preference level for the first communication protocol.

[0211] According to one embodiment of the present invention, the contents of the response messages transmitted and received in step (S1130) may be shown in Table 7 below.

[0212] [Table 7]

[0213] The response message, which includes information regarding the second communication protocol, may further include information regarding the success or failure of the communication protocol negotiations.

[0214] The aforementioned communication protocol negotiation procedure is a procedure for identifying the communication protocol to be followed during the hydrogen fuel supply fueling session, after the vehicle and dispenser have discovered and paired each other on a compatible communication channel. In particular, in this embodiment, the dispenser can take the lead in sending and receiving the communication protocol and parameters with the vehicle.

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

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

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

[0218] In the process of carrying out steps (S403) to (S405) of the present invention, information regarding the interoperability and / or compatibility between mobility and dispensers, which was shared in step (S401) of the discovery and pairing process, may be updated due to changes in the communication environment or changes in environmental variables related to hydrogen fuel supply.

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

[0220] In actual field operations, mobility and dispensers can be configured in various combinations depending on the communication standards, communication modes, fuel supply methods, communication levels, and other parameters related to hydrogen fuel supply. Here, communication standards related to hydrogen fuel supply can include SAE J2601 series, ISO 19885-3, ISO 19885-4, etc. Communication modes can include no communication (No comm.), IrDA, XYZ (ISO), etc. Fuel supply methods can include table-based fuel supply methods such as lookup tables, MC formula-based fuel supply methods, etc. Communication levels can include UCDC levels, and other parameters can include pressure class, CHSS (compressed hydrogen storage system) category, hydrogen fuel supply tables, etc.

[0221] On the other hand, the mobility or dispenser may be configured to further perform a process of falling back to the other party's lower type or lower UDC level depending on the mutual type or UDC level confirmed in the communication protocol negotiation procedure.

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

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

[0224] The dispenser will use the specific protocol selected from the protocol list.<selected protocol> A response message including ) can be sent to the mobility (S1130). The specific protocol is a common protocol selected by the dispenser that is supported by both the dispenser and the mobility and is the highest priority protocol preferred by the mobility, such as the ISO 19885-3-2023-UCDC-3 protocol (see Table 6).

[0225] According to the common protocol, mobility and dispensers can agree on a communication protocol to be used for fuel supply communication.

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

[0227] [Table 8]

[0228] In the aforementioned communication protocol negotiation use case UC3, once a communication protocol is selected, the vehicle and dispenser can activate the implementation of their respective communication protocols and begin fuel supply protocol negotiations. Fuel supply protocol negotiations are the procedure by which the vehicle and dispenser select and agree on the fuel supply protocols to be used in the fuel supply session. At this stage, the vehicle and dispenser can select the communication protocol that the vehicle prioritizes most from among the protocols that both support.

[0229] A hydrogen fuel supply communication protocol negotiation method according to one embodiment of the present invention is a hydrogen fuel supply communication protocol negotiation method performed by a communication control device of a hydrogen fuel mobility 100, comprising the steps of: transmitting a first message to a communication entity associated with a dispenser 200, which includes a list of at least one first fuel supply protocol and at least one first communication protocol required to perform the first fuel supply protocol, to a communication entity associated with a dispenser 200 (S1110); and receiving a response message from the communication entity associated with the dispenser 200, which includes a second communication protocol selected from at least one first communication protocol (S1130).

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

[0231] The first message can include priority information based on the preference level of mobility 100, as shown in Table 6. Furthermore, each message can be defined based on Tables 4 through 6.

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

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

[0234] The response message may include a second communication protocol, which is determined by the device type that falls back based on interoperability and backward compatibility between the mobility 100 and the dispenser 200, from among several first communication protocols required by the control device of the dispenser 200 to execute the first fuel supply protocol.

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

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

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

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

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

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

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

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

[0243] In another embodiment of the present invention, an embodiment may be provided in which the dispenser first sends a message to the mobility containing information about its applicable fuel supply protocols, the mobility selects a specific fuel supply protocol from among the common fuel supply protocols, and sends a message to the dispenser containing information about the selected specific fuel supply protocol.

[0244] This may further include a step in which the mobility requests information from the dispenser, including a list of fuel supply protocols applicable to the dispenser.

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

[0246] [Table 9]

[0247] According to one embodiment of the present invention, the content of the messages transmitted and received in step (S1210) may be shown in Table 10 below.

[0248] [Table 10]

[0249] Information regarding the first fuel supply protocol may include at least one of the following: the index of the first fuel supply protocol, the name of the first fuel supply protocol, the version of the first fuel supply protocol, the sub-protocols of the first fuel supply protocol, and the preference level for the first fuel supply protocol.

[0250] According to one embodiment of the present invention, the contents of the response messages transmitted and received in step (S1230) may be shown in Table 11 below.

[0251] [Table 11]

[0252] Messages containing information regarding the second fuel supply protocol may further include information on the success or failure of the fuel supply protocol negotiations.

[0253] The content of the message transmitted in step (S1210) according to one embodiment of the present invention may be shown in Table 12 below.

[0254] [Table 12]

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

[0256] In another embodiment of the present invention, the dispenser may proactively send and receive its own communication protocols and parameters with the mobility instead of the mobility, and may prioritize and provide the mobility with communication protocols supported by the dispenser.

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

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

[0259] [Table 13]

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

[0261] [Table 14]

[0262] According to Table 14, when the dispenser fails to detect a compatible protocol from the fueling protocol list supported by the mobility received from the mobility, the dispenser may transmit a response message including information indicating that there is no common protocol (for example, FAIL_NO_COMMON_PROTOCOL) in the ResultCode field to the mobility.

[0263] The examples of Table 13 and Table 14 may be similarly applied to the case where the dispenser selects the second communication protocol from the common communication protocols and responds to the mobility in step (S1130) of FIG. 11.

[0264] FIG. 13 is a flowchart for explaining a fueling parameter exchange / negotiation step (S405) that can be employed in the bidirectional hydrogen fueling communication process according to an embodiment of the present invention.

[0265] The fueling parameter exchange / negotiation step (S405) may include a step in which the mobility and the dispenser exchange detailed parameters required to transition to the fueling protocol with each other.

[0266] Referring to FIG. 13, the step of negotiating fueling parameters (S405) may include a step (S1310) of transmitting a message including information on mobility-side fueling parameters required by the second fueling protocol selected as a result of fueling protocol negotiation (S404) to the dispenser, and a step (S1350) of receiving a message including dispenser-side compatibility information for the mobility-side fueling parameters from the dispenser.

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

[0268] In step (S1310), the mobility device sends a message containing information about the fuel supply parameters on the mobility side, and the Accepted field for the relevant parameters <pending>It can be sent to the dispenser while remaining in that setting.

[0269] Similarly, the dispenser sends a message containing information about the fuel supply parameters on the dispenser side in step (S1330), and the Accepted field for the relevant parameters <pending>It can be sent to Mobility while remaining in that setting.

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

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

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

[0273] The mobility device and dispenser can reach an agreement on all parameters by repeatedly sending and receiving messages and responding to those messages.

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

[0275] Here, compatibility support parameters include pressure class, CHSS category, etc., physical property parameters include maximum allowable CHSS pressure, maximum allowable CHSS temperature, maximum allowable speed, CHSS volume, etc., monitoring parameters include current CHSS pressure, current CHSS temperature, etc., and acceptance-related parameters may include information indicating whether or not it is accepted, for example, a parameter indicating yes (true) or no (false). The aforementioned parameters may each have information about one of the pre-specified levels or settings, and information about different or identical main UCDC levels.

[0276] On the other hand, the dispenser has parameters that can be supported (<DIS’s parameters> (In a simplified way)<DIS’s params> Information regarding the mobility and the mobility parameters can be received, and an OK message can be sent to the mobility indicating acceptance (S1330, S1370).

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

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

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

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

[0281] Compatibility parameters may include, for example, pressure class and fuel supply transmission temperature; physical characteristics may include, for example, maximum CHSS pressure and maximum flow rate; fuel supply targets may include target SOC and target CHSS pressure; and monitoring parameters may include current CHSS temperature and ambient temperature.

[0282] If compatible parameters cannot be found and fuel supply cannot be continued, the FCEV can return to the communication protocol negotiation phase to attempt negotiation on other protocols or act to halt fuel supply by the dispenser. Furthermore, in the communication protocol negotiation phase to which it returns due to the failure of the fuel supply parameter exchange phase, the FCEV may be configured to exclude the protocols that failed in the fuel supply parameter exchange phase and propose a set of supported protocols to the dispenser.

[0283] Once a fuel supply protocol is negotiated according to the aforementioned use case (UC-4), the vehicle and dispenser can negotiate specific parameters regarding the fuel supply protocol, communicate static or dynamic states, and exchange detailed fuel supply parameters to determine fuel supply targets. If fuel supply parameter negotiation fails due to incompatibility, they can return to UC-3 to select another fuel supply protocol, or return to UC-1 to select another communication protocol, and if these are not successfully performed, the current communication can be terminated.

[0284] According to the configuration described above, a certain fuel supply protocol may be performed on a non-communication basis. Unidirectional IrDA may be required to perform a certain fuel supply protocol. Bidirectional communication may be required to perform a certain fuel supply protocol. Both bidirectional communication and unidirectional IrDA may be required to perform a certain fuel supply protocol.

[0285] A predetermined UCDC level or a higher UCDC level may be required for a certain fueling protocol to be executed. At least one or more fueling protocols may be proposed based on the make or type of the hydrogen electric vehicle and the make or type of the dispenser. The proposed fueling protocols may be proposed with different priorities. While taking into account the priorities of the proposed fueling protocols, the communication protocol and the fueling protocol between the hydrogen electric vehicle and the dispenser may be finally determined based on whether the communication protocol required by the fueling protocol is supported by the hydrogen electric vehicle and / or the dispenser.

[0286] In another embodiment of the present invention, either the mobility or the dispenser may first transmit fueling parameters to the other party, and the other party may retain acceptable parameters among the received fueling parameters, modify unacceptable parameters, and respond with a message containing newly reconfigured fueling parameters.

[0287] In another embodiment of the present invention, the mobility and the dispenser may perform parameter negotiation in stages. The mobility and the dispenser may first negotiate some of the parameters, and perform an exchange / negotiation process for each sub-parameter of the parameters for which an agreement has been reached.

[0288] In another embodiment of the present invention, each message containing fueling parameters may be set such that if a response message is not received within a preset message processing time, it is considered that no agreement has been reached.

[0289] Table 15 below shows the content of a message including fueling parameters on the mobility side according to an embodiment of the present invention.

[0290]

Table 15

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

[0292] [Table 16]

[0293] During the fuel supply parameter negotiation phase (S405), the mobility and dispenser may generate and send a message to the other party containing a range of values ​​for the fueling parameters that can be supported.

[0294] Parameters may include physical characteristic-related parameters (simply called "physical parameters"), monitoring parameters, safety policy-related parameters, acceptance-related parameters, and so on.

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

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

[0297] Here, physical parameters include fuel delivery temp., maximum fuel delivery pressure, maximum fuel delivery temperature, minimum fuel delivery temperature, and maximum fuel delivery speed; monitoring parameters include current fuel delivery temperature and ambient temperature; fuel delivery target-related parameters include selected fueling table, target SOC, target final CHSS pressure, target final CHSS temperature, target APR, and expected fuel delivery time; and acceptance-related parameters may include parameters such as "accepted". The aforementioned parameters may each contain information about either a preset level or a set value, and information about different or identical main UCDC levels.

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

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

[0300] Furthermore, after receiving a fuel supply parameter negotiation request message, if the dispenser discovers that it is incompatible with the vehicle's fuel supply parameters, the dispenser may respond to the FCEV by sending a fuel supply parameter negotiation response message with the "Result" set to "Failure" to indicate incompatibility with the vehicle in question (FCEV). The result indicates the value and information contained in the resultcode field, while failure is a failure at a specific point in time and may be expressed as an expression indicating incompatibility, such as "fail_incompat".

[0301] Furthermore, after receiving a fuel supply parameter negotiation request message, if the FCEV discovers that the dispenser's fuel supply parameters are incompatible, the FCEV can send an error notification request message to the dispenser, along with a predefined "reason" set for each error code, to indicate the incompatibility to the dispenser.

[0302] On the other hand, before commencing fuel supply, the vehicle and dispenser can be verified to ensure all safety conditions are met through a Safety Check-in use case (UC6). While this step is optional, it is preferable to define a dedicated Safety Check-in procedure in the fuel supply protocol to ensure the desired level of safety in a precise and explicit manner.

[0303] Figure 14 is a conceptual diagram illustrating a table of parameters transmitted from the mobility device to the dispenser side in a fuel supply parameter negotiation / exchange process according to one embodiment of the present invention.

[0304] Figure 15 is a conceptual diagram showing a table of parameters transmitted from the dispenser to the mobility side in a hydrogen fuel supply parameter negotiation / exchange process according to one embodiment of the present invention.

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

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

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

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

[0309] In a communication parameter exchange method for hydrogen fuel supply according to one embodiment of the present invention, at least one or more first hydrogen fuel supply method compatibility may include at least one of the following: the pressure class of mobility 100 and the fuel supply tank category.

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

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

[0312] In a communication parameter exchange method for hydrogen fuel supply according to one embodiment of the present invention, the first monitoring parameter may include at least one of the following: current CHSS pressure and current CHSS temperature.

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

[0314] In a communication parameter exchange method for hydrogen fuel supply according to one embodiment of the present invention, at least one second physical characteristic may include at least one of the following: Max Fuel Delivery Pressure, Max Fuel Delivery Temperature, Min Fuel Delivery Temperature, and Max Fuel Delivery Flow Rate.

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

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

[0317] In a communication parameter exchange method for hydrogen fuel supply according to one embodiment of the present invention, the second monitoring parameter may include at least one of the following: current fuel delivery temperature and ambient temperature.

[0318] Mobility 100 can provide first parameters compatible with the UCDC levels negotiated during the protocol negotiation process in a table format in stages (S1310).

[0319] The dispenser 200 can provide a second parameter in table form in stages (S1330) that is compatible with the UCDC level negotiated during the protocol negotiation process. In this case, the second parameter may be provided including a message indicating acceptance of the first parameter provided in stage (S1310).

[0320] If Mobility 100 or Dispenser 200 fails to accept the exchanged parameters, Mobility 100 may resume the protocol negotiation process. If Mobility 100 or Dispenser 200 still fails to accept the exchanged parameters, Mobility 100 may terminate the fuel supply session.

[0321] In a protocol negotiation process that is performed again following a parameter exchange process that failed because mobility 100 or dispenser 200 did not accept the exchanged parameters, mobility 100 may propose a supported protocol suite other than the protocol provided in the failed parameter exchange process.

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

[0323] [Table 17]

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

[0325] [Table 18]

[0326] A communication method according to one embodiment of the present invention may further include a step of renegotiating at least one of the communication protocol and fuel supply parameters if, as a result of fuel supply parameter negotiation (S405), the fuel supply parameters are incompatible between the mobility and the dispenser.

[0327] In this case, the renegotiation stage in the communication method according to one embodiment of the present invention can be repeated by performing steps (S403), (S404), and (S405). For example, it is possible to return to step (S403), perform the renegotiation from step (S403), and then perform steps (S404) and (S405) in sequence again. In yet another embodiment, it is also possible to return to step (S404), perform the renegotiation from step (S404), and then perform steps (S405) in sequence again.

[0328] The renegotiation step in the communication method according to another embodiment of the present invention may simplify steps (S403), (S404), and (S405), or omit some of the processes. Alternatively, steps (S403) and (S404) may be combined to negotiate the communication protocol and the fuel supply protocol together. For example, the communication protocol and the fuel supply protocol may be negotiated together based on a protocol list that includes the communication protocol and the fuel supply protocol together, based on the compatibility and / or interoperability information obtained in step (S401) to determine whether the communication protocol and the fuel supply protocol can support each other.

[0329] The step of renegotiating using a communication method according to another embodiment of the present invention may be performed based on the remaining list of communication protocols and fuel supply protocols, excluding the communication protocol or fuel supply protocol selected in steps (S403) and (S404).

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

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

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

[0333] Furthermore, referring to Figure 4, a safety check-in stage (S406) that can be adopted in a two-way hydrogen fuel supply communication process according to one embodiment of the present invention is illustrated.

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

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

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

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

[0338] The mobility unit and dispenser can send and receive messages for coupler inspection. The mobility unit can transmit a message to the dispenser containing information indicating the result of its own coupler inspection (e.g., Mobility: OK), and the dispenser can transmit a message to the mobility unit containing information indicating the result of its own coupler inspection (e.g., DP: OK).

[0339] Furthermore, the mobility unit and the dispenser can send and receive messages related to gas leak checks. In the process of sending and receiving leak check-related messages, the dispenser can transmit information to the mobility unit indicating that a leak check is in progress (ongoing). The mobility unit can then transmit information to the dispenser unit indicating that it is waiting for the leak check results (waiting). Once the leak check is complete, the dispenser can transmit a message to the mobility unit requesting the measured tank volume along with leak check completion information (Done).

[0340] Additionally, the dispenser can send messages to the mobile unit for immobilized status checks, and the mobile unit can send messages to the dispenser indicating that it is ready for a status check.

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

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

[0343] Step (S407) is a monitoring and control step that can be adopted in a two-way hydrogen fuel supply communication process according to one embodiment of the present invention.

[0344] During the monitoring and control phase (S407), the mobility and / or dispenser can monitor the fuel supply status and control fuel supply as needed. Once all safety checks are confirmed, the mobility and dispenser can begin fuel supply based on the selected fuel supply protocol using the given parameters. During fuel supply, the mobility and dispenser exchange various measurement data to understand the fuel supply status and can act to detect the occurrence of safety-critical accidents as quickly as possible.

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

[0346] To describe the monitoring and control phase (S407) in more detail, for example, a mobility unit including another mobility unit can send a message to a dispenser to start fuel supply control, and in response, the dispenser can send a message to the mobility unit including confirmation information (e.g., OK).

[0347] Furthermore, the mobility can send a message to the dispenser containing information about its own fueling loop (e.g., x, y, z), and the dispenser can provide the mobility with a message containing information about its own fueling loop corresponding to the mobility's fueling loop (e.g., a, b, c).

[0348] Additionally, the mobility unit can send a fueling control request message to the dispenser containing information to slow down or reduce the amount of fuel supplied, and the dispenser can send a response message to the mobility unit containing information indicating a decrease in the fueling status (e.g., slowing).

[0349] Furthermore, the mobility unit can send a fuel supply control request message to the dispenser requesting a interruption of fuel supply, and the dispenser can send a fuel supply status response message to the mobility unit indicating whether or not fuel supply is interrupted or has been interrupted (stopping / stopped).

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

[0351] Control-related request messages sent from the mobility unit to the dispenser may include information and parameters regarding fuel supply, such as start, pause, resume, and terminate. Reporting-related messages sent from the mobility unit to the dispenser may also include information and parameters regarding the current tank temperature, current tank pressure, etc.

[0352] Messages related to reporting transmitted from the dispenser to the mobility unit may include information and parameters such as status information, current ambient temperature, current pressure ramp rate (PRR [MPa / min]), delivered fuel flow rate (g / sec], current fuel delivery temperature, pre-cooling temperature, current fuel delivery pressure, whether full-fill (fully filled) is in use, whether the cooling dispenser is in use, whether fallback is in use, reason for fuel supply interruption, and the current amount of hydrogen delivered.

[0353] The messages associated with target parameter updates sent from the dispenser to the mobility unit may include information and parameters such as target final tank pressure, target final tank temperature, target fuel supply APR, target SOC, current SOC, and estimated remaining duration.

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

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

[0356] A Safety Check-out step (S408) that can be adopted in a two-way hydrogen fuel supply communication process according to one embodiment of the present invention may be performed as follows: The mobility and dispenser can verify through the Safety Check-out step (S408) that all necessary safety conditions are met before separating the dispenser nozzle from the receptacle. In other words, the mobility and dispenser can verify that it is completely safe for the user or operator to separate the nozzle from the mobility after fuel supply is complete.

[0357] For example, after Mobility receives a fuel supply loop response message from the dispenser where “result” is set to “OK”, “status” is set to “finished”, or the prefix is ​​“stopped”, if the hydrogen fuel supply protocol supports safe checkout, Mobility can initiate safe checkout and send a safe checkout request message to the dispenser within the message sequence setting time to perform the safe checkout stage (S408).

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

[0359] To elaborate on the aforementioned safety checkout stage (S408), for example, the mobility unit can send a message to the dispenser containing information about the coupler inspection result (e.g., OK), and the dispenser can send a message to the mobility unit containing information indicating that the coupler inspection is in progress (e.g., Ongoing).

[0360] Furthermore, the mobility device can send a message to the dispenser containing coupler inspection results (e.g., OK), and the dispenser can send a message to the mobility device containing coupler inspection completion information (e.g., Done).

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

[0362] During the aforementioned safe checkout phase (S408), the report message that the dispenser sends to the mobility may include information and parameters regarding the coupler unlock status. Coupler unlock status information may include information regarding locked, unlocked, icing, problem, etc.

[0363] If fuel supply is completed and the nozzle is safely separated according to the aforementioned hydrogen fuel supply protocol, or if a non-safety-critical issue occurs during another use case, the termination use case (UC9) can be performed.

[0364] A termination step (S409) that can be adopted in a two-way hydrogen fuel supply communication process according to one embodiment of the present invention may be carried out as follows.

[0365] The termination phase (S409) is the final stage of fuel supply, in which the mobility, including the mobility, and the dispenser can complete all stages (S409) of hydrogen fuel supply by exchanging information regarding fuel supply results concerning fuel supply performance and methods, and / or information regarding the reasons for any unexpected interruption of fuel supply. The termination use case may also be configured to handle any non-safety-critical issues that may arise.

[0366] For example, after the mobility receives a safety checkout response message from the dispenser with the "result" set to "DONE," or a fuel supply loop response message with the "status" set to "finished," or with the prefix "stopped," the mobility can transmit a termination request message to the dispenser to complete the termination phase (S409).

[0367] Regarding the final stage (S409), for example, to explain in more detail, a mobility device, including another mobility device, may send a message to a dispenser inquiring about how much fuel has been supplied. In response to the mobility device's inquiry message, the dispenser may send a response message to the mobility device containing information (e.g., X gram) about the amount of hydrogen supplied.

[0368] Additionally, the mobility unit can send a confirmation request message to the dispenser upon completion of fuel supply, and the dispenser can send a goodbye message to the mobility unit as a response to the confirmation request message.

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

[0370] Book-keeping information may include all information related to hydrogen fuel supply recorded in mobility and dispensers by established rules and policies across all fueling sessions for hydrogen fuel supply and prior to the completion of Use Case 9 (UC9) termination phase (S409).

[0371] Bookkeeping or summary information may include information on how much fuel was supplied and what reports were generated. Report messages sent from mobility to dispensers may include information and parameters on the current tank temperature and current tank pressure, while report messages sent from dispensers to mobility may include information on the final state of charge (SOC), final mean fuel delivery rate (APR), final measured tank pressure, actual fuel delivery time, and actual amount of hydrogen delivered.

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

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

[0374] [Table 19-1] [Table 19-2]

[0375] On the other hand, error handling use case UC10 is a functional block for handling situations where a non-safety-critical error occurs, such as terminating a fuel supply procedure in a manner similar to normal termination or suddenly interrupting communication.

[0376] An error handling step (S410) that can be adopted in the two-way hydrogen fuel supply communication process according to one embodiment of the present invention may be carried out as follows.

[0377] The error handling stage (S410) may define error conditions related to the fuel supply protocol and provide detection criteria, and if detected, may include a response process that includes notification, termination process, and fallback mechanism.

[0378] The error handling phase (S410) may be applied when a non-safety-critical error occurs and further communication is impossible. In other words, the mobility and dispenser, including the mobility, can handle any non-safety-critical error that occurs during fuel supply in the error handling phase (S410). In other words, the mobility and dispenser can immediately interrupt fuel supply, temporarily suspend the previously operating use case, and then proceed to the termination use case (UC9).

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

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

[0381] The aforementioned termination request messages may be transmitted in the event of non-critical communication errors, system errors, or qualitative errors, unless recovery is impossible.

[0382] In other words, for successful fuel supply, communication must exhibit expected behavior according to the protocol, and fuel supply operation should be within the acceptable range of the fuel supply protocol. However, in reality, a variety of abnormal events can occur. Some of these errors are minor and can be easily handled, while others cannot be recovered from and make it impossible to continue fuel supply. Therefore, in the error handling stage (S410), non-safety-critical error conditions are defined, and exemplary error conditions and possible responses are provided.

[0383] Examples of communication errors include disconnections, inability to recognize received data due to encoding or syntax errors, or receiving data being within an unacceptable range. System errors may include situations where the dispenser or mobility itself detects a significant system error. Qualitative errors may include situations where the quality of communication performance or the quality of data integrity or precision does not meet the required standards.

[0384] The two-way hydrogen fuel supply communication process of this embodiment can perform the following specific error handling steps (S410) in response to the aforementioned error conditions: (1) to (4).

[0385] (1) If a non-safety-critical error occurs and further communication becomes impossible, the mobility and dispenser may immediately cease fuel supply, take safe measures to terminate communication and end the session.

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

[0387] (3) If a non-safety-critical error is detected by the mobility and the communication channel is still operational, the mobility may transmit a termination request message to the dispenser with “Action” set to “Cancel” and “Reason” set to an appropriate reason code.

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

[0389] As described above, the two-way hydrogen fuel supply communication process, including the fuel supply protocol, defines error conditions related to the fuel supply protocol, provides detection criteria, and, if an error is detected by the detection criteria, can perform an error handling stage (S410) including notification, termination stage (S410), and fallback mechanism.

[0390] On the other hand, if a safety-critical problem occurs during fuel supply in a hydrogen fuel supply system, an emergency response may be required.

[0391] An emergency handling step (S411) that can be adopted in the two-way hydrogen fuel supply communication process according to one embodiment of the present invention may be carried out as follows.

[0392] The emergency response phase (S411) may define essential safety conditions requiring emergency response during fuel supply and may include response processes to prevent essential safety accidents.

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

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

[0395] Specifically, if the mobility system detects a high-pressure condition exceeding a previously set threshold during the hydrogen fuel supply phase (S411), the mobility system may send a first emergency stop request message to the dispenser containing information requesting the cessation of fuel supply due to the high pressure (e.g., Emg:Stop(High Pressure)). The dispenser may send a response message to the mobility system containing information indicating that it is processing an emergency fuel supply cessation in response to the first emergency stop request message (e.g., Emg:Stopping).

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

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

[0398] Furthermore, the dispenser may send a third emergency stop notification message to the mobility unit, which may contain information indicating that it has handled a fuel supply interruption due to a leak (e.g., Emg:Stopped(leaking)). The mobility unit may send a response message to the dispenser, which may contain information indicating that it has acknowledged the third emergency stop notification message (e.g., Emg:Confirmed).

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

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

[0401] The aforementioned emergency notification message may be sent as a TLS or DTLS message, depending on the technology used for communication.

[0402] Referring further to Figure 4, the objectives, prerequisites, and subsequent conditions of the safety check-in stage (S406) can be shown in Table 20 below.

[0403] [Table 20]

[0404] As previously mentioned, once the fuel supply parameter negotiation phase (S405) is successfully completed, the fuel supply protocol can proceed to the safety check-in phase (S406).

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

[0406] In this case, even if the communication physical layer is not specified to require a pairing procedure, the mobility and dispenser can check the pairing again before dispensing hydrogen at the safety check-in stage (S406).

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

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

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

[0410] According to one embodiment of the present invention, messages transmitted and received during the secure check-in phase (S406) may include a result value as a result element, which is the result of processing the request message. In this case, the result value that may be provided as the result element may include, for example, "OK" if successful, "FAILED" if unsuccessful, and "PENDING" otherwise.

[0411] When Mobility sends a SafetyCheckInReq message to the dispenser, if all safety conditions are met, the result value of that message may be set to "OK".

[0412] When Mobility sends a SafetyCheckInReq message to the dispenser, if certain safety conditions have not yet been met, the result value of that message may be set to "PENDING".

[0413] After the dispenser receives the SafetyCheckInReq message, it can send a SafetyCheckInRes message to the mobility device along with the safety check parameters within the MessageResponseTimeout time interval.

[0414] When the dispenser sends a SafetyCheckInRes message to the mobility device, if all safety conditions are met, the result value of that message may be set to "OK".

[0415] When the dispenser sends a SafetyCheckInRes message to a mobility device, if certain safety conditions have not yet been met, the result value of that message may be set to "PENDING".

[0416] If a SafetyCheckInRes message with a result value set to "PENDING" is received, Mobility may send further SafetyCheckInReq messages to the dispenser within the MessageResponseTimeout period.

[0417] If a SafetyCheckInReq message with a result value set to "PENDING" is received, the dispenser may send further SafetyCheckInReq messages to the mobility within the MessageResponseTimeout period.

[0418] If a mobility device or dispenser cannot confirm all safety conditions within a specified time (e.g., UCSafetyCheckInTimeout), it may send an ErrNotifReq message with the "reason" field set to the appropriate error code.

[0419] As an alternative embodiment, the mobility or dispenser may send a request message to the other party indicating the commencement of a safety check-in, and the other party may send a response message to the safety check-in request message within a predetermined time interval.

[0420] Referring further to Figure 4, the objectives, prerequisites, and subsequent conditions for the monitoring and control phase (S407) can be shown in Table 21 below.

[0421] [Table 21]

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

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

[0424] While the monitoring and control phase (S407) is being performed, the dispenser can perform all necessary steps to refuel the mobility.

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

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

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

[0428] In this case, 0-RTT does not need to be used for DTLS Session Resumption.

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

[0430] In addition, there may be additional requirements necessary for the black channel scheme.

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

[0432] The fuel supply protocol can identify static or dynamic data contained within FuelLoopReq and FuelLoopRes. This static or dynamic data is defined to monitor the fuel supply status and exchange safety-related information.

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

[0434] [Table 22]

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

[0436] [Table 23]

[0437] When a mobility device sends a FuelLoopReq message, the dispenser may be expected to perform an action. The mobility device can send the message with the desired action code set to "action". The action code may be defined by the fuel supply protocol.

[0438] After receiving a FuelLoopReq message (for example, with "action" set to "start"), once the dispenser is ready to start, it can initiate the fuel supply procedure using the negotiated method and send back a FuelLoopRes message with "result" set to "OK".

[0439] If a dispenser has not yet finished preparing to start after receiving a FuelLoopReq message (for example, with "action" set to "start"), the dispenser may reply with a FuelLoopRes message with "result" set to "pending".

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

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

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

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

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

[0445] The dispenser can send a FuelLoopRes message where "status" is set using one of the supported codes specified in Table 23 or the fuel supply protocol.

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

[0447] If the dispenser stops supplying fuel due to an error, it can send a FuelLoopRes message with "status" set to "stop_error" and "reason" set to the appropriate reason code.

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

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

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

[0451] If a mobility device receives a FuelLoopRes message and refueling is not yet complete, the mobility device may transmit a FuelLoopReq message within a predetermined time interval (e.g., MessageSequenceTimeout).

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

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

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

[0455] In this case, the conditions and related parameters that may be subject to monitoring requests may include a set of parameters that are exchanged in step (S475). The conditions and related parameters that may be subject to monitoring requests may include the conditions and parameters of the mobility or dispenser. The conditions and related parameters that may be subject to monitoring requests may include the fuel supply conditions and / or related parameters of the mobility and / or dispenser that are changed or maintained by the hydrogen fuel supply procedure.

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

[0457] Furthermore, referring to Figure 4, the objectives, prerequisites, and subsequent conditions of the safe checkout stage (S408) can be shown in Table 24 below.

[0458] [Table 24]

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

[0460] Information exchanged during the secure checkout phase may be used for the purpose of diagnosis and accountability in the event of a security-related incident.

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

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

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

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

[0465] As an alternative embodiment, a message requesting the commencement of stage (S408) may be sent to the other party by either the mobility device or the dispenser. In this case, the other party may perform stage (S408) by responding to the message requesting the commencement of stage (S408).

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

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

[0468] If, by any chance, Mobility sends a SafetyCheckOutReq message to the dispenser, and Mobility confirms that all safety conditions are met, the result value of that message may be set to "OK".

[0469] If, by any chance, Mobility sends a SafetyCheckOutReq message to the dispenser, and several safety conditions have not yet been met, the result value of that message may be set to "PENDING".

[0470] After the dispenser receives the SafetyCheckOutReq message, it can respond by sending a SafetyCheckOutRes message to the mobility device along with the safety-check parameters within the MessageResponseTimeout time interval.

[0471] If, when the dispenser sends a SafetyCheckOutRes message to the mobility device, the dispenser confirms that all safety conditions are met, the result value of that message may be set to "OK".

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

[0473] If a SafetyCheckOutRes message with a result value set to "PENDING" is received, Mobility can then transmit other SafetyCheckOutReq messages to the dispenser within the MessageResponseTimeout time interval.

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

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

[0476] As an alternative embodiment, either the mobility device or the dispenser can transmit a request message to the other party indicating the commencement of a secure checkout, and the other party can respond with a response message to the secure checkout request message within a predetermined time interval.

[0477] According to one embodiment of the present invention, if a non-safety-critical error is detected during the monitoring and control phase (S407) and the fuel supply has not yet been interrupted and completed, the fuel supply protocol can define a fallback mechanism that ensures backward compatibility among mutually compatible mechanisms between the mobility and the dispenser, and the fuel supply can be restarted and completed based on that fallback mechanism.

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

[0479] As an alternative embodiment, if a non-safety-critical error is detected during the monitoring and control phase (S407) and the fuel supply has not yet been interrupted and completed, the mobility and dispenser may re-execute some or all of the communication protocol negotiation phase (S403), the fuel supply protocol negotiation phase (S404), and the fuel supply parameter negotiation phase (S405).

[0480] As an alternative embodiment, the mobility and dispenser can utilize the interoperability information obtained in the discovery and pairing phase (S401) to reduce the information exchanged during the process of re-executing some or all of the communication protocol negotiation phase (S403), fuel supply protocol negotiation phase (S404), and fuel supply parameter negotiation phase (S405). For example, if a communication or fuel supply condition is identified where negotiation has already been completed and the selected protocol cannot be maintained, some or all of the communication protocol negotiation phase (S403), fuel supply protocol negotiation phase (S404), and fuel supply parameter negotiation phase (S405) may be re-executed, excluding the previously selected protocol.

[0481] As an alternative embodiment, if during the monitoring and control phase (S407) a change in the communication environment and a change in the fuel supply infrastructure are detected as a non-safety-critical error, and fuel supply is interrupted before completion, the mobility and dispenser may re-execute some or all of the communication protocol negotiation phase (S403), the fuel supply protocol negotiation phase (S404), and the fuel supply parameter negotiation phase (S405).

[0482] Changes in the communication environment can include situations where the communication channel connection is disconnected.

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

[0484] Changes in the communication environment may include situations where the quality of communication performance does not meet the required standards.

[0485] Changes in the communication environment may include situations where the integrity or accuracy of data exchanged through communication does not meet the required standards.

[0486] Changes in the fuel supply infrastructure may result in changes or maintenance of fuel supply parameters on the mobility side based on fuel supply control parameters on the dispenser side, but this may also include cases where the changes or maintenance of fuel supply-related parameters on the mobility side do not meet the required level.

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

[0488] Safety conditions may include elements related to the safety of both the mobility for hydrogen fuel supply (fuel supply) and the hydrogen fuel supply device or dispenser, and / or the engagement state of both nozzles and receptacles for initiating hydrogen fuel supply.

[0489] On the hydrogen mobility side, the pressure and temperature inside the hydrogen tank may also be included.

[0490] At the hydrogen refueling station, the following may be included: cylinder temperature, fuel transmission pressure, ambient temperature, etc.

[0491] Safety conditions on both sides of the connection and fuel supply path may include the fastening status of the nozzle-receptacle, i.e., whether or not it is fastened, the fastening status, and the leakage status.

[0492] The nozzle-receptacle engagement state may include information regarding whether it is in a suitable and / or sufficient state for carrying out the hydrogen fuel supply procedure.

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

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

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

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

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

[0498] In one of the alternative embodiments shown in Figure 4, the sharing, identification, monitoring, updating, and / or utilization of interoperability and / or compatibility may be performed throughout the entire process.

[0499] For example, an embodiment may be presented in which interoperability-related information shared between mobility and dispenser / filling station during the discovery and pairing stage (S401) is checked in subsequent stages (S402 to S411) according to the respective circumstances, updated with interoperability information available at each stage, or reconfirmed.

[0500] For example, if 10 interoperable protocol combinations (combinations of communication protocols and fuel supply protocols) between mobility and dispensers are identified in stage (S401), then in subsequent stages, communication / system errors, changes in the communication / system environment, or changes in the fuel supply environment may cause some of these 10 protocols to become incompatible or unusable, potentially reducing the number of usable protocol combinations to fewer than 10. Such situations may be checked in stages corresponding to each Use Case (S402 to S411), and as a result, the interoperability information may be updated to usable interoperability information, and each stage may be performed based on the updated interoperability information.

[0501] Furthermore, if, for example, a particular available interoperability protocol combination A is found to be temporarily incompatible or unavailable at an intermediate stage, it can be replaced with another interoperability protocol or fall back to, allowing the stage to proceed.

[0502] For example, if in stages S401 to S403 multiple available interoperability protocol combinations are identified, and interoperability protocol combination A is selected as a result of communication protocol negotiation based on preference and priority, then in stage S404 it is identified that interoperability protocol combination A is unavailable due to changes in the communication / system environment, errors, and / or changes in the fuel supply environment, then another interoperability protocol combination B, which is selected based on preference and priority or falls back to, may be determined as a result of fuel supply protocol negotiation, and stage S404 and subsequent stages may be performed.

[0503] In a similar other embodiment, in steps S401 to S404, multiple available interoperation protocol combinations are identified, and interoperation protocol combination A is selected from among them based on preference and priority as a result of fuel supply protocol negotiation. If, in step S405, it is determined that interoperation protocol combination A is unavailable due to changes in the communication / system environment, errors, and / or changes in the fuel supply environment, then another interoperation protocol combination B, which is selected or fallen back to based on preference and priority, is replaced as a result of communication protocol negotiation and fuel supply protocol negotiation, after which steps S405 and subsequent steps can be carried out.

[0504] In a similar other embodiment, in steps S401 to S406, multiple available interoperability protocol combinations are identified, and from these, interoperability protocol combination A is selected as a result of communication protocol negotiation, fuel supply protocol negotiation, and fuel supply parameter negotiation based on preference and priority. If, in step S407, interoperability protocol combination A is determined to be unusable due to changes in the communication / system environment, errors, and / or changes in the fuel supply environment, another interoperability protocol combination B, which is selected or fallen back to based on preference and priority, is replaced as a result of communication protocol negotiation, fuel supply protocol negotiation, and fuel supply parameter negotiation, after which the hydrogen fuel supply and subsequent steps related to step S407 can be carried out.

[0505] As another alternative implementation, for example, if a particular available interoperability protocol combination A becomes temporarily unavailable at an intermediate stage and is replaced by another interoperability protocol or falls back to, and interoperability protocol combination A becomes available again at a subsequent stage after that stage has been completed, then interoperability protocol combination A can be adopted at the subsequent stage based on renegotiation or a predetermined policy to proceed with the subsequent stage.

[0506] For example, suppose that in stages S401 to S406, interoperability protocol combination A is selected from among several available interoperability protocol combinations based on preference and priority as a result of communication protocol negotiation, fuel supply protocol negotiation, and fuel supply parameter negotiation. Then, in stage S407, it is determined that interoperability protocol combination A is unavailable due to changes in the communication / system environment, errors, and / or changes in the fuel supply environment. In this case, hydrogen fuel supply and subsequent stages are carried out according to stage S407 based on another interoperability protocol combination B that has been selected or fallen back to. If it is determined that interoperability protocol combination A is available again due to changes in the communication / system environment, errors, and / or changes in the fuel supply environment, interoperability protocol combination A can be restored through renegotiation between mobility and dispenser / filling station or through a predetermined restoration process.

[0507] In one of the alternative embodiments shown in Figure 4, if the already selected best-preference / highest-priority protocol combination becomes incompatible or unavailable in the interoperable protocol combinations between mobility and dispensers, when determining an alternative second-preference / next-priority protocol combination, it is possible to search for a combination in which the fuel supply protocol is changed while maintaining the same communication protocol as the existing best-preference / highest-priority protocol combination, or a combination in which the communication protocol is changed while maintaining the fuel supply protocol.

[0508] In one of the alternative embodiments shown in Figure 4, during the discovery and pairing process (stage S401), when searching for available protocol combinations and generating first interoperability information, priorities can be pre-set to prioritize cases where the communication protocol and fuel supply protocol match. For example, if the combination of communication protocol A1 and fuel supply protocol B1 is determined to be the highest priority / most preferred combination, then combinations of fuel supply protocols B2, B3, ..., etc. that can coexist with communication protocol A1, while maintaining communication protocol A1, can be pre-specified with a high priority as alternative combinations to the highest priority / most preferred combination. Alternatively, combinations of communication protocols A2, A3, etc. that can coexist with fuel supply protocol B1, while maintaining fuel supply protocol B1, can be pre-specified with a high priority as alternative combinations to the highest priority / most preferred combination.

[0509] In one of the alternative embodiments shown in Figure 4, while steps S403 to S409 are being performed, the process of updating the highest priority / preferred interoperability protocol combination can be carried out by renegotiating some or all of the steps S403 to S405.

[0510] In one of the alternative embodiments shown in Figure 4, while steps S403 to S409 are being performed, the process of updating the highest priority / preferred interoperability protocol combination may be performed by part or all of the steps S410 or S411.

[0511] In one of the alternative embodiments shown in Figure 4, while steps S403 to S409 are being performed, the process of updating the preferred / best-preference interoperability protocol combinations can be carried out by renegotiating some or all of steps S403 to S405 via some or all of steps S410 or S411.

[0512] A communication method for hydrogen fuel supply communication according to one embodiment of the present invention allows a mobility device, a dispenser, or a mobility device and a dispenser working together to determine a top-priority / preferred combination of interoperability protocols in step S401, and then, while steps S403 to S409 are being performed (with the assistance of steps S410 and S411), the top-priority / preferred combination of interoperability protocols can be determined. At this time, the method may further include a step of performing at least one step of a first process and a subsequent process of the first process based on a first communication protocol and a first fuel supply protocol. At this time, the interoperability communication protocol and fuel supply protocol determined based on the updated interoperability information may partially restrict the functions of the mobility device or partially restrict the communication functions between the mobility device and the dispenser, so in some cases, the dispenser may perform the hydrogen fuel supply process or subsequent processes alone or primarily. That is, if interoperability is downgraded or falls back, the dispenser can perform more roles than the mobility device.

[0513] Furthermore, referring to Figure 4, once fueling is successfully completed and all safety conditions are confirmed, the mobility and dispenser termination use case can be executed.

[0514] The objectives, prerequisites, and subsequent conditions of the final stage (S409) may be shown in Table 25 below.

[0515] [Table 25]

[0516] If the safety checkout use case is omitted after receiving a SafetyCheckOutRes message with "Result" set to "DONE" or a FuelLoopRes message with "status" set to a value prefixed with "finished" or "stopped", the mobility may send a termination request message (e.g., a "TerminateReq" message) to the dispenser.

[0517] Details regarding termination request messages (e.g., "TerminateReq" messages) may be defined in the respective fuel supply protocol specifications. For example, parameters included in the TerminateReq message and exchanged between mobility and dispensers may be defined separately for each individual fuel supply protocol.

[0518] The element names included in the TerminateReq message may include tank_press, tank_temp, amount, soc, reason, etc., and may be shown in Table 26 below. Elements not shown in Table 26 below may be identified by each fuel supply protocol standard, such as ISO 19885-3.

[0519] [Table 26]

[0520] When a dispenser receives a TerminateReq message from a mobility device, the dispenser can respond with a termination response message (e.g., TerminateRes) within a predetermined time interval (e.g., MessageResponseTimeout).

[0521] Details regarding termination response messages (e.g., "TerminateRes") may be defined in the respective fuel supply protocol specifications. For example, parameters included in the TerminateRes message and exchanged between mobility and dispensers may be defined separately by each individual fuel supply protocol.

[0522] The element names included in the TerminateRes message may include aprr, duration, amount, soc, result, etc., and may be shown in Table 27 below. Elements not shown in Table 27 below may be identified by each fuel supply protocol standard, such as ISO 19885-3.

[0523] [Table 27]

[0524] As an alternative embodiment, a message requesting the commencement of the termination phase (S409) may be sent to the other party by either the mobility device or the dispenser. In this case, the other party may perform the termination phase (S409) by responding to the message requesting the commencement of the termination phase (S409).

[0525] For successful fuel delivery, communications must provide expected behaviors according to the protocol. Fuel delivery actions must remain within acceptable limits according to the fuel delivery protocol. However, in reality, a variety of abnormal events can occur. Some errors are minor and can be easily handled. However, errors that cannot be recovered from and prevent fuel delivery from continuing can also occur.

[0526] In this specification, “error” or “error” may refer to an incident occurring during UC1 to UC9 (S401 to S409) or hydrogen fueling that can interrupt the ongoing process.

[0527] In stage (S410), the conditions for a non-safety critical error, exemplary error conditions, and their responses may be specified.

[0528] Referring further to Figure 4, the purpose, prerequisites, and subsequent conditions of the error handling stage (S410) can be shown in Table 28 below.

[0529] [Table 28]

[0530] Non-safety critical error conditions may include, for example, the following:

[0531] Communication errors may include: 1) communication being disconnected; 2) the received data being unrecognizable due to encoding or syntactic error; and 3) the received data being in an unacceptable range.

[0532] System errors may include cases where the dispenser or mobility device detects its own critical system error.

[0533] A Qualitative Error may include: 1) failure to meet the required level of communication performance, and 2) failure to meet the required level of data integrity or precision quality.

[0534] If a Non-Safety-Critical Error occurs and further communication becomes impossible, the mobility and dispenser will immediately cease fuel supply, take safety measures, and terminate the communication to end the session.

[0535] If a Non-Safety-Critical Error occurs and fuel supply is interrupted far from completion, the fuel supply protocol can define a fallback mechanism, for example, by defining a Non-Communication Fuelling Method.

[0536] If a Non-Safety-Critical Error is detected by Mobility and the communication channel is still operational, Mobility can send a TerminateReq message with "Action" set to "Stop" and "Reason" set to the appropriate Reason Code.

[0537] When a non-safety-critical error is detected by the dispenser and the communication channel is still operational, the dispenser can first immediately stop the fuel supply and send a TerminateReq message with "action" set to "stop" and "reason" set to the appropriate reason code.

[0538] A fuel supply protocol can define protocol-based error conditions and provide detection criteria, as well as pre-prescribed response procedures, including notification, termination procedures, and fallback mechanisms.

[0539] Referring further to Figure 4, the objectives, prerequisites, and subsequent conditions of the emergency handling stage (S411) can be shown in Table 29 below.

[0540] [Table 29]

[0541] A fuel supply protocol can define protocol-based emergency conditions and provide pre-prescribed response procedures, including detection criteria, notification, termination procedures, and fallback mechanisms, to avoid entering a detrimental situation by all means.

[0542] When a mobility device or dispenser detects a safety-critical situation, necessary actions to prevent a catastrophic incident may be taken immediately. If possible, an EmergencyNotif message may be transmitted along with information about the incident, and communication may be closed.

[0543] When a mobility device or dispenser receives an EmergencyNotif message, it can immediately respond to the action instructed in the message and immediately close the communication without undue delay.

[0544] EmergencyNotif messages can be TLS or DTLS messages, depending on the communication technology used.

[0545] Due to the criticality of the message and the efficiency of delivery, the fuel supply protocol may not permit modifications to the structure of the EmergencyNotif message.

[0546] The element names included in an EmergencyNotif message may include class, type, action, etc., and may be shown in Table 30 below. Elements not shown in Table 30 below may be specified by each fuel supply protocol standard, such as ISO 19885-3. For example, additional emergency reason codes and action codes may be specified by each protocol.

[0547] [Table 30]

[0548] Figure 16 is an operation flowchart illustrating one of the alternative embodiments of Figure 4.

[0549] Referring to Figure 16, the relationship between S2010 and S2020, which are added to steps S401 to S409 in Figure 4, is shown.

[0550] Referring together to Figures 4 and 16, a communication method for hydrogen fuel supply performed by a communication device for hydrogen fuel mobility according to one embodiment of the present invention may include a step of detecting an error occurring during the communication process of preparing for hydrogen fuel supply between a dispenser that supplies hydrogen to the mobility and the mobility (steps S403 to S406, or steps S408 to S409), or during the process of the dispenser supplying hydrogen to the mobility (step S407) (step S2010: may be performed as part of steps S403 to S409), a step of determining whether to stop the communication process (steps S403 to S406, or steps S408 to S409) or the hydrogen fuel supply process (step S407) in response to the detected error (step S2020: may be performed as part of step S410 or S411), and a step of performing a subsequent process defined based on the detected error (not shown as a separate step: performed as part of steps S403 to S411).

[0551] The following embodiments may be carried out based on interoperability or compatibility information shared between the mobility and the dispenser in step S401 of Figure 4. In particular, the process in which the communication protocol, fuel supply protocol, and fuel supply parameters are negotiated and determined in steps S403 to S405 may be carried out within the scope of the interoperability or compatibility information.

[0552] Interoperability or compatibility information is identified and shared in stage S401, but may be re-identified and shared in an updated state in subsequent processes to reflect the current situation.

[0553] In a communication method for hydrogen fuel supply performed by a mobility communication device according to one embodiment of the present invention, the step of deciding whether to suspend the communication process or the hydrogen fuel supply process in response to a detected error (step S2020: which may be performed as part of step S410 or S411) may include a step of classifying the detected error as either a safety-critical error or a non-safety-critical error.

[0554] At this time, the process of classifying the detected errors as safety-critical errors can be carried out by step S2020, or by part of step S411 in Figure 4. Once the detected errors are classified as safety-critical errors, the subsequent steps can be carried out by separate steps (S403 to S409), or by part of step S411 in Figure 4. At this time, errors classified as Safety-Critical Errors may be treated as Emergency.

[0555] In a communication method for hydrogen fuel supply performed by a mobility communication device according to one embodiment of the present invention, the step (S2020) of determining whether to suspend the communication process or the hydrogen fuel supply process in response to a detected error may further include a step (performed as part of step S410) of classifying the detected error as either a communication error, a system error, or a qualitative error, if the detected error is not fatal from a safety standpoint.

[0556] In a communication method for hydrogen fuel supply performed by a mobility communication device according to one embodiment of the present invention, the step of performing a subsequent process defined based on a detected error may include at least a portion of the step of performing an emergency handling process (S411) if the detected error is a safety-critical error.

[0557] In a communication method for hydrogen fuel supply performed by a mobility communication device according to one embodiment of the present invention, the step (S2020) of determining whether to terminate the communication process or the hydrogen fuel supply process in response to a detected error may further include a step of determining whether to replace the first fuel supply protocol of the communication process or the hydrogen fuel supply process with a fallback second fuel supply protocol if the detected error is not fatal from a safety standpoint.

[0558] In a communication method for hydrogen fuel supply performed by a mobility communication device according to one embodiment of the present invention, the step of performing a subsequent process defined based on a detected error may include the step of sending a message to a dispenser indicating whether the communication process or the hydrogen fuel supply process has been terminated.

[0559] Various types of incidents occurring during the execution of stages S403 to S409 may be detected by the mobility or dispenser (S2010). In this case, the detected incidents may be classified as errors if they meet certain conditions (S2010 and S2020). Detected errors may be handled by the error handling process in stage S410 or a separate subsequent stage if they are non-safety-critical errors, or by the emergency handling process in stage S411 if they are safety-critical errors.

[0560] In one embodiment of the present invention, the criteria for classifying a detected error as a non-safety-critical error or a safety-critical error (emergency) are predetermined by the fuel supply protocol in stages S403 to S409, and the errors detected in each of stages S403 to S409 when an error is detected can be classified accordingly.

[0561] In an alternative embodiment of the present invention, after an error is detected, it is sent to the process of steps S410 and / or S411, which can classify whether the detected error is a non-safety-critical error or a safety-critical error (emergency), respectively. That is, step S410 can classify whether the error is a non-safety-critical error and, if it is a non-safety-critical error, whether it is a communication error, a system error, or a qualitative error. Step S411 can classify whether the error is a safety-critical error.

[0562] Stage S410 classifies the detected error and can decide whether to abort the fuel supply process based on the classification result or the error status. If it is decided to continue the fuel supply process without aborting it (based on updated interoperability or compatibility information) using a fallback fuel supply protocol, then as a result of stage S410, the necessary stages from stages S403 to S409 for continuing the fuel supply process may be performed again.

[0563] Furthermore, when the cause of the error is removed and the system is restored to a normal state in stage S410 or S411, the mobility or dispenser may, individually or in cooperation with each other, return to any one of stages S403 to S409, or the next stage, that was being performed before the error occurred, and continue to perform the hydrogen fuel supply process and the communication process.

[0564] A communication method for hydrogen fuel supply (fueling) performed by a communication device of a dispenser that supplies hydrogen fuel to a hydrogen fuel mobility vehicle according to one embodiment of the present invention may include a step of detecting an error occurring during a communication process for preparing for hydrogen fuel supply between the dispenser and the mobility vehicle (steps S403 to S406, or steps S408 to S409), or during the process in which the dispenser supplies hydrogen fuel to the mobility vehicle (step S407) (step S2010; may be performed as part of steps S403 to S409); a step of determining whether to stop the communication process (steps S403 to S406, or steps S408 to S409) or the hydrogen fuel supply process (step S407) in response to the detected error (step S2020; may be performed as part of step S410 or S411); and a step of performing a subsequent process defined based on the detected error (performed as part of steps S403 to S411).

[0565] In a communication method for supplying hydrogen fuel performed by a communication device of a dispenser according to one embodiment of the present invention, the step of deciding whether to suspend the communication process or the hydrogen fuel supply process in response to a detected error (step S2020: which may be performed as part of step S410 or S411) may include a step of classifying the detected error as either a safety-critical error or a non-safety-critical error.

[0566] In a communication method for supplying hydrogen fuel performed by a communication device of a dispenser according to one embodiment of the present invention, the step (S2020) of determining whether to suspend the communication process or the hydrogen fuel supply process in response to a detected error may further include a step (which may be performed as part of step S410) of classifying the detected error as a communication error, a system error, or a qualitative error, if the detected error is not a safety-critical error.

[0567] In a communication method for supplying hydrogen fuel performed by a communication device of a dispenser according to one embodiment of the present invention, the step of performing a subsequent process defined based on a detected error may include at least a portion of the step of performing an emergency handling process (S411) if the detected error is a safety-critical error.

[0568] In a communication method for supplying hydrogen fuel performed by a communication device of a dispenser according to one embodiment of the present invention, the step (S2020) of determining whether to suspend the communication process or the hydrogen fuel supply process in response to a detected error may further include a step of determining whether to replace the first fuel supply protocol of the communication process or the hydrogen fuel supply process with a fallback second fuel supply protocol if the detected error is not a safety-critical error.

[0569] In a communication method for hydrogen fuel supply performed by a communication device of a dispenser according to one embodiment of the present invention, the step of performing a subsequent process defined based on a detected error may include a step in which the dispenser performs a process of supplying hydrogen based on a second fuel supply protocol when a first fuel supply protocol in the communication process or the hydrogen fuel supply process is replaced by a second fuel supply protocol.

[0570] In the event of a communication error, the dispenser can select the second fuel supply protocol by applying a pre-defined fallback according to the first fuel supply protocol or a pre-defined rule, and then supply hydrogen fuel based on the second fuel supply protocol.

[0571] In the event of a communication error, the mobility or dispenser may terminate the session if necessary.

[0572] In the event of a system error, the mobility or dispenser may terminate the session if necessary. In this case, the mobility or dispenser may terminate the session based on the detected error and send a message to the other party containing the stop action and a reason code corresponding to the reason.

[0573] In an alternative embodiment, in the event of a qualitative error, a fallback fuel supply protocol based on a restricted communication protocol or communication environment can be selected based on updated interoperability or compatibility information between the mobility and dispenser, and hydrogen can be supplied based on the selected fuel supply protocol.

[0574] In an alternative embodiment, in the event of a qualitative error, a different fuel supply protocol can be selected while maintaining the communication protocol between the mobility and the dispenser. In yet another alternative embodiment, a different communication protocol can be selected while maintaining the fuel supply protocol between the mobility and the dispenser.

[0575] In an alternative embodiment, in the event of a qualitative error, renegotiation may be performed to select a new combination of communication protocol and fuel supply protocol for the mobility and dispenser. In this case, some of steps S403 to S405 may be repeated for renegotiation, or renegotiation may be performed within step S410.

[0576] In an alternative embodiment, if communication is maintained even in an emergency, communication can be minimized and subsequent processes can be carried out. The mobility or dispenser can fall back on the communication protocol and fuel supply protocol.

[0577] In an alternative embodiment, fuel supply and communication shutdown may be given top priority in the event of an emergency.

[0578] In a communication method for hydrogen fuel supply performed by a communication device of a dispenser according to one embodiment of the present invention, the step of performing a subsequent process defined based on a detected error may include the step of transmitting a message to the mobility device, including whether or not the communication process or the hydrogen fuel supply process is being discontinued.

[0579] In a communication method for supplying hydrogen fuel performed by a communication device of a dispenser according to one embodiment of the present invention, if a message including whether or not the communication process or the hydrogen fuel supply process is to be stopped includes stopping the communication process or the hydrogen fuel supply process, the message may further include a reason code corresponding to an appropriate reason for stopping.

[0580] In a communication method for hydrogen fuel supply performed by a mobility and / or dispenser communication device according to one of the alternative embodiments of the present invention, the criticality of an error may be determined based on the UCDC level of available communication or fuel supply process in relation to the detected error. Furthermore, a decision may be made on whether or not to discontinue fuel supply based on the UCDC level. In this case, the process of determining the severity of the error and / or whether or not to discontinue fuel supply based on the UCDC level may be applied when the error is a qualitative error. However, the scope of the present invention is not limited by such embodiments.

[0581] In the embodiments of Figures 4 and 16, steps S2010, S2020, S410, and / or S411 are shown as embodiments relating to steps S403 to S409. In one alternative embodiment of the present invention, steps S2010 and S2020 can detect all incidents occurring during steps S401 to S409 or the fuel supply process, determine whether they are errors, and classify the errors. In another alternative embodiment of the present invention, after going through steps S2010, S2020 and steps S410 and S411 as part of another subsequent step, it is possible to return to any of steps S401 to S409 to carry out the subsequent process or to carry out the existing process and / or the next process if the error has been resolved.

[0582] Specifically, stages S2010 and S2020 can detect incidents occurring in stages such as stage S401-UC1: discovery and pairing, stage S402-UC2: communication security, stage S403-UC3: communication protocol negotiation, stage S404-UC4: fuel supply protocol negotiation, stage S405-UC5: fuel supply parameter negotiation, stage S406-UC6: safety check-in, stage S407-UC7: monitoring and control, stage S408-UC8: safety check-out, and stage S409-UC9: termination or parallel hydrogen fuel supply processes, determine whether the incident is an error, and detect or classify errors.

[0583] Furthermore, after an error has been classified and its handling has been carried out in stage S410 or S411, the system can return to stage S401 to S409 or a parallel hydrogen fuel supply process.

[0584] Furthermore, after the error has been processed and resolved, the system can return to the process that was being carried out before the error occurred, or to the next stage, such as stages S401 to S409 or the parallel hydrogen fuel supply process.

[0585] In one alternative embodiment, a criterion for determining whether an error is safety-critical may be whether it could cause damage to facilities and / or human life, or trigger a fire, explosion, leak, etc., as an incident that may occur before, during, or after hydrogen fuel supply.

[0586] In the event of a safety-critical error, communication and / or fuel supply may be interrupted or terminated. In alternative embodiments, even in the event of a safety-critical error, fuel supply may be continued if communication is maintained, fuel supply is possible, or if fuel supply must be continued (for reasons such as escaping a hazardous area or transporting a patient).

[0587] In the event of a non-safety-critical error, communication or fuel supply may be suspended or continued, based on the criticality / severity of the error, available communication environment, available fuel supply protocols, UCDC level, and the need for communication or fuel supply.

[0588] In the embodiments described above, the processes of continuous interoperability monitoring, updating interoperability information, and / or updating communication / fuel supply protocol combinations were primarily disclosed in which either the mobility unit or the dispenser performed the process. However, the detailed processes of these operations can, of course, be performed by either the mobility unit or the dispenser, or they may be performed through mutual cooperation. Furthermore, in alternative embodiments of the present invention, the mobility unit may take the lead in some parts of the processes of continuous interoperability monitoring, updating interoperability information, and / or updating communication / fuel supply protocol combinations, while the dispenser may take the lead in other parts.

[0589] Furthermore, error detection can be performed by either the mobility or the dispenser, and the entity that detected the error can send a message to the other party including the detection of the error, the detected error, the cessation of communication and fuel supply based on the error, or a reason code corresponding to the reason for the cessation.

[0590] Figure 17 is an operation flowchart illustrating a communication method for hydrogen fuel supply according to another embodiment of the present invention.

[0591] Referring together to Figures 16 and 17, a communication method for hydrogen fuel supply according to one embodiment of the present invention is performed by a communication device of a hydrogen-fueled mobility and may include the steps of: discovering a dispenser that supplies hydrogen fuel to the mobility, sharing pairing information between the mobility and the dispenser, and performing pairing between the mobility and the dispenser (S2100); negotiating a communication protocol or fuel supply protocol between the mobility and the dispenser for the process of the dispenser supplying hydrogen fuel to the mobility based on information regarding interoperability or compatibility between the mobility and the dispenser (S2200); and transmitting to the dispenser information required for monitoring and controlling the process of the dispenser supplying hydrogen fuel to the mobility, which is performed based on the fuel supply protocol (S2300). In this case, the operation performed in the pairing operation (S2100) may include some or all of the operation in step S401 in Figures 4 and 16. The actions performed for monitoring and control may include some or all of the actions in step S407 of Figures 4 and 16. The actions that the dispenser can perform in step S407 and / or the actions that the mobility can perform in step S407 may also be performed in step S2300.

[0592] A communication method for hydrogen fuel supply according to one embodiment of the present invention may further include, after the step of performing pairing (S2100), a step of establishing a secure channel between the mobility and the dispenser in order to negotiate a communication protocol or fuel supply protocol (see step S402 in Figures 4 and 16).

[0593] A communication method for hydrogen fuel supply according to one embodiment of the present invention may further include a check-in stage (see stage S406 in Figures 4 and 16) which checks whether a first necessary safety condition between the mobility and the dispenser is met, after a stage of negotiating a communication protocol or fuel supply protocol (S2200) and before the process of the dispenser refueling the mobility with hydrogen, and after the process of the dispenser refueling the mobility with hydrogen and before the nozzle is separated from the mobility, and after the process of the dispenser refueling the mobility with hydrogen, and before the nozzle is separated from the mobility.

[0594] The first and / or second required safety conditions relating to alternative embodiments of the present invention may include the fastening condition between the nozzle and the receptacle, the airtightness of the fastening area, the temperature, pressure, and residual capacity (SoC) of the hydrogen storage tank on the mobility or dispenser side.

[0595] A communication method for hydrogen fuel supply according to one embodiment of the present invention may further include a step of detecting and handling a non-safety-critical error that occurs while a step of negotiating a communication protocol or fuel supply protocol (S2200) or a step of transmitting information required for monitoring and control to a dispenser (S2300) is being performed (see steps S2010 and S410 in Figure 16), and a step of detecting and handling an emergency that occurs while a step of negotiating a communication protocol or fuel supply protocol (S2200) or a step of transmitting information required for monitoring and control to a dispenser (S2300) is being performed, in which the interaction between the dispenser and mobility must be stopped (see steps S2020 and S411 in Figure 16).

[0596] The step of negotiating a communication protocol or fuel supply protocol of a communication method for hydrogen fuel supply according to one embodiment of the present invention (S2200) may include a step of negotiating a communication protocol between a mobility device and a dispenser (see step S403 in Figures 4 and 16), a step of negotiating a fuel supply protocol between the mobility device and the dispenser based on the communication protocol (see step S404 in Figures 4 and 16), and a step of negotiating fuel supply parameters between the mobility device and the dispenser based on the fuel supply protocol (see step S405 in Figures 4 and 16).

[0597] In the step (S2200) of negotiating a communication protocol or fuel supply protocol of a communication method for hydrogen fuel supply according to one embodiment of the present invention, the information of the communication protocol or fuel supply protocol transmitted between the dispenser and the mobility may include the protocol name, index, version, priority, or preference.

[0598] In a communication method for supplying hydrogen fuel according to one embodiment of the present invention, the pairing information shared between the mobility device and the dispenser during the pairing stage (S2100) may include information regarding interoperability or compatibility between the mobility device and the dispenser.

[0599] In a communication method for hydrogen fuel supply according to one embodiment of the present invention, information regarding interoperability or compatibility between mobility and a dispenser is updated based on state information when the stage of negotiating a communication protocol or fuel supply protocol (S2200) or the stage of transmitting information required for monitoring and control to the dispenser (S2300) is performed, and the stage of negotiating a communication protocol or fuel supply protocol (S2200) or the stage of transmitting information required for monitoring and control to the dispenser (S2300) can be performed based on the updated interoperability or compatibility information.

[0600] A communication method for supplying hydrogen fuel according to one embodiment of the present invention may further include a step of repeating part or all of the step of negotiating a communication protocol or fuel supply protocol (S2200) if a non-safety-critical error occurs during the step of negotiating a communication protocol or fuel supply protocol (S2200) (S2010 and S410 in Figure 16).

[0601] In the step (S407) of transmitting information necessary for monitoring and controlling the communication method for hydrogen fuel supply according to one embodiment of the present invention to a dispenser, the information to be transmitted by the mobility device to the dispenser may be determined based on whether the fuel supply protocol allows bidirectional communication between the mobility device and the dispenser as a communication protocol.

[0602] A communication method for hydrogen fueling, performed by a communication device of a dispenser that supplies hydrogen fuel to a hydrogen fuel mobility vehicle according to one embodiment of the present invention, may include the steps of: discovering the mobility vehicle, sharing pairing information between the mobility vehicle and the dispenser, and performing pairing between the mobility vehicle and the dispenser (S2100); negotiating a communication protocol or fuel supply protocol between the mobility vehicle and the dispenser for the process of the dispenser refueling the mobility vehicle with hydrogen, based on information regarding interoperability or compatibility between the mobility vehicle and the dispenser (S2200); and monitoring and controlling the process of the dispenser refueling the mobility vehicle with hydrogen, performed based on the fuel supply protocol (S2300).

[0603] A communication method for hydrogen fuel supply performed by a dispenser communication device according to one embodiment of the present invention may further include, after the step of performing pairing (S2100), the step of establishing a secure channel between the mobility and the dispenser in order to negotiate a communication protocol or fuel supply protocol (S402).

[0604] A communication method for hydrogen fuel supply performed by a dispenser communication device according to one embodiment of the present invention may further include: a check-in step (S406) which checks whether a first necessary safety condition between the mobility and the dispenser is met, after a step of negotiating a communication protocol or fuel supply protocol (S2200) and before the process of the dispenser refueling the mobility with hydrogen; and a check-out step (S408) which checks whether a second necessary safety condition between the mobility and the dispenser is met, after the process of the dispenser refueling the mobility with hydrogen and before the nozzle is separated from the mobility.

[0605] A communication method for hydrogen fuel supply performed by a dispenser communication device according to one embodiment of the present invention may further include: a step of detecting and handling a non-safety-critical error that occurs while a step of negotiating a communication protocol or fuel supply protocol (S2200) or a step of controlling the dispenser to monitor the process of supplying hydrogen fuel to mobility (S2300, S407) is being performed; and a step of detecting and handling an emergency that occurs while a step of negotiating a communication protocol or fuel supply protocol or a step of controlling the dispenser to monitor the process of supplying hydrogen fuel to mobility (S2300, S407) is being performed, in which the interaction between the dispenser and mobility must be stopped (S2020, S411).

[0606] The step (S2200) of negotiating a communication protocol or fuel supply protocol for a communication method for hydrogen fuel supply performed by a communication device of a dispenser according to one embodiment of the present invention may include the steps of negotiating a communication protocol between the mobility and the dispenser (S403), negotiating a fuel supply protocol between the mobility and the dispenser based on the communication protocol (S404), and negotiating fuel supply parameters between the mobility and the dispenser based on the fuel supply protocol (S405).

[0607] A communication method for hydrogen fuel supply according to one embodiment of the present invention may include a step, as part of step S401 in Figure 4, step S401 in Figure 16, and step S2100 in Figure 17, in which information regarding interoperability or compatibility between mobility and dispensers is checked based on pairing information.

[0608] The method shown in Figure 17 can be carried out by the mobility device, by the dispenser, or through mutual cooperation between the mobility device and the dispenser.

[0609] In the embodiment shown in Figure 17, the entity communicating with the mobility is described as a dispenser, but the communication devices of the dispenser or station can communicate with the mobility individually or in cooperation with each other.

[0610] For example, if a station has multiple wireless LAN access points (APs), some of these APs may be assigned to a dispenser, while others can participate in communication with mobility devices even if they are not directly assigned to a dispenser.

[0611] Stage S2100 may include a process in which the mobility and the dispenser (or station) share pairing information using wireless communication and use it to discover each other's presence.

[0612] Stage S2100 may be a process to verify whether proper pairing has occurred between the mobility device and the dispenser. In this case, the entities performing the pairing check may be both the mobility device and the dispenser (station), or either one of them.

[0613] Based on step S2100 and the subsequent pairing information (based on interoperability and compatibility information within the pairing information), subsequent processes related to a communication protocol or fuel supply protocol for the process of the dispenser refueling the mobility with hydrogen can be carried out by the dispenser and mobility sending and receiving at least one message. This process may correspond, for example, to step S2200 in Figure 17, and steps S403 to S405 in Figures 4 and / or 16.

[0614] According to one embodiment of the present invention, the hydrogen fuel mobility and the dispenser / station can find each other, check compatibility, and verify whether or not there is correct pairing, thereby assisting in the initiation of the hydrogen fuel supply process and shortening the process until the hydrogen fuel supply process is initiated.

[0615] Furthermore, according to one embodiment of the present invention, during the discovery and pairing process, a standardized data field such as VSE (Vendor-Specific Element) can be used to provide the hydrogen fuel mobility and the dispenser / station with the functions, communication protocols, and / or fuel supply protocols of each respective device.

[0616] In this case, according to one embodiment of the present invention, information such as interoperability and compatibility required in subsequent stages can be shared with the other party, and the process until the start of the hydrogen fuel supply process can be shortened.

[0617] During the dispenser discovery stage (S2100), messages exchanged between the dispenser and the mobility device may include a VSE (Vendor-Specific Element) data field, which may contain at least some information regarding pairing.

[0618] The VSE data field may include, as at least part of the information regarding pairing, the standards supported by the dispenser or mobility, the version of the standards, the fuel supply protocol supported by the dispenser or mobility, the communication protocol supported by the dispenser or mobility, or identification information for pairing the dispenser or mobility.

[0619] The standards supported by the dispenser or mobility may be well-known standards such as ISO 19885, or they may include support for specific standards. The version of the standard may indicate the version of a particular standard.

[0620] For example, a VSE may claim that a mobility or dispenser is an ISO 19885 device and may include compatibility information, including a list of supported communication / fuel supply protocols.

[0621] Additionally, an identifier (ID) for pairing can be added to the VSE data field. The pairing ID can be used for pairing between the mobility device and the dispenser during the pairing phase (S2100).

[0622] The VSE (Vendor Specific Element) data field can be attached to beacon, probe request / response, association request (Assoc Req), reassociation request (Reassoc Req) messages, etc.

[0623] In stages S2100 and S2200, wireless communication technologies such as Wi-Fi (WLAN) may be used. Pairing information and / or interoperability / compatibility information may be shared between the mobility device and the dispenser / station using the VSE (Vendor Specific Element) data field.

[0624] Pairing information may include the dispenser's position or precise positioning information. Alternatively, additional pairing information may be transmitted via the fuel supply cable between the mobility device and the dispenser.

[0625] Pairing information may be exchanged using additional communication technologies other than Wi-Fi, such as cables, NFC, RFID, and barcodes. In this case, short-range communication technologies can assist in accurate location measurement and positioning.

[0626] The process of checking / verifying pairing can be carried out using one-way pairing. In one embodiment of one-way pairing, the mobility device can check the dispenser. Depending on the embodiment, the dispenser may check the mobility device, or both devices may check each other.

[0627] In the above embodiment, an embodiment was illustrated in which the message included a list of communication protocols; however, in other embodiments of the present invention, the message may include a list of fuel supply protocols or fuel supply parameters. Furthermore, the list of communication protocols may be exchanged in association with a list of supported fuel supply protocols.

[0628] In this case, the first message can mean a message transmitted by at least one wireless communication entity (2310, 2320, 2330) based on wireless communication technology. For example, in the case of Bluetooth®-based communication, it can be transmitted in the form of a beacon message, and in the case of wireless LAN-based communication, it can be transmitted in the form of a message permitted in wireless LAN communication. In this case, in embodiments of the present invention, the communication technology on which the first message depends is not limited to a specific communication medium.

[0629] In a communication method for hydrogen fuel supply performed by a communication device for hydrogen fuel mobility according to one embodiment of the present invention, information relating to interoperability or compatibility between a dispenser and mobility may include whether bidirectional communication is supported between the dispenser and mobility, whether a function for sharing measurement data via bidirectional communication between the dispenser and mobility is supported, whether the measurement data can be used to control or manage the hydrogen fuel supply process from the dispenser to mobility, or whether a fallback or alternative protocol for the communication protocol or fuel supply protocol can be determined based on changes in the communication environment between the dispenser and mobility during the fuel supply process from the dispenser to mobility.

[0630] In one of the alternative embodiments shown in Figure 17, the range of fuel supply protocols commonly supported by dispensers or mobility may be guided by whether or not bidirectional communication between dispensers or mobility can be supported, as an item identified in the list of communication protocols supported by dispensers or mobility.

[0631] In one of the alternative embodiments shown in Figure 17, whether or not the function of sharing real-time measurement data (actual measurement data from either the dispenser or the mobility device) between the dispenser and the mobility device is supported using bidirectional communication can be shared as interoperability / compatibility information.

[0632] In one of the alternative embodiments shown in Figure 17, real-time measurement data can be shared as interoperability / compatibility information to determine whether it can be used in the control or management process of the fuel supply protocol for the process of refueling hydrogen from a dispenser to mobility.

[0633] In one of the alternative embodiments shown in Figure 17, the occurrence of situations such as UC10 or UC11 may be shared between the mobility and the dispenser based on real-time measurement data. At this time, the presence or absence of interoperability / compatibility information fallback may be determined based on whether bidirectional communication is supported, whether real-time measurement data can be shared, or whether real-time measurement data can be utilized. In addition to fallback, an alternative or suboptimal communication / fuel supply protocol may be selected, and the hydrogen fuel supply process may be carried out or terminated depending on the situation based on the selected protocol.

[0634] In one embodiment of the present invention, by exploring the specific details of the hydrogen fuel supply protocol in advance during the pairing and discovery phase (S401), the agreement process in subsequent protocol negotiation phases (S403 to S405) can be supported, and incidentally, the negotiation process can be shortened.

[0635] In one embodiment of the present invention, when a situation corresponding to UC10 or UC11 occurs, the interoperability / compatibility information shared in S401 is used to quickly and efficiently process the response, thereby increasing the likelihood of success in the overall hydrogen fuel supply process and reducing the time required for the hydrogen fuel supply process.

[0636] Figure 18 is an operation flowchart illustrating one embodiment of step S401 of a communication method for hydrogen fuel supply according to one embodiment of the present invention.

[0637] A communication method for supplying hydrogen fuel according to one embodiment of the present invention is performed by a communication device of a hydrogen fuel mobility vehicle and includes the steps of: broadcasting a Dispenser Discovery Protocol (DDP) request message via a communication network including a dispenser that supplies hydrogen fuel to the mobility vehicle (S2400); receiving a DDP response message from the dispenser that includes identification information of the dispenser on the communication network (S2500); and performing authentication for pairing between the mobility vehicle and the dispenser using the identification information of the dispenser in the DDP response message (S2600).

[0638] A communication method for hydrogen fuel supply performed by a hydrogen fueled mobility communication device according to one embodiment of the present invention may further include, prior to the step of broadcasting a DDP request message (S2400), the step of determining the IP address of the mobility used in the communication network including the dispenser, and the mobility connecting to the communication network via a communication channel based on the mobility's IP address.

[0639] In this case, the process by which the mobility's IP address is determined may involve the communication network determining the IP address and assigning the mobility an IP address. Alternatively, in an alternative embodiment, the mobility may select one IP address from among the available IP addresses on the communication network, determine its IP address, and assign it to itself. In this case, the process of determining the mobility's IP address may be carried out through the cooperation of the communication network and / or the mobility, and this does not limit the concept of the present invention.

[0640] In an alternative embodiment of the present invention, once a Layer 1 / 2 connection is established in step S401, the mobility can join the dispenser network (the network to which the dispenser belongs, or a network under the management of an FSO (Fueling Station Operator) or FSMS (Fueling Station Managing System) that manages other surrounding dispensers, including the dispenser). At this time, the mobility can join the network by assigning or receiving an IP address. In an alternative embodiment of the present invention, after joining the network, the mobility can announce its connection information or identification information.

[0641] Mobility and dispensers can support IPv6, as defined in IETF RFCs 8200 and 8504.

[0642] After the data link between the mobility and the network to which the dispenser belongs has been activated (the communication channel has been successfully discovered, connected, and paired), the mobility may join the network by being assigned an IP address from the communication network or by assigning one to itself, as defined in IETF RFCs 4291, 4861, 4862, 4429, and 7527. At this point, the process by which the mobility connects to or pairs with the communication network may be a different process from the pairing process between the mobility and the dispenser.

[0643] In an alternative embodiment of the present invention, after a mobility device is assigned an IPv6 address, the mobility device can announce its IP address and TCP / UDP port number, etc., based on the Dispenser Discovery Protocol (DDP).

[0644] In a communication method for hydrogen fuel supply, performed by a mobility communication device according to one embodiment of the present invention, the IP address of the mobility device can be generated based on a random number.

[0645] In a communication method for hydrogen fuel supply performed by a mobility communication device according to one embodiment of the present invention, the mobility device can generate an IPv6 address in a manner specified, for example, in RFC3041, in order to avoid disclosing the MAC address of the mobility device, which may become permanent, when the IPv6 address is made public or shared with the dispenser.

[0646] In a communication method for hydrogen fuel supply performed by a mobility communication device according to one embodiment of the present invention, the mobility device can generate an IPv6 address based on a random number in a manner specified in, for example, RFC3041, in order to avoid disclosing the MAC address of the mobility device, which may become permanent, when the IPv6 address is made public or shared with the dispenser.

[0647] To perform the DDP protocol, mobility can broadcast a DDP request message (DDDPRequest message) over a communication network that includes a dispenser.

[0648] In this case, the DDP request message may or may not include mobility identification information and can be broadcast using predefined information (e.g., TCP port number, UDP port number, etc.).

[0649] For example, a message can be broadcast on port number 19885 using the link-local multicast address "0xff02::1".

[0650] Examples of how DDP request messages are implemented based on XML or the like can be disclosed in Table 31 below.

[0651] [Table 31]

[0652] The dispenser can open UDP port 19885 and prepare to receive the next message sent from the mobility device. At this time, the mobility device's pairing ID, etc., may be included in the initial DDP request message.

[0653] Examples of how DDP response messages are implemented based on XML or the like can be disclosed in Table 32 below.

[0654] [Table 32]

[0655] In alternative embodiments, the pairing IDs of the mobility and dispenser, for example, may be shared with the other party through a separate process within the DDP protocol other than the DDP request message or DDP response message, and used in the authentication process for pairing.

[0656] In an alternative embodiment of the present invention, in a communication method for hydrogen fuel supply performed by a hydrogen fueled mobility communication device, the mobility identification information contained in the DDP request message or messages transmitted in a subsequent process may include the mobility's IP address (generated to avoid disclosing the MAC address), and the dispenser identification information contained in the DDP response message may include the dispenser's IP address, the dispenser's TCP port number, or the dispenser's UDP port number.

[0657] In one embodiment of the present invention, in a communication method for hydrogen fuel supply performed by a hydrogen fueled mobility communication device, the mobility identification information contained in the DDP request message or messages transmitted in a subsequent process may include a mobility pairing identifier (ID), and the dispenser identification information contained in the DDP response message may include a dispenser pairing identifier (ID).

[0658] In one embodiment of the present invention, in a communication method for supplying hydrogen fuel performed by a communication device for hydrogen fueled mobility, the step of performing authentication for pairing between mobility and a dispenser (S2600) can be performed using a pairing identifier for mobility and a pairing identifier for dispenser.

[0659] In the stage of performing authentication for pairing between the mobility device and the dispenser (S2600), the pairing identifier of the mobility device and the pairing identifier of the dispenser can be used to perform authentication for pairing between the mobility device and the dispenser via a pairing channel different from the communication channel to which the mobility device is connected to the communication network.

[0660] The step of performing authentication for pairing between the mobility device and the dispenser (S2600) may include the steps of binding a pairing channel for pairing between the mobility device and the dispenser to a communication channel using the pairing identifier of the mobility device and the pairing identifier of the dispenser, and performing authentication for pairing between the mobility device and the dispenser within the pairing channel using the pairing identifier of the mobility device and the pairing identifier of the dispenser.

[0661] In one embodiment of the present invention, the communication channel and the pairing channel may be the same channel; in another embodiment, the communication channel and the pairing channel may be different channels of the same type; and in yet another embodiment, the communication channel and the pairing channel may be different channels of each other.

[0662] The pairing ID field in DDP request messages and / or DDP response messages can be particularly useful when a different pairing channel is used than the communication channel. For example, the pairing ID may be used when binding the pairing channel to the communication channel.

[0663] The pairing channel may be embodied as a separate secure channel (e.g., TCP and / or TLS). In an alternative embodiment, the pairing channel may consist of a communication technology that is heterogeneous with the communication channel. For example, the communication channel may be a WLAN and the pairing channel may be UWB, or it may be configured using short-range communication such as BLE, IrDA, or RFID.

[0664] In a communication method for hydrogen fueling performed by a communication device for a mobility and / or dispenser according to one embodiment of the present invention, mutual authentication may be required between the mobility and the dispenser.

[0665] While mobility can act as a client and dispenser as a server within TCP / TLS / DTLS, the concept of the present invention is not limited to any particular embodiment.

[0666] A mobility DDP request message can include inquiries about the location of the dispenser or who the dispenser is.

[0667] The dispenser's DDP response message can include information about who it is, where it is located, its IP address, or port information.

[0668] After the DDP request message and DDP response message have been exchanged, a TCP 3-way handshake and / or TLS 3-way handshake, etc., may be performed between the mobility and the dispenser.

[0669] In a TCP 3-way handshake, the mobility device can send a SYN message, the dispenser can respond with a SYN / ACK message, and the mobility device can respond with an ACK message.

[0670] In a TLS 3-way handshake, the mobility device can send a Client Hello message, the dispenser can respond with a Server Hello message, and the mobility device can transmit a Client finished + First fueling message.

[0671] In a communication method for hydrogen fueling, performed by a communication device for a mobility and / or dispenser according to one embodiment of the present invention, during mutual authentication between the mobility and the dispenser, each of the mobility and the dispenser can prove its identity using a certificate and a signature.

[0672] If the dispenser is acting as the server, the dispenser can request authentication from the client (mobility) at any time.

[0673] If dispenser authentication fails, the mobility can record such security event in the mobility's EVCC or related database, and, if possible, notify the user of such security event and suspend fuel supply based on emergency handling (UC11, S411).

[0674] If mobility authentication fails, the dispenser can record such security events in the dispenser's SECC or related database, and may halt fuel supply based on emergency handling (UC11, S411).

[0675] In the alternative embodiment stage (S401), after the stage of broadcasting the DDP request message (S2400), in the process of sharing pairing information between the mobility and the dispenser, the message transmitted by the mobility may include information about the communication protocol or fuel supply protocol supported by the mobility as information about interoperability or compatibility between the mobility and the dispenser.

[0676] In an alternative embodiment, at the stage of broadcasting the DDP request message (S2400), the DDP request message may include information about the communication protocol or fuel supply protocol supported by the mobility, as information regarding interoperability or compatibility between the mobility and the dispenser.

[0677] In a communication method for hydrogen fuel supply performed by a hydrogen fueled mobility communication device according to one embodiment of the present invention, information on the communication protocol or fuel supply protocol supported by the mobility may include the protocol name, index, version, priority, or preference.

[0678] In the stage of the alternative embodiment (S401), after the stage of sending / receiving a DDP response message (S2500), in the process of sharing pairing information between the mobility and the dispenser, the message sent by the dispenser may include information about the communication protocol or fuel supply protocol supported by the dispenser, as information regarding interoperability or compatibility between the mobility and the dispenser.

[0679] In an alternative embodiment, during the stage of sending / receiving a DDP response message (S2500), the DDP response message may include information about the communication protocol or fuel supply protocol supported by the dispenser, as information regarding interoperability or compatibility between the mobility and the dispenser.

[0680] In a communication method for hydrogen fuel supply performed by a mobility and / or dispenser communication device according to one embodiment of the present invention, information regarding a communication protocol or fuel supply protocol supported by the dispenser may include a protocol name, index, version, priority, or preference.

[0681] A communication method for supplying hydrogen fuel, performed by a communication device for hydrogen-fueled mobility according to one embodiment of the present invention, may further include a step (S403, S404, S405) of negotiating a communication protocol or fuel supply protocol between the mobility and the dispenser after pairing between the mobility and the dispenser has been performed.

[0682] A communication method for hydrogen fuel supply performed by a hydrogen fueled mobility communication device according to one embodiment of the present invention may further include a step (S402) of establishing a secure channel between the mobility and the dispenser in order to negotiate a communication protocol or fuel supply protocol between the mobility and the dispenser, after pairing between the mobility and the dispenser has been performed.

[0683] In a communication method for supplying hydrogen fuel, performed by a communication device for hydrogen-fueled mobility according to one embodiment of the present invention, the steps of negotiating a communication protocol or fuel supply protocol between mobility and a dispenser (S403, S404, S405) may include: a step of negotiating a communication protocol between mobility and a dispenser (S403); a step of negotiating a fuel supply protocol between mobility and a dispenser based on the communication protocol (S404); and a step of negotiating fuel supply parameters between mobility and a dispenser based on the fuel supply protocol (S405).

[0684] A communication method for hydrogen fuel supply performed by a communication device of a dispenser that supplies hydrogen fuel to a hydrogen fuel mobility vehicle according to one embodiment of the present invention may include the steps of: receiving a Dispenser Discovery Protocol (DDP) request message broadcast from the mobility vehicle via a communication network including the dispenser (S2400); transmitting a DDP response message containing the identification information of the dispenser on the communication network to the mobility vehicle (S2500); and performing authentication for pairing between the mobility vehicle and the dispenser vehicle using the identification information of the dispenser in the DDP response message (S2600).

[0685] In a communication method for hydrogen fuel supply performed by a dispenser communication device according to one embodiment of the present invention, the mobility identification information included in the DDP request message may include a mobility pairing identifier (ID), and the dispenser identification information included in the DDP response message may include a dispenser pairing identifier (ID).

[0686] In a communication method for hydrogen fuel supply performed by a communication device for a dispenser according to one embodiment of the present invention, the step of performing pairing authentication between the mobility device and the dispenser (S2600) can be performed using the pairing identifier of the mobility device and the pairing identifier of the dispenser.

[0687] During the pairing authentication stage between the mobility device and the dispenser, the pairing identifier of the mobility device and the pairing identifier of the dispenser can be used to perform pairing authentication between the mobility device and the dispenser via a pairing channel different from the communication channel to which the mobility device is connected to the communication network.

[0688] In a communication method for hydrogen fuel supply performed by a dispenser communication device according to one embodiment of the present invention, the dispenser identification information included in the DDP response message may include the dispenser's IP address, the dispenser's TCP port number, or the dispenser's UDP port number.

[0689] A communication method for hydrogen fueling performed by a dispenser communication device according to one embodiment of the present invention may further include the steps of negotiating a communication protocol or fuel supply protocol between the mobility and the dispenser after pairing between the mobility and the dispenser has been performed (S403, S404, S405), and monitoring and controlling the process by which the dispenser supplies hydrogen fuel to the mobility, based on the fuel supply protocol (S407).

[0690] A communication method for hydrogen fueling performed by a dispenser communication device according to one embodiment of the present invention may further include the step (not shown) of the dispenser opening its UDP port based on the UDP port number of the mobility included in a predetermined DDP request message.

[0691] In an alternative embodiment, authentication for pairing (S2600) may be performed by being requested or initiated by the mobility side as needed.

[0692] In an alternative embodiment, authentication for pairing (S2600) may be performed by being continuously requested from or initiated by the dispenser to the mobility. In particular, after hydrogen fuel supply has been initiated, in order to perform the step of monitoring and controlling the hydrogen fuel supply process (S407), the dispenser may periodically or continuously request or initiate the process related to authentication for pairing (S2600) to the mobility.

[0693] In an alternative embodiment, authentication for pairing (S2600) may be performed using unilateral authentication.

[0694] In an alternative embodiment, authentication for pairing (S2600) can be performed using mutual authentication.

[0695] In an alternative embodiment, the entity acting as the server during the authentication (S2600) process for pairing can transmit a certificate and signature to the other party.

[0696] In an alternative embodiment, the entity acting as the server during the authentication process for pairing (S2600) can transmit certificates, signatures, and certification requests to the other party.

[0697] In an alternative embodiment, when authentication for pairing (S2600) is performed using mutual authentication, the mobility device can act as the server once, and the dispenser can act as the server again.

[0698] In one embodiment of the present invention, for ease of explanation, an embodiment in which the protocol message is represented or coded as a JSON-based message is illustrated. In alternative embodiments of the present invention, a variety of message coding and / or representation techniques can be used to generate the protocol message, and the protocol message generated using a variety of techniques can be sent and received between mobility devices, dispensers, and filling stations.

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

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

[0701] At least a portion of the fuel supply communication method for electric vehicle fuel supply according to one embodiment of the present invention may be performed by the computing system 3000 shown in Figure 19.

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

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

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

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

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

[0707] Furthermore, each component included in the computing system 3000 is connected by a bus 3700 and can communicate with one another.

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

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

[0710] A communication device or communication control device for a hydrogen fuel mobility 100 according to one embodiment of the present invention may include a memory 3200 for storing at least one instruction and a processor 3100 for executing at least one instruction. The processor 3100 can broadcast a Dispenser Discovery Protocol (DDP) request message via a communication network including a dispenser that supplies hydrogen fuel to the mobility (S2400) by at least one instruction, receive a DDP response message from the dispenser including identification information of the dispenser on the communication network (S2500), and in the communication device for a hydrogen fuel mobility according to one embodiment of the present invention, authentication for pairing between the mobility and the dispenser can be performed using the identification information of the dispenser in the DDP response message (S2600).

[0711] In a communication device for hydrogen fuel mobility according to one embodiment of the present invention, the IP address of the mobility used in the communication network including the dispenser is determined before the DDP request message is broadcast (S2400), and the mobility can connect to the communication network via a communication channel based on the mobility's IP address.

[0712] In a communication device for hydrogen fuel mobility according to one embodiment of the present invention, a DDP request message may include a mobility pairing identifier (ID, Identification), and the dispenser identification information included in the DDP response message may include a dispenser pairing identifier (ID, Identification).

[0713] In a communication device for hydrogen fuel mobility according to one embodiment of the present invention, when authentication for pairing between mobility and dispenser is performed (S2600), authentication for pairing between mobility and dispenser may be performed using the pairing identifier of mobility and the pairing identifier of dispenser.

[0714] In a communication device for hydrogen fuel mobility according to one embodiment of the present invention, when authentication for pairing between mobility and dispenser is performed (S2600), authentication for pairing between mobility and dispenser can be performed via a pairing channel different from the communication channel to which mobility is connected to the communication network, using the pairing identifier of mobility and the pairing identifier of dispenser.

[0715] In a communication device for hydrogen fuel mobility according to one embodiment of the present invention, the dispenser identification information included in the DDP response message may include the dispenser's IP address, the dispenser's TCP port number, or the dispenser's UDP port number.

[0716] A communication device or communication control device for a dispenser that supplies hydrogen fuel to a hydrogen fuel mobility vehicle according to one embodiment of the present invention includes a memory 3200 for storing at least one instruction and a processor 3100 for executing at least one instruction, wherein the processor 3100 can receive a Dispenser Discovery Protocol (DDP) request message broadcast from the mobility vehicle via a communication network including the dispenser (S2400), send a DDP response message to the mobility vehicle including identification information of the dispenser on the communication network (S2500), and perform authentication for pairing between the mobility vehicle and the dispenser using the identification information of the dispenser in the DDP response message (S2600).

[0717] On the other hand, while most of the embodiments described above focused on a method in which the hydrogen fuel mobility device first transmits its communication protocol and parameters to the dispenser, the present invention is not limited to any particular embodiment, and it is of course possible to configure the device to first transmit its communication protocol and parameters to the hydrogen fuel mobility device from the dispenser. In this case, it is obvious that the only difference is that in the embodiment the sender becomes the receiver and the receiver becomes the sender, and that the two have substantially the same characteristics.

[0718] The operation of the method according to an embodiment of the present invention can be embodied as a computer-readable program or code on a computer-readable recording medium. The computer-readable recording medium includes any type of recording device on which information readable by a computer system is stored. The computer-readable recording medium may also be distributed across a network of computer systems, and computer-readable programs or code may be stored and executed in a distributed manner.

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

[0720] While some aspects of the present invention have been described in the context of apparatus, they can also be described by corresponding methods, where a block or apparatus corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method can be described as features of a corresponding block, item, or corresponding apparatus. Some or all of the method steps may be carried out by (or using) a hardware device such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, at least one of the most important method steps may be carried out by such a device.

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

[0722] While preferred embodiments of the present invention have been described above with reference to the present invention, those skilled in the art will understand that the present invention can be modified and altered in various ways without departing from the spirit and scope of the invention as set forth in the following claims.< / false> < / true> < / ok> < / true> < / ok> < / pending> < / pending>

Claims

1. A communication method for hydrogen fueling performed by hydrogen fueled mobility, comprising the steps of: broadcasting a Dispenser Discovery Protocol (DDP) request message via a communication network including a dispenser that supplies hydrogen fuel to the mobility; receiving a DDP response message from the dispenser including identification information of the dispenser on the communication network; and performing authentication between the mobility and the dispenser for pairing using the identification information of the dispenser in the DDP response message.

2. A communication method for hydrogen fuel supply according to claim 1, further comprising the steps of determining the IP address of the mobility used in the communication network including the dispenser, prior to the step of broadcasting the DDP request message, and the mobility connecting to the communication network via a communication channel based on the IP address of the mobility.

3. The communication method for supplying hydrogen fuel according to claim 2, wherein the IP address of the mobility is generated based on a random number.

4. A communication method for supplying hydrogen fuel according to claim 1, wherein the DDP request message includes a pairing identifier (ID, Identification) of the mobility, the identification information of the dispenser included in the DDP response message includes a pairing identifier (ID, Identification) of the dispenser, and in the step of performing authentication for pairing between the mobility and the dispenser, the pairing identifier of the mobility and the pairing identifier of the dispenser are used to perform authentication for pairing between the mobility and the dispenser.

5. A communication method for supplying hydrogen fuel according to claim 4, wherein, in the step of performing authentication for pairing between the mobility and the dispenser, authentication for pairing between the mobility and the dispenser is performed using the pairing identifier of the mobility and the pairing identifier of the dispenser via a pairing channel different from the communication channel to which the mobility is connected to the communication network.

6. Communication method for hydrogen fuel supply according to claim 4, wherein the step of performing authentication for pairing between the mobility and the dispenser includes the steps of binding a pairing channel for pairing between the mobility and the dispenser to a communication channel using a pairing identifier for the mobility and a pairing identifier for the dispenser, and performing authentication for pairing between the mobility and the dispenser within the pairing channel using a pairing identifier for the mobility and a pairing identifier for the dispenser.

7. The communication method for supplying hydrogen fuel according to claim 1, wherein the identification information of the dispenser included in the DDP response message includes the IP address of the dispenser, the TCP port number of the dispenser, or the UDP port number of the dispenser.

8. A communication method for hydrogen fuel supply according to claim 1, further comprising the step of negotiating a communication protocol or fuel supply protocol between the mobility and the dispenser after pairing between the mobility and the dispenser has been performed.

9. A communication method for hydrogen fuel supply according to claim 1, further comprising the step of establishing a secure channel between the mobility and the dispenser to negotiate a communication protocol or fuel supply protocol between the mobility and the dispenser, after the pairing between the mobility and the dispenser has been performed.

10. A communication method for supplying hydrogen fuel according to claim 8, wherein the step of negotiating a communication protocol or fuel supply protocol between the mobility and the dispenser includes the steps of negotiating the communication protocol between the mobility and the dispenser, negotiating the fuel supply protocol between the mobility and the dispenser based on the communication protocol, and negotiating fuel supply parameters between the mobility and the dispenser based on the fuel supply protocol.

11. A communication method for hydrogen fueling performed by a communication device of a dispenser that supplies hydrogen to a hydrogen fuel mobility, comprising the steps of: receiving a Dispenser Discovery Protocol (DDP) request message broadcast from the mobility via a communication network including the dispenser; transmitting a DDP response message containing identification information of the dispenser on the communication network to the mobility; and performing authentication for pairing between the mobility and the dispenser using the identification information of the dispenser in the DDP response message between the mobility and the dispenser.

12. Communication method for hydrogen fuel supply according to claim 11, wherein the DDP request message includes a pairing identifier (ID, Identification) of the mobility, the dispenser identification information included in the DDP response message includes a pairing identifier (ID, Identification) of the dispenser, and in the step of performing authentication for pairing between the mobility and the dispenser, the pairing identifier of the mobility and the pairing identifier of the dispenser are used to perform authentication for pairing between the mobility and the dispenser.

13. Communication method for hydrogen fuel supply according to claim 12, wherein, in the step of performing authentication for pairing between the mobility and the dispenser, authentication for pairing between the mobility and the dispenser is performed via a pairing channel different from the communication channel to which the mobility is connected to the communication network, using the pairing identifier of the mobility and the pairing identifier of the dispenser.

14. The communication method for supplying hydrogen fuel according to claim 11, wherein the dispenser identification information included in the DDP response message includes the IP address of the dispenser, the TCP port number of the dispenser, or the UDP port number of the dispenser.

15. A communication method for hydrogen fuel supply according to claim 11, further comprising the steps of: negotiating a communication protocol or fuel supply protocol between the mobility and the dispenser after pairing between the mobility and the dispenser has been performed; and monitoring and controlling the process by which the dispenser supplies hydrogen fuel to the mobility, which is performed based on the fuel supply protocol.

16. A communication device for supplying hydrogen fuel to a hydrogen fuel mobility vehicle, comprising a memory for storing at least one instruction and a processor for executing the at least one instruction, wherein the processor broadcasts a Dispenser Discovery Protocol (DDP) request message via a communication network that includes a dispenser that supplies hydrogen fuel to the mobility vehicle by the at least one instruction, receives a DDP response message from the dispenser containing the dispenser's identification information on the communication network, and performs authentication for pairing between the mobility vehicle and the dispenser using the dispenser's identification information in the DDP response message.

17. The communication device according to claim 16, wherein, before the DDP request message is broadcast, the IP address of the mobility used in the communication network including the dispenser is determined, and the mobility is connected to the communication network via a communication channel based on the IP address of the mobility.

18. The communication device according to claim 16, wherein the DDP request message includes a pairing identifier (ID, Identification) of the mobility, the dispenser identification information included in the DDP response message includes a pairing identifier (ID, Identification) of the dispenser, and when authentication for pairing between the mobility and the dispenser is performed, the pairing identifier of the mobility and the pairing identifier of the dispenser are used to perform authentication for pairing between the mobility and the dispenser.

19. The communication device according to claim 18, wherein when authentication for pairing between the mobility and the dispenser is performed, authentication for pairing between the mobility and the dispenser is performed via a pairing channel different from the communication channel to which the mobility is connected to the communication network, using the pairing identifier of the mobility and the pairing identifier of the dispenser.

20. The communication device according to claim 16, wherein the identification information of the dispenser included in the DDP response message includes the IP address of the dispenser, the TCP port number of the dispenser, or the UDP port number of the dispenser.

Images