Communication method and mobility

Abstract

Disclosed are a communication method for a mobility, a communication method for a dispenser, and a mobility capable of simultaneously and stably performing a sensor report and a control command in a fuel supply process. The communication method for a mobility comprises the steps of: identifying a communication pattern supportable with a dispenser; transmitting a first message to the dispenser if the supportable communication pattern supports an asynchronous communication pattern; and transmitting a second message to the dispenser regardless of whether a response to the first message is received, wherein the first message and the second message are messages of the same type.

Description

Communication methods and mobility

[0001] The present disclosure relates to a communication method and mobility, and more specifically, to a communication method of mobility, a communication method of a dispenser, and mobility.

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

[0003] Hydrogen cars, or hydrogen electric vehicles, refer to zero-emission automobiles that move using electrical energy generated by the interaction of high-pressure hydrogen stored in the vehicle with ambient air. Hydrogen electric vehicles are also known as Fuel Cell Electric Vehicles (FCEVs). Most hydrogen electric vehicles operate by generating electricity using a fuel cell system that utilizes hydrogen as an energy source. Hydrogen electric vehicles are attracting attention as a future eco-friendly mobility solution because they not only emit only pure water (H2O) during the electricity generation process but also possess the capability to remove ultrafine dust from the atmosphere while in operation. Given that hydrogen is an infinite source on Earth and the energy production process is environmentally friendly, this technology is widely recognized for its potential for application across various industries.

[0004] Hydrogen-fueled mobility refers to a type of mobility that uses hydrogen as an energy source or hydrogen as fuel to generate electrical energy and uses this to drive an electric motor. In addition to the hydrogen electric vehicles described above, hydrogen-fueled mobility includes aerial mobility as well as industrial trucks, trains, ships, and aircraft, and may include devices that generate electrical energy using hydrogen as fuel and use this to drive.

[0005] Most hydrogen fuel cell vehicles deliver high-pressure hydrogen, safely stored in a hydrogen fuel storage tank, and oxygen supplied through an air supply system to a fuel cell stack, generating electrical energy through an electrochemical reaction between the hydrogen and oxygen. This generated electrical energy is converted into kinetic energy via a drive motor to power the vehicle, and the vehicle has the advantage of emitting only pure water through its exhaust port while in motion.

[0006] Meanwhile, the concept of a hydrogen fueled car, as opposed to a hydrogen electric vehicle, also refers to a vehicle that uses hydrogen as fuel; a hydrogen fueled car operates by driving an electric motor using heat generated from the direct combustion of hydrogen in an internal combustion engine (ICE). The method of supplying hydrogen for hydrogen fueled cars is not significantly different from that used for hydrogen electric vehicles.

[0007] In a control technique for supplying hydrogen to a vehicle that uses hydrogen as fuel, the goal is to ultimately control the temperature and pressure of the Compressed Hydrogen Storage System (CHSS) on the fuel cell side to operate under limit temperature and limit pressure conditions for the safety of hydrogen fuel supply. To this end, communication is established between the hydrogen fuel mobility and the dispenser supplying hydrogen.

[0008] The technical problem of the present disclosure is to provide a communication method for mobility, a communication method for a dispenser, and mobility in which sensor reporting and control commands can be reliably performed simultaneously during the fuel supply process.

[0009] A communication method according to embodiments of the present disclosure for solving such problems, as a communication method for mobility, comprises the steps of: identifying a dispenser and a supported communication pattern; transmitting a first message to the dispenser based on whether an asynchronous communication pattern is supported; and transmitting a second message to the dispenser regardless of whether a response to the first message is received, wherein the first message and the second message are messages of the same type.

[0010] This communication method further includes the step of transmitting a third message to the dispenser; and the step of receiving a fourth message from the dispenser in response to the third message; and the transmission of the third message and the reception of the fourth message may be carried out in a handshake manner.

[0011] The transmission of the first to third messages and the reception of the fourth message may be carried out in a monitoring and control procedure.

[0012] The first message and the second message may be a FuelingDataNotif message, the third message may be a FuelingLoopReq message, and the fourth message may be a FuelingLoopRes message.

[0013] The step of verifying the above-mentioned supportable communication patterns can be performed during the Communication Setup step.

[0014] The transmission of the first to third messages and the reception of the fourth message can proceed without interfering with each other.

[0015] The transmission time interval between the first message and the second message can be determined by the packet loss rate and the probability that a packet does not arrive during the maximum allowed packet arrival interval.

[0016] A communication method according to embodiments of the present disclosure is a communication method of a dispenser, comprising: a step of identifying a communication pattern that is supported by a mobility; a step of receiving a first message from the mobility based on whether an asynchronous communication pattern is supported; and a step of receiving a second message from the mobility regardless of whether the dispenser transmits a response to the first message, wherein the first message and the second message may be messages of the same type.

[0017] This communication method comprises the step of receiving a third message from the mobility; and

[0018] The method further includes the step of transmitting a fourth message to the mobility in response to the third message, and the reception of the third message and the transmission of the fourth message may be performed in a handshake manner.

[0019] The reception of the first to third messages and the transmission of the fourth message may be carried out in a monitoring and control procedure.

[0020] The first message and the second message may be a FuelingDataNotif message, the third message may be a FuelingLoopReq message, and the fourth message may be a FuelingLoopRes message.

[0021] The step of verifying the above-mentioned supportable communication patterns can be performed during the Communication Setup step.

[0022] The reception of the first to third messages and the transmission of the fourth message can proceed without interfering with each other.

[0023] The reception time interval between the first message and the second message can be determined by the packet loss rate and the probability that a packet does not arrive during the maximum allowed packet arrival interval.

[0024] A mobility according to exemplary embodiments of the present disclosure comprises a processor and a communication device, as a mobility that performs communication with a dispenser. The processor identifies a communication pattern that is supported with the dispenser and, based on whether an asynchronous communication pattern is supported, controls the communication device to transmit a first message to the dispenser, and controls the communication device to transmit a second message to the dispenser regardless of whether a response to the first message is received. In this case, the first message and the second message are messages of the same type.

[0025] The processor controls the communication device so that the communication device transmits a third message to the dispenser, and the communication device receives a fourth message from the dispenser in response to the third message, wherein the transmission of the third message and the reception of the fourth message may be carried out in a handshake manner.

[0026] The transmission of the first to third messages and the reception of the fourth message can be carried out in a monitoring and control procedure without interfering with each other.

[0027] The first message and the second message may be a FuelingDataNotif message, the third message may be a FuelingLoopReq message, and the fourth message may be a FuelingLoopRes message.

[0028] Verification of the above-mentioned supported communication patterns can be performed during the Communication Setup stage.

[0029] The transmission time interval between the first message and the second message can be determined by the packet loss rate and the probability that a packet does not arrive during the maximum allowed packet arrival interval.

[0030] According to the present disclosure, by applying an asynchronous (Fire-and-Forget) communication pattern to sensor data reporting, mobility can periodically transmit data without waiting for a response, and the receiving side can maintain normal operation as long as data arrives within a certain period, even if some packets are lost. This overcomes the limitations of the existing synchronous (Request / Response) method and ensures real-time performance and reporting reliability.

[0031] Furthermore, by simultaneously executing Fire-and-Forget and Request / Response methods through a multiplexing structure, monitoring and control functions can be performed in parallel without mutual interference. Consequently, sensor reporting and control commands can be reliably executed simultaneously during the fuel supply process, significantly enhancing the safety and reliability of the entire system.

[0032] FIG. 1 is a conceptual diagram illustrating the operation of systems / devices within a hydrogen fuel supply environment in which a hydrogen fuel supply process to which bidirectional communication technology is applied is performed, according to embodiments of the present invention.

[0033] FIG. 2 is a conceptual diagram illustrating a system / device participating in a hydrogen fuel supply communication method according to embodiments of the present invention and sub-components within the system / device.

[0034] FIG. 3 is a conceptual diagram illustrating functional blocks corresponding to procedures in a hydrogen fuel supply communication method according to embodiments of the present invention.

[0035] FIG. 4 is an operation flowchart conceptually illustrating the operation between functional blocks corresponding to procedures in a hydrogen fuel supply communication method according to embodiments of the present invention.

[0036] FIG. 5 is an operation flowchart conceptually illustrating a secure communication method for hydrogen fuel supply according to embodiments of the present invention.

[0037] FIG. 6 is an operation flowchart conceptually illustrating the operation between functional blocks corresponding to procedures in a hydrogen fuel supply communication method according to embodiments of the present invention.

[0038] FIG. 7 is an operation flowchart conceptually illustrating a secure communication method for hydrogen fuel supply according to embodiments of the present invention.

[0039] FIG. 8 is an operation flowchart conceptually illustrating the operation between functional blocks corresponding to procedures in a hydrogen fuel supply communication method according to embodiments of the present invention.

[0040] FIG. 9 is a conceptual diagram illustrating a multiplexing structure in which a Fire-and-Forget method and a Request / Response method can be performed simultaneously in a communication process between a hydrogen fuel mobility and a dispenser according to embodiments of the present invention.

[0041] FIG. 10 is a conceptual diagram illustrating the message exchange process in a UC7 procedure with a multiplexing structure applied according to one embodiment of the present invention.

[0042] FIG. 11 is a conceptual diagram illustrating the relationship between the transmission period (INTtx), reception interval (INTrx), packet loss rate (r), and acceptance probability (P_tol) in a Fire-and-Forget message transmission method according to one embodiment of the present invention.

[0043] FIG. 12 is a flowchart illustrating a message processing procedure from a mobility perspective according to embodiments of the present invention.

[0044] FIG. 13 is a flowchart illustrating a message processing procedure from the perspective of a dispenser according to embodiments of the present invention.

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

[0046] In addition to the above objectives, other objectives and features of the present invention will become apparent through the description of embodiments with reference to the accompanying drawings.

[0047] The present invention is capable of various modifications and may have various embodiments, and specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the invention to specific embodiments, and it should be understood that the invention includes all modifications, equivalents, and substitutions that fall within the spirit and scope of the invention.

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

[0049] In the embodiments of the present application, "at least one of A and B" may mean "at least one of A or B" or "at least one of one or more combinations of A and B". Additionally, in the embodiments of the present application, "at least one of A and B" may mean "at least one of A or B" or "at least one of one or more combinations of A and B".

[0050] When it is stated that one component is "connected" or "connected" to another component, it should be understood that while it may be directly connected or connected to that other component, there may also be other components in between. On the other hand, when it is stated that one component is "directly connected" or "directly connected" to another component, it should be understood that there are no other components in between.

[0051] The terms used in this application are used merely to describe specific embodiments and are not intended to limit the invention. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this application, terms such as "comprising" or "having" are intended to specify the presence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

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

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

[0054] Hydrogen fueled mobility can refer to all types of mobility, including ICE (internal combustion engine) based mobility that obtains the power required for movement using hydrogen as an energy source, mobility that generates electrical energy using hydrogen as fuel and drives an electric motor using this, and / or hybrid vehicles / mobility equipped with an ICE and an electric motor using hydrogen as an energy source.

[0055] In addition to hydrogen electric vehicles, hydrogen fuel mobility may include aerial mobility, as well as industrial trucks, trains, ships, and aircraft, which use hydrogen as fuel to generate electrical energy and drive them.

[0056] Hydrogen electric vehicles generally refer to fuel cell electric vehicles (FCEVs) that utilize fuel cells, but they can include all mobility vehicles that drive electric motors using hydrogen as an energy source through methods other than fuel cells.

