Patent Description:
During operation of an aircraft, flight crews need to interface with the different systems of the aircraft, monitor equipment onboard the aircraft, access information, communicate with air traffic controllers, and respond to different events during all phases of a flight among other tasks involved in flying an airplane. Accessing information, monitoring equipment, and responding to certain occurrences, along with actually flying the airplane, can be hectic at times, particularly during high workload situations for the crew. Accordingly, there is a need for systems that reduce pilot workload, improve situational awareness, and allow the crew to focus on actual operation and navigation of the aircraft.

<CIT> describes, in accordance with its abstract, systems and methods for CPDLC message processing using dynamic on-demand screen generation for message response and composition. A described method for processing received CPDLC messages comprises: receiving a CPDLC message having a plurality of message elements; extracting the plurality of message elements from the CPDLC message; generating a first display screen at a user display interface for a first extracted message element, wherein the first display screen includes a user response field corresponding to a message-type attribute associated with the first extracted message element; generating a second display screen at the user display interface for a second extracted message element, wherein the second display screen includes a user response field corresponding to a message-type attribute associated with the second extracted message element; composing a response CPDLC message from a first user responses received via the first and second display screens; and sending the response CPDLC message.

<CIT> describes, in accordance with its abstract, a method and system of monitoring aural and message alerts received during flight in an internet of things cockpit of an aircraft generated by systems within the cockpit, the method includes: receiving a plurality of alerts which include at least one of an aural alert or message alert; applying a first natural language processing, NLP, process to the aural alert to convert the aural alert to a text alert consistent in structure with the message alert for aggregating together with the message alert to form a concatenated message alert; and identifying the context of the concatenated message alert by applying a second NLP process to the concatenated message alert in its entirety and subsequent tagging the concatenated message alert to associate a tagged message with a display element wherein the tagged message is a concatenated message.

In a first aspect, an interface system for flight deck communications in accordance with claim <NUM> is described. In a second aspect, a method for flight deck communications in accordance with claim <NUM> is described.

In accordance with an example, an interface system for flight deck communications includes a chatbot configured to perform a conversation with a pilot. The conversation includes speech communications, visual communications using a display, or both. The interface system also includes a dynamic conversational graph generator configured to perform a set of functions. The set of functions includes determining a flight operational procedure from the conversation with the pilot; providing information associated with the flight operational procedure to the chatbot for communicating to the pilot; and responding to any requests received from the pilot by the chatbot during the conversation with the pilot.

In accordance with another example, a method for flight deck communications includes performing, by a chatbot, a conversation with a pilot, wherein the conversation includes speech communications, visual communications using a display, or both. The method also includes determining, by a dynamic conversational graph generator, a flight operational procedure from the conversation with the pilot. The method additionally includes providing, by the dynamic conversational graph generator, information associated with the flight operational procedure to the chatbot for communicating to the pilot. The method further includes responding, by the dynamic conversational graph generator, to any requests from the pilot received by the chatbot during the conversation with the pilot.

In accordance with an example and any of the preceding examples, the interface system and method further include a tokenizer. The tokenizer is configured to: convert text received from the chatbot to tokens transmitted by the tokenizer; and convert tokens received by the tokenizer to text that is transmitted to the chatbot to perform the conversation with the pilot.

In accordance with an example and any of the preceding examples, the set of functions performed by the dynamic conversational graph generator further includes: detecting a keyword in the conversation with the pilot using the tokens from the tokenizer, wherein the keyword identifies a particular flight operational procedure; searching a plurality of nodes of a dynamic conversational graph to identify a node corresponding to the keyword in the conversation with the pilot, wherein each node corresponds to a different flight operational procedure; handing-off communications to a system directed conversation module in response to the node corresponding to the keyword having an owner, wherein the owner is a particular aircraft system associated with the flight operational procedure; and determining an identification of any neighboring nodes in the dynamic conversational graph to the node corresponding to the keyword in response to the node not having an owner, wherein the identification of any neighboring nodes are communicated to the pilot by the chatbot in the conversation.

In accordance with an example and any of the preceding examples, the interface system and the method further include a system directed conversation module configured to provide certain tokens including particular information associated with the flight operational procedure to the tokenizer in response to the flight operational procedure being associated with a particular aircraft system of a plurality of aircraft systems. The dynamic conversational graph generator is configured to handoff communications to the system directed conversation module in response to the flight operational procedure being associated with the particular aircraft system.

In accordance with an example and any of the preceding examples, the interface system and the method further include a command encoder/decoder configured to: receive and execute formatted instructions related to the flight operational procedure from the system directed conversation module for communications with the particular aircraft system of the plurality of aircraft systems; and decode the particular information from the particular aircraft system into a set of responses for communications with the system directed conversation module.

In accordance with an example and any of the preceding examples, the interface system and method further include a dynamic widget/form generator configured to perform a set of functions including: receiving the tokens from the tokenizer, or a controller-pilot data link communications (CPDLC)/Aircraft Communication Addressing and Reporting System (ACARS) text analyzer that receives text; and generating a particular form, widget or both in response to the tokens.

In accordance with an example and any of the preceding examples, the interface system and method further include a dynamic widget/form generator configured to generate a particular form, widget or both associated with the flight operational procedure for presentation in a window on a display. The particular form, widget or both are configured for interaction with the pilot.

In accordance with an example and any of the preceding examples, the interface system and method, wherein a visual positioning or alignment of the particular form, widget or both associated with the flight operational procedure is correlated to a corresponding visual chatbot conversational text.

In accordance with an example and any of the preceding examples, the interface system and method, wherein pilot interaction with the particular form, widget or both includes at least one of interaction by conversing with the chatbot or interaction by the pilot touching a feature of the particular form, widget, or both.

In accordance with an example and any of the preceding examples, the interface system and method further include an automatic speech recognition device configured to receive speech from the pilot and to convert the speech to text for transmission to the chatbot. The interface system and method additionally include a text-to-speech converter configured to receive text from the chatbot and to convert the text to speech for transmission to the pilot by a speaker, wherein the speaker is in a flight deck or a headset of the pilot.

