Two-way communication method and device for hydrogen fuel supply

Abstract

A method according to one embodiment of the present invention comprises the steps of: discovering a dispenser for supplying hydrogen fuel to a moving body, allowing pairing information to be shared between the moving body and the dispenser, and pairing the moving body and the dispenser; allowing a communication protocol or a fuel supply protocol for a process in which the dispenser supplies hydrogen fuel to the moving body to be negotiated between the moving body and the dispenser based on interoperability or compatibility related information between the moving body and the dispenser; and transmitting, to the dispenser, information required to monitor and control a process in which the dispenser supplies the hydrogen fuel to the moving body performed based on the fuel supply protocol.

Description

Technical Field

[0001] This disclosure relates to communication technologies for supplying hydrogen fuel from charging stations or distributors to hydrogen fuel vehicles, and more specifically, to a hydrogen fuel supply process capable of improving the safety, compatibility, efficiency, and reliability of hydrogen fuel supply, a two-way communication method for the hydrogen fuel supply process, and an apparatus using the method. Background Technology

[0002] The description in this section provides only background information on embodiments of this disclosure and is not intended to specify prior art.

[0003] Hydrogen vehicles, or hydrogen-electric vehicles, are vehicles powered by electricity generated from the reaction of high-pressure hydrogen stored inside the vehicle with oxygen in the air, producing very little pollution. Most hydrogen-electric vehicles are powered by fuel cell systems that use hydrogen as an energy source. Hydrogen-electric vehicles not only emit pure water (H2O) vapor during power generation but also remove ultrafine dust from the air while driving, thus attracting attention as an environmentally friendly mode of transportation for the future. Because fuel (i.e., hydrogen) is abundant on Earth and the energy production process is environmentally friendly, hydrogen-electric vehicles are attracting significant attention as a potential technology for industrial applications.

[0004] Hydrogen fuel cell vehicles are mobile vehicles that use hydrogen as an energy source or use hydrogen as fuel to generate electricity to drive an electric motor. In addition to the hydrogen electric vehicles mentioned above, hydrogen fuel cell vehicles can include airborne vehicles and industrial trucks, trains, ships, and airplanes that use hydrogen as fuel to generate electricity and are powered by electricity.

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

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

[0007] Control schemes for supplying or providing hydrogen to hydrogen fuel cell vehicles are designed to control hydrogen refueling / supply so that the temperature and pressure of the compressed hydrogen storage system (CHSS) on the fuel cell side are maintained below certain temperature and pressure limits to ensure safety.

[0008] The hydrogen refueling / supply process, control schemes, and protocols in conventional hydrogen electric vehicles were defined before the wired / wireless communication or computing technologies used for control became mature, and therefore did not fully utilize the latest information and communication technologies (ICT). Consequently, conventional hydrogen refueling / supply subsystems in hydrogen electric vehicles are inefficient, slow, and unsuitable for large-scale hydrogen fuel supply.

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

[0010] [Technical Issues]

[0011] To address the aforementioned problems, one objective of exemplary embodiments is to provide a hydrogen fuel supply process and a communication protocol for the fuel supply protocol used in the process, overcoming the limitations and vulnerabilities of conventional one-way communication for hydrogen fuel vehicles during the hydrogen fuel supply process, and enhancing the safety, compatibility, efficiency, and reliability of the hydrogen fuel supply. Specifically, this includes: a negotiation communication protocol method for the hydrogen fuel supply process, a fuel supply protocol and fuel supply parameters, a monitoring and control method, a safety entry method, a safety exit method, and apparatus for implementing the above methods.

[0012] Another object of this disclosure relates to error handling methods and emergency handling methods for hydrogen fuel supply processes, and to apparatus for using such error handling methods and emergency handling methods to handle errors and / or emergencies that occur during communication protocol negotiation, fuel supply protocol negotiation, fuel supply parameter negotiation, monitoring and control, safety entry and safety exit processes in the hydrogen fuel supply process.

[0013] Another objective of the exemplary embodiments is to provide a two-way communication process for hydrogen fuel supply that allows hydrogen fuel vehicles and distributors to control a communication protocol negotiation process that considers conventional or advanced communication media, two-way / one-way communication, and means for implementing these processes in order to efficiently achieve the hydrogen fuel supply objective.

[0014] [Technical Solution]

[0015] According to an aspect of an exemplary embodiment, a communication method for hydrogen fuel supply can be performed by a hydrogen fuel vehicle. The communication method may include: discovering a distributor supplying hydrogen to the vehicle; sharing pairing information between the vehicle and the distributor; and performing pairing between the vehicle and the distributor; negotiating a communication protocol or fuel supply protocol between the vehicle and the distributor for the process of supplying hydrogen from the distributor to the vehicle based on interoperability or compatibility-related information between the vehicle and the distributor; and sending information necessary for monitoring and controlling the process of supplying hydrogen from the distributor to the vehicle based on the fuel supply protocol to the distributor.

[0016] Communication methods for hydrogen fuel supply may also include: establishing a secure channel between the mobile unit and the distributor after pairing is performed to negotiate a communication protocol or a fuel supply protocol.

[0017] The communication method for hydrogen fuel supply may further include: after negotiating a communication protocol or fuel supply protocol, and before the distributor supplies hydrogen fuel to the mobile body, performing an entry operation to check whether a first necessary safety condition between the mobile body and the distributor is met; and after supplying hydrogen from the distributor to the mobile body and before the nozzle is disengaged from the mobile body, performing an exit operation to check whether a second necessary safety condition between the mobile body and the distributor is met.

[0018] The communication method for hydrogen fuel supply may also include: detecting and handling non-safety-critical errors that occur during the negotiation of a communication protocol or fuel supply protocol, or when information required for monitoring and control is sent to the distributor; and detecting and handling emergencies that occur during the negotiation of a communication protocol or fuel supply protocol, or when information required for monitoring and control is sent to the distributor, in which interoperability between the distributor and the mobile body will be suspended.

[0019] Negotiation of communication protocols or fuel supply protocols may include: negotiating a communication protocol between the mobile unit and the distributor; negotiating a fuel supply protocol between the mobile unit and the distributor based on the communication protocol; and negotiating fuel supply parameters between the mobile unit and the distributor based on the fuel supply protocol.

[0020] During the negotiation of a communication protocol or fuel supply protocol, the information of the communication protocol or fuel supply protocol transmitted between the distributor and the mobile body may include at least one of the following: protocol name, index, version, priority, and preference.

[0021] The pairing information shared between the mobile entity and the distributor during the pairing process may include at least one of interoperability-related information and compatibility-related information between the mobile entity and the distributor.

[0022] Interoperability or compatibility information between the mobile body and the distributor can be updated based on status information during the negotiation of communication or fuel supply protocols, or when information required for monitoring and control is sent to the distributor. Based on the updated interoperability or compatibility information, the negotiation of communication or fuel supply protocols, or the sending of information required for monitoring and control to the distributor can be performed.

[0023] If a non-safety-critical error is detected during the negotiation of a communication protocol or fuel supply protocol, the negotiation of part or all of the communication protocol or fuel supply protocol shall be re-executed.

[0024] In the process of sending the information required for monitoring and control to the distributor, the information sent from the mobile body to the distributor can be determined based on whether the fuel supply agreement allows two-way communication between the mobile body and the distributor as a communication protocol.

[0025] According to an aspect of an exemplary embodiment, a communication method for hydrogen fuel supply can be performed by a communication device of a dispenser that supplies hydrogen to a hydrogen fuel vehicle. The communication method may include: discovering the vehicle, sharing pairing information between the vehicle and the dispenser, and performing pairing between the vehicle and the dispenser; negotiating a communication protocol or fuel supply protocol between the vehicle and the dispenser for the process of supplying hydrogen from the dispenser to the vehicle based on interoperability or compatibility-related information between the vehicle and the dispenser; and monitoring and controlling the process of supplying hydrogen from the dispenser to the vehicle based on the fuel supply protocol.

[0026] Communication methods for hydrogen fuel supply may also include: establishing a secure channel between the mobile unit and the distributor after pairing is performed to negotiate a communication protocol or a fuel supply protocol.

[0027] The communication method for hydrogen fuel supply may further include: after negotiating a communication protocol or fuel supply protocol, and before the distributor supplies hydrogen fuel to the mobile body, performing an entry operation to check whether a first necessary safety condition between the mobile body and the distributor is met; and after the process of supplying hydrogen from the distributor to the mobile body and before the nozzle disengages from the mobile body, performing an exit operation to check whether a second necessary safety condition between the mobile body and the distributor is met.

[0028] The communication method for hydrogen fuel supply may also include: detecting and handling non-safety-critical errors that occur during the negotiation of a communication protocol or fuel supply protocol, or during the monitoring and control of the process of supplying hydrogen from a distributor to a mobile vehicle; and detecting and handling emergencies that occur during the negotiation of a communication protocol or fuel supply protocol, or during the monitoring and control of the hydrogen fuel supply from a distributor to a mobile vehicle, in which interoperability between the distributor and the mobile vehicle will be suspended.

[0029] Negotiation of communication protocols or fuel supply protocols may include: negotiating communication protocols between the mobile unit and the distributor; negotiating fuel supply protocols between the mobile unit and the distributor based on the communication protocols; and negotiating fuel supply parameters between the mobile unit and the distributor based on the fuel supply protocols.

[0030] According to an aspect of an exemplary embodiment, a communication device for hydrogen fuel supply can be disposed in a hydrogen fuel vehicle. The communication device may include: a memory configured to store at least one command; and a processor configured to execute at least one command. The processor, through at least one command, can discover a distributor supplying hydrogen to the vehicle, share pairing information between the vehicle and the distributor, and perform pairing between the vehicle and the distributor; can negotiate a communication protocol or fuel supply protocol between the vehicle and the distributor for the process of supplying hydrogen from the distributor to the vehicle based on interoperability or compatibility-related information between the vehicle and the distributor; and can send information necessary for monitoring and controlling the process of supplying hydrogen from the distributor to the vehicle based on the fuel supply protocol to the distributor.

[0031] After pairing is performed, the processor can establish a secure channel between the mobile body and the dispenser through at least one command to negotiate a communication protocol or a fuel supply protocol.

[0032] The processor can perform an entry operation by at least one command, after the process of negotiating a communication protocol or a fuel supply protocol and before the dispenser supplies hydrogen to the mobile body, to check whether the first necessary safety condition between the mobile body and the dispenser is met, and can perform an exit operation by at least one command, after the process of supplying hydrogen from the dispenser to the mobile body and before the nozzle disengages from the mobile body, to check whether the second necessary safety condition between the mobile body and the dispenser is met.

[0033] The processor can detect and handle non-safety-critical errors that occur during the execution of a negotiation communication protocol or a fuel supply protocol, or during the process of sending information required for monitoring and control to the distributor, via at least one command. It can also detect and handle emergencies that occur during the execution of a negotiation communication protocol or a fuel supply protocol, or during the process of sending information required for monitoring and control to the distributor, in which interoperability between the distributor and the mobile body will be stopped.

[0034] When negotiating a communication protocol or a fuel supply protocol, the processor can negotiate the communication protocol between the mobile body and the distributor, negotiate the fuel supply protocol between the mobile body and the distributor based on the communication protocol, and negotiate the fuel supply parameters between the mobile body and the distributor based on the fuel supply protocol.

[0035] A communication device for supplying hydrogen fuel to a hydrogen fuel mobile body according to an embodiment of the present invention includes: a memory configured to store at least one command; and a processor configured to execute at least one command, wherein the processor, by executing the at least one command, can discover the mobile body, share pairing information between the mobile body and the distributor, and perform pairing between the mobile body and the distributor; can negotiate a communication protocol or fuel supply protocol with the mobile body for the process of supplying hydrogen fuel from the distributor to the mobile body based on interoperability or compatibility-related information between the mobile body and the distributor; and can monitor and control the process of supplying hydrogen fuel from the distributor to the mobile body based on the fuel supply protocol.

[0036] [Beneficial Effects]

[0037] According to the communication method for hydrogen fuel supply, the apparatus for implementing the method, namely, a hydrogen fuel supply controller or a communication controller, according to exemplary embodiments of the present disclosure, can overcome the limitations and vulnerabilities of conventional one-way communication for hydrogen fuel vehicles (including fuel cell electric vehicles (FCEVs) or hydrogen fuel engines) and communication protocols for fuel supply protocols in the process of hydrogen fuel supply, and can enhance the safety, compatibility, efficiency and reliability of hydrogen fuel supply.

[0038] Exemplary embodiments of this disclosure can provide a method for negotiating a communication protocol and exchanging communication parameters and communication protocol fallback rules for hydrogen fuel supply, wherein the mobile entity and the distributor can select the hydrogen fuel supply protocol and the communication protocol required to execute the hydrogen fuel supply protocol according to the use case, while considering priorities based on the preferences of the mobile entity or the distributor to maximize interoperability between the mobile entity and the distributor, and considering backward compatibility.

[0039] Exemplary embodiments of this disclosure can provide the rules and procedures required for communication protocol negotiation, fuel supply protocol negotiation, and fuel supply parameter exchange, enabling mobile entities and distributors to effectively cooperate in determining conventional or advanced communication media to effectively achieve hydrogen fuel supply objectives.

[0040] Exemplary embodiments of this disclosure may provide rules and procedures for monitoring and controlling, security entry and security exit processes, enabling mobile bodies and dispensers to cooperate and efficiently achieve hydrogen fuel supply targets.

[0041] Exemplary embodiments of this disclosure can provide rules and procedures for use cases, wherein the processes of monitoring and control, security entry and security exit, as well as the processes of communication protocol negotiation, fuel supply protocol negotiation and fuel supply parameter exchange are interconnected, thereby enabling the mobile body and the dispenser to cooperate and efficiently achieve the hydrogen fuel supply target.

[0042] Exemplary embodiments of this disclosure can provide rules and procedures for use cases where error handling and emergency handling processes are interconnected in a hydrogen fuel supply process, wherein error handling and emergency handling occur during communication protocol negotiation, fuel supply protocol negotiation, fuel supply parameter negotiation, monitoring and control, safety check-in and safety check-out processes, thereby enabling mobile bodies and dispensers to cooperate and efficiently achieve hydrogen fuel supply objectives. Attached Figure Description

[0043] Figure 1 This is a diagram of a hydrogen fuel supply system for a hydrogen-electric vehicle (FCEV) according to an exemplary embodiment of the present disclosure, the hydrogen fuel supply system being adapted to apply a two-way communication process to the hydrogen fuel supply; Figure 2 yes Figure 1 A partially enlarged view of the physical connection structure between the FCEV and the distributor in a hydrogen fuel supply system; Figure 3 It is shown in Figure 1 A diagram illustrating the state changes of hydrogen fuel during the hydrogen fuel supply process in a hydrogen fuel supply system; Figure 4 A framework of functional blocks for performing a series of hydrogen fuel supply processes according to an exemplary embodiment of the present disclosure is shown, which may employ a bidirectional communication process for hydrogen fuel supply. Figure 5 An example of a communication stack based on the Open Systems Interconnection Reference Model (OSI) Layer 7, according to an exemplary embodiment of this disclosure, is shown in relation to a use case that can be employed in bidirectional communication for hydrogen fuel supply. Figure 6 This is a sequence diagram illustrating a pairing process for a discovery and pairing procedure that can be employed in a two-way communication process for hydrogen fuel supply, according to an exemplary embodiment of this disclosure. Figure 7 An example of backward compatibility that can be employed in a two-way communication process for hydrogen fuel supply, according to an exemplary embodiment of the present disclosure, is shown. Figure 8 This is a table summarizing examples of backward compatibility applicable to bidirectional communication processes for hydrogen fuel supply according to exemplary embodiments of this disclosure; Figure 9 The use classification of communication data (UCDC) in a two-way communication process for hydrogen fuel supply according to an exemplary embodiment of this disclosure and the backward compatibility of the use classification of communication data are shown; Figure 10This is a sequence diagram illustrating the authentication process during a communication security procedure that can be employed in a two-way communication process for hydrogen fuel supply, according to an exemplary embodiment of this disclosure. Figure 11 This is a sequence diagram illustrating the communication protocol negotiation process that can be employed in a two-way communication process for hydrogen fuel supply according to an exemplary embodiment of this disclosure; Figure 12 This is a sequence diagram illustrating the fuel supply agreement negotiation process during a two-way communication process for hydrogen fuel supply, according to an exemplary embodiment of this disclosure; Figure 13 This is a sequence diagram illustrating a fuel supply parameter exchange / negotiation process that can be employed in a two-way communication process for hydrogen fuel supply according to an exemplary embodiment of this disclosure; Figure 14 This is a conceptual diagram illustrating a table of parameters transmitted from the mobile body side to the distributor side during a fuel supply parameter exchange / negotiation process, according to an exemplary embodiment of this disclosure. Figure 15 This is a conceptual diagram illustrating a table summarizing parameters transmitted from the distributor side to the mobile body side during a fuel supply parameter exchange / negotiation process according to an exemplary embodiment of this disclosure; and Figure 16 It is shown Figure 4 A flowchart of an alternative exemplary implementation.

[0044] Figure 17 This is a flowchart illustrating a communication method for hydrogen fuel supply according to another exemplary embodiment of the present disclosure.

[0045] Figure 18 This is a schematic block diagram illustrating the physical configuration of a general-purpose computing system according to an exemplary embodiment of the present disclosure. The general-purpose computing system can operate as a communication device, a communication controller, and / or an electronic controller for hydrogen fuel supply, and can be installed on a hydrogen fuel vehicle, a distributor, and / or a fuel supply station. Detailed Implementation

[0046] In addition to the objectives described above, another objective and feature of this disclosure will become more apparent from the description of exemplary embodiments with reference to the accompanying drawings.

[0047] To better understand the features and advantages of this disclosure, exemplary embodiments of this disclosure will be described in detail with reference to the accompanying drawings. However, it should be understood that this disclosure is not limited to the specific embodiments disclosed herein, but includes all modifications, equivalents, and substitutions falling within the spirit and scope of this disclosure.

[0048] The terms including ordinal numbers (such as “first” and “second”) specified in this specification for interpreting various components are used to distinguish components from other components, but are not intended to limit to any particular component. For example, a second component may be referred to as a first component without departing from the scope of this disclosure, and similarly, a first component may be referred to as a second component. As used herein, the term “and / or” can include the presence of one or more associated listed items and any and all combinations of the listed items.

[0049] In the description of exemplary embodiments of this disclosure, "at least one of A and B" can mean "at least one of A or B" or "at least one combination of one or more of A and B". Furthermore, in the description of exemplary embodiments of this disclosure, "one or more of A and B" can express "one or more of A or B" or "one or more combinations of one or more of A and B".

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

[0051] These terms are used herein for the purpose of describing specific exemplary embodiments only and are not intended to limit this disclosure. Unless the context clearly specifies otherwise, the singular form also includes the plural indicator. Moreover, the expressions “comprising,” “including,” “constructed,” and “configured” are used to refer to the presence of a combination of said features, quantities, processing steps, operations, elements, or components, but are not intended to exclude the presence or addition of another feature, quantity, processing step, operation, element, or component.

[0052] 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 disclosure pertains. Terms such as those commonly used as defined in dictionaries should be interpreted as having the same meaning as the term in the context of the relevant literature and should not be interpreted as having an ideal or overly formal meaning unless expressly defined in this application.

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

[0054] Hydrogen electric vehicles can generally include fuel cell electric vehicles (FCEVs) that use fuel cells and vehicles with internal combustion engines (ICEs) that use hydrogen as fuel. Hydrogen electric vehicles can also be abbreviated as FCEVs.

[0055] While embodiments relating to hydrogen fuel cell vehicles are described in detail below, hydrogen-powered ICE-based vehicles using hydrogen as fuel can be used in another embodiment of this disclosure. In the following description, the focus is on hydrogen fuel cell vehicles to describe hydrogen fuel supply protocols and / or hydrogen fuel supply communication protocols. However, hydrogen fuel supply protocols and / or hydrogen fuel supply communication protocols can also be applied to ICE-based hydrogen vehicles according to another embodiment of this disclosure.

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

[0057] "Compressed Hydrogen Storage System (CHSS)": An apparatus comprising at least one tank installed on a vehicle for compressing and storing hydrogen.

[0058] "Pressure relief device (PRD)": A device located in a CHSS that isolates stored hydrogen from the fuel supply system and other parts of the environment and releases the hydrogen to the outside.

[0059] "Hydrogen fuel supply": The process of supplying high-pressure hydrogen from a hydrogen fueling station distributor to a vehicle to store hydrogen in the vehicle's tank. In the context of supplying hydrogen fuel to hydrogen-electric vehicles, hydrogen fuel supply can also be referred to as "fuel supply." That is, the terms "fueling," "hydrogen fueling," or "charging" used herein can refer to the supply of hydrogen fuel. For example, a fuel supply agreement can be referred to as a fuel supply agreement, a fuel supply session can be referred to as a fuel supply session, and a fuel supply method can be referred to as a hydrogen fuel supply method or a fuel supply method.

[0060] "Pressure Rise Rate (PRR)": The rate at which CHSS pressure increases and is measured in megapascals per minute (MPa / min).

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

[0062] "Pre-cooling": The process of cooling hydrogen in a hydrogen fuel supply station before it is supplied with fuel.

[0063] "Distributor": A component that supplies pre-cooled hydrogen to the CHSS (Chemical Hydrogen Storage System). The distributor can be located at a hydrogen refueling station to perform hydrogen refueling operations between the hydrogen storage tank at that station and the CHSS of the vehicle.

[0064] "Nozzle": A hydrogen distribution system connected to a hydrogen fuel supply station, which can be coupled to a receiver in a hydrogen electric vehicle and supply hydrogen fuel to the hydrogen electric vehicle.

[0065] "Fuel Supply Session": A communication session that occurs across the entire use case for hydrogen fuel supply.

[0066] "Interoperability": The state in which components of a system are interconnected with corresponding components of the system to perform the desired operations. Furthermore, information interoperability can refer to the ability of two or more networks, systems, devices, applications, or components to effectively share and easily use information without causing inconvenience to users.

[0067] Related or associated processes may include the process of establishing a relationship between two peer communicating entities.

