Bidirectional communication method and apparatus for hydrogen fuel supply

Abstract

A method according to an embodiment of the present invention comprises the steps of: broadcasting a dispenser discovery protocol (DDP) request message via a communication network including a dispenser for supplying hydrogen to a mobility means; receiving, from the dispenser, a DDP response message including identification information about the dispenser on the communication network; and performing authentication for pairing between the mobility means and the dispenser by using the identification information about the dispenser in the DDP response message between the mobility means and the dispenser.

Description

Two-way communication method and device for hydrogen fuel supply

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

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

[0003] Hydrogen vehicles, or hydrogen electric vehicles, are zero-emission vehicles that run on electricity generated by combining high-pressure hydrogen stored onboard with air. They are also called fuel cell electric vehicles (FCEVs). Most FCEVs use hydrogen as their energy source, generating electricity through a fuel cell system. FCEVs not only emit only pure water (H2O) during the electricity generation process, but also have the ability to remove ultrafine dust from the atmosphere during operation, making them a promising future eco-friendly form of mobility. Given the inexhaustible availability of hydrogen as a fuel and the environmental friendliness of the energy production process, they are gaining widespread attention as a technology with potential for widespread industrial application.

[0004] Hydrogen-fueled mobility refers to mobility that uses hydrogen as an energy source or fuel to generate electricity and use it to drive an electric motor. In addition to the hydrogen-powered vehicles described above, hydrogen-fueled mobility also includes aerial mobility, industrial trucks, trains, ships, and aircraft, as well as devices that use hydrogen as fuel to generate electricity and use it to drive vehicles.

[0005] Most hydrogen fuel cell vehicles use high-pressure hydrogen safely stored in hydrogen fuel tanks and oxygen supplied through an air supply system to deliver it to the fuel cell stack, where the electrochemical reaction between the hydrogen and oxygen produces electrical energy. This electrical energy is converted into kinetic energy via the drive motor, propelling the vehicle. While in motion, hydrogen fuel cell vehicles have the advantage of emitting only pure water through the exhaust.

[0006] Meanwhile, the concept of a hydrogen fuel cell vehicle (HV)—not a hydrogen electric vehicle—also refers to a vehicle that uses hydrogen as fuel. A HV uses the heat generated by directly combusting hydrogen in an internal combustion engine (ICE) to drive an electric motor. The method of supplying hydrogen for HVs is not significantly different from that for hydrogen electric vehicles.

[0007] The control technique for supplying hydrogen to a vehicle that uses hydrogen as fuel ultimately aims to control the temperature and pressure of the compressed hydrogen storage system (CHSS) on the fuel cell side to operate under the limit temperature and limit pressure conditions for the safety of hydrogen fuel supply.

[0008] The hydrogen fueling process, control techniques, and protocols for conventional hydrogen fuel cell vehicles were developed when wired and wireless communication technologies and control computing techniques were not yet mature. Therefore, they do not adequately reflect recent advancements in information and communication technology (ICT). Therefore, conventional hydrogen fueling technologies for hydrogen fuel cell vehicles are inefficient, slow, and unsuitable for large-scale hydrogen fueling.

[0009] In particular, in the case of hydrogen fuel supply communication, most hydrogen fuel supply control devices use one-way infrared communication devices in the case of wireless, and therefore, wireless-based hydrogen fuel supply communication still has the limitations and vulnerabilities of one-way communication.

[0010] The purpose of the present invention to solve the above problems is to provide a hydrogen fueling process of hydrogen fueled mobility, and a communication protocol for the process, which can overcome the limitations and vulnerabilities of existing one-way communication and improve the safety, compatibility, efficiency and reliability of hydrogen fueling, a communication protocol negotiation for the hydrogen fueling process, a fueling protocol negotiation, a fueling parameter negotiation method, a monitoring and control method, a safety check-in method, a safety check-out method and a device using the same.

[0011] Another object of the present invention is to provide an error handling and emergency handling method for a hydrogen fueling process, which handles errors and / or emergencies occurring during communication protocol negotiation, fueling protocol negotiation, fueling parameter negotiation, monitoring and control, safety check-in, and safety check-out processes for a hydrogen fueling process, and a device using the same.

[0012] Another object of the present invention is to provide a hydrogen fueling communication bidirectional process that can control a hydrogen fueling mobility and dispenser to determine a conventional communication medium or an advanced communication medium to effectively achieve a hydrogen fueling goal, a communication protocol negotiation process that considers bidirectional / unidirectional communication, and a device using the same.

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

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

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

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

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

[0018] In the step of performing authentication for pairing between the mobility and the dispenser, authentication for pairing between the mobility and the dispenser can be performed using the pairing identifier of the mobility and the pairing identifier of the dispenser.

[0019] In the step of performing authentication for pairing between the mobility and the dispenser, authentication for pairing between the mobility and the dispenser can be performed via a pairing channel different from the communication channel through which the mobility is connected to the communication network, using the pairing identifier of the mobility and the pairing identifier of the dispenser.

[0020] The step of performing authentication for pairing between the mobility and the dispenser may include the step of binding a pairing channel for pairing between the mobility and the dispenser to a communication channel using a pairing identifier of the mobility and a pairing identifier of the dispenser; and the step of performing authentication for pairing between the mobility and the dispenser using a pairing identifier of the mobility and a pairing identifier of the dispenser within the pairing channel.

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

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

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

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

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

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

[0027] In the step of performing authentication for pairing between the mobility and the dispenser, authentication for pairing between the mobility and the dispenser can be performed using the pairing identifier of the mobility and the pairing identifier of the dispenser.

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

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

[0030] A communication method for hydrogen fueling, performed by a communication device of a dispenser according to one embodiment of the present invention, may further include a step of negotiating a communication protocol or a fueling protocol between the mobility and the dispenser after pairing between the mobility and the dispenser is performed; and a step of monitoring and controlling a process of the dispenser supplying hydrogen to the mobility based on the fueling protocol.

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

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

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

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

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

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

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

[0038] According to a communication method for hydrogen fuel supply and a device using the same according to one embodiment of the present invention, that is, a hydrogen fuel supply control device or a communication control device for a vehicle / mobility, it is possible to overcome the limitations and vulnerabilities of existing one-way communication in a hydrogen fueling process of hydrogen fueled mobility including a hydrogen electric vehicle (FCEV: fuel cell electric vehicle) and a hydrogen fuel engine and a communication protocol therefor, and to improve the safety, compatibility, efficiency, and reliability of hydrogen fuel supply.

[0039] In addition, according to one embodiment of the present invention, a communication protocol negotiation, fueling protocol negotiation, and parameter exchange method for hydrogen fueling, and a communication protocol fallback rule can be provided, which select a communication protocol required for executing a protocol for hydrogen fueling according to a use case while considering priorities according to the preference of the mobility or dispenser while maximizing interoperability between the mobility and the dispenser and considering backward compatibility.

[0040] Additionally, according to one embodiment of the present invention, rules and procedures required for communication protocol negotiation, fueling protocol negotiation, and fueling parameter exchange can be provided to enable mobility and a dispenser to cooperate to effectively determine a conventional communication medium or an advanced communication medium to effectively achieve a hydrogen fueling goal.

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

[0042] In addition, according to one embodiment of the present invention, the rules and procedures required for a use case in which the monitoring and control, safety check-in, and safety check-out processes and the communication protocol negotiation, fueling protocol negotiation, and fueling parameter exchange processes are linked to effectively achieve the hydrogen fueling goal by cooperating with mobility and the dispenser can be provided.

[0043] In addition, according to one embodiment of the present invention, the rules and procedures required for a use case in which communication protocol negotiation, fueling protocol negotiation, fueling parameter negotiation, monitoring and control, error handling for a hydrogen fueling process that handles errors and / or emergencies occurring during the safety check-in and safety check-out processes, and emergency handling processes are linked to enable mobility and a dispenser to cooperate to effectively achieve a hydrogen fueling goal can be provided.

[0044] Additionally, according to one embodiment of the present invention, rules and procedures necessary for implementing a Dispenser Discovery Protocol (DDP) related process performed between hydrogen fuel mobility and a dispenser can be provided.

[0045] FIG. 1 is a conceptual diagram of a hydrogen fuel supply system for a fuel cell electric vehicle (FCEV) to which a two-way hydrogen fuel supply communication process according to one embodiment of the present invention can be applied.

[0046] Figure 2 is a partially enlarged view illustrating the physical connection structure between the FCEV and the dispenser in the hydrogen fuel supply system of Figure 1.

[0047] Figure 3 is a graph for explaining the state changes of hydrogen fuel that occur during the hydrogen fuel supply process by the hydrogen fuel supply system of Figure 1.

[0048] FIG. 4 is a framework for functional blocks that perform a series of hydrogen fueling procedures that can employ a hydrogen fueling communication bidirectional process according to one embodiment of the present invention.

[0049] FIG. 5 is an exemplary diagram showing a communication stack related to each use case that can be employed in a hydrogen fuel supply communication two-way process according to one embodiment of the present invention, centered on the OSI (Open Systems Interconnection reference model) 7 layer.

[0050] FIG. 6 is an exemplary diagram illustrating a pairing process of a discovery and pairing procedure that can be employed in a hydrogen fuel supply communication bidirectional process according to one embodiment of the present invention.

[0051] FIG. 7 is an exemplary diagram illustrating backward compatibility that can be employed in a hydrogen fuel supply communication bidirectional process according to one embodiment of the present invention.

[0052] FIG. 8 is an exemplary diagram illustrating backward compatibility that can be employed in a hydrogen fuel supply communication bidirectional process according to one embodiment of the present invention.

[0053] FIG. 9 is an exemplary diagram illustrating a communication data usage classification that can be employed in a hydrogen fuel supply communication two-way process according to one embodiment of the present invention and backward compatibility in the communication data usage classification.

[0054] FIG. 10 is a flowchart illustrating an authentication process of a communication security procedure that can be employed in a hydrogen fuel supply communication two-way process according to one embodiment of the present invention.

[0055] FIG. 11 is a flowchart illustrating a communication protocol negotiation procedure that can be employed in a hydrogen fuel supply communication bidirectional process according to one embodiment of the present invention.

[0056] FIG. 12 is a flowchart illustrating a fuel supply protocol negotiation procedure during a hydrogen fuel supply communication bidirectional process according to one embodiment of the present invention.

[0057] FIG. 13 is a flowchart illustrating a fueling parameter exchange / negotiation procedure that can be employed in a hydrogen fueling communication bidirectional process according to one embodiment of the present invention.

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

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

[0060] FIG. 16 is a flowchart illustrating one of the alternative embodiments of FIG. 4.

[0061] FIG. 17 is a flowchart illustrating a communication method for hydrogen fuel supply according to another embodiment of the present invention.

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

[0063] FIG. 19 is a conceptual block diagram of the internal structure of a generalized computing system that can be mounted on a hydrogen fuel mobility, dispenser, and / or fuel supply station as a communication device, a communication control device, and / or an electronic control device for hydrogen fuel supply according to one embodiment of the present invention.

[0064] In addition to the above purpose, other objects and features of the present invention will become apparent through the description of embodiments with reference to the attached drawings.

[0065] The present invention is susceptible to various modifications and embodiments. Specific embodiments are illustrated and described in detail in the drawings. However, this is not intended to limit the present invention to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the present invention.

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

[0067] In the embodiments of the present application, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.” Furthermore, in the embodiments of the present application, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.”

[0068] When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.

[0069] The terminology used in this application is only used to describe specific embodiments and is not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this application, it should be understood that the terms "comprise" or "have" indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but do not exclude in advance the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0070] 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 defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and will not be interpreted in an idealized or overly formal sense unless explicitly defined herein.

[0071] Some terms used in this specification are defined as follows:

[0072] Hydrogen fuel cell electric vehicles (FCEVs) generally include both fuel cell-powered vehicles (FCEVs) and internal combustion engine (ICE)-based vehicles that use hydrogen as fuel. The hydrogen fuel cell electric vehicles described below may also be referred to simply as FCEVs.

[0073] Although the following embodiments describe a hydrogen fuel cell vehicle as the main embodiment, 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 are disclosed with a focus on a hydrogen fuel cell vehicle, and according to another embodiment 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.

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

[0075] A Compressed Hydrogen Storage System (CHSS) may include at least one tank mounted on the vehicle side and a device coupled to the tank to compress and store hydrogen in the tank.

[0076] A pressure relief device (PRD) is placed in a CHSS and can be a device that isolates stored hydrogen from the vehicle's hydrogen fueling system and the surrounding environment and can discharge hydrogen to the outside.

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

[0078] Pressure Ramp Rate (PRR) is expressed in MPa / min and refers to the pressure increase rate of CHSS.

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

[0080] Pre-cooling can basically mean the process of cooling hydrogen in advance at a hydrogen charging station before fueling.

[0081] A dispenser is a component that delivers pre-cooled hydrogen to the CHSS. The dispenser is placed at a hydrogen charging station and can perform hydrogen refueling operations between the station's hydrogen storage tank and the vehicle's CHSS.

[0082] The nozzle is a device that is connected to the dispenser and is coupled to the receptacle of the hydrogen electric vehicle and allows the delivery of hydrogen fuel.

[0083] A fueling session may be used to mean communication sessions that occur across use cases for hydrogen fueling.

[0084] Interoperability can refer to the state in which components of a system can work together to achieve the intended function of the entire system. Information interoperability can refer to the ability of two or more networks, systems, devices, applications, or components to share information securely and effectively and easily with little or no user inconvenience.

[0085] Correlation / Association may include the process of establishing a relationship between two peer communication entities.

[0086] Command and control communication may refer to communication between an electric vehicle hydrogen fueling device and a hydrogen electric vehicle that exchanges information necessary for starting, controlling, and terminating the hydrogen fueling process.

[0087] Meanwhile, although the detailed description below illustrates embodiments related to hydrogen electric vehicles or fuel cell electric vehicles (FCEVs), it will be apparent to those skilled in the art that the spirit 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 generates electric energy using hydrogen as fuel and uses this to drive an electric motor. In addition to hydrogen electric vehicles, hydrogen fueled mobility may include aerial mobility, as well as industrial trucks, trains, ships, and aircraft, which produce electric energy using hydrogen as fuel and use this to drive devices.

[0088] In addition, the two-way communication process for hydrogen fuel supply of the present invention can be partially applied not only to hydrogen fuel mobility but also to buildings or facilities that use hydrogen as an energy source.

[0089] Additionally, in the following description, hydrogen fuel may include at least one of gaseous hydrogen and liquid hydrogen, and may basically mean compressed hydrogen, but is not limited thereto.

[0090] In addition, vehicles that utilize the hydrogen fuel supply communication two-way process are described with a focus on hydrogen electric vehicles (FCEVs) for convenience of explanation, but are not limited to this configuration and may also include hybrid EV (electric vehicle) vehicles that use hydrogen as fuel, and ICE (internal combustion engine) vehicles.

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

[0092] In the following specification, some or all of the processes of the communication method, the communication protocol negotiation method, the hydrogen fueling (fueling) protocol negotiation method, the hydrogen fueling (fueling) parameter negotiation method, the hydrogen fueling (fueling) method, and the hydrogen fueling (fueling) control method performed in the dispenser may be performed by a controller, an electronic control unit, a communication unit, or a communication control unit of the dispenser. In addition, some processes of the above methods may be performed by a controller, an electronic control unit, a communication unit, or a communication control unit of a fueling station associated with the dispenser.

[0093] Meanwhile, even if a technology was known prior to the filing date of the present invention, it may be included as a part of the composition of the present invention if necessary, and this will be described in this specification to the extent that it does not obscure the spirit of the present invention. However, in explaining the composition of the present invention, a detailed description of matters that were known prior to the filing date of the present invention and that could be clearly understood by those skilled in the art may obscure the spirit of the present invention, and therefore, an excessively detailed description of the known technology will be omitted. In addition, the spirit of the present invention is not to claim any rights to these known technologies, and the contents of the known technologies may be included as a part of the present invention to the extent that they do not deviate from the spirit of the present invention.

[0094] For example, in the case of one-way communication, IrDA technology may be used, in the case of two-way communication, short-range wireless communication technology (Bluetooth, WLAN, UWB) may be used, or wired communication technology for one-way / two-way communication may be used, and any of the known technologies prior to the filing of the present invention may be used, and at least some of these known technologies may be applied as element technologies necessary for implementing the present invention.

[0095] Hereinafter, a preferred embodiment according to the present invention will be described in detail with reference to the attached drawings.

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

[0097] Referring to FIG. 1, the hydrogen fuel supply system can be configured to include a hydrogen charging station and a hydrogen electric vehicle (100) in a broad sense.

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

[0099] The electronic control unit (110) transmits and receives signals and data to and from a hydrogen charging station or an electronic control unit (210) of a hydrogen charging station via wire or wirelessly for hydrogen fuel supply, and processes the signals and data to control hydrogen fuel supply on the vehicle side. The electronic control unit (110) may be configured as at least a part of another electronic control unit mounted on the vehicle, or vice versa, and may be referred to as a first electronic control unit or electronic control unit #1.

[0100] The vehicle system (120) may be connected to the first electronic control unit (110) and configured to control the hydrogen fuel supply or hydrogen discharge of the vehicle tank (130) according to a signal or command of the first electronic control unit (110) and to monitor the status of the vehicle tank (130). Depending on the implementation, the vehicle system (120) may include a component that controls the operation of the fuel cell system or performs such control operations, or may be configured to be coupled with such a component. This vehicle system (120) may also perform a vehicle safety function, in which case it may also be referred to as a vehicle safety system.

[0101] At least one, and preferably multiple, vehicle tanks (130) may be provided. The vehicle tank (130) may compress and store hydrogen supplied from a hydrogen charging station under the control of a vehicle safety system, and may release the stored hydrogen.

[0102] In addition, the vehicle tank (130) may correspond to a hydrogen storage system attached to the vehicle. In this case, the hydrogen storage system may be composed of a high-pressure hydrogen storage tank, a pressure control device, a high-pressure pipe, and an external frame. The high-pressure hydrogen storage tank may have a capacity of tens to hundreds of liters, and may be configured by connecting small storage tanks in parallel. A boss unit through which hydrogen fuel can be supplied or discharged may be combined with the high-pressure hydrogen storage tank, and hydrogen fuel supply and hydrogen discharge may be controlled through the boss unit. Valves, a pressure reducing device, and sensors for various measurements may be attached to the boss unit. Such a hydrogen storage system is known as a compressed hydrogen storage system (CHSS), and the expression "vehicle tank" in this specification may mean CHSS for the convenience of explanation.

[0103] 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 a 'FCEV', 'vehicle', or mobility (100). In the following specification, the subject simply referred to as a vehicle or mobility may be understood to include a vehicle / mobility that uses hydrogen as fuel in addition to the hydrogen electric vehicle (100).

[0104] A hydrogen charging station may be equipped with a dispenser (200), an electronic control unit (210), a charging station system (220), a hydrogen tank (230), a station box (240), and a nozzle (250).

[0105] The dispenser (200) can supply hydrogen supplied from a hydrogen tank (230) to a vehicle through a nozzle (250) rigidly connected to a receptacle (150) of the vehicle under the control of a charging station system (220). The dispenser (200) may have an electronic control device (210) inside the housing, but is not limited thereto. The nozzle (250) can basically be installed at the end of a cable extending to a certain length outside the housing of the dispenser (200).

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