In accordance with an example and any of the preceding examples, the interface system or method wherein the chatbot is configured to perform the conversation with the pilot using at least one of an audio panel in a flight deck, a cockpit display in the flight deck, or a portable electronic device.

The following detailed description of examples refers to the accompanying drawings, which illustrate specific examples of the disclosure. Other examples having different structures and operations do not depart from the scope of the present disclosure. Like reference numerals may refer to the same element or component in the different drawings.

The present disclosure may be a system, a method, and/or a computer program product. The computer program product may include a computer-readable storage medium (or media) having computer-readable program instructions thereon for causing a processor to carry out aspects of the present disclosure.

The computer-readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer-readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer-readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer-readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer-readable program instructions described herein can be downloaded to respective computing/processing devices from a computer-readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. A network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium within the respective computing/processing device.

Computer-readable program instructions for carrying out operations of the present disclosure may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In some examples, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer-readable program instructions by utilizing state information of the computer-readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present disclosure.

Aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to examples of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.

These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

In accordance with some examples of the present disclosure, an interface system for flight deck communications includes a chatbot configured to perform a conversation with a pilot. The conversation includes speech communications or audio communications, visual communications using a display or interactive touchscreen, or both. The interface system includes a dynamic conversational graph generator configured to perform a set of functions. The set of functions includes but is not limited to determining a flight operational procedure from the conversation with the pilot; providing information associated with the flight operational procedure to the chatbot for communicating to the pilot; and responding to any requests received from the pilot by the chatbot during the conversation with the pilot. In some examples, the interface system also includes a tokenizer configured to convert text received from the chatbot to tokens which are transmitted by the tokenizer and to convert tokens received by the tokenizer to text that is transmitted to the chatbot to perform the conversation with the pilot.

In some examples, the interface system also includes a system directed conversation module configured to direct the conversation with the pilot to a particular aircraft system associated with the flight operational procedure. The dynamic conversational graph generator is configured to handoff communications to the system directed conversation module in response to the flight operational procedure being associated with the particular aircraft system of a plurality of aircraft systems.

In some examples, the interface system also includes a dynamic widget/form generator configured to generate a particular form, widget or both associated with the flight operational procedure for presentation in a window on a display. The particular form, widget or both are configured for interaction with the pilot. Pilot interaction with the particular form, widget or both includes but is not limited to at least one of interaction by conversing with the chatbot or interaction by the pilot touching a feature of the particular form, widget, or both on a display. Examples of the display include but are not limited to a touchscreen cockpit display in the flight deck or a display of a portable electronic device. Accordingly, the examples of interface systems for flight deck communications described herein reduce pilot workload, improve situational awareness, and allow the crew to focus on actual operation and navigation of the aircraft.

<FIG> and <FIG> are a block schematic diagram of an example of an interface system <NUM> for flight deck communications in accordance with an example of the present disclosure. The interface system <NUM> includes a chatbot <NUM> configured to perform a conversation with a pilot <NUM>. The conversation includes speech or audio communications, visual communications using a display, or both. An example of performance of a conversation <NUM> between the chatbot <NUM> and a pilot <NUM> will be described with reference to <FIG>. The chatbot <NUM> is configured to perform the conversation <NUM> with the pilot <NUM> using at least one of an audio panel <NUM> in a flight deck <NUM>, a cockpit display <NUM> in the flight deck <NUM>, or a portable electronic device <NUM>, such as a tablet computer, electronic flight bag (EFB) or similar device. The audio panel <NUM> includes a microphone <NUM> to receive speech or audio signals from the pilot <NUM> and a speaker <NUM> to transmit speech or audio signals to the pilot <NUM>. In some examples, the cockpit display <NUM> includes a touchscreen <NUM> configured to receive inputs by the pilot <NUM> touching the cockpit display <NUM> as described herein. The portable electronic device <NUM> also includes a touchscreen <NUM> configured to receive inputs by touch.

In the examples in <FIG> and <FIG>, a display computer <NUM> interconnects the chatbot <NUM> to the cockpit display <NUM>. The display computer <NUM> is configured to convert text signals from the chatbot <NUM> to video signals for presentation on the cockpit display <NUM> and to convert input signals entered by the pilot <NUM> into the touchscreen <NUM> into text signals that are usable by the chatbot <NUM>.

In the examples in <FIG> and <FIG>, an aircraft interface device <NUM> interconnects the chatbot <NUM> to the portable electronic device <NUM>. The aircraft interface device <NUM> is configured to convert text signals from the chatbot <NUM> to video signals for presentation on the portable electronic device <NUM> and to convert input signals entered by the pilot into the touchscreen <NUM> into text signals that are usable by the chatbot <NUM>.

The interface system <NUM> also includes an automatic speech recognition (ASR) device <NUM> configured to receive speech from the pilot <NUM> by the microphone <NUM> and to covert the speech to text for transmission to the chatbot <NUM>. The interface system <NUM> additionally includes a text-to-speech (TTS) converter <NUM> configured to receive text from the chatbot <NUM> and to convert the text to speech or audio for transmission to the pilot <NUM> by the speaker <NUM>. The speaker <NUM> is in the flight deck <NUM> or a headset of the pilot <NUM>.

The interface system <NUM> further includes a tokenizer <NUM> configured to convert text received from the chatbot <NUM> to tokens transmitted by the tokenizer <NUM> and to convert tokens received by the tokenizer <NUM> to text that is transmitted to the chatbot <NUM> to perform the conversation <NUM> with the pilot <NUM>. The tokenizer <NUM> breaks-up sentences or a sequence of words or phrases spoken by the pilot <NUM> into pieces, such as words, keywords, phrases, symbols or other elements called tokens. Tokens can be individual words, phrases or a whole sentence.