[0057] Even if, for instance, a hydrogen fuel cell vehicle is disclosed as the primary embodiment in the following embodiments, other embodiments of the present invention may be implemented to include ICE-based hydrogen fueled mobility that utilizes hydrogen as fuel, within the scope consistent with the purpose of the invention. Even if a hydrogen fueling protocol and / or a communication protocol for hydrogen fueling is disclosed with a hydrogen fuel cell vehicle as the primary embodiment in the following embodiments, it is obvious to those skilled in the art that, according to other embodiments of the present invention, the hydrogen fueling protocol and / or the communication protocol for hydrogen fueling disclosed in the following embodiments may also be applied to ICE-based hydrogen fueled mobility. In this disclosure, the term "mobility" may also be used interchangeably.

[0058] Hydrogen fuel supply refers to the process of receiving high-pressure hydrogen from a dispenser at a hydrogen station and compressing and storing it in a hydrogen storage tank of a vehicle / mobility. In the sense of supplying hydrogen to hydrogen fuel mobility, hydrogen fuel supply can be briefly used interchangeably with the term "fueling." That is, in this specification, "fueling" may be used to mean fuel supply or hydrogen fuel supply, and "fuel supply" may mean the supply of hydrogen fuel. For example, "fuel supply protocol" may be referred to as "hydrogen fuel supply protocol," "fuel supply session" may be referred to as "hydrogen fuel supply session," and "fuel supply method" may be referred to as "hydrogen fuel supply method."

[0059] Hydrogen fluid fuels may include gaseous hydrogen fuel or liquid hydrogen fuel.

[0060] Hydrogen fuel may include at least one of hydrogen in a gaseous state and hydrogen in a liquid state, and may basically mean compressed hydrogen, but is not limited thereto.

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

[0062] A Pressure Relief Device (PRD) is deployed in the CHSS and refers to a device capable of isolating stored hydrogen from the mobility's hydrogen fuel supply system and the surrounding environment, and discharging the hydrogen to the outside.

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

[0064] The Average Pressure Ramp Rate (APRR) refers to the average value of the pressure increase rate from the beginning to the end of hydrogen fueling.

[0065] Pre-cooling basically refers to the process of cooling the hydrogen at a hydrogen refueling station in advance before supplying fuel.

[0066] The dispenser is a component that delivers pre-cooled hydrogen to the CHSS. The dispenser is placed at a hydrogen refueling station and can perform hydrogen fuel supply operations between the hydrogen storage tank of the hydrogen refueling station and the CHSS of the mobility.

[0067] A nozzle refers to a device that connects to a dispenser, connects to the receptacle of a hydrogen electric vehicle, and allows for the delivery of hydrogen fuel.

[0068] A fueling session can be used to mean communication sessions that take place throughout the entire use case for hydrogen fueling.

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

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

[0071] Command and control communication may refer to communication between an electric vehicle hydrogen fuel supply unit and a hydrogen electric vehicle that exchanges information necessary for the start, control, and termination of the hydrogen fuel supply process.

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

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

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

[0075] Meanwhile, even if technology was known prior to the filing date of the present invention, it may be included as part of the composition of the present invention if necessary, and such details are described in this specification to the extent that they do not obscure the spirit of the present invention. However, in describing the composition of the present invention, detailed descriptions of matters that are known prior to the filing date and are obvious to those skilled in the art may obscure the spirit of the present invention; therefore, overly detailed descriptions of known technology are omitted. Furthermore, the purpose of the present invention is not to claim rights regarding these known technologies, and the content of the known technologies may be included as part of the present invention to the extent that it does not deviate from the spirit of the present invention.

[0076] For example, for unidirectional communication, IrDA technology may be used; for bidirectional communication, short-range wireless communication technology (Bluetooth, WLAN, UWB) may be used; or wired communication technology for unidirectional / bidirectional communication may be used, etc., which are known technologies prior to the filing of the present invention, and at least some of these known technologies may be applied as elemental technologies necessary for implementing the present invention.

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

[0078] FIG. 1 is a conceptual diagram illustrating the operation of systems / devices within a hydrogen fuel supply environment in which a hydrogen fuel supply process to which bidirectional communication technology is applied is performed, according to embodiments of the present invention.

[0079] Referring to FIG. 1, pre-cooled hydrogen gas from a hydrogen refueling station (Station, 300) is supplied to a hydrogen fueled mobility (100) via a dispenser (200). At this time, the hydrogen fuel supply process can be described and controlled by parameters including a pressure ramp rate (PRR) or an average pressure ramp rate (APRR). The pressure ramp rate may refer to a concept applied to a relatively short time interval, while the average pressure ramp rate may refer to a concept applied to a time interval longer than the pressure ramp rate.

[0080] The mobility (100) may include hydrogen storage (102). The hydrogen storage (102) may be implemented by connecting one or more compressed hydrogen storage systems (CHSS) or commonly referred to as "tank" in parallel.

[0081] A pressure relief device (PRD, 104) is a device capable of discharging hydrogen fuel stored in a CHSS to the outside. Generally, hydrogen injection and discharge into the CHSS do not proceed simultaneously, and sensors capable of measuring state information such as the pressure and temperature of the hydrogen inside the CHSS may be attached.

[0082] The pressure of hydrogen stored on the mobility (100) side is also referred to as the State of Charge (SoC), which is analogous to the charging process of a battery.

[0083] A dispenser (200) is positioned as an interface between a hydrogen charging station (300) and a hydrogen fuel mobility (100), and the dispenser (200) can control the target pressure of hydrogen stored in the mobility (100) and the injection speed of hydrogen fuel supplied to the mobility (100) based on measurement data such as the temperature and pressure of hydrogen on the mobility (100) side and fuel supply information of the charging station (300). An example of a control logic currently in use is a control logic that follows the SAE J2601 (2020-05) standard.

[0084] For example, the target pressure of hydrogen is the goal of fuel supply, and the range of PRR or APRR can be determined based on the target time and target pressure. In this case, to ensure safety and reliability, the range of PRR or APRR may be adjusted or determined based on constraints such as the temperature rise caused by the increase in pressure during the fuel supply process and the temperature limit when the temperature rises.

[0085] The control logic that controls the hydrogen fuel supply process of the dispenser (200) may be referred to as a hydrogen fuel supply protocol (210). The hydrogen fuel supply protocol (210) illustrated in FIG. 1 may refer to a plurality of control logics possessed by the dispenser (200), and among these, one of the control logics is determined based on, for example, the SAE J2601 (2020-05) standard, or target information and environmental information, and the determined control logic may be executed by the elements of the hydrogen fuel supply protocol (210).

[0086] Regarding minimum safety requirements, simulations can be performed through thermodynamic modeling for various situations. Based on parameters derived from the simulation, a table-based single injection method and / or an MC-formula-based partial real-time correction method may be utilized.

[0087] Minimum safety requirements may include upper limits for the temperature and pressure conditions of hydrogen within the CHSS and guidelines for the State of Charge (SoC). Simulations may be performed through thermodynamic modeling using boundary conditions covering Best to Worst Cases.

[0088] The hydrogen refueling station (300) may include a hydrogen storage (302) and a pre-cooler (304). The hydrogen storage (302) on the side of the refueling station (300) may generally be a tank that stores high-pressure hydrogen. The pre-cooler (304) can supply hydrogen to the mobility (100) via the dispenser (200) with the temperature of the hydrogen gas lowered through pre-cooling.

[0089] Since the pressure and temperature of hydrogen may increase simultaneously during the hydrogen fuel supply process, pre-cooling may be performed for the safety and efficiency of the fuel supply. However, excessive pre-cooling may be a factor in causing excessive energy costs and operating costs. A method may be provided in which hydrogen status information (temperature, pressure, etc.) from the charging station (300) is transmitted to the dispenser (200) and considered together in the control logic of the hydrogen fuel supply protocol (210), thereby allowing the charging station (300) to control or optimize pre-cooling.

[0090] FIG. 2 is a conceptual diagram illustrating a system / device participating in a hydrogen fuel supply communication method according to one embodiment of the present invention and sub-components within the system / device.

[0091] Referring to FIG. 2, the dispenser (200) may include a controller (202) and a sensor (206). The controller (202) may generally be implemented as a Programmable Logic Controller (PLC) or by a device including electrical / electronic logic.

[0092] The controller (202) may include the aforementioned hydrogen fuel supply protocol (210) elements and communication device (204).

[0093] The sensor (206) on the dispenser (200) side can measure and detect the state information of the hydrogen supplied as fuel from the dispenser (200).

[0094] The mobility (100) may include an electronic control unit (ECU, 110) of a fuel supply system. The electronic control unit (110) may be connected to a hydrogen storage (102) on the mobility (100) side. The electronic control unit (110) may communicate with a communication device (114) and / or a sensor (116) on the mobility (100) side via an in-vehicle network.

[0095] The communication device (204) and the communication device (114) may be equipped with and operate communication software. A portion of the communication software may be implemented by being installed in the controller (202) of the dispenser (200) or in the network system and electronic control unit (110) of the mobility (100).

[0096] While the primary purpose of the communication software is network traffic management, it may also include a function to provide mobility data related to the hydrogen fuel supply process.

[0097] The sensor (116) may include not only sensors for temperature, pressure, etc., but also a pulse counter capable of measuring hydrogen pressure pulses (pulse counter of FIG. 10, 12, 13). In addition to this, various other sensors may be included. Data obtained from the sensor (116), etc., can be converted into a form suitable for transmission to the dispenser (200). Data obtained from the sensor (116), etc., can be transmitted to the dispenser (200) and used to control the hydrogen fuel supply process by the hydrogen fuel supply protocol (210) as shown in FIG. 1, and can also be used as a safety standard, such as an emergency stop in emergency situations such as exceeding a limit temperature.

[0098] For active and efficient control, real-time measurement data obtained from the sensor (116) can be transmitted to the dispenser (200).

[0099] In this case, real-time measurement and / or real-time communication data can be classified into static data and dynamic data. Static data may include the capacity, configuration, or type of equipment of a storage tank that does not change over time, while dynamic data may refer to data such as temperature or pressure that may change during the fuel supply process.

[0100] Static data may include, for example, the volume of the tank of the mobility (100) or charging station (300), pressure rating, maximum allowable pressure, type of tank, number of tanks, size of tank, serial number of tank, manufacturer of tank, usage data of tank, permissible temperature range of hydrogen fluid in tank, etc.

[0101] Dynamic data may include, for example, fuel supply commands (e.g., start, stop, pause, abandon, increase flow rate, decrease flow rate, tank change commands, etc.), control parameters for fuel supply (e.g., Average Pressure Ramp Rate (APRR), Pressure Ramp Rate, etc.), real-time measurements of pressure and / or temperature within the tank, including fluctuations in temperature and / or pressure within the tank (which may indicate leakage and / or imminent failure), the State of Charge (SOC) of the tank at the filling station or mobility side, the ambient temperature outside the tank, and / or real-time measurements of the flow rate of hydrogen fluid entering the tank.

[0102] The communication process performed between the communication device (204) and the communication device (114) using communication software, etc., may include an embodiment for exchanging information about the following situations.

[0103] (1) No communication situation: When the mobility (100) or charging station (300) is not equipped with a communication function, or the communication function is broken, or communication is impossible because the communication function is broken during fuel supply.

[0104] (2) Communication error: Although communication with the mobility (100) or charging station (300) is possible, if parts, sensors, or equipment operate abnormally and some of the data is missing or an error occurs

[0105] (3) Uncertified equipment, parts, or mobility: When communication with mobility (100) or charging station (300) is possible and data is collected normally, but the reliability of the transmitted data is low and verification is required or limited use is required.