[0107] Each of the aforementioned first electronic control unit (110) and second electronic control unit (210) may be comprised of multiple electronic control units, and may be configured to match and operate different electronic control units for each communication protocol. This may be useful when falling back to ensure backward compatibility and when two-way communication cannot be used and unidirectional communication must be used. Furthermore, when performing actual fuel supply after pairing via NFC, this may be useful when combining different communication methods, such as when using WiFi.

[0108] The charging station system (220) can monitor or control the pressure, speed, and temperature of hydrogen discharged from the hydrogen tank (230) based on signals and / or data from the second electronic control unit. To this end, the charging station system (220) can control the operation of the station box (240) connected to the discharge port or discharge valve of the hydrogen tank (230). The charging station system (220) may also be referred to as a charging station safety system.

[0109] In another embodiment of the present invention, the communication entity associated with the dispenser (200) for communicating with the vehicle / mobility (100) may be an electronic control device (210), a separate communication device mounted on the dispenser (200), or an electronic control device or separate communication device within the charging station system (220) may communicate with the vehicle / mobility (100) in place of the dispenser (200).

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

[0111] The hydrogen tank (230) stores hydrogen or compressed hydrogen. The hydrogen tank (230) can release the stored hydrogen at a predetermined pressure or speed under the control of the safety management module within the charging station system (220). The hydrogen tank may also be referred to as a hydrogen storage tank.

[0112] The station box (240) may be equipped with a control 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 be equipped with a means for adjusting the pressure, speed, temperature, etc. of the hydrogen being discharged, or a component that performs a function corresponding to such means. In addition, the station box (240) may be equipped with sensors for measuring the pressure, speed, temperature, etc. of the hydrogen being discharged.

[0113] The nozzle (250) can be connected to the hydrogen fuel supply system of the dispenser (200) through a conduit or flexible pipe of a predetermined length. The nozzle (250) can have a shape and structure that tightly and firmly engages with the receptacle of the vehicle.

[0114] The nozzle (250) can be engaged with the receptacle (150) as shown in Fig. 2. At this time, a signal or information regarding the engagement status of the nozzle (250) and the receptacle (150) is transmitted to the first electronic control unit or the vehicle safety system by the first sensor (160) installed in the vehicle and the second sensor (260) attached to the nozzle (250), and can also be transmitted to the second electronic control unit or the charging station safety system.

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

[0116] The interface between the hydrogen charging station and the vehicle (100) can be handled by the dispenser (200). The dispenser (200) can be configured to control the target pressure and injection speed for hydrogen fuel supply by synthesizing information indirectly obtained from the vehicle tank (130) and fuel supply information of the hydrogen charging station.

[0117] In the existing technology, there are two ways to transmit information from a vehicle (100) to a dispenser (200): a communication method and a non-communication method. When using communication, in the existing technology, the temperature and pressure values ​​of the vehicle tank (130) of the vehicle (100) are simply transmitted in one direction to the dispenser (200), and the dispenser (200) does not actively utilize the information, but only utilizes it as a safety standard, such as an emergency stop at the limit temperature and pressure. In addition, the hydrogen fuel supply protocol for safe and rapid fuel supply is managed by the dispenser (200), and only has a minimum safety management device that automatically discharges hydrogen through a pressure relief device (PRD) without active safety management of the vehicle tank (130).

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

[0119] A fuel supply control logic may be installed inside the dispenser (200) or in the second electronic control device, and the fuel supply control logic may be used to control the hydrogen fueling process by utilizing status information such as temperature and pressure of hydrogen fuel supplied to the vehicle or fueled to the vehicle tank (130), and fuel supply status information such as the state of charge (SOC, State of Charge) of the CHSS.

[0120] As described above, the hydrogen fueling process is controlled between the vehicle (100) and the hydrogen charging station by the dispenser (200), and the dispenser (200) may be equipped with a protocol for supplying hydrogen fuel to the vehicle according to a set procedure. This hydrogen fueling protocol may also be equipped in the vehicle. The protocol equipped in the vehicle or the dispenser (200) may include at least a portion of a communication protocol according to the SAE standard, ISO standard, etc.

[0121] To determine minimum safety requirements, simulations using thermodynamic modeling can be performed for various situations. The resulting parameters can be used in a table-based or MC-formula-based partial real-time correction (PRC) approach. These minimum safety requirements can include upper limits on CHSS temperature and pressure conditions and guidelines for the state of charge (SOC).

[0122] If the dispenser (200) does not actively control the status values ​​related to hydrogen fuel supply, the table-based method of the prior art has very low efficiency because it does not utilize the temperature of the pre-cooled hydrogen fuel provided from the gas filling station or the temperature of the vehicle tank (130) measured in the vehicle (100), and it is difficult to flexibly respond to changes in the surrounding conditions. In addition, the MC-Formula-based method of the prior art corrects the temperature of the pre-cooled hydrogen fuel in real time, but the calculation and application methods are complicated and the application is limited, making it difficult to expand. In this way, the existing communication protocol was developed with the main goal of completing safe fuel supply, and there is no alternative to actively control unexpected situations such as excessive pre-cooling or overheating of the vehicle tank (130). This may cause problems such as increased operating costs due to overcooling and delayed fuel supply due to overheating.

[0123] For example, when hydrogen fuel is supplied to a vehicle tank (see 130 in FIG. 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 to cover the dome and body of the vehicle tank with carbon fiber, which has low heat transfer efficiency, in order 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 fuel supply process, the temperature increase visible on the surface of the vehicle tank may be minimal compared to the internal temperature increase until the fuel supply is completed due to the low heat transfer characteristics of the vehicle tank.

[0124] Meanwhile, the temperature control of the hydrogen fuel supply process can be aimed at controlling the internal temperature of the vehicle tank (130) to be 85°C or lower at the time of completion of the final fuel supply by receiving pre-cooled hydrogen gas. That is, as shown in the characteristic curve for the hydrogen temperature during hydrogen fuel supply in FIG. 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 charging station, the temperature of the hydrogen fuel gradually increases due to the thermal mass of the hydrogen charging station in Phase II (P2), which is the stage of supplying hydrogen fuel from the hydrogen charging station to hydrogen mobility such as vehicles, the temperature of the hydrogen fuel 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 the temperature of the hydrogen fuel may rapidly 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.

[0125] Accordingly, in this embodiment, a hydrogen fuel supply procedure can be effectively performed through active state variable control reflecting real-time measurement data through a two-way hydrogen fuel supply communication process, and a hydrogen fuel supply protocol for this purpose can be provided.

[0126] FIG. 4 is a framework (hereinafter referred to as “hydrogen fuel supply framework”) for functional blocks that perform a series of hydrogen fuel supply procedures that can employ a hydrogen fuel supply communication two-way process according to one embodiment of the present invention.

[0127] Referring to FIG. 4, the hydrogen fuel supply framework is composed of function blocks for each use case (UC), including 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), and an emergency handling function. Blocks (UC11 or UC-11) can be equipped.

[0128] Each of the UC1 to UC11 function blocks may correspond to time-series steps (S401 to S411) as illustrated in FIG. 4. In this case, FIG. 4 may also be understood as an operational flowchart including time-series steps (S401 to S411).

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

[0130] The aforementioned use cases are functional blocks that collectively provide the entire hydrogen fueling procedure of a hydrogen fueling system in a consistent manner for safe and secure fueling communication. Vehicles and dispensers can sequentially execute each use case in a specific order to achieve the hydrogen fueling goal.

[0131] Additionally, after the dispenser nozzle is connected to the vehicle receptacle, the vehicle and the dispenser can perform fuel supply communication by implementing each use case in the order shown in Fig. 4. However, the vehicle and the dispenser may omit certain use cases as needed based on predefined requirements.

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

[0133] Meanwhile, the hydrogen fuel cell vehicle (hereinafter referred to simply as "vehicle") and dispenser implementing the aforementioned use case can exchange data for vehicle identification in UC-1. To this end, the vehicle may be equipped with sensors, an electric control unit (ECU), a transmitter, and a receiver. The receiver may be integrated with the transmitter for two-way communication.

[0134] The dispenser may be configured to receive specific data from the vehicle. The dispenser may store data for data logging or data designated by the charging station programmable logic controller (PLC) for use in the fueling protocol. Data logging may refer to a process of collecting data over a period of time to analyze a specific operating state of a hydrogen fueling system or to record data-based events / operations in a system or network environment, or data collected by this process. For two-way communication, the charging station may be equipped with a sensor designated by the fueling protocol, and the charging station PLC or electronic control unit may obtain measurements from the sensor and transmit these measurements to the vehicle. The aforementioned vehicle or charging station may use existing communication protocol standards for communication, such as infrared, Wi-Fi, or Bluetooth.

[0135] Additionally, the vehicle and dispenser can establish a communication channel between the vehicle and dispenser, physically connected at the vehicle-dispenser interface. The pairing process for establishing this communication channel can be performed using wired, optical, or wireless technologies.

[0136] The discovery and pairing procedure or pairing process may have prerequisites for the dispenser nozzle to be inserted into and securely connected to a vehicle fueling receptacle. The vehicle fueling receptacle may be simply referred to as a vehicle receptacle or receptacle.

[0137] Furthermore, the vehicle and dispenser inherently know which communication protocol to use. Therefore, subsequent communications after UC-1 can rely solely on the communication protocol agreed upon in the current use case, either as a discovery and pairing procedure or as a post-condition of the pairing process. If either the vehicle or dispenser selects a communication protocol outside the agreed upon scope, the selected communication will not occur. In other words, even if the pairing process completes successfully, fuel authorization or fuel delivery authorization may not be granted.

[0138] All methods used to pair the vehicle and dispenser must be designed to avoid increasing the risk of ignition or explosion beyond an acceptable level. For example, all wired pairing methods must be designed to mitigate or prevent sparking hazards caused by electrostatic discharge.

[0139] In terms of the effectiveness of physical pairing, any method used to pair a vehicle and a dispenser can be integrated into a vehicle-dispenser interface or installed so as to have proximity between the vehicle's fueling receptacle and the dispenser's nozzle and hose assembly. Here, the interface can refer to something physically integrated into the nozzle-receptacle interface. Proximity can be defined by hardware associated with the pairing method. For example, the physical geometry used for infrared communication can be specified, including the allowed distance between the transmitter and receiver. Furthermore, the physical configuration of the hydrogen fueling hardware can be pre-specified, and proximity does not include a pairing method that risks pairing a physically unconnected vehicle and dispenser, such as a relatively long-range wireless communication technology such as Bluetooth. Infrared communication can be referred to as infrared data association (IrDA) communication and can include bidirectional infrared (bi-IrDA) communication.

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

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

[0142] FIG. 5 is an exemplary diagram showing a communication stack related to each use case that can be employed in a hydrogen fuel supply communication two-way process according to one embodiment of the present invention, centered on the OSI (Open Systems Interconnection reference model) 7 layer.

[0143] As illustrated in Fig. 5, the communication stack related to the use case of the hydrogen fueling communication two-way process (briefly referred to as the 'hydrogen fueling 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 belonging to the OSI 7 layer.

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

[0145] Additionally, the hydrogen fuel supply communication stack may include the IPv6 (internet protocol version 6) protocol (520) as a protocol of the network layer of the OSI 7 layer.

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

[0147] Additionally, the hydrogen fueling communication stack may include at least one fourth protocol (540) selected from among TLS (transport layer security), DTLS (datagram transmission layer security), etc., as a protocol of the security layer of the OSI 7-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 in a TCP socket, and DTLS may be implemented in a UDP socket.

[0148] Additionally, the hydrogen fueling communication stack may 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) may be used when communicating between a vehicle and a dispenser or when sending data between an electronic control unit of a vehicle and an electronic control unit of a charging station.

[0149] Additionally, the hydrogen fueling communication stack may include JSON (JavaScript object notation) (560), a protocol at the presentation layer of the OSI 7-layer model. JSON is one of the formats that can be used when sending data from a server to a client. Using JSON, protocol messages between a vehicle and a dispenser, or between a vehicle's electronic control unit and a charging station's electronic control unit, can be expressed in JSON.

[0150] In addition, the hydrogen fueling communication stack may include fueling protocols (FP) (570) related to hydrogen fueling as a protocol of 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 nth fueling protocol (FPn). n may be any natural number greater than or equal to 3.

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

[0152] The overall communication data items exchanged between the vehicle and the charging station through the aforementioned hydrogen fuel supply communication stack are as shown in Table 1 below.

[0153] Charging station → Vehicle → Charging station communication data items - Supply hydrogen pressure - Supply hydrogen temperature - Supply hydrogen flow rate - Maximum supply hydrogen pressure - Maximum supply hydrogen temperature - Minimum supply hydrogen temperature - Maximum supply hydrogen flow rate - Ambient temperature - Communication availability (comm / non-comm) - Target value - Fuel supply in progress - Emergency stop - Hydrogen fuel supply protocol category - Supply hydrogen amount - Expected completion time of hydrogen fuel supply - Receptacle type - Receptacle operating pressure - Tank volume - Tank pressure - Tank temperature - Maximum operating pressure - Maximum operating temperature

