Communication method and apparatus for hydrogen filling

Abstract

The present invention provides a hydrogen filling process that can improve the safety, compatibility, efficiency, and reliability of hydrogen filling, a communication protocol negotiation method for the hydrogen filling process, a filling protocol negotiation method, and a filling parameter negotiation method, and an apparatus that uses the same. [Solution] A method according to one embodiment of the present invention includes steps of negotiating a communication protocol with a dispenser that supplies hydrogen to mobility, negotiating a fuel supply protocol with the dispenser for receiving a supply of hydrogen fuel from the dispenser, and negotiating fuel supply parameters with the dispenser based on the fuel supply protocol.

Description

[Technical Field]

[0001] The present invention relates to communication technology for hydrogen fueling of hydrogen fueled mobility, and more particularly to a hydrogen fueling process that can improve the safety, compatibility, efficiency, and reliability of hydrogen fueling, a communication protocol negotiation method for the hydrogen fueling process, a fueling protocol negotiation method, and a fueling parameter negotiation method, and an apparatus using the same. [Background technology]

[0002] The content described in this section is merely intended to provide background information for the present embodiment and is not intended to provide prior art. A hydrogen vehicle or hydrogen electric vehicle is a pollution-free vehicle that runs on electrical energy generated when high-pressure hydrogen stored in the vehicle meets atmospheric air. Hydrogen electric vehicles are also called fuel cell electric vehicles (FCEVs). Most hydrogen electric vehicles use hydrogen as their energy source and generate electricity using a fuel cell system. Hydrogen electric vehicles emit only pure water (H2O) during the electricity generation process and have the ability to remove ultrafine dust particles from the air while in operation, making them garnering attention as a future eco-friendly form of mobility. Given that hydrogen, the fuel, is limitless on Earth and the energy production process is environmentally friendly, hydrogen electric vehicles are attracting widespread attention as a technology with potential for industrial application.

[0003] Hydrogen-fueled mobility refers to mobility that uses hydrogen as an energy source or hydrogen as fuel to generate electrical energy and use it to drive an electric motor. In addition to the hydrogen electric vehicle mentioned above, hydrogen-fueled mobility includes aerial mobility as well as industrial trucks, trains, ships, and aircraft, and can include devices that generate electrical energy using hydrogen as fuel and use it to drive them.

[0004] Most hydrogen electric vehicles generate electrical energy through an electrochemical reaction between the hydrogen and oxygen, which is delivered to the fuel cell stack through high-pressure hydrogen stored safely in a hydrogen fuel storage tank and oxygen supplied through an air supply system. The generated electrical energy is converted into kinetic energy through the drive motor to power the hydrogen electric vehicle, and the hydrogen electric vehicle has the advantage of discharging only pure water through the exhaust while in motion.

[0005] Meanwhile, the concept of a hydrogen fueled car, rather than a hydrogen electric car, is also a vehicle that uses hydrogen as fuel, but a hydrogen fueled car uses the heat generated by directly burning hydrogen in the engine (ICE, Internal Combustion Engine) to drive the electric motor. The method of refueling hydrogen for a hydrogen fueled car is not much different from the method of refueling hydrogen for a hydrogen electric car.

[0006] The ultimate goal of the control technique for supplying hydrogen to vehicles that use hydrogen as fuel is to control the temperature and pressure of the compressed hydrogen storage system (CHSS) on the fuel cell side so that it operates within the limit temperature and pressure conditions for safe hydrogen filling.

[0007] The hydrogen refueling process, control techniques, and protocols for conventional hydrogen electric vehicles were established at a time when wired / wireless communication technologies and control computing techniques were not yet mature, and do not fully reflect recent advances in information and communications technology (ICT).As a result, conventional hydrogen refueling technologies for hydrogen electric vehicles are inefficient, slow, and unsuitable for large-volume hydrogen refueling.

[0008] In particular, in the case of wireless hydrogen filling communication, most hydrogen filling control devices use one-way infrared communication devices, and therefore wireless-based hydrogen filling communication still has the limitations and vulnerabilities of one-way communication. Summary of the Invention [Problem to be solved by the invention]

[0009] In order to solve the above problems, the object of the present invention is to provide a hydrogen fueling process for hydrogen fueled mobility and a communication protocol for the process that overcomes the limitations and vulnerabilities of existing one-way communication and can improve the safety, compatibility, efficiency, and reliability of hydrogen filling, as well as a method for negotiating a communication protocol, a fueling protocol, and a filling parameter negotiation for the hydrogen filling process, and an apparatus using the same.

[0010] Another object of the present invention is to provide a hydrogen fueling communication two-way process, a communication protocol negotiation process that considers two-way / one-way communication, and an apparatus that utilizes the same, which can be controlled to determine whether a conventional communication medium or an advanced communication medium is used so that hydrogen fuel mobility and dispensers can effectively achieve their hydrogen fueling goals. [Means for solving the problem]

[0011] To achieve the above object, a communication method for hydrogen fueling according to one embodiment of the present invention is a communication method for hydrogen fueling performed by a communication device of hydrogen-fueled mobility, and includes a step of negotiating a communication protocol with a dispenser that supplies hydrogen to the mobility, a step of negotiating a fuel supply protocol with the dispenser for receiving hydrogen fuel from the dispenser, and a step of negotiating fuel supply parameters based on the fuel supply protocol with the dispenser.

[0012] The step of negotiating a communication protocol may include a step of transmitting a message including information on a first communication protocol applicable to the mobility to the dispenser, and a step of receiving a message from the dispenser including information on a second communication protocol selected from common communication protocols applicable between the mobility and the dispenser.

[0013] The information about the first communication protocol may include at least one of an index of the first communication protocol, a name of the first communication protocol, a version of the first communication protocol, and a preference for the first communication protocol.

[0014] The message including the information about the second communication protocol may further include information about whether the communication protocol negotiation was successful.

[0015] The step of negotiating a fuel supply protocol may include a step of transmitting a message including information on a first fuel supply protocol applicable to the mobility to the dispenser based on the result of the communication protocol negotiation, and a step of receiving a message including information on a second fuel supply protocol selected from fuel supply protocols commonly applicable between the mobility and the dispenser from the dispenser.

[0016] The information for the first fuel supply protocol may include at least one of an index of the first fuel supply protocol, a name of the first fuel supply protocol, a version of the first fuel supply protocol, a sub-protocol of the first fuel supply protocol, and a preference for the first fuel supply protocol.

[0017] The message containing information regarding the second fueling protocol may further contain information regarding whether the fueling protocol negotiation resulted in success or failure.

[0018] The step of negotiating fuel supply parameters may include a step of transmitting a message to the dispenser including information on the mobility-side fuel supply parameters required by the second fuel supply protocol selected as a result of the fuel supply protocol negotiation, and a step of receiving a message from the dispenser including dispenser-side compatibility information for the mobility-side fuel supply parameters.

[0019] The step of negotiating fuel supply parameters may include receiving a message from the dispenser including information on dispenser-side fuel supply parameters required by a second fuel supply protocol selected as a result of the fuel supply protocol negotiation, and transmitting a message to the dispenser including mobility-side compatibility information for the dispenser-side fuel supply parameters.

[0020] 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 the fuel supply parameters if the fuel supply parameters become incompatible between the mobility and the dispenser as a result of the fuel supply parameter negotiation.

[0021] A communication method according to one embodiment of the present invention may further include a step of determining a third communication protocol and a third fuel supply protocol based on a predetermined policy when the fuel supply parameters are incompatible between the mobility and the dispenser as a result of the fuel supply parameter negotiation, and a step of supplying hydrogen based on the third communication protocol and the third fuel supply protocol.

[0022] The communication method according to one embodiment of the present invention may further include terminating communication between the dispenser and the mobility if the fuel supply parameters are incompatible between the mobility and the dispenser as a result of the fuel supply parameter negotiation.

[0023] The communication method according to an embodiment of the present invention may further include performing a discovery and pairing process with the dispenser using the first communication technology.

[0024] If the result of the communication protocol negotiation relates to a second communication technology, the steps of negotiating a fueling protocol and negotiating fueling parameters may be performed using the second communication technology.

[0025] During the discovery and pairing process, information regarding interoperability or compatibility between the mobility and the dispenser may be shared.

[0026] A communication device for hydrogen-fueled 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, using the at least one instruction, can negotiate a communication protocol with a dispenser that supplies hydrogen to the mobility, can negotiate with the dispenser a fuel supply protocol for receiving hydrogen fuel from the dispenser, and can negotiate with the dispenser fuel supply parameters based on the fuel supply protocol.

[0027] When negotiating a communication protocol, the processor can transmit a message including information about a first communication protocol applicable to the mobility to the dispenser, and can receive a message from the dispenser including information about a second communication protocol selected from common communication protocols applicable between the mobility and the dispenser.

[0028] The information regarding the first communication protocol may include at least one of an index of the first communication protocol, a name of the first communication protocol, a version of the first communication protocol, and a preference for the first communication protocol, and the message including the information regarding the second communication protocol may further include information regarding whether the communication protocol negotiation was successful.

[0029] When negotiating a fuel supply protocol, the processor can transmit a message including information on a first fuel supply protocol applicable to the mobility to the dispenser based on the result of the communication protocol negotiation, and can receive a message from the dispenser including information on a second fuel supply protocol selected from among fuel supply protocols commonly applicable between the mobility and the dispenser.

[0030] The information regarding the first fuel supply protocol may include at least one of an index of the first fuel supply protocol, a name of the first fuel supply protocol, a version of the first fuel supply protocol, a sub-protocol of the first fuel supply protocol, and a preference for the first fuel supply protocol, and the message including information regarding the second fuel supply protocol may further include information regarding whether the fuel supply protocol negotiation was successful.

[0031] When negotiating fuel supply parameters, the processor can transmit a message to the dispenser including information on the mobility-side fuel supply parameters required by the second fuel supply protocol selected as a result of the fuel supply protocol negotiation, and can receive a message from the dispenser including dispenser-side compatibility information for the mobility-side fuel supply parameters.

[0032] When negotiating fuel supply parameters, the processor can receive a message from the dispenser including information on dispenser-side fuel supply parameters required by a second fuel supply protocol selected as a result of the fuel supply protocol negotiation, and can transmit a message to the dispenser including mobility-side compatibility information for the dispenser-side fuel supply parameters.

[0033] The processor may, by at least one instruction, renegotiate at least one of the communication protocol and the fuel supply parameters if the fuel supply parameter negotiation results in the fuel supply parameters being incompatible between the mobility and the dispenser.

[0034] The processor may, by at least one instruction, determine a third communication protocol and a third fuel supply protocol based on a predetermined policy when the fuel supply parameter negotiation results in incompatible fuel supply parameters between the mobility and the dispenser, and hydrogen may be supplied based on the third communication protocol and the third fuel supply protocol.

[0035] The processor may, with at least one instruction, terminate communication between the dispenser and the mobility if the fueling parameter negotiation results in incompatible fueling parameters between the mobility and the dispenser.

[0036] The processor, in accordance with at least one instruction, can perform a discovery and pairing process with the dispenser using a first communication technology, and, if the result of the communication protocol negotiation relates to a second communication technology, can negotiate a fuel delivery protocol and fuel delivery parameters using the second communication technology.

[0037] When the processor performs the discovery and pairing process, information regarding interoperability or compatibility between the mobility and the dispenser can be shared.

[0038] A communication method for hydrogen fueling performed by a dispenser that supplies hydrogen fuel to a hydrogen-fueled mobility according to one embodiment of the present invention may include a step of negotiating a communication protocol with the mobility, a step of negotiating a fueling protocol with the mobility for fueling hydrogen to the mobility, and a step of negotiating fueling parameters based on the fueling protocol with the mobility.

[0039] A communication device for hydrogen fuel supply arranged in a dispenser that supplies hydrogen fuel to hydrogen-fueled mobility in one embodiment of the present invention includes a memory that stores at least one or more instructions; and a processor that executes at least one instruction, wherein the processor is capable of negotiating a communication protocol with the mobility, negotiating a fuel supply protocol with the mobility for fueling hydrogen to the mobility, and negotiating fuel supply parameters based on the fuel supply protocol with the mobility, using the at least one or more instructions. [Effects of the Invention]

[0040] According to an embodiment of the present invention, a communication method for hydrogen fuel supply and a device using the same, i.e., a vehicle / mobility hydrogen filling control device or communication control device, can overcome the limitations and vulnerabilities of existing one-way communication in the hydrogen fueling process of hydrogen fueled mobility including fuel cell electric vehicles (FCEVs) and hydrogen fuel engines and the communication protocol therefor, thereby improving the safety, compatibility, efficiency, and reliability of hydrogen filling.

[0041] Furthermore, according to one embodiment of the present invention, a communication protocol negotiation, fuel supply protocol negotiation, and parameter exchange method and communication protocol fallback rule for hydrogen fuel supply can be provided, in which the mobility and the dispenser take into account the priority based on the mobility or dispenser's preference, but maximize interoperability between the mobility and the dispenser, and consider backward compatibility to select the communication protocol required to execute the protocol for hydrogen fuel supply based on the use case.

[0042] Furthermore, according to one embodiment of the present invention, the rules and procedures necessary for communication protocol negotiation, fuel supply protocol negotiation, and fuel supply parameter exchange can be provided to effectively determine whether a conventional communication medium or an advanced communication medium is used so that mobility and dispensers can cooperate to effectively achieve hydrogen fueling goals. [Brief explanation of the drawings]