[0106] (4) Communication protocol not certified: In cases where communication with mobility (100) or charging station (300) is possible but the communication method is not specified in the standard or is not certified in the relevant country, and thus safety, reliability, and stability are not ensured

[0107] In one embodiment of the present invention, an artificial neural network model is placed in a dispenser (200), and the hydrogen fuel supply process may be controlled based on static data and / or dynamic data using the artificial neural network model to improve the performance and efficiency of the hydrogen fuel supply process. The artificial neural network model may cooperate with the hydrogen fuel supply protocol (210) or assist in the control operation of the hydrogen fuel supply protocol (210).

[0108] FIG. 3 is a conceptual diagram illustrating functional blocks corresponding to procedures in a hydrogen fuel supply communication method according to embodiments of the present invention.

[0109] Referring to FIG. 3, the communication procedure for the hydrogen fuel supply process may include four procedure groups.

[0110] "UC" shown in Fig. 3 can be understood as an abbreviation for Use Case.

[0111] The connecting group (S400) may be a procedure group that includes communication connection operations between the mobility and the dispenser.

[0112] The connecting group (S400) may include a UC1-discovery and pairing procedure (S410), a UC2-communication security procedure (S420), and a UC3-communication protocol negotiation procedure (S430).

[0113] The initializing group (S500) may be a procedure group that includes operations for initialization and preparation processes before fueling hydrogen to the mobility from the dispenser.

[0114] The initialization group (S500) may include a UC4-fuel supply protocol negotiation procedure (S540) and a UC5-fuel supply parameter negotiation procedure (S550).

[0115] The fueling group (S600) may be a procedure group that includes operations highly relevant to the process of fueling hydrogen to the mobility from a dispenser.

[0116] The fueling group (S600) may include UC6-safety check-in procedure (S660), UC7-monitoring and control procedure (S670), and UC8-safety check-out procedure (S680).

[0117] The closing group (S700) may be a procedure group that includes operations related to the cessation of hydrogen fuel supply or the termination of communication between the mobility and the dispenser.

[0118] The closing group (S700) may include a UC9-termination procedure (S710), a UC10-error handling procedure (S720), and a UC11-emergency handling procedure (S730).

[0119] In the UC1-Discovery and Pairing Procedure (S410), a discovery and pairing operation may be included to enable the mobility and the dispenser to discover and identify each other. The mobility and the dispenser may exchange pairing messages containing information about each other, and the information exchanged between them included in the pairing messages may be utilized to recognize the interoperability and / or compatibility between the mobility and the dispenser. The information exchanged between them may be used in the UC3-Communication Protocol Negotiation Procedure (S430), the UC4-Fuel Supply Protocol Negotiation Procedure (S540), and / or the UC5-Fuel Supply Parameter Negotiation Procedure (S550), etc.

[0120] In the UC2-communication security procedure (S420), a communication channel with enhanced security features between the mobility and the dispenser can be established. In one embodiment of the present invention, subsequent communication procedures can be performed via the secure communication channel.

[0121] In the UC3-communication protocol negotiation procedure (S430), the communication protocol to be used for communication can be determined through negotiation between the mobility and the dispenser.

[0122] In the UC4-fuel supply protocol negotiation procedure (S540), a fuel supply protocol for the hydrogen fuel supply process can be determined through negotiation between the mobility and the dispenser.

[0123] In the UC5-fuel supply parameter negotiation procedure (S550), detailed parameters under the fuel supply protocol can be exchanged and determined through negotiation between the mobility and the dispenser.

[0124] In the negotiation process of the UC3-communication protocol negotiation procedure (S430), the UC4-fuel supply protocol negotiation procedure (S540), and / or the UC5-fuel supply parameter negotiation procedure (S550), the mobility and / or dispenser exchange negotiation request and / or response messages including a list of available or supportable protocols, and any one of the protocols in the list may be determined based on interoperability and / or compatibility.

[0125] At this time, the mobility and / or dispenser may transmit a list of protocols including preferences or priorities, and preferences or priorities may be considered when determining the protocol.

[0126] Preferences or priorities can be determined based on the safety, efficiency, and performance of the fuel supply process, user / mobility needs, the surrounding environment, constraints of the fuel supply process, etc.

[0127] In the UC6-Safety Check-in Procedure (S660), the contents of a predetermined checklist for safety may be checked before the hydrogen fuel supply process begins, including checking the coupling between the nozzle and receptacle between the dispenser and the mobility. At this time, information provided by sensors on the dispenser and / or mobility side may be used for the safety check-in.

[0128] In the UC7-monitoring and control procedure (S670), information for monitoring may be exchanged between the mobility and the dispenser while the hydrogen fuel supply process is in progress. The information exchanged may include information regarding whether the hydrogen fuel supply process is proceeding smoothly or as planned, and information that must be checked for safety between the mobility and the dispenser.

[0129] Recognition and determination of the state in which the hydrogen fuel supply is finished when the target charge rate (SoC) is achieved as a result of the hydrogen fuel supply process can also be performed in the UC7-monitoring and control procedure (S670).

[0130] In the UC8-Safety Check-out Procedure (S680), the contents of a predetermined checklist for safety can be checked before the physical separation process between the mobility and the dispenser after the hydrogen fuel supply process has been terminated.

[0131] The UC9-termination procedure (S710) may perform an operation for the termination of the hydrogen fuel supply process and / or communication channel when the target SoC is achieved by hydrogen fuel supply or when the hydrogen fuel supply process needs to be terminated for other reasons.

[0132] In the UC10-Error Handling Procedure (S720), non-critical errors may be handled. Based on the type and state of the error, it may be determined whether the hydrogen fuel supply process will be stopped and transitioned to the UC9-Termination Procedure (S710), or whether the hydrogen fuel supply process will be resumed after performing other logic.

[0133] In the UC11-Emergency Handling Procedure (S730), a critical error or emergency situation may be handled. In this case, the hydrogen fuel supply process may be stopped and transition to the UC9-Termination Procedure (S710).

[0134] In one embodiment of the present invention, interoperability and / or compatibility between mobility and dispenser may be determined based on detailed information included in pairing-related information exchanged in the UC1-Discovery and Pairing Procedure (S410).

[0135] In an alternative embodiment of the present invention, information for determining or updating interoperability and / or compatibility between mobility and dispenser may be additionally exchanged or supplemented in the UC3-communication protocol negotiation procedure (S430), UC4-fuel supply protocol negotiation procedure (S540), UC5-fuel supply parameter negotiation procedure (S550), and / or UC6-safety check-in procedure (S660), etc.

[0136] For example, if renegotiation or re-determination is required due to changes in the communication environment, changes / errors in the performance and function of the communication channel, changes in the surrounding environment, changes in parameters affecting the fuel supply process, etc., pairing may be performed again or protocols / parameters may be renegotiated or determined in the UC3-communication protocol negotiation procedure (S430), UC4-fuel supply protocol negotiation procedure (S540), UC5-fuel supply parameter negotiation procedure (S550), and / or UC6-safety check-in procedure (S660).

[0137] At this time, some procedures of the UC10-Error Handling Procedure (S720) may be used in the renegotiation / redecision process.

[0138] For example, communication protocols and fuel supply protocols are determined based on communication compatibility between mobility and dispenser, but if a state in which the performance or reliability of the communication channel is temporarily degraded is detected during the safety check-in step immediately before the hydrogen fuel supply process or during the hydrogen fuel supply process, the communication protocol and fuel supply protocol with backward compatibility within the previously exchanged list may fall back to, or alternative communication / fuel supply protocols may be negotiated / determined.

[0139] In one alternative embodiment of the present invention, when the previously selected best / most preferred protocol combination becomes incompatible or unusable in the combination of interoperable available protocols between mobility and dispenser, when determining an alternative next-best / next-best protocol combination, a combination in which the fuel supply protocol is changed while maintaining the same communication protocol as the existing best / most preferred protocol combination may be searched, or a combination in which the communication protocol is changed while maintaining the fuel supply protocol may be searched.

[0140] In one alternative embodiment of the present invention, when generating first interoperability information by searching for available protocol combinations in the UC1-Discovery and Pairing Procedure (S410), a priority can be determined in advance to prioritize cases where the communication protocol and the fuel supply protocol each match. For example, if a combination of communication protocol A1 and fuel supply protocol B1 is determined as the highest priority / best preference combination, combinations of fuel supply protocols B2, B3, ..., which can coexist with communication protocol A1 while maintaining communication protocol A1, can be designated in advance with high priority as alternative combinations for the highest priority / best preference combination. Alternatively, combinations of communication protocols A2, A3, ..., which can coexist with fuel supply protocol B1 while maintaining fuel supply protocol B1, can be designated in advance with high priority as alternative combinations for the highest priority / best preference combination.

[0141] As an alternative embodiment, for example, in the UC7-monitoring and control procedure (S670), if a change in the communication environment and a change in the fuel supply infrastructure are detected as a non-safety-critical error and the fuel supply is interrupted before the fuel supply is completed, the mobility and dispenser may re-perform some or all of the UC3-communication protocol negotiation procedure (S430), the UC4-fuel supply protocol negotiation procedure (S540), and / or the UC5-fuel supply parameter negotiation procedure (S550).

[0142] Changes in the communication environment may include cases where the communication channel is disconnected.

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

[0144] Changes in the communication environment may include cases where the quality of communication performance does not meet the required level.

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

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

[0147] In one embodiment of the present invention, when the communication protocol or fuel supply protocol combination A falls back to combination B due to a temporary failure, the communication protocol or fuel supply protocol combination A can be restored.

[0148] In one embodiment of the present invention, the preference or priority of mobility or dispenser may be added to the list of fuel supply protocols. Available communication protocols may be added to the list of fuel supply protocols. Or, supported fuel supply protocols may be added to the list of communication protocols.

[0149] In the negotiation process of the communication protocol, the communication protocol may be determined based on the preference or priority of the fuel supply protocol, information on communication protocols supporting the fuel supply protocol, etc.

[0150] In an alternative embodiment of the present invention, some of the items to be checked in the UC6-Safety Check-in Procedure (S660) may be checked in the UC5-Fuel Supply Parameter Negotiation Procedure (S550).

[0151] Referring to FIG. 4, the linkage or combination between function blocks corresponding to each procedure shown in FIG. 3 is illustrated.

[0152] Table 1 discloses the purpose, preconditions, and subsequent conditions of the UC1-Discovery and Pairing Procedure (S410).

[0153]

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

[0155]

[0156] 표 2는 UC1-디스커버리 및 페어링 프로시져(S410)에서 이용될 수 있는, 지원되는 통신 기술(supported communication technologies) 및 각각의 clauses를 개시한다.

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

[0158] In the UC1-Discovery and Pairing Procedure (S410), the mobility and the dispenser may exchange pairing IDs with each other and check or identify the other party's pairing ID. The side initiating the pairing procedure among the mobility and the dispenser may broadcast a pairing request message containing its first pairing ID. The other party may transmit an ACK for the pairing ID and its own second pairing ID as a pairing response message. A list of supported fuel supply protocols and a list of communication protocols may be transmitted separately from, or together with, the pairing ID.

[0159] A session-specific randomized pairing ID can be used as the pairing ID included in the initial broadcast message. This approach resolves privacy concerns regarding the exchange of pairing IDs. In other words, trust in the pairing process is established by subsequent processes, and to this end, the session-specific pairing ID can be included in the data used to establish trust. This method is also referred to as the transmit-echo-verify method.