[0154] Meanwhile, the use case (UC1) of the discovery and pairing step (S401) of FIG. 4 enables the device to identify the communication partner (the vehicle or dispenser's communication module) responsible for controlling the physically connected receptacle or nozzle. UC1 can also define a method for identifying incompatibilities and define a safety mechanism.

[0155] In this use case (UC1), the vehicle and dispenser may attempt to discover a common communication technology to implement the fueling protocol. Based on the discovery mechanisms provided by the underlying data link and physical layers, the vehicle and dispenser can discover each other and initiate communication. An additional pairing procedure is required to establish a communication channel with the device connected to the fueling hose assembly. If the communication channel does not guarantee proper pairing, for example, in the case of wireless communication, a separate pairing channel may be required to convey pairing information. If pairing is implicitly guaranteed, for example, the communication channel integrated with the hose assembly may suffice.

[0156] Table 2 is a table showing the purpose, prerequisites, and follow-up conditions of use case UC1 of the discovery and pairing step (S401) of FIG. 4.

[0157] TypeDescriptionUse case nameUC-1: "Discovery and Pairing"ObjectivesUC-1 allows devices to identify the communication counterparty (communication module of vehicle or dispenser) that is responsible for the control of the physically connected receptacle or nozzle, respectively. UC-1 also defines how to identify incompatibility and may define a failsafe mechanism.Short DescriptionDuring this use case, vehicle and dispenser try to find out any common communication technologies to run a fuelling protocol. Depending on the discovery mechanism provided by the underlying physical / data-link layer, the vehicle and dispenser discovers each other and start communication. To ensure that the communication channel is established with the devices that are bound to the fuelling hose assembly, extra pairing procedure may need to be involved. When communication channel does not guarantee the correct pairing (e.g., wireless communication), we may need an extra pairing channel that delivers pairing information. When pairing is implicitly guaranteed (eg, communication integrated with hose assembly), only communication channel should be sufficient.Pre-conditionsThe dispenser nozzle is securely connected to the vehicle receptaclePost-conditionsVehicle and Dispenser knows what communication medium to use for the communication. After this use case, subsequent communication solely depends on the communication protocol that was agreed on in this use case. If an out-of-scope communication protocol is chosen, no further ISO 19985 communication is performed.

[0158] Table 3 is a table showing supported communication technologies and their respective clauses that can be used in use case UC1 of the discovery and pairing step (S401) of FIG. 4.

[0159] ClauseCommunication TechnologyCommunication ChannelPairing ChannelAnnex P.1Unidirectional irDA(irDA references)N / AAnnex P.2Bidirectional IrDA(irDA references)N / AAnnex P.3WLAN with NFCIEEE 802.11NFC Forum Specifications

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

[0161] Referring to FIG. 6, in the discovery and pairing step (S401) of FIG. 4, the pairing process is such that when pairing at UCDC level 2 and UCDC level 3, the vehicle and the dispenser can exchange pairing IDs and check the other party's pairing ID.

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

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

[0164] This transmit-echo-verify method allows vehicles and dispensers to use session-specific, randomized pairing IDs. This addresses privacy concerns surrounding pairing ID exchange. Trust in the pairing process is established through subsequent processes, and the session-specific pairing ID is included in the data used to establish trust.

[0165] Meanwhile, if secure communication is supported at a specific UCDC level, at least one of the vehicle and dispenser can ensure that the pairing provides sufficient information to secure the communication channel for any method used to pair the vehicle and dispenser. For example, pairing may include the exchange of encryption keys to enable the vehicle and dispenser to secure communication during refueling.

[0166] Note that UCDC Level 1 does not support bidirectional communication, so securing the communication channel may not be possible. Pairing a vehicle and dispenser at UCDC Level 2 and UCDC Level 3 can be configured to provide sufficient information to secure the communication to meet a specific security level, such as IEC 62443 Security Level 3. IEC 62443 Security Level 3 can be a security level for actors with adequate resources and appropriate motivation.

[0167] FIG. 7 is an exemplary diagram illustrating backward compatibility that can be employed in a hydrogen fuel supply communication bidirectional process according to one embodiment of the present invention.

[0168] Referring to Figure 7, the hydrogen fuel supply device can be designed as a backward-compatible device with existing devices, taking interoperability into consideration. When classifying devices based on interoperability, the hydrogen fuel supply device or its communication device can be classified into Type 0, Type 1, Type 2, and Type 3.

[0169] Type 0 may refer to a device that does not support fueling communication or does not receive such communication messages.

[0170] Type 1 may refer to a device that supports IrDA communication for fuel supply. Type 1 devices can fallback to Type 0 devices.

[0171] Type 2 can refer to devices that support advanced communication (AC). Type 2 devices can fall back to Type 0 devices.

[0172] Type 3 can refer to devices that support IrDA and advanced communications. Type 3 devices can fall back to any of Type 0, Type 1, or Type 2.

[0173] Advanced communication can refer to communication using a medium such as wireless local area network (WLAN), Bluetooth (BT), near field communication (NFC), WiFi, ultra-wideband (UWB), radio frequency identification (RFID), 4G, 5G, etc. and a specific protocol. In addition, advanced communication can include bidirectional IrDA, serial communication, automotive Ethernet (ETH), high level communication, etc. Here, specific protocols can include transmission control protocol / internet protocol (TCT / IP), fueling protocol, etc. High level communication can process all information exceeding the information handled by command and control communication. The data link of high level communication can use PLC (Power line communication), but is not limited thereto.

[0174] Additionally, advanced communications can take the form of hybrids, combining IrDA and wired or IrDA and wireless. Combining IrDA and wired may require modifications to the nozzle and receptacle.

[0175] In other words, advanced communication can be a two-way communication technology, either wired or wireless, and wireless communication technologies can include various communication means such as 5G, WLAN, BLE, ETH, UWB, RFID, and NFC. Known protocols such as TCP / IP can be used as protocols for these communication means. For example, communication means considered as wireless communication can use Bluetooth, WLAN, Wi-Fi (ISO 15118 for inductive / ACD), UWB (IEC limited consideration for ACD), etc.

[0176] In practice, hydrogen fueling devices can be implemented to support communication across different technologies. Accordingly, the bidirectional hydrogen fueling communication process of this embodiment is configured to maximize interoperability between devices.

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

[0178] Additionally, when a Type 2 device supporting Specification #2 according to a given standard encounters a Type 0 device or a Type 1 device, the Type 2 device can fall back to a Type 0 device (S620).

[0179] And when a Type 3 device supporting Specification #2 encounters a Type 0 device, the Type 3 device can fall back to the Type 0 device (S630). When a Type 3 device encounters a Type 1 device, the Type 3 device can fall back to the Type 1 device (S640). Also, when a Type 3 device encounters a Type 2 device, the Type 3 device can fall back to the Type 2 device (S650).

[0180] The aforementioned standard #1 may include the SAE (Society of Automotive Engineers) standard, etc. The standard #2 may include the ISO 19885-3 standard, etc.

[0181] Additionally, to support the aforementioned interoperability, the hydrogen fueling device may perform a connection compatibility check. For example, the hydrogen fueling device may perform a connection compatibility check as in Scenarios 1 through 3 below, depending on whether it supports WLAN, one of the advanced communication technologies.

[0182] In Scenario 1, the dispenser can serve as an access point (AP), a wireless router. The dispenser can support FCEV fuel station beaconing and fueling methods from xVSE (x-vehicle supply equipment). FCEVs in proximity to the dispenser can scan for the dispenser and establish a WLAN link with it.

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

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

[0185] FIG. 8 is an exemplary diagram illustrating backward compatibility that can be employed in a hydrogen fuel supply communication bidirectional process according to one embodiment of the present invention.

[0186] Referring to FIG. 8, the hydrogen fueling communication bidirectional process of the present embodiment may provide rules and principles for the fueling method and communication protocol to fall back to maximize interoperability without necessarily having the FCEV and dispenser select the most preferred communication method.

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

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

[0189] The aforementioned specification #1 may be a communication protocol of the SAE standard, and specification #2 may be a toe-in protocol of the ISO 19885 standard.

[0190] According to the aforementioned configuration, if there are two devices with "identical implementations," the vehicle and dispenser can both support and select the best of them. When a non-communication device (hereinafter referred to as a "non-communication device") encounters a device that supports unidirectional communication (hereinafter referred to simply as a "unidirectional communication device"), the latter can fall back to a no-communication (No communication) device that does not support any communication method. Furthermore, when two devices that support bidirectional communication encounter each other, both devices can maintain their bidirectional communication method. UCDC compatibility can be handled separately here. Furthermore, when a device encounters a non-communication device, it can rely on the non-communication method. This can be applied to all devices that support bidirectional communication (hereinafter referred to simply as a "bidirectional communication device").

[0191] Additionally, when a unidirectional communication device encounters a bidirectional communication device, if the bidirectional communication device supports both unidirectional and bidirectional communication modes, the bidirectional communication device can fall back to unidirectional communication mode. Furthermore, if the bidirectional communication device does not support unidirectional communication, the bidirectional communication device can fall back to the non-communication device, relying on no communication.

[0192] The aforementioned two-way communication device can be configured to support a fueling method using one-way communication, regardless of whether one-way communication is available. Such a two-way communication device must be able to verify 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.

[0193] FIG. 9 is an exemplary diagram illustrating a communication data usage classification that can be employed in a hydrogen fuel supply communication two-way process according to one embodiment of the present invention and backward compatibility in the communication data usage classification.

[0194] As shown in Fig. 9, the vehicle and the dispenser may have a pairing identity (ID), and the requirements for exchanging such identities may be classified by the use classification of communication data (UCDC) level. The UCDC level may have UCDC Level 1 (UCDC-1) (910), UCDC Level 2 (UCDC-2) (920), and UCDC Level 3 (UCDC-3) (930). The UCDC level may further have UCDC Level 0 (UCDC-0) (900).

[0195] UCDC Level 0 (900) may refer to communications that are not used by the fueling protocol for dispensing hydrogen or related safety functions, either because no data is transmitted or because data is transmitted. 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.

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

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

[0198] At UCDC Level 3 (930), static and dynamic data can be used for dynamic control within protocols or safety functions. This UCDC Level 3 (930) dynamic data may be in addition to the permitted uses for static and dynamic data defined for UCDC Level 2.

[0199] As described above, the UCDC levels can have a form where UCDC level 1 is included in UCDC level 2, and UCDC level 2 is included in UCDC level 3, i.e., a higher level includes a lower level. A device supporting a specific UCDC level can support a device with a lower UCDC level. Devices supporting different UCDC levels can use the highest UCDC level supported by both devices. It can be said that the UCDC levels described above also easily support UCDC level 0. It can be seen that the UCDC levels are backward compatible. In another embodiment of the present invention, backward compatibility can be effectively applied to each of Non-Comm, Uni-directional Comm, Bi-directional Comm, and combinations thereof, regardless of the UCDC level.

[0200] Referring to FIGS. 4 to 8 together, information regarding interoperability and / or compatibility between a vehicle / mobility and a dispenser may be shared in the discovery and pairing step (S401) of FIG. 4. In this case, interoperability and / or compatibility may be utilized in the communication protocol negotiation step (S403), the fuel supply protocol negotiation step (S404), and / or the fuel supply parameter negotiation step (S405), which will be described later.

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

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

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

[0204] A dispenser receives a DDPRequest and can respond to the DDPRequest by sending a DDPResponse. The DDPResponse can contain the dispenser's IP address "IPAddr", the dispenser's TCP port number "TCPPort", the dispenser's UDP port number "UDPPort", and the dispenser's pairing ID "pairing_id".

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

[0206] Referring to FIG. 10, the mobility may transmit a message requesting a list of authorization methods to the dispenser (S1010). The dispenser may transmit a response message to the mobility's request for a list of authorization methods (S1020). The response message may include information on a list of authentication methods related to external authentication procedures, such as radio frequency identification (RFID), credit cards, or debit cards, or to its own authentication procedures.

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

[0208] Next, the mobility may perform authentication using the previously selected authentication method based on the dispenser's response and transmit a confirmation (Done?) request message regarding the authentication performance to the dispenser (S1050). If the authentication performance is not confirmed or is not completed, the aforementioned series of steps (S1010 to S1050) may be repeated. Upon completion of authentication, the dispenser may transmit an authentication completion (Done (success)) message to the mobility (S1090).

[0209] According to the above configuration, the dispenser can check whether the mobility is authorized, i.e., whether the user of the mobility is authorized to supply hydrogen fuel, before proceeding further with the hydrogen fueling process.

[0210] To secure the authentication process, a hydrogen fueling device including at least one of a mobility device and a dispenser may establish a transport layer (i.e., a TCP connection) after a data link and physical layer connection is established between the mobility device and the dispenser, perform a TLS handshake for authentication, and exchange keys to establish a secure communication channel. Additionally, UDP communication protected by DTLS may be used while exchanging security-critical information.

[0211] Additionally, the mobility and dispenser can successfully complete the discovery and pairing procedures and establish data link and physical layer connections. Then, the credentials required for authentication and key exchange can be prepared. This allows the communication channel between the mobility and dispenser to be encrypted and integrity-protected. The dispenser can authenticate the mobility, and optionally, the mobility can authenticate the dispenser.

[0212] Meanwhile, in the aforementioned TLS handshake, mobility authentication may be required and dispenser authentication may be optional, in which case the dispenser may act as a client and the mobility may act as a server.

[0213] For TLS handshakes, the mobility and dispenser must prepare the necessary credentials. They can store the certificate chain, the corresponding private key, and the trust anchor certificate in a secure repository that protects them from unauthorized access.

[0214] During the TLS handshake, the mobility can request client authentication from the dispenser by sending a predefined CertificateRequest message. Upon receiving the CertificateRequest message, the dispenser can then send the certificate and CertificateVerify messages to the mobility to transmit the certificate.

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

[0216] According to another embodiment of the present invention, the purpose, prerequisites, and subsequent conditions of step (S402) can be illustrated by the following Table 4.

[0217] TypeDescriptionUse case nameUC-2: "Communication Security"Objectives / Vehicle and Dispenser establish a secure channel over the discovered communication channel to achieve communication security goals including confidentiality, integrity, and privacy.Short DescriptionAfter the physical and data-link layer connection is made between vehicle and dispenser, they setup layer-3 and establish a TCP connection, then perform a TLS handshake to authenticate and exchange keys to establish a secure communication channel.Pre-conditionsVehicle and dispenser performed discovery and pairing use case successfully and made a data-link layer connection. Credentials necessary for the authentication and key exchange are prepared.Post-conditionsDispenser authenticated the vehicle and the vehicle authenticated dispenser successfully. Communication channel between vehicle and dispenser are encrypted and integrity protected.

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

[0219] Referring to FIG. 11, the step of negotiating a communication protocol (S403) may include a step of transmitting a message including information on a first communication protocol applicable to mobility to the dispenser (S1110); and a step of receiving a message including information on a second communication protocol selected from among common communication protocols applicable between mobility and the dispenser from the dispenser (S1130).

[0220] Referring to the embodiment of FIG. 11, the dispenser may receive a message from the mobility including information on a first communication protocol applicable to the mobility (S1110), compare the first communication protocol with a communication protocol applicable to the dispenser, select a second communication protocol among common communication protocols applicable between the mobility and the dispenser, and transmit a message including information on the selected second communication protocol to the mobility (S1130).

[0221] Although not shown in FIG. 11 at this time, a step may further be included before step (S1110) in which the dispenser requests the mobility for information including a list of first communication protocols applicable to the mobility.

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

[0223] This may further include a step where the mobility requests the dispenser for information including a list of applicable communication protocols.

[0224] According to one embodiment of the present invention, the purpose, prerequisites, and subsequent conditions of step (S403) can be illustrated by the following Table 5.

[0225] TypeDescriptionUse case nameUC-3: "Communication Protocol Negotiation"ObjectivesVehicle and Dispenser determine which communication protocol to use throughout the fueling.Short DescriptionOnce TLS handshake is successfully finished, the vehicle and the dispenser negotiates on the communication protocol to use throughout the fueling session. The negotiation starts when the vehicle sends a list of its supported protocols and then the dispenser picks a common protocol supported by both and the vehicle prefers the most.Pre-conditionsA secure authenticated communication channel is established using TLS 1.3.Post-conditionsThe vehicle and the dispenser reached an agreement on which communication protocol to use for their fuelling communication.

[0226] According to one embodiment of the present invention, the contents of the message transmitted and received in step (S1110) can be illustrated by the following Table 6.

[0227] Element NameTypeSemanticsprotocolsCommProtocolTypeCommunication protocols supported by the vehicleCommProtocolTypeIndexUnsigned integerIndex of the protocolNameStringName of the protocolVerStringVersion of the protocolprefUnsigned integerPreference of protocols. Smaller number represents higher preference.

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

[0229] According to one embodiment of the present invention, the contents of the response message transmitted and received in step (S1130) can be illustrated by the following Table 7.

[0230] Element NameTypeSemanticsIndexUnsigned integerOptional:Index of chosen protocolResultresultTypeResult of the protocol negotiation. 'OK' if successful. 'FAILED_INCOMPAT' otherwise.

[0231] A response message containing information about the second communication protocol may further contain information on whether the communication protocol negotiation was successful or not.

[0232] The aforementioned 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 on a compatible communication channel. Specifically, in this embodiment, the dispenser takes the lead in exchanging communication protocols and parameters with the vehicle.

[0233] That is, the communication method according to one embodiment of the present invention can perform the step (S401) of performing the discovery and pairing process with the dispenser using the first communication technology.

[0234] If the result of the communication protocol negotiation step (S403) is related to the second communication technology, the step of negotiating the fuel supply protocol (S404) and the step of negotiating the fuel supply parameters (S405) described later can be performed using the second communication technology.

[0235] In step S401 of performing the discovery and pairing process, information on interoperability and / or compatibility between the mobility and the dispenser can be shared.

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

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

[0238] In reality, mobility and dispensers at each site can have various combinations based on hydrogen fueling communication-related standards, communication modes, fueling methods, communication levels, and other parameters. Here, hydrogen fueling communication-related standards can include SAE J2601 series, ISO 19885-3, ISO 19885-4, etc. Communication modes can include No comm., IrDA, XYZ (ISO), etc. Fueling methods can include table-based fueling methods such as lookup tables, MC formula-based fueling methods, etc. Communication levels can include UCDC levels, and other parameters can include pressure classes, CHSS (compressed hydrogen storage system) categories, and hydrogen fueling tables.

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

[0240] Additionally, in various possible combinations of environments, if incompatibilities are identified in the parameters exchanged during the negotiation procedures (UC3 to UC5) for hydrogen fuel supply, the mobility and dispenser can return to the communication protocol negotiation procedure and perform the negotiation procedures again.

[0241] In one embodiment of the present invention, the prioritized communication protocols may include protocols having priorities as exemplified in Table 6 described below.

[0242] The dispenser will accept a specific protocol selected from the protocol list (<selected protocol> ) can be transmitted to the mobility (S1130). The specific protocol may be a common protocol selected by the dispenser, supported by both the dispenser and the mobility, and having the highest priority preferred by the mobility, such as the ISO 19885-3-2023-UCDC-3 protocol (see Table 6).

[0243] A common protocol allows mobility and dispensers to reach agreement on the communication protocol to use for fueling communication.

[0244] Meanwhile, mobility can prioritize the communication protocols it supports. Mobility can then provide the prioritized communication protocols to the dispenser. An example of the prioritized communication protocols is shown in Table 8 below.

[0245] Protocol IDPrioritySAE J2601 - No comm.7SAE J2799 - IrDA6SAE J2601 - IrDA5ISO 19885-3-2023-UCDC-04ISO 19885-3-2023-UCDC-13ISO 19885-3-2023-UCDC-22ISO 19885-3-2023-UCDC-31

[0246] Once a communication protocol is selected in the aforementioned communication protocol negotiation use case (UC3), the vehicle and dispenser can activate their respective communication protocol implementations and initiate fueling protocol negotiation. Fueling protocol negotiation is the process by which the vehicle and dispenser discover and agree on a fueling protocol to use for the fueling session. During this step, the vehicle and dispenser can select the communication protocol most preferred by the vehicle among the protocols supported by both.

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

[0248] The communication entity associated with the dispenser (200) may be an electronic control device (210) of the dispenser (200), a separate communication device mounted on the dispenser (200), or an electronic control device or separate communication device within the charging station system (200) may communicate with the vehicle / mobility (100) on behalf of the dispenser (200).

[0249] The first message may include priority information based on the preference of mobility (100), as illustrated in Table 6. Additionally, each message may be defined based on Tables 4 to 6.

[0250] At this time, the response message may include a second communication protocol selected from at least one first communication protocol based on priority information based on preference. The mobility (100) side or the dispenser (200) side may select the second communication protocol based on priority information based on preference, either alone or in cooperation with each other. In addition, the act of finalizing the protocol negotiation process by sending an approval message to the other party may be primarily performed on the mobility (100) side, but may be modified to be performed on the dispenser (200) side. In this case, the dispenser (200) may first send a list of supported protocols, and the mobility (100) may then feed back the selected protocol.

[0251] The response message may include at least one first communication protocol and a second communication protocol selected from among common communication protocols common to the protocols supported by the dispenser (200).

[0252] The response message may include a second communication protocol determined according to the fallback device type based on interoperability and backward compatibility between the mobility (100) and the dispenser (200) among a plurality of first communication protocols required to execute the first fuel supply protocol by the control device of the dispenser (200).

[0253] At this time, according to one embodiment of the present invention, if a common communication protocol does not exist, the No comm. communication standard is selected as illustrated in FIGS. 7 to 9, and a hydrogen fueling protocol according to the No comm. communication standard is selected according to a predetermined rule so that hydrogen can be supplied. In this case, steps (S404) to (S405) described below may be simplified or omitted.

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

[0255] FIG. 12 is a flowchart illustrating a fuel supply protocol negotiation step (S404) among a hydrogen fuel supply communication two-way process according to one embodiment of the present invention.

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

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

[0258] The dispenser can select common fuel supply protocols among the fuel supply protocol applicable to the dispenser and the first fuel supply protocol as a hydrogen fuel supply protocol supporting the second communication protocol, and select the second fuel supply protocol from the selected common fuel supply protocols. In this case, the second fuel supply protocol can be selected based on interoperability and / or compatibility, and the second fuel supply protocol can be selected based on mobility or preferences set by the dispenser.

[0259] Referring to the embodiment of FIG. 12, the dispenser may receive a message from the mobility including information on a first fuel supply protocol applicable to the mobility (S1210), compare the first fuel supply protocol with a fuel supply protocol applicable to the dispenser, select a second fuel supply protocol among common fuel supply protocols applicable between the mobility and the dispenser, and transmit a message including information on the selected second fuel supply protocol to the mobility (S1130).

[0260] Although not shown in FIG. 12, a step may further be included before step (S1210) in which the dispenser requests the mobility for information including a list of first fuel supply protocols applicable to the mobility.

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

[0262] This may further include a step where the mobility requests information from the dispenser including a list of applicable fuel supply protocols.

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

[0264] TypeDescriptionUse case nameUC-4: "Fueling Protocol Negotiation"ObjectivesVehicle and Dispenser determine which fuelling protocol to use for the fuelling.Short DescriptionOnce communication protocol selection is done, the vehicle and the dispenser negotiates on the fuelling protocol to use for the fuelling. The negotiation starts when the vehicle sends a list of its supported protocols and then the dispenser picks a common protocol supported by both and the vehicle prefers the most.Pre-conditionsA communication protocol is selected.Post-conditionsThe vehicle and the dispenser reached an agreement on which fuelling protocol to use for their fuelling.

[0265] 본 발명의 일 실시예에 따르면, 단계(S1210)에서 전송 및 수신되는 메시지의 내용은 다음의 표 10에 의하여 도시될 수 있다.

[0266] Element NameTypeSemanticsfuelProtsFuellingProtocolTypeFuelling protocols supported by the vehicleFuellingProtocolTypeidxUnsigned integerIndex of the protocolNameStringName of the protocolVerStringVersion of the protocolsubprotStringOptional: Name of the sub-protocolprefUnsigned integerPreference of protocols. Smaller number represents higher preference.

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

[0268] According to one embodiment of the present invention, the contents of the response message transmitted and received in step (S1230) can be illustrated by the following Table 11.

[0269] Element NameTypeSemanticsIndexUnsigned integerOptional:Index of chosen protocolResultEnumerationResult of the protocol negotiation. 'OK' if successful. 'FAILED_INCOMPAT' otherwise.

[0270] A message containing information about a second fuel supply protocol may further contain information about whether the fuel supply protocol negotiation was successful or not.

[0271] The contents of the message transmitted in step (S1210) according to one embodiment of the present invention can be represented as shown in Table 12 below.

[0272] IndexNameRevisionSub-protocolPreference1PRHYDE2023TYPE3-T-initial42PRHYDE2024TYPE3-T-Special33RTR-HFP24ANN-MPC55HMC-FAST1.01

[0273] As shown in Table 12, mobility can provide the dispenser with parameter information in the form of a table, including an arbitrarily assigned name for the supported fuel supply method or fuel supply protocol, information on the revision date (year) or version, information on whether a sub-protocol is available, and preference information.

[0274] In another embodiment of the present invention, the dispenser can proactively exchange its own communication protocol and parameters with the mobility on behalf of the mobility, and can also provide the mobility with priority given to communication protocols supported by the dispenser.

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

[0276] An example of a message transmitted in step (S1230) according to one embodiment of the present invention is shown in Tables 13 and 14 below.

[0277] Fueling Protocol IDResultCode2OK

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

[0279] Fueling Protocol IDResultCodeFAIL_NO_COMMON_PROTOCOL

[0280] According to Table 14, if the dispenser fails to find a compatible protocol in the list of fueling protocols supported by the mobility received from the mobility, the dispenser may transmit a response message to the mobility containing information indicating that there is no common protocol (e.g., FAIL_NO_COMMON_PROTOCOL) in the ResultCode field.

[0281] The examples in Tables 13 and 14 can be similarly applied to the case where the dispenser responds with mobility by selecting a second communication protocol among the common communication protocols in step (S1130) of FIG. 11.

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

[0283] The fuel supply parameter exchange / negotiation step (S405) may include a step in which the mobility and the dispenser exchange detailed parameters necessary for executing the fueling protocol.

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

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

[0286] Mobility transmits a message containing information about fuel supply parameters on the mobility side in step (S1310), and includes an Accepted field for the parameters. <pending>It can be sent to the dispenser with the setting set to .

[0287] Likewise, the dispenser transmits a message containing information about the fuel supply parameters on the dispenser side in step (S1330), and includes an Accepted field for those parameters. <pending>It can be transmitted to mobility with the setting set to .

[0288] Mobility transmits a message containing information about fuel supply parameters on the dispenser side as a response message to the message received in step (S1330), and includes an Accepted field for the corresponding parameters. <ok>or <true>It can respond to the dispenser by setting it to (S1350).

[0289] The dispenser transmits a message containing information about fuel supply parameters on the mobility side as a response message to the message received in step (S1310), and includes an Accepted field for the corresponding parameters. <ok>or <true>It can respond with mobility by setting it to (S1370).

[0290] At this time, the mobility and dispenser can respond by indicating whether each of the fuel supply parameters is accepted. The Accepted field of the parameters that are not agreed upon is <false>can be displayed as

[0291] Mobility and dispensers can reach agreement on all parameters by repeatedly sending and receiving messages and responding to those messages.

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

[0293] Here, the compatibility support related parameters include pressure class, CHSS category, etc., the physical characteristic parameters include maximum allowable CHSS pressure, maximum allowable CHSS temperature, maximum allowable speed, CHSS volume, etc., the monitoring parameters include current CHSS pressure, current CHSS temperature, etc., and the acceptance related parameters may include information indicating whether it is accepted or not, such as a parameter indicating yes (true) or no (false). The above-mentioned parameters may each be set with information about one of the pre-specified levels or set values ​​and information about different or identical main UCDC levels.

[0294] Meanwhile, the dispenser supports the following parameters:<DIS's parameters> )(briefly<DIS's params> ) can transmit an OK message indicating that the information about the mobility and the parameters of the mobility have been received and accepted to the mobility (S1330, S1370).

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