The interface system <NUM> also includes a dynamic conversational graph generator <NUM> configured to perform a set of functions <NUM>. Referring also to <FIG> is a flow chart of an example of a method <NUM> of operation of the dynamic conversational graph generator <NUM> in accordance with an example of the present disclosure. The exemplary method <NUM> includes an example of the set of functions <NUM>. The method <NUM> or set of functions <NUM> includes but is not limited to: receiving, in block <NUM>, one or more tokens <NUM> corresponding to the conversation <NUM> with the pilot <NUM> from the tokenizer <NUM>; determining, in block <NUM>, a flight operational procedure from the tokens <NUM> corresponding to the conversation <NUM> with the pilot <NUM>; providing, in block <NUM>, information associated with the flight operational procedure to the chatbot <NUM> for communicating to the pilot <NUM>; and responding, in block <NUM>, to any requests received from the pilot <NUM> by the chatbot <NUM> during the conversation <NUM> with the pilot <NUM>. Examples of additional functions of the set of functions <NUM> performed by the dynamic conversational graph generator <NUM> will be described with reference <FIG> and <FIG>.

The dynamic conversational graph generator <NUM> accesses a historical/trained conversation database <NUM> to perform the set of functions <NUM>. An example of a method <NUM> for generating a historical/trained conversation database <NUM> will be described with reference to <FIG>. The historical/trained conversation database <NUM> includes historical information and/or is trained to form dynamic conversational graphs for performing a conversation with the pilot <NUM>, e.g., exemplary conversation <NUM> (<FIG>). An example of a dynamic conversational graph <NUM> is illustrated in <FIG> and is useable for performance of a conversation, such as the exemplary conversation <NUM> in <FIG>.

The interface system <NUM> further includes a system directed conversation module <NUM> configured to direct the conversation with the pilot <NUM> to a particular aircraft system <NUM> associated with the flight operational procedure. As used herein, an aircraft system <NUM> also includes a subsystem of an aircraft system <NUM>. The system directed conversation module <NUM> is configured to provide certain tokens including particular information associated with the flight operational procedure to the tokenizer <NUM> in response to the flight operational procedure being associated with a particular aircraft system <NUM> of a plurality of aircraft systems 136a-136n. The dynamic conversational graph generator <NUM> is configured to handoff communications to the system directed conversation module <NUM> in response to the flight operational procedure being associated with the particular aircraft system <NUM>. Examples of the aircraft systems 136a-136n include but are not limited to a flight management system (FMS) 136a, a flight computer (FC) 136b, electronic checklists 136c performed by a display system, a health management system 136d, and other airborne systems 136n or subsystems.

The system directed conversation module <NUM> is configured to perform a set of functions <NUM>. Referring also to <FIG> is a flow chart of an example of a method <NUM> of operation of a system directed conversation module <NUM> in accordance with an example of the present disclosure. The exemplary method <NUM> includes an example of the set of functions <NUM>. The method <NUM> or set of functions <NUM> includes but is not limited to the functions described with reference to blocks <NUM>-<NUM>. In block <NUM>, the method <NUM> or set of functions <NUM> includes receiving one or more tokens <NUM> from the tokenizer <NUM>. The tokens <NUM> include information associated with the flight operational procedure.

In block <NUM>, the method or set of functions <NUM> includes querying a database <NUM> related to the flight operational procedure by the system directed conversation module <NUM> using the tokens <NUM>. An example of a database <NUM> for use by the system directed conversation module <NUM> will be described with reference to <FIG>.

In block <NUM>, the method <NUM> or set of functions <NUM> includes determining the particular aircraft system <NUM> of the plurality of aircraft systems 136a-136n for performing the flight operational procedure.

In block <NUM>, the method <NUM> or set of functions <NUM> includes executing a sequence of steps <NUM> (<FIG>) associated with the flight operational procedure and fetching a set of commands <NUM> that describes the flight operational procedure stored in the database <NUM>.

In block <NUM>, the method <NUM> or set of functions <NUM> includes communicating the commands <NUM> by the system directed conversation module <NUM> to the command encoder/decoder <NUM> for communication with the particular aircraft system <NUM>. The particular aircraft system <NUM> is configured to perform the commands <NUM> and return information related to the flight operational procedure similar to that described with reference to the examples in <FIG> and <FIG>.

In block <NUM>, the method <NUM> or set of functions <NUM> include receiving information related to the flight operational procedure by the system directed conversation module <NUM> from the particular aircraft system via the command encoder/decoder <NUM>.

In block <NUM>, the method <NUM> or set of functions <NUM> includes communicating information related to the flight operational procedure by the system directed conversation module <NUM> to the pilot <NUM> through the tokenizer <NUM> and the chatbot <NUM>.

In some examples, the database <NUM> includes one or more subsystem specific speech/TTS databases 140a-140n. The database <NUM> is created for the desired flight operational procedures and is field loadable. Referring also to <FIG> is an illustration of an example of a database <NUM> for use by the system directed conversation module <NUM> in accordance with an example of the present disclosure. The exemplary database <NUM> illustrated in <FIG> includes an example of a sequence of steps <NUM> for presenting an approach checklist <NUM> by an electronic checklist 136c on a display system <NUM>, e.g., the cockpit display <NUM>, portable electronic device <NUM>, or both. The database <NUM> is used by the system directed conversation module <NUM> in translation of tokens <NUM> into the sequence of steps <NUM> which contains mnemonics/opcode and operands/formatted instructions <NUM> which the command encoder/decoder <NUM> is configured to interpret. The response from the command encoder/decoder <NUM> is used by the system directed conversation module <NUM> to fetch the tokens from the database <NUM> and forward the tokens to the tokenizer <NUM> for communication in the conversation <NUM> with the pilot <NUM>.

Referring back to <FIG> and <FIG>, the interface system <NUM> further includes a command encoder/decoder <NUM>. The command encoder/decoder <NUM> is configured to receive and execute the mnemonics/opcode and operands/formatted instructions from the system directed conversation module <NUM>. Thereby, the command encoder/decoder <NUM> encodes and communicates avionics data with the particular aircraft system <NUM> of the plurality of the systems 136a-136n, as illustrated in <FIG> and <FIG>. The command encoder/decoder <NUM> is also configured to decode the particular information from the particular aircraft system <NUM> of the plurality of aircraft systems 136a- 136n into a set of responses for communication with the system directed conversation module <NUM> and execution of the set of functions <NUM>.