[0160] If secure communication is supported at a specific Use Classification of Communicated Data (UCDC) level, at least one of the mobility and / or dispenser can verify that for all methods used to pair the mobility and the dispenser, the pairing provides sufficient information to secure the communication channel. For example, the pairing may include the exchange of encryption keys so that the mobility and the dispenser can secure communication during refueling.

[0161] Since UCDC Level 1 does not support bidirectional communication, communication channel security may not be possible. Pairing mobility and dispensers at UCDC Level 2 and UCDC Level 3 may be implemented to provide sufficient information to protect communication in order to meet a specific security level, e.g., IEC 62443 Security Level 3. IEC 62443 Security Level 3 may be a security level for actors with appropriate resources and appropriate motives.

[0162] The purpose, preconditions, and subsequent conditions of the UC2-communication security procedure (S420) may be disclosed according to the following Table 3.

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

[0164] Mobility may use UDP with DTLS for communication to support black channel communication. Black channel communication may refer to communication that applies the black channel principle, which ensures secure communication despite the output characteristics of a communication channel having unsecured attributes or attributes unrelated to the application. The communication channel prior to and after the UC2-communication security procedure (S420) may be established using different communication technologies. For example, the UC1-discovery and pairing procedure (S410) may be performed via a first communication channel based on a first communication technology that has a relatively wide range, including WLAN. The sequence after the UC2-communication security procedure (S420) may be performed via a second communication channel based on a second communication technology that has a relatively narrow range but has strengths in local communication.

[0165] The sequence following the UC2-communication security procedure (S420) may be performed partially via the first communication channel and / or the second communication channel based on shared information or required functions.

[0166] The purpose, preconditions, and subsequent conditions of the UC3-communication protocol negotiation procedure (S430) may be disclosed by the following Table 4.

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

[0168]

[0169] UC3-통신 프로토콜 협상 프로시져(S430)에서 협상 요청을 위하여 전송 및 수신되는 메시지의 내용은 다음의 표 5에 의하여 개시될 수 있다.

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

[0171]

[0172] Information regarding the communication protocol may include at least one of the index of the communication protocol, the name of the communication protocol, the version of the communication protocol, and the preference for the communication protocol. The content of the response message to the negotiation request message in the UC3-communication protocol negotiation procedure (S430) may be disclosed by the following Table 6.

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

[0174]

[0175] The response message may further include information regarding success or failure as a result of the communication protocol negotiation. Mobility and dispensers may interact based on various combinations of standards related to hydrogen fuel supply communication, communication modes, fuel supply methods, communication levels, and other parameters. Standards related to hydrogen fuel supply communication may include the SAE J2601 series, ISO 19885-3, ISO 19885-4, etc. Communication modes may include no comm., IrDA, XYZ (ISO), etc. Fuel supply methods may include table-based fuel supply methods such as lookup tables, MC formula-based fuel supply methods, etc. Communication levels may include UCDC levels, and other parameters may include pressure class, CHSS (compressed hydrogen storage system) category, fueling tables, etc.

[0176] The mobility or dispenser may further perform a process of falling back to the other party's lower type or lower UCDC level according to the mutual type or UCDC level confirmed in the communication protocol negotiation procedure.

[0177] If incompatibility is detected in the parameters exchanged while performing negotiation procedures (UC3 to UC5) for hydrogen fuel supply, the mobility and dispenser can return to the communication protocol negotiation procedure and perform the negotiation procedures again.

[0178] Mobility can assign priority to the communication protocols it supports. Mobility can provide the prioritized communication protocols to the dispenser. An example of the prioritized communication protocols is shown in Table 7 below.

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

[0180] The dispenser uses a specific protocol selected from the protocol list (<selected protocol> A response message containing ) can be delivered to the mobility. The specific protocol may be a common protocol selected by the dispenser, which is supported by both the dispenser and the mobility and is the highest priority protocol preferred by the mobility, such as the ISO 19885-3-2023-UCDC-3 protocol (see Table 7). According to the common protocol, the mobility and the dispenser can reach an agreement on the communication protocol to be used for fueling communication. When a communication protocol is selected in the UC3-communication protocol negotiation procedure (S430), the mobility and the dispenser can activate their respective communication protocol implementations and start the UC4-fueling protocol negotiation procedure (S540). The UC4-fueling protocol negotiation procedure (S540) is a procedure in which the mobility and the dispenser find and agree on a fueling protocol to be used for a fueling session. At this stage, among the protocols that both mobility and dispenser support, mobility can select the communication protocol it prefers most.

[0181] The purpose, preconditions, and subsequent conditions of the UC4-Fuel Supply Protocol Negotiation Procedure (S540) may be disclosed by the following Table 8.

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

[0183] The content of the message transmitted and received as a negotiation request message in the UC4-fuel supply protocol negotiation procedure (S540) can be disclosed according to the following Table 9.

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

[0185]

[0186] Information regarding the fuel supply protocol may include at least one of the index of the fuel supply protocol, the name of the fuel supply protocol, the version of the fuel supply protocol, the sub-protocol of the fuel supply protocol, and / or preference for the fuel supply protocol. The contents of the response message transmitted and received as a negotiation response message corresponding to the negotiation request in the UC4-fuel supply protocol negotiation procedure (S540) may be disclosed by the following Table 10.

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

[0188] The response message may further include information on whether the fuel supply protocol negotiation was successful. In another embodiment of the present invention, the content of the message transmitted as a negotiation request message in the UC4-fuel supply protocol negotiation procedure (S540) may be disclosed as shown in Table 11 below.

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

[0190] As shown in Table 11, the mobility may provide the dispenser with parameter information in the form of a table containing an arbitrarily assigned name, revision time (year) or version information, information on whether sub-protocols are provided, and preference information regarding supported fuel supply methods or fuel supply protocols. In another embodiment of the present invention, the dispenser may proactively exchange its own communication protocols and parameters with the mobility on behalf of the mobility, and may provide the mobility with priority assigned to the communication protocols supported by the dispenser.

[0191] In Table 11, PRHYDE (PRotocol for heavy-duty HYDrogEn refueling) may be presented by one of the European projects that has been developing a heavy-duty mobility refueling protocol, RTR-HFP may be presented by a protocol concept that improves refueling efficiency based on real-time communication, and ANN-MPC may be presented by a protocol concept that collects and analyzes data from the refueling site and predicts and applies it to the actual refueling situation.

[0192] Certain fueling protocols can be performed on a non-communicative basis. Unidirectional IrDA may be required for other fueling protocols to be executed. Bidirectional communication may be required for yet another fueling protocol to be executed. Both bidirectional communication and unidirectional IrDA may be required for yet another fueling protocol to be executed.

[0193] A predetermined UCDC level or a higher UCDC level may be required for a specific fuel supply protocol to be executed. At least one fuel supply protocol may be proposed based on the type or class of mobility and the type or class of dispenser. The proposed fuel supply protocols may be proposed with different priorities. Considering the priorities of the proposed fuel supply protocols, the communication protocol between the hydrogen mobility and / or dispenser and the fuel supply protocol may ultimately be determined based on whether the communication protocol required by the fuel supply protocol is supported by the hydrogen mobility and / or dispenser.

[0194] Tables 12 through 15 disclose parameters included in messages exchanged between mobility and dispenser in the UC5-fuel supply parameter negotiation procedure (S550).

[0195] Table 12 is an example of parameters on the mobility side.

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

[0197] Table 13 is an example of parameters on the dispenser side.

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

[0199] Table 14 is another example of parameters on the mobility side.

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

[0201] 표 15는 디스펜서 측의 파라미터의 다른 예시이다.

[0202] Physical ParametersFueling Delivery temp.T30Max Fuel Delivery Pressure? MPaMax Fuel Delivery Temp.? ℃Min Fuel Delivery Temp.? ℃Mas Fuel Delivery Flow Rate? g / sMonitoring ParametersCurrent Fuel Delivery Temp.? ℃Ambient Temperature? ℃Fueling GoalSelected Fueling TableD1Target SoC? %Target Final CHSS Pressure? MPaTarget Final CHSS Temperature? ℃Target APR? MPa / sAllowed Temperature? ℃Expected Fueling Duration? sSafety PolicyAcceptanceAcceptedTRUE / FALSE / PENDING

[0203] In the UC5-fuel supply parameter negotiation procedure (S550), the mobility and dispenser may generate and transmit a message to the other party containing ranges / values ​​for supported fueling parameters. The parameters may include physical characteristic-related parameters (briefly 'physical parameters'), monitoring parameters, safety policy-related parameters, acceptance-related parameters, etc. For the aforementioned parameters, information regarding one of the preset levels or set values ​​and information regarding different or identical main UCDC levels may be set, respectively. The negotiation process of the UC3-communication protocol negotiation procedure (S430), the UC4-fuel supply protocol negotiation procedure (S540), and / or the UC5-fuel supply parameter negotiation procedure (S550) may not be completed with a single message exchange, but may be completed by repeatedly exchanging messages multiple times.

[0204] At this time, for the protocols / parameters / items for which negotiation has been completed, in the transmitted message <accepted> , <true>, or <ok>Mark with , and for parameters / items currently under negotiation <pending>By indicating the above, the negotiation can be reached sequentially.

[0205] Parameters / items that are rejected or unusable during negotiation <rejected>, or <false>It can be excluded from the negotiation process by being marked as such.

[0206] Mobility and dispensers can reach a consensus on all parameters by repeatedly sending and receiving messages multiple times and responding to those messages.

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

[0208] The purpose, preconditions, and subsequent conditions of the UC6-Safety Check-in Procedure (S660) may be disclosed by the following Table 16.

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

[0210] Before the hydrogen fuel supply process begins, the UC6-Safety Check-in Procedure (S660) may be performed to check whether all safety conditions of the mobility and dispenser are met. This step may be optional. Whether the UC6-Safety Check-in Procedure (S660) is mandatory may be defined by the fuel supply protocol. A dedicated safety check-in procedure may be defined in the fuel supply protocol to ensure the desired level of safety in an accurate and explicit manner. If the UC3-communication protocol negotiation procedure (S430), the UC4-fuel supply protocol negotiation procedure (S540), and / or the UC5-fuel supply parameter negotiation procedure (S550) are successfully performed, the fuel supply protocol may perform the UC6-safety check-in procedure (S660). At this time, if the communication physical layer is specified to require a pairing procedure, the mobility and the dispenser may re-check the pairing before dispensing hydrogen in the UC6-safety check-in procedure (S660).

[0211] Even if the communication physical layer is not specified to require a pairing procedure, the mobility and dispenser can re-check the pairing before dispensing hydrogen in the UC6-safety check-in procedure (S660).

[0212] When fuel supply parameters are exchanged and mobility and dispenser are considered compatible, at step S660, mobility and dispenser can perform a safety status check to verify whether the fuel supply is safe. In an alternative embodiment of the present invention, the safety check may be performed implicitly within the protocol according to the fuel supply protocol, and depending on the implementation, the explicit safety check step (S660) may be omitted.

[0213] A mobility device or dispenser can send a request message to the other party signifying the initiation of a safety check-in, and the other party can respond with a response message to the safety check-in request message within a predetermined time interval.

[0214] In the safety check-in step (S660), the mobility and / or dispenser can check whether the nozzle-receptacle is secured (this may be referred to as a coupler check), check for leaks, and check the last-minute status.

[0215] In the safety check-in step (S660), the mobility and / or dispenser may exchange messages containing information indicating the inspection target (e.g., coupler, leakage, the last-minute status), the inspection result / status (OK / DONE / pending / ongoing / waiting / FAIL), and the inspector (mobility or dispenser). Here, "waiting" may refer to a state of waiting for an inspection result from the other party.