[0296] Here, the compatibility support related parameters include fueling delivery temp., selected fueling table, etc., the physical characteristic parameters include maximum fuel delivery pressure, maximum fuel delivery temperature, minimum fuel delivery temperature, maximum fuel delivery speed, etc., the fueling target related parameters include target SOC, target final CHSS pressure, target final CHSS temperature, target APR, expected fueling duration, etc., the monitoring parameters include current fuel delivery temperature, ambient temperature, etc., and the acceptance related parameters may include parameters such as accepted, etc. The above-mentioned parameters may each be set with information on one of preset levels or set values ​​and information on different or identical main UCDC levels.

[0297] In this way, mobility can provide the dispenser with parameters listed in a table format. The listed parameters include FCEV parameters compatible with the UCDC level negotiated during the fueling protocol negotiation phase.

[0298] As mentioned above, once a communication link is established and the communication and fueling protocols are selected during the protocol negotiation phase, the vehicle and dispenser can exchange various parameters to determine whether they can execute a compatible fueling procedure. Information necessary for performing a safe and efficient fueling procedure may include compatibility parameters, physical characteristics, fueling targets, and monitoring parameters.

[0299] Compatibility parameters may include, for example, pressure rating, fuel delivery transfer temperature, etc., physical characteristics 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.

[0300] If compatible parameters cannot be found and fuel delivery cannot proceed, the FCEV may return to the communication protocol negotiation phase to attempt negotiation of a different protocol or to stop fuel delivery to the dispenser. Furthermore, in the reverting communication protocol negotiation phase due to a failure in the fuel delivery parameter exchange phase, the FCEV may be configured to propose a set of supported protocols to the dispenser, excluding the protocol that failed in the fuel delivery parameter exchange phase.

[0301] Once the fueling protocol is negotiated through the aforementioned use case (UC-4), the vehicle and dispenser can negotiate specific parameters for the fueling protocol, communicate static or dynamic states, and exchange detailed fueling parameters to determine fueling targets. If the fueling parameter negotiation fails due to incompatibility, the system can return to UC-3 to select a different fueling protocol or to UC-1 to select a different communication protocol. If these fail, the current communication can be terminated.

[0302] According to the aforementioned configuration, some fueling protocols can be implemented on a non-communicative basis. Unidirectional IrDA may be required for some fueling protocols. Bidirectional communication may be required for some fueling protocols. Both bidirectional communication and unidirectional IrDA may be required for some fueling protocols.

[0303] 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 or type of the hydrogen fuel cell vehicle and the type or type of the dispenser. The proposed fueling protocols may be proposed with different priorities. While considering the priorities of the proposed fueling protocols, the communication protocol and fueling protocol between the hydrogen fuel cell vehicle and the dispenser may be ultimately determined based on whether the communication protocol required by the fueling protocol is supported by the hydrogen fuel cell vehicle and / or the dispenser.

[0304] In another embodiment of the present invention, either the mobility or the dispenser may first transmit fuel supply parameters to the other party, and the other party may respond with a message including newly reconfigured fuel supply parameters by maintaining parameters that it accepts among the received fuel supply parameters and changing parameters that it does not accept.

[0305] In another embodiment of the present invention, the mobility and dispenser may perform parameter negotiation in a step-by-step manner. The mobility and dispenser may first negotiate some parameters, and then exchange / negotiate subparameters of the parameters for which agreement has been reached.

[0306] In another embodiment of the present invention, each message including fuel supply parameters may be configured to be considered as not reaching an agreement if no response message is received within a preset message processing time.

[0307] Table 15 below shows the contents of a message including fuel supply parameters on the mobility side according to one embodiment of the present invention.

[0308] NameUnitPrecisionRange / ValuesTypeSemanticsPressure ClassN / AN / A{H35, H70}StaticPressure classof the tankCHSS VolumeLiter2 decimalsPositive, No-maxStaticVolumeof the tankCHSS PressureMPa2 decimalsPositive, No-maxDynamicCurrent pressureof the tankEmergency PolicyN / AN / A{Terminate,Fallback}StaticEmergency handling policy

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

[0310] NameUnitPrecisionRange / ValuesTypeSemanticsFueling Delivery TemperatureN / AN / A{H35, H70}Static...FuelingTemperatureMPa2 decimalsPositive, No-maxDynamicCurrent pressureof the tankEmergency PolicyN / AN / A{Terminate,Fallback}StaticEmergency handling policy

[0311] In the fuel supply parameter negotiation step (S405), the mobility and the dispenser can generate a message with range / values ​​for the supportable parameters (fueling parameters) and transmit it to the other party.

[0312] Parameters may include physical characteristic related parameters (simply 'physical parameters'), monitoring parameters, safety policy related parameters, acceptance related parameters, etc.

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

[0314] Parameters related to fuel supply parameter negotiation may include physical characteristic related parameters (hereinafter referred to as 'physical parameters'), monitoring parameters, fuel supply target related parameters, safety policy related parameters, and acceptance related parameters.

[0315] Here, the physical parameters include fueling 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 fueling target related parameters include selected fueling table, target SOC, target final CHSS pressure, target final CHSS temperature, target APR, expected fueling time, etc., and the acceptance related parameters may include parameters such as accepted, etc. The above-mentioned parameters may each be set with information on one of preset levels or set values ​​and information on different or identical main UCDC levels.

[0316] In this way, the FCEV can provide the dispenser with parameters listed in a table format. The listed parameters include FCEV parameters compatible with the UCDC level negotiated during the fueling protocol negotiation phase.

[0317] Meanwhile, if the received fuel supply parameters are compatible with the dispenser after receiving the fuel supply parameter negotiation request message, the dispenser can respond with its own fuel supply parameters by sending a fuel supply parameter negotiation response message with the “result” set to “OK” to the FCEV within a preset message response time.

[0318] Additionally, 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 may respond by sending a fuel supply parameter negotiation response message to the FCEV with the "result" set to "fail" to indicate the incompatibility with the FCEV in question. The result may indicate a value or information contained in the result code field, and the failure may be expressed as a failure at a specific time, such as "fail_incompat", indicating the incompatibility.

[0319] Additionally, if the FCEV finds that the fuel supply parameters of the dispenser are incompatible after receiving the fuel supply parameter negotiation request message, the FCEV may indicate the incompatibility to the dispenser by sending an error notification request message with a “reason” set to each predefined error code.

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

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

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

[0323] Referring to FIGS. 13 and 15 together, a method for exchanging fuel supply parameters over communication for hydrogen fuel supply according to an embodiment of the present invention is a method for exchanging fuel supply parameters over communication for hydrogen fuel supply performed by a communication control device of hydrogen fuel mobility (100), comprising: a step (S1310) of transmitting a first parameter including at least one or more first hydrogen fuel supply method compatibility supported by the mobility (100) and at least one or more first physical characteristics to a communication entity associated with a dispenser (200); and a step (S1370) of receiving a response message including a second parameter including at least one or more second hydrogen fuel supply method compatibility supported by the dispenser (200), at least one or more second physical characteristics, and a fueling goal from the communication entity associated with the dispenser (200).

[0324] The communication entity associated with the dispenser (200) may be an electronic control device (210) of the dispenser (200), a separate communication device mounted on the dispenser (200), or an electronic control device or separate communication device within the charging station system (200) may communicate with the vehicle / mobility (100) on behalf of the dispenser (200).

[0325] At this time, the first parameter may further include a first monitoring parameter supported by the mobility (100). The second parameter may further include a second monitoring parameter supported by the dispenser (200).

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

[0327] In a method for exchanging parameters over communication for hydrogen fuel supply according to one embodiment of the present invention, at least one first hydrogen fuel supply method compatibility may include at least one of a pressure class of mobility (100) and a fuel supply tank category (CHSS Category).

[0328] In a method for exchanging parameters over communication for hydrogen fuel supply according to one embodiment of the present invention, at least one first physical characteristic may include at least one of a maximum allowed CHSS pressure, a maximum allowed CHSS temperature, a maximum allowed flow rate, and a CHSS volume.

[0329] In a method for exchanging parameters over communication for hydrogen fuel supply according to one embodiment of the present invention, the first parameter may further include parameters related to acceptance of mobility (100).

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

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

[0332] In a method for exchanging parameters over communication for hydrogen fuel supply according to one embodiment of the present invention, at least one second physical characteristic may include at least one of a maximum fuel delivery pressure (Max Fuel Delivery Pressure), a maximum fuel delivery temperature (Max Fuel Delivery Temperature), a minimum fuel delivery temperature (Min Fuel Delivery Temperature), and a maximum fuel delivery flow rate (Max Fuel Delivery Flow Rate).

[0333] In a method for exchanging parameters over communication for hydrogen fuel supply according to one embodiment of the present invention, the fuel supply target may include at least one of a target SoC, a target final fuel supply tank pressure, a target final CHSS temperature, a target average fuel supply rate (APR), and an expected fuel supply time.

[0334] In a method for exchanging parameters over communication for hydrogen fuel supply according to one embodiment of the present invention, the second parameter may further include parameters related to acceptance of the dispenser (200).

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

[0336] Mobility (100) can provide first parameters compatible with the UCDC level negotiated during the protocol negotiation process in the form of a table at step (S1310).

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

[0338] If the mobility (100) or the dispenser (200) does not accept the exchanged parameters, the mobility (100) may re-perform the protocol negotiation process. Alternatively, if the mobility (100) or the dispenser (200) does not accept the exchanged parameters, the mobility (100) may terminate the fueling session.

[0339] In a protocol negotiation process that is re-performed due to a failed parameter exchange process in which the mobility (100) or dispenser (200) does not accept the exchanged parameters, the mobility (100) may propose a set of supported protocols other than the protocols provided in the failed parameter exchange process.

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

[0341] Physical ParametersReceptacle Type?Pressure ClassH35 / H70CHSS CategoryA / B / C / DCHSS Type1 / 2 / 3 / 4CHSS Volume? LMaximum allowed CHSS Pressure? MPaMaximum allowed BHSS temp.? ℃Maximum allowed flow rate? g / sMonitoring ParametersCurrent CHSS Pressure? MPaCurrent CHSS Temp.? ℃Safety PolicyEmergency Policy?Safety Enforcement Level?AcceptanceAcceptedTRUE / FALSE / PENDING

[0342] Table 18 illustrates the contents of a message including fuel supply parameters on the dispenser side according to another embodiment of the present invention.

[0343] Physical ParametersFueling Delivery temp.T30Max Fuel Delivery Pressure? MPaMax Fuel Delivery Temp.? ℃Min Fuel Delivery Temp.? ℃Mas Fuel Delivery Flow Rate? g / sMonitoring ParametersCurrent Fuel Delivery Temp.? ℃Ambient Temperature? ℃Fueling GoalSelected Fueling TableD1Target SoC? %Target Final CHSS Pressure? MPaTarget Final CHSS Temperature? ℃Target APR? MPa / sExpected Fueling Duration? ℃Safety Policy? sAcceptanceAcceptedTRUE / FALSE / PENDING

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

[0345] At this time, in the communication method according to one embodiment of the present invention, the renegotiation step may be performed again at steps (S403), (S404), and (S405). For example, the process may return to step (S403), perform renegotiation from step (S403), and then sequentially perform steps (S404) and (S405) again. In another embodiment, the process may return to step (S404), perform renegotiation from step (S404), and then sequentially perform step (S405) again.

[0346] In another embodiment of the communication method of the present invention, the renegotiation step may simplify steps (S403), (S404), and (S405) or omit some of the steps. Alternatively, steps (S403) and (S404) may be combined to negotiate the communication protocol and the fuel supply protocol together. For example, based on the compatibility and / or interoperability information identified in the preceding step (S401), the communication protocol and the fuel supply protocol may be negotiated together based on a protocol list that includes both the communication protocol and the fuel supply protocol, based on whether the communication protocol and the fuel supply protocol are mutually supported.

[0347] In a communication method according to another embodiment of the present invention, the renegotiation step may be performed based on a list of communication protocols and fuel supply protocols other than the communication protocol or fuel supply protocol selected in the previous step (S403) and step (S404).

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

[0349] For example, if communication between the mobility and the dispenser is impossible due to changes in the communication environment, the dispenser can fall back to No Communication and supply hydrogen using a hydrogen fueling protocol based on No Communication.

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

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

[0352] At the safety check-in stage (S406), the mobility and dispenser, including the mobility, can verify that all necessary safety conditions are met before the actual fuel supply begins.

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

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

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

[0356] Mobility and the dispenser can exchange messages for coupler checks. Mobility can send a message containing information indicating the results of its own coupler check (e.g., Mobility: OK) to the dispenser, and the dispenser can send a message containing information indicating the results of its own coupler check (e.g., DP: OK) to Mobility.

[0357] Additionally, the mobility and the dispenser can exchange messages related to gas leak checks. During the exchange of leak check-related messages, the dispenser can send information indicating that the leak check is in progress (ongoing) to the mobility. Furthermore, the mobility can send information indicating that it is waiting for the results of the leak check (waiting) to the dispenser. Once the leak check is complete, the dispenser can send a message requesting the measured tank volume to the mobility, along with information indicating that the leak check is complete (Done).

[0358] Additionally, the dispenser can send a message to the mobility for an immobilized status check, and the mobility can send a message to the dispenser indicating that it is ready for a status check.

[0359] In this way, when the mobility reports parameters about the current state or immobilization status of the mobility to the dispenser, the dispenser can report parameters about the coupler lock status, leak check status, predicted mobility tank capacity, etc. to the mobility.

[0360] Once the aforementioned safety check-in step (S406) is completed, fueling can begin. During fueling, the mobility and dispenser can exchange information to monitor various status parameters to ensure safe and efficient fueling. If necessary, either the mobility or dispenser can send control messages to control the fueling step (S406) or request action from the other party to address safety-related conditions. The parameters and commands to be exchanged may vary depending on the actual fueling protocol.

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

[0362] In the monitoring and control step (S407), the mobility and / or dispenser, including the mobility, can monitor the fuel supply status and control the fuel supply as necessary. Once all safety checks are confirmed, the mobility and dispenser can begin supplying fuel according to the selected fuel supply protocol using the given parameters. During the fuel supply, the mobility and dispenser can exchange various measurement data to determine the fuel supply status and operate to detect safety-critical incidents as quickly as possible.

[0363] Additionally, the mobility can transmit specific commands to the dispenser to control the fuel supply phase (S407), such as starting and ending fuel supply. At this time, the mobility can use UDP with DTLS for communication to support black-channel communication. Black-channel communication refers to communication that applies the black-channel principle, which ensures secure communication despite the output characteristics of the communication channel having unsecured or application-unrelated properties.

[0364] To explain the monitoring and control step (S407) in more detail, for example, the mobility including the mobility can transmit a message to the dispenser to start fueling control, and in response, the dispenser can transmit a message including confirmation information (e.g., OK) to the mobility.

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

[0366] Additionally, the mobility may transmit a fueling control request message to the dispenser that includes information to slow down or reduce the amount of fuel supplied, and the dispenser may transmit a response message to the mobility that includes information indicating a decrease in the fueling status (e.g., slowing).

[0367] Additionally, the mobility can transmit a fuel supply control request message requesting a stop of fuel supply to the dispenser, and the dispenser can transmit a fuel supply status response message including information on stopping or stopping fuel supply (stopping / stopped) to the mobility.

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

[0369] Request messages related to control transmitted from the mobility to the dispenser may include information or parameters related to starting, pausing, resuming, and terminating fuel supply. Additionally, messages related to reporting transmitted from the mobility to the dispenser may include information or parameters related to current tank temperature, current tank pressure, and the like.

[0370] Messages related to reporting transmitted from the dispenser to the mobility may include information or parameters such as status information, current ambient temperature, current pressure ramp rate (PRR [Mbar / min]), deliver fuel flow rate (g / sec]), current fuel delivery temperature, pre-cooling temperature, current fuel delivery pressure, whether in use before full charge (full charge), whether in use of a cooled dispenser, whether in use of a fallback, reason for fueling stop, and current amount of hydrogen delivered.

[0371] Additionally, messages related to target parameter updates transmitted from the dispenser to the mobility may include information or parameters regarding target final tank pressure, target final tank temperature, target fuel supply APR, target SOC, current SOC, estimated remaining duration, etc.