[0043] [Figure 1] 1 is a conceptual diagram of a hydrogen filling system for a fuel cell electric vehicle (FCEV) to which a two-way hydrogen filling communication process according to an embodiment of the present invention can be applied. [Figure 2]FIG. 2 is a partially enlarged view illustrating the physical fastening structure between the FCEV and the dispenser in the hydrogen filling system of FIG. 1. [Figure 3] 2 is a graph for explaining changes in the state of hydrogen fuel that occur during the hydrogen filling process using the hydrogen filling system of FIG. 1. [Figure 4] 1 is a framework for functional blocks that perform a series of hydrogen filling procedures that can employ a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 5] 1 is an exemplary diagram illustrating a communication stack related to each use case that can be adopted in a hydrogen filling communication two-way process according to one embodiment of the present invention, focusing on the OSI (Open Systems Interconnection reference model) 7 layer. [Figure 6] 1 is an exemplary diagram illustrating a pairing process of a discovery and pairing procedure that can be adopted in a hydrogen filling communication two-way process according to an embodiment of the present invention. FIG. [Figure 7] 1 is an exemplary diagram illustrating backward compatibility that can be adopted in a hydrogen filling communication two-way process according to an embodiment of the present invention. [Figure 8] 1 is an exemplary diagram illustrating backward compatibility that can be adopted in a hydrogen filling communication two-way process according to an embodiment of the present invention. [Figure 9] 1 is an exemplary diagram illustrating a communication data usage classification that can be adopted in a hydrogen filling communication two-way process according to an embodiment of the present invention and backward compatibility in the communication data usage classification. FIG. [Figure 10] 1 is a flowchart illustrating an authentication process of a communication security procedure that can be employed in a two-way hydrogen filling communication process according to an embodiment of the present invention. [Figure 11]1 is a flowchart illustrating a communication protocol negotiation procedure that can be employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 12] 10 is a flowchart illustrating a fuel supply protocol negotiation procedure in a two-way hydrogen filling communication process according to an embodiment of the present invention. [Figure 13] 1 is a flow chart illustrating a fueling parameter exchange / negotiation procedure that may be employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 14] 1 is a conceptual diagram illustrating a table of parameters transmitted from the mobility side to the dispenser side in a fuel supply parameter negotiation / exchange process according to one embodiment of the present invention. [Figure 15] 1 is a conceptual diagram illustrating a table of parameters transmitted from a dispenser to a mobility side in a fuel supply parameter negotiation / exchange process according to one embodiment of the present invention. [Figure 16] FIG. 1 is a conceptual block diagram of the internal structure of a generalized computing system that may be installed in a hydrogen fuel mobility vehicle, dispenser, and / or filling station as a communication device, communication control device, and / or electronic control device for hydrogen fuel supply according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0044] In addition to the above objects, other objects and features of the present invention will become apparent from the description of the embodiments with reference to the accompanying drawings. While the present invention can be modified in various ways and has various embodiments, specific embodiments will be illustrated in the drawings and described in detail, but it should be understood that this is not intended to limit the present invention to the specific embodiments, and that the present invention includes all modifications, equivalents, and alternatives that fall within the spirit and technical scope of the present invention.

[0045] Terms such as "first," "second," "A," and "B" may be used to describe various components, but the components should not be limited by these terms. These terms are used only to distinguish one component from another. For example, a first component may be designated as a second component, and similarly, a second component may be designated as a first component, without departing from the scope of the present invention. The term "and / or" includes a combination of multiple associated listed items or any of multiple associated listed items.

[0046] In the examples of this application, "at least one of A and B" may mean "at least one of A or B" or "at least one of a combination of one or more of A and B." Also, in the examples of this application, "one or more of A and B" may mean "one or more of A or B" or "one or more of a combination of one or more of A and B."

[0047] When a component is said to be "coupled" or "connected" to another component, it should be understood that it may be directly coupled or connected to the other component, but that there may be other components in between. Conversely, when a component is said to be "directly coupled" or "directly connected" to another component, it should be understood that there are no other components in between.

[0048] The terms used in this application are merely used to describe specific embodiments and are not intended to limit the present invention. The singular expressions include the plural expressions unless the context clearly dictates otherwise. In this application, the terms "comprise" or "have" are intended to specify the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, and should be understood not to preclude the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0049] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. Terms as defined in commonly used dictionaries should be interpreted to have a meaning consistent with the meaning they have in the context of the relevant art, and should not be interpreted in an idealized or overly formal sense unless expressly defined in this application.

[0050] Some terms used in this specification are defined as follows: Hydrogen electric vehicles generally include hydrogen fuel cell electric vehicles (FCEVs) that use fuel cells or ICE (internal combustion engine)-based vehicles that use hydrogen as fuel. The hydrogen electric vehicles described below may also be simply referred to as FCEVs.

[0051] Although the following embodiments are primarily described with reference to a hydrogen fuel cell vehicle, other embodiments of the present invention may include an ICE-based hydrogen vehicle that uses hydrogen as fuel. In the following embodiments, a hydrogen fueling protocol and / or a communication protocol for hydrogen fuel supply are disclosed with reference to a hydrogen fuel cell vehicle, and according to other embodiments of the present invention, the hydrogen fuel supply protocol and / or the communication protocol for hydrogen fuel supply disclosed in the following embodiments may also be applied to an ICE-based hydrogen vehicle.

[0052] The hydrogen fluid fuel may include gaseous hydrogen fuel or liquid hydrogen fuel. A compressed hydrogen storage system (CHSS) can include at least one tank mounted on a vehicle and a device coupled to the tank for compressing and storing hydrogen in the tank.

[0053] A pressure relief device (PRD) is a device placed in a CHSS that can isolate stored hydrogen from the vehicle's hydrogen filling system and the surrounding environment, and can discharge hydrogen to the outside.

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

[0055] The pressure ramp rate (PRR) is expressed in MPa / min and refers to the rate at which the pressure of the CHSS increases. Average Pressure Ramp Rate (APRR) refers to the average pressure ramp rate from the start to the end of hydrogen fueling. Pre-cooling basically refers to the process of pre-cooling hydrogen at a hydrogen filling station before filling it.

[0056] The dispenser is a component that delivers pre-cooled hydrogen to the CHSS. The dispenser is installed at the hydrogen filling station to perform hydrogen filling between the hydrogen storage tank at the hydrogen filling station and the vehicle's CHSS. A nozzle refers to a device that is connected to a dispenser and coupled to a receptacle of a hydrogen electric vehicle to allow delivery of hydrogen fuel. A fueling session may be used to encompass a communication session across use cases for hydrogen fueling.

[0057] Interoperability can refer to the state in which components of a system relative to one another can work together to accomplish 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 easily use information securely, effectively, and with little or no inconvenience to users.

[0058] Correlation / Association can involve the establishment of a relationship between two peer communicating entities. Command and control communication may refer to communication between an electric vehicle hydrogen fuel supply system and a hydrogen electric vehicle to exchange information necessary to initiate, control, and terminate the hydrogen fueling process.

[0059] While the following detailed description illustrates embodiments related to a hydrogen electric vehicle or a fuel cell electric vehicle (FCEV), it will be apparent to those skilled in the art that the concept of the present invention can be applied to various types of hydrogen-fueled mobility. Hydrogen-fueled mobility refers to a type of mobility that uses hydrogen as an energy source or hydrogen as fuel to generate electrical energy and use it to drive an electric motor. In addition to hydrogen-fueled vehicles, hydrogen-fueled mobility can also include aerial mobility, industrial trucks, trains, ships, aircraft, and even devices that use hydrogen as fuel to generate electrical energy and use it to drive.

[0060] Furthermore, the two-way communication process for hydrogen filling of the present invention can be partially applied not only to hydrogen-fueled mobility but also to buildings or facilities that use hydrogen as an energy source. In the following description, the hydrogen fuel may include at least one of gaseous hydrogen and liquid hydrogen, and may essentially mean compressed hydrogen, but is not limited thereto.

[0061] For the sake of convenience, the vehicle using the hydrogen filling communication two-way process will be described as a hydrogen electric vehicle (FCEV), but it is not limited to this configuration and can also include hybrid electric vehicles (EVs) that use hydrogen as fuel, and internal combustion engine (ICE) vehicles.

[0062] In the following description, some or all of the processes of the communication method, communication protocol negotiation method, hydrogen filling (fueling) protocol negotiation method, and hydrogen filling (fueling) parameter negotiation method performed in hydrogen-fueled mobility may be performed by an electronic control unit (ECU), communication device, or communication control device within the hydrogen-fueled mobility.

[0063] In the following description, some or all of the steps of the communication method, communication protocol negotiation method, hydrogen filling (fueling) protocol negotiation method, hydrogen filling (fueling) parameter negotiation method, hydrogen filling (fueling) method, and hydrogen filling (fueling) control method performed by the dispenser may be performed by a controller, electronic control device, communication device, or communication control device of the dispenser. Also, some of the steps of the methods may be performed by a controller, electronic control device, communication device, or communication control device of a filling station associated with the dispenser.

[0064] Meanwhile, even if a technology was publicly known before the filing date of the present invention, it may be included as part of the configuration of the present invention, if necessary, and such technology will be described in this specification to the extent that it does not obscure the gist of the present invention. However, in describing the configuration of the present invention, detailed descriptions of technology that was publicly known before the filing date and that would be obvious to a person skilled in the art may obscure the gist of the present invention, so excessively detailed descriptions of publicly known technology will be omitted. Furthermore, the gist of the present invention is not intended to claim rights to such publicly known technology, and the content of publicly known technology may be included as part of the present invention to the extent that it does not deviate from the gist of the present invention.

[0065] For example, IrDA technology can be used for one-way communication, short-range wireless communication technology (Bluetooth (registered trademark), WLAN, UWB) can be used for two-way communication, and wired communication technology for one-way / two-way communication can be used as publicly known technology prior to the filing of the present invention, and at least some of these publicly known technologies can be applied as elemental technologies necessary to implement the present invention.

[0066] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. Figure 1 is a conceptual diagram of a hydrogen filling system for a hydrogen electric vehicle (FCEV) to which a two-way hydrogen filling 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 filling system of Figure 1. And Figure 3 is a graph illustrating changes in the state of hydrogen fuel that occur during the hydrogen filling process using the hydrogen filling system of Figure 1.

[0067] Referring to FIG. 1, a hydrogen filling system can be broadly configured to include a hydrogen filling station and a hydrogen electric vehicle 100 . In addition to the mechanical, mechanical, electrical, electronic, and communication devices that are basically required for a vehicle, the hydrogen electric vehicle 100 may be equipped with an electronic control device 110 for hydrogen filling, a vehicle system 120, a vehicle tank 130, and a receptacle 150.

[0068] The electronic control unit 110 can transmit and receive signals and data via wire or wirelessly to and from a hydrogen filling station or an electronic control unit 210 at the hydrogen filling station, process the signals, and control hydrogen filling on the vehicle side. The electronic control unit 110 can be configured as at least a part of another electronic control unit installed in the vehicle, or vice versa, and can be referred to as a first electronic control unit or electronic control unit #1.

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

[0070] There may be at least one, and preferably a plurality, of vehicle tanks 130. The vehicle tanks 130 can compress and store hydrogen supplied from a hydrogen filling station and release the stored hydrogen under the control of the vehicle safety system.

[0071] The vehicle tank 130 may also correspond to a hydrogen storage system attached to a vehicle. In this case, the hydrogen storage system may be composed of a high-pressure hydrogen storage tank, a pressure control device, high-pressure piping, and an external frame. The high-pressure hydrogen storage tank may have a capacity of tens to hundreds of liters and may be configured with small storage tanks connected in parallel. A boss unit through which hydrogen fuel can enter and exit may be attached to the high-pressure hydrogen storage tank, and hydrogen filling and release can be controlled through the boss unit. A valve, a pressure reducing mechanism, and various sensors for measurement 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" herein may refer to a CHSS.

[0072] The hydrogen electric vehicle 100 described above may be equipped with a fuel cell system including a fuel cell stack, but is not limited thereto, and for convenience of explanation, may be simply referred to as an "FCEV," a "vehicle," or a mobility 100. In the following description, the subject simply referred to as a vehicle or mobility may be understood to include not only the hydrogen electric vehicle 100 but also a vehicle / mobility that uses hydrogen as fuel.

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

[0074] Dispenser 200 can supply hydrogen supplied from hydrogen tank 230 to a vehicle through nozzle 250 firmly connected to receptacle 150 of the vehicle under the control of filling station system 220. Dispenser 200 can include electronic control unit 210 inside the housing, but is not limited to this. Nozzle 250 can basically be installed at the end of a cable extending a certain length outside the housing of dispenser 200.

[0075] The electronic control unit 210 transmits and receives signals and data via wire or wirelessly to and from the vehicle's first electronic control unit 110 for hydrogen filling, processes the signals, and controls hydrogen filling at the hydrogen filling station. The electronic control unit 210 can exchange preset signals and data with the filling station system 220. The electronic control unit 210 may also be referred to as the second electronic control unit or electronic control unit #2.

[0076] The first electronic control unit 110 and the second electronic control unit 210 may each be configured with a plurality of electronic control units, and may be configured to operate by matching different electronic control units for each communication protocol. This may be useful when fallback is required for backward compatibility, or when one-way communication is required because two-way communication is not available. Also, this may be useful when using a combination of different communication methods, such as using WiFi when performing actual charging after pairing via NFC.

[0077] The filling station system 220 can monitor and adjust the pressure, speed, and temperature of the hydrogen released from the hydrogen tank 230 using signals and / or data from the second electronic control device. To this end, the filling station system 220 can control the operation of the station box 240 connected to the outlet and release valve of the hydrogen tank 230. The filling station system 220 can also be referred to as a filling station safety system.

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

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

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

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

[0082] The nozzle 250 may be connected to the hydrogen fuel supply system of the dispenser 200 through a length of conduit or flexible pipe. The nozzle 250 may be shaped and configured to tightly and securely mate with a receptacle on the vehicle. 2, the nozzle 250 can be engaged with the receptacle 150. At this time, a first sensor 160 installed in the vehicle and a second sensor 260 attached to the nozzle 250 transmit signals and information regarding the engagement state of the nozzle 250 and the receptacle 150 to a first electronic control unit or a vehicle safety system, and can also be transmitted to a second electronic control unit or a filling station safety system.