[0068] "Command and Control Communications": Communications used to exchange information required to start, control, and terminate the hydrogen fuel supply process between hydrogen distributors and hydrogen fuel vehicles.

[0069] Furthermore, although embodiments relating to hydrogen electric vehicles or fuel cell electric vehicles (FCEVs) are described in detail below, it will be apparent to those skilled in the art that the inventive concept of this disclosure can be applied to various types of hydrogen fuel cell vehicles. A hydrogen fuel cell vehicle is a vehicle that uses hydrogen as an energy source or uses hydrogen as fuel to generate electricity to drive an electric motor. In addition to the aforementioned hydrogen electric vehicles, hydrogen fuel cell vehicles may include airborne vehicles and industrial trucks, trains, ships, and aircraft that use hydrogen as fuel to generate electricity and are powered by that electricity.

[0070] In addition to hydrogen fuel vehicles, the two-way communication process for hydrogen fuel supply disclosed herein can also be applied in part to buildings or facilities that use hydrogen as an energy source.

[0071] In the following description, hydrogen fuel may include one or more of gaseous or liquid hydrogen. Hydrogen fuel essentially refers to compressed hydrogen, but is not limited to this.

[0072] Furthermore, although a two-way communication process for hydrogen fuel supply is described for the purposes of explanation in relation to hydrogen electric vehicles (FCEVs), this disclosure is not limited thereto, and the two-way communication process for hydrogen fuel supply can also be applied to hybrid electric vehicles (EVs) or ICE-based vehicles that use hydrogen as fuel.

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

[0074] In the following description, some or all of the processes of the communication method, communication protocol negotiation method, hydrogen fuel supply protocol negotiation method, hydrogen fuel supply parameter negotiation method, hydrogen fuel supply method, and hydrogen fuel supply control method performed by the distributor may also be performed by the distributor's controller, electronic control unit, communication device, or communication controller. Alternatively, some processes of the above methods may be performed by the controller, electronic control unit, communication device, or communication controller of the fuel supply station associated with the distributor.

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

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

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

[0078] Figure 1 This is a diagram of a hydrogen fuel supply system for a hydrogen-electric vehicle (FCEV) according to an exemplary embodiment of the present disclosure, the hydrogen fuel supply system being adapted to apply a two-way communication process to the hydrogen fuel supply. Figure 2 yes Figure 1 A magnified view of the physical connection structure between the FCEV and the distributor in a hydrogen fuel supply system. Figure 3 It is shown in Figure 1 A diagram illustrating the state changes of hydrogen fuel during the hydrogen fuel supply process in a hydrogen fuel supply system.

[0079] See Figure 1 A hydrogen fuel supply system can typically be configured to include a hydrogen fuel supply station and a hydrogen fuel vehicle 100.

[0080] In addition to the basic mechanical, electrical, electronic, and communication devices required for a vehicle, the hydrogen fuel cell 100 may be equipped with an electronic controller 110, a cell system 120, a cell tank 130, and a refueling port 150 for hydrogen fuel supply.

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

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

[0083] At least one mobile tank 130 may be present in the vehicle, preferably multiple mobile tanks 130. The mobile tank 130 can compress and store hydrogen supplied from the hydrogen refueling station under the control of the vehicle safety system, and can discharge the stored hydrogen.

[0084] Furthermore, the mobile tank 130 can correspond to a hydrogen storage system installed in a vehicle. In this case, the hydrogen storage system may include a high-pressure hydrogen storage tank, a pressure control device, a high-pressure pipe, and an external frame. The high-pressure hydrogen storage tank may have a capacity of tens to hundreds of liters and may have a shape with smaller storage tanks connected in parallel. A boss unit that allows hydrogen fuel to pass through can be integrated into the high-pressure hydrogen storage tank, and thus the supply and discharge of hydrogen can be controlled through the boss unit. The boss unit may include valves, pressure reducing devices, and various sensors for measurement. This hydrogen storage system is referred to as a compressed hydrogen storage system (CHSS). For ease of explanation, the term "mobile tank 130" as used herein may refer to a CHSS.

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

[0086] A hydrogen fuel supply station may include a distributor 200, an electronic controller 210, a fuel supply station system 220, a hydrogen tank 230, a station box 240, and a nozzle 250.

[0087] Distributor 200, under the control of fuel supply station system 220, supplies hydrogen from hydrogen tank 230 to the vehicle via nozzle 250, which is securely coupled to refueling port 150 of the vehicle. Distributor 200 may include an electronic controller 210 within a housing, but this disclosure is not limited thereto. Nozzle 250 may be mounted at the end of a cable that extends a certain length outside the housing of distributor 200.

[0088] Electronic controller 210 can transmit and receive signals and data from the vehicle's first electronic controller 110 via wired or wireless communication, and process the signals and data to control the hydrogen fuel supply at the hydrogen fuel supply station. Electronic controller 210 can exchange prescribed signals and data with the fuel supply station system 220. Electronic controller 210 can also be referred to as a second electronic controller or electronic control unit #2.

[0089] Each of the first electronic controller 110 and the second electronic controller 210 may consist of multiple electronic control units and may be configured such that each communication protocol can be executed by a different electronic control unit. Such a configuration may be useful when fallback is used for backward compatibility and when bidirectional communication is not possible and unidirectional communication can be used instead. Furthermore, this configuration may be useful when using a combination of different communication methods, for example, when NFC is used for pairing and WiFi is used for actual fuel delivery.

[0090] The fuel supply station system 220 can monitor or control the pressure, rate, and temperature of hydrogen discharged from the hydrogen tank 230 based on signals and / or data from a second electronic controller. For this purpose, the fuel supply station system 220 can control the operation of the station container 240 connected to the discharge port or discharge valve of the hydrogen tank 230. The fuel supply station system 220 can also be referred to as a fuel supply station safety system.

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

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

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

[0094] The station 240 may be equipped with a control valve having an inlet connected to a discharge port or discharge valve of the hydrogen tank 230 and an outlet connected to or coupled to a nozzle 250 of the distributor 200. The station 240 may be equipped with a device or another component for controlling the pressure, rate, and temperature of the discharged hydrogen. Furthermore, the station 240 may be equipped with sensors for measuring the pressure, rate, and temperature of the discharged hydrogen.

[0095] The nozzle 250 can be connected to the hydrogen fuel supply system of the dispenser 200 via a conduit or flexible tube of a predetermined length. The nozzle 250 may be configured with a shape and structure that fits snugly and securely into the vehicle's refueling port.

[0096] like Figure 2 As shown, nozzle 250 can engage with filler port 150. A first sensor 160 installed in the vehicle and a second sensor 260 attached to nozzle 250 can send signals or information about the coupling status of nozzle 250 and filler port 150 to a first electronic controller or vehicle safety system and to a second electronic controller or fuel supply station safety system.

[0097] Pre-cooled hydrogen fuel can be supplied from the hydrogen fuel supply station to the hydrogen fuel vehicle 100 via distributor 200. At this time, the hydrogen fuel supply process can be described by parameters including pressure rise rate (PRR) and / or average pressure rise rate (APRR).

[0098] Distributor 200 can act as the interface between the hydrogen fuel supply station and the mobile unit 100. Distributor 200 can be configured to control the target pressure and injection rate for hydrogen fuel supply based on information indirectly obtained from the mobile unit tank 130 and fuel supply information from the hydrogen fuel supply station.

[0099] Traditionally, there are two methods for transmitting information from mobile body 100 to distributor 200: a communication method and a non-communication method. In the communication method, the temperature and pressure values ​​of the mobile body tank 130 of mobile body 100 are transmitted unidirectionally to distributor 200, and distributor 200 does not actively utilize this information, but only uses it as a safety reference for, for example, emergency stops at temperature or pressure limits. Furthermore, the hydrogen fuel supply protocol for safe and rapid fuel supply is managed by distributor 200, which has only minimal safety management devices that automatically release hydrogen via a pressure relief device (PRD), without any active safety management schemes for mobile body tank 130.

[0100] Meanwhile, in order to handle hydrogen temperatures at Figure 3 The hydrogen fuel supply station can be equipped with a precooler to address the increased phenomena observed during the hydrogen fuel supply process. This precooler can reduce the temperature of the hydrogen fuel through precooling. The precooler can be installed in or combined with one or more of the hydrogen tanks 230 and station containers 240. Alternatively, the precooler can be installed in or combined with the pipeline that transports hydrogen within the hydrogen fuel supply station.

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

[0102] As described above, the hydrogen fuel supply process between the hydrogen fuel vehicle 100 and the hydrogen fuel supply station is controlled by the distributor 200, and the distributor 200 may include a protocol for supplying hydrogen fuel to the vehicle according to a prescribed procedure. This hydrogen fuel supply protocol may also be installed in the vehicle. The protocol installed in the vehicle or distributor 200 may include at least some of the communication protocols based on SAE standards, ISO standards, and similar standards.

[0103] For minimum safety requirements, simulations based on thermodynamic modeling can be performed for various scenarios, and partial real-time corrections based on tables or MC formulas can be performed using parameters derived from the simulations. Minimum safety requirements may include upper limits on temperature and pressure conditions for CHSS and guidance on fuel supply rate (SOC).

[0104] In the absence of active control over state values ​​related to hydrogen fuel supply in distributor 200, table-based correction has disadvantages and can exhibit very low efficiency because it does not utilize the temperature of pre-cooled hydrogen fuel supplied by the fuel supply station or the temperature of the mobile tank 130 measured in mobile 100, and therefore may be difficult to respond flexibly to changes in ambient conditions. Correction based on the MC-formula allows for real-time compensation of the pre-cooled hydrogen fuel temperature, but the calculation and application of this method are complex, which may limit its application and make it difficult to scale. Therefore, conventional communication protocols developed with the primary objective of safely completing fuel supply cannot proactively respond to unexpected situations (such as over-pre-cooling or overheating of mobile tank 130) and may lead to problems such as increased operating costs due to overcooling and delayed fuel supply due to overheating.

[0105] For example, when hydrogen fuel is filled into the mobile tank 130, the internal temperature of the mobile tank 130 rises due to the heat of compression, and consequently, the temperature of the hydrogen fuel inside the mobile tank 130 rises. The mobile tank 130 is designed such that its dome and body are wrapped with carbon fiber, which has low thermal conductivity, to prevent heat exchange between the external atmosphere and the hydrogen fuel stored inside the mobile tank 130. Therefore, during fuel supply, as the temperature of the hydrogen fuel inside the mobile tank 130 rises, the temperature rise on the surface of the mobile tank 130 is smaller compared to the temperature rise until the fuel supply is complete, due to the low thermal properties of the mobile tank 130.

[0106] Simultaneously, temperature control during the hydrogen fuel supply process can be designed to ensure that the internal temperature of the mobile tank 130 remains below 85°C upon completion of fuel supply by supplying pre-cooled hydrogen. During the hydrogen fuel supply process, the temperature of the hydrogen fuel can undergo changes according to… Figure 3 The characteristic curves shown depict the changes in temperature. The temperature of the hydrogen fuel can decrease at a constant rate in stage 1 (P1), which is the pre-cooling stage of the hydrogen fuel supply station. In stage 2 (P2), during which hydrogen fuel is supplied from the hydrogen fuel supply station to a hydrogen mobile body such as a vehicle, the temperature of the hydrogen fuel gradually increases due to the thermal mass of the hydrogen fuel supply station. In stage 3 (P3), during which hydrogen fuel is transferred from inside the vehicle to the mobile body tank 130, the temperature of the hydrogen fuel increases at a higher rate due to the thermal mass of the vehicle. In stage 4 (P4), during which the hydrogen fuel is compressed and stored in the mobile body tank 130, the temperature of the hydrogen fuel may increase rapidly due to the heat of compression.

[0107] According to this embodiment, the hydrogen fuel supply process can be effectively executed via a two-way communication process for hydrogen fuel supply through active state variable control that reflects real-time measurement data. Furthermore, a hydrogen fuel supply protocol for this process can be provided.

[0108] Figure 4 A framework of functional blocks for performing a series of hydrogen fuel supply processes (hereinafter referred to as the "hydrogen fuel supply framework") according to an exemplary embodiment of the present disclosure is shown, which may employ a bidirectional communication process for hydrogen fuel supply.

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

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

[0111] Use cases UC10 and UC11 can be individually connected to use cases UC3 through UC8 and error handling and / or emergency handling can be performed in each use case.

[0112] The use cases are functional blocks designed for safe and reliable fuel supply communication, providing a consistent framework for the entire hydrogen fuel supply system's hydrogen fuel supply process. Vehicles and dispensers can execute these use cases sequentially to achieve hydrogen fuel supply.

[0113] After the dispenser nozzle is coupled to the vehicle's filler neck, the vehicle and dispenser can communicate via... Figure 4 The sequence shown implements use cases for performing fuel supply communication. However, some use cases can be omitted from the vehicle and dispenser according to predetermined requirements if necessary.

[0114] Each of the above use cases can be achieved through communication between a distributor control system that supplies hydrogen as fuel to the hydrogen fuel vehicle according to a fuel supply agreement for hydrogen fuel vehicles and the hydrogen fuel vehicle.

[0115] Simultaneously, the hydrogen fuel supply vehicle (hereinafter also referred to as the "vehicle") and the dispenser implementing the use case can perform data exchange to identify the vehicle in use case UC-1. For this purpose, the vehicle can be equipped with sensors, an electronic control unit (ECU), a transmitter, and a receiver. In the case of bidirectional communication, the receiver can be integrated with the transmitter.

[0116] The dispenser can be configured to receive specific data from the vehicle. The dispenser can store this specific data in the programmable logic controller (PLC) of the fuel supply station for data logging or use in the fuel supply protocol. Data logging can refer to the process of collecting data over a period of time to analyze a certain operational state of the hydrogen fuel supply system or recording data-based events / operations of the system or network environment, or data collected by such a process. In the case of two-way communication, the fuel supply station can be equipped with sensors defined by the fuel supply protocol, and the PLC or the fuel supply station's electronic control unit can acquire measurements from the sensors and transmit these measurements to the vehicle. The vehicle or fuel supply station can use conventional communication protocol standards for communication, such as infrared communication, WiFi, and Bluetooth.

[0117] Furthermore, a vehicle or distributor can establish a communication channel with itself, physically coupled at its vehicle-to-distributor interface. The pairing process for establishing such a communication channel can be performed using wired, optical, or wireless communication technologies.

[0118] The discovery and pairing procedure or pairing process may have the prerequisite that the dispenser nozzle is inserted and securely coupled to the vehicle's fuel supply filler port. The vehicle's fuel supply filler port may be simply referred to as the vehicle filler port or filler port.

[0119] Furthermore, vehicles and distributors typically know by default which communication protocol to follow. Therefore, communication performed following use case UC-1 can rely solely on the agreed-upon communication protocol in the current use case as a subsequent condition for the discovery and pairing procedure or pairing process. If the vehicle or distributor selects a communication protocol outside the agreed-upon scope, the selected communication will not be performed. That is, even if the pairing process is successfully completed, fuel supply will not be authenticated.

[0120] All methods used to pair vehicles with distributors can be configured not to increase the risk of fire or explosion to an acceptable level. For example, all wired pairing methods can be configured to mitigate or prevent the hazard of sparks caused by electrostatic discharge.

[0121] Regarding the effectiveness of physical pairing, any method used to pair a vehicle with a dispenser can be integrated into the vehicle-dispenser interface or installed to maintain proximity between the vehicle's fuel supply inlet and the dispenser's nozzle and hose assembly. Here, the interface can refer to something physically integrated into the interface between the nozzle and the inlet. Proximity can be defined by the hardware associated with the pairing method. For example, the physical geometry for infrared communication can be specified, including the permissible distance between the transmitter and receiver. Furthermore, the physical geometry of the hydrogen fuel supply hardware can be predefined, in which case proximity does not include the pairing method, which could lead to the risk of associating the dispenser with a vehicle not physically coupled to the dispenser, such as long-range wireless communication technologies like Bluetooth. Infrared communication can be referred to as Infrared Data Association (IrDA) communication and can include bi-directional infrared (bi-IrDA) communication.

[0122] Refer again Figure 4 A communication method for hydrogen fuel supply, which can be executed by a communication device of a hydrogen fuel vehicle according to an exemplary embodiment of the present disclosure, may include: an operation of negotiating a communication protocol with a distributor that supplies hydrogen to the vehicle (S403); an operation of negotiating a fuel supply protocol with the distributor to supply hydrogen from the distributor (S404); and an operation of negotiating fuel supply parameters with the distributor based on the fuel supply protocol (S405).

[0123] A communication method for supplying hydrogen fuel, performed by a distributor that supplies hydrogen to a hydrogen fuel vehicle according to an exemplary embodiment of the present disclosure, may include: negotiating a communication protocol with the hydrogen fuel vehicle (S403); negotiating a fuel supply protocol with the hydrogen fuel vehicle to supply / provide hydrogen to the hydrogen fuel vehicle (S404); and negotiating fuel supply parameters of the supplied hydrogen based on the fuel supply protocol (S405).

[0124] Figure 5 An example of a communication stack based on the Open Systems Interconnection Reference Model (OSI) Layer 7, according to an exemplary embodiment of this disclosure, is shown in relation to a use case that can be employed in bidirectional communication for hydrogen fuel supply.

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

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

[0127] In addition, the hydrogen fuel supply communication stack can include Internet Protocol version 6 (IPv6) Protocol 520 as a network layer protocol of OSI layer 7.

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

[0129] Furthermore, the hydrogen fuel supply communication stack may include at least one fourth protocol 540 selected from Transport Layer Security (TLS), Datagram Transport Layer Security (DTLS), etc., as a security layer of OSI 7. TLS may include versions such as TLS 1.2 and TLS 1.3, and DTLS may include versions such as DTLS 1.2 and DTLS 1.3. TLS can be implemented over TCP sockets, while DTLS can be implemented over UDP sockets.

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

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

[0132] Furthermore, the hydrogen fuel supply communication stack can include a fuel supply protocol FP 570 related to hydrogen fuel supply as an application layer protocol of OSI 7 layer. Fuel supply protocol 570 can include a first fuel supply protocol FP1, a second fuel supply protocol FP2, and an nth fuel supply protocol FP n, where "n" can be a natural number greater than or equal to 3.

[0133] In an alternative implementation, the hydrogen fuel supply communication stack may include power line communication (PLC) or WLAN as a data link and physical and network layer protocol; TCP and / or IPv6 as a transport and security layer protocol; Extensible Markup Language (XML) as a session layer protocol; and one of the existing protocols used in electric vehicles as a presentation and application layer protocol. The existing protocols used in electric vehicles may include at least one protocol for DC charging, AC charging, wireless power transfer (WPT), and automatic docking device pantograph charging (ACDP) for electric vehicles.

[0134] The communication data items that can be exchanged between vehicles and fuel supply stations via the hydrogen fuel supply communication stack can be summarized as shown in Table 1.

[0135] [Table 1]