[0216] Depending on the inspection target, additional information may be included in the message or additional information may be requested. For example, when a leak inspection is completed, the dispenser may send a message to the mobility requesting the measured tank volume along with leak inspection completion information (Done).

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

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

[0219] In the UC7-monitoring and control procedure (S670), the mobility and / or dispenser can monitor the fuel supply status and control the fuel supply as necessary. Once all safety checks are verified, the mobility and dispenser can start fueling according to a selected fuel supply protocol using given parameters. While fueling, the mobility and dispenser can operate to determine the fuel supply status by exchanging various measurement data and to detect the occurrence of a safety-critical accident as quickly as possible.

[0220] The purpose, prerequisites, and subsequent conditions of the UC7-monitoring and control procedure (S670) may be disclosed according to the following Table 17.

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

[0222] If the UC6-Safety Check-in Procedure (S660) is successfully executed, the fuel supply protocol can execute the UC7-Monitoring and Control Procedure (S670). If the UC6-Safety Check-in Procedure (S660) is omitted, and the UC5-Fuel Supply Parameter Negotiation Procedure (S550) is successfully executed, the fuel supply protocol can execute the UC7-Monitoring and Control Procedure (S670). While the UC7-Monitoring and Control Procedure (S670) is being executed, the dispenser can perform all necessary steps to supply fuel to the mobility.

[0223] In addition, the mobility can transmit specific commands to the dispenser to control the fuel supply process, such as starting and stopping fuel supply. In this case, the mobility can use the aforementioned black channel communication.

[0224] The fuel supply protocol may specify static or dynamic data included in the message to be transmitted from the UC7-monitoring and control procedure (S670). The static or dynamic data may be defined to monitor the fuel supply status and exchange safety-related information.

[0225] The contents of the messages transmitted and received in the UC7-monitoring and control procedure (S670) may be disclosed according to the following Tables 18 and 19.

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

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

[0228] Static and dynamic data transmitted in the UC7-monitoring and control procedure (S670) can be used to generate control information for the fuel supply process and to control the fuel supply process. The dispenser can transmit a message with "status" set to "finished" when the fuel supply is completed (done) and the intended fuel supply goal is achieved. The dispenser can transmit a message with "status" set to "stop_error" and "reason" set to an appropriate reason code when the fuel supply is stopped due to a reason related to an error.

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

[0230] The dispenser can send a message with "status" set to "stopped_requested" when the "action" of the most recent message sent from the mobility is set to "stop" and the fuel supply has been completely stopped.

[0231] If Mobility sends a FuelLoopReq message with "action" set to "stop" and receives a FuelLoopRes message with "status" set to "stopping", Mobility can send a FuelLoopRes message with "action" set to "stop".

[0232] If a critical safety incident occurs, the mobility or dispenser can immediately send an EmergencyReq message, stop the fuel supply procedure, and shut down communication.

[0233] In one embodiment of the present invention, the mobility may request the start of step S670 and the dispenser may respond, but the concept of the present invention is not limited thereto. In an alternative embodiment of the present invention, either the mobility or the dispenser may first transmit a message requesting the start of step S670, and the other party may respond to the message requesting the start of step S670, thereby performing step S670.

[0234] In step S670, a message transmitted by either the mobility or the dispenser may include a request for monitoring regarding the status of the hydrogen fuel supply procedure. A response message sent by the other party may include the requested status information of the monitored target.

[0235] At this time, the state and related parameters that may be the subject of the monitoring request may include a set of parameters exchanged in step S550. The state and related parameters that may be the subject of the monitoring request may include the state and parameters of the mobility or dispenser. The state and related parameters that may be the subject of the monitoring request may include the fuel supply state and / or related parameters of the mobility and / or dispenser that are changed or maintained by the hydrogen fuel supply procedure.

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

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

[0238] In addition, the mobility can transmit a fuel supply control request message requesting the stop of fuel supply to the dispenser, and the dispenser can transmit a fuel supply status response message to the mobility that includes information on whether the fuel supply is being stopped or has been stopped (stopping / stopped).

[0239] In step S670, the mobility and the dispenser may exchange parameters related to the fuel supply status continuously or periodically. The mobility transmits the current tank temperature, current tank pressure, etc. to the dispenser, and the dispenser may provide the mobility with parameters related to the start, stop, ramping up, ramping down of fuel supply, current injection pressure, and future fuel supply plan.

[0240] Request messages related to control transmitted from the mobility to the dispenser may include information or parameters regarding the start, pause, resume, termination, etc. of fuel supply. Additionally, messages related to reporting transmitted from the mobility to the dispenser may include information or parameters regarding the current tank temperature, current tank pressure, etc.

[0241] Messages related to reporting transmitted from the dispenser to the mobility may include information or parameters regarding status information, current ambient temperature, current pressure ramp rate (PRR [Mbar / min]), deliver fuel flow rate (g / sec]), current fuel delivery temperature, pre-cooling temperature, current fuel delivery pressure, whether in use before full charge (buffering), whether the cooling dispenser is in use, whether the fallback is in use, the reason for stopping fuel supply, the amount of hydrogen currently supplied, etc.

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

[0243] According to one embodiment of the present invention, when a non-safety-critical error is detected in the UC7-monitoring and control procedure (S670) and the fuel supply is interrupted before the fuel supply is completed, the fuel supply protocol defines a fallback mechanism that ensures backward compatibility among mutually compatible mechanisms between the mobility and the dispenser, and can resume and complete the fuel supply based on the fallback mechanism.

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

[0245] After the hydrogen fuel supply process and the UC7-monitoring and control procedure (S670) are finished, and before terminating the session and unplugging the nozzle from the mobility, the mobility and the dispenser can verify that each of the mobility and the dispenser meets all safety conditions through the UC8-safety check-out procedure (S680). The UC8-safety check-out procedure (S680) may be optional.

[0246] It is strongly recommended that the fuel supply protocol define a dedicated UC8-Safety Checkout Procedure (S680) to ensure the desired safety level in an accurate and explicit manner.

[0247] The purpose, preconditions, and subsequent conditions of the UC8-Safety Check Out Procedure (S680) may be disclosed by the following Table 20.

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

[0249] Messages transmitted and received between the mobility and the dispenser in the UC8-Safety Check-Out Procedure (S680) may be implemented by borrowing the content of a message that includes information indicating the inspection target (e.g., coupler, leakage, the last-minute status), inspection result / status (OK / DONE / pending / ongoing / waiting / FAIL), and the inspection subject (mobility or dispenser) initiated in the aforementioned UC6-Safety Check-In Procedure (S660). The mobility and the dispenser may repeatedly report their respective statuses to each other until all safety inspections are confirmed. If the bidirectional hydrogen fuel supply communication process does not require such safety confirmation at the end, the use case for safety check-out may be omitted. When the coupler inspection completion information is confirmed to be successfully completed, the nozzle of the dispenser may be detached from the receptacle of the mobility by a user or operator.

[0250] In the UC8-safety check-out procedure (S680), the report message that the dispenser sends to the mobility may include information or parameters regarding the coupler unlock status. The coupler unlock status information may include information regarding locked, unlocked, icing, problem, etc.

[0251] The information exchange used in the UC8-Safety Check Out Procedure (S680) can be used for the purpose of diagnosing and identifying responsibility when a safety-related incident occurs.

[0252] Either the mobility or the dispenser may send a request message to the other party signifying the start of step S680, and the other party may respond with a response message to the request message for safe checkout within a predetermined time interval.

[0253] When fueling is successfully finished and optionally all safety conditions are confirmed, the mobility and dispenser can perform the UC9-termination procedure (S710).

[0254] The purpose, preconditions, and subsequent conditions of the UC9-termination procedure (S710) may be disclosed by the following Table 21.

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

[0256] A message requesting the start of the UC9-termination procedure (S710) may include the contents disclosed in Table 22 below.

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

[0258] The content of the Terminate Res message responding to the Terminate Req message of Table 22 may be disclosed according to the following Table 23.

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

[0260] In step S710, Mobility may send a message to the dispenser inquiring about how much fuel has been supplied. In response to the query message from Mobility, the dispenser may send a response message to Mobility containing information about the amount of hydrogen supplied (e.g., X gram). Mobility may send a confirmed request message regarding the completion of fuel supply to the dispenser, and the dispenser may send a "good bye" message to Mobility as a response message to the confirmed request message. After fuel supply is completed and safety checks are confirmed, Mobility and the dispenser may exchange at least some book-keeping information regarding the hydrogen fuel supply session in the termination step (S409). Before completing step S409, Mobility and the dispenser may exchange summary information regarding the hydrogen fuel supply session.

[0261] Book-keeping information may include all information related to hydrogen fuel supply that is recorded in the mobility or dispenser according to preset rules or policies prior to completing step S409 over all fueling sessions for hydrogen fuel supply.

[0262] Ledger information or summary information may include information such as how much fuel has been supplied and what reports have been generated. Additionally, report messages transmitted from the mobility to the dispenser may include information or parameters regarding the current tank temperature and current tank pressure, and report messages transmitted from the dispenser to the mobility may include information regarding the final SOC, the final average fueling rate (APR), the final measured tank pressure, the actual fueling time, and the actual amount of hydrogen supplied.

[0263] Once all necessary information for the fuel supply session is saved, the fuel supply session can be completely terminated.

[0264] For successful refueling, communication must provide expected behaviors according to the protocol. Refueling behavior must remain within an acceptable range based on the refueling protocol. However, in reality, various abnormal events can occur. Some errors are minor and can be easily handled. However, errors that are unrecoverable and prevent the continuation of refueling may also occur.

[0265] In this specification, 'error' or 'error' may refer to an incident occurring during UC1 to UC9 or hydrogen fueling that can interrupt the ongoing process.

[0266] In the UC10-error handling procedure (S720), non-critical errors can be handled. In this case, conditions for non-critical errors, exemplary error conditions, and responses can be specified.

[0267] The purpose, preconditions, and subsequent conditions of the UC10-Error Handling Procedure (S720) may be disclosed by the following Table 24.

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

[0269] Non-safety-critical error conditions that are not fatal to safety but may affect the hydrogen fuel supply process may include, for example, the following: communication errors, which may include 1) when communication is disconnected, 2) when received data cannot be recognized due to encoding or syntactic errors, or 3) when received data is in an unacceptable range. System errors, which may include when the dispenser or mobility detects its own critical system error.

[0270] Qualitative errors may include 1) cases where communication performance fails to meet the required level, and 2) cases where the quality of data integrity or precision fails to meet the required level.

[0271] When a non-safety-critical error occurs and further communication is impossible, the mobility and dispenser immediately stop the fueling and take safe steps, stop the communication, and end the session.

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

[0273] When a non-safety-critical error is detected by the mobility and the communication channel is still operating, the mobility can send a TerminateReq message in which "action" is set to "stop" and "reason" is set to an appropriate reason code.

[0274] When a non-safety-critical error is detected by the dispenser and the communication channel is still operating, the dispenser may first immediately stop the fuel supply and send a TerminateReq message in which "action" is set to "stop" and "reason" is set to an appropriate reason code.

[0275] The fuel supply protocol can define error conditions according to the protocol and can provide detection criteria, and prescribe response procedures including notification, termination procedure, and fallback mechanism.

[0276] Step S720 defines error conditions related to the fuel supply protocol and provides detection criteria, and may include a response process including notification, termination process, and fallback mechanism when detected.