Referring to <FIG>, the interface system <NUM> further includes a dynamic widget/form generator <NUM> configured to generate a particular form, widget or both associated with the flight operational procedure for presentation in a window of a display, e.g., the cockpit display <NUM>, display of the portable electronic device <NUM>, or both. The dynamic widget/form generator <NUM> uses a keyword/phrase to dynamic forms/widgets database <NUM> to generate the particular form, widget or both. An example of a method <NUM> of operation of the dynamic widget/form generator <NUM> and using the keyword/phrase to dynamic forms/widgets database <NUM> to generate a particular form, widget or both will be described with reference to <FIG> and <FIG> and <FIG>. The particular form, widget or both are configured for interaction with the pilot <NUM>. As shown in the example in <FIG>, the dynamic widget/form generator <NUM> is coupled to cockpit display <NUM> by the display computer <NUM>. The cockpit display <NUM> is also coupled to the chatbot <NUM> as previously described and shown in <FIG> The display computer <NUM> is configured to convert signals from the dynamic widget/form generator <NUM> to video signals for presentation on the cockpit display <NUM> and to convert input signals entered by the pilot <NUM> into the touchscreen <NUM> into signals that are usable by the dynamic widget/form generator <NUM> for communication with a particular aircraft system <NUM>, using the tokenizer <NUM>, system directed conversation module <NUM> and command encoder/decoder <NUM>.

The dynamic widget/form generator <NUM> is coupled to the portable electronic device <NUM> by the aircraft interface device <NUM>. The portable electronic device <NUM> is also coupled to the chatbot <NUM> as previously described and shown in <FIG>. The aircraft interface device <NUM> is configured to convert signals from the dynamic widget/form generator <NUM> to video signals for presentation on the portable electronic device <NUM> and to convert input signals entered by the pilot <NUM> into the touchscreen <NUM> into signals that are usable by the dynamic widget/form generator <NUM> for communication with a particular aircraft system <NUM> using the tokenizer <NUM>, system directed conversation module <NUM> and command encoder/decoder <NUM>.

In some examples, the dynamic widget/form generator <NUM> is configured to perform a set of functions <NUM> including but not limited to receiving tokens <NUM> from the tokenizer <NUM>, or receiving tokens <NUM> from a data link/controller-pilot data link communications (DL/CPDLC)/Aircraft Communications Addressing and Reporting System (ACARS) text analyzer <NUM> that receives text <NUM>; and generating a particular form, widget or both in response to the tokens <NUM> or <NUM>. The DL/CPDLC/ACARS text analyzer <NUM> receives the text <NUM> from a ground station or other source.

An example of a method <NUM> of operation of the dynamic widget/form generator <NUM> will be described with reference to <FIG>. Examples of a form, widget or both presented in a window 904a-904d of a display <NUM> are illustrated in <FIG> and will be described with reference to <FIG>. A visual positioning or alignment of a particular form, widget or both associated with a flight operational procedure is correlated to a corresponding visual chatbot conversational text <NUM> as illustrated in <FIG>. The pilot interaction with the particular form, widget or both includes at least one of interaction by conversing with the chatbot <NUM> or interaction by the pilot <NUM> touching a feature of the particular form, widget, or both, on a touchscreen <NUM> or <NUM> as described with reference to <FIG> and <FIG>.

<FIG> are a flow chart of an example of a method <NUM> of operation of the interface system <NUM> in <FIG> and <FIG> in accordance with an example of the present disclosure. The flow chart is divided into functions or operations that are performable by the different components in <FIG> and <FIG>. In some examples, the set of functions <NUM> performable by the dynamic conversational graph generator <NUM> and the set of functions <NUM> performable by the system directed conversation module <NUM> are embodied in the method <NUM>. In block <NUM>, the method <NUM> includes receiving text by a display. In accordance with some examples, the text is received by the touchscreen <NUM> of the cockpit display <NUM> or the touchscreen <NUM> of the display of the portable electronic device <NUM> entered by the pilot <NUM> as previously described.

In addition, or alternatively to receiving text by the display, in block <NUM>, the method <NUM> includes receiving speech from the pilot <NUM>. In some examples, in block <NUM>, the method <NUM> includes presenting text of the speech on the display.

In block <NUM>, the method <NUM> includes receiving the text by the chatbot <NUM>. In block <NUM>, the method <NUM> includes converting the text to tokens by the tokenizer <NUM>.

In accordance with some examples, the set of functions <NUM> performable by the dynamic conversational graph generator <NUM> includes blocks <NUM>-<NUM> and blocks <NUM>-<NUM> in <FIG>. In block <NUM>, the method <NUM> or set of functions <NUM> includes receiving the tokens by the dynamic conversational graph generator <NUM>.

Referring also to <FIG> are a table <NUM> illustrating an example of performance of a conversation <NUM> with a pilot <NUM> in accordance with an example of the present disclosure. In block <NUM> (<FIG>), the method <NUM> or set of functions <NUM> performed by the dynamic conversational graph generator <NUM> includes detecting a keyword <NUM> (<FIG>) or keywords in the conversation <NUM> with the pilot <NUM> using the tokens from the tokenizer <NUM>. The keyword <NUM> identifies a particular flight operational procedure. In the example in <FIG>, the keyword <NUM> or keywords are "Approach Phase" which identifies the particular flight operational procedure.

Referring also to <FIG> is an example of a dynamic conversational graph <NUM> in accordance with an example of the present disclosure. In block <NUM>, the method <NUM> or set of functions <NUM> additionally includes searching a plurality of nodes <NUM>-<NUM> (<FIG>) of a dynamic conversational graph <NUM> to identify a node <NUM> corresponding to the keyword <NUM> (<FIG>) in the conversation <NUM> with the pilot <NUM>. Each node <NUM>-<NUM> of the dynamic conversational graph <NUM> corresponds to a different flight operational procedure. In the example in <FIG> and <FIG>, the keyword <NUM> "Approach Phase" corresponds to the flight operational procedure node <NUM> in <FIG>.

In block <NUM>, the method <NUM> or set of functions <NUM> performed by the dynamic conversational graph generator <NUM> further includes determining if the node <NUM> corresponding to the flight operational procedure has an owner or particular aircraft system <NUM> for performing the flight operational procedure.