[0136] at the same time, Figure 4 The discovery and pairing procedure (S401) in use case UC1 enables the device to identify the communication counterpart (i.e., the vehicle's communication module or distributor) responsible for controlling the filling port or nozzle physically coupled to the device. Furthermore, use case UC1 can also define incompatibility identification methods and safety device mechanisms.

[0137] In use case UC1, the vehicle and dispenser may attempt to find a common communication technology to execute the fuel supply protocol. The vehicle and dispenser can discover each other and initiate communication based on discovery mechanisms provided by the data link and physical layer. Additional pairing procedures may be required to establish a communication channel with devices connected to the fuel supply hose assembly. In cases where proper pairing cannot be guaranteed, such as in the case of wireless communication, a separate pairing channel may be needed to send pairing information. However, if pairing is implicitly guaranteed, the communication channel integrated with the hose assembly may be sufficient, for example.

[0138] Table 2 shows Figure 4 The objectives, prerequisites, and follow-up conditions of use case UC1 for the discovery and pairing operation (S401) shown.

[0139] [Table 2]

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

[0141] [Table 3]

[0142] Figure 6 This is a sequence diagram showing in detail the operation S401 according to an exemplary embodiment of the present disclosure.

[0143] refer to Figure 6 ,exist Figure 4 During the pairing process of the discovery and pairing operation (S401) shown, the vehicle and the distributor can exchange pairing IDs with each other and discover the corresponding pairing ID during UCDC Level 2 and UCDC Level 3 pairing.

[0144] For example, a vehicle can broadcast a message PAIR_ID_ANNOUNCE containing its pairing ID (PAIR_ID) (i.e., vehicle ID) (in operation S710). The distributor can send a message PAIR_ID_ACK to the vehicle to acknowledge receipt of the vehicle ID (in operation S720). The vehicle can send a message PAIR_ID_CONFIRM to the distributor to acknowledge receipt of the ACK message (in operation S730).

[0145] Next, the distributor can broadcast a message PAIR_ID_ANNOUNCE containing its pairing ID (i.e., the distributor ID) (in operation S740). The vehicle can send a message PAIR_ID_ACK to the distributor to acknowledge receiving the distributor ID from the distributor (in operation S750). The distributor can send a message PAIR_ID_CONFIRM to the vehicle to acknowledge receiving the ACK message from the distributor (in operation S760).

[0146] This transport-echo authentication method enables vehicles and distributors to use session-specific randomized pairing IDs. This method helps address privacy concerns associated with the exchange of pairing IDs. Specifically, trust established during the pairing process can be built through subsequent processes, and for this purpose, session-specific pairing IDs can be included in the data used to establish trust.

[0147] Additionally, when supporting secure communication at a specific UCDC level, one or more of the vehicles or dispensers can verify that the pairing provides sufficient information to secure the communication channels for all methods used to pair the vehicle with the dispenser. For example, pairing may include the exchange of keys, enabling the vehicle and dispenser to ensure communication during fuel supply.

[0148] It is important to note that because UCDC Level 1 does not support bidirectional communication, it may not guarantee the security of the communication channel. Pairing vehicles and distributors at UCDC Levels 2 and 3 can be configured to provide sufficient information to ensure communication security meets a specific security level (e.g., IEC 62443 security level 3). IEC 62443 security level 3 can be a security level for actors with sufficient resources and motivation.

[0149] Figure 7 An example of backward compatibility that can be employed in bidirectional communication for hydrogen fuel supply according to an exemplary embodiment of this disclosure is shown.

[0150] See Figure 7 Considering interoperability, hydrogen fuel supply units can be designed to be backward compatible with existing units. Hydrogen fuel supply units or communication devices within hydrogen fuel supply units can be classified into Type 0, Type 1, Type 2, and Type 3 based on interoperability.

[0151] Type 0 devices may refer to devices that do not support fuel supply communication or cannot receive related communication messages.

[0152] Type 1 devices can refer to devices that support IrDA communication for fuel supply. Type 1 devices can revert to Type 0 devices.

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

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

[0155] Advanced communication can refer to communication using specific protocols and media, such as wireless local area networks (WLAN), Bluetooth (BT), near field communication (NFC), WiFi, ultra-wideband (UWB), radio frequency identification (RFID), 4G, and 5G. Furthermore, advanced communication can include bidirectional IrDA, serial communication, vehicle Ethernet (ETH), high-level communication, etc. Specific protocols can include Transmission Control Protocol / Internet Protocol (TCT / IP), fuel supply protocols, etc. High-level communication can handle all the information beyond that handled by command and control communication. The data link for high-level communication can use power line communication (PLC), but this disclosure is not limited thereto.

[0156] Advanced communication can include hybrid forms, such as a combination of IrDA communication and wired communication, or a combination of IrDA communication and wireless communication. A combination of IrDA communication and wired communication may require modifications to the nozzle and filling port.

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

[0158] In practice, hydrogen fuel supply devices can be implemented to support different communication schemes. Therefore, the bidirectional communication process for hydrogen fuel supply according to this embodiment can be configured to maximize interoperability between devices.

[0159] In other words, such as Figure 7 As shown, when a Type 1 device that supports specification #1 according to a specific standard satisfies a Type 0 device or a Type 2 device, a Type 1 device can fall back to Type 0 (S610).

[0160] Furthermore, when a Type 2 device that supports Specification #2 according to a specific standard satisfies a Type 0 device or a Type 1 device, the Type 2 device can revert to Type 0 (S620).

[0161] Furthermore, when a Type 3 device supporting Specification #2 satisfies the requirements of a Type 0 device, the Type 3 device can fall back to Type 0 (S630). When a Type 3 device satisfies the requirements of a Type 1 device, the Type 3 device can fall back to Type 1 (S640). When a Type 3 device satisfies the requirements of a Type 2 device, the Type 3 device can fall back to Type 2 (S650).

[0162] The aforementioned specification #1 may include specifications based on the Society of Automotive Engineers (SAE) standards. Specification #2 may include specifications based on the ISO 19885-3 standard.

[0163] To support the interoperability described above, the hydrogen fuel supply unit can perform connectivity compatibility checks. For example, depending on whether each unit supports WLAN as one of the advanced communication schemes, connectivity compatibility checks can be performed according to cases 1 through 3 below.

[0164] In scenario 1, the distributor can be equipped with an access point (AP), i.e., a wireless router. The access point can emit beacon signals, enabling vehicles to access the fuel supply station and xVSE (xVehicle Supply Equipment). FCEVs approaching the distributor can scan for and discover it, and can establish a WLAN link with it.

[0165] In scenario 2, the distributor does not support bidirectional WLAN, but instead supports unidirectional IrDA. The distributor corresponds to a type 1 device. An FCEV (which is a type 3 device) approaching the distributor cannot scan for or discover the distributor (which is a type 1 device). IrDA communication can be initiated between the FCEV and the distributor when the nozzle of the cable attached to the distributor is coupled to the filling port of the FCEV.

[0166] In scenario 3, the distributor can support both bidirectional WLAN communication and unidirectional IrDA communication. In this case, the distributor corresponds to a Type 3 device. The FCEV (which is a Type 1 device) may be parked near the distributor. The distributor still cannot find any WLAN clients. IrDA communication can be initiated between the FCEV and the distributor when the nozzle of the cable attached to the distributor is coupled to the filling port of the FCEV.

[0167] Figure 8 This is a table summarizing examples of backward compatibility applicable to bidirectional communication processes for hydrogen fuel supply according to exemplary embodiments of this disclosure.

[0168] refer to Figure 8 The bidirectional communication process for hydrogen fuel supply according to this embodiment can provide rules and principles for backtracking when selecting fuel supply methods and communication protocols to maximize interoperability, rather than selecting the most preferred communication scheme for FCEVs or distributors.

[0169] In other words, when vehicles or distributors encounter each other, a device with a relatively high type or UCDC level can be configured to revert to the type or level of a device with a relatively low type or UCDC level.

[0170] For example, if the vehicle and the dispenser are of the same type or the same UCDC level, the two 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, the two devices can be configured to fall back to type 0. Meanwhile, if one device is a type 3 device and the other is not a type 3 device, the type 3 device can be configured to fall back to the same type or UCDC level as the other device.

[0171] The aforementioned specification #1 may be a communication protocol based on the SAE standard, and specification #2 may be a communication protocol based on the ISO 19885 standard.

[0172] Under the above configuration, if the mobile unit and the distributor have common or identical type implementations, the mobile unit and the distributor can choose the type supported by both devices, and this type is the best among these types. When a device without communication capabilities (hereinafter referred to as a "non-communication device") encounters a device that supports unidirectional communication (hereinafter simply referred to as a "unidirectional communication device"), the latter can fall back to the non-communication device that does not support any communication scheme. When two devices supporting bidirectional communication meet each other, the two devices can maintain their original bidirectional communication scheme. Here, UCDC-level compatibility can be handled separately. When a device encounters a non-communication device, the device must rely on the non-communication device. This rule can be applied to all devices that support bidirectional communication (hereinafter simply referred to as "bidirectional communication devices").

[0173] Furthermore, when a unidirectional communication device encounters a bidirectional communication device, if the bidirectional communication device supports both unidirectional and bidirectional communication schemes, the bidirectional communication device can revert to the unidirectional communication scheme. If the bidirectional communication device does not support unidirectional communication, it can revert to a no-communication scheme.

[0174] The aforementioned two-way communication device, regardless of whether it possesses one-way communication capability, can support fuel supply methods based on one-way communication. The two-way communication device needs to be able to check whether the corresponding device supports two-way communication. If the corresponding FCEV (or mobile vehicle) and / or distributor does not support two-way communication, the two-way communication device can revert to a one-way communication device that relies on a one-way communication scheme compatible between the devices.

[0175] Figure 9 The use classification of communication data (UCDC) in a two-way communication process for hydrogen fuel supply according to an exemplary embodiment of this disclosure is shown, along with backward compatibility of the use classification of communication data.

[0176] like Figure 9 As shown, mobile entities and distributors can have corresponding pairing identities (IDs), and the requirements for exchanging IDs can be categorized using a classification of communication data (UCDC) levels. UCDC levels can have UCDC level 1 (UCDC-1) 910, UCDC level 2 (UCDC-2) 920, and UCDC level 3 (UCDC-3) 930. UCDC levels can also include UCDC level 0 (UCDC-0) 900.

[0177] In UCDC Level 0 (UCDC-0) 900, data is not transmitted. Even if data is transmitted, the transmitted data is not used for the hydrogen fuel supply agreement or associated with safety functions. In UCDC Level 0 (900), because no communication is performed between the mobile unit and the distributor, the distributor cannot send the pairing ID to the mobile unit during process control or safety functions.

[0178] When attempting pairing at UCDC Level 1 (UCDC-1) 910, the mobile entity can send a pairing ID to the distributor. Although the data transmitted at UCDC Level 1 (UCDC-1) 910 is not used for safety functions, the static data transmitted can be used to improve the performance of the fuel supply protocol, and the dynamic data transmitted can be used to reduce the risk of resisting process deviations during the fuel supply protocol.

[0179] Static data communicated at UCDC Level 2 (UCDC-2) 920 can be used for security functions. UCDC Level 2 static data (UCDC-2) 920 can be data added to the static and dynamic data defined for permitted use at UCDC Level 1.

[0180] Static and dynamic data at UCDC Level 3 (UCDC-3) 930 can be used for dynamic control of the protocol or for security functions. Dynamic data at UCDC Level 3 (UCDC-3) 930 can be data added to static data and dynamic data defined for permitted use at UCDC Level 2.

[0181] As described above, UCDC levels can have a structure where UCDC level 1 is included in UCDC level 2 and UCDC level 2 is included in UCDC level 3, that is, higher levels include lower levels. A device supporting a certain UCDC level can support devices supporting lower UCDC levels. Devices capable of supporting different UCDC levels can use the highest UCDC level supported by both devices. The aforementioned UCDC levels can also easily support UCDC level 0. Therefore, UCDC levels are backward compatible. In another embodiment of this disclosure, backward compatibility can be effectively applied to each or a combination of non-comm, uni-directional Comm, and bi-directional Comm communication schemes, regardless of the UCDC level.

[0182] Let's refer to each other. Figures 4 to 8 , can Figure 4The discovery and pairing operation (S401) shown herein shares information related to interoperability and / or compatibility between the mobile body / mobile body and the distributor. Information related to interoperability and / or compatibility may be utilized in the communication protocol negotiation operation (S403), fuel supply protocol negotiation operation (S404), and / or fuel supply parameter negotiation operation (S405), which will be described below.

[0183] In another exemplary embodiment of this disclosure, the communication protocol negotiation operation (S403), fuel supply protocol negotiation operation (S404), and / or fuel supply parameter negotiation operation (S405) can be updated or shared again. Figure 4 The discovery and pairing operation (S401) shown illustrates information related to interoperability and / or compatibility shared between the mobile unit / mobile unit and the distributor. This interoperability and / or compatibility information can be updated due to changes in the communication environment, changes in parameters affecting the fuel supply process, etc.

[0184] In another exemplary embodiment of this disclosure, Figure 4 At least a portion of the discovery and pairing operation (S401) shown can be referred to as the Distributor Discovery Protocol (DDP).

[0185] DDP can be initiated via a DDPRequest message broadcast by the hydrogen fuel cell vehicle. The DDPRequest can include the pairing ID of the hydrogen fuel cell vehicle, "pairing_id".

[0186] The allocator can receive DDP request messages (DDPRequest) and respond to them by sending DDP response messages (DDPResponse). The DDP response message (DDPResponse) can include the allocator's IP address "IPAddr", the allocator's TCP port number "TCPPort", the allocator's UDP port number "UDPPort", and the allocator's pairing ID "pairing_id".

[0187] Figure 10 This is a sequence diagram illustrating an authentication process during a communication security procedure (S402) that can be employed in a two-way communication process for hydrogen fuel supply according to an exemplary embodiment of this disclosure.

[0188] See Figure 10 The hydrogen fuel cell vehicle can request a list of authentication methods from the dispenser (S1010). The dispenser can send a response message to the hydrogen fuel cell vehicle requesting the list of authentication methods (S1020). The response message may include a list of authentication methods related to self-authentication or external authentication (such as RFID, credit card, or debit card).

[0189] Next, the hydrogen fuel vehicle can send an authentication request message to the dispenser, which includes an authentication method selected from a list of authentication methods such as RFID (S1030). The dispenser can then send a response message to the hydrogen fuel vehicle in response to the authentication request (S1040). The response message may include information indicating that authentication using the authentication method selected by the hydrogen fuel vehicle is in progress.

[0190] The hydrogen fuel cell vehicle can then wait for a response containing the authentication result from the dispenser and can send an authentication result request message (Completion?) to the dispenser for the selected authentication method (S1050). If no authentication result is received or authentication is not completed, operations S1010-S1050 can be repeated. After authentication is completed, the dispenser can send an authentication completion message ("Completion (Success)") to the hydrogen fuel cell vehicle (S1090).

[0191] According to the method described above, the dispenser can verify whether the hydrogen fuel vehicle is certified, that is, whether the user of the hydrogen fuel vehicle has the right to hydrogen fuel supply, before continuing the hydrogen fuel supply process.

[0192] To ensure the security of the authentication process, after establishing a data link and physical layer connection between the hydrogen fuel vehicle and the distributor, one or more hydrogen fuel supply devices, including the hydrogen fuel vehicle or distributor, can establish a transport layer connection (i.e., a TCP connection) and then perform a TLS handshake to authenticate and exchange keys, thereby establishing a secure communication channel. During the exchange of critical information for security purposes, User Datagram Protocol (UDP) communication protected by Datagram Transport Layer Security (DTLS) can be used.

[0193] Furthermore, the hydrogen fuel cell vehicle and the distributor can perform discovery and pairing procedures and establish connections at the data link and physical layer. The credentials required for authentication and key exchange can then be prepared. Therefore, the communication channel between the hydrogen fuel cell vehicle and the distributor can be encrypted and fully protected. The distributor can authenticate the hydrogen fuel cell vehicle, and optionally, the hydrogen fuel cell vehicle can authenticate the distributor.

[0194] Meanwhile, during the TLS handshake, authentication of the hydrogen fuel cell may be mandatory, while authentication of the distributor may be optional. In this scenario, the distributor can act as a client and the hydrogen fuel cell can act as a server.

[0195] For the TLS handshake, the Hydrogen Fuel Cell and Distributor must prepare the necessary credentials. The Hydrogen Fuel Cell and Distributor can store and maintain the certificate chain, the private key corresponding to its certificate, and the certificate of the trust anchor in a secure storage device to prevent unauthorized access.

[0196] During the TLS handshake, the hydrogen fuel cell vehicle can send a predefined certificate request message to the distributor to request client authentication from the distributor. Upon receiving the certificate request message, the distributor can send a certificate and certificate verification message to the hydrogen fuel cell vehicle to provide the certificate.

[0197] If the hydrogen fuel cell vehicle sends a certificate request message along with a handshake message (such as ServerHello), but the distributor does not send a certificate verification message along with the certificate, the hydrogen fuel cell vehicle can terminate the TLS handshake by sending an alert message with the alert code "Certificate_required".

[0198] According to another exemplary embodiment of this disclosure Figure 4 The objectives, prerequisites, and follow-up conditions of operation S401 shown in Table 4 can be summarized as follows.

[0199] [Table 4]

[0200] Figure 11 This is a sequence diagram illustrating the communication protocol negotiation operation S403 that can be used in a two-way communication process for hydrogen fuel supply according to an exemplary embodiment of this disclosure.

[0201] refer to Figure 11 The communication protocol negotiation operation S403 may include an operation of sending a message to the distributor including information related to a first communication protocol applicable to the mobile body (S1110); and an operation of receiving a message from the distributor including information related to a second communication protocol selected from a common communication protocol applicable to both the mobile body and the distributor (S1130).

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

[0203] Although Figure 11 Although not shown in the diagram, prior to operation S1110, the communication protocol negotiation operation may also include an operation in which the distributor requests information from the mobile body including a list of first communication protocols applicable to the mobile body.

[0204] In an alternative exemplary embodiment of this disclosure, the distributor may first send a message to the mobile body including information related to a communication protocol applicable to itself, and the mobile body may select a specific communication protocol from the public communication protocols and send a message including information related to the selected communication protocol to the distributor.

[0205] In such a case, the communication protocol negotiation operation may also include the operation of the mobile body requesting information from the distributor, including a list of applicable communication protocols.

[0206] Table 5 shows the objectives, prerequisites, and follow-up conditions of operation S403 according to an exemplary embodiment of the present disclosure.

[0207] [Table 5]

[0208] Table 6 shows the contents of messages sent or received in operation S1110 according to an exemplary embodiment of the present disclosure.

[0209] [Table 6]

[0210] Information relating to the first communication protocol may include one or more of the following: an index of the first communication protocol, the name of the first communication protocol, the version of the first communication protocol, and / or preferences for the first communication protocol.

[0211] According to an exemplary embodiment of this disclosure, the content of the messages sent or received in operation S1130 can be summarized as shown in Table 7.

[0212] [Table 7]

[0213] The response message, which includes information related to the second communication protocol, may also include information related to whether the negotiation of the communication protocol was successful.

[0214] After the mobile vehicle and the dispenser discover each other and pair up on a compatible communication channel, a communication protocol negotiation procedure is performed to identify the communication protocol to be followed during the hydrogen refueling session. Specifically, in this embodiment, the dispenser may proactively exchange communication protocols and parameters with the mobile vehicle.

[0215] That is, the communication method according to the exemplary embodiments of this disclosure can perform operation S401 of performing the discovery and pairing process with the distributor using a first communication technology.

[0216] When the result of the communication protocol negotiation operation S403 is related to the second communication technology, the operation S404 of negotiating the fuel supply agreement and the operation S405 of negotiating the fuel supply parameters (which will be described in detail below) can be performed using the second communication technology.

[0217] During operation S401, which performs the discovery and pairing process, information related to interoperability and / or compatibility between the mobile body and the distributor can be shared.

[0218] During the execution of operations S403-S405, the information related to interoperability and / or compatibility between the mobile body and the distributor shared in operation S401, which performs the discovery and pairing process, may be updated to take into account changes in the communication environment and environmental variables related to hydrogen fuel supply.

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

[0220] In practical implementations, various combinations may exist between the mobile unit and the distributor, depending on the hydrogen fuel supply communication standards, communication modes, fuel supply methods, communication levels, and other parameters. Here, hydrogen fuel supply communication standards may include the SAE J2601 series, ISO 19885-3, and ISO 19885-4 standards. Communication modes may include no communication, IrDA, XYZ (ISO), etc. Fuel supply methods may include table-based methods, such as lookup table-based methods, and MC formula-based methods. Communication levels may include UCDC levels, and other parameters may include pressure levels, the type of compressed hydrogen storage system (CHSS), hydrogen fuel supply tables, etc.

[0221] Simultaneously, the mobile unit or distributor can be configured to perform a fallback to a lower type or lower UCDC level based on the type and UCDC level of the corresponding device discovered during the communication protocol negotiation process.

[0222] In a variety of possible combinations of environments, if incompatibility is identified in the parameters exchanged during the negotiation process for hydrogen fuel supply (e.g., in use cases UC3-UC5), the mobile entity and distributor can revert to the communication protocol negotiation process to perform the negotiation process again.

[0223] Table 8 shows an example of a communication protocol for allocating priorities according to an exemplary embodiment of this disclosure.

[0224] The distributor can send a response message to the mobile body, including a specific protocol selected from the protocol list (i.e., the selected protocol) (S1130). The selected protocol chosen by the distributor can be a public protocol supported by both the distributor and the mobile body, having the highest priority and being the most preferred protocol by the mobile body, such as the ISO 19885-3-2023-UCDC-3 protocol in the examples in Table 8.

[0225] A common protocol can be the result of an agreement between the mobile entity and the distributor regarding a communication protocol to be used for fuel supply communications.

[0226] Additionally, a mobile entity can prioritize the communication protocols it supports. A mobile entity may include an FCEV (Federal Container Registry Vehicle). This mobile entity can provide the allocator with a preferred communication protocol. Table 8 shows an example of assigning priority to a communication protocol.

[0227] [Table 8]

[0228] After selecting a communication protocol in use case UC3, the mobile unit and distributor can activate their communication protocol implementations and begin fuel supply protocol negotiation. Fuel supply protocol negotiation is the procedure by which the mobile unit and distributor find and receive the fuel supply protocol to be used in the fuel supply session. In this operation, the mobile unit and distributor can select the mobile unit's preferred communication protocol from among protocols supported by both.

[0229] A communication protocol negotiation method for hydrogen fuel supply executed by the communication controller of a hydrogen fuel vehicle 100 according to an exemplary embodiment of the present disclosure may include: operation S1110, sending a first message to a communication entity associated with a dispenser 200, the first message including a list of one or more first fuel supply protocols supported by the vehicle and one or more first communication protocols required to execute the one or more first fuel supply protocols; and operation S1130, receiving a response message from the communication entity associated with the dispenser 200, the response message including a second fuel supply protocol selected from the one or more first fuel supply protocols.

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

[0231] The first message may include priority information based on the preferences of the mobile entity 100, as shown in Table 8. Furthermore, each message can be defined according to Tables 4 through 6.

[0232] The response message may include a second fuel supply protocol selected from one or more first fuel supply protocols based on preference-based priority information. The mobile body 100 side or the distributor 200 side may select the second fuel supply protocol individually or collaboratively based on preference-based priority information. The operation of finally sending an approval message to the other party to complete the protocol negotiation process can be performed by the mobile body 100 side, but alternatively by the distributor 200 side. In this case, the distributor 200 may first send a list of supported protocols, and the mobile body 100 may provide feedback on the selected protocol.

[0233] The response message may include one or more first fuel supply protocols, and a second fuel supply protocol selected from protocols typically included in one or more first fuel supply protocols and protocols supported by the distributor 200.

[0234] The response message may include a second communication protocol determined by the controller of dispenser 200 from a plurality of first communication protocols required to execute the first fuel supply agreement, based on the type of fallback device for interoperability and backward compatibility between mobile body 100 and dispenser 200.

[0235] According to an exemplary embodiment of this disclosure, if no common communication protocol exists, then as follows: Figures 7 to 9 The diagram shows the selection of a no-communication scheme, and a hydrogen fuel supply protocol based on the no-communication scheme can be selected according to predetermined rules, so that hydrogen can be supplied according to the selected hydrogen fuel supply protocol. In this case, operations S404-S405 described below can be simplified or omitted.

[0236] According to another exemplary embodiment of this disclosure, if no common communication protocol exists, communication between the mobile body 100 and the distributor 200 can be terminated (S409).

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

[0238] refer to Figure 12 The operation S404 of negotiating a fuel supply agreement according to an exemplary embodiment of the present disclosure may include: operation S1210, sending a message including information related to a first fuel supply agreement applicable to the mobile body to the distributor (S403) based on the result of the communication protocol negotiation; and operation S1230, receiving from the distributor a message including information related to a second fuel supply agreement selected from fuel supply agreements applicable to both the mobile body and the distributor.

[0239] As a result of the communication protocol negotiation (S403), after selecting the second communication protocol, a message including information related to one or more available first fuel supply protocols supporting the selected second communication and applicable to the mobile body can be sent to the distributor (S1210).

[0240] The dispenser can select a fuel supply protocol that commonly belongs to a fuel supply protocol supporting a second communication protocol and applicable to the dispenser, and one or more available first fuel supply protocols, and determine one of the selected common protocols as the second fuel supply protocol. In this case, the second fuel supply protocol can be determined based on interoperability and / or compatibility. Furthermore, the second fuel supply protocol can be determined based on preferences set by the mobile unit or the dispenser.

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

[0242] Although Figure 12 It is not shown in the figure, but may include an operation before operation S1210, wherein the distributor requests information from the mobile body including a list of first fuel supply protocols applicable to the mobile body.

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

[0244] In this case, it may also include an operation in which the mobile body requests information from the distributor that includes a list of applicable fuel supply protocols.

[0245] Table 9 shows the objectives, prerequisites, and follow-up conditions of operation S404 according to an exemplary embodiment of this disclosure.

[0246] [Table 9]

[0247] Table 10 shows the contents of messages sent or received in operation S1210 according to an exemplary embodiment of the present disclosure.

[0248] [Table 10]

[0249] Information relating to the first fuel supply agreement may include one or more of the following: an index of the first fuel supply agreement, the name of the first fuel supply agreement, the version of the first fuel supply agreement, sub-agreements of the first fuel supply agreement, or preferences of the first fuel supply agreement.

[0250] Table 11 shows the contents of messages sent or received in operation S1230 according to an exemplary embodiment of the present disclosure.

[0251] [Table 11]

[0252] Messages that include information related to the second fuel supply agreement may also include information related to whether negotiations for the fuel supply agreement were successful.

[0253] Table 12 shows the contents of messages sent or received in operation S1210 according to an exemplary embodiment of the present disclosure.

[0254] [Table 12]

[0255] As shown in Table 12, a mobile entity can provide the dispenser with tabular parameter information for the fuel supply method or fuel supply protocol supported by the mobile entity. The parameter information includes the name, revision date or year or version, information related to the availability of sub-protocols, and preference information.

[0256] In an alternative exemplary implementation, the distributor may proactively exchange communication protocols and parameters with the mobile body. In this case, the distributor may prioritize the communication protocols it supports to provide the mobile body with information on preferred communication protocols.

[0257] In Table 11, PRHYDE (Hydrogen Refueling Protocol for Heavy Vehicles) was proposed by one of the European projects that developed hydrogen refueling protocols for heavy mobile vehicles; RTR-HFP stands for Real-Time Response Hydrogen Refueling Protocol and was proposed as a type of protocol concept for improving refueling efficiency based on real-time communication; and ANN-MPC was proposed as a type of protocol concept for collecting and analyzing data from fuel supply conditions and applying predictive control to fuel supply conditions.

[0258] Examples of messages sent in operation S1230 according to an exemplary implementation are shown in Tables 13 and 14.

[0259] [Table 13]

[0260] As shown in Table 13, the distributor can select the fuel supply protocol corresponding to index 2 and send a response message including an OK result code to the mobile body.

[0261] [Table 14]

[0262] As shown in Table 14, when the dispenser fails to find a compatible protocol in the list of fuel supply protocols supported by the mobile body received from the mobile body, the dispenser may send a response message to the mobile body containing information in the result code field indicating that a common protocol does not exist (e.g., FAIL_NO_COMMON_PROTOCOL).

[0263] The examples shown in Tables 13 and 14 can be similarly applied to... Figure 11 The operation S1130 shown is the case where the distributor selects a second communication protocol from the common communication protocol and responds to the mobile body.

[0264] Figure 13 This is a sequence diagram illustrating a fuel supply parameter exchange / negotiation operation (S405) that can be applied to a two-way communication process for hydrogen fuel supply according to an exemplary embodiment of this disclosure.

[0265] The fuel supply parameter exchange / negotiation operation (S405) may include the exchange of detailed parameters required for the execution of a fuel supply agreement between the mobile body and the distributor.

[0266] See Figure 13 The fuel supply parameter exchange / negotiation operation (S405) may include an operation (S1310) to send a message containing information related to the fuel supply parameters on the mobile body side required by the second fuel supply protocol selected as a result of the fuel supply protocol negotiation operation (S404); and an operation (S1350) to receive a message from the distributor containing compatible information on the fuel supply parameters for the mobile body side on the distributor side.

[0267] The fuel supply parameter negotiation operation S405 may include operation S1330, receiving from the distributor a message containing information related to the fuel supply parameters on the distributor side required for a second fuel supply protocol selected as a result of the fuel supply protocol negotiation operation S404; and operation S1370, sending to the distributor a message containing information on the compatibility of the supply parameters on the distributor side with respect to the mobile body side.

[0268] In operation S1310, when the mobile body sends a message containing information related to fuel supply parameters on the mobile body side, the mobile body may set the "accept" field of each corresponding parameter to <pending> before sending it to the distributor.

[0269] Similarly, in operation S1330, when the distributor sends a message containing information related to fuel supply parameters on the distributor side, the distributor may set the “accept” field of each corresponding parameter to <pending> before sending it to the mobile body.

[0270] When the mobile unit sends a message including information related to fuel supply parameters on the dispenser side in response to the message received in operation S1330, the mobile unit may set the "accept" field of each corresponding parameter to [value] before responding to the dispenser. <ok>Or <is> (S1350).

[0271] When the distributor sends a message including information related to fuel supply parameters on the mobile body side in response to the message received in operation S1310, the distributor may set the "accept" field of each corresponding parameter to [value] before responding to the mobile body. <ok>Or <is>.

[0272] The moving body and the allocator can respond by setting an "Accept" field for each parameter. For parameters for which an agreement has not yet been reached through negotiation, the "Accept" field can be set to <No>.

[0273] Mobile units and distributors can agree on all fuel supply parameters by repeatedly sending and receiving messages and responding to the received messages.

[0274] The parameters exchanged between the dispenser and the mobile body may include parameters to support compatibility of fuel supply methods, physical property-related parameters, monitoring parameters, and reception-related parameters.

[0275] Compatibility-related parameters may include pressure rating and CHSS category. Physical characteristic-related parameters may include maximum permissible CHSS pressure, maximum permissible CHSS temperature, maximum permissible flow rate, and CHSS volume. Monitoring parameters may include current CHSS pressure and current CHSS temperature. Receivable-related parameters may include information indicating whether they are accepted, i.e., parameters indicating yes (TRUE) or no (FALSE). Each of the above parameters may include information corresponding to a predefined rating or setting, as well as information about the same or different primary UCDC ratings.

[0276] At the same time, the distributor can send information about the second parameter supported by the distributor (i.e., the parameter of the distributor) and an OK message indicating that the first parameter has been received to the mobile body (S1330, S1370).

[0277] The second parameter related to fuel supply protocol exchange / negotiation may include parameters to support fuel supply method compatibility, physical characteristic-related parameters, fuel supply target parameters (target SoC), monitoring parameters, and reception-related parameters.

[0278] Compatibility-related parameters may include fuel supply delivery temperature and the selected fuel supply schedule. Physical characteristic-related parameters may include maximum fuel supply pressure, maximum fuel supply temperature, minimum fuel supply temperature, and maximum fuel supply flow rate. Fuel supply target parameters may include target SOC, target final CHSS pressure, target final CHSS temperature, target APR, and target or expected fuel supply duration. Monitoring parameters may include current fuel supply temperature and ambient temperature. Receipt-related parameters may include information indicating whether they are accepted. Each of the above parameters may include information corresponding to a predetermined level or setting, as well as information about the same or different primary UCDC levels.

[0279] As described above, the mobile unit can provide the distributor with parameters listed in tabular form. The listed parameters may include FCEV parameters compatible with the UCDC level negotiated during the fuel supply agreement negotiation process.

[0280] As described above, after establishing a communication link and selecting a communication protocol and fuel supply protocol during the protocol negotiation phase, the mobile unit and the dispenser can exchange various parameters to determine whether they can execute a compatible fuel supply procedure. Here, the information required to execute a safe and efficient fuel supply procedure may include compatibility-related parameters, physical characteristic-related parameters, fuel supply target parameters, and monitoring parameters.

[0281] Compatibility-related parameters may include fuel supply protocol type and fuel delivery temperature. Physical characteristic-related parameters may include CHSS pressure and maximum permissible flow rate. Fuel supply target parameters may include target SOC and target CHSS pressure. Monitoring parameters may include current CHSS temperature and ambient temperature.

[0282] If compatible parameters cannot be found and fuel supply cannot continue, the mobile body can return to the communication protocol negotiation procedure to attempt to negotiate another protocol or stop fuel supply to the distributor. During the communication protocol negotiation procedure following a fuel supply parameter exchange failure, the mobile body can submit a set of supported protocols to the distributor, excluding the protocols that failed during the fuel supply parameter exchange.

[0283] After negotiating the fuel supply protocol in use case UC-4, the mobile unit and the distributor can negotiate specific parameters of the fuel supply protocol, notify static or dynamic states, and exchange detailed fuel supply parameters to determine fuel supply targets. If fuel supply parameter negotiation fails due to parameter incompatibility, the distributor and the mobile unit can return to use case UC-3 to select another fuel supply protocol or return to use case UC-1 to select another communication protocol. If use cases UC-3 and UC-1 cannot be executed normally, the distributor and the mobile unit can terminate the current communication.

[0284] Based on the above construction, some fuel supply protocols can be executed using a communication-free scheme. Another fuel supply protocol may require one-way IrDA communication. Yet another fuel supply protocol may require two-way communication. Yet another fuel supply protocol may require both two-way communication and one-way IrDA communication.

[0285] Some fuel supply agreements may require a predetermined UCDC level or higher. At least one fuel supply agreement can be proposed based on the category or type of hydrogen fuel vehicle and the category or type of distributor. Proposed fuel supply agreements can be assigned different priorities. The communication protocol between the hydrogen fuel vehicle and the distributor, along with the fuel supply agreement, can be ultimately determined based on whether the communication protocol required by the fuel supply agreement is supported by the hydrogen fuel vehicle and / or distributor, and taking into account the priority of the proposed fuel supply agreement.

[0286] In another exemplary embodiment of this disclosure, one of the mobile body or dispenser may first send fuel supply parameters to the other party, which may respond with a message including the newly reconfigured fuel supply parameters by changing the unacceptable parameters in the received fuel supply parameters while keeping the accepted parameters.

[0287] In another exemplary embodiment of this disclosure, the mobile body and the allocator can perform parameter negotiation step by step. The mobile body and the allocator can initiate negotiation for some parameters and perform an exchange / negotiation process for sub-parameters among the parameters that have been agreed upon.

[0288] In another exemplary embodiment of this disclosure, if a response message is not received within a preset message processing time, each message including fuel supply parameters may be set to be considered as not having reached an agreement.

[0289] Table 15 shows the contents of a message including fuel supply parameters on the mobile body side according to an exemplary embodiment of this disclosure.

[0290] [Table 15]

[0291] Table 16 shows the contents of a message including fuel supply parameters on the dispenser side according to an exemplary embodiment of this disclosure.

[0292] [Table 16]

[0293] In the fuel supply parameter negotiation operation (S405), the mobile body and the distributor can send a message containing the range or value of the supported fuel supply parameters to the corresponding device.

[0294] Parameters may include physical characteristic parameters (hereinafter referred to as "physical parameters"), monitoring parameters, security policy parameters, and acceptance parameters.

[0295] Physical parameters may include filler port type, pressure rating, CHSS category, CHSS type, CHSS capacity, maximum permissible CHSS pressure, maximum permissible CHSS temperature, and maximum permissible flow rate. Monitoring parameters may include current CHSS pressure and current CHSS temperature. Safety policy-related parameters may include emergency response policies and safety enforcement levels. Acceptance-related parameters may include information indicating whether they are accepted, i.e., indicating yes (TRUE), no (FALSE), or pending.

[0296] Parameters related to fuel supply parameter negotiation may include physical characteristic parameters (i.e., physical parameters), monitoring parameters, fuel supply target parameters, safety strategy parameters, and acceptance parameters.

[0297] Physical characteristic parameters may include maximum fuel delivery pressure, maximum fuel delivery temperature, minimum fuel delivery temperature, and maximum fuel delivery flow rate. Monitoring parameters may include current fuel delivery temperature and ambient temperature. Fuel supply target parameters may include the selected fuel supply schedule, target SOC, target final CHSS pressure, target final CHSS temperature, target APR, and target or expected fuel supply duration. Acceptance parameters may include information indicating whether they are accepted. Each of the above parameters may include information corresponding to one of the predefined levels or settings, as well as information about the same or different master UCDC levels.

[0298] The mobile unit can provide the distributor with parameters listed in tabular form. The listed parameters may include FCEV parameters compatible with the UCDC level negotiated in the fuel supply agreement negotiation process.

[0299] Additionally, if a fuel supply parameter negotiation request message is received and the received fuel supply parameters are compatible with the distributor, the distributor can respond to the request message with its own fuel supply parameters by sending a fuel supply parameter negotiation response message with a negotiation result set to "OK" within a specified message response time interval.

[0300] If a fuel supply parameter negotiation request message is received, but the received fuel supply parameters are incompatible with the dispenser, the dispenser can respond to the request message by sending a fuel supply parameter negotiation response message to the FCEV with a negotiation result set to "failed" to indicate incompatibility with the FCEV. The negotiation result can indicate the value or information contained in the result code field, and failure can indicate a negative failure at a specific time and can be indicated by an incompatibility indication (e.g., "Fail_uncompat").

[0301] Meanwhile, if a mobile body receives a fuel supply parameter negotiation request message but finds that the received fuel supply parameters are incompatible with the mobile body, the mobile body can notify the dispenser of the incompatibility by sending an error notification message with a "reason" set to a predefined error code.

[0302] On the other hand, before fuel delivery begins, the mobile unit and distributor can verify that all safety conditions are met via use case UC6 for safety check-in. This operation is optional, but it is desirable to define a dedicated safety check-in procedure in the fuel supply agreement to ensure the desired level of safety in a precise and explicit manner.

[0303] Figure 14 This is a conceptual diagram illustrating a table of parameters transmitted from the mobile body side to the distributor side during a fuel supply parameter exchange process, according to an exemplary embodiment of this disclosure.

[0304] Figure 15 This is a conceptual diagram illustrating a table of parameters transmitted from the distributor side to the mobile body side during a fuel supply parameter exchange process, according to an exemplary embodiment of this disclosure.

[0305] Let's refer to each other. Figure 13 and Figure 15 A method for exchanging parameters of hydrogen fuel supply via communication according to an exemplary embodiment may include: operation S1310: sending a first parameter to a communication entity associated with the dispenser 200, the first parameter including at least one of one or more first hydrogen fuel supply method compatibility supported by the mobile body 100 and one or more first physical characteristics; and operation S1330: receiving a response message from the communication entity associated with the dispenser 200 including a second parameter, the second parameter including at least one of one or more second hydrogen fuel supply method compatibility supported by the dispenser, one or more second physical characteristics, and fuel supply target.

[0306] The communication entity associated with dispenser 200 may be the electronic controller 210 of dispenser 200 or a separate communication device mounted on dispenser 200. Alternatively, the electronic controller or separate communication device in fuel supply station system 220 may replace dispenser 200 in communicating with mobile body / mobile body 100.

[0307] The first parameter may also include a first monitoring parameter supported by the mobile body 100. The second parameter may also include a second monitoring parameter supported by the distributor 200.

[0308] In a parameter exchange method via communication for a hydrogen fuel supply process according to an exemplary embodiment of this disclosure, the parameter exchange process can be terminated based on an acknowledgment message (e.g., an OK message) included in a response message. The parameter exchange process can be terminated when the mobile unit 100 and the dispenser 200 accept all exchanged parameters. The parameter exchange process can also be terminated if either party does not accept the exchanged parameters. In the event that either party does not accept the exchanged parameters, the protocol negotiation process can be revisited according to the following procedure, or the fuel supply session can be terminated.

[0309] In a parameter exchange method via communication in an exemplary embodiment of a hydrogen fuel supply process according to this disclosure, one or more first hydrogen fuel supply method compatibility may include one or more of the pressure rating and CHSS category of the mobile body 100.

[0310] In a parameter exchange method via communication for a hydrogen fuel supply process according to an exemplary embodiment of the present disclosure, one or more first physical characteristics may include one or more of the following: maximum permissible CHSS pressure, maximum permissible CHSS temperature, maximum permissible flow rate, and CHSS volume.

[0311] In a parameter exchange method via communication for a hydrogen fuel supply process according to an exemplary embodiment of the present disclosure, the first parameter further includes parameters related to the receiving mobile body 100.

[0312] In a parameter exchange method via communication in a hydrogen fuel supply process according to an exemplary embodiment of the present disclosure, the first monitoring parameter may include one or more of the current CHSS pressure and the current CHSS temperature.

[0313] In a parameter exchange method via communication in an exemplary embodiment of the hydrogen fuel supply process according to this disclosure, one or more second hydrogen fuel supply method compatibility may include the fuel supply delivery temperature of the dispenser 200 and one or more selected fuel supply tables. The selected fuel supply table may include a sequence list of selected fuel supply protocols and may be included in the OK message shown in operation S1330.

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

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

[0316] In a parameter exchange method via communication in a hydrogen fuel supply process according to an exemplary embodiment of the present disclosure, the second parameter may further include parameters related to acceptance by the dispenser 200.

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

[0318] In operation S1310, the mobile body 100 may provide the distributor 200 with first parameters in tabular form that are compatible with the UCDC level negotiated during the protocol negotiation process.

[0319] In operation S1330, the distributor 200 may provide the mobile body 100 with a second parameter in tabular form that is compatible with the UCDC level negotiated during the protocol negotiation process. At this time, the second parameter may be provided together with a message indicating acceptance of the first parameter provided in operation S1310.

[0320] If mobile body 100 or distributor 200 does not accept the exchanged parameters, mobile body 100 may re-execute the protocol negotiation process. Alternatively, if mobile body 100 or distributor 200 does not accept the exchanged parameters, mobile body 100 may terminate the fuel supply session.

[0321] During a protocol negotiation process that is retried due to a failure of the parameter exchange process by which the mobile body 100 or the distributor 200 does not accept the exchanged parameters, the mobile body 100 may propose a set of supported protocols in addition to those already provided in the failed parameter exchange process.

[0322] Table 17 shows the contents of a message including fuel supply parameters on the mobile body side according to another exemplary embodiment of this disclosure.

[0323] [Table 17]

[0324] Table 18 shows the contents of a message including fuel supply parameters on the dispenser side according to another exemplary embodiment of this disclosure.

[0325] [Table 18]

[0326] The communication method according to an exemplary embodiment of the present disclosure may further include the following operation: when, as a result of fuel supply parameter negotiation, the fuel supply parameters are incompatible between the mobile body and the dispenser, one or more of the communication protocol or fuel supply parameters are renegotiated (S405).

[0327] In such a case, the renegotiation operation in the communication method according to the exemplary embodiment may include re-executing operations S403, S404, and S405. For example, it is possible to return to operation S403, perform renegotiation in operation S403, and then perform operations S404 and S405 sequentially again. In another embodiment, the procedure may return to operation S404 to perform renegotiation in operation S404, and then perform operation S405 again.

[0328] In another exemplary embodiment of the communication method according to this disclosure, the renegotiation operation may be performed in a simplified mode, including operations S403, S404, and S405, or some processes may be omitted. Alternatively, the renegotiation operation may combine operations S403 and S404 to negotiate the communication protocol and the fuel supply protocol together. For example, based on compatibility and / or interoperability information identified in operation S401, the communication protocol and the fuel supply protocol may be negotiated together using a protocol list that includes both the communication protocol and the fuel supply protocol, based on their common support in the mobile body and the dispenser.

[0329] In another exemplary embodiment of the communication method according to this disclosure, a renegotiation operation can be performed based on a list of communication protocols or fuel supply protocols other than those selected in operations S403 and S404 respectively.

[0330] The communication method according to an exemplary embodiment of this disclosure may further include, when fuel supply parameters are incompatible between the mobile body and the dispenser as a result of fuel supply parameter negotiation, determining a third communication protocol and a third fuel supply protocol based on a predetermined strategy (S405); and supplying hydrogen based on the third communication protocol and the third fuel supply protocol. In this case, the third fuel supply parameters can be determined based on the third fuel supply protocol, and the hydrogen supply operation can be performed based on the third fuel supply protocol and the third fuel supply parameters.

[0331] For example, if communication between the mobile unit and the distributor becomes impossible due to changes in the communication environment, the distributor can fall back to a no-communication scheme and supply hydrogen using a hydrogen fuel supply protocol based on the no-communication scheme.

[0332] A communication method according to an exemplary embodiment of the present disclosure may include operation S409: terminating communication between the dispenser and the mobile body when, as a result of fuel supply parameter negotiation, the fuel supply parameters are incompatible between the mobile body and the dispenser.

[0333] Return to reference Figure 4 According to an exemplary embodiment of this disclosure, a secure check-in procedure may be employed during two-way communication for hydrogen fuel supply.

[0334] In the safety check-in operation S406, the dispenser and the mobile body including the mobile body can check whether all necessary safety conditions are met before the actual fuel supply begins.

[0335] After the fuel supply parameters are exchanged and the mobile unit and dispenser are deemed compatible, the mobile unit and dispenser can perform a safety status check to determine whether fuel supply can be safely performed. Depending on the fuel supply protocol, the safety check can be performed implicitly within the scheme. Furthermore, depending on the implementation, the safety check operation S406 can be omitted.

[0336] During the safety check operation S406, the moving body and / or dispenser can check whether the engagement of the nozzle and filling port is locked, check for any leaks, and check the last minute status.

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

[0338] The mobile entity and the distributor can exchange messages for coupler checks. The mobile entity can send a message to the distributor that includes information indicating its own coupler check result (e.g., "Mobile entity: OK"), and the distributor can send a message to the mobile entity that includes information indicating its own coupler check result (e.g., DP: OK).

[0339] The mobile unit and the distributor can exchange messages related to gas leak checks. During the exchange of such messages, the distributor can send a message to the mobile unit indicating that the leak check is in progress ("in progress"). Furthermore, the mobile unit can send a message to the distributor indicating that it is awaiting the leak check results from the distributor ("waiting"). When the leak check is complete, the distributor can send a message to the mobile unit requesting a measurement of the tank volume and a message indicating that the leak check is complete ("complete").

[0340] The distributor can send messages to the mobile body for fixed status checks, and the mobile body can send messages to the distributor indicating that it is ready to perform a status check.

[0341] If the mobile unit reports parameters about its current or stationary status to the distributor, the distributor can report parameters about the coupler lock-up status, leak check status, and predicted mobile unit tank capacity to the mobile unit.

[0342] After completing the security check-in operation S406 described above, actual fuel supply can begin. During fuel supply, the mobile unit and the distributor can exchange information monitoring various status parameters to ensure that fuel supply is performed safely and efficiently. If necessary, the mobile unit or distributor can send control messages requesting actions from the other party to control the fuel supply procedure or respond to safety-related situations. The parameters and commands to be exchanged may vary depending on the actual fuel supply protocol.

[0343] Operation S407 represents a monitoring and control procedure that can be employed during two-way communication for hydrogen fuel supply according to an exemplary embodiment of this disclosure.

[0344] In monitoring and control operation S407, the dispenser and / or the mobile body, including the mobile unit, can monitor the fuel supply status and control the fuel supply process as necessary. The mobile body and dispenser can continue the fuel supply process according to the selected fuel supply protocol and using parameters, while verifying all safety checks. During fuel supply, the mobile body and dispenser can exchange various measurement data to determine the fuel supply status and detect safety-critical events as quickly as possible.

[0345] Furthermore, the mobile entity can send commands to the distributor to control the fuel supply process, such as starting or terminating fuel supply. In this case, the mobile entity can use UDP, including DTLS, to support black channel communication. Black channel communication refers to communication that applies black channel principles to ensure secure communication, although the output characteristics of the communication channel may be insecure or have application-independent properties.

[0346] The monitoring and control operation S407 will be described in more detail. The mobile body can send a message to the distributor to initiate fuel supply control, and in response, the distributor can send a message to the mobile body including an acknowledgment (e.g., "OK").

[0347] In addition, the mobile body can send a message to the distributor including information about its own fuel supply circuits (e.g., x, y, z), and the distributor can send a message to the mobile body including information about its own fuel supply circuits corresponding to the mobile body (e.g., a, b, c).

[0348] In addition, the mobile body can send a fuel supply control request message to the distributor, including information for slowing down the fuel supply or reducing the amount of fuel delivered, and the distributor can send a response message to the mobile body, which includes information indicating a slowdown in the fuel supply flow.

[0349] In addition, the mobile vehicle can send a fuel supply control request message to the distributor to request the cessation of fuel supply. The distributor can send a fuel supply status response message to the mobile vehicle, including information that fuel supply has stopped or has already stopped.

[0350] According to the monitoring and control procedures, the mobile unit and the distributor can continuously or periodically exchange parameters related to the fuel supply status. The mobile unit can send information such as the current tank temperature and current tank pressure to the distributor, and the distributor can provide the mobile unit with parameters related to the start, stop, increase or decrease of fuel supply, current injection pressure, fuel supply schedule, etc.

[0351] Messages sent by the mobile unit to the distributor regarding fuel supply control requests may include information or parameters related to the start, pause, resumption, and / or termination of fuel supply. Additionally, messages related to reports sent by the mobile unit to the distributor may include information or parameters such as the current tank temperature and current tank pressure.

[0352] The messages sent by the distributor to the mobile body regarding the report may include, for example, information or parameters related to status information, current ambient temperature, current pressure increase rate (PRR), fuel delivery flow rate, current fuel delivery temperature, pre-cooling temperature, current fuel delivery pressure, whether full fuel supply is being used, whether a cooling distributor is being used, whether backoff is being used, the reason for fuel supply interruption, and the amount of hydrogen currently being delivered.

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

[0354] Meanwhile, when TCP is used in monitoring and control operation S407, if the security check response message or security check procedure according to the fuel supply protocol is omitted, the mobile unit can send a fuel supply loop request message to the distributor within the message sequence set time interval after receiving the fuel supply parameter negotiation response message from the distributor. Request or response messages related to the fuel supply loop can be sent via DTLS messages.

[0355] After hydrogen fuel supply is completed via monitoring and control operation S407, and before terminating the session and disengaging the nozzle from the mobile unit, the mobile unit and dispenser can be checked for compliance with all safety conditions via a safety check-in use case. The safety check-in process may be optional, but it is desirable to define a dedicated safety check-in procedure in the fuel supply agreement to ensure the desired safety level is met in a precise and unambiguous manner.

[0356] The safety detection procedure S408 that can be used in the two-way communication process of hydrogen fuel supply according to an exemplary embodiment of this disclosure can be executed as follows. The mobile unit and the dispenser can check that all necessary safety conditions are met before the dispenser nozzle is disconnected from the mobile unit's filling port through the safety detection procedure. In other words, the mobile unit and the dispenser can confirm that it is absolutely safe for the user or operator to disconnect the nozzle from the mobile unit after fuel supply is completed.

[0357] For example, if the mobile body receives a fuel supply loop response message from the distributor with a "result" attribute set to "OK" or a "status" attribute set to "complete", or if the mobile body receives a fuel supply status response message including information about stopping fuel supply, and if the hydrogen fuel supply protocol supports safety detection, the mobile body can initiate safety detection and perform safety detection operation S408 by sending a safety detection request message to the distributor within the message sequence set time period.

[0358] The mobile unit and the dispenser can repeatedly report their status to each other until a safety check confirms it. If such a safety check is not required at the end of the two-way communication process for hydrogen fuel supply, the use case for safety detection can be omitted.

[0359] The security detection operation S408 will be described in more detail. The mobile body may send a message to the distributor containing information related to the result of the coupler check (e.g., "OK"), and the distributor may send a message to the mobile body containing information indicating that the coupler check is in progress (e.g., "in progress").

[0360] In addition, the mobile body can send a message containing information related to the coupler check result (e.g., "OK") to the distributor, and the distributor can send a message containing information indicating that the coupler check is complete (e.g., "Completed") to the mobile body.

[0361] When the coupler check result shows that the coupler check is completed normally, the nozzle of the dispenser can be detached from the mobile body filling port by the user or operator.

[0362] In security detection operation S408, the report message sent by the distributor to the mobile body may include information or parameters regarding the coupler unlock status. Coupler unlock status information may include information about locking, unlocking, freezing, or problems.

[0363] Use case UC9 can be terminated when fuel supply according to the hydrogen fuel supply agreement is completed and the nozzle is safely disconnected, or when a non-safety-critical issue occurs during another use case.

[0364] According to an exemplary embodiment of this disclosure, the termination step S409 that can be used in the bidirectional communication process of hydrogen fuel supply can be performed as follows.

[0365] In the termination operation S409, which is the final stage of fuel supply, the mobile unit and the dispenser can exchange information regarding the fuel supply results related to fuel supply performance and methods, and / or information related to the reasons for the unexpected cessation of fuel supply, to complete all operations related to hydrogen fuel supply. The termination use case can also be configured to handle tasks related to non-safety-critical issues when such issues occur.

[0366] For example, after the mobile body receives a safety detection response message (where the "result" attribute is set to "complete") or a fuel supply loop response message (where the "status" attribute is set to "complete") or information including stopping fuel supply from the distributor, the mobile body may send a termination request message to the distributor to perform termination operation S409.

[0367] The termination operation S409 will be described in more detail. The mobile vehicle may send a message to the distributor to query how much fuel supply has been provided from the distributor. In response to the query message, the distributor may send a response message to the mobile vehicle including information related to the amount of hydrogen fuel supplied (e.g., X grams).

[0368] Subsequently, the mobile vehicle can send a confirmation request message to the dispenser indicating that the fuel supply is complete, and the dispenser can send a goodbye message to the mobile vehicle as a response to the confirmation request message.

[0369] After fuel supply is completed and safety checks are performed, in termination operation S409, the mobile unit and the distributor can exchange at least some bookkeeping information for the hydrogen fuel supply session. Before completing termination operation S409, the mobile unit and the distributor can exchange summary information related to the hydrogen fuel supply session.

[0370] The bookkeeping information may include all information related to hydrogen fuel supply recorded in the mobile unit or dispenser in accordance with prescribed rules or policies during all fuel supply sessions of hydrogen fuel supply and before the termination operation S409 of use case UC-9.

[0371] Bookkeeping or summary information may include information related to how much fuel was dispensed and what reports were generated. Additionally, report messages sent from the mobile unit to the dispenser may include information or parameters related to the current tank temperature and current tank pressure. Meanwhile, report messages sent from the dispenser to the mobile unit may include information related to the final State of Charge (SOC), final average fuel supply rate (APR), final measured tank pressure, actual fuel supply time, and the actual amount of hydrogen fuel supplied.

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

[0373] Examples of communication data exchanged in some use cases of UC5-UC9 are summarized in Table 19.

[0374] [Table 19]

[0375] Meanwhile, the error handling use case UC10 is a function block for handling non-safety-critical errors that occur due to the shutdown of a fuel supply procedure similar to a normal termination or a sudden interruption of communication.

[0376] Error handling operation S410, employed in a two-way communication process for hydrogen fuel supply according to an exemplary embodiment of this disclosure, can be performed as follows.

[0377] When an error occurs, the error handling operation S410 may include the definition of error conditions related to the fuel supply agreement, the provision of detection criteria, and a response procedure including notification, termination procedures, and rollback mechanisms.

[0378] When a non-safety-critical error occurs and further communication is impossible, error handling operation S410 can be applied. According to the error handling procedure, the mobile unit and distributor can handle the occurrence of non-safety-critical errors at any time during fuel supply. When a non-safety-critical error occurs, the mobile unit and distributor can immediately stop fuel supply, temporarily halt the previously selected and currently operating use case, and then continue with the termination use case UC9.

[0379] If a mobile entity detects an event related to a non-safety-critical error, it can notify the distributor of the termination reason via a termination request message and terminate the current fuel supply session or communication session. The distributor can terminate the current communication session in response to the termination request message. If further communication is not possible, the current session can be terminated without further notification.

[0380] When a non-safety-critical error is detected in a mobile entity and the communication channel remains operational, the mobile entity may send a termination request message to the distributor with an "Action" attribute set to "Stop" and a "Cause" attribute set to an appropriate cause or cause code. Examples of appropriate causes or cause codes may include causes such as "Message corrupted".

[0381] Termination request messages can be sent in the event of non-safety-critical communication errors, system errors, or qualitative errors (excluding unrecoverable situations).

[0382] In other words, for successful refueling, communication must convey the actions or operations that are likely to be anticipated according to the protocol, and the refueling operation must be within the acceptable range of the fuel supply protocol. However, various abnormal events may occur in practice. While some errors are trivial and easily handled, others are unrecoverable and may prevent refueling from taking place. Error handling operation S410 is able to define non-safety-critical error conditions and provide exemplary error conditions and possible responses.

[0383] Examples of communication errors can include instances of communication interruptions, received data that cannot be recognized due to encoding or syntax errors, or received data that is outside the permissible range. System errors can include instances where the distributor or mobile unit detects a critical system error. Qualitative errors can include instances where the quality of communication performance or the quality of data integrity or accuracy does not meet the required level.

[0384] According to this embodiment, the two-way communication process for hydrogen fuel supply can perform specific error handling operations S410 as outlined in (1) to (4) below in response to the above-mentioned error conditions.

[0385] (1) In the event of a non-safety-critical error and inability to communicate further, the mobile body and distributor may immediately stop fuel supply but may take safety actions and terminate the session by stopping communication.

[0386] (2) In the event of a non-safety-critical error and a suspension of fuel supply without completion, the fuel supply protocol may, for example, define a fallback mechanism by defining a non-communication fuel supply method.

[0387] (3) If a non-safety-critical error is detected in the mobile body and the communication channel is still operational, the mobile body may send a termination request message to the distributor, wherein the "action" attribute is set to "stop" and the "reason" attribute is set to the appropriate reason or reason code.

[0388] (4) If the distributor detects a non-safety-critical error and the communication channel remains operational, the distributor may immediately stop the fuel supply and send a termination request message to the mobile body, wherein the "action" attribute is set to "stop" and the "reason" attribute is set to the appropriate reason or reason code.

[0389] As described above, the bidirectional communication process for hydrogen fuel supply, including the fuel supply agreement, can define error conditions related to the fuel supply agreement, provide detection criteria, and when an error is detected according to the detection criteria, execute error handling operation S410, which includes notification, termination operation S409, and rollback mechanism.

[0390] At the same time, emergency action / handling may be required when a safety-critical issue occurs during the fuel supply of the hydrogen fuel supply system.

[0391] The emergency handling procedure S411, which can be used in a two-way communication process for hydrogen fuel supply according to an exemplary embodiment of this disclosure, can be executed as follows.

[0392] Emergency handling operation S411 can define safety-critical conditions that require emergency action during fuel supply and can include response procedures to prevent safety-critical incidents.

[0393] For secure fuel supply, communication must convey actions or operations as anticipated according to the agreement, and fuel supply operations must be conducted within the safety limits of the fuel supply agreement. However, problems may arise during fuel supply, causing the fuel supply system to reach a critical state that must be avoided at all costs. Emergency handling operation S411 enables the definition of safety-critical emergency situations and possible actions or operations in response to these situations, and can provide important considerations.

[0394] Fuel supply agreements can define emergency situations related to the agreement, provide detection criteria for emergency situations and performance requirements for mobile vehicles or distributors, and specify response procedures S411 to avoid entering hazardous situations.

[0395] More specifically, when a high-pressure condition exceeding a preset reference value is detected by the mobile unit during the hydrogen fuel supply process, the mobile unit can send a first emergency stop request message to the distributor. This first emergency stop request message includes information requesting a halt to fuel supply based on the high pressure (e.g., "Emg: Stop (High Pressure)"). In response to the first emergency stop request message, the distributor can send a response message to the mobile unit including information indicating that the distributor is handling an emergency fuel supply halt (e.g., "Emg: Stop").

[0396] Furthermore, upon receiving a response message or after a preset time has elapsed since receiving the response message, the mobile unit may send a first emergency stop request message to the dispenser again. After an emergency stop of fuel supply, the dispenser may send a response message to the mobile unit including information indicating that fuel supply has been stopped in an emergency (e.g., "Emg: Stop").

[0397] Simultaneously, if a hydrogen fuel leak is detected by the dispenser during the hydrogen fuel supply process, the dispenser can send a second emergency stop request message to the mobile vehicle. The second emergency stop request message includes information indicating that it is handling a stoppage in fuel supply due to the leak (e.g., "Emg: Stop (Leak)"). The mobile vehicle can send a response message to the dispenser including information confirming the second emergency stop request message (e.g., "Emg: Confirmation").

[0398] In addition, the dispenser can send a third emergency stop notification message to the mobile vehicle, which includes information indicating that fuel supply has stopped due to a leak (e.g., "Emg: Stop (Leak)"). The mobile vehicle can send a response message to the dispenser including information confirming the third emergency stop notification message (e.g., "Emg: Confirmation").

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

[0400] Upon receiving an emergency notification message, the mobile entity or distributor can immediately respond to the situation indicated in the emergency notification message and terminate communication without excessive delay. An emergency notification message may include a header and a body containing the message. The header may include information indicating an emergency notification, and the message may include the category, type, and action value, information, or parameters of the emergency notification.

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

[0402] Refer again Figure 4 The purpose, prerequisites and follow-up conditions of the security check-in operation (S406) can be shown in Table 20 below.

[0403] [Table 20]

[0404] As described above, when the fuel supply parameter negotiation operation (S405) is successfully executed, the fuel supply protocol can support the safe check-in operation (S406).

[0405] If the communication physical layer is defined as requiring a pairing procedure, the mobile body and the dispenser can recheck the pairing before dispensing hydrogen in the security check-in operation (S406).

[0406] Even if the communication physical layer is not defined as requiring a pairing procedure, the mobile body and the dispenser can recheck the pairing before dispensing hydrogen in the security check-in operation (S406).

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

[0408] As an alternative exemplary implementation, when one of the mobile bodies or distributors sends a message indicating the completion of operation S405 to the other, one or the other may send a new message indicating the start of the security check-in operation (S406).

[0409] According to an exemplary embodiment of this disclosure, the messages sent and received in the security check-in operation (S406) can be defined based on the content of each fuel supply agreement as defined in a standard such as ISO 19885-3.

[0410] According to an exemplary embodiment of this disclosure, the messages sent and received in the security check-in operation (S406) may include a result value of processing the request message as a result element. For example, the result value provided as a result element may include "OK" in the case of success, "Failure" in the case of failure, and "Pending" in other cases.

[0411] If all safety conditions are met when the mobile body sends the SafetyCheckInReq message to the allocator, the result value of the message can be set to "OK".

[0412] If some safety conditions are not met when the mobile entity sends the SafetyCheckInReq message to the allocator, the result value of the message can be set to "pending".

[0413] After receiving the SafetyCheckInReq message, the allocator can respond to the moving body with a SafetyCheckInRes message that includes safety check parameters within the MessageResponseTimeout time interval.

[0414] If all safety conditions are met when the distributor sends the SafetyCheckInRes message to the mobile body, the message's result value can be set to "OK".

[0415] If certain safety conditions are not met when the allocator sends the SafetyCheckInRes message to the mobile body, the message's result value can be set to "pending".

[0416] If a mobile entity receives a SafetyCheckInRes message with the result value set to "Pending", the mobile entity can send another SafetyCheckInReq message to the distributor within the MessageResponseTimeout time interval.

[0417] If the allocator receives a SafetyCheckInReq message with the result value set to "Pending", the allocator can send another SafetyCheckInReq message to the mobile body within the MessageResponseTimeout time interval.

[0418] If the mobile unit or distributor fails to verify all safety conditions within a predetermined time (e.g., UCSafetyCheckInTimeout), an ErrNOtifReq message with a "reason" field set to the appropriate error code can be sent.

[0419] As an alternative exemplary implementation, the mobile body or distributor may send a request message indicating the start of security check to another party, and the other party may respond to the security check request message with a response message within a predetermined time interval.

[0420] Refer again Figure 4 The purpose, prerequisites, and follow-up conditions of the monitoring and control operation (S407) can be shown in Table 21 below.

[0421] [Table 21]

[0422] As previously stated, when the safety check-in operation (S406) is successfully performed, the fuel supply protocol can perform monitoring and control operations (S407).

[0423] If the safety check-in operation (S406) is omitted, the fuel supply protocol can perform monitoring and control operations (S407) when the fuel supply parameter negotiation operation (S405) is successfully executed.

[0424] During monitoring and control operations (S407), the distributor can perform all the necessary steps to supply hydrogen fuel to the mobile vehicle.

[0425] When using the TCP specification in the fuel supply control and monitoring use case, the mobile body may send a message (e.g., a FuelLoopReq message) requesting the start of monitoring and control operations (S407) to the distributor after receiving the SafetyCheckInRes message, or in an exemplary implementation that omits the safety check-in operation (S406), after receiving the FuelParamNegores message, within a predetermined time interval (e.g., MessageSequenceTimeout).

[0426] When using the aforementioned black channel, after sending the SafetyCheckInRes message, or in an exemplary implementation that omits the security check-in operation (S406), after sending the FuelParamNegores message, the mobile entity (as client) and the distributor (as server) can initiate a DTLS 1.3 handshake compliant with RFC 9147 along with session resumption using the NewSessionTicket. In this case, the NewSessionTicket can be received from the distributor.

[0427] After the DTLS 1.3 handshake is successfully completed, the mobile entity can send a message (e.g., a FuelLoopReq message) requesting the start of monitoring and control operations (S407) to the distributor within a predetermined time interval (e.g., MessageSequenceTimeout).

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

[0429] Both the FuelLoopReq message and its corresponding response message (e.g., the FuelLoopRes message) can be sent according to the DTLS message specification.

[0430] Additional requirements for the black channel method can be added.

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

[0432] The fuel supply protocol can specify static or dynamic data to be included in the FuelLoopReq and FuelLoopRes messages, allowing the static or dynamic data to monitor the fuel supply status and exchange safety-related information.

[0433] The names of elements included in the FuelLoopReq message may include actions (or operations, procedures, and / or sequences), reasons, etc., and may be shown in Table 22 below. Elements not shown in Table 22 may be specified according to each fuel supply agreement specification such as ISO 19885-3.

[0434] [Table 22]

[0435] The element names contained in messages sent and received in operation S407 (e.g., FuelLoopRes messages) may include status, cause, result, etc., and may be shown in Table 23 below. Elements not shown in Table 23 may be specified according to each fuel supply agreement specification such as ISO 19885-3.

[0436] [Table 23]

[0437] When a mobile entity sends a FuelLoopReq message, the allocator is expected to execute the corresponding action, operation, procedure, and / or sequence. The mobile entity can set the "action" to the desired action code and send the message. The action code can be defined according to the hydrogen fuel supply protocol.

[0438] Upon receiving a FuelLoopReq message (e.g., with "Action" set to "Start"), the distributor can initiate the hydrogen fuel supply procedure using a negotiated method when it is ready to begin, and respond with a FuelLoopReq message with "Result" set to "OK".

[0439] After receiving a FuelLoopReq message (e.g., setting "Action" to "Start"), the allocator can respond with a FuelLoopReq message with "Result" set to "Pending" when it is not ready to start.

[0440] Upon receiving a FuelLoopReq message (e.g., with an "action" set to "stop"), the dispenser can halt the hydrogen fuel supply process defined in the hydrogen fuel supply protocol when it is ready to stop, and respond with a FuelLoopRes message with a "result" set to "in progress".

[0441] Upon receiving a FuelLoopReq message (e.g., with an "action" set to "stop"), the dispenser can immediately stop the hydrogen fuel supply process and respond with a FuelLoopRes message with a "result" set to "OK" when it is ready to stop.

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

[0443] When a received FuelLoopReq message is successfully processed, the allocator can send a FuelLoopRes message with the "Result" set to "OK".

[0444] When a received FuelLoopReq message is not successfully processed, the allocator may send a FuelLoopRes message with the "Result" set to "Failure" or another appropriate error code.

[0445] The distributor can send a FuelLoopRes message with the "status" set to one of the supported codes specified in Table 23 or the hydrogen fuel supply protocol.

[0446] When the hydrogen fuel supply is complete (or finished) and the expected fuel supply target is achieved (target SoC is reached), the dispenser can send a FuelLoopRes message with the "status" set to "complete".

[0447] When hydrogen fuel supply is stopped due to an error-related reason, the dispenser can send a FuelLoopRes message with "Status" set to "Stop_Error" and "Reason" set to the appropriate reason code.

[0448] When the "Action" of the most recent FuelLoopReq message is set to "Stop" and the hydrogen fuel supply has not completely stopped, the dispenser can send a FuelLoopRes message with the "Status" set to "Stop".

[0449] When the "Action" of the most recent FuelLoopReq message is set to "Stop" and the hydrogen fuel supply has been completely stopped, the distributor can send a FuelLoopRes message with the "Status" set to "Stop_Request".

[0450] When a mobile entity has sent a FuelLoopReq message with "Action" set to "Stop" and received a FuelLoopRes message with "Status" set to "Stop", the mobile entity can send a FuelLoopRes message with "Action" set to "Stop".

[0451] When a mobile entity receives a FuelLoopRes message but has not yet completed its hydrogen fuel supply, it can send a FuelLoopReq message within a predefined time interval (e.g., MessageSequenceTimeout).

[0452] In the event of a critical safety incident, the mobile unit or distributor can immediately send an EmergencyReq message to terminate the hydrogen fuel supply process and shut down communication.

[0453] The above exemplary implementations related to operation S407 have been described based on the scenario where each operation is initiated based on a request from the mobile body and the distributor responds. However, the concept of this disclosure is not limited thereto. In alternative exemplary implementations, the mobile body or the distributor may send a message requesting the initiation of operation S407, and the corresponding party may respond to the request, thereby enabling the execution of operation S407.

[0454] During operation S407, messages sent by the mobile unit or distributor may include monitoring requests regarding the status of the hydrogen fuel supply process. Response messages from the corresponding party may include the status information of the requested monitoring entity.

[0455] The status and related parameters of the subject making the monitoring request may include the set of parameters exchanged in operation S405. The status and related parameters of the subject making the monitoring request may include the status and parameters of the moving body or distributor. The status and related parameters of the subject making the monitoring request may include the hydrogen fuel supply status and / or related parameters of the moving body and / or distributor, which may change or remain constant through the hydrogen fuel supply procedure.

[0456] Furthermore, the status of the subject of the monitoring request can include the status and / or information of the hydrogen fuel supply process itself, which is executed from the dispenser to the mobile body. For example, this information can include whether the hydrogen fuel supply process is in progress, suspended, completely terminated, and / or if it stops / terminates, whether it is due to an error or due to the achievement of an expected goal (because the fuel supply target SoC has been reached), etc.

[0457] Refer again Figure 4 The purpose, prerequisites and follow-up conditions of the safety detection operation (S408) can be shown in Table 24 below.

[0458] [Table 24]

[0459] After fuel supply is completed, a safety check operation (S408) can be performed to ensure that the mobile body and dispenser meet safety conditions before terminating the session and removing the nozzle from the mobile body. Although the safety check operation (S408) is optional, it is strongly recommended that a dedicated safety check procedure be defined by the fuel supply agreement to ensure the desired level of safety in an accurate and explicit manner.

[0460] When a safety-related incident occurs, the information exchange used in the safety detection operation (S408) may be used for diagnostic and accountability verification purposes.

[0461] As described above, when the monitoring and control operation (S407) and the associated fuel supply procedure are successfully completed, the fuel supply protocol can perform a safety detection operation (S408).

[0462] Regardless of whether a safety check is performed, a fuel supply protocol conforming to ISO 19885-2 can define a set of safety conditions to be confirmed between the moving body and the dispenser before the nozzle is pulled out.

[0463] When a FuelLoopRes message is received with "Result" set to "OK" and "Status" set to a value prefixed / suffixed with "Completed" or "Stopped", and the fuel supply protocol supports safety checkout, the mobile unit may send a message (e.g., a SafetyCheckOutReq message) requesting the start of the safety checkout operation (S408) to the distributor via a TLS channel within a predetermined time interval (e.g., MessageSequenceTimeout).

[0464] When the TCP / TLS channel is broken, the mobile entity can re-establish the TCP / TLS channel with the allocator. The reconstruction process can be initiated via a TLS recovery handshake using a NewSessionTicket received before the SafetyCheckOutReq message is sent.

[0465] As an alternative exemplary implementation, the message requesting the start of the security check operation (S408) can be sent to another party via a mobile body or a distributor. The other party can then perform operation S408 in response to the message requesting the start of the security check operation (S408).

[0466] According to an exemplary embodiment of this disclosure, the messages sent and received in the safety detection operation (S408) can be defined based on the content of each fuel supply agreement as specified in a standard such as ISO 19885-3.

[0467] According to an exemplary embodiment of this disclosure, the messages sent and received in the security check operation (S408) may include a result type as a result of processing the request message. In this case, the values ​​that can be provided as a result type may include "OK" in the case of success, "Failure" in the case of failure, and "Pending" in other cases.

[0468] If the mobile entity confirms that all safety conditions are met when sending the SafetyCheckOutReq message to the distributor, the message's result value can be set to "OK".

[0469] If the mobile entity determines that certain safety conditions have not been met when the SafetyCheckOutReq message is sent to the allocator, the resulting value of the message can be set to "pending".

[0470] After receiving the SafetyCheckOutReq message, the allocator can respond to the moving body with a SafetyCheckOutRes message that includes safety check parameters within the MessageResponseTimeout interval.

[0471] If the allocator confirms that all safety conditions are met when sending the SafetyCheckOutRes message to the mobile body, the message's result value can be set to "OK".

[0472] If the allocator determines that certain safety conditions have not been met when the SafetyCheckOutRes message is sent to the mobile body, the message's result value can be set to "pending".

[0473] If a SafetyCheckOutRes message with a result value set to "Pending" is received, the mobile body can send another SafetyCheckOutReq message to the distributor within the MessageResponseTimeout interval.

[0474] Upon receiving a SafetyCheckOutReq message in which the result value is set to "pending", the allocator can transmit another SafetyCheckOutReq message to the mobile body within the MessageResponseTimeout interval.

[0475] If a mobile entity or distributor fails to verify all safety conditions within a predetermined time (e.g., UCSafetyCheckOutTimeout), the mobile entity or distributor may send an ErrNOtifReq message with a "Reason" field set to the appropriate error code.

[0476] As an alternative exemplary implementation, the mobile body or distributor may send a request message to the other party instructing the commencement of a security check operation (S408), and the other party may respond to the request message of the security check operation (S408) within a predetermined time interval.

[0477] According to an exemplary embodiment of this disclosure, when a non-safety-critical error is detected in the monitoring and control operation (S407) and the fuel supply is interrupted before completion, the fuel supply protocol can define a rollback mechanism that ensures backward compatibility in compatible mechanisms between the mobile body and the dispenser, and the pending fuel supply can be restarted based on the rollback mechanism.

[0478] For example, a fallback mechanism could be a method without communication fuel supply.

[0479] As an alternative exemplary implementation, when a non-safety-critical error is detected in the monitoring and control operation (S407) and the fuel supply is interrupted before completion, the mobile body and dispenser may re-execute some or all of the communication protocol negotiation operation (S403), the fuel supply protocol negotiation operation (S404), and the fuel supply parameter negotiation operation (S405).

[0480] As an alternative exemplary implementation, the mobile unit and the dispenser can reduce the amount of information exchanged during some or all of the re-execution of the communication protocol negotiation operation (S403), fuel supply protocol negotiation operation (S404), and fuel supply parameter negotiation operation (S405) by using the interoperability information obtained in the discovery and pairing operation (S401). For example, when it is determined that the communication state or fuel supply state does not allow the previously negotiated and selected protocol to be maintained, some or all of the communication protocol negotiation operation (S403), fuel supply protocol negotiation operation (S404), and / or fuel supply parameter negotiation operation (S405) other than the previously selected protocol can be re-executed.

[0481] As an alternative exemplary implementation, when a non-safety-critical error (such as a change in the communication environment or fuel supply infrastructure) is detected in the monitoring and control operation (S407), and the fuel supply is interrupted before completion, the mobile body and dispenser may re-execute some or all of the communication protocol negotiation operation (S403), the fuel supply protocol negotiation operation (S404), and the fuel supply parameter negotiation operation (S405).

[0482] Changes in the communication environment can include situations where communication channels are disconnected.

[0483] Changes in the communication environment may include situations where received data is not identified, or where the received data is within an unacceptable range.

[0484] Changes in the communication environment can include situations where the quality of communication performance does not meet or reach the required level.

[0485] Changes in the communication environment can include situations where the integrity or accuracy of data exchanged via communication does not meet the required level.

[0486] Changes to the fuel supply infrastructure may include situations where fuel supply parameters on the mobile body side are changed or maintained based on control parameters for fuel supply on the distributor side, but such changes or maintenance of fuel supply-related parameters on the mobile body side do not meet the required levels.

[0487] Table 19 shows some of the safety conditions that are checked or monitored in safety entry operations (S406), monitoring and control operations (S407), and / or safety exit operations (S408), but the following may be considered additionally or supplementarily.

[0488] Safety conditions may include elements related to the safety of the moving body and hydrogen supply or distributor, and / or elements related to the connection status of the nozzles and receivers on both sides used to initiate the hydrogen fuel supply.

[0489] Regarding hydrogen mobile bodies, pressure and temperature within the hydrogen tank can also be included.

[0490] On the hydrogen fuel supply station side, this can include the temperature inside the cylinder, the supply pressure, and the ambient temperature.

[0491] As a safety condition for the connection between the two sides and the fuel supply path, it can include the nozzle-fill port connection status, i.e. the presence of the connection, the connection status, and the leakage status.

[0492] The nozzle-fill port connection status may include information related to whether the status is suitable and / or sufficient to perform the hydrogen fuel supply procedure.

[0493] exist Figure 4 In an alternative exemplary implementation, when the safety check-in operation (S406) performs a minimum state confirmation check including safety elements such as whether the nozzle and filling port are connected and the connection status, the safety check-in operation (S406) may be performed before the fuel supply parameter negotiation operation (S405).

[0494] exist Figure 4 In an alternative exemplary implementation, when the safety check operation (S406) performs checks on safety elements including minimum state confirmation of whether the nozzle and filling port are connected and their connection status, any remaining safety elements not checked in the safety check operation (S406) may be negotiated and checked in the fuel supply parameter negotiation operation (S405).

[0495] exist Figure 4 In an alternative exemplary implementation, when the safety check operation (S406) performs checks on safety elements including minimum state confirmation such as whether the nozzle and filling port are connected and their connection status, any remaining safety elements not checked in the safety check operation (S406) can be monitored and checked in the monitoring and control operation (S407). Safety elements can be monitored and checked in the monitoring and control operation (S407) regardless of whether negotiation and checks were performed in the fuel supply parameter negotiation operation (S405).

[0496] exist Figure 4 In an alternative exemplary implementation, multiple safety elements, including those checked in the safety check-in operation (S406), can be negotiated and checked in the fuel supply parameter negotiation operation (S405).

[0497] exist Figure 4 In an alternative exemplary implementation, multiple safety elements, including the safety element checked in the safety check-in operation (S406), can be monitored and checked in the monitoring and control operation (S407). Safety elements can be monitored and checked in the monitoring and control operation (S407) regardless of whether negotiation and checking were performed in the fuel supply parameter negotiation operation (S405).

[0498] exist Figure 4 In one alternative exemplary implementation, sharing, identification, monitoring, updating, and / or leveraging interoperability and / or compatibility can be performed throughout the process.

[0499] For example, in the discovery and pairing operation (S401), the interoperability-related information shared between the mobile body and the distributor / station can be checked in each case of subsequent operations (S402 to S411), and exemplary implementations can be presented in which the interoperability information is updated or reconfirmed as available interoperability information in each operation.

[0500] For example, if the combination of interoperable protocols (combination of communication protocols and fuel supply protocols) available between the mobile body and the dispenser is 10, in subsequent operations, some of these 10 protocols may become incompatible or unavailable due to communication / system errors, changes in the communication / system environment, or changes in the fuel supply environment, thus reducing the number of available protocol combinations to less than 10. Such a situation can be checked in operations (S402 to S411) corresponding to each use case, and as a result, the interoperability information can be updated to include available interoperability information, and each operation can be performed based on the updated interoperability information.

[0501] Furthermore, for example, when a particular available interoperable protocol combination A is determined to be temporarily incompatible or unavailable during intermediate operations, the operation can be performed by replacing it with another interoperable protocol or falling back to another interoperable protocol.

[0502] For example, when multiple available interoperable protocol combinations are identified in operations S401 to S403, and interoperable protocol combination A is selected as a result of communication protocol negotiation based on preference and / or priority, and subsequently in operation S404, it is determined that interoperable protocol combination A is unavailable due to changes in the communication / system environment, errors, and / or changes in the fuel supply environment, as a result of fuel supply protocol negotiation, it can be determined to select another interoperable protocol combination B based on preference and / or priority, or to fall back to another interoperable protocol combination B, and operation S404 and subsequent operations can be performed.

[0503] In a similar alternative exemplary implementation, when multiple available interoperable protocol combinations are identified in operations S401 to S404, and among the combinations, interoperable protocol combination A is selected as a result of fuel supply protocol negotiation based on preference and / or priority, and subsequently in operation S405, interoperable protocol combination A is determined to be unavailable due to changes in the communication / system environment, errors, and / or changes in the fuel supply environment, as a result of communication protocol negotiation and fuel supply protocol negotiation, another interoperable protocol combination B selected based on preference and / or priority, or a fallback interoperable protocol combination B, can replace interoperable protocol combination A, and operation S405 and subsequent operations can be performed.

[0504] In a similar alternative exemplary implementation, when multiple available interoperable protocol combinations are identified in operations S401 to S406, and among the combinations, interoperable protocol combination A is selected as a result of communication protocol negotiation, fuel supply protocol negotiation, and fuel supply parameter negotiation based on preference and priority, and subsequently in operation S407, if interoperable protocol combination A is determined to be unavailable due to changes in the communication / system environment, errors, and / or changes in the fuel supply environment, another interoperable protocol combination B selected based on preference and / or priority, or a fallback interoperable protocol combination B, can replace interoperable protocol combination A as a result of communication protocol negotiation, fuel supply protocol negotiation, and fuel supply parameter negotiation, and hydrogen fuel supply and subsequent operations can be performed according to operation S407.

[0505] In another alternative implementation, for example, when a particular available interoperable protocol combination A becomes unavailable during intermediate operation and is performed by substitution or fallback to another interoperable protocol, and subsequently becomes available again in a later operation, the subsequent operation can be performed using the interoperable protocol combination A based on a renegotiated or predetermined strategy.

[0506] For example, in operations S401 to S406, among multiple available interoperable protocol combinations, interoperable protocol combination A is selected as a result of communication protocol negotiation, fuel supply protocol negotiation, and fuel supply parameter negotiation based on preference and priority. Subsequently, in operation S407, after it is determined that interoperable protocol combination A is unavailable due to changes in the communication / system environment, errors, and / or changes in the fuel supply environment, and subsequent operations are performed based on the selected or backed-to another interoperable protocol combination B according to the hydrogen fuel supply in operation S407, when it is determined that interoperable protocol combination A is available again due to changes in the communication / system environment, errors, and / or changes in the fuel supply environment, interoperable protocol combination A can be restored through renegotiation between the mobile unit and the distributor / station or through a predetermined recovery process.

[0507] exist Figure 4 In an alternative exemplary implementation, when the previously selected best / preferred protocol combination among the interoperable protocol combinations available between the mobile body and the dispenser becomes incompatible or unavailable, in determining alternative second-preferred / second-preferred protocol combinations, a combination of communication protocols that remain the same as the previously selected best / preferred protocol combination when the fuel supply protocol is changed, or a combination that keeps the fuel supply protocol unchanged when the communication protocol is changed, can be searched.

[0508] exist Figure 4 In an alternative exemplary implementation, when generating first interoperability information by searching for available protocol combinations in the discovery and pairing process (operation S401), priorities can be predetermined such that matching of the communication protocol and the fuel supply protocol is preferred. For example, when a combination of communication protocol A1 and fuel supply protocol B1 is determined to be the most preferred / preferred combination, a combination of communication protocol A1 and fuel supply protocols B2, B3, ... that can coexist with communication protocol A1 can be predetermined by giving high priority to alternative combinations that are the most preferred / preferred combination. Alternatively, while maintaining fuel supply protocol B1, a combination of fuel supply protocol B1 and communication protocols A2, A3, ... that can coexist with fuel supply protocol B1 can be predetermined by giving high priority to alternative combinations that are the most preferred / preferred combination.

[0509] exist Figure 4 In an alternative exemplary implementation, when operations S403 to S409 are performed, an update process for the most preferred / preferred combination of interoperable protocols can be performed by renegotiating some or all of operations S403 to S405.

[0510] exist Figure 4 In an alternative exemplary implementation, when operations S403 to S409 are performed, an update process for the most preferred / preferred combination of interoperable protocols can be performed by a portion or all of operations S410 or S411.

[0511] exist Figure 4 In an alternative exemplary implementation, when operations S403 to S409 are performed, an update process for the most preferred / preferred combination of interoperable protocols can be performed by renegotiating part or all of operations S403 to S405 via operations S410 or S411.

[0512] A communication method for hydrogen fuel supply according to an exemplary embodiment of this disclosure may include: in operation S401, after the mobile body, or the distributor, or the mobile body and the distributor collaboratively determine the most preferred / preferred combination of interoperable protocols, (with the assistance of operations S410 and S411) determining the most preferred / preferred combination of interoperable protocols during the execution of operations S403 to S409. The method may also include performing one or more of a first process or a subsequent process of the first process based on a first communication protocol and a first fuel supply protocol. Since the interoperability communication protocol and fuel supply protocol determined based on updated interoperability information may partially limit the functionality on the mobile body side or may partially limit the communication functionality between the mobile body and the distributor, in some cases, a separate distributor or a distributor in a leading manner may perform the hydrogen fuel supply process or its subsequent processes. That is, when interoperability is degraded or reverted, the distributor may perform more functions than the mobile body.

[0513] Refer again Figure 4 When fuel supply is successfully completed and all safety conditions are optionally confirmed, a termination use case between the mobile body and the dispenser can be performed.

[0514] The objectives, prerequisites, and follow-up conditions for the termination operation (S409) can be shown in Table 25 below.

[0515] [Table 25]

[0516] When a mobile entity receives a SafetyCheckOutRes message with "Result" set to "Completed", or a FuelLoopRes message with "Status" set to a value prefixed with "Completed" or "Stopped" and omitting the safety checkout use case, the mobile entity may send a termination request message (e.g., "TerminateReq") to the allocator.

[0517] Details regarding termination request messages (e.g., "TerminateReq") can be defined in the specification of each fuel supply protocol. For example, the parameters included in the TerminateReq message and exchanged between the mobile body and the distributor can be defined differently depending on the individual fuel supply protocol.

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

[0519] [Table 26]

[0520] When the allocator receives a TerminateReq message from the mobile body, the allocator may respond with a termination response message (e.g., TerminateRes) within a predetermined time interval (e.g., MessageResponseTimeout).

[0521] Details regarding termination response messages (e.g., TerminateRes) can be defined in the specification of each fuel supply protocol. For example, the parameters included in the TerminateRes message and exchanged between the mobile entity and the distributor can be defined differently depending on the individual fuel supply protocol.

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

[0523] [Table 27]

[0524] As an alternative exemplary implementation, the message requesting the initiation of a termination operation (S409) can be sent from the mobile body or the distributor to the other party. The other party can perform the termination operation (S409) by responding to the message requesting the initiation of a termination operation (S409).

[0525] For successful fuel supply to occur, communication is required to deliver the expected behavior according to the protocol. Fuel supply behavior needs to remain within acceptable limits defined by the fuel supply protocol. However, in reality, various anomalies can occur. Some errors are minor and easily handled. However, some errors may be irreversible and prevent the fuel supply process from continuing.

[0526] In this specification, the term "error" may refer to an event that occurs during UC1 to UC9 (S401 to S409) or during hydrogen fuel supply, which may interrupt the ongoing process.

[0527] In operation S410, conditions for non-safety critical errors, exemplary error conditions, and responses to them can be defined.

[0528] Refer again Figure 4 The objectives, prerequisites, and follow-up conditions of the error handling operation (S410) can be shown in Table 28 below.

[0529] [Table 28]

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

[0531] Communication errors can include: 1) communication failure; 2) received data that cannot be recognized or interpreted due to encoding or syntax errors; and 3) received data that is within an unacceptable range.