[0372] Meanwhile, when TCP is used in the aforementioned monitoring and control step (S407), if the safety check-in response message or the safety check-in step by the fuel supply protocol is omitted, the mobility may transmit a fueling loop request message to the dispenser within a message sequence setting time after receiving a fueling parameter negotiation response message from the dispenser. The request message or response message related to the fueling loop may be transmitted as a DTLS message.

[0373] After completing the hydrogen fueling process through the aforementioned monitoring and control step (S407), and before terminating the session and disconnecting the nozzle from the mobility, the mobility and dispenser, including the mobility, can verify that the quantity and dispenser each meet all safety requirements through a safety check-out use case. While this safety check-out step is optional, it is recommended to define a dedicated safety check step (S407) in the fueling protocol to ensure the desired safety level in a precise and explicit manner.

[0374] A safety check-out step (S408) applicable to a two-way hydrogen fueling communication process according to one embodiment of the present invention may be performed as follows. The mobility and dispenser, including the mobility, can verify, through the safety check-out step (S408), that all necessary safety conditions have been met before disconnecting the nozzle of the dispenser from the outlet. In other words, the mobility and dispenser can verify that it is absolutely safe for a user or operator to disconnect the nozzle from the mobility after fueling is complete.

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

[0376] The mobility and dispenser can repeatedly report their status to each other until all safety checks are completed. If the two-way hydrogen fueling communication process does not require this final safety check, the use case for safety checkout can be omitted.

[0377] For example, to explain the aforementioned safe checkout step (S408) in more detail, the mobility can transmit a message containing information about the result of the coupler check (e.g., OK) to the dispenser, and the dispenser can transmit a message containing information indicating that the coupler check is in progress (e.g., Ongoing) to the mobility.

[0378] Additionally, the mobility can transmit a message containing coupler inspection result information (e.g., OK) back to the dispenser, and the dispenser can transmit a message containing coupler inspection completion information (e.g., Done) to the mobility.

[0379] When the above-described coupler inspection completion information is confirmed to have been completed normally, the nozzle of the dispenser can be separated from the receptacle of the mobility by the user or operator.

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

[0381] When fueling is completed and the nozzle is safely disconnected according to the hydrogen fueling protocol described above, or when a non-safety-critical issue occurs during another use case, the termination use case (UC9) can be performed.

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

[0383] The termination step (S409) is the final step of the fueling process. The mobility system and the dispenser, including the mobility system, exchange information about the fueling results, including fueling performance and methods, and / or the reason for any unexpected fueling interruption, thereby completing all steps (S409) of the hydrogen fueling process. The termination use case can also be configured to handle tasks related to non-safety-critical issues that may arise.

[0384] For example, after the mobility receives a safe checkout response message from the dispenser with the "result" set to "DONE", or a fuel supply loop response message with the "status" set to "finished" or the prefix "stopped", the mobility may perform the termination step (S409) by sending a termination request message to the dispenser.

[0385] For example, in more detail regarding the termination step (S409), the mobility including the mobility can transmit a message to the dispenser inquiring about how much fuel has been supplied. The dispenser can transmit a response message including information about the amount of hydrogen supplied (e.g., X grams) to the mobility in response to the query message from the mobility.

[0386] Additionally, the mobility can transmit a confirmation request message for the completion of fuel supply to the dispenser, and the dispenser can transmit a goodbye message to the mobility as a response message to the confirmation request message.

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

[0388] The book-keeping information may include all information related to hydrogen fueling recorded in the mobility or dispenser according to preset rules or policies throughout all fueling sessions for hydrogen fueling and prior to completing the termination step (S409) of use case 9 (UC9).

[0389] The ledger information or summary information may include information such as how much fuel was dispensed, what reports were generated, etc. Additionally, the reporting message transmitted from the mobility to the dispenser may include information or parameters regarding the current tank temperature and current tank pressure, and the reporting message transmitted from the dispenser to the mobility may include information regarding the final SOC, the final average fueling rate (APR), the final measured tank pressure, the actual fueling time, and the actual amount of hydrogen fueled.

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

[0391] An example of communication data for some of the use cases described above (UC5 to UC9) is shown in Table 19 below.

[0392] UC classificationCharging station → vehicleVehicle → charging stationFueling ParameterNegotiationCheck communication transmissionFuel supply protocolHydrogen supply (cooling) temperature targetFuel supply pressure targetExpected (expected) tank temperature after fuel supplyTarget fuel supply volume (SOC %)Target fuel supply timeStandby temperatureCheck communication transmissionMaximum operating pressureMaximum operating temperatureMaximum operating flowTank temperatureTank pressureTank volumeVehicle fuel supply pressure (350 / 700, etc.)Safety Check-inNozzle-receptacle connectionHydrogen storage system leak check resultCharging station predicted vehicle tank volume (check usage map suitability)Tank temperatureTank pressureTank volumeMonitoring and ControlHydrogen supply (cooling) temperature targetFuel supply pressure targetExpected (expected) tank temperature after fuel supplyTarget fuel supply volume (SOC %)Standby temperatureTarget fuel supply speedActual fuel supply speedTarget fuel supply timeActual fuel supply timeFuel supply flowFuel supply status (start / fueling / stop / pause)Communication Status: Reason for fuel supply interruption (normal termination / low pressure at charging station / communication error) Only fuel supply (Top-off) Whether cold dispenser is used Whether fallback is in progress Tank temperature Tank pressure Tank volume Fuel supply interruption request Safety Check-out Whether nozzle-receptacle can be separated (separable / icing, etc.) Tank temperature Tank pressure Tank volume Termination Target fuel supply amount Actual fuel supply amount Target fuel supply speed Actual fuel supply speed Target fuel supply pressure Actual fuel supply pressure Target tank temperature Actual tank temperature Target fuel supply time Actual fuel supply time

[0393] Meanwhile, the error handling use case (UC10) is a function block for handling situations in which a non-critical error occurs, such as terminating the fuel supply procedure or suddenly stopping communication, similar to a normal shutdown.

[0394] An error handling step (S410) that can be employed in a hydrogen fuel supply communication two-way process according to one embodiment of the present invention can be performed as follows.

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

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

[0397] If a mobility detects an event indicating a non-safe critical error, the mobility may notify the dispenser of the reason for termination via a Terminate Request (TerminateReq) message and stop the current fueling or communication session. The dispenser may terminate the current communication session in response to the Terminate Request message. If further communication is not possible, the current session may be terminated without further notification.

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

[0399] The aforementioned termination request message may be sent in error situations of non-critical communication errors, system errors, and qualitative errors, except in cases where recovery is not possible.

[0400] In other words, for successful refueling, communication must exhibit expected behavior according to the protocol, and refueling behavior must fall within the acceptable range of the refueling protocol. However, in reality, various abnormal events can occur. Some errors are trivial and easily handled, while others are unrecoverable and prevent refueling from proceeding. Therefore, the error handling step (S410) defines non-safety-critical error conditions and provides exemplary error conditions and possible responses.

[0401] Examples of communication errors include a loss of communication, unrecognizable received data due to encoding or syntax errors, or data falling outside of acceptable ranges. System errors may include instances where the dispenser or mobility device detects a critical system error. Qualitative errors may include instances where the quality of communication performance does not meet requirements, or where the quality of data integrity or accuracy does not meet requirements.

[0402] The hydrogen fuel supply communication two-way process of the present embodiment can perform specific error handling steps (S410) such as the following (1) to (4) for the above-described error conditions.

[0403] (1) If a non-critical safety error occurs and further communication is no longer possible, the Mobility and Dispenser will immediately stop supplying fuel, but may take safe action and terminate the session by stopping communication.

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

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

[0406] (4) If a non-safety critical error is detected by the dispenser and the communication channel is still operational, the dispenser may first immediately stop fuel supply and send a termination request message to the mobility with “Action” set to “Stop” and “Reason” set to an appropriate reason or reason code.

[0407] As described above, the hydrogen fueling communication bidirectional process including the fueling protocol can define error conditions related to the fueling protocol, provide detection criteria, and perform an error handling step (S410) including a notification, a termination step (S410), and a fallback mechanism when an error is detected by the detection criteria.

[0408] Meanwhile, safety-critical issues may arise during fuel supply in a hydrogen fuel supply system, requiring an emergency response.

[0409] An emergency handling step (S411) that can be employed in a hydrogen fuel supply communication two-way process according to one embodiment of the present invention can be performed as follows.

[0410] The emergency handling step (S411) may define safety-critical conditions requiring emergency response during fuel supply and include response processes to prevent safety-critical accidents.

[0411] To ensure safe refueling, communication must behave as expected according to the protocol, and refueling operations must remain within the safe limits of the refueling protocol. However, there is a possibility that a problem may occur during refueling, potentially causing the refueling system (or hydrogen refueling system) to reach a critical state that must be avoided at all costs. Therefore, the emergency handling step (S411) can define safety-critical emergency conditions and possible responses to them, providing critical cases to consider.

[0412] A fueling protocol may define emergency conditions associated with the protocol, provide detection criteria and performance requirements, and prescribe response steps (S411) to ensure that hazardous conditions are not encountered.

[0413] Specifically, when a high pressure state exceeding a preset reference value is detected by the mobility during the hydrogen fuel supply step (S411), the mobility may transmit a first emergency stop request message including information requesting a stop of fuel supply due to the high pressure (e.g., Emg: Stop (high pressure)) to the dispenser. The dispenser may transmit a response message including information indicating that it is processing an emergency fuel supply stop (e.g., Emg: Stopping) to the mobility according to the first emergency stop request message.

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

[0415] Meanwhile, if a hydrogen fuel leak is detected by the dispenser during the hydrogen fuel supply step (S411), the dispenser may transmit a second emergency stop request message to the mobility, which includes information indicating that it is processing a fuel supply stop due to the leak (e.g., Emg: Stopping (leaking)). The mobility may transmit a response message to the dispenser, which includes information indicating that it has confirmed the second emergency stop request message (e.g., Emg: Confirmed).

[0416] Additionally, the dispenser may transmit a third emergency stop notification message to the mobility, which includes information indicating that it has processed a fuel supply stop due to a leak (e.g., Emg: Stopped (leaking)). The mobility may transmit a response message to the dispenser, which includes information indicating that it has confirmed the third emergency stop notification message (e.g., Emg: Confirmed).

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

[0418] Upon receiving an emergency notification message, the mobility or dispenser can immediately respond according to the action indicated in the emergency notification message and terminate the communication without undue delay. The emergency notification message includes a header and a message body connected to the header. The header includes information indicating that it is an emergency notification, and the message may include values, information, or parameters regarding the class, type, and action of the emergency notification.

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

[0420] Referring again to FIG. 4, the purpose, prerequisites, and subsequent conditions of the safety check-in step (S406) can be illustrated by the following Table 20.

[0421]

[0422] TypeDescriptionUse case nameUC-6: "Safety Check-in"ObjectivesVehicle and Dispenser confirms that all the necessary safety conditions are met and the communication link is correctly paired with the pairing channel before actual fuelling is started.Short DescriptionOnce fuelling parameters are exchanged and vehicle and dispenser are considered compatible, vehicle and dispenser performs safety condition checks and pairing checks to make sure the fuelling is safe and the communication is reliable. Depending on the fuelling protocol and the communication physical layer, the safety checks can be implicitly done within the protocol or physical association and this step may be omitted.Pre-conditionsNecessary fuelling parameters are exchanged.Post-conditionsThe vehicle and the dispenser confirmed all the safety conditions and correctness of the pairing, and ready to begin fuelling.

[0423] 연료공급 파라미터 협상 단계(S405)가 성공적으로 수행되면, 연료공급 프로토콜은 안전 체크인 단계 (S406)를 수행할 수 있음은 전술한 바와 같다.

[0424] If the communication physical layer is stipulated to require a pairing procedure at this time, the mobility and dispenser may recheck the pairing before dispensing hydrogen in the safety check-in step (S406).

[0425] Even if the communication physical layer is not specified to require a pairing procedure at this time, the mobility and dispenser may recheck the pairing before dispensing hydrogen in the safety check-in step (S406).

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

[0427] As an alternative embodiment, if a message indicating the completion of step (S405) is transmitted by one of the mobility and the dispenser to the other, that one or the other may transmit a message indicating the start of the safety check-in step (S406).

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

[0429] According to one embodiment of the present invention, the message transmitted and received in the safety check-in step (S406) may include a result value of processing the request message as a result element. The result value that may be provided as the result element may include, for example, 'OK' in the case of success, 'FAILED' in the case of failure, and 'PENDING' in other cases.

[0430] If all safety conditions are met when the mobility sends a SafetyCheckInReq message to the dispenser, the result value of that message can be set to "OK".

[0431] If some safety conditions are not yet met when the mobility sends a SafetyCheckInReq message to the dispenser, the result value of that message may be set to "PENDING".

[0432] After the dispenser receives the SafetyCheckInReq message, the dispenser can respond to the mobility with a SafetyCheckInRes message with safety-check parameters within the MessageResponseTimeout time period.

[0433] If all safety conditions are met when the dispenser sends a SafetyCheckInRes message to the mobility, the result value of that message can be set to "OK".

[0434] If some safety conditions have not yet been met when the dispenser sends a SafetyCheckInRes message to the mobility, the result value of that message may be set to "PENDING".

[0435] If a SafetyCheckInRes message with the result value set to "PENDING" is received, the mobility may send another SafetyCheckInReq message to the dispenser within the MessageResponseTimeout time interval.

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

[0437] When a mobility or dispenser cannot confirm all safety conditions within a given time (e.g. UCSafetyCheckInTimeout), it can send an ErrNotifReq message with the "reason" field set to an appropriate error code.

[0438] As an alternative embodiment, the mobility or dispenser may transmit a request message to the counterpart indicating the start of a safety check-in, and the counterpart may respond with a response message to the request message for a safety check-in within a predetermined time period.

[0439] Referring again to FIG. 4, the purpose, prerequisites, and subsequent conditions of the monitoring and control step (S407) can be illustrated by the following Table 21.

[0440]

[0441] TypeDescriptionUse case nameUC-7: "Fuelling control and monitoring"ObjectivesVehicle and Dispenser monitors the fuelling status and control the fuelling if necessary.Short DescriptionOnce all the safety checks are confirmed, the vehicle and dispenser starts the fuelling according to the chosen fuelling protocol with given parameters. During the fuelling, vehicle and dispenser exchange various measured data to understand the fuelling status and detect any safety-critical incidents as early as possible. Vehicle can also submit certain commands to dispenser to control the fuelling procedure, such as starting and ending the fuelling.To support black-channel communication, UDP with DTLS is used for the communication.Pre-conditionsAll the safety checks are confirmed and vehicle and dispenser are ready to fuel.Post-conditionsThe fuelling is finished successfully.

[0442] 안전 체크인 단계(S406)가 성공적으로 수행되면, 연료공급 프로토콜은 모니터링 및 제어 단계 (S407)를 수행할 수 있음은 전술한 바와 같다.

[0443] If the safety check-in step (S406) is omitted and the fuel supply parameter negotiation step (S405) is successfully performed, the fuel supply protocol can perform the monitoring and control step (S407).

[0444] While the monitoring and control step (S407) is being performed, the dispenser can perform all necessary steps to supply fuel to the mobility.

[0445] When the TCP specification is used in the fuel supply control and monitoring use case, the mobility may transmit a message (e.g., FuelLoopReq message) to the dispenser requesting the start of the monitoring and control phase (S407) within a predetermined time interval (e.g., MessageSequenceTimeout) after receiving the SafetyCheckInRes message or, in an embodiment where the safety check-in phase (S406) is omitted, after receiving the FuelParamNegoRes message.

[0446] In embodiments where the SafetyCheckInRes message is sent when the black channel described above is used or the safety check-in step (S406) is omitted, after sending the FuelParamNegoRes message, the mobility (as a client) and the dispenser (as a server) can initiate a DTLS 1.3 handshake following RFC 9147 with session resumption using NewSessionTicket. At this time, the NewSessinTicket can be received from the dispenser.

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

[0448] At this time, 0-RTT may not be used for DTLS session resumption.

[0449] Both the FuelLoopReq and its response messages (e.g., FuelLoopRes messages) can be transmitted following the DTLS message specification.

[0450] In addition, additional requirements may be added for the black channel method.

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

[0452] The fuel supply protocol may specify static or dynamic data to be included within FuelLoopReq and FuelLoopRes to monitor fuel supply status and exchange safety-related information.

[0453] The element names included in the FuelLoopReq message may include action, reason, etc., and may be illustrated by Table 22 below. Elements not illustrated in Table 22 below may be specified by each fuel supply protocol standard, such as ISO 19885-3, for example.

[0454] Element NameTypeSemanticsactionactionTypeOptional:Action that Vehicle requests to Dispenser.- start- stop- (Any custom actions defined by fuelling protocol)reasonreasonTypeOptional:Reason for why the "action" is requested.

[0455] The element names included in the message transmitted and received in step S407 (e.g., FuelLoopRes message) may include status, reason, result, etc., and may be illustrated by Table 23 below. Elements not illustrated in the contents of Table 23 below may be specified by each fuel supply protocol standard, such as ISO 19885-3, for example.

[0456] Element NameTypeSemanticstatusstatusTypeOptional: - preparing- precooling- fuelling- standby- faulted- ramping-up- ramping-down- stopping- finished- stopped_error- stopped_requested- stopped_unknown- (Any custom status codes defined by fuelling protocol)reasonreasonTypeOptional:Reason for stopping when the fuelling is stopped abnormallyresultresultTypeResult of processing the request message. 'OK' if successful. 'FAILED' otherwise. See Table XYZ for the list of result codes.

[0457] When a mobility sends a FuelLoopReq message, the dispenser can be expected to perform an action. The mobility can send the message with "action" set to the desired action code, which can be defined by the fueling protocol.

[0458] After receiving a FuelLoopReq message (e.g. with "action" set to "start"), if the dispenser is ready to start, the dispenser may initiate the fueling procedure using the negotiated method and respond with a FuelLoopRes message with "result" set to "OK".

[0459] After receiving a FuelLoopReq message (e.g. with "action" set to "start"), if the dispenser is not ready to start, the dispenser can respond with a FuelLoopRes message with "result" set to "pending".

[0460] After receiving a FuelLoopReq message (e.g. with "action" set to "stop"), if the dispenser is ready to stop, the dispenser may stop the fueling procedure as defined in the fueling protocol and respond with a FuelLoopRes message with "result" set to "ONGOING".

[0461] After receiving a FuelLoopReq message (e.g. with "action" set to "stop"), if the dispenser is ready to stop, the dispenser can immediately stop the fueling procedure and respond with a FuelLoopRes message with "result" set to "OK".

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

[0463] The dispenser can send a FuelLoopRes message with "result" set to "OK" if the received FuelLoopReq message was successfully processed.

[0464] The dispenser may send a FuelLoopRes message with "result" set to "FAILED" or another appropriate error code if the received FuelLoopReq message was not successfully processed.

[0465] The dispenser may send a FuelLoopRes message with "status" set to one of the supported codes specified in Table 23 or the fueling protocol.

[0466] The dispenser may send a FuelLoopRes message with "status" set to "finished" when fueling is complete (done) and the intended fueling goal has been achieved.

[0467] The dispenser may send a FuelLoopRes message with "status" set to "stop_error" and "reason" set to an appropriate reason code if fuel delivery is stopped for any error-related reason.