[0083] Pre-cooled hydrogen fuel from the hydrogen filling station is supplied to the hydrogen electric vehicle 100 via the dispenser 200. At this time, the hydrogen filling process can be described by parameters including the pressure rise rate (PRR) and / or the average pressure rise rate (APRR). The interface between the hydrogen filling station and the vehicle 100 may be handled by the dispenser 200. The dispenser 200 may be configured to combine information indirectly acquired from the vehicle tank 130 and fuel supply information from the hydrogen filling station to control the target pressure and injection rate for hydrogen filling.

[0084] In existing technology, there are two methods for transmitting information from the vehicle 100 to the dispenser 200: a communication method and a non-communication method. When communication is used, the temperature and pressure values ​​of the vehicle tank 130 of the vehicle 100 are simply transmitted unidirectionally to the dispenser 200, and the dispenser 200 does not actively use the information, but only uses it as a safety standard such as an emergency stop at the limit temperature and pressure. In addition, the hydrogen filling protocol for safe and quick filling is managed by the dispenser 200, and it only has a minimal safety management device that automatically releases hydrogen through a pressure relief device (PRD) without active safety management of the vehicle tank 130.

[0085] Meanwhile, to address the phenomenon of the temperature of hydrogen gas rising during hydrogen filling (see FIG. 3), the hydrogen filling station may be equipped with a pre-cooler. The pre-cooler can lower the temperature of the hydrogen fuel through pre-cooling. The pre-cooler may be installed in or connected to at least one of the hydrogen tank 230 and the station box 240. Of course, the pre-cooler may also be installed in or connected to the piping that transports hydrogen at the hydrogen filling station.

[0086] A filling control logic may be installed inside the dispenser 200 or in the second electronic control device, and the filling control logic may be used to control the hydrogen fueling process using status information such as the temperature and pressure of the hydrogen fuel supplied to the vehicle or filled into the vehicle tank 130, and filling status information such as the filling rate (SOC, State of Charge) of the CHSS.

[0087] As described above, the hydrogen filling process is controlled by the dispenser 200 between the vehicle 100 and the hydrogen filling station, and the dispenser 200 may be equipped with a protocol for supplying hydrogen fuel to the vehicle according to a predetermined procedure. Such a hydrogen filling protocol may also be installed in the vehicle. The protocol installed in the vehicle and the dispenser 200 may include at least a portion of a communication protocol in accordance with an SAE standard, an ISO standard, or the like.

[0088] For minimum safety requirements, simulations are carried out through thermodynamic modeling for various situations, and the parameters derived from these simulations can be used to perform table-based or MC-formula-based partial real-time correction. Here, minimum safety requirements can include upper limits on the temperature and pressure conditions of the CHSS and guidelines for the State of Charge (SOC).

[0089] If the dispenser 200 does not actively control status values ​​related to hydrogen filling, the conventional table-based method is highly inefficient and difficult to flexibly respond to changes in surrounding conditions because it does not utilize the temperature of pre-cooled hydrogen fuel provided by the gas filling station or the temperature of the vehicle tank 130 measured by the vehicle 100. Furthermore, the conventional MC-Formula-based method corrects the temperature of pre-cooled hydrogen fuel in real time, but the calculation and application methods are complex, limiting its applicability and making it difficult to expand. As such, because the existing communication protocol was developed with the primary goal of completing safe filling, there is no alternative that can actively control unexpected situations such as excessive pre-cooling or overheating of the vehicle tank 130. This can lead to problems such as increased operating costs due to overcooling and delays in filling due to overheating.

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

[0091] Meanwhile, temperature control during the hydrogen filling process can be aimed at controlling the internal temperature of the vehicle tank 130 to 85°C or less at the time of final filling completion after receiving the supply of pre-cooled hydrogen gas. That is, as shown in the characteristic curve for hydrogen temperature during hydrogen filling shown in Figure 3, the temperature of the hydrogen fuel decreases at a constant rate in Phase I (P1), which is the pre-cooling stage of the hydrogen filling station, gradually increases due to the thermal mass of the hydrogen filling station in Phase II (P2), which is the stage of supplying hydrogen fuel to hydrogen mobility such as vehicles at the hydrogen filling station, further gradually increases due to the thermal mass of the vehicle in Phase III (P3), which is the stage of transferring hydrogen fuel from inside the vehicle to the vehicle tank, and then rapidly increases due to the heat of compression in Phase IV (P4), which is the stage of compressing and storing hydrogen fuel in the vehicle tank.

[0092] Therefore, in this embodiment, the hydrogen filling procedure can be effectively performed through active state variable control that reflects real-time measurement data through the hydrogen filling communication two-way process, and a hydrogen filling protocol can be provided for this purpose.

[0093] FIG. 4 is a framework for functional blocks that perform a series of hydrogen filling procedures that can employ a hydrogen filling communication bidirectional process according to one embodiment of the present invention (hereinafter referred to as the "hydrogen filling framework").

[0094] Referring to FIG. 4, the hydrogen filling framework includes use case (UC)-specific function blocks, such as a discovery and pairing function block (hereinafter, simply referred to as "UC1" or "UC-1"), a communication security function block (UC2 or UC-2), a communication protocol negotiation function block (UC3 or UC-3), a fueling protocol negotiation function block (UC4 or UC-4), a fueling parameter negotiation function block (UC5 or UC-5), a safety check-in function block (UC6 or UC-6), a monitoring and control function block (UC7 or UC-7), a safety check-out function block (UC8 or UC-8), a termination function block (UC9 or UC-9), an error handling function block (UC10 or UC-10), an emergency response function block (UC11 or UC-11), an error handling function block (UC12 or UC-12), an error handling function block (UC13 or UC-13), an error handling function block (UC14 or UC-14), an error handling function block (UC15 or UC-15), an error handling function block (UC16 or UC-16), an error handling function block (UC17 or UC-17), an error handling function block (UC18 or UC-18), an error handling function block (UC19 or UC-19), an error handling function block (UC20 or UC-20), an error handling function block (UC21 or UC21), an error handling function block (UC22 or UC22), an error handling function block (UC23 or UC23), an error handling function block (UC24 or UC24), an error handling function block (UC25 or UC25), an error handling function block (UC26 or UC26), an error handling function block (UC27 or UC27), an error handling function block (UC28 or UC28), an error handling function block (UC29 or UC29), an error handling function block (UC30 or UC30), an error handling function block (UC31 or UC31), handling function block (UC11 or UC-11).

[0095] Each of the UC1 to UC11 functional blocks may correspond to a time-series step (S401 to S411) as shown in Fig. 4. In this case, Fig. 4 may be understood as an operational flowchart including the time-series steps (S401 to S411). UC10 and UC11 may be individually connected to UC3 to UC8 to perform error handling and / or emergency handling in each use case.

[0096] The aforementioned use cases are functional blocks that collectively provide the entire hydrogen filling 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 filling goal.

[0097] Also, after the dispenser nozzle is connected to the vehicle receptacle, the vehicle and dispenser can perform fuel supply communication by implementing each use case in the order shown in Figure 4. However, the vehicle and dispenser can omit certain use cases if necessary due to predefined requirements.

[0098] Each of the above use cases can be implemented through communication between a hydrogen-fueled vehicle and a dispenser control system of a dispenser that supplies hydrogen as fuel to the hydrogen-fueled vehicle according to a fuel supply protocol for the hydrogen-fueled vehicle.

[0099] Meanwhile, hydrogen fuel vehicles (hereinafter simply referred to as "vehicles") and dispensers implementing the above-mentioned use cases can exchange data for vehicle identification using UC-1. To this end, the vehicle can be equipped with sensors, an electronic control unit (ECU), a transmitter, and a receiver. The receiver can be integrated with the transmitter for two-way communication.

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

[0101] Additionally, a communication channel can be established between the vehicle and the dispenser that are physically connected at the vehicle-dispenser interface. The pairing process for establishing such a communication channel can be performed using wired, optical, or wireless technology.

[0102] The discovery and pairing procedure or pairing processor may have pre-conditions that the dispenser nozzle be inserted into and firmly coupled to a vehicle fueling receptacle, which may be simply referred to as a vehicle receptacle or receptacle.

[0103] In addition, the vehicle and dispenser essentially know which communication protocol to follow. Therefore, communication following UC-1 is a post-condition of the discovery and pairing procedure or pairing process and can only depend on the communication protocol agreed upon in the current use case. If a communication protocol outside the agreed upon range is selected by the vehicle or dispenser, the selected communication will not be carried out. In other words, even if the pairing process is successfully completed, authorization for fuel or fuel supply may not be granted.

[0104] All methods used to pair the vehicle and dispenser shall be configured so as not to increase the risk of ignition or explosion beyond an acceptable level. For example, all wired pairing methods shall be configured to mitigate or eliminate spark hazards due to static discharge.

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

[0106] Referring again to FIG. 4, a communication method for hydrogen fueling according to one embodiment of the present invention is a communication method for hydrogen fueling performed by a communication device of a hydrogen-fueled mobility, and may include a step of negotiating a communication protocol with a dispenser that supplies hydrogen to the mobility (S403), a step of negotiating a fuel supply protocol with the dispenser for receiving hydrogen fuel from the dispenser (S404), and a step of negotiating fuel supply parameters based on the fuel supply protocol with the dispenser (S405).

[0107] A communication method for hydrogen fueling performed by a dispenser that supplies hydrogen fuel to a hydrogen-fueled mobility according to one embodiment of the present invention may include a step of negotiating a communication protocol with the mobility (S403), a step of negotiating a fueling protocol with the mobility for fueling hydrogen to the mobility (S404), and a step of negotiating fueling parameters based on the fueling protocol with the mobility (S405).

[0108] FIG. 5 is an exemplary diagram illustrating a communication stack related to each use case that can be employed in a two-way hydrogen filling communication process according to an embodiment of the present invention, focusing on the seven layers of the OSI (Open Systems Interconnection reference model).

