Communication protocol negotiation method for hydrogen filling and device using same

Abstract

The present invention provides a hydrogen filling process that can improve the safety, compatibility, efficiency, and reliability of hydrogen filling in a communication protocol for hydrogen filling of hydrogen-fueled mobility, a communication protocol negotiation method for the hydrogen filling process, and an apparatus that utilizes the method. [Solution] A method according to one embodiment of the present invention includes transmitting a first message to a communication entity associated with a dispenser, the first message including a list of at least one first filling protocol supported by mobility and a first communication protocol required to execute the at least one first filling protocol, and receiving a response message from the communication entity associated with the dispenser, the response message including a second filling protocol selected from the at least one first filling protocol.

Description

[Technical Field]

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

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

[0003] A hydrogen vehicle or 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 not only emit pure water (H2O) during the electricity generation process, but also have the ability to remove ultrafine dust particles from the atmosphere while in operation, making them garnering attention as an environmentally friendly form of future mobility. Given that hydrogen, the fuel, is infinitely available on Earth and the energy production process is environmentally friendly, hydrogen electric vehicles are attracting attention as a technology with potential for use across industries.

[0004] 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 the vehicle.

[0005] Most hydrogen electric vehicles generate electrical energy through an electrochemical reaction between the hydrogen and oxygen, which is transferred 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.

[0006] Meanwhile, the concept of a hydrogen fueled car, which is not 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.

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

[0008] 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 therefore do not adequately reflect recent advances in information and communications technology (ICT).As a result, conventional hydrogen refueling technologies for hydrogen electric vehicles are inefficient, slow, and not suitable for large-volume hydrogen refueling.

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

[0010] In order to solve the above-mentioned problems, an object of the present invention is to provide a hydrogen filling process that overcomes the limitations and weaknesses of existing one-way communication in communication protocols for hydrogen fueling of hydrogen fueled mobility and can improve the safety, compatibility, efficiency, and reliability of hydrogen filling, as well as a communication protocol negotiation method for the hydrogen filling process and an apparatus that uses the method.

[0011] Another object of the present invention is to provide a hydrogen filling communication two-way process, a communication protocol negotiation process that considers two-way / one-way communication, and an apparatus that uses the same, which can provide rules and principles for fallback to a hydrogen filling protocol and a communication protocol therefor, so that vehicles, including fuel cell electric vehicles (FCEVs), and dispensers that supply hydrogen fuel to these vehicles can select a protocol that maximizes interoperability rather than choosing their own most preferred method.

[0012] It is yet another object of the present invention to provide a two-way hydrogen filling communication process that can be controlled to determine an advanced communication medium for a vehicle and a dispenser to effectively achieve a hydrogen fueling goal, a communication protocol negotiation process that takes into account two-way / one-way communication, and an apparatus that utilizes the same. [Means for solving the problem]

[0013] To achieve the above object, one embodiment of the present invention provides a hydrogen filling communication protocol negotiation method performed by a communication control device of hydrogen-fueled mobility, and includes the steps of transmitting a first message to a communication entity associated with a dispenser, the first message including a list of at least one first fueling protocol supported by the hydrogen-fueled mobility 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, the response message including a second fueling protocol selected from the at least one first fueling protocol.

[0014] The first message may include priority information based on the hydrogen-fueled mobility preference.

[0015] At this time, the response message may include the second filling protocol selected from the at least one first filling protocol based on the priority information based on the preference.

[0016] The response message may include the second filling protocol selected from a common protocol commonly included in the at least one first filling protocol and protocols supported by the dispenser.

[0017] At this time, the response message may include the second filling protocol selected from the at least one first filling protocol by the dispenser control device.

[0018] The response message may include a second communication protocol required by the dispenser controller to execute the second fill protocol.

[0019] The response message may include a second communication protocol selected from at least one communication protocol required by the dispenser controller to execute the second fill protocol.

[0020] The response message may include a second communication protocol determined by a device type that is fallbacked based on interoperability and backward compatibility between the hydrogen fuel mobility device and the dispenser from among multiple communication protocols required by the dispenser's control device to execute the second filling protocol.

[0021] In a hydrogen filling protocol negotiation method according to one embodiment of the present invention, a negotiation request message for communication protocol negotiation between the hydrogen fuel mobility and the dispenser may be transmitted by the communication control device of the hydrogen fuel mobility to a communication entity associated with the dispenser.

[0022] The hydrogen filling protocol negotiation method according to one embodiment of the present invention may further include a step of performing protocol negotiation by the communication control device of the hydrogen fueled mobility transmitting a confirmation message in response to the response message.

[0023] At this time, in the transmitting the first message, the first message may be transmitted as the negotiation request message to the communication entity associated with the dispenser.

[0024] A communication control device for hydrogen-fueled mobility according to an embodiment of the present invention may include a memory for storing at least one instruction and a processor for executing the at least one instruction, wherein the processor transmits a first message to a communication entity associated with a dispenser, the first message including a list of at least one first fueling protocol supported by the hydrogen-fueled mobility and a first communication protocol required to execute the at least one first fueling protocol, in accordance with the at least one instruction, and receives a response message from the communication entity associated with the dispenser, the response message including a second fueling protocol selected from the at least one first fueling protocol.

[0025] In a communication control device for hydrogen-fueled mobility according to an embodiment of the present invention, the first message may include priority information based on a preference for the hydrogen-fueled mobility.

[0026] In one embodiment of the communication control device for hydrogen-fueled mobility according to the present invention, the response message may include a second charging protocol selected from the at least one first charging protocol based on the priority information based on the preference.

[0027] In one embodiment of the present invention, in a communication control device for hydrogen-fueled mobility, the response message may include the second filling protocol selected from among a common protocol commonly included in the at least one first filling protocol and a protocol supported by the dispenser.

[0028] In one embodiment of the present invention, in a communication control device for hydrogen-fueled mobility, the response message may include the second filling protocol selected by the dispenser control device from among the at least one first filling protocol.

[0029] In a communication control device for hydrogen-fueled mobility according to one embodiment of the present invention, the response message may include the second communication protocol required by the dispenser control device to execute the second filling protocol.

[0030] In one embodiment of the present invention, in a communication control device for hydrogen-fueled mobility, the response message may include a second communication protocol selected from at least one communication protocol required by the dispenser control device to execute the second filling protocol.

[0031] In one embodiment of the present invention, in a communication control device for hydrogen-fueled mobility, the response message may include a second communication protocol determined by the device type that is fallbacked based on interoperability and backward compatibility between the mobility and the dispenser among multiple communication protocols required by the dispenser control device to execute the second filling protocol.

[0032] In a communication control device for hydrogen-fueled mobility according to one embodiment of the present invention, the processor may transmit a negotiation request message for negotiating a communication protocol between the hydrogen-fueled mobility and the dispenser to a communication entity associated with the dispenser.

[0033] Protocol negotiation may occur by the processor transmitting an acknowledgement message in response to the response message.

[0034] The processor may transmit the first message as the negotiation request message to a communications entity associated with the dispenser. [Effects of the Invention]

[0035] According to one embodiment of the present invention, a hydrogen filling communication protocol negotiation method 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 communication protocols for hydrogen fueling of hydrogen fueled mobility including fuel cell electric vehicles (FCEVs) and hydrogen fueled engines, thereby improving the safety, compatibility, efficiency, and reliability of hydrogen filling.