[0468] A dispenser may send a FuelLoopRes message with "status" set to "stopping" if the most recent FuelLoopReq message had "action" set to "stop" and fueling has not been completely stopped.

[0469] A dispenser may send a FuelLoopRes message with "status" set to "stopped_requested" if the most recent FuelLoopReq message had "action" set to "stop" and fueling has been completely stopped.

[0470] When a mobility sends a FuelLoopReq message with "action" set to "stop" and receives a FuelLoopRes message with "status" set to "stopping", the mobility may send a FuelLoopRes message with "action" set to "stop".

[0471] If a mobility receives a FuelLoopRes message and the fueling is not finished, the mobility can send a FuelLoopReq message within a predefined time interval (e.g., MessageSequenceTimeout).

[0472] If a safety critical event occurs, the mobility or dispenser can immediately send an EmergencyReq message, stop the fueling procedure, and close the communication.

[0473] While the above-described embodiment related to step S407 focuses on an embodiment in which the mobility requests the start of each step and the dispenser responds, the spirit of the present invention is not limited thereto. In an alternative embodiment of the present invention, either the mobility or the dispenser can first transmit a message requesting the start of step S407, and the other party can then respond to the message requesting the start of step S407, thereby performing step S407.

[0474] In step S407, the message transmitted by either the mobility or the dispenser may include a monitoring request regarding the status of the hydrogen fueling procedure. The response message sent by the other party may include status information regarding the requested monitoring target.

[0475] At this time, the states and related parameters that can be the target of the monitoring request may include the parameter set exchanged in step (S405). The states and related parameters that can be the target of the monitoring request may include the states and parameters of the mobility or dispenser. The states and related parameters that can be the target of the monitoring request may include the fuel supply states and / or related parameters of the mobility and / or dispenser that are changed or maintained by the hydrogen fuel supply procedure.

[0476] Additionally, the status that may be the subject of a monitoring request may include the status and / or information regarding the fueling procedure itself, which involves the fueling from the dispenser to the vehicle. For example, the fueling procedure may include information such as whether it is ongoing, paused, terminated, and / or, if stopped / terminated, whether it was stopped due to an error or finished due to the achievement of a goal.

[0477] Referring again to FIG. 4, the purpose, prerequisites, and subsequent conditions of the safe checkout step (S408) can be illustrated by the following Table 24.

[0478] TypeDescriptionUse case nameUC-8: "Safety Check-out"ObjectivesVehicle and Dispenser confirms that all the necessary safety conditions are met before the nozzle can be detached from the receptacleShort DescriptionAfter the fuelling has been finished, the vehicle and dispenser ensure that it is absolutely safe for the user or operator to unplug the nozzle from the vehicle. The vehicle and dispenser repeatedly report their condition until the safety checks are all. This use case may be omitted if the fueling protocol does not require such safety checks at the end.Pre-conditionsFuelling is finished.Post-conditionsIt is safe to unplug the nozzle from the receptacle.

[0479] After the fueling is finished, and before terminating the session and unplugging the nozzle from the vehicle, a safety checkout step (S408) may be performed to ensure that the vehicle and dispenser meet safety conditions. This step (S408) is optional, but it is strongly recommended that a dedicated safety checkout procedure be defined by the fueling protocol to ensure the desired safety level in a precise and explicit manner.

[0480] Information exchanged during the safety checkout process can be used to diagnose and determine accountability when a safety-related incident occurs.

[0481] As previously mentioned, once the monitoring and control step (S407) and the associated fuel supply procedure are successfully finished, the fuel supply protocol can perform the safety checkout step (S408).

[0482] Regardless of whether a safety checkout is performed, a fueling protocol compliant with ISO 19885-2 can define a set of safety conditions to be confirmed between the mobility and the dispenser before unplugging the nozzle.

[0483] After receiving a FuelLoopRes message with "Result" set to "OK" and "status" prefixed with "finished" or "stopped", if the fueling protocol supports safe checkout, the mobility may send a message (e.g. SafetyCheckOutReq) to the dispenser over the TLS channel, requesting the start of the safe checkout phase (S408) within a predefined time interval (e.g. MessageSequenceTimeout).

[0484] If the TCP / TLS channel is disconnected at this point, the mobility can re-establish the TCP / TLS channel with the dispenser. The re-establishment process can be initiated by a TLS-resumption handshake using the NewSessionTicket received before sending the SafetyCheckOutReq message.

[0485] As an alternative embodiment, a message requesting the start of step (S408) may be transmitted by either the mobility or the dispenser to the other party. In this case, the other party may perform step (S408) by responding to the message requesting the start of step (S408).

[0486] According to one embodiment of the present invention, the messages transmitted and received in the safe check-out step (S408) may be defined based on the contents of each fuel supply protocol specified in a standard such as ISO 19885-3, for example.

[0487] According to one embodiment of the present invention, the message transmitted and received in the secure checkout step (S408) may include a result value of processing the request message as a result type. In this case, the result value that may be provided as a result type may include, for example, 'OK' in case of success, 'FAILED' in case of failure, and 'PENDING' in other cases.

[0488] If the mobility confirms that all safety conditions are met when sending a SafetyCheckOutReq message to the dispenser, the result value of that message can be set to "OK".

[0489] If some safety conditions are not yet met when the mobility sends a SafetyCheckOutReq message to the dispenser, the result value of that message may be set to "PENDING".

[0490] After the dispenser receives the SafetyCheckOutReq message, the dispenser can respond to the mobility with a SafetyCheckOutRes message with safety-check parameters within the MessageResponseTimeout time period.

[0491] If the dispenser confirms that all safety conditions are met when sending a SafetyCheckOutRes message to the mobility, the result value of that message can be set to "OK".

[0492] If some safety conditions have not yet been met when the dispenser sends a SafetyCheckOutRes message to the mobility, the result value of that message may be set to "PENDING".

[0493] If a SafetyCheckOutRes message with the result value set to "PENDING" is received, the mobility may send another SafetyCheckOutReq message to the dispenser within the MessageResponseTimeout time interval.

[0494] If a SafetyCheckOutReq message with the result value set to "PENDING" is received, the dispenser may send another SafetyCheckOutReq message to the mobility within the MessageResponseTimeout time interval.

[0495] When a mobility or dispenser cannot confirm all safety conditions within a given time (e.g. UCSafetyCheckOutTimeout), it can send an ErrNotifReq message with the "reason" field set to an appropriate error code.

[0496] As an alternative embodiment, either the mobility or the dispenser can transmit a request message to the other party indicating the start of a safe checkout, and the other party can respond with a response message to the request message for safe checkout within a predetermined time period.

[0497] According to one embodiment of the present invention, in the monitoring and control step (S407), if a non-critical error is found and fuel supply is interrupted before the fuel supply is completed, the fuel supply protocol may define a fallback mechanism that ensures backward compatibility among the mutually compatible mechanisms between the mobility and the dispenser, and may resume and complete the fuel supply based on the fallback mechanism.

[0498] The fallback mechanism at this time may be, for example, a non-communication fueling method.

[0499] As an alternative embodiment, if a non-safety critical error is found in the monitoring and control step (S407) and fuel supply is interrupted before fuel supply is completed, the mobility and the dispenser may re-perform some or all of the communication protocol negotiation step (S403), the fuel supply protocol negotiation step (S404), and the fuel supply parameter negotiation step (S405).

[0500] As an alternative embodiment, the mobility and the dispenser may reduce the information exchanged in the process of re-performing some or all of the communication protocol negotiation step (S403), the fuel supply protocol negotiation step (S404), and the fuel supply parameter negotiation step (S405) by using the interoperability information obtained in the discovery and pairing step (S401). For example, if a communication state or fuel supply state is identified in which the previously negotiated and selected protocol cannot be maintained, some or all of the communication protocol negotiation step (S403), the fuel supply protocol negotiation step (S404), and the fuel supply parameter negotiation step (S405) may be re-performed excluding the previously selected protocol.

[0501] As an alternative embodiment, if a change in the communication environment and a change in the fuel supply infrastructure are detected as non-critical errors in the monitoring and control step (S407), and the fuel supply is interrupted before the fuel supply is completed, the mobility and the dispenser may re-perform some or all of the communication protocol negotiation step (S403), the fuel supply protocol negotiation step (S404), and the fuel supply parameter negotiation step (S405).

[0502] Changes in the communication environment may include instances where communication channels are disconnected.

[0503] Changes in the communication environment may include cases where received data is not recognized or cases where received data is in an unacceptable range.

[0504] Changes in the communications environment may include instances where the quality of communications performance does not meet the required level.

[0505] Changes in the communication environment may include cases where the integrity or precision of data exchanged through communication does not meet the required level.

[0506] Changes in the fuel supply infrastructure may include cases where fuel supply parameters on the mobility side change or maintain a state based on control parameters for fuel supply on the dispenser side, but the change or maintenance of the state of fuel supply-related parameters on the mobility side does not meet the required level.

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

[0508] Safety conditions may include elements related to the mobility for hydrogen fuel supply (fuel supply) and the safety of both sides of the hydrogen fuel supply device or dispenser and / or the fastening status of nozzles and receptacles on both sides for initiating hydrogen fuel supply.

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

[0510] On the hydrogen charging station side, this may include cylinder temperature, fuel supply pressure, and ambient temperature.

[0511] Safety conditions along the connection and fuel supply path on both sides may include the nozzle-receptacle mating status - i.e., whether mated, mating condition, leakage condition, etc.

[0512] The nozzle-receptacle engagement status may include information about whether the nozzle-receptacle engagement status is suitable and / or sufficient to perform a hydrogen fueling procedure.

[0513] In one alternative embodiment of FIG. 4, the safety check-in step (S406) may be executed prior to the fuel supply parameter negotiation step (S405) if the safety check-in step (S406) performs a minimum status check, i.e., a check of safety elements including whether the nozzle-receptacle is engaged, the engagement status, etc.

[0514] In one alternative embodiment of FIG. 4, when the safety check-in step (S406) performs a check of safety elements including a minimum status check, i.e., whether the nozzle-receptacle is engaged, the engagement status, etc., the remaining safety elements not checked in the safety check-in step (S406) can be negotiated and checked in the fuel supply parameter negotiation step (S405).

[0515] In one alternative embodiment of FIG. 4, when the safety check-in step (S406) performs a check of safety elements including a minimum status check, i.e., whether the nozzle-receptacle is engaged, the engagement status, etc., the remaining safety elements not checked in the safety check-in step (S406) can be monitored and checked in the monitoring and control step (S407). In this case, the safety elements can be monitored and checked in the monitoring and control step (S407) regardless of (or independently of) what is negotiated and checked in the fuel supply parameter negotiation step (S405).

[0516] In one alternative embodiment of FIG. 4, a plurality of safety elements, including safety elements checked in the safety check-in step (S406), can be negotiated and checked in the fuel supply parameter negotiation step (S405).

[0517] In one alternative embodiment of FIG. 4, a plurality of safety elements, including safety elements checked in the safety check-in step (S406), may be monitored and checked in the monitoring and control step (S407). In this case, the safety elements may be monitored and checked in the monitoring and control step (S407) independently (or independently) of those negotiated and checked in the fuel supply parameter negotiation step (S405).

[0518] In one alternative embodiment of FIG. 4, sharing, identifying, monitoring, updating and / or leveraging interoperability and / or compatibility can be performed throughout the entire process.

[0519] For example, an embodiment may be presented in which interoperability-related information shared between mobility and dispenser / charging station in the discovery and pairing step (S401) can be checked for each situation in subsequent steps (S402 to S411), and updated or reconfirmed with available interoperability information in each step.

[0520] For example, when the number of combinations of interoperability protocols (combinations of communication protocols and fuel supply protocols) between mobility-dispensers identified in step (S401) is 10, in a subsequent step, some of the 10 protocols may become incompatible or unusable due to communication / system errors, changes in the communication / system environment, or changes in the fuel supply environment, thereby reducing the number of available protocol combinations to less than 10. This situation is checked in steps (S402 to S411) corresponding to each Use Case, and as a result, the interoperability information is updated with the available interoperability information, and each step can be performed based on the updated interoperability information.

[0521] Additionally, for example, if at any intermediate step a particular available interoperability protocol combination A is temporarily determined to be incompatible or unusable, the step can be performed by replacing or falling back to another interoperability protocol.

[0522] For example, in steps S401 to S403, a plurality of available interoperability protocol combinations are identified, and after interoperability protocol combination A is selected as a result of communication protocol negotiation based on preferences and priorities among them, in step S404, if interoperability protocol combination A is identified as unavailable due to a change in the communication / system environment, an error, and / or a change in the fuel supply environment, another interoperability protocol combination B, which is selected or falls back to based on preferences and priorities, is determined as a result of fuel supply protocol negotiation, and step S404 and subsequent steps can be performed.

[0523] In another similar embodiment, after a plurality of available interoperability protocol combinations are identified in steps S401 to S404, and interoperability protocol combination A is selected as a result of the fueling protocol negotiation based on preferences and priorities among them, if interoperability protocol combination A is identified as unavailable in step S405 due to a change in the communication / system environment, an error, and / or a change in the fueling environment, another interoperability protocol combination B, which is selected or falls back based on preferences and priorities, is substituted as a result of the communication protocol negotiation and the fueling protocol negotiation, and then step S405 and subsequent steps may be performed.

[0524] In another similar embodiment, after a plurality of available interoperability protocol combinations are identified in steps S401 to S406, and interoperability protocol combination A is selected as a result of communication protocol negotiation, fuel supply protocol negotiation, and fuel supply parameter negotiation based on preferences and priorities among them, if interoperability protocol combination A is identified as unavailable in step S407 due to a change in the communication / system environment, an error, and / or a change in the fuel supply environment, another interoperability protocol combination B, which is selected or falls back based on preferences and priorities, is replaced as a result of communication protocol negotiation, fuel supply protocol negotiation, and fuel supply parameter negotiation, and then hydrogen fueling according to step S407 and subsequent steps can be performed.

[0525] In another alternative embodiment, for example, during a step, a particular available interoperability protocol combination A may be temporarily unavailable and replaced or fall back to another interoperability protocol, and after that step is performed, when the interoperability protocol combination A becomes available again in a subsequent step, the subsequent step may be performed by adopting the interoperability protocol combination A based on renegotiation or a predetermined policy.

[0526] For example, suppose that after interoperability protocol combination A is selected as a result of communication protocol negotiation, fueling protocol negotiation, and fueling parameter negotiation based on preferences and priorities among multiple available interoperability protocol combinations in steps S401 to S406, and then hydrogen fueling according to step S407 and subsequent steps are performed based on another interoperability protocol combination B that is selected or fallen back after interoperability protocol combination A is determined to be unavailable due to a change in the communication / system environment, an error, and / or a change in the fueling environment. At this time, if interoperability protocol combination A is determined to be available again due to a change in the communication / system environment, an error, and / or a change in the fueling environment, interoperability protocol combination A may be restored by renegotiation between the mobility and the dispenser / charging station or by a predetermined restoration process.

[0527] In one alternative embodiment of FIG. 4, when determining an alternative sub-preferred / sub-priority protocol combination, if the previously selected most preferred / highest priority protocol combination becomes incompatible or unusable among the combinations of interoperable protocols between the mobility and the dispenser, a combination in which the fueling protocol is changed while maintaining the same communication protocol as the previously selected most preferred / highest priority protocol combination may be searched for, or a combination in which the communication protocol is changed while maintaining the fueling protocol may be searched for.

[0528] In one of the alternative embodiments of FIG. 4, when generating the first interoperability information by searching for available protocol combinations in the discovery and pairing process (step S401), the priorities may be pre-determined to give priority to cases where the communication protocol and the fueling protocol each match. For example, if the combination of the communication protocol A1 and the fueling protocol B1 is determined as the highest priority / most preferred combination, combinations of the fueling protocols B2, B3, ..., etc., which can coexist with the communication protocol A1 while maintaining the communication protocol A1, may be pre-designated with high priorities as alternative combinations for the highest priority / most preferred combination. Alternatively, combinations of the communication protocols A2, A3, ..., etc., which can coexist with the fueling protocol B1 while maintaining the fueling protocol B1, may be pre-designated with high priorities as alternative combinations for the highest priority / most preferred combination.

[0529] In one of the alternative embodiments of FIG. 4, the update process for the highest priority / most preferred interoperability protocol combination while steps S403 to S409 are performed may be performed by renegotiating part or all of steps S403 to S405.

[0530] In one of the alternative embodiments of FIG. 4, the update process for the highest priority / highest preferred interoperability protocol combination may be performed by some or all of steps S410 or S411 while steps S403 to S409 are performed.

[0531] In one of the alternative embodiments of FIG. 4, the update process for the highest priority / most preferred interoperability protocol combination while steps S403 to S409 are performed may be performed by renegotiating part or all of steps S403 to S405, but via part or all of steps S410 or S411.

[0532] According to one embodiment of the present invention, a communication method for hydrogen fuel supply may be performed such that after mobility, a dispenser, or mobility and a dispenser cooperate to determine a combination of top-priority / highest-preference interoperability protocols in step S401, the combination of top-priority / highest-preference interoperability protocols may be determined while steps S403 to S409 are performed (with the help of steps S410 and S411). At this time, the method may further include a step of performing at least one of a first process and a subsequent process of the first process based on the first communication protocol and the first fuel supply protocol. At this time, the interoperability communication protocol and the fuel supply protocol determined based on the updated interoperability information may partially restrict functions on the mobility side or partially restrict communication functions between the mobility and the dispenser, and therefore, in some cases, the dispenser may perform the hydrogen fuel supply process or a subsequent process thereof alone or proactively. That is, if interoperability is downgraded or falls back, the dispenser can take on more of a role than the mobility.

[0533] Referring again to Figure 4, once fueling is successfully finished and optionally all safety conditions are confirmed, the mobility and dispenser termination use cases can be performed.

[0534] The purpose, prerequisites, and subsequent conditions of the termination step (S409) can be illustrated by the following Table 25.

[0535]

[0536] TypeDescriptionUse case nameUC-9: "Termination"ObjectivesAs the last step of fuelling, vehicle and dispenser finalizes the fuelling by exchanging information about fuelling results regarding fuelling performance and methods, and any reasons if the fuelling stopped unexpectedly. This use case also handles the house-keeping when a non-safety-critical problem occurred.Short DescriptionAfter the fuelling has been finished and safety checks are confirmed, vehicle and dispenser exchanges some book-keeping information regarding the fuelling session.When a non-safety-critical problem occurred, this use case allows the vehicle and dispenser to exchange wrap-up information about the fuelling session before leaving.Pre-conditionsThe fuelling is finished and the nozzle is safe to unplug.Or a non-safety-critical problem occurred during any other use cases.Post-conditionsInformation about the fuelling session is stored and the fuelling session is completely finished.

[0537] If the safety check-out use case is skipped after receiving a SafetyCheckOutRes message with "Result" set to "DONE" or a FuelLoopRes message with "status" set to a prefixed value of "finished" or "stopped", the mobility can send a termination request message (e.g., "TerminateReq") to the dispenser.

[0538] Details of the TerminateReq message (e.g., "TerminateReq") may be defined in the respective fueling protocol specifications. For example, the parameters exchanged between the mobility and the dispenser within the TerminateReq message may be defined differently for each individual fueling protocol.

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