[0532] As a system error, it can include situations where the allocator or the mover detects a critical system error of itself.

[0533] As a qualitative error, it can include: 1) situations where communication performance does not meet the required level; and 2) situations where the quality of data integrity or accuracy does not meet the required level.

[0534] When a non-safety-critical error occurs and further communication is impossible, the mobile unit and dispenser immediately stop fuel supply but take safety steps and cease communication to end the session.

[0535] When a non-safety-critical error occurs and the fuel supply is interrupted before it is fully completed, the fuel supply protocol can, for example, define a fallback mechanism by defining a non-communication fuel supply method.

[0536] When a mobile entity detects a non-safety-critical error and the communication channel is still operational, the mobile entity can send a TerminateReq message, where the "Action" is set to "Stop" and the "Reason" is set to the appropriate reason code.

[0537] When the dispenser detects a non-safety-critical error and the communication channel is still running, the dispenser can first immediately stop the fuel supply and then send a TerminateReq message, where the "Action" is set to "Stop" and the "Reason" is set to the appropriate reason code.

[0538] Fuel supply agreements can define error conditions and provide prescribed response procedures, including detection criteria, notifications, termination procedures, and rollback mechanisms.

[0539] Refer again Figure 4 The objectives, prerequisites, and follow-up conditions of the emergency response operation (S411) can be shown in Table 29 below.