[0036] Furthermore, according to one embodiment of the present invention, a hydrogen filling communication protocol negotiation method and communication protocol fallback rules can be provided in which the vehicle and dispenser take into account priorities based on the vehicle's preferences, but also maximize interoperability between the vehicle and dispenser and consider backward compatibility to select a protocol for hydrogen filling and a communication protocol required to execute the hydrogen filling protocol based on the use case.

[0037] Furthermore, according to one embodiment of the present invention, it is possible to provide rules and procedures necessary for negotiating a communication protocol so that a vehicle and a dispenser can cooperate to effectively determine an advanced communication medium to effectively achieve a hydrogen fueling goal. [Brief explanation of the drawings]

[0038] [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 yet another communication protocol negotiation procedure in a two-way hydrogen filling communication process according to another 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 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 15] 1 is a flowchart illustrating a safety check-in procedure that may be employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 16] 1 is a flow chart illustrating a monitoring and control procedure that may be employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 17] 1 is a flowchart illustrating a safety check-out procedure that can be employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 18] 1 is a flowchart illustrating a termination procedure that may be employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 19] 10 is a flow chart illustrating an error handling procedure that may be employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 20] 1 is a flow chart illustrating an emergency handling procedure that may be employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. [Figure 21]10 is a schematic block diagram of an apparatus (simply "hydrogen filling apparatus") utilizing a hydrogen filling communication two-way process according to yet another embodiment of the present invention. [Figure 22] FIG. 22 is a block diagram for explaining a software module that can be employed in the hydrogen filling device of FIG. 21. DETAILED DESCRIPTION OF THE INVENTION

[0039] The present invention can be modified in various ways and can have various embodiments, and specific embodiments will be illustrated in the drawings and described in detail in the detailed description. However, this is not intended to limit the present invention to the specific embodiments, and it should be understood that the present invention includes all modifications, equivalents, and alternatives that fall within the spirit and technical scope of the present invention. In the description of each drawing, similar reference numerals are used to refer to similar components.

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

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

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

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

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

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

[0046] 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 electric vehicle that uses hydrogen as fuel. In the following embodiments, a hydrogen fueling protocol and / or a communication protocol for hydrogen fueling is disclosed with reference to a hydrogen fuel cell vehicle, and in other embodiments of the present invention, the hydrogen fueling protocol and / or the communication protocol for hydrogen fueling disclosed in the following embodiments may also be applied to an ICE-based hydrogen electric vehicle.

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

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

[0049] 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 simply used interchangeably with fueling in terms 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 fuel supply protocol can be referred to as a filling protocol, a fuel supply session can be referred to as a filling session, and a fuel supply method can be referred to as a hydrogen filling method or a fueling method.

[0050] The pressure ramp rate (PRR) is expressed in MPa / min and indicates the rate at which the pressure of the CHSS increases.

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

[0052] Pre-cooling basically refers to the process of pre-cooling hydrogen at a hydrogen filling station before filling it.

[0053] The dispenser is a component that delivers pre-cooled hydrogen to the CHSS. The dispenser is installed at the hydrogen filling station and can perform hydrogen filling operations between the hydrogen storage tank at the hydrogen filling station and the vehicle's CHSS. Nozzle refers to a device connected to the dispenser that mates with a receptacle in 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.

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

[0055] Furthermore, the hydrogen filling communication two-way process of the present invention can be partially applied not only to hydrogen fueled mobility but also to hydrogen-powered buildings or facilities.

[0056] In the following description, the hydrogen fuel may include at least one of gaseous hydrogen and liquid hydrogen, and basically refers to compressed hydrogen, but is not limited thereto. 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.

[0057] Meanwhile, even technologies that were publicly known before the filing date of the present invention may be included as part of the configuration of the present invention, if necessary, and will be described in this specification to the extent that the gist of the present invention is not obscured. However, in describing the configuration of the present invention, detailed descriptions of technologies that were 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 technologies will be omitted. Furthermore, the gist of the present invention is not intended to claim rights to such publicly known technologies, and the content of publicly known technologies may be included as part of the present invention to the extent that it does not deviate from the gist of the present invention.

[0058] 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 connection structure between the FCEV and the dispenser in the hydrogen filling system of Figure 1. 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.

[0059] 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 also be equipped with an electronic control device 110 for hydrogen filling, a vehicle system 120, a vehicle tank 130, and a receptacle 150.

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

[0061] The vehicle system 120 is connected to the first electronic control unit 110 and may be configured to control the filling and discharging of hydrogen 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 components that perform such control operations, or may be configured to be connected to such components. Such a vehicle system 120 may be referred to as a vehicle safety system.

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

[0063] 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 mechanism, 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 reduction 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.

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

[0065] 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). Dispenser 200 can supply hydrogen supplied from hydrogen tank 230 to a vehicle through nozzle 250 firmly connected to vehicle receptacle 150 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.

[0066] 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, and processes the signals and data to control 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.

[0067] 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 instead of two-way communication. This may also be useful when using a combination of different communication methods, such as using WiFi when performing actual charging after pairing via NFC.

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

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

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

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

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

[0073] 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 vehicle receptacle.

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

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

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

[0077] Existing technologies include communication and non-communication methods for transmitting information from the vehicle 100 to the dispenser 200. When communication is used, the existing technology only transmits the temperature and pressure values ​​of the vehicle tank 130 of the vehicle 100 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 critical temperature and pressure. In addition, the hydrogen filling protocol for safe and rapid filling is managed by the dispenser 200, and it only has minimal safety management equipment that automatically releases hydrogen through a pressure relief device (PRD) without active safety management of the vehicle tank 130.

[0078] Meanwhile, to address the phenomenon of the temperature of hydrogen gas rising during hydrogen filling (see FIG. 3), a 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 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 or connected to the piping that transports hydrogen at the hydrogen filling station.

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

[0080] 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 or the dispenser 200 may include at least a portion of a communication protocol according to an SAE standard, an ISO standard, or the like.

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

[0082] If the dispenser 200 does not actively control status values ​​related to hydrogen filling, the conventional table-based method is highly inefficient and has difficulty responding flexibly to changes in surrounding conditions because it does not utilize the temperature of pre-cooled hydrogen fuel provided at 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.

[0083] 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 on the surface of the vehicle tank can be negligible compared to the internal temperature rise until filling is complete due to the vehicle tank's low heat transfer characteristics.

[0084] 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 may suddenly increase due to the heat of compression in Phase IV (P4), which is the stage of compressing and storing hydrogen fuel in the vehicle tank.

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

[0086] FIG. 4 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 (hereinafter referred to as the "hydrogen filling framework").

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

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

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

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

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

[0092] Meanwhile, a hydrogen-fueled vehicle (hereinafter simply referred to as "vehicle") and a dispenser implementing the above-mentioned use case 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.

[0093] 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 controller 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.

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

[0095] The discovery and pairing procedure or pairing processor may include a pre-condition 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.

[0096] 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 performed. In other words, even if the pairing process is successfully completed, approval for fuel or fuel supply may not be granted.

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

[0098] 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. Furthermore, while the physical shape of the hydrogen filling hardware can be specified in advance, proximity does not include pairing methods that risk pairing a vehicle and a dispenser that are not physically connected, such as relatively long-range wireless communication technologies such as Bluetooth. Infrared communication can be referred to as infrared data association (IrDA) communication and can include bidirectional infrared (bi-IrDA) communication.