[0277] Step S720 may be applied in cases where a non-safety fatal error occurs and further communication is impossible. That is, the mobility and dispenser can handle a non-safety fatal error that may occur at any time during fuel supply in Step S720. In other words, the mobility and dispenser can immediately stop fuel supply, pause the previously operating use case, and then proceed to the termination use case (UC9, Step S710).

[0278] In step S720 according to an embodiment of the present invention, specific operations can be performed as follows (1) to (4) regarding the aforementioned error conditions.

[0279] (1) If a non-critical error occurs and further communication is impossible, the mobility and dispenser may immediately stop fuel supply, but take safe measures and stop communication to terminate the session.

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

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

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

[0283] The purpose, prerequisites, and subsequent conditions of the UC11-Emergency Handling Procedure (S730) may be disclosed by the following Table 25.

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

[0285] The fuel supply protocol may define emergency conditions according to the protocol and provide prescribed response procedures to avoid entering a detrimental situation by all means, including detection criteria, notification, termination procedures, and fallback mechanisms. When the mobility or dispenser detects a safety-critical situation, necessary actions to prevent a catastrophic event may be performed immediately. Additionally, if possible, a message notifying the emergency along with information about the event may be transmitted, and communication may be closed. When the mobility or dispenser receives the message notifying the emergency, it may immediately respond to the action instructed within the message and close the communication without undue delay.

[0286] For the criticality of the message and the efficiency of delivery, the fuel supply protocol may not be permitted to modify the structure of the message notifying of the emergency.

[0287] The names of elements included in the message notifying an emergency may include class, type, action, etc., and may be disclosed according to Table 26 below. Elements not shown in the contents of Table 26 below may be specified by each fuel supply protocol standard, for example, ISO 19885-3. For example, additional emergency reason codes and action codes may be specified for each protocol.

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

[0289] For safe fuel supply, communication must exhibit expected behavior according to the protocol, and the fuel supply operation must be within the safe range of the fuel supply protocol. However, there is a possibility that a problem may occur during fuel supply, causing the fuel supply system (or hydrogen fuel supply system) to reach a critical state that must be avoided at all costs. Therefore, in step S730, safety-critical emergency conditions and possible responses to emergency conditions may be defined, and critical cases to be considered may be provided. The fuel supply protocol may define emergency conditions related to the protocol, provide detection criteria and performance requirements, and define step S730 for responding to ensure that hazardous situations are not entered. For example, if a high pressure state exceeding a preset threshold is detected by the mobility while hydrogen fuel supply is in progress, the mobility may transmit an emergency request message to the dispenser requesting the cessation of fuel supply due to the high pressure.

[0290] In addition, for example, if a hydrogen fuel leak is detected by the dispenser, the dispenser can send an emergency request message to the mobility requesting the cessation of fuel supply due to the leak.

[0291] The content of the response message to the emergency request message can refer to the content defined in the emergency request message.

[0292] In each step of FIG. 4 that proceeds sequentially, when a preceding step is completed, a message indicating the initiation of a subsequent step may be transmitted within a predetermined time interval. For example, when a message indicating the completion of the UC5-fuel supply parameter negotiation procedure (S550) is exchanged between the mobility and the dispenser, a message indicating the initiation of the UC6-safety check-in procedure (S660) may be transmitted from the mobility to the dispenser, or from the dispenser to the mobility, within a predetermined time interval.

[0293] FIG. 5 is an operation flowchart conceptually illustrating a hydrogen fuel supply security communication method according to one embodiment of the present invention.

[0294] In the secure communication method illustrated in FIG. 5, the operation of the mobility (100) can be performed by the communication device (114) of the mobility (100), and the operation of the dispenser (200) can be performed by the communication device (204) of the dispenser (200).

[0295] Referring to FIG. 5, a communication method for hydrogen fuel supply according to an embodiment of the present invention is performed between a communication device (114) of a hydrogen fueled mobility (100) and a communication device (204) of a dispenser (200) that supplies hydrogen to the mobility (100), and comprises: a discovery and pairing step (UC1, S410) in which the mobility (100) and the dispenser (200) discover and pair each other; and a step (S1300) of performing authentication or authorization between the mobility (100) and the dispenser (200) based on dispenser authentication information transmitted from a hydrogen fueling operator (HFO) (350) associated with the dispenser (200) and provided from the dispenser (200) to the mobility (100), and mobility authentication information provided from the mobility (100). and may include a step (S1400) of establishing a secure communication channel between the mobility (100) and the dispenser (200) based on the result of authentication or authorization between the mobility (100) and the dispenser (200).

[0296] In a communication method for hydrogen fuel supply according to one embodiment of the present invention, the step (S1300) of performing authentication or authorization between the mobility (100) and the dispenser (200) and the step (S1400) of establishing a secure communication channel between the mobility (100) and the dispenser (200) may be performed as part of a transport layer security (TLS) handshake procedure between the mobility (100) and the dispenser (200). In this case, the TLS handshake procedure may be performed as part of the aforementioned step S420.

[0297] In a communication method for hydrogen fuel supply according to one embodiment of the present invention, the step (1300) of performing authentication or authorization between the mobility (100) and the dispenser (200) and the step (1400) of establishing a secure communication channel between the mobility (100) and the dispenser (200) may be performed using a security algorithm of a predetermined security level or higher.

[0298] At this time, the predetermined Security Level is 256 bits (>10 77 It may be. The security algorithm may use the ECC curve: sep521r1 as the public key algorithm. The signature algorithm may be the ECDSA algorithm. The certificate format may be X.509. The key exchange algorithm may be ECDHE. The encryption / integrity algorithm may be AES-256-GCM. The hash algorithm may be SHA512.

[0299] In a communication method for hydrogen fuel supply according to one embodiment of the present invention, the dispenser authentication information may be distributed from the hydrogen fuel supply business operator (HFO) (350) to the dispenser (200) (S1140).

[0300] In a communication method for hydrogen fuel supply according to one embodiment of the present invention, the dispenser authentication information may be generated by a trusted service provider associated with the hydrogen fuel supply business operator (HFO) (350) and transmitted to the dispenser (200) via the hydrogen fuel supply business operator (HFO) (350).

[0301] In a communication method for hydrogen fuel supply according to one embodiment of the present invention, the mobility authentication information is transmitted from the original equipment manufacturer (OEM) (150) of the mobility (100) (S1120) and can be provided from the mobility (100) to the dispenser (200).

[0302] FIG. 6 is an operation flowchart conceptually illustrating the operation between functional blocks corresponding to procedures in a hydrogen fuel supply communication method according to one embodiment of the present invention.

[0303] Referring to FIG. 6, a communication method for hydrogen fuel supply according to one embodiment of the present invention may perform at least one of steps S430, S540, S550, S660, S670, S680, S710, S720, and / or S730 based on the secure communication channel established in step S420 based on the result of authentication or authorization between the mobility (100) and the dispenser (200).

[0304] A communication method for hydrogen fuel supply according to one embodiment of the present invention may further include a step (S430, S540, or S550) of negotiating a communication protocol, a fuel supply protocol, or fuel supply parameters between the mobility (100) and the dispenser (200) based on the secure communication channel established in step S420 based on the result of authentication or authorization between the mobility (100) and the dispenser (200).

[0305] A communication method for hydrogen fuel supply according to one embodiment of the present invention may further include a step (S660) of checking in safety requirements before a hydrogen fuel supply process is started between the mobility (100) and the dispenser (200), based on the secure communication channel established in step S420 based on the result of authentication or authorization between the mobility (100) and the dispenser (200).

[0306] A communication method for hydrogen fuel supply according to one embodiment of the present invention may further include a monitoring step (S670) in which status information of the mobility side based on the hydrogen fuel supply process is provided while the hydrogen fuel supply process is performed between the mobility (100) and the dispenser (200), based on the secure communication channel established in step S420 based on the result of authentication or authorization between the mobility (100) and the dispenser (200).

[0307] FIG. 7 is an operation flowchart conceptually illustrating a secure communication method for hydrogen fuel supply according to one embodiment of the present invention.

[0308] Referring to FIG. 7, a communication method for hydrogen fuel supply according to one embodiment of the present invention may include a process of requesting and responding to authentication-related information of the other party between the mobility (100) or the dispenser (200).

[0309] A communication method for hydrogen fuel supply according to one embodiment of the present invention may further include the step (S1120) in which a first entity, which is either the mobility (100) or the dispenser (200), requests authentication-related information from a second entity, which is the counterpart, in order to establish the secure communication channel.

[0310] At this time, the step (S1120) of requesting authentication-related information of the second entity may be performed as part of a transport layer security (TLS) handshake procedure between the mobility (100) and the dispenser (200).

[0311] A communication method for hydrogen fuel supply according to one embodiment of the present invention may further include the step (S1160) in which the second entity requests authentication-related information of the first entity while responding with authentication-related information of the second entity (S1140).

[0312] At this time, the step (S1160) of requesting authentication-related information of the first entity can be performed as part of a transport layer security (TLS) handshake procedure between the mobility (100) and the dispenser (200).

[0313] In the embodiment of FIG. 7, an embodiment is shown in which the first entity is a dispenser (200) and the second entity is a mobility (100), but in an alternative embodiment of the present invention, the first entity may be a mobility (100) and the second entity may be a dispenser (200) as needed.

[0314] In one embodiment of the present invention, in order to respond in step S1140 to the authentication-related information of the second entity requested in step S1120, the second entity may provide the authentication-related information of the second entity, which is stored in advance, to the first entity in step S1140.

[0315] In an alternative embodiment of the present invention, in order to respond in step S1140 with the authentication information of the second entity requested in step S1120, the second entity may provide the authentication information of the second entity to the first entity in step S1140 through additional handshake communication with the OEM (150).

[0316] In one embodiment of the present invention, in order to respond in step S1180 with authentication-related information of the first entity requested in step S1160, the first entity may provide prior-stored authentication-related information of the first entity to the second entity in step S1180.

[0317] In an alternative embodiment of the present invention, in order to respond in step S1180 with the authentication-related information of the first entity requested in step S1160, the first entity may provide the authentication-related information of the first entity to the second entity in step S1180 through additional handshake communication with the HFO (350).

[0318] In the embodiments of FIGS. 6 and 7, HFO (350), dispenser (200), mobility (100), and OEM (150) may be part of an ecosystem for hydrogen fuel supply.

[0319] Certification information for authentication between the dispenser (200) and the mobility (100) in the ecosystem for hydrogen fuel supply can be generated by a trusted service provider. The trusted service provider may be an HFO (350) or an OEM (150), etc., or a specialized organization that handles certification information (certificates) as a third party.

[0320] Public and private keys may be used to generate and process authentication / authorization information. Authentication / authorization information may be generated, signed, and managed based on a hierarchical structure by one or more entities included within the ecosystem.

[0321] Information related to authentication / authorization can be classified into higher-level certificates and leaf certificates based on a hierarchical structure.

[0322] Information regarding the certification / authorization of the mobility (100) may have a specified validity period or life.

[0323] The process of generating, processing, and managing authentication / authorization-related information can be implemented based on the security provided by the Public Key Infrastructure (PKI).

[0324] PKI-based authentication / authorization / certification information provided by an ecosystem including HFO (350), dispenser (200), mobility (100), and OEM (150) can be used to establish a secure communication channel between mobility (100) and dispenser (200).

[0325] PKI-based authentication / authorization / proof information provided by an ecosystem including HFO (350), dispenser (200), mobility (100), and OEM (150) can be used in a separate authentication / authorization / verification process after the pairing step (S410).

[0326] FIG. 8 is an operation flowchart conceptually illustrating the operation between functional blocks corresponding to procedures in a hydrogen fuel supply communication method according to embodiments of the present invention.

[0327] FIG. 8 is an alternative embodiment of the embodiment of FIG. 4, wherein the UC index for identifying some of the functional blocks of FIG. 4 is shown in FIG. 8 and has been modified, but the substantial function can be considered the same. The description of the functional blocks of FIG. 10, which overlaps with the description of the functional blocks of FIG. 4, is omitted.

[0328] Referring to FIG. 8, a UC2-communication setup procedure (S415) may be included in the connecting group (S400) between the UC1-discovery and pairing procedure (S410) and the UC3-communication security procedure (S420).

[0329] A UC4-encoding and session management procedure (S425) may be included in the connecting group (S400) between the UC3-communication security procedure (S420) and the UC5-communication protocol negotiation procedure (S430).

[0330] Between the UC8-safety check-in procedure (S660) and the UC10-monitoring and control procedure (S670), the UC9-safety-critical communication procedure (S665) may be included in the fueling group (S600).

[0331] In FIG. 8, at least some of the procedures following the UC4-encoding and session management procedure (S425) can be performed using the secure communication channel established in the UC3-communication security procedure (S420).

[0332] For example, all or part of S425, S430, S540, S550, S660, S665, S670, S680, S710, S720, and / or S730 may be performed using a secure communication channel established in the UC3-communication security procedure (S420).

[0333] In the UC1-Discovery and Pairing Procedure (S410), pairing can be performed, and the communication device (114) or communication module of the mobility (100) and the communication device (204) or communication module of the dispenser (200) can discover each other and a data link can be established.

[0334] In the UC2-communication setup procedure (S415), an IP address can be set up between the mobility (100) and the dispenser (200), the mobility (100) can discover the dispenser (200) using the TCP / UDP protocol, and establish a TCP link.

[0335] The UC2-communication setup procedure (S415) may be a procedure performed at the network layer or the transport layer of the OSI-7 layers.

[0336] Table 27 discloses the purpose, preconditions, and subsequent conditions of the UC2-communication setup procedure (S415) of FIG. 8.

[0337] TypeDescriptionUse case nameUC-2: "Communication Setup"ObjectivesUC-2 allows the vehicle / mobility to setup the communication with dispenser in network and transport layer. This includes IP address assignment, Dispenser's IP / port discovery and TCP link establishment. During this process, a paired status is also confirmed.Short DescriptionAfter data-link is established, the vehicle / mobility first self-assigns its IP address according to SLAAC mechanism defined in IPv6. Once IP address is assigned, the vehicle / mobility broadcasts an inquiry message, which is replied by the dispenser with its connection information. The connection information includes the IP address and TCP & UDP port number of the dispenser. These inquiry and response messages also contain pairing IDs so that the vehicle / mobility and dispenser can confirm that they are talking to paired entities. Then vehicle / mobility initiates TCP handshake to make a reliable connection with the dispenser.Pre-conditionsData-link between vehicle / mobility and the dispenser is active.Post-conditionsPaired vehicle / mobility and dispenser established a TCP connection and the vehicle / mobility is ready to send a UDP packet when needed.

[0338] The pre-conditions of the UC2-communication setup procedure (S415) may include 1) that the physical & data link connection among the OSI-7 layers is completed, and 2) that initialized pairing is performed at the data link level, and 3) that the initialized pairing refers to the pairing between the communication module / device of the mobility (100) and the dispenser (200), respectively. In the UC3-communication security procedure (S420), a TLS link may be established. The UC4-encoding and session management procedure (S425) may provide a method for managing the type and schema of application payloads / messages exchanged between the mobility (100) and the dispenser (200) so as to distinguish various fuel supply sessions and manage messages in a chronological order.