[0540] [Table 29]

[0541] Fuel supply agreements can define emergency situations and provide prescribed response procedures to prevent entry into harmful situations by all means, including detection criteria, notification, termination procedures, and rollback mechanisms.

[0542] When a mobile device or distributor detects a safety-critical situation, it can immediately take necessary actions to prevent catastrophic events. Furthermore, if possible, an EmergencyNotif message can be sent along with information about the event, and communication can be shut down.

[0543] When a mobile entity or distributor receives an EmergencyNotif message, it can immediately respond to the action indicated in the message and can close the communication without undue delay.

[0544] Depending on the communication technology used, the EmergencyNotif message can be a TLS or DTLS message.

[0545] Modifications to the structure of the EmergencyNotif message may not be permitted by the fuel supply protocol due to the criticality and delivery efficiency of the message.

[0546] The element names included in an EmergencyNotif message may include level, type, action (or operation, procedure, and / or sequence), etc., and may be shown in Table 30 below. Elements not shown in Table 30 may, for example, be specified by each fuel supply protocol specification such as ISO 19885-3. For example, each protocol may specify additional emergency cause codes and action codes.

[0547] [Table 30]

[0548] Figure 16 It is shown Figure 4 A flowchart of an alternative exemplary implementation.

[0549] like Figure 16 As shown, it illustrates what has been added Figure 4 The relationship between operations S401 to S409 and operations S2010 to S2030.