[0099] 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 Open Systems Interconnection reference model (OSI).

[0100] 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 each of 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.

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

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

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

[0104] In addition, the hydrogen filling communication stack may include at least one fourth protocol 540 selected from transport layer security (TLS), datagram transmission layer security (DTLS), 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.

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

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

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

[0108] 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) charging, alternate current (AC) charging, wireless power transfer (WPT), automatic connection device pantograph (ACDP), etc.

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

[0110] On the other hand, use case UC1 of the discovery and pairing procedure allows a device to identify the communication partner (vehicle or dispenser communication module) responsible for controlling the physically connected receptacle or nozzle. UC-1 also defines how to identify incompatibilities and can define fail-safe mechanisms.

[0111] In this use case UC1, the vehicle and dispenser can search for a common communication technology to execute the fuel supply protocol. The discovery mechanism provided by the basic data link and physical layers allows the vehicle and dispenser to find each other and begin communication. An additional pairing procedure is required to establish a communication channel with the device connected to the fuel supply hose assembly. If the communication channel does not guarantee correct pairing, for example, in the case of wireless communication, a separate pairing channel that transmits pairing information may be required. If pairing is implicitly guaranteed, for example, a communication channel integrated with the hose assembly may be sufficient.

[0112] FIG. 6 is an exemplary diagram illustrating a pairing process of a discovery and pairing procedure that can be employed in a two-way hydrogen filling communication process according to an embodiment of the present invention. Referring to FIG. 6, in the pairing process, when pairing at UCDC Level 2 and UCDC Level 3, the vehicle and the dispenser can exchange pairing IDs and confirm each other's pairing ID.

[0113] For example, a vehicle broadcasts a message (PAIR_ID_ANNOUNCE) including its pairing ID (PAIR_ID), i.e., a vehicle ID (vehicle_id) (S710). The dispenser transmits a message (PAIR_ID_ACK) to the vehicle, acknowledging that it has received the vehicle ID (S720). The vehicle transmits a message (PAIR_ID_CONFIRM) to the dispenser, acknowledging that it has successfully received the ACK message indicating that the dispenser has received the vehicle ID (S730).

[0114] Next, the dispenser broadcasts a message (PAIR_ID_ANNOUNCE) containing its pairing ID, i.e., dispenser ID (dispenser_id) (S740). The vehicle transmits a message (PAIR_ID_ACK) to the dispenser, acknowledging that it has received the dispenser ID from the dispenser (S750). The dispenser transmits 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 (S760).

[0115] 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 regarding pairing ID exchange. 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.

[0116] On the other hand, if a particular UCDC level supports secure communication, at least one of the vehicle and the dispenser can 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 can include exchanging encryption keys so that the vehicle and the dispenser can secure communication during fueling.

[0117] Incidentally, 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, such as IEC 62443 Security Level 3. IEC 62443 Security Level 3 may be a security level for actors with appropriate resources and motivation.

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

[0119] 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. Type 2 may refer to devices that support advanced communication (AC). Type 2 devices can fall back to Type 0 devices. Type 3 can refer 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.

[0120] Advanced communication may refer to communication using a medium and specific protocol, such as wireless local area network (WLAN), Bluetooth (BT), near field communication (NFC), Wi-Fi (Wi-Fi), ultra-wideband (UWB), radio frequency identification (RFID), 4G, or 5G. Advanced communication may also include two-way IrDA, serial communication, vehicular Ethernet (ETH), 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).

[0121] Additionally, advanced communication may include hybrid forms 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.

[0122] 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. Well-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.

[0123] 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. In other words, as shown in FIG. 7, when a Type 1 device supporting Specification #1 according 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).

[0124] Also, when a Type 2 device supporting Specification #2 conforming to a predetermined standard encounters a Type 0 device or a Type 1 device, the Type 2 device can fall back to a Type 0 device (S620).

[0125] If 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). If a Type 3 device meets a Type 1 device, the Type 3 device can fall back to the Type 1 device (S640). Also, if a Type 3 device meets a Type 2 device, the Type 3 device can fall back to the Type 2 device (S650).

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

[0127] To support the interoperability, the hydrogen filling device can also 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 it supports WLAN, one of the advanced communications.

[0128] In Scenario 1, the dispenser can be equipped with an access point (AP), which is a wireless router. The dispenser can support FCEV gas 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.

[0129] 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 begin between the FCEV and the dispenser.

[0130] 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 receptacle is connected to the nozzle attached to the dispenser cable, IrDA communication can begin between the FCEV and the dispenser.

[0131] 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 without necessarily selecting the communication method that they most prefer.

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

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

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

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

[0136] Also, 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. And 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 (No comm).

[0137] The two-way communication device described above can be configured to support a fuel dispensing 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.

[0138] 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 pairing identities (IDs), but the requirements for exchanging such identities 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.

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

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

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

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

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

[0144] FIG. 10 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 one embodiment of the present invention. 10, an FCEV can transmit a message requesting a list of authorization methods to a dispenser (S1010). The dispenser can transmit a response message to the FCEV in response to the FCEV's request for the authorization method list (S1020). The response message can include authorization method list information related to external authorization procedures such as RFID (radio frequency identification), credit cards, and debit cards, as well as self-authorization procedures.

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

[0146] Next, the FCEV performs authentication using the authentication method selected previously in response to the dispenser's response, and may transmit a message requesting confirmation of the authentication performance (Done?) 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. Once the authentication is completed, the dispenser may transmit an authentication completion (Done(success)) message to the FCEV (S1090).

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

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

[0149] Furthermore, the vehicle and dispenser can successfully complete the 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. This allows the communication channel between the vehicle and dispenser to be encrypted and integrity protected. The dispenser can authenticate the vehicle, and optionally, the vehicle can authenticate the dispenser.

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

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

[0152] During the TLS handshake, the vehicle 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 vehicle.

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

[0154] FIG. 11 is a flow chart 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.

[0155] Referring to FIG. 11, in the communication protocol negotiation procedure, the FCEV can transmit a negotiation request message to the dispenser to start protocol negotiation in order to identify the protocol version of the fuel supply protocol that the FCEV and dispenser will use for the two-way hydrogen filling communication process (S1110).

[0156] Next, the dispenser may provide the FCEV with a response message including a protocol list for communication protocols supported by the dispenser in response to the negotiation request message (S1130). The response message may include information on communication protocols supported by SAE standards, ISO standards, etc. SAE standards include the SAE J2601 standard, etc., and ISO standards include the ISO 19885-3 standard, the ISO 19885-4 standard, etc.

[0157] Next, the FCEV can select a specific protocol, for example, the ISO-v1-ucdc-3 protocol, from a protocol list of communication protocols supported by the dispenser and transmit a protocol selection message containing information about the selected communication protocol to the dispenser (S1150).

[0158] Next, the dispenser can check the protocol included in the protocol selection message of the FCEV and transmit a negotiation OK message to the FCEV (S1170).

[0159] The above-described communication protocol negotiation procedure is a procedure for identifying the communication protocol to be followed during a hydrogen fueling session after the vehicle and dispenser discover and pair with each other through a compatible communication channel. In particular, in this embodiment, the dispenser can take the initiative in exchanging communication protocols and parameters with the vehicle.