[0339] Table 28 discloses the purpose, preconditions, and subsequent conditions of the UC4-encoding and session management procedure (S425) of FIG. 10.

[0340] TypeDescriptionUse case nameUC-4: "Encoding and Session Management"ObjectivesUC-4 allows the vehicle / mobility and dispenser to exchange application payload in a coherent format, effectively switch between different types of messaging schema, and manage a fueling session so that different fueling sessions are distinguished and messages are managed in a chronical order.Short DescriptionOnce a secure communication channel is established, the vehicle / mobility and dispenser can exchange message payloads. To handle diverse nature of application messages, we use ASN.1 schemas with COER encoding rules to coherently express information in a modular way. The messages are encapsulated with a common message header so that devices can efficiently allocate resources to handle messages, and can distinguish different schemas. With session ID and time stamps in the session header, different sessions can be managed separately and chronical order of the messages are preserved.Pre-conditionsAn authenticated and encrypted communication link is established.Post-conditionsVehicle / mobility and dispenser can exchange application payloads using different ASN.1 schemas with session management and messaging time preservation.

[0341] The UC4-Encoding and Session Management Procedure (S425) may propose a format including a header and message payload of an application payload / message exchanged between the mobility (100) and the dispenser (200), and may provide a procedure for encoding a message to include the header and message payload. In the UC5-Communication Protocol Negotiation Procedure (S430), an application layer protocol may be initiated and a communication protocol may be negotiated. In the UC8-Safety Check-in Procedure (S660), a safety check-in may be performed and pairing may be performed again.

[0342] The UC9-safety-critical communication procedure (S665) can provide a communication environment for transmitting and receiving safety-critical dynamic data using a black channel, etc., after confirming that safety conditions are met before hydrogen fuel supply begins.

[0343] Table 29 discloses the purpose, preconditions, and subsequent conditions of the UC9-safety-critical communication procedure (S665) of FIG. 10.

[0344] TypeDescriptionUse case nameUC-9: "Safety-critical Communication"ObjectivesAfter vehicle / mobility and dispenser is ready for fueling, if the fueling communication contains safety-critical dynamic data to be exchanged (e.g., UCDC-3), this use case achieves a reliable communication using a safety-critical messaging layer with black-channel assumption. This use case is optional and only applies to UCDC-3.Short DescriptionSince the failure of the UCDC-3 communication can lead to safety-critical incidents, vehicle / mobility and dispenser switches to UDP / DTLS and achieve reliable communication by Safety-critical Messaging Protocol (SMP) that resides between security layer and session layer. The SMP addresses various reliability concerns such as corruption, loss, reordering, delay, redundancy, insertion, masquerade, and wrong addressing.Pre-conditionsVehicle / mobility and dispenser are ready to begin fueling in a safe status.Post-conditionsVehicle / mobility and dispenser can exchange their fueling messages in a secure and reliable manner.

[0345] The UC9-Safety-Critical Communication Procedure (S665) may provide a sequence that can switch to the UDP / DTLS protocol to achieve Safety-critical Messaging Protocol (SMP) between the security layer and the session layer. In the UC10-Monitoring and Control Procedure (S670), the DTLS protocol may be set up if necessary. Referring to the embodiments of FIGS. 1 through 8, PKI-based authentication / authorization / certification information provided by an ecosystem including HFO (350), dispenser (200), mobility (100), and OEM (150) may be used to establish a secure communication channel between mobility (100) and dispenser (200).

[0346] Referring to the embodiments of FIGS. 1 to 8, PKI-based authentication / authorization / proof information provided by an ecosystem including HFO (350), dispenser (200), mobility (100), and OEM (150) can be used in a separate authentication / authorization / verification process after the pairing step (S410).

[0347] FIG. 9 is a conceptual diagram illustrating a multiplexing structure in which a Fire-and-Forget method and a Request / Response method can be performed simultaneously in a communication process between a hydrogen fuel mobility and a dispenser according to embodiments of the present invention.

[0348] Referring to FIG. 9, the mobility (100) and the dispenser (200) exchange messages of different nature during the hydrogen fueling process. Some messages need to be transmitted repeatedly at very short intervals (e.g., 50ms), while others require a request for a specific action and an acknowledgment thereto. The Fire-and-Forget method is a method in which the sender unilaterally transmits data regardless of whether the receiver responds, and is suitable for the transmission of continuous and frequent monitoring data, such as sensor value reports of pressure, temperature, and flow rate within the CHSS. The Request / Response method is a method in which the sender transmits a request and the receiver provides a response, and is suitable for control functions such as starting, stopping, and verifying the reason for stopping fueling.

[0349] As illustrated in FIG. 9, the Fire-and-Forget message stream and the Request / Response message stream can operate independently of each other while operating simultaneously on a single communication path. This multiplexing structure is particularly useful in the UC7 (monitoring and control) procedure of FIG. 4 or the UC10 (monitoring and control) procedure of FIG. 8, and ensures that the mobility and the dispenser can reliably exchange control commands while sharing their states in real time.

[0350] FIG. 10 is a conceptual diagram illustrating the message exchange process in a UC7 procedure with a multiplexing structure applied according to one embodiment of the present invention.

[0351] Referring to FIG. 10, the mobility (100) repeatedly transmits a FuelingDataNotif message in a Fire-and-Forget manner, and the dispenser (200) transmits a FuelingStatusNotif message to the mobility (100) in a Fire-and-Forget manner. The FuelingDataNotif message may include dynamic data such as pressure, temperature, flow rate, and State of Charge (SOC) on the side of the mobility (100), and this data serves as the basis for the dispenser (200) to determine in real time whether the fuel supply process is proceeding safely.

[0352] The FuelingStatusNotif message indicates the fueling status of the dispenser (200) and may include status codes such as preparing, fueling, ramping-up, stopping, finished, aborted, etc. Meanwhile, when the mobility (100) sends a FuelingLoopReq message to command the start or stop of fuel supply, the dispenser (200) may respond with a FuelingLoopRes message to confirm whether the request has been processed successfully.

[0353] In this case, FuelingLoopReq / Res messages operate according to the Request / Response pattern and are executed concurrently with the Fire-and-Forget message stream, but are processed independently by the message management layer so that no interference occurs.

[0354] According to the structure illustrated in Fig. 10, fuel supply status reporting, control command transmission, and safety status verification can all be performed in parallel, which has the effect of improving the stability and reliability of the fuel supply session.

[0355] FIG. 11 shows a transmission period (INT) in a Fire-and-Forget message transmission method according to embodiments of the present invention. tx ), reception interval(INT rx ), packet loss rate (r), acceptance probability (P tol This is a conceptual diagram illustrating the relationship between ).

[0356] Referring to FIG. 11, the FuelingDataNotif message, which is periodically transmitted from the mobility (100) to the dispenser (200), has a specific transmission period (INT tx It is transmitted every ) and the dispenser (200) has a maximum allowable reception interval (INT rx At least one message must be received within ) to be determined to be in a normal state.

[0357] If INTtx is set to an excessively long duration, there is a risk that the message will not arrive within INTrx in the event of packet loss, leading to it being recognized as an abnormal state. Therefore, INTtx must be set to be sufficiently short in proportion to INTrx, along with the loss rate r and the tolerance probability P tol Considering this, the following mathematical formula 1 must be satisfied.

[0358]

[0359] For example, r = 1% and P tol If = 0.1%, INTtx must be limited to about 66% or less of INTrx (INTtx ≤ INTrx*0.66). This means that mobility must send messages more frequently in order for the dispenser to reliably receive data.

[0360] The X marking shown in Fig. 11 indicates a case where the message does not arrive and is determined to be abnormal, while the others indicate a case where the message arrives normally and monitoring is maintained. This control method according to one embodiment of the present invention ensures the reliability of Fire-and-Forget messages and, at the same time, can transmit data at shorter intervals compared to the request-response method, thereby improving the performance of the UC7 monitoring and control procedure.