[0550] like Figure 4 and Figure 16 As shown, a communication method for hydrogen fuel supply performed by a communication device of a hydrogen fuel vehicle according to an exemplary embodiment of the present disclosure may include: detecting an error occurring during a communication process (operations S403 to S406 or S408 to S409) for preparing hydrogen fuel supply between a distributor for supplying hydrogen to the vehicle and the vehicle (operation S407) (operation S2010; this may be performed as part of operations S403 to S409), determining whether to stop the communication process (operations S403 to S406 or S408 to S409) or the hydrogen fuel supply process (operation S407) in response to the detected error (operation S2020; may be performed as part of operations S410 or S411), and performing a subsequent process defined based on the detected error (not shown as a separate operation; performed as part of operations S403 to S411).

[0551] It is possible Figure 4 In operation S401, the following exemplary implementation is performed based on interoperability or compatibility information shared between the mobile body and the distributor. Specifically, in operations S403 to S405, communication protocols, fuel supply protocols, and fuel supply parameters can be negotiated and determined within the scope of the interoperability or compatibility information.

[0552] Interoperability or compatibility information is identified and shared during operation S401, but during subsequent processes, interoperability or compatibility information can be re-identified and shared in the updated state based on the current situation.

[0553] In a communication method for hydrogen fuel supply performed by a communication device of a mobile body according to an exemplary embodiment of the present disclosure, determining whether to stop the communication process or the hydrogen fuel supply process in response to a detected error (operation S2020, which may be performed as part of operation S410 or S411) may include classifying the detected error as a safety-critical error or a non-safety-critical error.