[0540] Element NameTypeSemanticstank_pressFinal tank pressuretank_tempFinal tank temperatureamountOptional:The amount of hydrogen that is fuelled.socOptional:The final state of charge from vehicle's measurementreasonTypeReason for termination from Vehicle's point of view. “finished” if dispenser indicated so. "stopped_user" if the user requested to stop. “complete” if the fueling goal is achieved. "unknown" otherwise. Other reason code can be defined by fueling protocol.

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

[0542] Details of the Terminate Response message (e.g., "TerminateRes") may be defined in the respective fueling protocol specifications. For example, the parameters exchanged between the mobility and the dispenser within the TerminateRes message may be defined differently for each individual fueling protocol.

[0543] Element names included in the TerminateRes message may include aprr, duration, amount, soc, result, etc., and may be illustrated by Table 27 below. Elements not illustrated in Table 27 below may be specified by each fuel supply protocol standard, such as ISO 19885-3, for example.

[0544] Element NameTypeSemanticsaprrOptional:Average Pressure Ramping RatedurationOptional:Duration of the fuellingamountOptional:The amount of hydrogen that is fuelled.socOptional:The final state of charge from dispenser's measurementresultresultType

[0545] As an alternative embodiment, a message requesting the start of a termination step (S409) may be transmitted by either the mobility or the dispenser to the other party. In this case, the other party may perform the termination step (S409) by responding to the message requesting the start of the termination step (S409).

[0546] For successful refueling, communication must provide the expected behaviors according to the protocol. Refueling behavior must remain within acceptable limits within the refueling protocol. However, in practice, various abnormal events can occur. Some errors are minor and easily handled. However, errors that cannot be recovered and prevent refueling from continuing can also occur.

[0547] In this specification, 'error' or 'error' may refer to incidents occurring during UC1 to UC9 (S401 to S409) or hydrogen fueling, which may interrupt the ongoing process.

[0548] In step (S410), conditions for non-safety critical errors, exemplary error conditions and responses thereto can be specified.

[0549] Referring again to FIG. 4, the purpose, prerequisites, and subsequent conditions of the error handling step (S410) can be illustrated by the following Table 28.

[0550]

[0551] TypeDescriptionUse case nameUC-10: "Error Handling"ObjectivesThis use case handles the situation when a non-safety-critical error occurred by terminating the fuelling procedure similar to normal terminations or abruptly stopping the communication.Short DescriptionAt any time during the fuelling, a non-safety critical error can occur. In this case, vehicle and dispenser stops the use case at the moment and then move to Termination use case (UC-9) to finish the fuelling procedure with both ends informed about the termination reasons. If further communication is not possible, the communication channel is dropped without further notification.Pre-conditionsA non-safety critical error occurred and fuelling cannot be performed further.Post-conditionsVehicle and dispenser is informed about the error and stopped the fuelling.

[0552] non-safety critical error 조건은 예를 들어 다음을 포함할 수 있다.

[0553] Communication errors may include 1) communication being disconnected, 2) received data being unrecognizable due to encoding or syntactic errors, and 3) received data being in an unacceptable range.

[0554] As a system error, this may include cases where the dispenser or mobility detects its own critical system error.

[0555] Qualitative errors may include 1) failure to meet the required level of communication performance, and 2) failure to meet the required level of data integrity or precision.

[0556] When a non-safety-critical error occurs and further communication is no longer possible, the mobility and dispenser stop the fueling immediately but take safe steps, and stop the communication to end the session.

[0557] When a non-safety-critical error occurs and fueling is interrupted while far from complete, the fueling protocol can define a fallback mechanism, for example by defining a non-communication fueling method.

[0558] When a non-safety-critical error is detected by the mobility and the communication channel is still operational, the mobility may send a TerminateReq message with "action" set to "stop" and "reason" set to an appropriate reason code.

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

[0560] A fueling protocol may define protocol-specific error conditions and provide detection criteria, and prescribed response procedures including notification, termination procedures, and fallback mechanisms.

[0561] Referring again to FIG. 4, the purpose, prerequisites, and subsequent conditions of the emergency handling step (S411) can be illustrated by the following Table 29.

[0562]

[0563] TypeDescriptionUse case nameUC-11: "Emergency Handling"ObjectivesDefine safety-critical conditions that warrant an urgent response and prescribe the response procedure to avoid safety-critical incidents.Short DescriptionFor safe fueling, communication must exhibit expected behaviors according to the protocol and the fueling behavior must stay within the safe range of the fueling protocol. However, it is possible that something goes wrong and the fueling system approaches a critical condition that the system must avoid at all cost. In this use case, we define safety-critical emergency conditions and possible reactions, and provide exemplary cases to consider.Pre-conditionsA safety-critical problem occurred during any moment of fuelling and an urgent response is necessary.Post-conditionsSafety-critical incidents are avoided or minimized, and the fuelling session has been stopped completely.

[0564] A fueling protocol may define emergency conditions according to the protocol and may provide for prescribed response procedures to avoid entering a detrimental situation by all means, including detection criteria, notification, termination procedures, and fallback mechanisms.

[0565] When a mobility device or dispenser detects a safety-critical situation, necessary actions can be taken immediately to prevent a catastrophic event. Additionally, if possible, an EmergencyNotif message can be sent with information about the incident, and communication can be closed.

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

[0567] The EmergencyNotif message can be a TLS or DTLS message, depending on the communication technology used.

[0568] For the sake of message criticality and efficiency of delivery, the fueling protocol may not be allowed to modify the structure of the EmergencyNotif message.

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

[0570] Element NameTypeSemanticsclassunsignedByteOptional:Severity class of this emergency, from 1 to 5 with decreasing severity.typeunsignedByteEmergency reason code by number defined in Table XYZactionunsignedByteOptional:Pre-defined action code necessary or recommended to be performed by the receiving party

[0571] FIG. 16 is a flowchart illustrating one of the alternative embodiments of FIG. 4.

[0572] Referring to FIG. 16, the relationship between S2010 and S2020 added to steps S401 to S409 of FIG. 4 is illustrated.

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

[0574] The following embodiments may be performed based on interoperability or compatibility information shared between the mobility and the dispenser in step S401 of FIG. 4. In particular, the process of negotiating and determining the communication protocol, fuel supply protocol, and fuel supply parameters in steps S403 to S405 may be performed within the scope of the interoperability or compatibility information.

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

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

[0577] The process of classifying the detected error as a safety-critical error at this time may be performed by step S2020, or may be performed by a part of step S411 of Fig. 4, and the step of performing the subsequent process when the detected error is classified as a safety-critical error may be performed by a separate step (S403 to S409), or may be performed by a part of step S411 of Fig. 4. At this time, an error classified as a safety-critical error may be treated as an emergency.

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

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

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

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

[0582] Various types of incidents occurring during the execution of steps S403 to S409 can be detected by the mobility or dispenser (S2010). The detected incidents can be classified as errors if they meet certain conditions (S2010 and S2020). If the detected error is a non-safety-critical error, it can be handled through the error handling process of step S410 or a separate subsequent step, and if it is a safety-critical error, it can be handled through the emergency handling process of step S411.

[0583] In one embodiment of the present invention, the criteria for classifying a detected error as a non-safety-critical error or a safety-critical error (emergency) are predefined by the fuel supply protocol of steps S403 to S409, and the detected error can be classified by each step S403 to S409 when the error is detected.

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

[0585] Step S410 may classify the detected error and determine whether to stop the fuel supply process based on the classification result or the status of the error. If it is determined not to stop the fuel supply process and to continue the fuel supply process by the fallback fuel supply protocol (based on updated interoperability or compatibility information), steps necessary for continuing the fuel supply process among steps S403 to S409 may be performed again as a result of step S410.

[0586] Additionally, in step S410 or S411, when the cause of the error is removed and the normal state is restored, the mobility or dispenser may, either alone or in cooperation with each other, return to any one of steps S403 to S409 that was being performed before the error occurred, or to the next step, and continue the hydrogen fueling process and the communication process.

[0587] A communication method for hydrogen fueling performed by a communication device of a dispenser for supplying hydrogen fuel to hydrogen fuel mobility according to one embodiment of the present invention comprises: a step (step S2010; which may be performed as a part of steps S403 to S406, or steps S408 to S409) for preparing hydrogen fueling between the dispenser and the mobility or a step (step S407) for supplying hydrogen to the mobility by the dispenser; a step (step S2020; which may be performed as a part of steps S410 or S411) for determining whether to stop the communication process (steps S403 to S406, or steps S408 to S409) or the process of supplying hydrogen to the mobility in response to the detected error; and a step of performing a defined follow-up process based on the detected error (performed as part of steps S403 to S411).

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

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

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

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

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

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

[0594] In case of a communication error, the mobility or dispenser can stop the session if necessary.

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

[0596] In an alternative embodiment, in the case of a qualitative error, a fallback fueling protocol based on a limited communication protocol or communication environment may be selected based on updated interoperability or compatibility information between the mobility and the dispenser, and hydrogen may be fueled based on the selected fueling protocol.

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

[0598] In an alternative embodiment, in the event of a qualitative error, the mobility and dispenser may perform renegotiation to select a new communication protocol and fuel supply protocol combination. Renegotiation may involve re-performing portions of steps S403 through S405, or may be performed within step S410.

[0599] In an alternative embodiment, communication can be minimized and subsequent processing can be performed even in an emergency situation, provided communication remains active. The mobility or dispenser can fallback to the communication protocol and fuel delivery protocol.

[0600] In an alternative embodiment, in the case of an emergency, the cessation of fuel supply and communication may be performed with the highest priority.

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

[0602] In a communication method for hydrogen fuel supply performed by a communication device of a dispenser according to one embodiment of the present invention, when a message including whether to stop a communication process or a hydrogen fuel supply process includes a stop of the communication process or the hydrogen fuel supply process, the message may further include a reason code corresponding to an appropriate reason for the stop.

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

[0604] In the embodiments of FIGS. 4 and 16, steps S2010, S2020, S410, and / or S411 are illustrated in an embodiment in which steps S403 to S409 are related to steps S403 to S409. In one alternative embodiment of the present invention, steps S2010 and S2020 may detect all incidents occurring during steps S401 to S409, or during the fuel supply process, determine whether they are errors, and classify the errors. In another alternative embodiment of the present invention, after going through steps S2010, S2020, and steps S410 and S411 as part of a separate subsequent step, the process may return to any one of steps S401 to S409 to perform the subsequent process or to perform the existing process and / or the next process if the error is resolved.

[0605] That is, steps S2010 and S2020 can detect incidents occurring in the hydrogen fueling process, such as steps S401 - UC1: Discovery and Pairing, steps S402 - UC2: Communication Security, steps S403 - UC3: Communication Protocol Negotiation, steps S404 - UC4: Fuel Supply Protocol Negotiation, steps S405 - UC5: Fuel Supply Parameter Negotiation, steps S406 - UC6: Safety Check-in, steps S407 - UC7: Monitoring and Control, steps S408 - UC8: Safety Check-out, steps S409 - UC9: Termination, or in parallel therewith, determine whether incidents are errors, detect errors, or classify errors.

[0606] Additionally, after the error is classified and its handling is performed in S410 or S411, the process may return to steps S401 to S409 or a hydrogen fuel supply process in parallel therewith.

[0607] In addition, after the error is processed and resolved, the process that was being performed before the error occurred or the next step can be returned to steps S401 to S409 or the hydrogen fuel supply process that is performed in parallel therewith.

[0608] In one alternative embodiment, as a criterion for determining whether an error is critical to safety, incidents that may occur before / during / after hydrogen fueling, which may cause damage to the facility and / or human life, or may cause fire, explosion, leak, etc. may be considered.

[0609] In the event of a safety-critical error, communication and fueling may be interrupted and / or terminated. In an alternative embodiment, fueling may continue even in the event of a safety-critical error if communication is secured, fueling is available, or fueling must continue (e.g., for reasons such as evacuation from a hazardous area, transport of a patient, etc.).

[0610] In case of non-safety-critical errors, communication or fueling may be stopped or continued based on the criticality / severity of the error, available communication environment, available fueling protocol, UCDC level, necessity of communication or fueling, etc.

[0611] In the above embodiments, the process of continuous monitoring of interoperability, updating of interoperability information accordingly, and / or updating of a communication / fuel supply protocol combination has been disclosed with a focus on an embodiment in which either the mobility or the dispenser performs the process, but the detailed process of these processes may be performed by either the mobility or the dispenser, and may be performed through mutual cooperation. In addition, in an alternative embodiment of the present invention, part of the process of continuous monitoring of interoperability, updating of interoperability information accordingly, and / or updating of a communication / fuel supply protocol combination may be performed proactively by the mobility, and part of the process may be performed proactively by the dispenser.

[0612] Additionally, the detection of an error may be performed by either the mobility or the dispenser, and the entity that detected the error may transmit a message to the other party including the detection of the error, the detected error, the suspension of communication and fuel supply based on the error, or a reason code corresponding to the reason for the suspension.

[0613] FIG. 17 is a flowchart illustrating a communication method for hydrogen fuel supply according to another embodiment of the present invention.

[0614] Referring to FIGS. 16 and 17 together, a communication method for hydrogen fueling according to an embodiment of the present invention is performed by a communication device of hydrogen fueled mobility, and may include a step of discovering a dispenser that fuels hydrogen to mobility, sharing pairing information between the mobility and the dispenser, and performing pairing between the mobility and the dispenser (S2100); a step of negotiating a communication protocol or a fueling protocol for a process in which the dispenser fuels hydrogen to the mobility based on information related to interoperability or compatibility between the mobility and the dispenser (S2200); and a step of transmitting information required for monitoring and controlling a process in which the dispenser fuels hydrogen to the mobility based on the fueling protocol to the dispenser (S2300). At this time, the operation performed in the step (S2100) of performing pairing may include part or all of the operation of step S401 of FIGS. 4 and 16. The operation performed for monitoring and control may include part or all of the operation of step S407 of FIGS. 4 and 16. The operation that the dispenser can perform in step S407 and / or the operation that the mobility can perform in step S407 may be performed in step S2300.

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

[0616] A communication method for hydrogen fuel supply according to one embodiment of the present invention may further include a check-in step (see step S406 of FIGS. 4 and 16) for checking whether a first necessary safety condition is satisfied between the mobility and the dispenser before the process of the dispenser supplying hydrogen to the mobility, after the step of negotiating a communication protocol or a fuel supply protocol (S2200); and a check-out step (see step S408 of FIGS. 4 and 16) for checking whether a second necessary safety condition is satisfied between the mobility and the dispenser after the process of the dispenser supplying hydrogen to the mobility and before the nozzle is separated from the mobility.

[0617] According to an alternative embodiment of the present invention, the first necessary safety condition and / or the second necessary safety condition may include a state of engagement between the nozzle and the receptacle, a state of airtightness of the engagement portion, a temperature, pressure, remaining charge (SoC) of the hydrogen storage tank on the mobility or dispenser side, etc.

[0618] A communication method for hydrogen fuel supply according to one embodiment of the present invention may further include a step of detecting and handling a non-safety-critical error that occurs during the step of negotiating a communication protocol or a fuel supply protocol (S2200) or the step of transmitting information required for monitoring and control to the dispenser (S2300) (see steps S2010 and S410 of FIG. 16); and a step of detecting and handling an emergency situation that requires stopping the interaction between the dispenser and mobility that occurs during the step of negotiating a communication protocol or a fuel supply protocol (S2200) or the step of transmitting information required for monitoring and control to the dispenser (S2300) (see steps S2020 and S411 of FIG. 16).

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

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

[0621] In a communication method for hydrogen fuel supply according to one embodiment of the present invention, in the step of performing pairing (S2100), pairing information shared between the mobility and the dispenser may include information related to interoperability or compatibility between the mobility and the dispenser.

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

[0623] A communication method for hydrogen fuel supply according to one embodiment of the present invention may further include a step of re-performing part or all of the step of negotiating a communication protocol or a fuel supply protocol (S2200) if a non-safety-critical error that occurs during the step of negotiating a communication protocol or a fuel supply protocol (S2010 and S410 of FIG. 16) is detected.

[0624] In the step (S407) of transmitting information required for monitoring and controlling a communication method for hydrogen fuel supply according to one embodiment of the present invention to a dispenser, the information transmitted by the mobility to the dispenser can be determined based on whether the fuel supply protocol allows two-way communication between the mobility and the dispenser as a communication protocol.

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

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

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

[0628] A communication method for hydrogen fuel supply performed by a communication device of a dispenser according to one embodiment of the present invention may further include steps (S2010 and S410) of detecting and handling a non-safety-critical error that occurs during the step of negotiating a communication protocol or a fuel supply protocol (S2200) or the step of controlling the dispenser to monitor a process of fueling hydrogen to mobility (S2300, S407); and steps (S2020 and S411) of detecting and handling an emergency situation that requires stopping mutual operation between the dispenser and the mobility, which occurs during the step of negotiating a communication protocol or a fuel supply protocol or the step of controlling the dispenser to monitor a process of fueling hydrogen to mobility (S2300, S407).

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

[0630] A communication method for hydrogen fuel supply according to one embodiment of the present invention may include, as part of step S401 of FIG. 4, step S401 of FIG. 16, and step S2100 of FIG. 17, a step of checking information related to interoperability or compatibility between mobility and a dispenser based on pairing information.

[0631] The method illustrated in FIG. 17 may be performed by the mobility or by the dispenser, or may be performed by mutual cooperation between the mobility and the dispenser.

[0632] In the embodiment of FIG. 17, the entity communicating with the mobility is described as a dispenser, but the communication devices of the dispenser or station may communicate with the mobility alone or in cooperation.

[0633] For example, multiple wireless LAN Access Points (APs) are deployed at a station, and some of these APs are assigned to dispensers, while others can participate in communication with mobility without being directly assigned to dispensers.

[0634] Step S2100 may include a process of sharing pairing information using wireless communication between the mobility and the dispenser (or station), and using this to discover the presence of each other.

[0635] Step S2100 may be a process for verifying the correct pairing between the mobility and the dispenser. The entity performing the pairing check may be either the mobility or the dispenser (station), or it may be either one or both.

[0636] Based on the pairing information from step S2100 and thereafter (based on the interoperability and compatibility information within the pairing information), the dispenser and the mobility may perform subsequent processes related to a communication protocol or a fueling protocol for supplying hydrogen to the mobility by transmitting and receiving at least one message. This process may correspond to, for example, step S2200 of FIG. 17, steps S403 to S405 of FIG. 4 and / or steps S405 of FIG. 16.

[0637] According to one embodiment of the present invention, the hydrogen fuel mobility and the dispenser / station can discover each other, check compatibility, and verify correct pairing, thereby supporting the start of the hydrogen fueling process and shortening the process up to the start of the hydrogen fueling process.

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

[0639] At this time, according to one embodiment of the present invention, information such as interoperability and compatibility required in a subsequent process can be shared with the other party, and the process up to the start of the hydrogen fuel supply process can be shortened.

[0640] In the step of discovering a dispenser (S2100), a message transmitted and received between the dispenser and the mobility may include a VSE (Vendor Specific Element) data field, and the VSE data field may include at least a part of information regarding pairing.