In block <NUM>, the method <NUM> or set of functions <NUM> performed by the dynamic conversational graph generator <NUM> additionally includes handing-off (block <NUM>) communications to the system directed conversation module <NUM> in response to the node <NUM> corresponding to the keyword <NUM> having an owner. The owner is a particular aircraft system <NUM> associated with the flight operational procedure or particular aircraft system <NUM> that performs the flight operational procedure. The method <NUM> or set of functions <NUM> advances to block <NUM> in response to the node <NUM> corresponding to the keyword <NUM> not having an owner.

In block <NUM>, the method <NUM> or set of functions <NUM> performed by the dynamic conversational graph generator <NUM> further includes determining an identification of any neighboring nodes <NUM> in the dynamic conversational graph <NUM> to the node <NUM> corresponding to the keyword <NUM> in response to the node <NUM> not having an owner in block <NUM>. In the example illustrated in <FIG>, the neighboring nodes <NUM> to node <NUM> corresponding to the keyword <NUM> and flight operational procedure include the identifications <NUM>: "Approach Chart" 606a (neighboring node 704a), "Approach Clearance" 606b (neighboring node 704b), "Approach Checklist" 606c (neighboring node 704c), and "Approach Briefing" 606d (neighboring node 704d). The identifications <NUM> of the neighboring nodes <NUM> are communicated to the pilot <NUM> by the chatbot <NUM> in the conversation <NUM> as illustrated in the example conversation in <FIG> and block <NUM> of <FIG>.

In block <NUM>, the method <NUM> or set of functions <NUM> performed by the dynamic conversational graph generator <NUM> includes generating a response including the identifications <NUM> of the neighboring nodes <NUM> in response to the node <NUM> corresponding to the keyword <NUM> and flight operational procedure having neighboring nodes 704a-704d. The response generated by the dynamic conversational graph generator <NUM> includes tokens each corresponding to the identifications 606a-606d of the neighboring nodes 704a-704d.

In block <NUM>, the tokenizer <NUM> converts the tokens to text. In block <NUM>, the chatbot <NUM> constructs one or more sentences using the text from the tokenizer <NUM> as illustrated in <FIG>. In block <NUM>, the text-to-speech (TTS) converter <NUM> converts the text to speech. The speech is transmitted to the pilot <NUM> in block <NUM> by the speaker <NUM>, or the text is presented on a display <NUM> or <NUM> in block <NUM>, or both as illustrated in <FIG>. In performance of the conversation with the pilot <NUM>, which was indicated at block <NUM> as including the dynamic conversational graph generator detecting a keyword or keywords "Approach Phase" in the conversation with the pilot using the tokens from the tokenizer, from which a node is identified corresponding to the keyword in the conversation that is determined to pertain to a particular aircraft system associated with the flight operational procedure, the dynamic conversational graph generator then generates a response that includes tokens corresponding to the identification that are converted by the tokenizer to construct one or more sentences that are output or transmitted to the pilot as speech and/or displayed on a display in the cockpit, such that the pilot can request an Approach checklist for display (which can further be confirmed by voice or an entry by the pilot using a touchscreen).

In the example in <FIG> and <FIG>, the conversation <NUM> with the pilot <NUM> continues similar to that previously described. In block <NUM>, the method <NUM> includes receiving a text response by the display, e.g., the cockpit display <NUM> or display of the portable electronic device <NUM> entered by the pilot <NUM> using touchscreen <NUM> or <NUM>. Alternatively, or in addition, in block <NUM>, the method <NUM> includes receiving a speech response from the pilot <NUM> by the automatic speech recognition (ASR) device <NUM>. The response <NUM> in the example in <FIG> is either a text response, speech response or both. In block <NUM>, the ASR device <NUM> converts the speech to text.

In block <NUM>, the method <NUM> includes receiving the text response <NUM> by the chatbot <NUM> from either the ASR device <NUM>, display, or both. In block <NUM>, the method <NUM> includes converting the text response <NUM> to tokens by the tokenizer <NUM>.

In block <NUM>, the method <NUM> includes receiving the tokens by the dynamic conversational graph generator <NUM>. In block <NUM>, the method <NUM> or set of functions <NUM> includes detecting another keyword <NUM> or keywords corresponding to another flight operational procedure in the response <NUM> from the pilot <NUM> using the tokens. In the example conversation <NUM> in <FIG>, the other keyword <NUM> or keywords are "Approach Checklist" in the response <NUM> from the pilot <NUM>.

In block <NUM>, the method <NUM> or set of functions <NUM> performed by the dynamic conversational graph generator <NUM> further includes searching the neighboring nodes 704a-704d of the dynamic conversational graph <NUM> to identify a certain neighboring node 704c corresponding to another keyword <NUM> or keywords during the conversation <NUM> with the pilot <NUM>. In the example in <FIG>, the keyword <NUM> "Approach Checklist" corresponds to neighboring node 704c.

In block <NUM>, the method <NUM> or set of functions <NUM> further includes determining if the certain neighboring node 704c corresponding to the flight operational procedure "Approach Checklist" has an owner or aircraft system <NUM> for performing the flight operational procedure. In the example in <FIG>, the neighboring node 704c has the owner node 706d "Electronic Checklist" which corresponds to the electronic checklist 136c performed by the display system in <FIG> and <FIG>.

In block <NUM>, the method <NUM> or set of functions <NUM> includes handing-off (block <NUM>) communications to the system directed conversation module <NUM> in response to the certain neighboring node 704c having an associated owner node 706d. Alternatively, the method <NUM> advances to block <NUM> in response to the certain neighboring node <NUM> not having an owner or aircraft system <NUM> for performing the flight operational procedure. In block <NUM>, the conversation ends or continues in response to the pilot <NUM> continuing the conversation <NUM> by speech being received by the ASR device <NUM> and/or text being received by a display, e.g., cockpit display <NUM> or display of a portable electronic device <NUM>.

<FIG> is an example of continuing the conversation using a particular aircraft system <NUM> in accordance with an example of the present disclosure. In block <NUM>, the method <NUM> includes receiving text by a display. In accordance with some examples, the text is received by the touchscreen <NUM> of the cockpit display <NUM> or the touchscreen <NUM> of the display of the portable electronic device <NUM>. In addition, or alternatively to receiving text by the display, in block <NUM>, the method <NUM> includes receiving speech by the ASR device <NUM>. In block <NUM>, the ASR device <NUM> converts the speech to text. In some examples, the method <NUM> includes presenting text of the speech on the display.