[0554] Detected errors can be classified as safety-critical errors through operation S2020, and can be used as... Figure 4 This is part of operation S411. When a detected error is classified as a safety-critical error, subsequent processes can be executed through separate operations (S403 to S409), and can also be used as... Figure 4 This is part of the execution of operation S411. Errors classified as safety-critical errors can be considered as emergency situations.

[0555] In the communication method for hydrogen fuel supply executed by a communication device of a mobile body according to an exemplary embodiment of the present disclosure, determining whether to stop the communication process or the hydrogen fuel supply process in response to a detected error (operation S2020) may further include classifying the detected error as any one of a communication error, a system error, or a qualitative error when the detected error is a non-safety-critical error (executed as part of operation S410).

[0556] In a communication method for hydrogen fuel supply performed by a communication device of a mobile body according to an exemplary embodiment of the present disclosure, when the detected error is a safety-critical error, performing subsequent processes based on the definition of the detected error may include at least a portion of an emergency handling process (operation S411).

[0557] In a communication method for hydrogen fuel supply performed by a communication device of a mobile body according to an exemplary embodiment of the present disclosure, determining whether to stop the communication process or the hydrogen fuel supply process in response to a detected error (operation S2020) may further include determining whether to replace the first fuel supply protocol of the communication process or the hydrogen fuel supply process with a second fuel supply protocol that has been rolled back when the detected error is a non-safety-critical error.

[0558] In a communication method for hydrogen fuel supply performed by a communication device of a mobile body according to an exemplary embodiment of the present disclosure, performing subsequent processes based on a detected error definition may include sending a message including whether to stop the communication process or the hydrogen fuel supply process to a distributor.

[0559] Various types of events occurring during the execution of operations S403 to S409 can be detected by a moving body or distributor (operation S2010). Detected events can be classified as errors based on the fulfillment of predetermined conditions (operations S2010 and S2020). When a detected error is a non-safety-critical error, it can be handled through the error handling procedure of operation S410 or through separate follow-up operations. When a detected error is a safety-critical error, it can be handled through the emergency handling procedure of operation S411.

[0560] In an exemplary embodiment of this disclosure, criteria for classifying detected errors as non-safety-critical errors or safety-critical errors (emergency situations) can be predefined by operating the fuel supply protocol of S403 to S409, and the detected error can be classified by operating each of S403 to S409 when the error is detected.

[0561] In an alternative exemplary embodiment of this disclosure, after an error is detected, the error can be passed to operations S410 and / or S411, and each of operations S410 and / or S411 can classify whether the detected error is a non-safety-critical error or a safety-critical error (emergency). That is, operation S410 can classify whether the error is a non-safety-critical error, and when the error is a non-safety-critical error, classify the error as a communication error, a system error, or a qualitative error. Operation S411 can classify whether the error is a safety-critical error.

[0562] Operation S410 can classify detected errors and determine whether to stop the fuel supply process based on the classification result or the status of the error. When it is determined, based on updated interoperability or compatibility information, that the fuel supply process should not be stopped but should continue using the rollback fuel supply protocol, as a result of operation S410, the operations required to continue the fuel supply process in operations S403 to S409 can be performed again.

[0563] Furthermore, in operation S410 or S411, when the cause of the error is removed and the normal state is restored, the mobile body or dispenser can return individually or collaboratively to any of the operations S403 to S409 that were performed before the error occurred, or return to the subsequent process, and can continue the hydrogen fuel supply process and the communication process.

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

[0565] In a communication method for hydrogen fuel supply performed by a communication device of a distributor according to an exemplary embodiment of the present disclosure, determining whether to stop the communication process or the hydrogen fuel supply process in response to a detected error (operation S2020; which may be performed as part of operation S410 or S411) may include classifying the detected error as a safety-critical error or a non-safety-critical error.

[0566] In the communication method for hydrogen fuel supply executed by the communication device of the distributor according to an exemplary embodiment of the present disclosure, determining whether to stop the communication process or the hydrogen fuel supply process in response to a detected error (operation S2020) may further include classifying the detected error as any one of a communication error, a system error, or a qualitative error when the detected error is a non-safety-critical error (this may be performed as part of operation S410).

[0567] In a communication method for hydrogen fuel supply performed by a distributor's communication device according to an exemplary embodiment of the present disclosure, when the detected error is a safety-critical error, performing subsequent procedures based on the definition of the detected error may include at least a portion of an emergency handling procedure (operation S411).

[0568] In a communication method for hydrogen fuel supply executed by a communication device of a distributor according to an exemplary embodiment of the present disclosure, determining whether to stop the communication process or the hydrogen fuel supply process in response to a detected error (operation S2020) may further include determining whether to replace the first fuel supply protocol of the communication process or the hydrogen fuel supply process with a second fuel supply protocol of fallback when the detected error is a non-safety-critical error.

[0569] In a communication method for hydrogen fuel supply performed by a communication device of a distributor according to an exemplary embodiment of the present disclosure, performing a subsequent process based on a detected error definition may include: performing the hydrogen fuel supply process based on a second fuel supply protocol when a first fuel supply protocol of the communication process or the hydrogen fuel supply process is replaced by a second fuel supply protocol.

[0570] In the event of a communication error, the distributor can select a second fuel supply protocol based on a first fuel supply protocol or predefined rules by applying a predefined fallback, and can perform hydrogen fuel supply based on the second fuel supply protocol.

[0571] In the event of a communication error, the mobile entity or distributor may terminate the session as needed.

[0572] In the event of a system error, the mobile entity or distributor may terminate the session as needed. The mobile entity or distributor may terminate the session based on the detected error and send a message to the other party including the termination action and a reason code corresponding to the cause.

[0573] In an alternative implementation, in the event of a qualitative error, a fallback fuel supply protocol based on a limited communication protocol or communication environment can be selected based on updated interoperability or compatibility information between the mobile unit and the distributor, and hydrogen fuel supply can be performed based on the selected fuel supply protocol.

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

[0575] In an alternative implementation, in the event of a qualitative error, renegotiation can be performed between the mobile unit and the distributor to select a new combination of communication and fuel supply protocols. In such a case, for renegotiation, portions of operations S403 to S405 can be performed again, or renegotiation can be performed within operation S410.

[0576] In an alternative implementation, even in an emergency, subsequent processes can be performed while communication is still available, albeit with minimal communication. The mobile unit or distributor can revert to communication and fuel supply protocols.

[0577] In an alternative implementation, fuel supply and communications can be shut down first in an emergency.

[0578] In a communication method for hydrogen fuel supply performed by a communication device of a distributor according to an exemplary embodiment of the present disclosure, performing subsequent processes based on a detected error definition may include sending a message containing whether to stop the communication process or the hydrogen fuel supply process to the mobile body.

[0579] In a communication method for hydrogen fuel supply executed by a communication device of a distributor according to an exemplary embodiment of the present disclosure, when a message including whether to stop the communication process or the hydrogen fuel supply process includes a stop instruction, the message may also include a reason code corresponding to an appropriate reason for the stop.

[0580] In a communication method for hydrogen fuel supply performed by a communication device of a mobile body and / or dispenser according to one of the alternative embodiments of this disclosure, the criticality of the error can be determined based on the UCDC level of the available communication or fuel supply process associated with the detected error. Furthermore, whether to stop fuel supply can be determined based on the UCDC level. The process of determining the criticality of the error and / or whether to stop fuel supply based on the UCDC level can be applied when the error is a qualitative error. However, this embodiment does not limit the scope of this disclosure.

[0581] exist Figure 4 and Figure 16 Examples of operations S403 to S409 related to operations S2010, S2020, S410, and / or S411 have been shown in exemplary embodiments. In one alternative embodiment of this disclosure, operations S2010 and S2020 may detect any event occurring in operations S401 to S409 or during the fuel supply process, determine whether the event is an error, and classify the error. Furthermore, in alternative embodiments of this disclosure, as part of and a separate follow-up process to operations S2010 and S2020, subsequent processes may be performed after operations S410 and S411, or, when an error is resolved, operations S401 to S409 may be returned to perform existing processes and / or subsequent processes.

[0582] That is, operations S2010 and S2020 can detect events, determine whether an event is an error, detect errors, or classify them in operations S401-UC1: discovery and pairing, S402-UC2: communication security, S403-UC3: communication protocol negotiation, S404-UC4: fuel supply protocol negotiation, S405-UC5: fuel supply parameter negotiation, S406-UC6: safety check-in, S407-UC7: fuel supply control and monitoring, S408-UC8: safety check-out, and S409-UC9: errors occurring during termination or in parallel hydrogen fuel supply.

[0583] Furthermore, after errors are classified and processed in operation S410 or S411, the process can return to operation S401 to S409 or the parallel hydrogen fuel supply process.

[0584] Furthermore, after the error has been processed and resolved, it is possible to return to the process executed before the error occurred or to subsequent processes, such as operations S401 to S409 or the parallel hydrogen fuel supply process.

[0585] In one alternative implementation, as a criterion for determining whether an error is safety-critical, consideration may be given to whether events that may occur before, during, or after the supply of hydrogen fuel pose a hazard to the facility and / or human life, or result in fire, explosion, leak, etc.

[0586] In some cases, safety-critical errors may lead to the cessation and / or termination of communications and fuel supply. In alternative implementations, even in the event of a safety-critical error, fuel supply may continue when communications are secure or fuel supply is feasible, or when continued fuel supply is required (for reasons such as evacuation from a hazardous location or transport of a patient).

[0587] In the event of a non-safety-critical error, communication or fuel supply may be stopped or may continue, depending on the criticality or severity of the error, the available communication environment, the available fuel supply protocol, the UCDC level, and the necessity of communication or fuel supply.

[0588] In the exemplary embodiments described above, constant monitoring of interoperability, corresponding updates to interoperability information, and / or updates to the communication / fuel supply protocol combination have been primarily described in the context of being performed by a mobile body or distributor. However, it will be apparent that these detailed processes can be performed by the mobile body or distributor, or through cooperation between the mobile body and the distributor. In alternative embodiments of this disclosure, a portion of the constant monitoring of interoperability, updates to interoperability information, and / or updates to the communication / fuel supply protocol combination may be initiated by the mobile body, while another portion may be initiated by the distributor.

[0589] In addition, error detection can be performed by a moving entity or distributor, and an entity that has detected an error can send a message to the other party, which includes the error detection, the detected error, the cessation of communication and fuel supply based on the error, or a reason code corresponding to the reason for the cessation.

[0590] Figure 17 This is a flowchart illustrating a communication method for hydrogen fuel supply according to another exemplary embodiment of the present disclosure.

[0591] like Figure 16 and Figure 17 As shown, the communication method for hydrogen fuel supply according to an exemplary embodiment of this disclosure is performed by a communication device of a hydrogen fuel vehicle, and the communication method may include: discovering a dispenser for supplying hydrogen to the vehicle; sharing pairing information between the vehicle and the dispenser; and performing pairing between the vehicle and the dispenser (S2100); negotiating a communication protocol or fuel supply protocol between the vehicle and the dispenser for the process of supplying hydrogen from the dispenser to the vehicle based on interoperability or compatibility-related information between the vehicle and the dispenser (S2200); and sending information required for monitoring and controlling the process of supplying hydrogen from the dispenser to the vehicle based on the fuel supply protocol to the dispenser (S2300). In this case, the operation performed in step S2100 may include Figure 4 and Figure 16 Some or all of the operations in step S401. Operations performed for monitoring and control may include... Figure 4 and Figure 16 Some or all of the operations in step S407 can be performed in step S2300. The operations that the dispenser can perform in step S407 and / or the operations that the moving body can perform in step S407 can be performed in step S2300.

[0592] The communication method for hydrogen fuel supply according to an exemplary embodiment of this disclosure may further include: after pairing is performed in step S2100, establishing a secure channel between the mobile body and the dispenser to negotiate a communication protocol or a fuel supply protocol (see...). Figure 4 and Figure 16 Step S402 in the process.

[0593] The communication method for hydrogen fuel supply according to an exemplary embodiment of this disclosure may further include: after negotiating a communication protocol or fuel supply protocol in step S2200, before the distributor supplies hydrogen fuel to the mobile body, performing an access step to check whether a first necessary safety condition between the mobile body and the distributor is met (see [link to relevant documentation]). Figure 4 and Figure 16 Step S406 in the process); and after the process of supplying hydrogen to the mobile body and before the nozzle is disengaged from the mobile body, a detection step is performed to check whether the second necessary safety condition between the mobile body and the dispenser is met (see step S406 in the process ... Figure 4 and Figure 16 Step S408 in the process.

[0594] According to alternative exemplary embodiments of this disclosure, the first necessary safety condition and / or the second necessary safety condition may include the coupling state between the nozzle and the filling port, the sealing state of the coupling portion, temperature, pressure, or the residual state of charge (SoC) of the hydrogen storage tank on the moving body or dispenser side.

[0595] The communication method for hydrogen fuel supply according to an exemplary embodiment of this disclosure may further include: detecting and processing non-safety-critical errors occurring during the execution of step S2200 for negotiating a communication protocol or a fuel supply protocol, or during step S2300 for sending information required for monitoring and control to a distributor (see...). Figure 16 Steps S2010 and S410 in the process); and detecting and handling emergencies during the execution of step S2200 for negotiating a communication protocol or a fuel supply protocol, or step S2300 for sending information required for monitoring and control to the distributor, in which interoperability between the distributor and the mobile unit must cease (see steps S2010 and S410 in the process); and detecting and handling emergencies during the execution of step S2200 for negotiating a communication protocol or a fuel supply protocol, or step S2300 for sending information required for monitoring and control to the distributor, in which case interoperability between the distributor and the mobile unit must cease (see steps S2010 and S410 in the process). Figure 16 Steps S2020 and S411 in the process.

[0596] In a communication method for hydrogen fuel supply according to an exemplary embodiment of the present disclosure, step S2200 of negotiating a communication protocol or a fuel supply protocol may include negotiating a communication protocol between the mobile body and the dispenser (see...). Figure 4 and Figure 16 Step S403); based on the communication protocol, negotiate a fuel supply agreement between the mobile unit and the distributor (see step S403). Figure 4 and Figure 16 Step S404 in the text); and based on the fuel supply agreement, negotiating fuel supply parameters between the mobile unit and the distributor (see step S404 in the text). Figure 4 and Figure 16 Step S405 in the process.

[0597] In a communication method for hydrogen fuel supply according to an exemplary embodiment of the present disclosure, in step S2200 of negotiating a communication protocol or a fuel supply protocol, the information of the communication protocol or fuel supply protocol transmitted between the dispenser and the mobile body may include protocol name, index, version, priority, or preference.

[0598] In a communication method for hydrogen fuel supply according to an exemplary embodiment of the present disclosure, the pairing information shared between the mobile body and the dispenser in step S2100 for performing pairing may include interoperability or compatibility-related information between the mobile body and the dispenser.

[0599] In the communication method for hydrogen fuel supply according to an exemplary embodiment of the present disclosure, interoperability or compatibility-related information between the mobile body and the distributor can be updated based on the status information at the time of step S2200 of negotiating a communication protocol or a fuel supply protocol or step S2300 of sending information required for monitoring and control to the distributor. Furthermore, step S2200 of negotiating a communication protocol or a fuel supply protocol or step S2300 of sending information required for monitoring and control to the distributor can be performed based on the updated interoperability or compatibility-related information.