[0641] The VSE data field may include, as at least part of the information regarding pairing, a specification supported by the dispenser or mobility; a version of the specification; a fueling protocol supported by the dispenser or mobility; a communication protocol supported by the dispenser or mobility; or identification information for pairing the dispenser or mobility.

[0642] The specifications supported by the dispenser or mobility device may be known standards, such as ISO 19885, or may include support for specific standards. The specification version may refer to a specific version of the standard.

[0643] For example, a VSE may indicate that the mobility or dispenser is an ISO 19885 device and may include compatibility information, including a list of supported communication / fueling protocols.

[0644] Additionally, identifier (ID) information for pairing may be added to the VSE data field. The pairing ID may be used for pairing between the mobility and the dispenser in the pairing step (S2100).

[0645] The VSE (Vendor Specific Element) data field can be added to beacon, probe request / response, association request (Assoc Req), and re-association request (Reassoc Req) messages.

[0646] In steps S2100 and S2200, wireless communication technologies such as wireless local area network (WLAN) may be utilized. Pairing information and / or interoperability / compatibility information may be shared between the mobility and the dispenser / station using the Vendor Specific Element (VSE) data field.

[0647] Pairing information may include the location or precise positioning information of the dispenser. Additional pairing information may also be provided via a fueling cable between the mobility device and the dispenser.

[0648] Pairing information can be exchanged using additional communication technologies other than wireless LAN, such as cables, NFC, RFID, and barcodes. Short-range communication technologies can support precise location measurement and positioning.

[0649] The process of checking / verifying pairing can be performed using one-way pairing. In one embodiment of one-way pairing, the mobility can check the dispenser. In other embodiments, the dispenser can check the mobility, or both can check the other.

[0650] While the above embodiment illustrates an embodiment in which a message includes a list of communication protocols, in other embodiments of the present invention, the message may include a list of fuel supply protocols or fuel supply parameters. Furthermore, the list of communication protocols may be exchanged in association with a list of supported fuel supply protocols.

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

[0652] In a communication method for hydrogen fueling performed by a communication device of hydrogen fuel mobility according to one embodiment of the present invention, information related to interoperability or compatibility between a dispenser and mobility may include whether two-way communication between the dispenser and mobility is supported; whether a function of sharing measurement data through two-way communication between the dispenser and mobility is supported; whether the measurement data can be used to control or manage a process in which the dispenser supplies hydrogen to the mobility; or whether a fallback or alternative protocol of a communication protocol or a fueling protocol can be determined based on a change in a communication environment between the dispenser and the mobility during a process in which the dispenser supplies hydrogen to the mobility.

[0653] In one alternative embodiment of FIG. 17, the range of fueling protocols commonly supported by the dispenser or mobility may be guided by whether bidirectional communication is supported between the dispenser or mobility, as identified in the list of communication protocols supported by the dispenser or mobility.

[0654] In one alternative embodiment of FIG. 17, whether the sharing of real-time measurement data (actual measurement data on the dispenser side or the mobility side) between the dispenser and the mobility is supported using two-way communication can be shared as interoperability / compatibility information.

[0655] In one alternative embodiment of FIG. 17, whether real-time measurement data can be utilized in the control or management process of the fueling protocol for the process of supplying hydrogen from the dispenser to the mobility can be shared as interoperability / compatibility information.

[0656] In one alternative embodiment of FIG. 17, the occurrence of situations such as UC10 or UC11 can be shared between the mobility and the dispenser based on real-time measurement data. At this time, whether or not interoperability / compatibility information is fallbacked can be determined based on factors such as whether bidirectional communication is supported, whether real-time measurement data can be shared, and whether real-time measurement data can be utilized. In addition to fallback, an alternative communication / fueling protocol or a second-best communication / fueling protocol can be selected, and the hydrogen fueling process can be performed or terminated based on the selected protocol, depending on the situation.

[0657] In one embodiment of the present invention, by searching for specific details of the hydrogen fuel supply protocol in advance in the pairing and discovery step (S401), the agreement process such as the subsequent protocol negotiation step (S403 to S405) can be supported, and the negotiation process can be shortened secondarily.

[0658] In one embodiment of the present invention, when a situation corresponding to UC10 or UC11 occurs, the response process is processed quickly and efficiently using the interoperability / compatibility information shared in S401, thereby improving the success probability of the overall hydrogen fueling process and shortening the time required for the hydrogen fueling process.

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

[0660] A communication method for hydrogen fueling according to one embodiment of the present invention is performed by a communication device of hydrogen fueled mobility, and may include a step (S2400) of broadcasting a Dispenser Discovery Protocol (DDP) request message via a communication network including a dispenser that supplies hydrogen to mobility; a step (S2500) of receiving a DDP response message including identification information of the dispenser on the communication network from the dispenser; and a step (S2600) of performing authentication for pairing between the mobility and the dispenser using the identification information of the dispenser in the DDP response message.

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

[0662] At this time, the process of determining the IP address of the mobility may involve the communication network determining the IP address and the mobility being assigned an IP address. In an alternative embodiment, the mobility may select one of the available IP addresses in the communication network to determine the IP address and assign the IP address to itself. At this time, the process of determining the IP address of the mobility may be performed through mutual cooperation between the communication network and / or the mobility, and the scope of the present invention is not limited thereto.

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

[0664] Mobility and dispensers can support IPv6 as defined in IEFT RFCs 8200 and 8504.

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

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

[0667] In a communication method for hydrogen fueling performed by a communication device of mobility according to one embodiment of the present invention, an IP address of the mobility may be generated based on a random number.

[0668] In a communication method for hydrogen fueling performed by a communication device of mobility according to one embodiment of the present invention, the mobility may generate an IPv6 address by a method specified in, for example, RFC 3041, etc., in order to avoid exposure of a MAC address that may be permanent of the mobility when the IPv6 address is exposed or shared with a dispenser.

[0669] In a communication method for hydrogen fueling performed by a communication device of mobility according to one embodiment of the present invention, the mobility may generate an IPv6 address based on a random number, for example, by a method specified in RFC 3041, etc., in order to avoid exposure of a MAC address that may be permanent of the mobility when the IPv6 address is exposed or shared with a dispenser.

[0670] To perform the DDP protocol, the mobility can broadcast a DDPRequest message over a communication network that includes the dispenser.

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

[0672] For example, a message could be broadcast using the link-local multicasting address "0xff02::1" and port number 19885.

[0673] An embodiment in which a DDP request message is implemented based on XML, etc. can be disclosed by Table 31 below.

[0674] DDPRequest = {"pairing_id" :<vehicle's pairing ID> (optional)}

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

[0676] An embodiment in which a DDP response message is implemented based on XML, etc. can be disclosed by Table 32 below.

[0677] DDPResponse = {"IPaddress" :<dispenser IP address> ,"TCPPort":<dispenser's TCP port number> ,"UDPPort":<dispenser's UDP port number> "pairing_id" :<dispenser's pairing ID> (optional)}

[0678] In an alternative embodiment, the pairing ID of the mobility and dispenser, etc. may be shared with the other party using a separate process within the DDP protocol other than the DDP request message or DDP response message and may be used in the authentication process for pairing.

[0679] In a communication method for hydrogen fueling performed by a communication device of hydrogen fueled mobility according to an alternative embodiment of the present invention, identification information of mobility included in a DDP request message or a message transmitted in a subsequent process may include an IP address of the mobility (generated to avoid exposure of a MAC address), and identification information of a dispenser included in a DDP response message may include an IP address of the dispenser, a TCP port number of the dispenser, or a UDP port number of the dispenser.

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

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

[0682] In the step (S2600) of performing authentication for pairing between the mobility and the dispenser, authentication for pairing between the mobility and the dispenser can be performed via a pairing channel different from the communication channel through which the mobility is connected to the communication network, using the pairing identifier of the mobility and the pairing identifier of the dispenser.

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

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

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

[0686] The pairing channel may be implemented as a separate secure channel (e.g., TCP and / or TLS). In alternative implementations, the pairing channel may be established using a different communication technology than the communication channel. For example, the communication channel may be WLAN, and the pairing channel may be UWB, or it may be established using short-range communication such as BLE, irDA, or RFID.

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

[0688] Although mobility may act as a client within TCP / TLS / DTLS and the dispenser may act as a server, the spirit of the present invention is not limited to any particular embodiment.

[0689] A mobility DDP request message may include queries such as where a dispenser is or who the dispenser is.

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

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

[0692] In a TCP 3-way handshake, the mobility sends a SYN message, the dispenser responds with a SYN / ACK message, and the mobility can respond with an ACK message.

[0693] In a TLS 3-way handshake, the mobility sends a Client Hello message, the dispenser responds with a Server Hello message, and the mobility can send a Client finished + First fueling message.

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

[0695] If the dispenser acts as a server, the dispenser can request authentication from the client (mobility) at any time.

[0696] If dispenser authentication fails, the mobility may log this security event in the mobility's EVCC or associated database, notify the user of this security event if possible, and stop fueling based on emergency handling (UC11, S411).

[0697] If mobility authentication fails, the dispenser can log this security event in the dispenser's SECC or associated database and stop fueling based on emergency handling (UC11, S411).

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

[0699] In an alternative embodiment, in the step of broadcasting a DDP request message (S2400), the DDP request message may include information on a communication protocol or fuel supply protocol supported by the mobility as information related to interoperability or compatibility between the mobility and the dispenser.

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

[0701] In the alternative embodiment step (S401), in the process of sharing information for pairing between the mobility and the dispenser after the step (S2500) of transmitting / receiving a DDP response message, the message transmitted by the dispenser may include information on a communication protocol or fuel supply protocol supported by the dispenser as information related to interoperability or compatibility between the mobility and the dispenser.

[0702] In an alternative embodiment, in the step of transmitting / receiving a DDP response message (S2500), the DDP response message may include information on a communication protocol or fuel supply protocol supported by the dispenser as information related to interoperability or compatibility between the mobility and the dispenser.

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

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

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

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

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

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

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

[0710] In the step of performing authentication for pairing between the mobility and the dispenser, authentication for pairing between the mobility and the dispenser can be performed via a pairing channel different from the communication channel through which the mobility is connected to the communication network, using the pairing identifier of the mobility and the pairing identifier of the dispenser.

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

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

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

[0714] In an alternative embodiment, authentication for pairing (S2600) may be performed by requesting or initiating it on the mobility side as needed.

[0715] In an alternative embodiment, authentication for pairing (S2600) may be performed by the dispenser continuously requesting or initiating the mobility. In particular, to perform the step (S407) of monitoring and controlling the hydrogen fueling process after hydrogen fueling has begun, the dispenser may periodically or continuously request or initiate the process related to authentication for pairing (S2600) from the mobility.

[0716] In an alternative embodiment, authentication for pairing (S2600) can be performed with unilateral authentication.

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

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

[0719] In an alternative embodiment, an entity performing the role of a server in the authentication process for pairing (S2600) may transmit a certificate, a signature, a cert request, etc. to the other party.

[0720] In an alternative embodiment, when authentication for pairing (S2600) is performed with mutual authentication, the mobility may act as the server once and the dispenser may act as the server once.

[0721] For convenience of explanation, one embodiment of the present invention illustrates an embodiment in which protocol messages are expressed or coded as JSON-based messages. In alternative embodiments of the present invention, protocol messages can be generated using various message coding and / or representation techniques, and protocol messages generated using various techniques can be transmitted and received between mobility, dispensers, and charging stations.

[0722] FIG. 19 is a conceptual block diagram of the internal structure of a generalized computing system that can be mounted on a hydrogen fuel mobility, dispenser, and / or fuel supply station as a communication device, a communication control device, and / or an electronic control device for hydrogen fuel supply according to one embodiment of the present invention.

[0723] Although omitted in the drawings in the embodiments of FIGS. 1 to 18, a processor and a memory are electronically connected to each component, and the operation of each component can be controlled or managed by the processor.

[0724] At least a part of the process of the fuel supply communication method for supplying fuel to an electric vehicle according to one embodiment of the present invention can be executed by the computing system (3000) of FIG. 19.

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

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

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

[0728] Additionally, the computing system (3000) may include a communication interface (3300) that performs communication via a wired / wireless network.

[0729] Additionally, the computing system (3000) may further include a storage device (3400), an input interface (3500), an output interface (3600), etc.

[0730] Additionally, each component included in the computing system (3000) can communicate with each other by being connected by a bus (3700).

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

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

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

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

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

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

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

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

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

[0740] Meanwhile, while most of the aforementioned embodiments have focused on first transmitting the communication protocol or parameters of hydrogen fuel mobility from the hydrogen fuel mobility to the dispenser, the present invention is not limited to a specific embodiment and can be configured to first transmit the communication protocol or parameters of the dispenser from the dispenser to the hydrogen fuel mobility. In this case, it is self-evident that the embodiments have substantially the same features, except that the transmitter becomes the receiver and the receiver becomes the sender.

[0741] The operations of the method according to an embodiment of the present invention can be implemented as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes any type of recording device that stores information readable by a computer system. Furthermore, a computer-readable recording medium can be distributed across network-connected computer systems, allowing the computer-readable program or code to be stored and executed in a distributed manner.

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

[0743] While some aspects of the present invention have been described in the context of a device, they may also represent a description of a corresponding method, wherein a block or device corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method may also be described as a corresponding block or item or a feature of a corresponding device. 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 an electronic circuit. In some embodiments, at least one or more of the most important method steps may be performed by such a device.

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

[0745] Although the present invention has been described above with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various modifications and changes may be made to the present invention without departing from the spirit and scope of the present invention as set forth in the claims below.< / false> < / true> < / ok> < / true> < / ok> < / pending> < / pending>

Claims

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

2. In paragraph 1, A step of determining an IP address of the mobility to be used in the communication network including the dispenser prior to the step of broadcasting the DDP request message, and connecting the mobility to the communication network via a communication channel based on the IP address of the mobility; Including more, A method of communication for hydrogen fuel supply.

3. In paragraph 2, The IP address of the above mobility is generated based on a random number. A method of communication for hydrogen fuel supply.

4. In paragraph 1, The above DDP request message includes the pairing identifier (ID) of the mobility, The identification information of the dispenser included in the above DDP response message includes the pairing identifier (ID) of the dispenser, In the step of performing authentication for pairing between the above mobility and the above dispenser, A communication method for hydrogen fuel supply, which performs authentication for pairing between the mobility and the dispenser using the pairing identifier of the mobility and the pairing identifier of the dispenser.

5. In paragraph 4, In the step of performing authentication for pairing between the above mobility and the above dispenser, Using the pairing identifier of the above mobility and the pairing identifier of the above dispenser, the mobility performs authentication for pairing between the mobility and the dispenser via a pairing channel different from the communication channel through which the mobility is connected to the communication network. A method of communication for hydrogen fuel supply.

6. In paragraph 4, The step of performing authentication for pairing between the above mobility and the above dispenser is: A step of binding a pairing channel for pairing between the mobility and the dispenser to a communication channel using the pairing identifier of the mobility and the pairing identifier of the dispenser; and A step of performing authentication for pairing between the mobility and the dispenser using the pairing identifier of the mobility and the pairing identifier of the dispenser within the pairing channel; comprising; A method of communication for hydrogen fuel supply.

7. In paragraph 1, The identification information of the dispenser included in the above DDP response message is: including the IP address of the dispenser, the TCP port number of the dispenser, or the UDP port number of the dispenser. A method of communication for hydrogen fuel supply.

8. In paragraph 1, After pairing between the above mobility and the above dispenser is performed, A step of negotiating a communication protocol or a fuel supply protocol between the above mobility and the above dispenser; Including more, A method of communication for hydrogen fuel supply.

9. In paragraph 1, After pairing between the above mobility and the above dispenser is performed, A step of establishing a secure channel between the mobility and the dispenser to negotiate a communication protocol or a fuel supply protocol between the mobility and the dispenser; Including more, A method of communication for hydrogen fuel supply.

10. In paragraph 8, The step of negotiating a communication protocol or fuel supply protocol between the above mobility and the above dispenser is: A step of negotiating the communication protocol between the said mobility and the said dispenser; A step of negotiating the fuel supply protocol between the mobility and the dispenser based on the above communication protocol; and A step of negotiating fuel supply parameters between the mobility and the dispenser based on the above fuel supply protocol; Including, A method of communication for hydrogen fuel supply.

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

12. In paragraph 11, The above DDP request message includes the pairing identifier (ID) of the mobility, The identification information of the dispenser included in the above DDP response message includes the pairing identifier (ID) of the dispenser, In the step of performing authentication for pairing between the above mobility and the above dispenser, Performing authentication for pairing between the mobility and the dispenser using the pairing identifier of the mobility and the pairing identifier of the dispenser. A method of communication for hydrogen fuel supply.

13. In paragraph 12, In the step of performing authentication for pairing between the above mobility and the above dispenser, Using the pairing identifier of the above mobility and the pairing identifier of the above dispenser, the mobility performs authentication for pairing between the mobility and the dispenser via a pairing channel different from the communication channel through which the mobility is connected to the communication network. A method of communication for hydrogen fuel supply.

14. In paragraph 11, The identification information of the dispenser included in the above DDP response message is: including the IP address of the dispenser, the TCP port number of the dispenser, or the UDP port number of the dispenser. A method of communication for hydrogen fuel supply.

15. In paragraph 11, After pairing between the above mobility and the above dispenser is performed, a step of negotiating a communication protocol or a fuel supply protocol between the above mobility and the above dispenser; and A step of monitoring and controlling a process in which the dispenser supplies hydrogen to the mobility based on the above fuel supply protocol; Including more, A method of communication for hydrogen fuel supply.

16. A communication device for hydrogen fuel supply, deployed in hydrogen fuel mobility, a memory storing at least one command; and comprising a processor for executing at least one instruction; The processor, by means of at least one instruction, Broadcasting a Dispenser Discovery Protocol (DDP) request message via a communication network that includes a dispenser that supplies hydrogen to the above mobility, Receive a DDP response message from the dispenser including identification information of the dispenser on the communication network, Between the above mobility and the above dispenser, authentication for pairing between the above mobility and the above dispenser is performed using the identification information of the above dispenser in the above DDP response message. Communication device.

17. In paragraph 16, Before the above DDP request message is broadcast, the IP address of the mobility to be used in the communication network including the dispenser is determined, and the mobility is connected to the communication network via a communication channel based on the IP address of the mobility. Communication device.

18. In paragraph 16, The above DDP request message includes the pairing identifier (ID) of the mobility, The identification information of the dispenser included in the above DDP response message includes the pairing identifier (ID) of the dispenser, When authentication for pairing between the above mobility and the above dispenser is performed, Authentication for pairing between the mobility and the dispenser is performed using the pairing identifier of the mobility and the pairing identifier of the dispenser. Communication device.

19. In paragraph 18, When authentication for pairing between the above mobility and the above dispenser is performed, Using the pairing identifier of the above mobility and the pairing identifier of the above dispenser, authentication for pairing between the above mobility and the above dispenser is performed via a pairing channel different from the communication channel through which the above mobility is connected to the communication network. Communication device.

20. In paragraph 16, The identification information of the dispenser included in the above DDP response message is: including the IP address of the dispenser, the TCP port number of the dispenser, or the UDP port number of the dispenser. Communication device.

Images