In block <NUM>, the method <NUM> includes receiving the text by the chatbot <NUM>. In block <NUM>, the method <NUM> includes converting the text to tokens by the tokenizer <NUM>. In block <NUM>, the method <NUM> includes receiving the tokens by the system directed conversation module <NUM> as illustrated in the example in <FIG>. The tokens include information associated with the flight operational procedure from the conversation with the pilot <NUM>. The system directed conversation module <NUM> is configured to identify, using the tokens, a particular aircraft system <NUM> for performing the flight operational procedure. In block <NUM>, mnemonic/opcode and operand/formatted instructions related to the flight operational procedure are fetched by the system directed conversation module <NUM> from the database <NUM> as illustrated in the example in <FIG>. The mnemonic/opcode and operand/formatted instructions are transmitted by the system directed conversation module <NUM> to the command encoder/decoder <NUM>.

In block <NUM>, the command encoder/decoder <NUM> is configured to receive and execute formatted instructions related to the flight operational procedure from the system directed conversation module for communications with a particular aircraft system <NUM> of the plurality of aircraft systems 136a-136n. The command encoder/decoder <NUM> is further configured to interpret the mnemonic/opcode and operand/formatted instructions and communicate avionics data with the particular aircraft system <NUM> of the plurality of aircraft systems 136a-136n for performing the flight operational procedure.

In block <NUM>, the method <NUM> includes performing an operation by the particular aircraft system <NUM> in response to the encoded information. Examples of operations performed by a particular aircraft system <NUM> and communication with the pilot <NUM> are illustrated in the conversation <NUM> in the example in <FIG>. In the example in <FIG>, the particular aircraft system <NUM>, e.g., a display system, includes presenting <NUM> a checklist on a display; verifying <NUM> landing lights are switched on by the pilot <NUM> and presenting confirmation on the display; verifying <NUM> an altimeter setting set by the pilot <NUM> and presenting the altimeter setting on the display; and reading <NUM> navigation frequencies of the navigation radios set by the pilot <NUM>.

In block <NUM>, the method <NUM> includes generating a response including any information or data by the particular aircraft system <NUM> for communication to the pilot <NUM>. In block <NUM>, the response is transmitted by the particular aircraft system <NUM> to the command encoder/decoder <NUM>.

In block <NUM>, the command encoder/decoder <NUM> is configured to decode the particular information from the particular aircraft system <NUM> into a set of responses for communications with the system directed conversation module <NUM>. In block <NUM>, the command encoder/decoder <NUM> generates one or more responses for the mnemonics/opcode-operands/formatted instructions that are executed by the particular aircraft system <NUM>. The one or more responses are transmitted to the system directed conversation module <NUM>. In block <NUM>, the system directed conversation module <NUM> receives the response or responses to the mnemonics/opcode-operand/formatted instructions and fetches one or more corresponding tokens from the database <NUM>. The system directed conversation module <NUM> transmits the one or more tokens to the tokenizer <NUM> as also illustrated in the example in <FIG> and <FIG>. In block <NUM>, converting the tokens to text is performed by the tokenizer <NUM>. The tokenizer <NUM> transmits the text to the chatbot <NUM> for communication with the pilot <NUM>.

In block <NUM>, the chatbot <NUM> constructs one or more sentences using the tokens received from the tokenizer <NUM>. Examples of sentences constructed by the Chatbot <NUM> during the exemplary conversation <NUM> with the pilot <NUM> are illustrated in <FIG>. The chatbot <NUM> transmits the one or more sentences to the TTS converter <NUM>.

In block <NUM>, converting the text in the sentences to speech is performed by the TTS converter <NUM>. In block <NUM>, transmitting the speech to the pilot <NUM> is performed by the TTS converter <NUM> using the speaker <NUM>. In some examples, as previously described, the speaker <NUM> is mounted in an audio panel <NUM> in the flight deck <NUM>, a headset worn by the pilot <NUM>, or both. In block <NUM>, the conversation <NUM> with the pilot <NUM> ends or the method <NUM> returns to block <NUM> to continue the conversation <NUM> and receive additional speech from the pilot <NUM>. Referring also to <FIG> illustrates an example of the conversation <NUM> continuing between the pilot <NUM> and a particular aircraft system <NUM> using the chatbot <NUM>, system directed conversation module <NUM> and command encoder/decoder <NUM>.

In some example, in block <NUM> in <FIG>, the text or sentences from the chatbot <NUM> are also presented on a display, e.g., cockpit display <NUM>, the display of the portable electronic device <NUM>, or both. In block <NUM>, the conversation <NUM> ends or the method <NUM> returns to block <NUM> for receiving additional text entered by the pilot <NUM> in the display.

<FIG> is a flow chart of an example of a method <NUM> of operation of a dynamic widget/form generator <NUM> in accordance with an example of the present disclosure. In block <NUM>, the method <NUM> includes receiving the tokens <NUM>, <NUM> from the tokenizer <NUM>, or a controller-pilot data link communications (CPDLC)/Aircraft Communication Addressing and Reporting System (ACARS) text analyzer <NUM> that receives text <NUM>. The method <NUM> also includes converting text <NUM> to one or more forms, widgets or both. The text <NUM> is text tokens <NUM> or communication (COMM) tokens received from an Aircraft Communications Addressing and Reporting System (ACARS) and/or a Data Link/Controller-Pilot Data Link Communications (DL/CPDLC) text analyzer <NUM>, or TTS tokens <NUM> received from a system directed conversation module <NUM> or dynamic conversational graph generator <NUM> via a tokenizer <NUM>. The token or tokens are converted to graphical opcode/operand/formatted instructions by the dynamic widget/form generator <NUM> using a keyword/phrase to dynamic forms/widgets database <NUM>. Referring also to <FIG> and <FIG>, <FIG> and <FIG> are examples of chatbot windows 902a-902d and a pilot interaction window 904a-904d generated by the dynamic widget/form generator <NUM> during a conversation in accordance with an example of the present disclosure. <FIG> and <FIG> also illustrate tables 906a-906d including keywords 908a-908d and corresponding widget definition files 910a-910d. The tables 906a-906d are stored in the keyword/phrase to dynamic forms/widgets database <NUM> for use by the dynamic widget/form generator <NUM> to generate dynamic forms, widgets, or both as illustrated in the examples in chatbot widows <NUM>-902d and pilot interaction windows 904a-904d.