[0109] As illustrated in Figure 5, the communication stack associated with the use case of the hydrogen filling communication two-way process (simply referred to as the "hydrogen filling 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 of the OSI seven-layer hierarchy.

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

[0111] The hydrogen filling communication stack can also include an IPv6 (Internet Protocol Version 6) protocol 520 as a protocol of the network layer of the OSI 7 layer.

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

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

[0114] In addition, the hydrogen filling communication stack can include a JSON-based session protocol 550 as a protocol of the session layer of the OSI 7 layer. The JSON-based session protocol 550 can be used when communicating between a vehicle and a dispenser or when sending data between the electronic control unit of the vehicle and the electronic control unit of the filling station.

[0115] The hydrogen filling communication stack can also include JSON (JavaScript object notation) 560 as a protocol in the representation layer of the OSI 7 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 a vehicle's electronic control unit and a filling station's electronic control unit.

[0116] The hydrogen filling communication stack may also include hydrogen filling-related fueling protocols (FP) 570 as protocols in the application layer of the OSI 7 layer. The fueling protocols 570 may include a first fueling protocol FP1, a second fueling protocol FP2, and an n-th fueling protocol FPn, where n may be any natural number greater than or equal to 3.

[0117] In yet another embodiment, the hydrogen filling communication stack described above may be configured to use protocols such as programmable logic controller (PLC) and WLAN as protocols for the data link, physical layer, and network layer; TCP and / or IPv6 as protocols for the transmission layer and security layer; binary extensible markup language (XML) as a session layer protocol corresponding to the encoding layer; and one of the existing protocols used in electric vehicles as protocols for the representation layer and application layer. Existing protocols used in electric vehicles may include at least one protocol for direct current (DC) filling, alternate current (AC) filling, wireless power transfer (WPT), automatic connection device pantograph (ACDP), etc. of electric vehicles.

[0118] The general communication data items exchanged between the vehicle and the filling station through the hydrogen filling communication stack described above are shown in Table 1. [Table 1]

[0119] Meanwhile, use case UC1 of the discovery and pairing step (S401) in Figure 4 allows a device to identify the communication partner (vehicle or dispenser communication module) responsible for controlling the physically connected receptacle or nozzle. UC1 can also define a method for identifying incompatibilities and define a fail-safe mechanism. In this use case UC1, the vehicle and dispenser may attempt to search for a common communication technology to execute the fuel supply protocol. The vehicle and dispenser can search for each other and start communication using the search mechanism provided in the basic data link and physical layers. An additional pairing procedure is required to establish a communication channel with a device connected to the fuel supply hose assembly. If the communication channel does not guarantee correct pairing, for example, in the case of wireless communication, a separate pairing channel to transmit pairing information may be required. If pairing is implicitly guaranteed, for example, a communication channel integrated with the hose assembly may be sufficient.

[0120] Table 2 illustrates the purpose, prerequisites, and subsequent conditions of use case UC1 in the discovery and pairing phase (S401) of FIG. [Table 2]

[0121] Table 3 illustrates supported communication technologies and their respective clauses that may be utilized in use case UC1 of the discovery and pairing phase (S401) of FIG. [Table 3]

[0122] 6 is an operational flowchart illustrating in detail step S401 according to an embodiment of the present invention. Referring to FIG. 6, in the pairing process of the discovery and pairing step S401 of FIG. 4, when pairing at UCDC level 2 and UCDC level 3, the vehicle and dispenser can exchange pairing IDs and confirm each other's pairing ID.

[0123] For example, a vehicle can broadcast a message (PAIR_ID_ANNOUNCE) containing its pairing ID (PAIR_ID), i.e., a vehicle ID (vehicle_id). The dispenser can transmit a message (PAIR_ID_ACK) to the vehicle acknowledging that it has received the vehicle ID from the vehicle. The vehicle can transmit a message (PAIR_ID_CONFIRM) to the dispenser confirming that it has successfully received the ACK message indicating that the dispenser has received the vehicle ID.

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

[0125] This transmission-echo-verification method allows the vehicle and dispenser to use a session-specific randomized pairing ID, which solves the problem of protecting personal information when exchanging pairing IDs. In other words, trust in the pairing process is established by subsequent processes, and for this reason, the session-specific pairing ID is included in the data used to establish trust.

[0126] On the other hand, if secure communication is supported at a particular UCDC level, at least one of the vehicle and the dispenser may verify that the pairing provides sufficient information to secure the communication channel for all methods used to pair the vehicle and the dispenser. For example, pairing may include exchanging encryption keys to enable secure communication between the vehicle and the dispenser while dispensing fuel.

[0127] For reference, UCDC Level 1 does not support two-way communication, so communication channel security may not be possible. Pairing a vehicle and a dispenser at UCDC Level 2 and UCDC Level 3 may be configured to provide sufficient information to secure communications to meet a specific security level, for example, IEC 62443 Security Level 3. IEC 62443 Security Level 3 may be a security level for actors with appropriate resources and motivation.

[0128] FIG. 7 is an exemplary diagram illustrating backward compatibility that can be employed in a two-way hydrogen filling communication process according to an embodiment of the present invention. Referring to Figure 7, hydrogen filling devices can be made backward compatible with existing devices for interoperability. When devices are classified based on interoperability, hydrogen filling devices and their communication devices can be classified into Type 0, Type 1, Type 2, and Type 3.

[0129] Type 0 may refer to a device that does not support communication for fueling or cannot receive the corresponding communication message. Type 1 may refer to devices that support IrDA communication for fuel delivery. Type 1 devices can fallback to Type 0 devices.

[0130] Type 2 may refer to devices that support advanced communication (AC). Type 2 devices can fall back to Type 0 devices. Type 3 refers to devices that support IrDA and advanced communications. Type 3 devices can fall back to any one of Type 0, Type 1, and Type 2.

[0131] Advanced communication may refer to communication using a medium and specific protocol, such as wireless local area network (WLAN), Bluetooth (BT, registered trademark), near field communication (NFC, registered trademark), Wi-Fi (Wi-Fi, registered trademark), ultra-wideband (UWB), radio frequency identification (RFID), 4G, or 5G. Advanced communication may also include two-way IrDA, serial communication, vehicular Ethernet (ETH, registered trademark), high-level communication, etc. Specific protocols may include transmission control protocol / internet protocol (TCT / IP), fueling protocols, etc. High-level communication can handle all information beyond that handled by command and control communication. The data link for high-level communication may use, but is not limited to, power line communication (PLC).

[0132] In addition, the advanced communication may be a hybrid form, such as a combination of IrDA and wired, or a combination of IrDA and wireless. In the case of a combination of IrDA and wired, modifications to the nozzle and receptacle may be required.

[0133] That is, advanced communication may be a wired / wireless bidirectional communication technology, and wireless communication technologies may include various communication means such as 5G, WLAN, BLE, ETH, UWB, RFID, and NFC. Known protocols such as TCP / IP may be used as protocols for such communication means. For example, communication means considered to be wireless communication may include Bluetooth, WLAN, Wi-Fi (ISO 15118 for inductive / ACD), UWB (IEC limited consideration for ACD), etc.

[0134] In practice, hydrogen filling devices may be implemented to support communication using different technologies, and therefore the hydrogen filling communication bidirectional process of this embodiment is configured to maximize interoperability between devices.

[0135] In other words, as shown in FIG. 7, when a Type 1 device supporting Specification #1 conforming to a predetermined standard meets a Type 0 device or a Type 2 device, the Type 1 device can fall back to a Type 0 device (S610). Also, when a Type 2 device supporting Specification #2 conforming to a predetermined standard meets a Type 0 device or a Type 1 device, the Type 2 device can fall back to a Type 0 device (S620).

[0136] Then, when a Type 3 device supporting Standard #2 meets a Type 0 device, the Type 3 device can fall back to the Type 0 device (S630). When a Type 3 device meets a Type 1 device, the Type 3 device can fall back to the Type 1 device (S640). Also, when a Type 3 device meets a Type 2 device, the Type 3 device can fall back to the Type 2 device (S650).

[0137] The aforementioned Standard #1 can include SAE (Society of Automotive Engineers) standards, etc. Standard #2 can include ISO 19885-3 standards, etc.

[0138] To support the interoperability, the hydrogen filling device can perform a connection compatibility check. For example, the hydrogen filling device can perform a connection compatibility check as shown in the following scenarios 1 to 3 depending on whether or not WLAN, one of the advanced communications, is supported.

[0139] In Scenario 1, the dispenser can be equipped with an access point (AP), which is a wireless router. The dispenser can support FCEV fuel station beaconing and fuel supply methods at VSE (vehicle supply equipment). FCEVs in the vicinity of a dispenser can scan and find the dispenser and establish a WLAN link with the discovered dispenser.

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

[0141] In Scenario 3, the dispenser can support WLAN and IrDA communications. In this case, the dispenser corresponds to a Type 3 device. An FCEV, a Type 1 device, can be parked near the dispenser. The dispenser cannot yet find any WLAN clients. When the FCEV's receptacle is connected to the nozzle attached to the dispenser's cable, IrDA communication can be initiated between the FCEV and the dispenser.

[0142] FIG. 8 is an exemplary diagram illustrating backward compatibility that can be employed in a two-way hydrogen filling communication process according to an embodiment of the present invention. Referring to FIG. 8, the hydrogen filling communication two-way process of this embodiment can provide rules and principles for the FCEV and dispenser to fall back on fueling methods and communication protocols to maximize interoperability rather than necessarily selecting their most preferred communication method.

[0143] That is, when one of the vehicles and dispensers meets the other, the device with the relatively higher Type or UCDC level may be configured to fall back to match the type or level of the device with the relatively lower Type or level.

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

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

[0146] According to the above configuration, when there are two devices with the same implementation, the vehicle and dispenser can select the best one that both support. When a device with no communication (hereinafter referred to as a "no communication device") meets a device that supports one-way communication (hereinafter simply referred to as a "one-way communication device"), the latter can fall back to the no communication (No comm) device that does not support a communication method. Also, when two devices that support two-way communication meet, the two devices can maintain the two-way communication method as is. Here, UCDC compatibility can be handled separately. Also, when a device meets a no communication device, it can rely on no communication. This can be applied to all devices that support two-way communication (hereinafter simply referred to as a "two-way communication device").

[0147] In addition, when a one-way communication device meets a two-way communication device, if the two-way communication device supports both one-way and two-way communication methods, the two-way communication device can fall back to the one-way communication method. If the two-way communication device does not support one-way communication, the two-way communication device can fall back to the no-communication method to rely on no-communication.

[0148] The two-way communication device described above can be configured to support a fuel supply method using one-way communication, regardless of whether one-way communication is used. Such a two-way communication device must be able to determine whether the other party supports two-way communication. If the FCEV or dispenser does not support two-way communication, the two-way communication device can fall back to a one-way communication device that uses a compatible one-way communication method.

[0149] FIG. 9 is an exemplary diagram illustrating communication data usage classifications that can be adopted in a hydrogen filling communication two-way process according to an embodiment of the present invention and backward compatibility in the communication data usage classifications. As shown in Figure 9, vehicles and dispensers may have a pairing identity (ID), but the requirements for exchanging such identity may be classified by use classification of communication data (UCDC) levels. UCDC levels may include UCDC Level 1 (UCDC-1) (910), UCDC Level 2 (UCDC-2) (920), and UCDC Level 3 (UCDC-3) (930). UCDC levels may further include UCDC Level 0 (UCDC-0) (900).

[0150] UCDC Level 0 (900) can refer to communication where no data is transmitted or where data is transmitted but is not used by the fuel supply protocol for dispensing of hydrogen or related safety functions. UCDC Level 0 (900) does not support communication between the vehicle and the dispenser (no communication), so the dispenser cannot transmit the pairing ID to the vehicle during process control or safety functions.

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

[0152] Static data transmitted at UCDC Level 2 (920) may be used for safety functions. Such UCDC Level 2 (920) static data may be in addition to the permitted uses for static and dynamic data defined for UCDC Level 1.

[0153] At UCDC Level 3 (930), static and dynamic data may be used for dynamic control within a protocol or safety function. Such UCDC Level 3 (930) dynamic data may be in addition to the permitted uses for static and dynamic data defined for UCDC Level 2.

[0154] 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, i.e., higher levels include lower levels. A device supporting a particular UCDC level can support a device with an even lower UCDC level. Devices supporting different UCDC levels can use the highest UCDC level supported by the two devices. The above-mentioned UCDC levels can also easily support UCDC level 0. It can be seen that UCDC levels are backward compatible. In other embodiments of the present invention, backward compatibility can be effectively applied to Non-Comm, Uni-directional Comm, Bi-directional Comm, and their combinations, regardless of the UCDC level.

[0155] 4 to 8, information regarding interoperability and / or compatibility between a vehicle / mobility and a dispenser may be shared in the discovery and pairing step (S401) of Fig. 4. At this time, the interoperability and / or compatibility may be utilized in a communication protocol negotiation step (S403), a fuel supply protocol negotiation step (S404), and / or a fuel supply parameter negotiation step (S405) described below.

[0156] In another embodiment of the present invention, information regarding interoperability and / or compatibility shared between the vehicle / mobility and the dispenser in the discovery and pairing step (S401) of Fig. 4 may be updated or re-shared through a communication protocol negotiation step (S403), a fuel supply protocol negotiation step (S404), and / or a fuel supply parameter negotiation step (S405). Information regarding interoperability and / or compatibility may be updated depending on changes in the communication environment, changes in parameters affecting the fuel supply process, etc.

[0157] In another embodiment of the present invention, at least a portion of the discovery and pairing step (S401) of FIG. 4 may be referred to as a Dispenser Discovery Protocol (DDP).

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

[0159] The dispenser receives a DDPRequest and can transmit a DDPResponse in response to the DDPRequest. The DDPResponse can 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".

[0160] FIG. 10 is a flowchart illustrating an authentication process of a communication security procedure (S402) that can be adopted in a two-way hydrogen filling communication process according to an embodiment of the present invention. 10, the mobility may transmit a message requesting a list of authorization methods to the dispenser (S1010). The dispenser may transmit a response message to the mobility in response to the mobility's request for the authorization method list (S1020). The response message may include authentication method list information related to external authentication procedures such as RFID (radio frequency identification), credit cards, debit cards, etc., and its own authentication procedure.

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

[0162] Next, the mobility performs authentication using the authentication method selected previously in response to the dispenser's response, and may transmit a message requesting confirmation (Done?) of the authentication performance to the dispenser (S1050). If confirmation of the authentication performance is not received or the authentication is not completed, the above series of steps (S1010 to S1050) may be repeated. When the authentication is completed, the dispenser may transmit an authentication completion (Done(success)) message to the mobility (S1090).

[0163] According to the above-described configuration, the dispenser can verify whether the mobility is approved, i.e., whether the user of the mobility has the authority to fill with hydrogen, before proceeding further with the hydrogen filling process.

[0164] For security of the authentication process, a hydrogen filling device including at least one of a mobility device and a dispenser can establish a data link and physical layer connection between the mobility device and the dispenser, and then establish a transport layer (i.e., a TCP connection) by performing a TLS handshake for authentication and exchange keys to establish a secure communication channel. Also, while security-critical information is exchanged, UDP communication protected by DTLS can be used.

[0165] In addition, the mobility and the dispenser can successfully perform discovery and pairing procedures to establish a data link and physical layer connection. Then, the credentials necessary for authentication and key exchange can be prepared. As a result, the communication channel between the mobility and the dispenser can be encrypted and integrity protected. The dispenser can authenticate the mobility, and optionally the mobility can authenticate the dispenser.

[0166] Meanwhile, during the aforementioned TLS handshake, mobility authentication is mandatory and dispenser authentication can be optional, in which case the dispenser can act as the client and mobility can act as the server.

[0167] For a TLS handshake, the mobility and dispenser must prepare the necessary credentials. The mobility and dispenser may store the certificate chain, the private keys corresponding to the certificates, and the trust anchor certificate in a secure repository that protects them from unauthorized access.

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

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

[0170] According to another embodiment of the present invention, the purpose, prerequisites, and subsequent conditions of step S402 can be illustrated in Table 4 below. [Table 4]

[0171] 11 is a flowchart illustrating a communication protocol negotiation step (S403) that can be employed in a two-way hydrogen filling communication process according to an embodiment of the present invention. Referring to FIG. 11, the communication protocol negotiation step (S403) can include a step (S1110) of transmitting a message including information on a first communication protocol applicable to the mobility to the dispenser; and a step (S1130) of receiving a message including information on a second communication protocol selected from common communication protocols commonly applicable between the mobility and the dispenser from the dispenser.

[0172] Referring to the embodiment of Figure 11, the dispenser receives a message from the mobility including information on a first communication protocol applicable to the mobility (S1110), compares the first communication protocol with the communication protocol applicable to the dispenser, selects a second communication protocol from among common communication protocols applicable between the mobility and the dispenser, and transmits a message including information on the selected second communication protocol to the mobility (S1130).

[0173] At this time, although not shown in FIG. 11, a step of the dispenser requesting information including a list of first communication protocols applicable to the mobility from the mobility before step S1110 may be further included.

[0174] In another embodiment of the present invention, an embodiment may be provided in which the dispenser first transmits a message containing information about its applicable communication protocol to the mobility, and the mobility selects a specific communication protocol from the common communication protocols and transmits a message containing information about the selected specific communication protocol to the dispenser. At this time, the method may further include a step in which the mobility requests information including a list of communication protocols applicable to the dispenser from the dispenser.

[0175] According to one embodiment of the present invention, the purpose, prerequisites, and subsequent conditions of step S403 can be illustrated in Table 5 below. [Table 5]

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

[0177] The information about the first communication protocol may include at least one of an index of the first communication protocol, a name of the first communication protocol, a version of the first communication protocol, and a preference for the first communication protocol. According to an embodiment of the present invention, the contents of the response message transmitted and received in step S1130 may be illustrated in Table 7 below. [Table 7]

[0178] The response message including information about the second communication protocol may further include information about whether the communication protocol negotiation was successful. The above-mentioned communication protocol negotiation procedure is a procedure for identifying the communication protocol to be followed during a hydrogen filling session after the vehicle and dispenser discover and pair with each other through compatible communication channels. In particular, in this embodiment, the dispenser can take the initiative to exchange communication protocols and parameters with the vehicle. That is, in the communication method according to an embodiment of the present invention, the step of performing a discovery and pairing process with a dispenser (S401) can be performed using the first communication technology.

[0179] If the result of the communication protocol negotiation step (S403) relates to a second communication technology, the fuel supply protocol negotiation step (S404) and the fuel supply parameter negotiation step (S405) described below may be performed using the second communication technology.

[0180] In the step of performing the discovery and pairing process (S401), information regarding interoperability and / or compatibility between the mobility and the dispenser may be shared. In the process of performing steps (S403) to (S405) of the present invention, information regarding interoperability and / or compatibility between the mobility and dispenser shared in step (S401) of performing the discovery and pairing process may be updated depending on changes in the communication environment and environmental variables related to hydrogen fuel supply.

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

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

[0183] Meanwhile, the mobility or dispenser may be configured to further perform a process of falling back to a lower type or UCDC level of the other party depending on the mutual type or UCDC level confirmed in the communication protocol negotiation procedure.

[0184] In addition, in an environment where various combinations can occur, if incompatibility is found in the parameters exchanged during the negotiation procedure (UC3 to UC5) for hydrogen filling between the mobility and the dispenser, they can return to the communication protocol negotiation procedure and perform the negotiation procedure again.

[0185] In one embodiment of the present invention, prioritized communication protocols may include protocols having priorities as exemplified in Table 6 below. The dispenser will run a specific protocol (<selected protocol> The dispenser may transmit a response message including the protocol to the mobility (S1130). The specific protocol may be a common protocol selected by the dispenser, supported by both the dispenser and the mobility, and the protocol with the highest priority preferred by the mobility, such as the ISO 19885-3-2023-UCDC-3 protocol (see Table 6).

[0186] The common protocol allows the mobility and the dispenser to reach an agreement on the communication protocol to use for fueling communication.

[0187] Meanwhile, the mobility can assign priorities to the communication protocols it supports. The mobility can provide the prioritized communication protocols to the dispenser. An example of the prioritized communication protocols is shown in Table 8 below. [Table 8]

[0188] Once a communication protocol is selected in the communication protocol negotiation use case (UC3), the vehicle and dispenser can activate their respective communication protocol implementations and begin fueling protocol negotiation. Fueling protocol negotiation is a procedure in which the vehicle and dispenser search for and agree on a fueling protocol to be used in a fueling session. At this stage, the vehicle and dispenser can select the vehicle's most preferred communication protocol from among the protocols they both support. A hydrogen filling communication protocol negotiation method according to one embodiment of the present invention is a hydrogen filling communication protocol negotiation method performed by a communication control device of a hydrogen-fueled mobility (100). The method includes the steps of: transmitting a first message to a communication entity associated with the dispenser (200) containing a list of at least one first fueling protocol supported by the mobility (100) and a first communication protocol required to execute the at least one first fueling protocol; and receiving a response message from the communication entity associated with the dispenser (200) containing a second communication protocol selected from the at least one first communication protocol. The communication entity associated with the dispenser 200 may be the electronic control unit 210 of the dispenser 200, or a separate communication device mounted on the dispenser 200, or an electronic control unit or a separate communication device within the filling station system 220 may communicate with the vehicle / mobility 100 on behalf of the dispenser 200.

[0189] The first message may include priority information based on the preference of the mobility 100 as shown in Table 6. Each message may be defined based on Tables 4 to 6.

[0190] At this time, the response message may include a second communication protocol selected from at least one of the first communication protocols based on priority information based on preference. The mobility 100 side or the dispenser 200 side may select the second communication protocol based on priority information based on preference, either independently or in cooperation with each other. Furthermore, the final operation of transmitting an acknowledgement message to the other party to terminate the protocol negotiation process may be mainly performed by the mobility 100 side, but may be modified to be performed by the dispenser 200 side. In this case, the dispenser 200 may first send a list of supported protocols, and then the mobility 100 may feed back the selected protocol.

[0191] The response message may include at least one of the first communication protocol and a second communication protocol selected from among common communication protocols commonly included in protocols supported by the dispenser 200 . The response message may include a second communication protocol determined by the device type that is a fallback based on interoperability and backward compatibility between the mobility 100 and the dispenser 200 from among multiple first communication protocols required by the control device of the dispenser 200 to execute the first fuel supply protocol.

[0192] At this time, according to one embodiment of the present invention, if there is no common communication protocol, the No comm. communication protocol is selected as shown in Figures 7 to 9, and a hydrogen fuel supply protocol is selected according to the No comm communication protocol according to a predetermined rule, and hydrogen can be supplied as fuel. At this time, steps S404 to S405 described below can be simplified or omitted.

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

[0194] FIG. 12 is an operational flowchart illustrating the fuel supply protocol negotiation step (S404) in the hydrogen filling communication two-way process according to an embodiment of the present invention. Referring to FIG. 12, the step of negotiating a fuel supply protocol (S404) according to one embodiment of the present invention may include a step of transmitting a message including information on a first fuel supply protocol applicable to the mobility to the dispenser (S1210) based on the result of the communication protocol negotiation (S403); and a step of receiving a message from the dispenser including information on a second fuel supply protocol selected from fuel supply protocols commonly applicable between the mobility and the dispenser (S1230).

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

[0196] The dispenser may select a common protocol between the fuel supply protocol applicable to the dispenser and the first fuel supply protocol as a hydrogen fuel supply protocol supporting the second communication protocol, and may select the second fuel supply protocol from the selected common fuel supply protocols. At this time, the second fuel supply protocol may be selected based on interoperability and / or compatibility, and the second fuel supply protocol may be selected based on mobility or a preference set by the dispenser.

[0197] Referring to the embodiment of Figure 12, the dispenser receives a message from the mobility including information on a first fuel supply protocol applicable to the mobility (S1210), compares the first fuel supply protocol with the fuel supply protocol applicable to the dispenser, selects a second fuel supply protocol from the common fuel supply protocols applicable between the mobility and the dispenser, and transmits a message including information on the selected second fuel supply protocol to the mobility (S1130).

[0198] At this time, although not shown in FIG. 12, a step of the dispenser requesting information including a list of first fuel supply protocols applicable to the mobility from the mobility before step S1210 may be further included.

[0199] In another embodiment of the present invention, an embodiment may be provided in which the dispenser first transmits a message containing information about its applicable fuel supply protocol to the mobility, and the mobility selects a specific fuel supply protocol from the common fuel supply protocols and transmits a message containing information about the selected specific fuel supply protocol to the dispenser. At this time, the method may further include a step in which the mobility requests information including a list of fuel supply protocols applicable at the dispenser from the dispenser.

[0200] According to one embodiment of the present invention, the purpose, prerequisites, and subsequent conditions of step S404 can be illustrated by the following Table 9. [Table 9]

[0201] According to one embodiment of the present invention, the contents of the messages transmitted and received in step S1210 can be illustrated by the following Table 10. [Table 10]

[0202] The information on the first fuel supply protocol may include at least one of an index of the first fuel supply protocol, a name of the first fuel supply protocol, a version of the first fuel supply protocol, a sub-protocol of the first fuel supply protocol, and a preference for the first fuel supply protocol. According to one embodiment of the present invention, the contents of the response message transmitted and received in step S1230 may be illustrated by Table 11 below. [Table 11]

[0203] The message including information about the second fuel supply protocol may further include information about whether the fuel supply protocol negotiation was successful. The contents of the message transmitted in step S1210 according to one embodiment of the present invention may be as shown in Table 12 below. [Table 12]

[0204] As shown in Table 12, the mobility can provide the dispenser with parameter information in table form, including arbitrarily assigned names for the fuel supply methods and fuel supply protocols that can be supported, revision time (year) and version information, information on whether subprotocols are available, and preference information.

[0205] In another embodiment of the present invention, the dispenser may take the initiative to exchange its own communication protocols and parameters with the mobility instead of the mobility, and may assign priorities to the communication protocols that the dispenser supports and provide them to the mobility.

[0206] In Table 11, PRHYDE (PROtocol for heavy-duty HYDrogEn refueling) is presented from one of the European projects that has developed a heavy-duty vehicle refueling protocol, RTR-HFP is presented from a type of protocol concept that improves refueling efficiency based on real-time communication, and ANN-MPC can be presented from a type of protocol concept that collects and analyzes data from the refueling site and applies predictions to actual refueling conditions.

[0207] An example of a message transmitted in step S1230 according to an embodiment of the present invention is shown in Tables 13 and 14 below. [Table 13]

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

[0209] According to Table 14, if the dispenser fails to find a compatible protocol in the fuel supply 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 (e.g., FAIL_NO_COMMON_PROTOCOL) in the ResultCode field to the mobility. The examples of Tables 13 and 14 may also be applied when the dispenser selects the second communication protocol from the common communication protocols in step S1130 of FIG. 11 and responds to the mobility.

[0210] FIG. 13 is a flowchart illustrating a fueling parameter exchange / negotiation step (S405) that can be employed in a hydrogen filling communication two-way process according to one embodiment of the present invention.

[0211] The fueling parameter exchange / negotiation step (S405) may include a step in which the mobility and the dispenser exchange detailed parameters required to execute a fueling protocol.

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

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

[0214] The mobility sends a message containing information about the fuel supply parameters of the mobility side in step S1310 and sets the Accepted field for the corresponding parameters. <pending>The data can be transmitted to the dispenser while still set to

[0215] Similarly, the dispenser transmits a message containing information about the dispenser's fuel supply parameters in step S1330, and sets the Accepted field for the corresponding parameters. <pending>It can be transmitted to mobility while being set to

[0216] The mobility sends a message including information on the fuel supply parameters of the dispenser as a response message to the message received in step S1330, and sets the Accepted field for the corresponding parameter. <ok>or <true>and respond to the dispenser (S1350).

[0217] The dispenser transmits a message including information on fuel supply parameters of the mobility side as a response message to the message received in step S1310, and sets the Accepted field for the corresponding parameter. <ok>or <true>and respond to the mobility (S1370).

[0218] At this time, the mobility and dispenser can respond by indicating whether or not each fuel supply parameter has been accepted. The Accepted field for parameters that have not been agreed upon is <false>can be displayed as:

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

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

[0221] Here, compatibility support related parameters include pressure class, CHSS category, etc., physical characteristic 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 accepted, such as a parameter called yes (true) or no (false). The above parameters may be set with information for one of pre-specified levels or set values ​​and information for a different or the same UCDC level, respectively.

[0222] On the other hand, the dispenser supports the following parameters (<DIS’s parameters> )(briefly<DIS’s params> ) and the mobility parameters, and can transmit an OK message to the mobility indicating that the information and the mobility parameters have been received and accepted (S1330, S1370).

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

[0224] Here, compatibility support related parameters include fuel delivery temperature, selected fueling table, etc., physical characteristic parameters include maximum fuel delivery pressure, maximum fuel delivery temperature, minimum fuel delivery temperature, maximum fuel delivery speed, 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, atmospheric temperature, etc., and acceptance related parameters may include parameters such as accepted. The above parameters may be set with information for one of preset levels or set values ​​and information for a UCDC level that is different or the same from each other.

[0225] In this way, Mobility can provide the dispenser with parameters listed in table form, including FCEV parameters compatible with UCDC levels negotiated during the fuel supply protocol negotiation phase.

[0226] As described above, once a communication link is established and a communication and fuel supply protocol is selected in the protocol negotiation phase, the mobility and the dispenser can exchange various parameters to confirm whether they can execute a compatible fuel supply procedure. Here, information required to execute a safe and efficient fuel supply procedure can include compatibility parameters, physical characteristics, fuel supply targets, monitoring parameters, etc.

[0227] Compatibility parameters may include, for example, pressure rating, fuel delivery temperature, etc.; physical properties may include, for example, maximum CHSS pressure, maximum flow rate, etc.; fuel delivery targets may include target SOC, target CHSS pressure, etc.; and monitoring parameters may include current CHSS temperature, ambient temperature, etc.

[0228] If compatible parameters cannot be found and fuel delivery cannot proceed, the FCEV can return to the communication protocol negotiation step to attempt negotiation with another protocol or stop fuel delivery to the dispenser. Furthermore, when returning to the communication protocol negotiation step due to a failure in the fuel delivery parameter exchange step, the FCEV can be configured to propose to the dispenser a set of supported protocols excluding the protocol that failed in the fuel delivery parameter exchange step.

[0229] Once the fueling protocol is negotiated according to the aforementioned use case (UC-4), the vehicle and dispenser can negotiate specific parameters for the fueling protocol, communicate static or dynamic conditions, and exchange detailed fueling parameters to determine fueling targets. If the fueling parameter negotiation fails due to incompatibility, the vehicle can return to UC-3 to select another fueling protocol or return to UC-1 to select another communication protocol, and if these are not successful, the current communication can be terminated.

[0230] According to the above configuration, some fueling protocols can be performed on a non-communication basis. Some fueling protocols may require unidirectional IrDA. Some fueling protocols may require bidirectional communication. Some fueling protocols may require both bidirectional communication and unidirectional IrDA.

[0231] A certain fueling protocol may require a certain UCDC level or a higher UCDC level to be executed. At least one fueling protocol may be proposed based on the type of hydrogen electric vehicle and the type of dispenser. The proposed fueling protocols may have different priorities. Taking into account the priority of the proposed fueling protocols, the communication protocol between the hydrogen electric vehicle and the dispenser and the fueling protocol may ultimately be determined based on whether the communication protocol required by the fueling protocol is supported by the hydrogen electric vehicle and / or the dispenser.

[0232] In another embodiment of the present invention, either the mobility or the dispenser may first transmit fuel supply parameters to the other party, and the other party may maintain the received fuel supply parameters that it accepts and change the received parameters that it does not accept, and respond with a message containing the newly reconfigured fuel supply parameters.

[0233] 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 then perform an exchange / negotiation process for sub-parameters of the parameters for which an agreement has been reached.

[0234] In another embodiment of the present invention, each message containing fueling parameters may be configured such that if no response message is received within a pre-defined message processing time, no agreement is considered to have been reached.

[0235] Table 15 below illustrates the contents of a message containing mobility-side fueling parameters according to one embodiment of the present invention. [Table 15]

[0236] Table 16 below illustrates the contents of a message containing dispenser-side fueling parameters according to one embodiment of the present invention. [Table 16]

[0237] In the fuel supply parameter negotiation step (S405), the mobility and the dispenser can generate and transmit a message having ranges / values ​​for supportable parameters to the other party. The parameters can include physical property-related parameters (simply referred to as "physical parameters"), monitoring parameters, safety policy-related parameters, and acceptance-related parameters.

[0238] Here, the physical parameters include receptacle type, pressure class, CHSS category, CHSS type, CHSS capacity, maximum allowable CHSS pressure, maximum allowable CHSS temperature, maximum allowable speed, etc., the monitoring parameters include current CHSS pressure, current CHSS temperature, etc., the safety policy-related parameters include emergency policy, safety enforcement level, etc., and the acceptance-related parameters include information indicating whether accepted or not, such as parameters called yes (true), no (false), or pending.

[0239] Parameters associated with fueling parameter negotiation may include physical property-related parameters (simply "physical parameters"), monitoring parameters, fueling target-related parameters, safety policy-related parameters, and acceptance-related parameters.

[0240] Here, the physical parameters include fuel delivery temperature, maximum fuel delivery pressure, maximum fuel delivery temperature, minimum fuel delivery temperature, maximum fuel delivery speed, etc., the monitoring parameters include current fuel delivery temperature, ambient temperature, etc., the fuel delivery target-related parameters include selected fueling table, target SOC, target final CHSS pressure, target final CHSS temperature, target APR, expected fuel delivery time, etc., and the acceptance-related parameters may include parameters such as accepted. The above parameters may be set with information for one of preset levels or set values ​​and information for a UCDC level that is different or the same from each other.

[0241] In this way, the FCEV can provide the dispenser with parameters listed in table form, including FCEV parameters compatible with UCDC levels negotiated during the fuel supply protocol negotiation phase.

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

[0243] Furthermore, if the dispenser finds that the fuel supply parameters of the vehicle are incompatible after receiving the fuel supply parameter negotiation request message, the dispenser can respond by transmitting a fuel supply parameter negotiation response message to the FCEV with the "result" field set to "failed" to indicate incompatibility with the corresponding vehicle, the FCEV. The result indicates the value or information contained in the result code field, and the failure is a failure at a specific time, and can be expressed as an expression indicating incompatibility, such as "fail_incompat."

[0244] In addition, if the FCEV finds that the fuel supply parameters of the dispenser are incompatible after receiving the fuel supply parameter negotiation request message, the FCEV can notify the dispenser of the incompatibility by transmitting an error notification request message to the dispenser along with a "reason" set for each predefined error code.

[0245] Meanwhile, before fuel delivery begins, the vehicle and dispenser can verify that all safety conditions have been met through the use case for safety check-in (UC6). Although this step is optional, it is preferable to define a dedicated safety check-in procedure in the fuel delivery protocol to ensure the desired safety level in a precise and explicit manner.

[0246] FIG. 14 is a conceptual diagram illustrating a table of parameters transmitted from the mobility side to the dispenser side in a fuel supply parameter negotiation / exchange process according to one embodiment of the present invention. FIG. 15 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.

[0247] Referring to both Figures 13 and 15, a method for exchanging fuel supply parameters over communication for hydrogen filling according to one embodiment of the present invention is a method for exchanging parameters over communication for hydrogen filling performed by a communication control device of a hydrogen-fueled mobility 100, and includes the steps of transmitting first parameters including at least one of at least one first hydrogen filling method compatibility and at least one first physical characteristics supported by the mobility 100 to a communication entity associated with the dispenser 200 (S1310); and receiving a response message from the communication entity associated with the dispenser 200 including second parameters including at least one of at least one second hydrogen filling method compatibility supported by the dispenser 200, at least one second physical characteristics, and a filling goal (S1370).

[0248] The communication entity associated with the dispenser 200 may be the electronic control unit 210 of the dispenser 200, or a separate communication device mounted on the dispenser 200, or an electronic control unit or a separate communication device within the filling station system 220 may communicate with the vehicle / mobility 100 on behalf of the dispenser 200. In this case, the first parameters may further include a first monitoring parameter supported by the mobility 100. The second parameters may further include a second monitoring parameter supported by the dispenser 200.

[0249] In a communication parameter exchange method for hydrogen filling according to an embodiment of the present invention, the parameter exchange process may be terminated based on a confirmation message (OK message) included in a response message. The parameter exchange process may be terminated when the mobility 100 and the dispenser 200 accept all exchanged parameters, or when either party does not accept the exchanged parameters. If not accepted, the protocol negotiation process may be revisited or the filling session may be terminated according to the process described below.

[0250] In a communication parameter exchange method for hydrogen filling according to one embodiment of the present invention, at least one first hydrogen filling method compatibility may include at least one of the pressure class of the mobility 100 and the filling tank category (CHSS Category).

[0251] In a communication parameter exchange method for hydrogen filling according to one embodiment of the present invention, the at least one first physical characteristic may include at least one of a maximum allowed CHSS pressure, a maximum allowed CHSS temperature, a maximum allowed flow rate, and a CHSS volume.

[0252] In the method for exchanging parameters over communication for hydrogen filling according to an embodiment of the present invention, the first parameters may further include parameters related to the acceptance of the mobility 100 .

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

[0254] In a method for exchanging parameters over communication for hydrogen filling according to an embodiment of the present invention, the at least one second filling method compatibility may include at least one of a fueling delivery temperature and a selected fueling table of the dispenser 200. The selected fueling table may include a sequence table of a filling protocol selected during the protocol negotiation process and may be included in the OK message of S1330.

[0255] In a method for exchanging parameters over communication for hydrogen filling according to one embodiment of the present invention, the at least one second physical characteristic may include at least one of a maximum fuel delivery pressure, a maximum fuel delivery temperature, a minimum fuel delivery temperature, and a maximum fuel delivery flow rate.

[0256] In a method for exchanging parameters over communication for hydrogen filling according to one embodiment of the present invention, the filling target may include at least one of a target filling rate (SoC), a target final filling tank pressure (Target Final CHSS Pressure), a target final filling tank temperature (Target Final CHSS Temperature), a target average fueling rate (Target APR), and an expected fueling duration.

[0257] In the method for exchanging parameters over communication for hydrogen filling according to an embodiment of the present invention, the second parameters may further include parameters related to the acceptance of the dispenser 200 .

[0258] In a method for exchanging parameters over communication for hydrogen filling according to one embodiment of the present invention, the second monitoring parameters may include at least one of a current fuel delivery temperature and an ambient temperature.

[0259] The mobility 100 may provide the first parameters compatible with the UCDC level negotiated in the protocol negotiation process in the form of a table in step S1310.

[0260] The dispenser 200 may provide second parameters compatible with the UCDC level negotiated during the protocol negotiation process in the form of a table in step S1330. At this time, the second parameters may be provided together with a message indicating acceptance of the first parameters provided in step S1310.

[0261] If the mobility 100 or the dispenser 200 does not accept the exchanged parameters, the mobility 100 can perform the protocol negotiation process again, or if the mobility 100 or the dispenser 200 does not accept the exchanged parameters, the mobility 100 can terminate the filling session.

[0262] In a protocol negotiation process that is performed again due to a parameter exchange process that failed because the mobility 100 or the dispenser 200 did not accept the exchanged parameters, the mobility 100 can propose a set of supported protocols other than the protocols provided in the failed parameter exchange process.

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

[0264] Table 18 illustrates the contents of a message containing dispenser-side fueling parameters according to another embodiment of the present invention. [Table 18]

[0265] The communication method according to an embodiment of the present invention may further include a step of renegotiating at least one of the communication protocol and the fuel supply parameters if the fuel supply parameters are incompatible between the mobility and the dispenser as a result of the fuel supply parameter negotiation (S405). In this case, the renegotiation step in the communication method according to an embodiment of the present invention may involve re-performing steps S403, S404, and S405. For example, the renegotiation may be performed by returning to step S403 and starting from step S403, and then steps S404 and S405 may be sequentially performed again. In yet another embodiment, the renegotiation may be performed by returning to step S404 and starting from step S404, and then step S405 may be sequentially performed again.

[0266] In the renegotiating step of the communication method according to another embodiment of the present invention, steps S403, S404, and S405 may be simplified or some steps may be omitted, or steps S403 and S404 may be combined to negotiate both the communication protocol and the fuel supply protocol.

[0267] In the communication method according to another embodiment of the present invention, the renegotiation step may be performed based on the remaining communication protocols and fuel supply protocols excluding the communication protocol or fuel supply protocol selected in step S403 and step S404. For example, the communication protocol and the fuel supply protocol may be negotiated together based on a protocol list including both the communication protocol and the fuel supply protocol based on whether the communication protocol and the fuel supply protocol are mutually supported according to the compatibility and / or interoperability information acquired in step S401.

[0268] The communication method according to an embodiment of the present invention may further include, if the fuel supply parameters are incompatible between the mobility and the dispenser as a result of the fuel supply parameter negotiation (S405), determining a third communication protocol and a third fuel supply protocol based on a predetermined policy; 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.

[0269] For example, if communication between the mobility and the dispenser is not possible due to a change in the communication environment, the dispenser can fall back to No Communication and supply hydrogen using a hydrogen fuel supply protocol based on No Communication.

[0270] The communication method according to an embodiment of the present invention may perform a step of terminating communication between the dispenser and the mobility (S409) if the fuel supply parameters are incompatible between the mobility and the dispenser as a result of the fuel supply parameter negotiation.

[0271] Referring again to FIG. 4, a safety check-in step (S406) that can be employed in a hydrogen filling communication two-way process according to one embodiment of the present invention is illustrated.

[0272] In a safety check-in step (S406), the mobility containing the mobility and the dispenser can verify that all necessary safety conditions have been met before actual fuel dispensing begins.

[0273] Once the fuel supply parameters are exchanged and the mobility and dispenser are deemed compatible, the mobility and dispenser can perform a safety status check to verify whether fuel supply is safe. Depending on the fuel supply protocol, the safety check may be performed implicitly within the protocol, and the safety check step (S406) may be omitted depending on the implementation.

[0274] Also, in a safety check-in step (S406), the mobility and / or dispenser can check whether the nozzle-receptacle is secured, check for leaks, and check the last-minute status.

[0275] Also, if the fuel supply protocol supports safe check-in after receiving a fuel supply parameter negotiation response message from the dispenser, the mobility can start the safe check-in step (S406) by transmitting a safe check-in request message to the dispenser within the message sequence setting time.

[0276] The mobility and the dispenser can exchange messages for coupler check. The mobility can transmit a message containing information indicating the result of its coupler check (e.g., mobility: OK) to the dispenser, and the dispenser can transmit a message containing information indicating the result of its coupler check (e.g., DP: OK) to the mobility.

[0277] Additionally, the mobility and dispenser can exchange messages related to gas leak checks. While exchanging leak check-related messages, the dispenser can transmit information indicating that it is conducting a leak check (ongoing) to the mobility. The mobility can then transmit information indicating that it is waiting for the dispenser's leak check results (waiting) to the dispenser. Once the leak check is complete, the dispenser can transmit a message to the mobility requesting the measured tank volume along with information indicating that the leak check has been completed (Done).

[0278] In addition, the dispenser can transmit a message to the mobility for an immobilized status check, and the mobility can transmit a message to the dispenser informing it that it is ready for a status check.

[0279] In this way, when the mobility reports parameters regarding the mobility's current status or immobilization status to the dispenser, the dispenser can report parameters regarding the coupler lock status, leak check status, predicted mobility tank capacity, etc. to the mobility.

[0280] Once the safety check-in step (S406) described above has been passed, fuel supply can begin. During fuel supply, the mobility and dispenser can exchange information and monitor various status parameters to ensure that fuel supply is carried out safely and efficiently. If necessary, the mobility or dispenser can send a control message to control the fuel supply step (S406) or request the other party to take action to address safety-related conditions. The parameters and commands exchanged may vary depending on the actual fuel supply protocol.

[0281] Step S407 is a monitoring and control step that can be employed in the hydrogen filling communication two-way process according to one embodiment of the present invention.

[0282] In the monitoring and control step (S407), the mobility including the mobility and / or the dispenser can monitor the fuel supply status and control the fuel supply as needed. Once all safety checks are confirmed, the mobility and dispenser can start fuel supply according to the selected fuel supply protocol using the given parameters. While supplying fuel, the mobility and dispenser exchange various measurement data to understand the fuel supply status and can operate to detect the occurrence of important accidents as quickly and safely as possible.

[0283] In addition, the mobility can transmit specific commands to the dispenser to control fuel supply steps (S407), such as starting and ending fuel supply. At this time, the mobility can use UDP with DTLS for communication to support black channel communication. Black channel communication can refer to communication that applies the black channel principle, in which secure communication must be guaranteed despite the output characteristics of a communication channel that has unsecured attributes or attributes not related to the application.

[0284] To explain this more specifically using the monitoring and control step (S407) as an example, a mobility including a mobility can transmit a message to a dispenser to start fueling control, and in response, the dispenser can transmit a message including confirmation information (e.g., OK) to the mobility.

[0285] In addition, the mobility can transmit a message to the dispenser containing information about its fuel supply loop (e.g., x, y, z), and the dispenser can provide the mobility with a message containing information about its fuel supply loop (e.g., a, b, c) that corresponds to the mobility's fuel supply loop.

[0286] In addition, the mobility may transmit a fueling control request message to the dispenser including information to slow down fuel supply or reduce the amount of fuel supplied (S1660), and the dispenser may transmit a response message to the mobility including information indicating a decrease in the fueling status (e.g., slowing) (S1670).

[0287] In addition, the mobility may transmit a fuel supply control request message to the dispenser requesting the suspension (stop) of fuel supply (S1680), and the dispenser may transmit a fuel supply status response message to the mobility including information on whether fuel supply is being suspended or has been suspended (stopping / stopped) (S1690).

[0288] In this manner, in the monitoring and control step (S407), the mobility and the dispenser can continuously or periodically exchange parameters related to the fuel supply state. The mobility transmits the current tank temperature, current tank pressure, etc. to the dispenser, and the dispenser can provide the mobility with parameters related to fuel supply start, stop, ramping up, ramping down, current injection pressure, future fuel supply plan, etc.

[0289] A control-related request message transmitted from the mobility to the dispenser may include information and parameters for starting, pausing, resuming, terminating fuel supply, etc. Additionally, a reporting-related message transmitted from the mobility to the dispenser may include information and parameters for the current tank temperature, the current tank pressure, etc.

[0290] Messages related to reporting transmitted from the dispenser to the mobility may include information and parameters regarding status information, current atmospheric temperature, current pressure ramp rate (PRR [Mbar / min]), delivery fuel flow rate (deliver fuel flow rate [g / sec]), current fuel delivery temperature, pre-cooling temperature, current fuel delivery pressure, whether full tank filling is in use, whether cooling dispenser is in use, whether fallback is in use, reason for refueling suspension, amount of hydrogen currently supplied, etc.

[0291] The message related to the target parameter update transmitted from the dispenser to the mobility may include information and parameters regarding the target final tank pressure, target final tank temperature, target fuel supply APR, target SOC, current SOC, estimated remaining duration, etc.

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

[0293] After hydrogen fuel supply is completed through the monitoring and control step (S407) described above, before the session is ended and the nozzle is separated from the mobility, the mobility and dispenser including the mobility can check whether the quantity and each dispenser meets all safety conditions through a safety check-out use case. While this safety check-out step is optional, it is preferable to define a dedicated safety check step (S407) in the fuel supply protocol to ensure the desired safety level in an accurate and explicit manner.

[0294] A safety checkout step (S408) that can be employed in a two-way communication process for hydrogen filling according to an embodiment of the present invention can be performed as follows. Through the safety checkout step (S408), a mobility including a mobility and a dispenser can confirm whether all necessary safety conditions have been met before separating the nozzle of the dispenser from the outlet. In other words, the mobility and the dispenser can confirm whether it is absolutely safe for a user or worker to separate the nozzle from the mobility after fuel supply is completed.

[0295] For example, after the mobility receives a fuel supply loop response message from the dispenser with the "result" set to "OK," the "status" set to "finished," or the prefix "stopped," if the hydrogen filling protocol supports safety checkout, the mobility can initiate safety checkout and transmit a safety checkout request message to the dispenser within the message sequence setting time to perform the safety checkout step (S408).

[0296] The mobility and dispenser can repeatedly report their status to each other until all safety checks are confirmed. If the hydrogen filling communication two-way process does not require such safety confirmation at the end, the use case for safety checkout can be omitted.

[0297] To explain the aforementioned safety checkout step (S408) in more detail using an example, the mobility can transmit a message to the dispenser containing information on the coupler check result (e.g., OK), and the dispenser can transmit a message to the mobility containing information indicating that the coupler check is in progress (e.g., Ongoing).

[0298] In addition, the mobility can transmit a message including coupler inspection result information (e.g., OK) back to the dispenser, and the dispenser can transmit a message including coupler inspection completion information (e.g., Done) to the mobility.

[0299] Once the above-mentioned coupler inspection completion information is confirmed to be completed normally, the nozzle of the dispenser can be separated from the receptacle of the mobility by the user or operator.

[0300] In the safety checkout step (S408), the report message transmitted from the dispenser to the mobility may include information and parameters regarding the coupler unlock status. The coupler unlock status information may include information regarding locked, unlocked, icing, problem, etc.

[0301] The termination use case (UC9) can be performed when fuel supply is completed and the nozzle is safely separated according to the hydrogen filling protocol described above, or when a non-safety critical issue occurs during another use case.

[0302] The termination step (S409) that can be employed in the hydrogen filling communication two-way process according to an embodiment of the present invention can be performed as follows. The termination step (S409) is the final step of fuel supply, and the mobility including the mobility and the dispenser exchange information on the fuel supply results regarding fuel supply performance and method, and / or information on the reason for unexpected interruptions in fuel supply, to complete all steps of hydrogen filling (S409). The termination use case can also be configured to handle work related to issues that are not critical to safety if they occur.

[0303] 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 prefixed with "stopped," the mobility can transmit a termination request message to the dispenser and perform the termination step (S409).

[0304] To explain the termination step (S409) in more detail using an example, a mobility including the mobility can transmit a message to the dispenser inquiring about how much fuel has been supplied. In response to the mobility's inquiry message, the dispenser can transmit a response message to the mobility including information (e.g., X-gram) about the amount of hydrogen supplied.

[0305] In addition, the mobility may transmit a confirmation request message for the completion of fuel supply to the dispenser, and the dispenser may transmit a goodbye message to the mobility as a response message to the confirmation request message.

[0306] Meanwhile, after fuel supply is completed and safety inspection is confirmed, the mobility and the dispenser may exchange at least some bookkeeping information for the hydrogen filling session in the finalization step (S409). The mobility and the dispenser may exchange summary information for the hydrogen filling session before completing the finalization step (S409).

[0307] Book-keeping information can include all information related to hydrogen fueling that is recorded in the mobility or dispenser according to established rules and policies across all fueling sessions and prior to completing the termination step (S409) of Use Case 9 (UC9).

[0308] The ledger information or summary information may include information on how much fuel has been supplied, what kind of report has been created, etc. In addition, the report message transmitted from the mobility to the dispenser may include information or parameters on the current tank temperature and current tank pressure, and the report message transmitted from the dispenser to the mobility may include information on the final SOC, the final average fueling rate (APR), the final measured tank pressure, the actual fuel supply time, the amount of hydrogen actually supplied, etc.

[0309] Once all necessary information for a fueling session has been saved, the fueling session may be completely terminated.

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

[0311] Meanwhile, the error handling use case (UC10) is a functional block for safely handling a situation where a non-fatal error occurs by terminating the fuel supply procedure or abruptly terminating communication, similar to a normal termination. The error handling step (S410) that can be employed in the hydrogen filling communication two-way process according to one embodiment of the present invention can be performed as follows.

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

[0313] The error handling step (S410) can be applied when a non-safety fatal error occurs and further communication is impossible. That is, the mobility and dispenser including the mobility can handle the occurrence of a non-safety fatal error at any time during fuel supply in the error handling step (S410). In other words, the mobility and dispenser can immediately stop fuel supply, pause the previously running use case, and then move to the end use case (UC9).

[0314] If the mobility detects a non-safety fatal error event, it can stop the current fuel supply session or communication session by notifying the dispenser of the reason for termination via a terminate request (TerminateReq) message. The dispenser can terminate the current communication session in response to the terminate request message. If additional communication is not possible, the current session can be terminated without additional notification.

[0315] Additionally, 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 'action' set to 'stop' and 'reason' set to an appropriate reason or reason code. The appropriate reason or reason code can include reasons such as the message being corrupted.

[0316] The above-mentioned termination request message may be sent in error situations such as communication errors, system errors, and qualitative errors that are not fatal unless recovery is not possible.

[0317] That is, for successful fuel delivery, communication must exhibit the behavior expected by the protocol, and fuel delivery behavior must be within the acceptable range of the fuel delivery protocol. However, in reality, various abnormal events can occur. Some of these errors are minor and can be easily handled, but some other errors cannot be recovered and prevent fuel delivery from proceeding. Therefore, the error handling step (S410) defines error conditions that are not critical to safety and provides example error conditions and possible responses.

[0318] Examples of communication errors include communication interruptions, inability to recognize received data due to encoding or syntax errors, or received data that is within an unacceptable range. System errors include cases where a dispenser or mobility independently detects a significant system error. Qualitative errors include cases where the quality of communication performance does not meet the required standards, or where the quality of data completeness or accuracy does not meet the required standards.

[0319] The hydrogen filling communication two-way process of this embodiment can perform the following specific error processing steps (S410) (1) to (4) for the above-mentioned error conditions. (1) If a non-safety-critical error occurs and further communication is not possible, the mobility and dispenser may immediately stop fuel delivery but take safety measures to stop communication and terminate the session. (2) If a non-safety-critical error occurs and fuel delivery is interrupted and fuel delivery is not completed, the fuel delivery protocol may define a fallback mechanism, for example, by defining a non-communication fuel delivery method.

[0320] (3) If a non-safety critical error is detected by the mobility and the communication channel is still active, the mobility may send a termination request message to the dispenser with the 'action' set to 'stop' and the 'reason' set to an appropriate reason code. (4) If a non-safety critical error is detected by the dispenser and the communication channel is still active, the dispenser may first immediately stop fuel delivery and transmit a termination request message to the mobility with “Action” set to “Abort” and “Reason” set to an appropriate reason or reason code.

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

[0322] On the other hand, a safety-critical problem may occur during fuel supply in the hydrogen filling system, requiring an urgent response. An emergency handling step (S411) that can be adopted in the hydrogen filling communication two-way process according to an embodiment of the present invention can be performed as follows.

[0323] The emergency handling step (S411) may include a response process for preventing safety-critical accidents by defining safety-critical conditions that require emergency response during fuel filling.

[0324] For safe fuel supply, communications must demonstrate the behavior expected by the protocol, and fuel supply operations must be within the safe range of the fuel supply protocol. However, problems may occur during fuel supply, causing the fuel supply system (or hydrogen filling system) to reach a critical state that must be avoided at all costs. Therefore, the emergency handling step (S411) defines emergency conditions that are important to safety and possible responses to those emergency conditions, and provides important cases to consider.

[0325] The fueling protocol may define emergency conditions associated with the protocol, provide sensing criteria and performance requirements, and prescribe response steps (S411) to ensure harmful situations are not entered into.

[0326] Specifically, when the mobility detects a high pressure state exceeding a preset reference value during the hydrogen filling step (S411), the mobility can transmit a first emergency stop request message including information requesting the stop of fuel supply due to the high pressure (e.g., Emg:Stop(high pressure)) to the dispenser. The dispenser can transmit a response message including information indicating that the emergency stop of fuel supply is being processed in response to the first emergency stop request message (e.g., Emg:Stopping).

[0327] In addition, after receiving the response message, the mobility may again transmit a first emergency stop request message to the dispenser immediately or after a preset time has elapsed. The dispenser may transmit a response message to the mobility including information indicating that fuel supply has been urgently stopped in response to the first emergency stop request message (e.g., Emg:Stopped).

[0328] Meanwhile, if the dispenser detects hydrogen fuel leakage during the hydrogen filling step (S411), the dispenser may transmit a second emergency stop request message including information indicating that the dispenser is processing the suspension of fuel supply due to the leakage (e.g., Emg:Stopping(leaking)) to the mobility. The mobility may transmit a response message including information indicating that the second emergency stop request message has been confirmed (e.g., Emg:Confirmed) to the dispenser.

[0329] In addition, the dispenser may transmit a third emergency stop notification message including information indicating that the fuel supply stop due to leakage has been processed (e.g., Emg:Stopped(leaking)) to the mobility. The mobility may transmit a response message including information indicating that the third emergency stop notification message has been confirmed (e.g., Emg:Confirmed) to the dispenser.

[0330] According to the above-mentioned configuration, when a serious situation affecting safety is detected in a mobility or dispenser including a mobility device, necessary measures can be taken immediately to prevent a disaster from occurring, and if possible, an emergency notification message containing information about the situation can be sent to the other party to cut off communication.

[0331] When an emergency notification message is received, the mobility or dispenser can immediately respond with the action indicated in the emergency notification message and terminate the communication without undue delay. The emergency notification message includes a header and a message body linked to the header, and the header includes information indicating that it is an emergency notification. The message may include values, information, or parameters for the class, type, and action for the emergency notification.

[0332] The emergency notification message described above can be transmitted as a TLS or DTLS message depending on the technology used for communication.

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

[0334] Although not shown in the drawings, a processor and memory may be electronically connected to each component in the embodiments of FIGS. 1 to 15, and the operation of each component may be controlled or managed by the processor.

[0335] At least some of the steps of the filling communication method for filling an electric vehicle according to one embodiment of the present invention may be performed by the computing system 3000 of FIG.

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

[0337] The processor 3100 may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which the methods according to the embodiments of the present invention are performed.

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

[0339] The computing system 3000 may also include a communication interface 3300 for effecting communications over a wireless network.

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

[0341] In addition, the components included in the computing system 3000 are connected by a bus 3700 to perform communication.

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

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

[0344] The communication control device of hydrogen-fueled mobility 100 according to one embodiment of the present invention may include a memory 3200 that stores at least one instruction, and a processor 3100 that executes at least one instruction. The processor 3100, according to the at least one instruction, may negotiate a communication protocol with a dispenser that supplies hydrogen to the mobility, may negotiate a fuel supply protocol with the dispenser for receiving a supply of hydrogen fuel from the dispenser, and may negotiate fuel supply parameters based on the fuel supply protocol with the dispenser.

[0345] When negotiating a communication protocol, the processor 3100 can transmit a message including information on a first communication protocol applicable to the mobility to the dispenser, and can receive a message from the dispenser including information on a second communication protocol selected from common communication protocols applicable between the mobility and the dispenser.

[0346] The information regarding the first communication protocol may include at least one of an index of the first communication protocol, a name of the first communication protocol, a version of the first communication protocol, and a preference for the first communication protocol, and the message including the information regarding the second communication protocol may further include information regarding whether the communication protocol negotiation was successful.

[0347] When negotiating a fuel supply protocol, the processor 3100 can transmit a message including information on a first fuel supply protocol applicable to the mobility to the dispenser based on the result of the communication protocol negotiation, and can receive a message from the dispenser including information on a second fuel supply protocol selected from among fuel supply protocols commonly applicable between the mobility and the dispenser.

[0348] The information regarding the first fuel supply protocol may include at least one of an index of the first fuel supply protocol, a name of the first fuel supply protocol, a version of the first fuel supply protocol, a sub-protocol of the first fuel supply protocol, and a preference for the first fuel supply protocol, and the message including information regarding the second fuel supply protocol may further include information regarding whether the fuel supply protocol negotiation was successful.

[0349] When negotiating fuel supply parameters, the processor 3100 can transmit a message to the dispenser including information on the mobility side fuel supply parameters required by the second fuel supply protocol selected as a result of the fuel supply protocol negotiation, and can receive a message from the dispenser including dispenser side compatibility information for the mobility side fuel supply parameters.

[0350] When negotiating fuel supply parameters, the processor 3100 can receive a message from the dispenser including 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, and can transmit a message to the dispenser including mobility-side compatibility information for the dispenser-side fuel supply parameters.

[0351] The processor 3100 can, by at least one instruction, renegotiate at least one of the communication protocol and the fuel supply parameters if the fuel supply parameters become incompatible between the mobility and the dispenser as a result of the fuel supply parameter negotiation.

[0352] The processor 3100 may, by at least one instruction, determine a third communication protocol and a third fuel supply protocol based on a predetermined policy when the fuel supply parameter negotiation results in incompatible fuel supply parameters between the mobility and the dispenser, and hydrogen may be supplied based on the third communication protocol and the third fuel supply protocol.

[0353] The processor 3100 can, by at least one instruction, terminate communication between the dispenser and the mobility if the fuel supply parameter negotiation results in incompatible fuel supply parameters between the mobility and the dispenser.

[0354] The processor 3100 can, by at least one instruction, perform a discovery and pairing process with the dispenser using a first communication technology, and if the result of the communication protocol negotiation relates to a second communication technology, can negotiate a fuel delivery protocol and fuel delivery parameters using the second communication technology.

[0355] When the processor 3100 performs the discovery and pairing process, information regarding interoperability or compatibility between the mobility and the dispenser may be shared.

[0356] A communication device for hydrogen fuel supply arranged in a dispenser that supplies hydrogen fuel to hydrogen-fueled mobility according to one embodiment of the present invention includes a memory 3200 that stores at least one or more instructions; and a processor 3100 that executes at least one instruction, wherein the processor 3100 can negotiate a communication protocol with the mobility, negotiate a fuel supply protocol with the mobility for fueling hydrogen to the mobility, and negotiate fuel supply parameters based on the fuel supply protocol with the mobility, according to the at least one or more instructions.

[0357] While most of the above-described embodiments have been described with a focus on a method in which a hydrogen-fueled mobility device first transmits its communication protocol and parameters to a dispenser, the present invention is not limited to a specific embodiment and may be configured to first transmit its communication protocol and parameters to a hydrogen-fueled mobility device. In this case, it is clear that the embodiments have essentially the same features, except that the sender becomes the receiver and the receiver becomes the sender.

[0358] The operations of the methods according to the embodiments of the present invention may be embodied as a computer-readable program or code stored on a computer-readable recording medium. The computer-readable recording medium includes all types of storage devices that store information readable by a computer system. The computer-readable recording medium may also be distributed across network-connected computer systems, so that the computer-readable program or code may be stored and executed in a distributed manner.

[0359] Additionally, the computer-readable recording medium may include a hardware device specially configured to store and execute program instructions, such as a ROM, RAM, flash memory, etc. The program instructions may include not only machine language code, such as that produced by a compiler, but also high-level language code that can be executed by a computer using an interpreter, etc.

[0360] Although some aspects of the invention have been described in the context of an apparatus, they may also be described in terms of a corresponding method, where a block or apparatus corresponds to a method step or feature of a method step. Similarly, aspects described in the context of a method may also be described in terms of a corresponding block or item or feature of a corresponding apparatus. Some or all of the method steps may be performed by (or using) a hardware device, such as, for example, a microprocessor, a programmable computer, or electronic circuitry. In some embodiments, at least one or more of the most significant method steps may be performed by such a device.

[0361] In some 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 some embodiments, a field programmable gate array may operate in conjunction with a microprocessor to perform one of the methods described herein. In general, it is preferred that the methods be performed by some hardware device.

[0362] Although the present invention has been described above with reference to preferred embodiments, it will be understood by those skilled in the art that various modifications and variations of the present invention may be made without departing from the spirit and scope of the present invention as set forth in the following claims. [Explanation of symbols]

[0363] 100 Hydrogen Electric Vehicles 110, 210 Electronic control device 120 Vehicle Systems 130 Vehicle Tank 150 receptacles 160 First Sensor 200 Dispensers 220 Filling Station System 230 Hydrogen Tank 240 Station Box 250 nozzles 260 Second Sensor 900 UCDC Level 0 910 UCDC Level 1 920 UCDC Level 2 930 UCDC Level 3 3000 Computing System 3100 processor 3200 memory 3300 Communication Interface 3400 storage device 3500 Input Interface 3600 Output Interface 3700 Bus< / false> < / true> < / ok> < / true> < / ok> < / pending> < / pending>

Claims

1. 1. A communication method for hydrogen fueling performed by hydrogen fueled mobility, comprising: negotiating a communication protocol with a dispenser that supplies hydrogen to said hydrogen-fueled mobility; negotiating a fueling protocol with the dispenser for receiving a supply of hydrogen fuel from the dispenser; and negotiating fueling parameters based on the fueling protocol with the dispenser; A communication method for hydrogen fuel supply, comprising:

2. The step of negotiating a communication protocol comprises: transmitting a message to the dispenser, the message including information for a first communication protocol applicable to the hydrogen-fueled mobility; and receiving a message from the dispenser, the message including information about a second communication protocol selected from common communication protocols commonly applicable between the hydrogen fuel mobility device and the dispenser; 2. The method of claim 1, further comprising:

3. The information for the first communication protocol is the first communication protocol includes at least one of an index of the first communication protocol, a name of the first communication protocol, a version of the first communication protocol, and a preference for the first communication protocol; The message including information for the second communication protocol is 3. The communication method for hydrogen fuel supply according to claim 2, further comprising information indicating whether the communication protocol negotiation was successful or not.

4. negotiating the fueling protocol includes: transmitting a message including information about a first fuel supply protocol applicable to the hydrogen-fueled mobility to the dispenser based on a result of the communication protocol negotiation; and receiving, from the dispenser, a message including information on a second fuel supply protocol selected from fuel supply protocols commonly applicable between the hydrogen fuel mobility and the dispenser; 2. The method of claim 1, further comprising:

5. The information for the first fueling protocol is at least one of an index of the first fueling protocol, a name of the first fueling protocol, a version of the first fueling protocol, a sub-protocol of the first fueling protocol, and a preference for the first fueling protocol; The message including information for the second fueling protocol comprises:

5. The communication method for hydrogen fueling according to claim 4, further comprising information indicating whether or not the fueling protocol negotiation was successful.

6. negotiating the fueling parameters includes: transmitting a message to the dispenser containing information regarding fueling parameters of the hydrogen-fueled mobility side required by a second fueling protocol selected as a result of the fueling protocol negotiation; and receiving a message from the dispenser containing compatibility information of the dispenser with fueling parameters of the hydrogen-fueled mobility; 2. The method of claim 1, further comprising:

7. negotiating the fueling parameters includes: receiving a message from the dispenser containing information regarding dispenser-side fueling parameters required by a second fueling protocol selected as a result of fueling protocol negotiation; and transmitting a message to the dispenser containing compatibility information of the hydrogen fuel mobility system with the dispenser's fuel supply parameters; 2. The method of claim 1, further comprising:

8. renegotiating at least one of the communication protocol and the fuel supply parameters when the fuel supply parameters are incompatible between the hydrogen fuel mobility device and the dispenser as a result of the fuel supply parameter negotiation; 10. The method of claim 1, further comprising:

9. determining a third communication protocol and a third fuel supply protocol based on a predetermined policy when the fuel supply parameter negotiation results in the fuel supply parameters being incompatible between the mobility and the dispenser; and fueling hydrogen based on the third communication protocol and the third fueling protocol; 10. The method of claim 1, further comprising:

10. If the fuel supply parameters are incompatible between the hydrogen-fueled mobility and the dispenser as a result of the fuel supply parameter negotiation, terminating communication between the dispenser and the hydrogen-fueled mobility; 10. The method of claim 1, further comprising:

11. performing a discovery and pairing process with the dispenser using a first communication technology; further comprising 2. The communication method for hydrogen fuel supply of claim 1, wherein if a result of the communication protocol negotiation relates to a second communication technology, the steps of negotiating the fuel supply protocol and negotiating the fuel supply parameters are performed using the second communication technology.

12. In the step of performing the discovery and pairing process, 12. The communication method for hydrogen fuel supply according to claim 11, wherein information regarding interoperability or compatibility between the hydrogen fuel mobility and the dispenser is shared.

13. A communication device for hydrogen fuel supply arranged in a hydrogen fuel mobility, comprising: a memory for storing at least one instruction; and a processor for executing the at least one instruction; The processor, in response to the at least one instruction, negotiating a communication protocol with a dispenser that supplies hydrogen to said hydrogen-fueled mobility; negotiating a fueling protocol with the dispenser for receiving a supply of hydrogen fuel from the dispenser; A communication device that negotiates fueling parameters based on the fueling protocol with the dispenser.

14. The processor, when negotiating the communication protocol, transmitting a message including information for a first communication protocol applicable to the hydrogen-fueled mobility to the dispenser; receiving a message from the dispenser, the message including information about a second communication protocol selected from common communication protocols commonly applicable between the hydrogen-fueled mobility device and the dispenser; The information for the first communication protocol is the first communication protocol includes at least one of an index of the first communication protocol, a name of the first communication protocol, a version of the first communication protocol, and a preference for the first communication protocol; The message including information for the second communication protocol is 14. The communication device according to claim 13, further comprising information indicating whether the communication protocol negotiation was successful or not.

15. The processor, when negotiating the fueling protocol, transmitting a message including information about a first fuel supply protocol applicable to the hydrogen-fueled mobility to the dispenser based on a result of the communication protocol negotiation; receiving, from the dispenser, a message including information on a second fuel supply protocol selected from fuel supply protocols commonly applicable between the hydrogen fuel mobility and the dispenser; The information for the first fueling protocol is at least one of an index of the first fueling protocol, a name of the first fueling protocol, a version of the first fueling protocol, a sub-protocol of the first fueling protocol, and a preference for the first fueling protocol; The message including information for the second fueling protocol comprises:

14. The communication device of claim 13, further comprising information indicating whether or not the fueling protocol negotiation resulted in success.

16. The processor, when negotiating the fueling parameters, transmitting a message to the dispenser containing information regarding fueling parameters of the hydrogen-fueled mobility side required by a second fueling protocol selected as a result of the fueling protocol negotiation; receiving a message from the dispenser containing compatibility information of the dispenser with fueling parameters of the hydrogen-fueled mobility; receiving a message from the dispenser containing information regarding dispenser-side fueling parameters required by a second fueling protocol selected as a result of the fueling protocol negotiation; The communication device of claim 13 , further comprising: a communication device configured to transmit a message to the dispenser, the message including compatibility information of the hydrogen-fueled mobility system with the dispenser's fuel supply parameters.

17. The processor, in response to the at least one instruction, 14. The communication device of claim 13, wherein if the fuel supply parameters become incompatible between the hydrogen fuel mobility device and the dispenser as a result of fuel supply parameter negotiation, at least one of the communication protocol and the fuel supply parameters is renegotiated.

18. The processor, in response to the at least one instruction, determining a third communication protocol and a third fuel supply protocol based on a predetermined policy when the fuel supply parameter negotiation results in the fuel supply parameters being incompatible between the hydrogen fuel mobility device and the dispenser; 14. The communication device of claim 13, wherein hydrogen is fueled based on the third communication protocol and the third fueling protocol.

19. The processor, in response to the at least one instruction, 14. The communication device of claim 13, wherein if the fuel supply parameter negotiation results in the fuel supply parameters being incompatible between the hydrogen-fueled mobility and the dispenser, the communication device terminates communication between the dispenser and the hydrogen-fueled mobility.

20. The processor, in response to the at least one instruction, performing a discovery and pairing process with the dispenser using a first communication technology; if a result of the communication protocol negotiation relates to a second communication technology, negotiating the fueling protocol and the fueling parameters using the second communication technology; When performing the discovery and pairing process, The communication device of claim 13 , wherein information regarding interoperability or compatibility between the hydrogen fuel mobility device and the dispenser is shared.

21. 1. A communication method for hydrogen fueling performed by a dispenser that supplies hydrogen fuel to hydrogen-fueled mobility, comprising: negotiating a communication protocol with said hydrogen fueled mobility; negotiating a fueling protocol with the hydrogen-fueled mobility for fueling the mobility with hydrogen; and negotiating fueling parameters based on the fueling protocol with the hydrogen-fueled mobility; A communication method for hydrogen fuel supply, comprising:

22. A communication device for hydrogen fuel supply, disposed in a dispenser that supplies hydrogen fuel to hydrogen-fueled mobility, comprising: a memory for storing at least one instruction; and a processor for executing the at least one instruction; The processor, in response to the at least one instruction, negotiating a communication protocol with said hydrogen-fueled mobility vehicle; negotiating a fueling protocol with the hydrogen-fueled mobility vehicle for fueling the hydrogen-fueled mobility vehicle with hydrogen; A communication device configured to negotiate fueling parameters based on the fueling protocol with the hydrogen-fueled mobility system.

Images