[0600] The communication method for hydrogen fuel supply according to an exemplary embodiment of this disclosure may further include: when a non-safety-critical error is detected during step S2200 of executing a negotiation communication protocol or a fuel supply protocol (see... Figure 16 When steps S2010 and S410 are performed, part or all of step S2200 of negotiating the communication protocol or fuel supply protocol is executed again.

[0601] In step S407 of the communication method for hydrogen fuel supply according to an exemplary embodiment of the present disclosure, in which information required for monitoring and control is sent to the distributor, the information sent from the mobile body to the distributor may be determined based on whether the fuel supply agreement allows bidirectional communication between the mobile body and the distributor as a communication protocol.

[0602] According to an exemplary embodiment of this disclosure, a communication method for supplying hydrogen fuel, executed by a communication device for supplying hydrogen fuel to a hydrogen fuel vehicle, may include: discovering the vehicle; sharing pairing information between the vehicle and the distributor; and performing pairing between the vehicle and the distributor (S2100); negotiating a communication protocol or fuel supply protocol between the vehicle and the distributor for the process of supplying hydrogen from the distributor to the vehicle based on interoperability or compatibility-related information between the vehicle and the distributor (S2200); and monitoring and controlling the process of supplying hydrogen from the distributor to the vehicle based on the fuel supply protocol (S2300).

[0603] The communication method for hydrogen fuel supply performed by the communication device of the dispenser according to an exemplary embodiment of the present disclosure may further include: after pairing is performed in step S2100, establishing a secure channel between the mobile body and the dispenser to negotiate a communication protocol or a fuel supply protocol (S402).

[0604] The communication method for hydrogen fuel supply executed by the communication device of the dispenser according to an exemplary embodiment of the present disclosure may further include: after negotiating a communication protocol or fuel supply protocol in step S2200, before the dispenser supplies hydrogen fuel to the mobile body, performing an entry step (S406) to check whether a first necessary safety condition between the mobile body and the dispenser is met; and after the process of supplying hydrogen to the mobile body and before the nozzle is disengaged from the mobile body, performing an exit step (S408) to check whether a second necessary safety condition between the mobile body and the dispenser is met.

[0605] The communication method for hydrogen fuel supply executed by the communication device of the distributor according to an exemplary embodiment of the present disclosure may further include: detecting and handling non-safety-critical errors (S2010 and S410) that occur during step S2200 of executing the negotiation communication protocol or fuel supply protocol or during steps S2300 and S407 of controlling and monitoring the process of supplying hydrogen from the distributor to the mobile body; and detecting and handling emergency situations (S2020 and S411) during step S2200 of executing the negotiation communication protocol or fuel supply protocol or during steps S2300 and S407 of controlling and monitoring the process of supplying hydrogen from the distributor to the mobile body, in which case the interoperability between the distributor and the mobile body must be stopped.

[0606] In a communication method for hydrogen fuel supply performed by a communication device of a distributor according to an exemplary embodiment of the present disclosure, step S2200 of negotiating a communication protocol or a fuel supply protocol may include: negotiating a communication protocol between a mobile body and a distributor (S403); negotiating a fuel supply protocol between a mobile body and a distributor based on the communication protocol (S404); and negotiating fuel supply parameters between a mobile body and a distributor based on the fuel supply protocol (S405).

[0607] A communication method for hydrogen fuel supply according to an exemplary embodiment of this disclosure may include: as Figure 4 Step S401 in Figure 16 Step S401 and Figure 17 As part of step S2100, interoperability or compatibility information between the mobile body and the distributor is checked based on the pairing information.

[0608] exist Figure 17 The method shown can be executed by a moving body or by a distributor, and can be executed through cooperation between the moving body and the distributor.

[0609] exist Figure 17 In an exemplary implementation, the entity communicating with the mobile body is described as a distributor, but the communication means of the distributor or station may communicate with the mobile body individually or collaboratively.

[0610] For example, a station can be equipped with multiple wireless LAN access points (APs), some of which are assigned to a distributor, and some of which can participate in communication with the mobile body without being directly assigned to a distributor.

[0611] In step S2100, wireless communication may be used to share information about pairing between the mobile body and the distributor (or station), and may include a process of using the pairing information to discover the existence of the counterpart.

[0612] Step S2100 may be a process of checking whether the pairing between the mobile body and the distributor is correct. In this case, the entity performing the pairing check may be either the mobile body or the distributor (station).

[0613] In step S2100 and in subsequent processes based on pairing information (based on interoperability and compatibility information in the pairing information), the dispenser and the mobile body can perform subsequent processes related to the communication protocol or fuel supply protocol for supplying hydrogen from the dispenser to the mobile body by sending and receiving at least one message between the dispenser and the mobile body. This process can, for example, correspond to... Figure 17 Step S2200 and Figure 4 and / or Figure 16 Steps S403 to S405 in the process.

[0614] According to an exemplary embodiment of this disclosure, hydrogen fuel vehicles and dispensers or stations find each other, check compatibility, and verify that the pairing is correct, thereby supporting the start of the hydrogen fuel supply process and shortening the process until the start of the hydrogen fuel supply process.

[0615] Furthermore, according to an exemplary embodiment of this disclosure, during the discovery and pairing process, hydrogen fuel cell vehicles and dispensers or stations can provide each other with the functions, communication protocols, and / or fuel supply protocols that the hydrogen fuel cell vehicles and dispensers or stations have, respectively, by using standardized data fields such as supplier-specific elements (VSEs).

[0616] In this context, according to an exemplary embodiment of this disclosure, information such as interoperability and compatibility required in subsequent processes can be shared with the counterparties, and the process up to the start of the hydrogen fuel supply process can be shortened.

[0617] In step S2100 of discovering the distributor, the messages sent and received between the distributor and the mobile body may include a VSE (Vendor Specific Element) data field, and the VSE data field may include at least a portion of the information about the pairing.

[0618] As at least part of the information about pairing, the VSE data field may include the specification supported by the dispenser or mobile body, the version of the specification, the fuel supply protocol supported by the dispenser or mobile body, the communication protocol supported by the dispenser or mobile body, or identification information for pairing of the dispenser or mobile body.

[0619] The specifications supported by the distributor or moving body can be, for example, known standard specifications such as ISO 19885, or may include whether a specific standard specification is supported. The version of the specification can indicate the version of a specific standard specification.

[0620] For example, VSE can indicate that the mobile unit or dispenser is an ISO 19885 device and can include compatibility information, which includes a list of supported communication or fuel supply protocols.

[0621] Furthermore, identifier (ID) information for pairing can be added to the VSE data field. In step S2100, the pairing ID can be used for pairing between the mobile body and the distributor.

[0622] VSE (Vendor Specific Element) data fields can be added to beacon, probe request or response, association request (AssocReq) or reassoc request (ReassocReq) messages.

[0623] In steps S2100 and S2200, wireless communication technologies such as wireless LAN (WLAN) can be used. Pairing information and / or interoperability and compatibility information can be shared between the mobile unit and the distributor or station using the VSE (Vendor Specific Element) data field.

[0624] The pairing information may include the dispenser's location information or precise positioning information. Additionally, further pairing information can be provided via the fuel supply cable between the mobile unit and the dispenser.

[0625] Pairing information can be exchanged using communication technologies other than wireless LAN (e.g., wired, NFC, RFID, barcodes, etc.). In this case, short-range communication technologies can support precise location measurement and positioning.

[0626] The process of checking or verifying a pair can be performed as a one-way pairing. In this case, in an exemplary embodiment of one-way pairing, the moving body can check the dispenser. According to an exemplary implementation, the dispenser can check the moving body, and both parties can check each other.

[0627] In the exemplary embodiments described above, an exemplary implementation has been shown where the message includes a list of communication protocols. However, in another exemplary embodiment of this disclosure, the message may include a list of fuel supply protocols or fuel supply parameters. Furthermore, the list of communication protocols may be exchanged in association with a list of supported fuel supply protocols.

[0628] In this context, the first message can represent a message sent by at least one wireless communication entity (2310, 2320, 2330) based on wireless communication technology. For example, in the case of Bluetooth-based communication, the first message can be sent in the form of a beacon message, and in the case of wireless LAN-based communication, the first message can be sent in the form of a message permitted in wireless LAN communication. In exemplary embodiments of this disclosure, the communication technology upon which the first message relies is not limited to a specific communication medium.

[0629] In a communication method for hydrogen fuel supply performed by a communication device of a hydrogen fuel vehicle according to an exemplary embodiment of the present disclosure, interoperability or compatibility-related information between the distributor and the vehicle may include whether bidirectional communication between the distributor and the vehicle is supported, whether the function of sharing measurement data through bidirectional communication between the distributor and the vehicle is supported, whether the measurement data can be used to control or manage the process of supplying hydrogen from the distributor to the vehicle, or whether a fallback or alternative protocol for the communication protocol or fuel supply protocol can be determined based on changes in the communication environment between the distributor and the vehicle during the process of supplying hydrogen from the distributor to the vehicle.

[0630] exist Figure 17 In an alternative exemplary implementation, as an item identified in a list of communication protocols supported by the dispenser or the mobile body, a series of fuel supply protocols jointly supported by the dispenser or the mobile body can be guided depending on whether bidirectional communication between the dispenser and the mobile body is supported.

[0631] exist Figure 17 In an alternative exemplary implementation, whether or not the ability to share real-time measurement data (actual measurement data on the distributor side or the mobile body side) between the distributor and the mobile body via bidirectional communication can be considered as sharing interoperability or compatibility information.

[0632] exist Figure 17 In an alternative exemplary implementation, whether the real-time measurement data can be used in the control or management process of the fuel supply protocol for the process of supplying hydrogen from the distributor to the mobile body can be shared as interoperability or compatibility information.

[0633] exist Figure 17 In an alternative exemplary implementation, the presence of conditions such as UC10 or UC11 can be shared between the mobile unit and the distributor based on real-time measurement data. In this case, whether to perform a fallback of interoperability or compatibility information can be determined based on whether bidirectional communication is supported, whether real-time measurement data can be shared, and whether real-time measurement data can be utilized. In this case, in addition to fallback, alternative communication or fuel supply protocols or secondary communication or fuel supply protocols can be selected, and the hydrogen fuel supply process can be performed based on the selected protocol, or the hydrogen fuel supply process can be terminated depending on the circumstances.

[0634] In an exemplary embodiment of this disclosure, by pre-searching for specific details of the hydrogen fuel supply agreement in the pairing and discovery step S401, subsequent agreement processes such as agreement negotiation steps S403 to S405 can be supported, and the negotiation process can be shortened a second time.

[0635] In an exemplary embodiment of this disclosure, when a situation corresponding to UC10 or UC11 occurs, the response process can be processed quickly and efficiently by using interoperability or compatibility information shared in S401, thereby increasing the success probability of the entire hydrogen fuel supply process and shortening the time required for the hydrogen fuel supply process.

[0636] Figure 18 This is a schematic block diagram illustrating the physical configuration of a general-purpose computing system according to an exemplary embodiment of the present disclosure. The general-purpose computing system can operate as a communication device, a communication controller, and / or an electronic controller for hydrogen fuel supply, and can be installed on a hydrogen fuel vehicle, a distributor, and / or a fuel supply station.

[0637] Although Figures 1 to 17 Although not shown, the processor and memory can be electrically connected to each component, allowing the operation of each component to be controlled or managed by the processor.

[0638] At least some processes of the fuel supply communication method according to exemplary embodiments of this disclosure can be performed by Figure 18 The computing system 3000 is running.

[0639] A computing system 3000 according to an exemplary embodiment of the present disclosure may include at least one processor 3100 and a memory 3200 storing program instructions that instruct the at least one processor 3100 to perform at least one processing step. At least some operations or processing steps of the method according to an exemplary embodiment of the present disclosure may be executed by at least one processor 3100 that loads program instructions from the memory 3200.

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

[0641] Each of the memory 3200 and the storage device 3400 may include one or more of volatile or non-volatile storage media. For example, the memory 3200 may include one or more of read-only memory (ROM) or random access memory (RAM).

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

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

[0644] The components of the computing system 3000 can be connected to each other via the system bus 3700 to communicate with each other.

[0645] The apparatus / device including processor 3100 according to exemplary embodiments of the present disclosure can be any data processing device capable of communicating via a network, such as a desktop computer, laptop computer, notebook PC, smartphone, tablet PC, mobile phone, smartwatch, smart glasses, e-book reader, portable multimedia player (PMP), portable game console, navigation device, digital camera, digital multimedia broadcast (DMB) player, digital audio recorder, digital audio player, digital video recorder, digital video player, and personal digital assistant (PDA).

[0646] A communication device / equipment for hydrogen fuel supply according to an exemplary embodiment of the present disclosure is installed on a hydrogen fuel vehicle and / or dispenser to perform communication between the hydrogen fuel vehicle and the dispenser, and may include a processor 3100 that receives at least one instruction from a memory 3200 and executes the at least one instruction.

[0647] A communication device or communication control device for a hydrogen fuel cell vehicle 100 according to an exemplary embodiment of the present disclosure may include a memory 3200 configured to store at least one command and a processor 3100 configured to execute at least one command. The processor 3100 may, via at least one command, discover a distributor supplying hydrogen to the vehicle, share pairing information between the vehicle and the distributor, and perform pairing between the vehicle and the distributor (S2100); negotiate a communication protocol or fuel supply protocol for the process of supplying hydrogen from the distributor to the vehicle based on interoperability or compatibility-related information between the vehicle and the distributor (S2200); and send information to the distributor required for monitoring and controlling the process of supplying hydrogen from the distributor to the vehicle based on the fuel supply protocol (S2300).

[0648] According to an exemplary embodiment of this disclosure, the processor 3100 of the communication device of a hydrogen fuel cell vehicle can establish a secure channel between the vehicle and the dispenser via at least one command to negotiate a communication protocol or a fuel supply protocol after pairing is performed (see [link to documentation]). Figure 4 and Figure 16 Step S402 in the process.

[0649] According to an exemplary embodiment of this disclosure, the processor 3100 of the communication device of the hydrogen fuel vehicle can, after the process of negotiating a communication protocol or a fuel supply protocol (S2200), perform an access check (see [link to documentation]) by at least one command before the dispenser performs hydrogen fuel supply to the vehicle, to check whether the first necessary safety condition between the vehicle and the dispenser is met. Figure 4 Step S406 and Figure 16 ); and after the process of supplying hydrogen from the dispenser to the mobile body and before the nozzle detaches from the mobile body, a check is performed to determine whether the second necessary safety condition between the mobile body and the dispenser is met (see Figure 4 and Figure 16 Step S408 in the process.

[0650] According to an exemplary embodiment of this disclosure, the processor 3100 of the communication device of a hydrogen fuel cell vehicle can detect and process non-safety-critical errors occurring during the process of executing a negotiation communication protocol or fuel supply protocol (S2200) or the process of sending information required for monitoring and control to a distributor (S2300) via at least one command (see [link to relevant documentation]). Figure 16 In steps S2010 and S410), and in detecting and handling emergencies where interoperability between the distributor and the mobile unit must be stopped during the process of executing the negotiation communication protocol or fuel supply protocol (S2200) or the process of sending information required for monitoring and control to the distributor (S2300) (see steps S2010 and S410), and during the process of detecting and handling emergencies where interoperability between the distributor and the mobile unit must be stopped (see steps S2010 and S410), and during the process of executing the negotiation communication protocol or fuel supply protocol (S2200) or the process of sending information required for monitoring and control to the distributor (S2300) (see steps S2010 and S410), Figure 16 Steps S2020 and S411 in the process.

[0651] According to an exemplary embodiment of this disclosure, the processor 3100 of the communication device of the hydrogen fuel cell can negotiate the communication protocol between the cell and the dispenser when negotiating the communication protocol or the fuel supply protocol (S2200). Figure 4 and Figure 16 In step S403), a fuel supply agreement is negotiated between the mobile unit and the distributor based on the communication protocol (see...). Figure 4 and Figure 16 Step S404 in the process), and negotiate fuel supply parameters between the mobile unit and the distributor based on the fuel supply agreement (see step S404 in the process). Figure 4 and Figure 16 Step S405 in the process.

[0652] A communication device or communication control device for a distributor supplying hydrogen to a hydrogen fuel cell according to an exemplary embodiment of the present disclosure includes: a memory 3200 configured to store at least one command; and a processor 3100 configured to execute at least one command, wherein the processor 3100 can discover a mobile body via at least one command, share pairing information between the mobile body and the distributor, and perform pairing between the mobile body and the distributor (S2100); negotiate a communication protocol or fuel supply protocol for the process of supplying hydrogen from the distributor to the mobile body based on interoperability or compatibility information between the mobile body and the distributor (S2200); and monitor and control the process of supplying hydrogen from the distributor to the mobile body based on the fuel supply protocol (S2300).

[0653] On the other hand, while most of the implementations described above focus on the method by which the mobile body first sends the communication protocol or parameters to the distributor, this disclosure is not limited thereto, and can be configured such that the distributor first sends the communication protocol or parameters of the distributor to the mobile body. Apart from the change in the sender and receiver, this implementation has essentially the same features as the implementations described above.

[0654] The apparatus and methods according to exemplary embodiments of this disclosure can be implemented by computer-readable program code or instructions stored on a computer-readable intangible recording medium. The computer-readable recording medium includes all types of recording means for storing data readable by a computer system. The computer-readable recording medium can be distributed across a computer system connected via a network, allowing the computer-readable program or code to be stored and executed in a distributed manner.

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

[0656] Some aspects of this disclosure described above in the context of apparatus can indicate a corresponding description of a method according to this disclosure, and blocks or apparatuses can correspond to operations or features of operations of the method. Similarly, some aspects described in the context of the method can be expressed by features of blocks, items, or corresponding apparatuses. Some or all operations of the method can be performed using hardware apparatus (e.g., a microprocessor, a programmable computer, or electronic circuitry). In some exemplary embodiments, one or more of the most important operations of the method can be performed by such apparatus.

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

[0658] Although this disclosure has been described with reference to preferred embodiments, those skilled in the art will understand that various modifications and changes may be made without departing from the spirit and scope of this disclosure as defined in the appended claims.< / ok> < / ok>

Claims

1. A communication method for hydrogen fuel supply (fuel supply), performed by a hydrogen fuel vehicle (hydrogen fuel vehicle), the communication method comprising: A distributor that supplies hydrogen to a mobile body is discovered, pairing information is shared between the mobile body and the distributor, and pairing between the mobile body and the distributor is performed; Based on interoperability or compatibility information between the mobile body and the distributor, a communication protocol or fuel supply protocol for the process of supplying hydrogen from the distributor to the mobile body is negotiated between the mobile body and the distributor. as well as Information required for monitoring and controlling the process of supplying hydrogen from the distributor to the mobile body based on the fuel supply agreement is sent to the distributor.

2. The communication method for hydrogen fuel supply according to claim 1, further comprising: After the pairing is performed, a secure channel is established between the mobile body and the dispenser to negotiate the communication protocol or the fuel supply protocol.

3. The communication method for hydrogen fuel supply according to claim 1, further comprising: After negotiating the communication protocol or the fuel supply protocol, and before the dispenser supplies hydrogen fuel to the mobile body, a check-in operation is performed to check whether the first necessary safety condition (necessary safety condition) between the mobile body and the dispenser is met. as well as After the hydrogen is supplied from the dispenser to the mobile body, and before the nozzle is disengaged from the mobile body, a detection operation is performed to check whether the second necessary safety condition (necessary safety condition) between the mobile body and the dispenser is met.

4. The communication method for hydrogen fuel supply according to claim 1, further comprising: Detect and handle non-safety-critical errors (non-safety-critical errors) that occur during the negotiation of the communication protocol or the fuel supply protocol, or when transmitting information required for monitoring and control to the distributor; and The system detects and handles emergencies that occur during the negotiation of the communication protocol or the fuel supply protocol, or when sending information required for monitoring and control to the dispenser, in which case interoperability between the dispenser and the mobile unit will be suspended.

5. The communication method for hydrogen fuel supply according to claim 1, wherein, The negotiation of the communication protocol or the fuel supply agreement includes: The communication protocol is negotiated between the mobile body and the distributor; Based on the communication protocol, the fuel supply agreement is negotiated between the mobile body and the dispenser; and Based on the fuel supply agreement, fuel supply parameters are negotiated between the mobile body and the dispenser.

6. The communication method for hydrogen fuel supply according to claim 1, wherein, During the negotiation of the communication protocol or the fuel supply protocol, the information of the communication protocol or the fuel supply protocol transmitted between the dispenser and the mobile body includes at least one of the following: protocol name, index, version, priority, and preference.

7. The communication method for hydrogen fuel supply according to claim 1, wherein, The pairing information shared between the mobile body and the distributor during the pairing process includes at least one of interoperability-related information and compatibility-related information between the mobile body and the distributor.

8. The communication method for hydrogen fuel supply according to claim 1, wherein, Based on the status information during the negotiation of the communication protocol or the fuel supply protocol, or when sending information required for monitoring and control to the dispenser, the interoperability or compatibility information between the mobile body and the dispenser is updated, and Specifically, based on the updated interoperability or compatibility-related information, the negotiation of the communication protocol or the fuel supply protocol, or the transmission of information required for monitoring and control to the distributor, is performed.

9. The communication method for hydrogen fuel supply according to claim 1, further comprising: If a non-safety-critical error is detected during the negotiation of the communication protocol or the fuel supply protocol, the negotiation of part or all of the communication protocol or the fuel supply protocol shall be re-executed.

10. The communication method for hydrogen fuel supply according to claim 1, wherein, In the process of sending the information required for monitoring and control to the distributor, the information sent from the mobile body to the distributor is determined based on whether the fuel supply agreement allows bidirectional communication between the mobile body and the distributor as a communication protocol.

11. A communication method for hydrogen fuel supply (fuel supply), performed by a communication device of a distributor supplying hydrogen to a hydrogen fuel vehicle, the communication method comprising: The mobile body is detected, pairing information is shared between the mobile body and the distributor, and pairing between the mobile body and the distributor is performed; Based on interoperability or compatibility information between the mobile body and the distributor, a communication protocol or fuel supply protocol for the process of supplying hydrogen from the distributor to the mobile body is negotiated between the mobile body and the distributor. as well as The process of supplying hydrogen from the distributor to the mobile body, performed based on the fuel supply agreement, is monitored and controlled.

12. The communication method for hydrogen fuel supply according to claim 11, further comprising: After the pairing is performed, a secure channel is established between the mobile body and the dispenser to negotiate the communication protocol or the fuel supply protocol.

13. The communication method for hydrogen fuel supply according to claim 11, further comprising: After negotiating the communication protocol or the fuel supply protocol, and before the dispenser supplies hydrogen fuel to the mobile body, a check-in operation is performed to check whether the first necessary safety condition (necessary safety condition) between the mobile body and the dispenser is met. as well as After the process of supplying hydrogen from the dispenser to the mobile body and before the nozzle is disengaged from the mobile body, a detection operation is performed to check whether the second necessary safety condition (necessary safety condition) between the mobile body and the dispenser is met.

14. The communication method for hydrogen fuel supply according to claim 11, further comprising: Detect and handle non-safety-critical errors (non-safety-critical errors) that occur during the negotiation of the communication protocol or the fuel supply protocol, or during the monitoring and control of the hydrogen supply from the dispenser to the mobile body; and The system detects and handles emergencies that occur during the negotiation of the communication protocol or the fuel supply protocol, or during the monitoring and control of the hydrogen fuel supply from the dispenser to the mobile body, in which case the interoperability between the dispenser and the mobile body will be suspended.

15. The communication method for hydrogen fuel supply according to claim 11, wherein, The negotiation of the communication protocol or fuel supply agreement includes: The communication protocol is negotiated between the mobile body and the distributor; Based on the communication protocol, the fuel supply agreement is negotiated between the mobile body and the dispenser; and Based on the fuel supply agreement, fuel supply parameters are negotiated between the mobile body and the dispenser.

16. A communication device for supplying hydrogen fuel, disposed in a hydrogen fuel mobile body, the communication device comprising: The memory is configured to store at least one command; as well as The processor is configured to execute the at least one of the commands. The processor, through the at least one command, A distributor supplying hydrogen to the mobile body is discovered; pairing information is shared between the mobile body and the distributor; and pairing between the mobile body and the distributor is performed. Based on interoperability or compatibility information between the mobile vehicle and the distributor, a communication protocol or fuel supply protocol for the process of supplying hydrogen from the distributor to the mobile vehicle is negotiated between the mobile vehicle and the distributor. Information required for monitoring and controlling the process of supplying hydrogen from the distributor to the mobile body, based on the fuel supply agreement, is sent to the distributor.

17. The communication device according to claim 16, wherein, After the pairing is performed, the processor establishes a secure channel between the mobile body and the dispenser via at least one command to negotiate the communication protocol or the fuel supply protocol.

18. The communication device according to claim 16, wherein, The processor, through the at least one command, performs an entry operation to check whether a first necessary safety condition (necessary safety condition) between the mobile body and the distributor is met after the process of negotiating the communication protocol or the fuel supply protocol and before the distributor performs the process of supplying hydrogen to the mobile body, and performs an exit operation to check whether a second necessary safety condition (necessary safety condition) between the mobile body and the distributor is met after the process of supplying hydrogen from the distributor to the mobile body and before the nozzle disengages from the mobile body.

19. The communication device according to claim 16, wherein, The processor, through the at least one command, detects and handles non-safety-critical errors that occur during the process of negotiating the communication protocol or the fuel supply protocol, or during the process of sending information required for monitoring and control to the dispenser, and detects and handles emergencies that occur during the process of negotiating the communication protocol or the fuel supply protocol, or during the process of sending information required for monitoring and control to the dispenser, in which interoperability between the dispenser and the mobile body will be stopped.

20. The communication device according to claim 16, wherein, When negotiating the communication protocol or the fuel supply protocol, the processor negotiates the communication protocol between the mobile body and the distributor, negotiates the fuel supply protocol between the mobile body and the distributor based on the communication protocol, and negotiates fuel supply parameters between the mobile body and the distributor based on the fuel supply protocol.

Images