In block <NUM>, the method <NUM> includes creating a panel <NUM> and positioning widgets <NUM> within the panel <NUM> for pilot interaction window 904a-904d. In block <NUM>, the method <NUM> includes positioning the panel <NUM> in pilot interaction window 904a-904d in alignment to the chatbot response in the chatbot window 902a-902d. In block <NUM>, the method <NUM> includes processing the graphics and transmitting the graphics to the display computer <NUM> for presentation on the cockpit display <NUM>, and/or transmitting the graphics to the aircraft interface device <NUM> for presentation on the portable electronic device <NUM>.

In block <NUM>, the method <NUM> includes receiving a response or input from the pilot <NUM>. As previously described, the response or input is in the form of speech received by the system <NUM> from the pilot <NUM> and/or the pilot <NUM> interacting with a touchscreen <NUM> of the cockpit display <NUM> or touchscreen <NUM> of the portable electronic device <NUM>. In block <NUM>, the method <NUM> returns to the chatbot <NUM> and ASR device <NUM> to receive further responses or inputs from the pilot <NUM>.

<FIG> is a flow chart of an example of a method <NUM> for generating a historical/trained conversation database <NUM> in accordance with an example of the present disclosure. In block <NUM>, the method <NUM> includes receiving conversational text, e.g., text is received from a pilot or other user. In block <NUM>, the method <NUM> includes converting the text into tokens by the tokenizer.

In block <NUM>, the method <NUM> includes creating a bag of words. Creating a bag of words is a process of representing text data when modeling text with a machine learning algorithm. The bag of words includes a vocabulary of known words, e.g., approach, phase, weather, destination, airport, radio, frequency, tuning, etc..

In block <NUM>, the method <NUM> includes performing feature characterization using document sources <NUM>. Each word or phrase is referred to as a gram. Creating a vocabulary of two-words (n=<NUM>) pairs is, in turn, referred to as a bigram model, e.g., approach briefing, flight phase, approach checklist, destination airport, weather destination, etc. Examples of document sources <NUM> for performing feature characterization include but are not limited to an aircraft system/subsystem list <NUM>, an airport directory <NUM>, an airplane flight manual (AFM) <NUM>, a quick reference handbook (QRH) <NUM>, dispatch files <NUM>, different checklists <NUM>, and aeronautical charts <NUM>. Examples of the aircraft system/subsystem list <NUM> include are not limited to displays, a flight control system (FCS), a flight management system (FMS), maintenance system, etc..

In block <NUM>, the method <NUM> includes performing word-to-vector (Word2Vec) conversions. Word associations are made from a large corpus of words. Word2Vec conversion represents each distinct word with a particular list of numbers called a vector. In Word2Vec conversion, each word or phrase originating from document sources <NUM> and the inter-relationship between the words or phrases characterized in block <NUM> are numerically represented as an array of numbers.

In block <NUM>, the method <NUM> includes performing topic modeling. Topic modeling facilitates in the discovery of semantic structures in a text body by comparing the distance between the vectors in the word vector space to identify the topics. Topic modeling also includes extracting main topics from a dataset. Examples of semantic structures include but are not limited to weather, navigation, aircraft state, standard operating procedures (SOPs), etc..

In block <NUM>, the method <NUM> includes clustering or grouping words or phrases into different clusters <NUM>-<NUM>. Words or phrases that are related are grouped into the same cluster. Each clusters is then associated to a topic, e.g., similarity measurements are used to cluster related words, phrases or documents together. Examples of clusters include but are not limited to AFM cluster <NUM>, QRH cluster <NUM>, checklists cluster <NUM>, etc. For example, if conversational text is "Hey bot, can you get me the approach checklist. " There is a high probability, e.g., about <NUM>% chance to hit the checklists cluster <NUM>.

In block <NUM>, the method <NUM> includes mapping to an avionic application owner in response to a keyword or keywords in the conversation text. In the example where the keywords are "approach checklist," the conversation is mapped to the display system which is the avionic application owner for displaying the approach checklist.

In block <NUM>, the method <NUM> includes performing graph generation which builds the relationship with data elements within the cluster, between the clusters, and avionics application owners to necessary data elements in the form of a graph represented by a mesh comprising nodes and edges. This graph is stored and represented as a historical/trained conversation database <NUM>, which is field loadable.

<FIG> is a flow chart of an example of a method <NUM> for flight deck communications in accordance with an example of the present disclosure. In some examples, the method <NUM> is embodied in and performed by the system <NUM> in <FIG> and <FIG>. In some examples, the set of functions <NUM> performed by the dynamic conversational graph generator <NUM>, the set of functions <NUM> performed by the system directed conversation module <NUM>, the set of functions <NUM> performed by the dynamic widget/form generator <NUM>, and functions performed by other components of the system <NUM> as described herein are also included in the method <NUM>.

In block <NUM>, the method <NUM> includes performing, by a chatbot, a conversation with a pilot. The conversation includes speech communications, visual communications using a display, or both.

In block <NUM>, the method <NUM> includes determining, by a dynamic conversational graph generator, a flight operational procedure from the conversation with the pilot. In block <NUM>, the method <NUM> includes providing, by the dynamic conversational graph generator, information associated with the flight operational procedure to the chatbot for communicating to the pilot. In block <NUM>, the method <NUM> includes responding, by the dynamic conversational graph generator, to any requests received by the chatbot during the conversation with the pilot.

In block <NUM>, the method <NUM> further includes handing-off communications to a system directed conversation module by the dynamic conversational graph generator in response to the flight operational procedure being associated with a particular aircraft system or avionics application owner. In block <NUM>, the method <NUM> includes directing the conversation with the pilot to a particular aircraft system, e.g., one of aircraft systems 136a-136n in <FIG> and <FIG>.