[0160] 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 hydrogen filling communication two-way process.

[0161] In practice, various combinations of FCEVs and dispensers at each site may occur depending on the hydrogen filling communication-related standard, communication mode, fuel supply method, communication level, and other parameters. Here, hydrogen filling communication-related standards may include the SAE J2601 series, ISO 19885-3, ISO 19885-4, etc. Communication modes may include no communication (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, fueling tables, etc.

[0162] Meanwhile, the vehicle 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. In addition, in an environment where various combinations can occur, if an incompatibility is found in the parameters exchanged during the hydrogen filling negotiation procedures UC3 to UC5 between the vehicle and the dispenser, they can return to the communication protocol negotiation procedure and perform the negotiation procedure again.

[0163] FIG. 12 is a flowchart illustrating yet another communication protocol negotiation procedure in a two-way hydrogen filling communication process according to another embodiment of the present invention. Referring to FIG. 12, during the communication protocol negotiation procedure, the FCEV selects a protocol list (<list of protocols> ) to the dispenser (S1210). The prioritized communication protocol may include protocols having priorities as exemplified in Table 2.

[0164] The dispenser will run a specific protocol (<selected protocol> ) to the FCEV (S1230). The specific protocol may be a common protocol selected by the dispenser, supported by both the dispenser and the vehicle, and the protocol with the highest priority that the vehicle prefers most, such as the ISO 19885-3-2023-UCDC-3 protocol (see Table 2).

[0165] The common protocol allows the vehicle and dispenser to reach agreement on a communication protocol to use for fueling communication.

[0166] Meanwhile, a vehicle can assign priorities to the communication protocols it supports. The vehicle can include an FCEV. The vehicle can provide the dispenser with prioritized communication protocols. Examples of prioritized communication protocols are shown in Table 2 below. [Table 2]

[0167] Once the communication protocol is selected in the communication protocol negotiation use case UC3 described above, the vehicle and dispenser can activate their respective communication protocol implementations and begin fuel supply protocol negotiation. Fuel supply protocol negotiation is a procedure in which the vehicle and dispenser search for and agree on a fuel supply protocol to use for the fuel supply session. At this stage, the vehicle and dispenser can select the communication protocol that the vehicle most prefers from the protocols they both support.

[0168] 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, and includes the steps of transmitting a first message including a list of at least one first fueling protocol supported by the mobility 100 and at least one first communication protocol required to execute the first fueling protocol to a communication entity associated with the dispenser 200 (S1210); and receiving a response message including a second filling protocol selected from the at least one first fueling protocol from the communication entity associated with the dispenser 200 (S1230).

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

[0170] The first message may include priority information based on the mobility 100 preferences as shown in Table 2. At this time, the response message may include a second filling protocol selected from at least one of the first protocols based on priority information based on preference. The mobility 100 side or the dispenser 200 side may select the second filling 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.

[0171] The response message may include at least one of the first filling protocol and a second filling protocol selected from among common protocols commonly included in protocols supported by the dispenser 200 . At this time, referring to the embodiment of FIG. 12, the response message may include a second filling protocol selected by the control device of the dispenser 200 from at least one of the first filling protocols.

[0172] The response message may include a second communication protocol required by the controller of the dispenser 200 to execute a second filling protocol.

[0173] The response message may include a second communication protocol selected from at least one or more communication protocols required by the controller of the dispenser 200 to execute the second fill protocol.

[0174] 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 communication protocols required by the control device of the dispenser 200 to execute the second filling protocol.

[0175] Referring to both Figures 11 and 12, in a hydrogen filling protocol negotiation method according to one embodiment of the present invention, an initial negotiation request message for communication protocol negotiation between the mobility 100 and the dispenser 200 can be transmitted by the communication control device of the mobility 100 to a communication entity associated with the dispenser 200. At this time, the hydrogen filling protocol negotiation method according to one embodiment of the present invention may further include a step in which protocol negotiation is performed by the communication control device of the mobility 100 transmitting a confirmation message in response to the response message. At this time, in the step of transmitting a first message (S1210), the first message may be transmitted to a communication entity associated with the dispenser 200 as a negotiation request message.

[0176] FIG. 13 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.

[0177] The fuel supply parameter exchange / negotiation procedure may include a step in which the vehicle and the dispenser exchange detailed parameters necessary to execute a fueling protocol. The vehicle may include an FCEV.

[0178] Referring to FIG. 13, in the fuel supply parameter exchange / negotiation procedure, the FCEV selects the first parameter (<FCEV’s parameter> ) can be provided to the dispenser (S1310).

[0179] The first parameters may include parameters for supporting fueling method compatibility, parameters for physical characteristics, monitoring parameters, acceptance-related parameters, and the like.

[0180] 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 include information indicating whether accepted or not, for example, a parameter indicating yes (true) or no (false). The above parameters can be set with information for one of pre-specified levels or setting values ​​and information for a main UCDC level that is different or the same as each other.

[0181] On the other hand, the dispenser can support a second parameter (<DIS’s parameters> )(briefly<DIS’s params> ) and an OK message indicating that the first parameter has been received can be transmitted to the FCEV (S1330). At this time, if the parameter exchange process of FIG. 13 and the protocol negotiation process of FIG. 12 are linked, the OK message of step S1330 can be used to transmit information regarding the selected protocol among the first parameters ( <ok>A response message including the information about the vehicle speed (see reference number 1330) can be transmitted to the FCEV (S1330).

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

[0183] 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 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 main UCDC level that is different or the same from each other.

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

[0185] On the other hand, the dispenser can support a second parameter (<DIS’s parameters> )(briefly<DIS’s params> ) and information about the selected protocol among the first parameters (see FIG. 13). <ok>A response message including the address (see reference) can be transmitted to the FCEV.

[0186] Furthermore, the second parameters related to the fueling protocol can be shown in another form as shown in Table 3. [Table 3]

[0187] As shown in Table 3, the dispenser can provide the FCEV with parameter information in table format, which includes reference information such as names arbitrarily assigned to the fuel supply methods and fuel supply protocols that it can support, revision time (year), version information, information on whether subprotocols are available, and priority.

[0188] Additionally, the dispenser, like the vehicle, can proactively communicate its own communication protocols and parameters with the vehicle and can be configured to prioritize and provide to the vehicle the communication protocols that the dispenser supports.

[0189] In Table 3, PRHYDE (Protocol for heavy-duty HYDrogEn refueling) is proposed from one of the European projects that has been developing a heavy-duty vehicle refueling protocol, RTR-HFP is proposed from a type of protocol concept that improves refueling efficiency based on real-time communication, and ANN-MPC is proposed from a type of protocol concept that collects and analyzes data from the refueling site and applies predictions to actual refueling conditions.

[0190] In addition, examples of information on selection protocols related to fueling protocols that can be transmitted from a dispenser to an FCEV are shown in Table 4 and FIG. [Table 4]

[0191] As shown in Table 4, the dispenser can select the fuel supply protocol corresponding to index 2 and transmit a response message including a result code OK to the FCEV. [Table 5]

[0192] As shown in Table 5, if the dispenser fails to find a compatible protocol in the list of fuel supply protocols that the FCEV can support and received from the FCEV, the dispenser can transmit a response message to the FCEV containing information indicating that there is no common protocol (e.g., FAIL_NO_COMMON_PROTOCOL) in the result code field.

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

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

[0195] If compatible parameters cannot be found and fuel supply cannot proceed, the FCEV can return to the communication protocol negotiation step and attempt negotiation of another protocol, or can stop supplying fuel to the dispenser. Furthermore, when returning to the communication protocol negotiation step due to a failure in the fuel supply 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 supply parameter exchange step.

[0196] Once the fuel supply protocol is negotiated according to the aforementioned use case UC-4, the vehicle and dispenser can negotiate specific parameters for the fuel supply protocol, inform of static or dynamic conditions, and exchange detailed fuel supply parameters to determine the fuel supply target. If the fuel supply parameter negotiation fails due to incompatibility, the vehicle and dispenser can return to UC-3 to select another fuel supply protocol or return to UC-1 to select another communication protocol, and if this is not successful, the current communication can be terminated.

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

[0198] A certain fueling protocol may require a certain UCDC level or a higher UCDC level to be performed. 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 be proposed with 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.

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

[0200] As shown in FIG. 14, the vehicle and dispenser can determine the detailed parameters necessary to execute the selected fueling protocol based on the desired safety level and performance. In other words, once the selection of the fueling protocol is completed in the fueling protocol negotiation, the vehicle and dispenser exchange the detailed parameters that must be exchanged before executing the corresponding fueling protocol. That is, the FCEV sends the parameter values ​​of the fueling parameters to the dispenser (S1410), and when the dispenser responds with its own parameter values ​​(S1430), the fueling parameter negotiation begins. During the parameter exchange, the vehicle and dispenser can determine whether they can execute the fueling protocol.

[0201] During fuel supply parameter negotiation, the FCEV and dispenser can exchange protocol-specific parameters necessary for proper and efficient hydrogen fueling while maintaining a safe hydrogen filling system one or more times until a protocol-specific agreement is reached. The receiver that receives the parameters can transmit a response message to the sender indicating that the parameters have been accepted. Parameter acceptance can be displayed as "yes" (true) in the accepted field; if not accepted, it can be displayed as "pending" or "false."

[0202] After receiving the fuel supply protocol negotiation response message from the dispenser, the FCEV can transmit the fuel supply protocol negotiation response message within a preset message processing time to provide the fuel supply parameters to be set to the dispenser. Examples of FCEV parameters are shown in Table 6 below. [Table 6]

[0203] The dispenser parameters are shown in Table 7 below. [Table 7]

[0204] As described above, in the fueling parameter negotiation procedure, the FCEV can transmit a message having ranges / values ​​for the third parameters (fueling parameters) that it can support to the dispenser (S1410).

[0205] The third parameters may include physical characteristic-related parameters (simply referred to as "physical parameters"), monitoring parameters, safety policy-related parameters, acceptance-related parameters, etc.

[0206] 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.; monitoring parameters include current CHSS pressure, current CHSS temperature, etc.; safety policy-related parameters include emergency policy, safety enforcement level, etc.; and acceptance-related parameters include information indicating whether accepted or not, such as yes (true), no (false), or pending.

[0207] Meanwhile, the dispenser may transmit a message including ranges and values ​​for the fourth parameters (fueling parameters) that the dispenser can support to the FCEV (S1430).

[0208] The fourth parameters associated with fueling parameter negotiation may include physical characteristic-related parameters (simply, "physical parameters"), monitoring parameters, fueling target-related parameters, safety policy-related parameters, and acceptance-related parameters.

[0209] 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 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 main UCDC level that is different or the same from each other.

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

[0211] On the other hand, after receiving the 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.

[0212] 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" 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 can be expressed as a failure at a specific time, such as "fail_incompat," indicating incompatibility.

[0213] In addition, if the FCEV finds that the dispenser's fuel supply parameters 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 in each predefined error code.

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

[0215] FIG. 15 is a flow chart illustrating a safety check-in procedure that may be employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. A safety check-in procedure allows the vehicle containing the FCEV and the dispenser to verify that all necessary safety conditions have been met before fueling actually begins.

[0216] Once the fuel delivery parameters have been exchanged and the vehicle and dispenser are deemed compatible, the vehicle and dispenser can perform a safety check to verify that fuel delivery is safe. Depending on the fuel delivery protocol, the safety check may be performed implicitly within the protocol, and the safety check step may be omitted depending on the implementation.

[0217] Also, during the safety check-in procedure, the vehicle and / or dispenser can check that the nozzle-receptacle is secured, check for leaks, and check the last-minute status. Also, after receiving a fuel supply parameter negotiation response message from the dispenser, if the fuel supply protocol supports safe check-in, the vehicle can begin the safe check-in procedure by transmitting a safe check-in request message to the dispenser within the message sequence setting time.

[0218] Specifically, as shown in Figure 15, the vehicle and the dispenser can exchange messages for coupler check (S1510, S1520). The vehicle can transmit a message including information indicating the result of its own coupler check (e.g., FCEV: OK) to the dispenser, and the dispenser can transmit a message including information indicating the result of its own coupler check (e.g., DP: OK) to the vehicle.

[0219] In addition, the vehicle and dispenser can exchange messages related to gas leak checks (S1530, S1570). During the exchange of messages related to leak checks, the dispenser can transmit information indicating that it is conducting a leak check (ongoing) to the vehicle (S1540). The vehicle can then transmit information indicating that it is waiting for the dispenser's leak check results (waiting) to the dispenser (S1560). Once the leak check is complete, the dispenser can transmit a message requesting the measured tank volume along with information indicating that the leak check has been completed (Done) to the vehicle (S1570).

[0220] The dispenser may also transmit a message to the vehicle for an immobilized status check (S1580), and the vehicle may transmit a message to the dispenser informing it that it is ready for a status check (S1590).

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

[0222] Once the safety check-in procedure described above is passed, fuel delivery can begin. During fuel delivery, the vehicle and dispenser can exchange information to monitor various status parameters to ensure that fuel delivery is performed safely and efficiently. If necessary, the vehicle or dispenser can send control messages to control the fuel delivery procedure or request action from the other party to address safety-related conditions. The parameters and commands exchanged can vary depending on the actual fuel delivery protocol.

[0223] FIG. 16 is a flow chart illustrating a monitoring and control procedure that may be employed in a hydrogen filling communication two-way process according to one embodiment of the present invention.

[0224] In the monitoring and control procedure, the vehicle, including the FCEV, and / or the dispenser can monitor the fuel supply status and control the fuel supply as necessary. Once all safety checks are confirmed, the vehicle and dispenser can begin fuel supply according to the selected fuel supply protocol using given parameters. During fuel supply, the vehicle and dispenser exchange various measurement data to understand the fuel supply status and can operate to detect the occurrence of critical accidents as quickly and safely as possible.

[0225] In addition, the vehicle can transmit specific commands to the dispenser to control fuel supply procedures, such as starting and stopping fuel supply. At this time, the vehicle 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.

[0226] To explain the monitoring and control procedure in more detail using an example, as shown in FIG. 16, a vehicle including an FCEV can transmit a message to a dispenser to start fueling control (S1610), and in response, the dispenser can transmit a message including confirmation information (e.g., OK) to the vehicle (S1620).

[0227] In addition, the vehicle transmits a message including information about its fueling loop (e.g., x, y, z) to the dispenser (S1630), and the dispenser can provide the vehicle with a message including information about its fueling loop (e.g., a, b, c) corresponding to the vehicle's fueling loop (S1640).

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

[0229] In addition, the vehicle 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 vehicle including information on whether fuel supply is being suspended or has been suspended (stopping / stopped) (S1690).

[0230] In this way, the vehicle and the dispenser can continuously or periodically exchange parameters related to the fuel supply status through the monitoring and control procedure. The vehicle transmits the current tank temperature, current tank pressure, etc. to the dispenser, and the dispenser can provide the vehicle with parameters related to fuel supply start, stop, ramping up, ramping down, current injection pressure, future fuel supply plan, etc.

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

[0232] Messages related to reporting transmitted from the dispenser to the vehicle 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 fill is in use, whether cooling dispenser is in use, whether fallback is in use, reason for refueling stop, amount of hydrogen currently supplied, etc.

[0233] The message related to the target parameter update transmitted from the dispenser to the vehicle 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.

[0234] On the other hand, when TCP is used in the above-mentioned monitoring and control procedure, if the safety check-in response message or the safety check-in step according to the fuel supply protocol is omitted, the vehicle 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 in a DTLS message.

[0235] After hydrogen fueling is completed through the aforementioned monitoring and control procedures, before the session ends and the nozzle is separated from the vehicle, the vehicle (including the FCEV) and the dispenser can use a safety check-out use case to check whether the quantity and each dispenser meet all safety conditions. While this safety check-out step is optional, it is preferable to define a dedicated safety inspection procedure in the fueling protocol to ensure the desired safety level in an accurate and explicit manner.

[0236] FIG. 17 is a flow chart illustrating a safety check-out procedure that may be employed in a hydrogen filling communication two-way process according to one embodiment of the present invention.

[0237] Vehicles, including FCEVs, and dispensers can use safety checkout procedures to verify that all necessary safety conditions are met before separating the dispenser nozzle from the outlet. In other words, vehicles and dispensers can verify that it is absolutely safe for a user or worker to separate the nozzle from the vehicle after fuel supply is complete.

[0238] For example, after a vehicle receives a fuel supply loop response message from a 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 vehicle can begin safety checkout and transmit a safety checkout request message to the dispenser within the message sequence setting time to perform the safety checkout procedure.

[0239] The vehicle 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.

[0240] To explain the above-mentioned safety checkout procedure in more detail using an example, as shown in Figure 17, the vehicle can transmit a message to the dispenser containing information on the coupler check result (e.g., OK) (S1710), and the dispenser can transmit a message to the vehicle containing information indicating that the coupler check is in progress (e.g., Ongoing) (S1730).

[0241] The vehicle may also transmit a message including coupler inspection result information (e.g., OK) to the dispenser again (S1750), and the dispenser may transmit a message including coupler inspection completion information (e.g., Done) to the vehicle (S1770).

[0242] Once the coupler inspection completion information is confirmed to be completed normally, the dispenser nozzle can be detached from the vehicle receptacle by the user or operator.

[0243] In the safety checkout procedure, the report message transmitted from the dispenser to the vehicle may include information and parameters regarding the coupler unlock status. The coupler unlock status information may include information regarding locked, unlocked, icing, problem, etc.

[0244] The termination use case UC9 can be executed 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 in another use case.

[0245] FIG. 18 is a flow chart illustrating a termination procedure that may be employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. The termination procedure is the final stage of fuel supply, and vehicles including FCEVs and dispensers can complete all procedures for hydrogen filling by exchanging information on fuel supply results regarding fuel supply performance and methods, and / or information on the reasons for unexpected interruptions to fuel supply. The termination use case can also be configured to handle work related to issues that are not critical to safety if they occur.

[0246] For example, after a vehicle receives a safety checkout response message from a dispenser with the "result" set to "DONE" or a fuel supply loop response message with the "status" set to "finished" or the prefix "stopped," the vehicle can transmit a termination request message to the dispenser to perform the termination procedure.

[0247] To explain the termination procedure in more detail using an example, as shown in Figure 18, a vehicle including an FCEV can transmit a message to a dispenser inquiring about how much fuel has been supplied (S1810). In response to the FCEV's inquiry message, the dispenser can transmit a response message to the vehicle that includes information about the amount of hydrogen supplied (e.g., X gram) (S1830).

[0248] In addition, the vehicle may transmit a confirmation request message for the completion of fuel supply to the dispenser (S1850), and the dispenser may transmit a goodbye message to the vehicle as a response message to the confirmation request message (S1870).

[0249] Meanwhile, after fuel supply is completed and safety inspections are confirmed, the vehicle and the dispenser can exchange at least some bookkeeping information for the hydrogen filling session in a termination procedure. The vehicle and the dispenser can exchange summary information for the hydrogen filling session before completing the termination procedure.

[0250] Book-keeping information can include all hydrogen fueling-related information recorded in the vehicle and dispenser according to pre-established rules and policies across all fueling sessions and prior to completing the termination procedure for Use Case 9 (UC9).

[0251] 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 vehicle 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 vehicle may include information on the final SOC, final average fueling rate (APR), final measured tank pressure, actual fuel supply time, actual amount of hydrogen supplied, etc.

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

[0253] Table 8 below shows examples of communication data for some of the use cases UC5 to UC9 mentioned above. [Table 8] TIFF2025534326000010.tif154155

[0254] On the other hand, the error handling use case UC10 is a function block for safely handling situations where a non-fatal error occurs by terminating the fuel supply procedure or suddenly interrupting communication, just like a normal termination.

[0255] FIG. 19 is a flow chart illustrating an error handling procedure that may be employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. The error handling procedures may define error conditions associated with the fueling protocol, provide criteria for detection, and include procedures for responding when detected, including notification, termination procedures, and fallback mechanisms.

[0256] Referring to Figure 19, an error handling procedure can be applied when a non-safety-critical error occurs and further communication is not possible. That is, vehicles including FCEVs and dispensers can handle the occurrence of a non-safety-critical error at any time during fuel supply using the error handling procedure. In other words, the vehicle and dispenser can immediately stop fuel supply, pause the previously active use case, and then move to the termination use case UC9.

[0257] If the vehicle detects a non-safety fatal error event (S1910), the vehicle notifies the dispenser of the reason for termination via a terminate request (TerminateReq) message (S1930) and can terminate the current fuel supply session or communication session (S1950). The dispenser can terminate the current communication session in response to the terminate request message (S1970). If additional communication is not possible, the current session can be terminated without additional notification.

[0258] Additionally, if a non-safety critical error is detected in the vehicle and the communication channel continues to operate, the vehicle can send a TerminateReq message to the dispenser with the 'action' set to 'stop' and the 'reason' set to an appropriate reason or reason code, such as that the message is corrupted.

[0259] The above-mentioned termination request message may be transmitted in error situations such as communication errors, system errors, and qualitative errors that are not fatal to safety, except when recovery is not possible.

[0260] That is, for successful fuel delivery, communications must exhibit behavior expected by the protocol, and fuel delivery behavior must be within the acceptable range of the fuel delivery protocol. However, in practice, a variety of abnormal events can occur. Some errors are minor and can be easily handled, but other errors cannot be recovered and prevent fuel delivery from proceeding. Therefore, the error handling procedure defines error conditions that are not critical to safety and provides example error conditions and possible responses.

[0261] Examples of communication errors include a communication interruption, an encoding error, or a syntax error that prevents the received data from being recognized, or the received data is in an unacceptable range. A system error may include a case where a dispenser or vehicle independently detects a significant system error. And a qualitative error may include a case where the quality of communication performance does not meet the required level, or the quality of data completeness or accuracy does not meet the required level.

[0262] The hydrogen filling communication two-way process of this embodiment can perform the following specific error handling procedures (1) to (4) for the above-mentioned error conditions.

[0263] (1) If a non-safety-critical error occurs that makes further communication impossible, the vehicle and dispenser will immediately cease fueling, but may take safety measures to discontinue communication and end the session.

[0264] (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.

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

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

[0267] 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 can perform error handling procedures, including notification, termination procedures, and fallback mechanisms, if an error is detected by the detection criteria.

[0268] On the other hand, a safety-critical problem may occur during fuel supply in the hydrogen filling system, requiring urgent action.

[0269] FIG. 20 is a flow chart illustrating an emergency handling procedure that may be employed in a hydrogen filling communication two-way process according to one embodiment of the present invention. Emergency handling procedures may define safety critical conditions requiring emergency response during fuel filling and may include response procedures to prevent safety critical incidents.

[0270] For safe fuel delivery, communications must behave as expected by the protocol, and fuel delivery operations must be within the safe limits of the fuel delivery protocol. However, problems may occur during fuel delivery, causing the fuel delivery system (or hydrogen filling system) to reach a critical state that must be avoided at all costs. Therefore, emergency procedures can define emergency conditions that are important to safety and possible responses to emergency conditions, providing key cases that must be considered.

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

[0272] 20, when a vehicle, including an FCEV, detects a high pressure exceeding a preset reference value during a hydrogen filling procedure, the vehicle 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 (S2010). 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) to the vehicle (S2020).

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

[0274] Meanwhile, if the dispenser detects a hydrogen fuel leak during the hydrogen filling procedure, the dispenser may transmit a second emergency stop request message including information (e.g., Emg:Stopping(leaking)) notifying the vehicle that it is processing to stop fuel supply due to the leak (S2060). The vehicle may transmit a response message to the dispenser including information (e.g., Emg:Confirmed) notifying the vehicle that it has confirmed the second emergency stop request message (S2070).

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

[0276] According to the above-mentioned configuration, when a serious situation affecting safety is detected in a vehicle, including an FCEV, or a dispenser, 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 and communication can be cut off.

[0277] When an emergency notification message is received, the vehicle 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 body message linked to the header, and the header includes information indicating that it is an emergency notification, and the message may include values, information, or parameters for the class, type, and action for the emergency notification. The emergency notification message described above can be transmitted in a TLS or DTLS message depending on the technology used for communication.

[0278] Fig. 21 is a schematic block diagram of an apparatus (simply "hydrogen filling apparatus") utilizing a hydrogen filling communication two-way process according to yet another embodiment of the present invention. Fig. 22 is a block diagram illustrating software modules that can be employed in the hydrogen filling apparatus of Fig. 21.

[0279] Referring to FIG. 21, the hydrogen filling device 3000 may be implemented in the form of a computing device or computing system including a processor 3100 electronically coupled to a memory 3200.

[0280] The hydrogen filling device 3000 may be a device that provides hydrogen filling services, or a hydrogen filling control device or hydrogen filling communication device that is provided in such a device. Similarly, the hydrogen filling device 3000 may be a device that receives hydrogen filling services, or a hydrogen filling control device or hydrogen filling communication device that is provided in such a device.

[0281] The hydrogen filling device 3000 may also include a processor 3100, a memory 3200, a transceiver 3300, an input interface device 3400, an output interface device 3500, a storage 3600, and a bus 3700. The components included in the hydrogen filling device 3000 are connected to each other by the bus 3700 to perform communication.

[0282] The processor 3100 may include a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor configured to perform methods according to embodiments of the present invention.

[0283] Each of the memory 3200 and the storage 3600 may 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).

[0284] The hydrogen filling apparatus 3000 can execute at least some of the steps of the hydrogen filling communication two-way process, fuel supply protocol, fuel supply method, hydrogen filling protocol, or hydrogen filling method described above. To this end, the hydrogen filling apparatus 3000 can include at least one processor 3100 and a memory 3200 that stores instructions that instruct the at least one processor 3100 to execute at least one step. At least some steps of the above-described two-way process or method can be executed by the at least one processor 3100 loading and executing instructions from the memory 3200.

[0285] 22, the hydrogen filling device 3000 may include additional function blocks 3110-3180 in addition to the function blocks UC1-UC11 described with reference to Fig. 4. Such function blocks 3110-3180 may be mounted on the hydrogen filling device 3000 or at least one processor 3100 of the hydrogen filling device 3000.

[0286] The aforementioned functional blocks 3110 to 3180 may include a first functional block 3110 for version negotiation, a second functional block 3120 for session allocation, a third functional block 3130 for service negotiation, a fourth functional block 3140 for settlement negotiation, a fifth functional block 3150 for authentication, a sixth functional block 3160 for fuel supply parameter exchange, a seventh functional block 3170 for fuel supply, and an eighth functional block 3180 for abort / pause.

[0287] The first function block 3110 can check and compare the versions of communication protocols available for all fueling protocols when performing a handshake. The first function block 3110 can also check the TLS version, etc.

[0288] The second function block 3120 can assign IP addresses, IPv6 addresses, session identifiers, etc., depending on the vehicle or dispenser.

[0289] The third functional block 3130 can negotiate the services to be applied to hydrogen electric vehicles based on price, user convenience, etc. when there are differences in service items such as filling fees depending on the region, time of day, or service provider when filling hydrogen.

[0290] The fourth function block 3140 can determine the payment method for hydrogen filling and process the payment process.

[0291] The fifth function block 3150 can process at least one of user authentication, vehicle authentication, dispenser authentication, and hydrogen filling station authentication. The fifth function block 3150 can correspond to at least a portion of the function block of the discovery and pairing use case UC1.

[0292] The sixth function block 3160 may correspond to at least a portion of the function blocks of the fueling parameter negotiation use case UC5.

[0293] The seventh function block 3170 is a function for monitoring and controlling fuel supply and may correspond to at least a portion of the monitor and control use case UC7, and may correspond to at least a portion of a combination of the secure check-in use case UC6, the monitor and control use case UC7, the secure check-out use case UC8, and the terminate use case UC9.

[0294] The eighth function block 3180 is used to stop or temporarily suspend fuel supply, communication, etc. during error processing or emergency processing, and can correspond to at least a part of the combination of the error processing use case UC10 and the emergency processing use case UC11.

[0295] The hydrogen filling apparatus 3000 may also include various types of computing devices mounted on a vehicle or dispenser. Examples of such computing devices include a communication-enabled desktop computer, laptop computer, notebook computer, smartphone, tablet PC, mobile phone, smart watch, smart glass, e-book reader, portable multimedia player (PMP), portable game console, navigation device, digital camera, digital multimedia broadcasting (DMB) player, digital audio recorder, digital audio player, digital video recorder, digital video player, personal digital assistant (PDA), etc.

[0296] 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. Processor 3100 transmits a first message to a communication entity associated with dispenser 200, the first message including a list of at least one first fueling protocol supported by mobility 100 and a first communication protocol required to execute the at least one first fueling protocol, according to the at least one instruction, and receives a response message from the communication entity associated with dispenser 200, the response message including a second fueling protocol selected from the at least one first fueling protocol.

[0297] In a communication control device for hydrogen-fueled mobility 100 according to one embodiment of the present invention, the first message may include priority information based on the preferences of the mobility 100 .

[0298] In a communication control device of a hydrogen-fueled mobility 100 according to one embodiment of the present invention, the response message may include a second filling protocol selected from at least one of the first protocols based on preference-based priority information.

[0299] In a communication control device of a hydrogen-fueled mobility 100 according to one embodiment of the present invention, the response message may include a second filling protocol selected from among at least one first filling protocol and a common protocol commonly included in the protocols supported by the dispenser 200.

[0300] In the communication control device of the hydrogen-fueled mobility 100 according to one embodiment of the present invention, the response message may include a second filling protocol selected by the control device of the dispenser 200 from at least one of the first filling protocols.

[0301] In a communication control device of hydrogen-fueled mobility 100 according to one embodiment of the present invention, the response message may include a second communication protocol required by the control device of dispenser 200 to execute a second filling protocol.

[0302] In a communication control device of a hydrogen-fueled mobility 100 according to one embodiment of the present invention, the response message may include a second communication protocol selected from at least one communication protocol required by the control device of the dispenser 200 to execute a second filling protocol.

[0303] In one embodiment of the present invention, in a communication control device of a hydrogen-fueled mobility 100, the response message may include a second communication protocol determined by the device type that is fallbacked based on interoperability and backward compatibility between the mobility 100 and the dispenser 200 among multiple communication protocols required by the control device of the dispenser 200 to execute the second filling protocol.

[0304] In a communication control device of a hydrogen-fueled mobility 100 according to one embodiment of the present invention, the processor 3100 can transmit a negotiation request message for communication protocol negotiation between the mobility 100 and the dispenser 200 to a communication entity associated with the dispenser 200.

[0305] The protocol negotiation may be performed by the processor 3100 transmitting an acknowledgement message in response to the response message. The processor 3100 may transmit the first message as a negotiation request message to a communication entity associated with the dispenser 200 .

[0306] Meanwhile, in most of the above-described embodiments, the vehicle communication protocol and parameters are primarily transmitted from the dispenser to the vehicle, but the present invention is not limited to a specific embodiment and may be configured to transmit the dispenser communication protocol and parameters to the vehicle first. In this case, it is obvious that the same characteristics are essentially maintained, except that the sender becomes the receiver and the receiver becomes the sender in the corresponding embodiment.

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

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

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

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

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

[0312] 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 510 Protocol 1 520 IPv6 Protocol 530 Third Protocol 540 Protocol 4 550 JSON-based Session Protocol 560 JSON 570 Fuel Supply Protocol 900 UCDC Level 0 910 UCDC Level 1 920 UCDC Level 2 930 UCDC Level 3 3000 Hydrogen Filling Equipment 3100 processor 3110, 3120, 3130, 3140, 3150, 3160, 3170, 3180 Function Blocks 3200 memory 3300 Transmitter / Receiver 3400 Input Interface Device 3500 Output Interface Device 3600 Storage 3700 Bus< / ok> < / ok>

Claims

1. 1. A hydrogen filling communication protocol negotiation method performed by a communication controller of a hydrogen fueled mobility vehicle, comprising: transmitting a first message to a communication entity associated with a dispenser, the first message including a list of at least one first fueling protocol supported in the hydrogen-fueled mobility and a first communication protocol required to execute the at least one first fueling protocol; and A hydrogen filling communication protocol negotiation method comprising: receiving a response message including a second filling protocol selected from the at least one first filling protocol from a communication entity associated with the dispenser.

2. 2. The hydrogen filling communication protocol negotiation method of claim 1, wherein the first message includes priority information based on the hydrogen fueled mobility preference.

3. The response message The hydrogen filling communication protocol negotiation method of claim 2, further comprising selecting the second filling protocol from the at least one first filling protocol based on the priority information based on the preference.

4. The response message The hydrogen filling communication protocol negotiation method of claim 1, wherein the second filling protocol is selected from among common protocols commonly included in the at least one first filling protocol and protocols supported by the dispenser.

5. The response message 2. The hydrogen filling communication protocol negotiation method according to claim 1, wherein the second filling protocol is selected from the at least one first filling protocol by the dispenser control device.

6. The response message 6. The hydrogen filling communication protocol negotiation method of claim 5, further comprising a second communication protocol required by a controller of the dispenser to execute the second filling protocol.

7. The response message The hydrogen filling communication protocol negotiation method described in claim 6, characterized in that the second communication protocol is selected from at least one or more communication protocols required by the dispenser control device to execute the second filling protocol.

8. The response message 8. The hydrogen filling communication protocol negotiation method of claim 7, further comprising: a second communication protocol determined by a device type that falls back based on interoperability and backward compatibility between the hydrogen fuel mobility device and the dispenser among a plurality of communication protocols required by the dispenser's control device to execute the second filling protocol.

9. a communication request message for negotiating a communication protocol between the hydrogen-fueled mobility device and the dispenser is transmitted by the communication control device of the hydrogen-fueled mobility device to a communication entity associated with the dispenser; 2. The hydrogen filling communication protocol negotiation method of claim 1, further comprising a step of performing protocol negotiation by the communication control device of the hydrogen fueled mobility transmitting a confirmation message in response to the response message.

10. In the step of transmitting the first message, 10. The hydrogen filling communication protocol negotiation method of claim 9, wherein the first message is transmitted as the negotiation request message to the communication entity associated with the dispenser.

11. A communication control device for 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, transmitting a first message to a communication entity associated with a dispenser, the first message including a list of at least one first fueling protocol supported by the hydrogen-fueled mobility and a first communication protocol required to execute the at least one first fueling protocol; and receiving a response message from a communication entity associated with the dispenser, the response message including a selected second fill protocol of the at least one first fill protocol.

12. The communication control device of claim 11 , wherein the first message includes priority information based on the preference for hydrogen-fueled mobility.

13. The response message The communication control device according to claim 12, further comprising the second filling protocol selected from the at least one first filling protocol based on the priority information based on the preference.

14. The response message The communication control device of claim 11, wherein the second filling protocol is selected from a common protocol commonly included in the at least one first filling protocol and protocols supported by the dispenser.

15. The response message The communication control device of claim 11, further comprising the second filling protocol selected from the at least one first filling protocol by a controller of the dispenser.

16. The response message 16. The communications controller of claim 15, including a second communications protocol required by the dispenser controller to execute the second filling protocol.

17. The response message 17. The communication control device of claim 16, wherein the second communication protocol is selected from at least one communication protocol required by the dispenser control device to execute the second filling protocol.

18. The response message 18. The communication control device of claim 17, wherein the second communication protocol is determined by a device type that falls back based on at least one of interoperability and backward compatibility between the hydrogen fuel mobility and the dispenser among a plurality of communication protocols required for executing the second filling protocol by the dispenser control device.

19. The processor: transmitting a negotiation request message for negotiating a communication protocol between the hydrogen fuel mobility device and the dispenser to a communication entity associated with the dispenser; 12. The communication control device according to claim 11, wherein the protocol negotiation is performed by transmitting a confirmation message in response to the response message.

20. The communication control device of claim 19, wherein the processor transmits the first message as the negotiation request message to a communication entity associated with the dispenser.

Images