[0361] FIG. 12 is a flowchart illustrating a message processing procedure from a mobility perspective according to embodiments of the present invention.

[0362] As illustrated in FIGS. 2 and 12, the mobility (100) first performs a step (S1210) of identifying a supportable communication pattern with the dispenser (200). This step (S1210) of identifying a supportable communication pattern may be performed in the U2 Communication Setup step of FIG. 8.

[0363] Subsequently, based on whether an asynchronous communication pattern is supported (i.e., if an asynchronous communication pattern is supported), the mobility (100) transmits a first message to the dispenser (200) (step S1220), and transmits a second message to the dispenser (200) regardless of whether a response to the first message is received (step S1240). The first message and the second message are messages of the same type, for example, the first message and the second message are FuelingDataNotif. That is, the first and second messages contain dynamic data such as sensor values ​​on the mobility (100) side, such as pressure, temperature, and flow rate, and are transmitted periodically regardless of whether a response is received, as they are transmitted in a Fire-and-Forget manner.

[0364] Additionally, the mobility (100) may transmit a third message to the dispenser (200) (step S1230). Subsequently, the mobility (100) receives a fourth message from the dispenser (200) in response to the third message (step S1250). For example, the third message is a message requesting a specific control operation, such as fuel supply start, stop, or emergency stop, and the fourth message is a response message to this. The third message may be a fueling loop request message (FuelingLoopReq), and the fourth message may be a fueling loop response message (FuelingLoopRes). Through this, it is possible to verify whether the requested control operation was performed normally.

[0365] The transmission of the first to third messages and the reception of the fourth message can proceed without interfering with each other.

[0366] Meanwhile, in FIG. 12, only the step of the fourth message following the third message is constrained, and the rest of the message sequence can be freely arranged, which is obvious to those skilled in the art from FIG. 9 and FIG. 10. The transmission and reception of these messages (steps S1220 to S1250) may be carried out in the UC7 monitoring and control procedure in FIG. 4, or in the UC10 monitoring and control procedure in FIG. 8.

[0367] FIG. 13 is a flowchart illustrating a message processing procedure from the perspective of a dispenser according to embodiments of the present invention.

[0368] As illustrated in FIGS. 2 and 13, the dispenser (200) first performs a step (S1310) of identifying a supportable communication pattern with the mobility (100). This step (S1310) of identifying a supportable communication pattern may be performed in the U2 Communication Setup step of FIG. 8.

[0369] Subsequently, based on whether an asynchronous communication pattern is supported (i.e., if an asynchronous communication pattern is supported), the dispenser (200) receives a first message from the mobility (100) (step S1320), and receives a second message from the mobility (100) regardless of whether a response to the first message is transmitted (step S1340). The first message and the second message are messages of the same type, for example, the first message and the second message are FuelingDataNotif. That is, the first and second messages contain dynamic data such as sensor values ​​on the mobility (100) side, such as pressure, temperature, and flow rate, and are transmitted periodically regardless of whether a response is received, as they are transmitted in a Fire-and-Forget manner.

[0370] Additionally, the dispenser (200) may receive a third message from the mobility (100) (step S1330). Subsequently, the dispenser (200) transmits a fourth message in response to the third message to the mobility (100) (step S1350). For example, the third message is a message requesting a specific control operation such as fuel supply start, stop, or emergency stop, and the fourth message is a response message to this. The third message may be a fueling loop request message (FuelingLoopReq), and the fourth message may be a fueling loop response message (FuelingLoopRes). Through this, it is possible to verify whether the requested control operation was performed normally.

[0371] The reception of the first to third messages and the transmission of the fourth message can proceed without interfering with each other.

[0372] Meanwhile, in FIG. 12, only the step of the fourth message following the third message is constrained, and the rest of the message sequence can be freely arranged, which is obvious to those skilled in the art from FIG. 9 and FIG. 10. The transmission and reception of these messages (steps S1320 to S1350) may be carried out in the UC7 monitoring and control procedure in FIG. 4, or in the UC10 monitoring and control procedure in FIG. 8.

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

[0374] Although omitted in the drawings in the embodiments of FIGS. 1 to 13, each component and functional element of the embodiments of FIGS. 1 to 13 may have their operation controlled or managed by a processor that is electronically connected to a processor and memory, and loads and executes program instructions stored in memory.

[0375] At least some of the processes of the fuel supply communication method for electric vehicle fuel supply according to embodiments of the present invention can be executed by the computing system (3000) of FIG. 16.

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

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

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

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

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

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

[0382] An artificial neural network model (3800) may be used to implement the embodiments of FIGS. 1 to 13. As shown in FIG. 14, the artificial neural network model (3800) may electronically communicate with other components, including a processor (3100) and a memory (3200), via a bus (3700).

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

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

[0385] A communication device or communication control device disposed in a hydrogen fuel mobility (100) according to embodiments of the present invention may include a memory (3200) storing at least one command; and a processor (3100) executing at least one command. The processor (3100) may perform the following process by executing at least one command.

[0386] Referring to FIGS. 2 and 14, the processor (3100) checks for a supported communication pattern with the dispenser (200) and, based on whether an asynchronous communication pattern is supported, controls the communication device (114) to transmit a first message to the dispenser (200), and controls the communication device (114) to transmit a second message to the dispenser (200) regardless of whether a response to the first message is received. At this time, the first message and the second message are messages of the same type.

[0387] The processor (3100) controls the communication device (114) so ​​that the communication device (114) transmits a third message to the dispenser (200), and the communication device (114) receives a fourth message from the dispenser (200) in response to the third message, wherein the transmission of the third message and the reception of the fourth message may be carried out in a handshake manner.

[0388] The transmission of the first to third messages and the reception of the fourth message can be carried out in a monitoring and control procedure without interfering with each other.

[0389] The first message and the second message may be a FuelingDataNotif message, the third message may be a FuelingLoopReq message, and the fourth message may be a FuelingLoopRes message.

[0390] Verification of the above-mentioned supported communication patterns can be performed during the Communication Setup stage.

[0391] The transmission time interval between the first message and the second message can be determined by the packet loss rate and the probability that a packet does not arrive during the maximum allowed packet arrival interval.

[0392] Meanwhile, although most of the aforementioned embodiments have focused on a method of first transmitting the communication protocol or parameters of the hydrogen fuel mobility from the hydrogen fuel mobility to the dispenser, the present invention is not limited to specific embodiments and can be configured to first transmit the communication protocol or parameters of the dispenser from the hydrogen fuel mobility. In this case, it is obvious that the invention has substantially the same features, except that the sender becomes the receiver and the receiver becomes the sender in the corresponding embodiment.

[0393] The operation of the method according to an embodiment of the present invention can be implemented as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes all types of recording devices in which information that can be read by a computer system is stored. Additionally, the computer-readable recording medium may be distributed across networked computer systems, allowing computer-readable programs or code to be stored and executed in a distributed manner.

[0394] In addition, computer-readable recording media may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, and flash memory. Program instructions may include machine code, such as that generated by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc.

[0395] Some aspects of the invention have been described in the context of a device, but may also be described according to a corresponding method, wherein a block or device corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method may also be described according to a corresponding block or item or a feature of a corresponding device. Some or all of the method steps may be performed by (or using) a hardware device, such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, at least one of the most important method steps may be performed by such a device.

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

[0397] Although the present invention has been described with reference to preferred embodiments, those skilled in the art will understand that various modifications and changes can be made to the invention without departing from the spirit and scope of the invention as described in the following claims.< / false> < / rejected> < / pending> < / ok> < / true> < / accepted>

Claims

1. In a communication method for mobility, A step of verifying the dispenser and supported communication patterns; A step of transmitting a first message to the dispenser based on whether an asynchronous communication pattern is supported; and The method includes the step of transmitting a second message to the dispenser regardless of whether a response to the first message is received, and The first message and the second message are messages of the same type, Communication method.

2. In Claim 1, A step of transmitting a third message to the dispenser; and The method further includes the step of receiving a fourth message from the dispenser in response to the third message; The transmission of the third message and the reception of the fourth message are carried out via a handshake method. Communication method.

3. In Claim 2, The transmission of the first to third messages and the reception of the fourth message are carried out in the Monitoring and Control procedure, Communication method.

4. In Claim 3, The first message and the second message above are fuel charging data notification messages (FuelingDataNotif), and The above third message is a Fueling Loop Request message (FuelingLoopReq), and The above fourth message is a Fueling Loop Response message, Communication method.

5. In Claim 1, The step of verifying the above-mentioned supportable communication patterns is performed during the Communication Setup step, Communication method.

6. In Claim 2, The transmission of the first to third messages and the reception of the fourth message proceed without interfering with each other. Communication method.

7. In Claim 1, The transmission time interval between the first message and the second message is determined by the packet loss rate and the probability that a packet does not arrive during the maximum allowed packet arrival interval. Communication method.

8. In the communication method of the dispenser, Step of verifying mobility and supported communication patterns; A step of receiving a first message from the mobility based on whether an asynchronous communication pattern is supported; and The method includes the step of receiving a second message from the mobility regardless of whether the dispenser transmits a response to the first message, and The first message and the second message are messages of the same type, Communication method.

9. In Claim 8, A step of receiving a third message from the above mobility; and The method further includes the step of transmitting a fourth message to the mobility in response to the third message above, and The reception of the third message and the transmission of the fourth message are carried out via a handshake method. Communication method.

10. In Claim 9, The reception of the first to third messages and the transmission of the fourth message are carried out in the Monitoring and Control procedure. Communication method.

11. In Claim 10, The first message and the second message above are fuel charging data notification messages (FuelingDataNotif), and The above third message is a Fueling Loop Request message (FuelingLoopReq), and The above fourth message is a Fueling Loop Response message, Communication method.

12. In claim 8, The step of verifying the above-mentioned supportable communication patterns is performed during the Communication Setup step, Communication method.

13. In Claim 9, The reception of the first to third messages and the transmission of the fourth message proceed without interfering with each other. Communication method.

14. In Claim 8, The reception time interval between the first message and the second message is determined by the packet loss rate and the probability that a packet does not arrive during the maximum allowed packet arrival interval. Communication method.

15. As a mobility that performs communication with a dispenser, processor; and Includes a communication device; The above processor is, Check the above dispenser and supported communication patterns, and Based on whether an asynchronous communication pattern is supported, the communication device is controlled to transmit a first message to the dispenser, and The communication device is controlled to transmit a second message to the dispenser regardless of whether a response to the first message is received, and The first message and the second message are messages of the same type, Mobility.

16. In Claim 15, The processor controls the communication device so that the communication device transmits a third message to the dispenser, and The communication device receives a fourth message from the dispenser in response to the third message, and The transmission of the third message and the reception of the fourth message are carried out via a handshake method. Mobility.

17. In Claim 16, The transmission of the first to third messages and the reception of the fourth message proceed in a monitoring and control procedure without interfering with each other. Mobility.

18. In Claim 16, The first message and the second message above are fuel charging data notification messages (FuelingDataNotif), and The above third message is a Fueling Loop Request message (FuelingLoopReq), and The above fourth message is a Fueling Loop Response message, Mobility.

19. In Claim 15, The verification of the above-mentioned supported communication patterns is performed during the Communication Setup phase, Mobility.

20. In Claim 15, The transmission time interval between the first message and the second message is determined by the packet loss rate and the probability that a packet does not arrive during the maximum allowed packet arrival interval. Mobility.

Images