In block <NUM>, the method <NUM> includes providing, by the system directed conversation module or the particular aircraft system, the information associated with the flight operational procedure to the chatbot for communication to the pilot.

In block <NUM>, the method <NUM> includes generating a particular form, widget or both associated with the flight operational procedure for presentation in a window on a display. The particular form, widget or both are configured for interaction with the pilot. Pilot interaction with the particular form, widget or both includes at least one of interaction by conversing with the chatbot or interaction by the pilot touching a feature of the particular form, widget, or both in a display or touchscreen.

In block <NUM>, the method <NUM> includes presenting the form, widget or both in a window on the display for interaction with the pilot. In accordance with the example in <FIG> and <FIG>, the display includes the cockpit display <NUM>, display of the portable electronic device <NUM>, or both. The pilot interaction includes the pilot touching a touchscreen <NUM> of a cockpit display <NUM>, the touchscreen <NUM> of a portable electronic device <NUM>, or both. In some examples, the pilot interaction also includes speech communication with the form, widget or both using the audio panel <NUM>, microphone <NUM>, speaker <NUM>, ASR device <NUM>, TTS converter <NUM>, chatbot <NUM> and tokenizer <NUM> in <FIG> and <FIG>.

<FIG> is an example of a system <NUM> for flight deck communications in accordance with an example of the present disclosure. In some examples, the system <NUM> in <FIG> and <FIG> is embodied in one or more systems similar to or the same as the system <NUM>. In some examples, at least some of the components of the system <NUM> in <FIG> and <FIG>, e.g., the chatbot <NUM>, the tokenizer <NUM>, the dynamic conversational graph generator <NUM>, the system directed conversation module <NUM>, the command encoder/decoder <NUM>, one or more of the aircraft systems <NUM>, the dynamic widget/form generator <NUM>, the DL/CPDLC/ACARS text analyzer <NUM>, the aircraft interface device <NUM>, and the display computer <NUM> are embodied in one or more systems similar to or the same as the system <NUM>. In some examples, at least some of the methods <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> are embodied in and performed by one or more systems similar to or the same as the system <NUM>.

The system <NUM> includes a processing circuit <NUM> and a memory <NUM> associated with the processing circuit <NUM>. The memory <NUM> includes computer-readable program instructions <NUM> that, when executed by the processing circuit <NUM> causes the processing circuit <NUM> to perform a set of functions <NUM>. In some examples, the set of functions <NUM> includes the set of functions <NUM> performable by the dynamic conversational graph generator <NUM>, the set of functions <NUM> performable by the system directed conversation module <NUM>, and/or the set of functions <NUM> performable by the dynamic widget/form generator <NUM>. The sets of functions <NUM>, <NUM> and <NUM> are embodied on one or more systems that are similar to or the same as the system <NUM>. In some examples, the set of functions <NUM> includes at least some of the methods <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> that are embodied on and performed by one or more systems that are similar to or the same as the system <NUM>.

In some examples, the system <NUM> also includes one or more input/output devices <NUM>. The input/output devices <NUM> include separate input devices, output device or combination input and output devices. Examples of the input/output devices <NUM> include but are not limited to one or more display devices, a touchscreen, microphone, speaker, keyboard or keypad, pointing device, and a device configured to read or access computer-readable program instructions on a computer program product <NUM> similar to that described herein. Any of the methods <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and/or <NUM> can be embodied on the computer program product <NUM>, read by the input/output device <NUM> and stored in the memory <NUM>.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various examples of the present disclosure.

Claim 1:
An interface system (<NUM>) for flight deck communications, the interface system (<NUM>) comprising:
a chatbot (<NUM>) configured to perform a conversation (<NUM>) with a pilot (<NUM>), wherein the conversation (<NUM>) comprises speech communications, visual communications using a display (<NUM>), or both; and
a dynamic conversational graph generator (<NUM>) configured to perform a set of functions (<NUM>) comprising:
determining (<NUM>) a flight operational procedure from the conversation (<NUM>) with the pilot (<NUM>);
providing (<NUM>) information associated with the flight operational procedure to the chatbot (<NUM>) for communicating to the pilot (<NUM>); and
responding (<NUM>) to any requests received from the pilot (<NUM>) by the chatbot (<NUM>) during the conversation (<NUM>) with the pilot (<NUM>),
the interface system (<NUM>) further comprising a tokenizer (<NUM>) configured to:
convert (<NUM>) text (<NUM>) received from the chatbot (<NUM>) to tokens (<NUM>, <NUM>) transmitted by the tokenizer (<NUM>); and
convert (<NUM>) tokens received by the tokenizer (<NUM>) to text (<NUM>) that is transmitted to the chatbot (<NUM>) to perform the conversation (<NUM>) with the pilot (<NUM>),
wherein the set of functions (<NUM>) performed by the dynamic conversational graph generator (<NUM>) further comprises:
detecting (<NUM>) a keyword (<NUM>) in the conversation (<NUM>) with the pilot (<NUM>) using the tokens (<NUM>) from the tokenizer (<NUM>), wherein the keyword (<NUM>) identifies a particular flight operational procedure;
searching (<NUM>) a plurality of nodes (<NUM>-<NUM>) of a dynamic conversational graph (<NUM>) to identify a node (<NUM>) corresponding to the keyword (<NUM>) in the conversation (<NUM>) with the pilot (<NUM>), wherein each node (<NUM>-<NUM>) corresponds to a different flight operational procedure;
handing-off (<NUM>) communications to a system directed conversation module (<NUM>) in response to the node (<NUM>) corresponding to the keyword (<NUM>) having an owner, wherein the owner is a particular aircraft system (<NUM>) associated with the flight operational procedure; and
determining (<NUM>) an identification of any neighboring nodes (704a-704d) in the dynamic conversational graph (<NUM>) to the node (<NUM>) corresponding to the keyword (<NUM>) in response to the node (<NUM>) not having an owner, wherein the identification of any neighboring nodes (704a-704d) are communicated to the pilot (<NUM>) by the chatbot (<NUM>) in the conversation (<NUM>).