EP4210025A1 - Systeme und verfahren zur verbesserung des datenverbindungsbetriebs - Google Patents

Systeme und verfahren zur verbesserung des datenverbindungsbetriebs Download PDF

Info

Publication number
EP4210025A1
EP4210025A1 EP22215484.1A EP22215484A EP4210025A1 EP 4210025 A1 EP4210025 A1 EP 4210025A1 EP 22215484 A EP22215484 A EP 22215484A EP 4210025 A1 EP4210025 A1 EP 4210025A1
Authority
EP
European Patent Office
Prior art keywords
expected response
response time
aircraft
cpdlc message
cpdlc
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP22215484.1A
Other languages
English (en)
French (fr)
Inventor
Anil Kumar Songa
Sadguni Venkataswamy
Siddaray Medegar
Suresh Bazawada
Candace GUNNING
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Honeywell International Inc
Original Assignee
Honeywell International Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US17/655,915 external-priority patent/US20230222923A1/en
Application filed by Honeywell International Inc filed Critical Honeywell International Inc
Publication of EP4210025A1 publication Critical patent/EP4210025A1/de
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
    • G08G5/0004—Transmission of traffic-related information to or from an aircraft
    • G08G5/0013—Transmission of traffic-related information to or from an aircraft with a ground station
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
    • G08G5/0017—Arrangements for implementing traffic-related aircraft activities, e.g. arrangements for generating, displaying, acquiring or managing traffic information
    • G08G5/0021—Arrangements for implementing traffic-related aircraft activities, e.g. arrangements for generating, displaying, acquiring or managing traffic information located in the aircraft

Definitions

  • Embodiments of the subject matter described herein relate generally to datalink communication between a flight operation center (FOC) such as an air traffic control (ATC) center and flight crew in an aerial vehicle. More particularly, embodiments of the subject matter relate to systems and methods for enhancing datalink communication operation.
  • FOC flight operation center
  • ATC air traffic control
  • CPDLC Controller Pilot Datalink Communication
  • ATC Air Traffic Management authorities
  • authorities are increasingly concerned with data communication performance, and many regions monitor communication performance.
  • Transactions times for CPDLC exchanges are recorded for many aircraft. In some instances, aircraft that exhibit poor performance may have various approvals revoked.
  • Different airspaces require different levels of communication performance, for example, due to differing separation standards and differing densities of air traffic.
  • the oceanic environment is different from the domestic environment. High altitude airspace is different from lower altitude airspace.
  • An acceptable transaction time in one environment may be unacceptable in another.
  • the complexity of a particular CPDLC uplink may require more cognitive workload from the flight crew (e.g., executing an altitude change is less complex than executing a route modification).
  • authorities from different regions may define different expected pilot response times. Further, authorities within a region may define different expected response times for different CPDLC uplink elements.
  • flight crews are trained to respond to CPDLC uplinks as quickly as they can, they are likely unaware of the expected response time for the current uplink they are working on. Because the expected response may differ based on the airspace in which an aircraft flies, it is more likely that a flight crew may not know the expected response time for an uplink communication.
  • a flight deck system in an aircraft for enhancing controller pilot datalink communication (CPDLC) operation includes a controller configured to: receive a CPDLC message having a CPDLC message type from a flight operation center (FOC) having an FOC name; retrieve an expected response time for the CPDLC message from an expected response time database containing expected response times for a plurality of CPDLC message types for FOCs; generate a timer function that causes the display of a timer (e.g., countdown timer) on an aircraft display device that has a set duration based on the expected response time; signal the aircraft display device to display the timer; monitor communications from flight crew for a response to the CPDLC message; and signal the aircraft display device to end the display of the timer when a communication has been detected within the set duration that is responsive to the CPDLC message.
  • a timer e.g., countdown timer
  • a method in a flight deck system in an aircraft for enhancing controller pilot datalink communication (CPDLC) operation includes: receiving a CPDLC message having a CPDLC message type from a flight operation center (FOC) having an FOC name; retrieving an expected response time for the CPDLC message from an expected response time database containing expected response times for a plurality of CPDLC message types for FOCs; generating a timer function that causes the display of a timer (e.g., countdown timer) on an aircraft display device that has a set duration based on the expected response time; signaling the aircraft display device to display the timer; monitoring communications from flight crew for a response to the CPDLC message; and signaling the aircraft display device to end the display of the timer when a communication has been detected within the set duration that is responsive to the CPDLC message.
  • a timer e.g., countdown timer
  • a non-transitory computer readable medium encoded with programming instructions configurable to cause a controller in a flight deck system in an aircraft to perform a method for enhancing controller pilot datalink communication (CPDLC) operation includes: receiving a CPDLC message having a CPDLC message type from a flight operation center (FOC) having an FOC name; retrieving an expected response time for the CPDLC message from an expected response time database containing expected response times for a plurality of CPDLC message types for FOCs; generating a timer function that causes the display of a timer (e.g., countdown timer) on an aircraft display device that has a set duration based on the expected response time; signaling the aircraft display device to display the timer; monitoring communications from flight crew for a response to the CPDLC message; and signaling the aircraft display device to end the display of the timer when a communication has been detected within the set duration that is responsive to the CPDLC message.
  • FOC flight operation center
  • module refers to any hardware, software, firmware, electronic control component, processing logic, and/or processor device, individually or in any combination, including without limitation: application specific integrated circuit (ASIC), a field-programmable gate-array (FPGA), an electronic circuit, a processor (shared, dedicated, or group) and memory that executes one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.
  • ASIC application specific integrated circuit
  • FPGA field-programmable gate-array
  • processor shared, dedicated, or group
  • memory executes one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.
  • Embodiments of the present disclosure may be described herein in terms of functional and/or logical components and various processing steps. It should be appreciated that such functional and/or logical components may be realized by any number of hardware, software, and/or firmware components configured to perform the specified functions. For example, an embodiment of the present disclosure may employ various integrated circuit components, e.g., memory elements, digital signal processing elements, logic elements, look-up tables, or the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. In addition, those skilled in the art will appreciate that embodiments of the present disclosure may be practiced in conjunction with any number of systems, and that the systems described herein is merely exemplary embodiments of the present disclosure.
  • Different airspaces require different levels of communication performance, for example, due to differing separation standards and differing densities of air traffic.
  • the oceanic environment is different from the domestic environment. High altitude airspace is different from lower altitude airspace.
  • An acceptable transaction time in one environment may be unacceptable in another.
  • the complexity of a particular CPDLC uplink may require more cognitive workload from the flight crew (e.g., executing an altitude change is less complex than executing a route modification).
  • authorities from different regions may define different expected pilot response times. Further, authorities within a region may define different expected response times for different CPDLC uplink elements.
  • the subject matter described herein discloses apparatus, systems, techniques, and articles for providing a separately loadable Expected Response Time database that can specify various expected response times for a datalink message (e.g., a CPDLC uplink).
  • the disclosed apparatus, systems, techniques, and articles may specify various expected response times for a datalink message based on two inputs - flight operation center (FOC) names (e.g., KUSA (US domestic), EGGX (Shanwick oceanic), CZEG (Edmonton domestic)) and an uplink element numbers (e.g., UM19-CLIMB TO [altitude], UM79-CLEARED TO [position] VIA ROUTE CLEARANCE).
  • FOC flight operation center
  • the subject matter described herein further discloses apparatus, systems, techniques, and articles for providing a cockpit timer display that provides a timer (e.g., countdown timer) specific to a current open datalink message.
  • the disclosed apparatus, systems, techniques, and articles may retrieve an expected response time value for the timer from the Expected Response Time database, based on the current active FOC and the current uplink element number.
  • the disclosed apparatus, systems, techniques, and articles may locate a cockpit timer display in the form of a timer next to an existing forward display Alert that indicates an open CPDLC uplink exists.
  • the disclosed apparatus, systems, techniques, and articles may provide a cockpit timer display in the form of a timer displayed on an existing ATC UPLINK page (e.g., on an MCDU or graphical page, depending on the platform).
  • the cockpit timer display provided by the disclosed apparatus, systems, techniques, and articles may display a message such as text indicating ⁇ Respond ASAP' when the previously displayed timer has expired and the flight crew had not yet responded to the uplink.
  • FIG. 1 is a block diagram depicting an example flight environment 100 such as one around a busy aerodrome.
  • the example environment 100 includes a plurality of aerial vehicles (ownship aircraft 102 and traffic aircraft 104, 106 in this example), but could include a variety of types of aerial vehicles such as helicopters, UAVs (unmanned aerial vehicles), and others.
  • the example environment 100 also includes a plurality of flight operation centers (FOCs) (e.g., air traffic control towers 108, 110) containing control personnel such as air traffic controllers (ATC) for directing ground and air traffic in the vicinity of the aerodrome.
  • FOCs flight operation centers
  • ATC air traffic controllers
  • the example ownship aircraft 102 includes avionics equipment 112 that receives ongoing communications between the aerial vehicles (e.g., 102, 104, 106) and ATC (e.g., via towers 108, 110) using communication equipment 114.
  • the avionics equipment 112 further includes a datalink system 116 that receives datalink communication, such as CPDLC communication, from the communication equipment 114.
  • the example datalink system 116 for datalink communications directed to the ownship, decodes the datalink communications and retrieves message content including an instruction type from the messages and an FOC name.
  • the example datalink system 116 accesses an Expected Response Time database that contains expected response times for a plurality of CPDLC message types for one or more air traffic control centers, generates a timer function that causes the display of a timer 120 (e.g., countdown timer) on an aircraft display device 118 that has a set duration based on the expected response time, and signals the aircraft display device 118 to display the countdown timer 120.
  • the example datalink system 116 further monitors communications from flight crew for a response to CPDLC messages and signals the aircraft display device 118 to end the display of the countdown timer 120 when a communication has been detected within the set duration that is responsive to the CPDLC message.
  • the aircraft display device 118 may be one of many types of graphical display units onboard an aircraft such as a navigation display, a PFD (primary flight display), a PED (personal electronic device), an EFB (electronic flight bag), HUD (heads up display), HDD (heads down display), and others.
  • a navigation display a PFD (primary flight display), a PED (personal electronic device), an EFB (electronic flight bag), HUD (heads up display), HDD (heads down display), and others.
  • FIG. 2 is a block diagram depicting example avionics equipment 200.
  • the example avionics equipment 200 includes a datalink system 202, and expected response time database 204, an aircraft display device 206.
  • the example datalink system 202 includes an analysis module 212, an output module 214, and a communication monitoring module 216.
  • Each of the datalink system 202, the analysis module 212, the output module 214, and the communication monitoring module 216 is implemented by a processing component such as a controller (e.g., the same or separate controllers).
  • the processing component includes at least one processor and a computer-readable storage device or media encoded with programming instructions for configuring the processing component.
  • the processor may be any custom-made or commercially available processor, a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), an auxiliary processor among several processors associated with the processing component, a semiconductor-based microprocessor (in the form of a microchip or chip set), any combination thereof, or generally any device for executing instructions.
  • the computer readable storage device or media may include volatile and nonvolatile storage in read-only memory (ROM), random-access memory (RAM), and keep-alive memory (KAM), for example.
  • KAM is a persistent or non-volatile memory that may be used to store various operating variables while the processor is powered down.
  • the computer-readable storage device or media may be implemented using any of a number of known memory devices such as PROMs (programmable read-only memory), EPROMs (electrically PROM), EEPROMs (electrically erasable PROM), flash memory, or any other electric, magnetic, optical, or combination memory devices capable of storing data, some of which represent executable programming instructions, used by the processing component.
  • the analysis module 212 is configured to receive an incoming datalink message 211, such as CPDLC message, from ownship communication equipment, decode the datalink message 211, determine an expected response time for the datalink message 211, and set a time limit for responding to the datalink message 211.
  • the time limit may be equal to the expected response time or some time less than the expected response time. There may be circumstances wherein the time limit may be greater than the expected response time by some predetermined amount. In each case, the time limit is based on the expected response time.
  • the example analysis module 212 is configured to retrieve message content including an instruction type of the datalink message 211 and an FOC name for the datalink message 211.
  • the example analysis module 212 uses the retrieved message content to access (e.g., query) the Expected Response Time database 204, which contains expected response times for a plurality of CPDLC message types for one or more FOCs, to obtain the expected response time for the flight crew to respond to the datalink message 211.
  • the example analysis module 212 can use the instruction type of the datalink message 211 and the FOC name associated with the datalink message 211 to identify the specific expected response time for the datalink message from the Expected Response Time database 204.
  • the example analysis module 212 may include a keyword spotter and sentence segmentor for deriving segmented text from the datalink message 211 and a semantic/intent/data analyzer for analyzing the segmented text.
  • the semantic/intent/data analyzer may be configured to analyze the segmented text to identify an instruction type for the datalink message 211 and an FOC name for the datalink message 211.
  • the example analysis module 212 may be configured to generate a query request for the expected response time database that includes the FOC name (e.g., for the FOC from which the CPDLC message originated or for the geographical area in which the aircraft is located) and an uplink element number that corresponds to the CPDLC message type of the CPDLC message.
  • the example analysis module 212 may be further configured to query the expected response time database 204, using the query request, for an expected response time for the received CPDLC message, and retrieve a query result from the expected response time database 204 that includes the expected response for the CPDLC message.
  • the example output module 214 is configured to generate a timer function for a graphical display indicator (e.g., a countdown timer) for display on the aircraft display device 206 that indicates how much time the flight crew has left to respond to the datalink message 211.
  • the example output module 214 is configured to set a time limit for display in the graphical display indicator that is equal to the time limit determined by the example analysis module 212.
  • FIG. 3A is a diagram of an example display page 300 on an aircraft display device (e.g., display device 206).
  • the example display page 300 displays information regarding a specific datalink message - 0410z ATC uplink.
  • the example display page 300 also displays a graphical display indicator 302 that is specific to a current open uplink and that includes both text that indicates the time left to respond to the datalink message (0410z ATC uplink) and a numeric timer (e.g., countdown timer) that indicates how much of the time limit is left to respond to the datalink message.
  • a numeric timer e.g., countdown timer
  • FIG. 3B is a diagram of an example display page 320 on an aircraft display device (e.g., display device 206).
  • the example display page 320 displays aircraft status information 322 regarding aircraft systems during flight. Included in the aircraft status information 322 on the example display page 320 is a graphical display indicator 324 that is specific to a current open uplink and that includes text that indicates that the graphical display indicator 324 relates to the remaining response time for an ATC Message and a numeric timer (e.g., countdown timer) that indicates how much of the time limit is left to respond to the datalink message.
  • a numeric timer e.g., countdown timer
  • the example output module 214 may be further configured to generate a Respond ASAP indication that indicates that a communication has not been detected within the set duration that is responsive to the datalink message.
  • the example output module 214 may be further configured to signal the aircraft display device to display the Respond ASAP indication when a communication has not been detected within the set duration that is responsive to the datalink message.
  • the example output module 214 may be further configured to signal the aircraft display device to end the display of the Respond ASAP indication when a communication has been detected that is responsive to the datalink message.
  • the Respond ASAP indication may include the words "Respond ASAP" or may include other words, phrases, images, etc. that indicate to the flight crew that the timer has expired and that a response is still needed to the datalink message.
  • the example communication monitoring module 216 is configured to monitor onboard systems for communications from flight crew, determine when a communication is responsive to the datalink message 211, and signal the output module 214 when the flight crew has responded to the datalink message 211.
  • the output module 214 may terminate a corresponding graphical display indicator (e.g., graphical display indicator 302, graphical display indicator 324, or Respond ASAP indication) and signal the aircraft display device 206 to end the display of the corresponding graphical display indicator.
  • a graphical display indicator e.g., graphical display indicator 302, graphical display indicator 324, or Respond ASAP indication
  • the example expected response time database 204 may be part of the datalink system 202, located in other equipment onboard the ownship, or may be resident on a cloud-based system.
  • the expected response time database 204 may be preloaded onto the aircraft before flight or downloaded onto the aircraft during flight.
  • the example expected response time database 204 may be searchable via input of an FOC name and an uplink element number for retrieving an expected response time for a specific response time for a specific FOC.
  • the aircraft display device 206 may be one of many types of graphical display units onboard an aircraft such as a navigation display, a PFD (primary flight display), a PED (personal electronic device), an EFB (electronic flight bag), HUD (heads up display), HDD (heads down display), and others.
  • a navigation display a PFD (primary flight display), a PED (personal electronic device), an EFB (electronic flight bag), HUD (heads up display), HDD (heads down display), and others.
  • FIG. 4 is a process flow chart depicting an example process 400 in an example datalink system (e.g., datalink system 202).
  • the order of operation within the process 400 is not limited to the sequential execution as illustrated in the figure but may be performed in one or more varying orders as applicable and in accordance with the present disclosure.
  • the example process 400 includes receiving a datalink message (e.g., CPDLC) having a message type from a FOC (flight operation center such as an ATC center) having an FOC name (operation 402) and retrieving an expected response time for the datalink message from an expected response time database containing expected response times for a plurality of datalink message types for one or more FOCs (operation 404).
  • a datalink message e.g., CPDLC
  • FOC light operation center such as an ATC center
  • the expected response time database may be preloaded onto the aircraft before flight or downloaded onto the aircraft during flight.
  • the expected response time database may be searchable via input of an FOC name and an uplink element number for retrieving an expected response time for a specific response time for a specific FOC.
  • Retrieving an expected response time for the datalink message from the expected response time database may include: generating a query request for the expected response time database that includes the FOC name for the FOC from which the datalink message originated and an uplink element number that corresponds to the datalink message type of the datalink message; querying the expected response time database, using the query request, for an expected response time for the received datalink message; and retrieving a query result from the expected response time database that includes the expected response for the datalink message.
  • the example process 400 includes, generating a timer function that causes the display of a timer on an aircraft display device that has a set duration based on the expected response time (operation 406) and signaling the aircraft display device to display the timer (operation 408).
  • the set duration of the timer may be equal to the expected response time retrieved from the expected response time database or some predetermined offset (greater than or less than) the retrieved expected response time.
  • the example process 400 includes monitoring communications from flight crew for a response to the datalink message (operation 410) and signaling the aircraft display device to end the display of the timer when a communication has been detected within the set duration that is responsive to the datalink message (operation 412).
  • the example process 400 may further include signaling the aircraft display device to display a Respond ASAP indication when a communication has not been detected within the set duration that is responsive to the datalink message.
  • the example process 400 may further include signaling the aircraft display device to end the display of the Respond ASAP indication when a communication has been detected that is responsive to the datalink message.
  • the Respond ASAP indication may include the words "Respond ASAP" or may include other words, phrases, images, etc. that indicate to the flight crew that the timer has expired and that a response is still needed to the datalink message.
  • the subject matter described herein discloses apparatus, systems, techniques, and articles for advising flight crew in an aerial vehicle when to respond to a datalink message, such as a controller pilot datalink communication (CPDLC).
  • a datalink message such as a controller pilot datalink communication (CPDLC).
  • a flight deck system in an aircraft for enhancing controller pilot datalink communication (CPDLC) operation is provided.
  • the flight deck system comprises a controller configured to: receive a CPDLC message having a CPDLC message type from a flight operation center (FOC) having an FOC name; retrieve an expected response time for the CPDLC message from an expected response time database containing expected response times for a plurality of CPDLC message types for one or more FOCs; generate a timer function that causes the display of a timer (e.g., countdown timer) on an aircraft display device that has a set duration based on the expected response time; signal the aircraft display device to display the timer; monitor communications from flight crew for a response to the CPDLC message; and signal the aircraft display device to end the display of the timer when a communication has been detected within the set duration that is responsive to the CPDLC message.
  • a timer e.g., countdown timer
  • the controller may be further configured to signal the aircraft display device to display a Respond ASAP indication when a communication has not been detected within the set duration that is responsive to the CPDLC message.
  • the controller may be further configured to signal the aircraft display device to end the display of the Respond ASAP indication when a communication has been detected that is responsive to the CPDLC message.
  • the expected response time database may be preloaded onto the aircraft before flight or downloaded onto the aircraft during flight.
  • the expected response time database may be searchable via input of an FOC name and an uplink element number for retrieving an expected response time for a specific response time for a specific FOC.
  • the controller may be further configured to: generate a query request for the expected response time database that includes the FOC name for the FOC from which the CPDLC message originated and an uplink element number that corresponds to the CPDLC message type of the CPDLC message; query the expected response time database, using the query request, for an expected response time for the received CPDLC message; and retrieve a query result from the expected response time database that includes the expected response for the CPDLC message.
  • the set duration of the timer may be equal to the expected response time retrieved from the expected response time database.
  • a method in a flight deck system in an aircraft for enhancing controller pilot datalink communication (CPDLC) operation comprises: receiving a CPDLC message having a CPDLC message type from a flight operation center (FOC) having an FOC name; retrieving an expected response time for the CPDLC message from an expected response time database containing expected response times for a plurality of CPDLC message types for FOCs; generating a timer function that causes the display of a timer (e.g., countdown timer) on an aircraft display device that has a set duration based on the expected response time; signaling the aircraft display device to display the timer; monitoring communications from flight crew for a response to the CPDLC message; and signaling the aircraft display device to end the display of the timer when a communication has been detected within the set duration that is responsive to the CPDLC message.
  • a timer e.g., countdown timer
  • the method may further comprise signaling the aircraft display device to display a Respond ASAP indication when a communication has not been detected within the set duration that is responsive to the CPDLC message.
  • the method may further comprise signaling the aircraft display device to end the display of the Respond ASAP indication when a communication has been detected that is responsive to the CPDLC message.
  • the expected response time database may be preloaded onto the aircraft before flight or downloaded onto the aircraft during flight.
  • the expected response time database may be searchable via input of an FOC name and an uplink element number for retrieving an expected response time for a specific response time for a specific FOC.
  • Retrieving an expected response time for the CPDLC message from the expected response time database may comprise: generating a query request for the expected response time database that includes the FOC name for the FOC from which the CPDLC message originated and an uplink element number that corresponds to the CPDLC message type of the CPDLC message; querying the expected response time database, using the query request, for an expected response time for the received CPDLC message; and retrieving a query result from the expected response time database that includes the expected response for the CPDLC message.
  • the set duration of the timer may be equal to the expected response time retrieved from the expected response time database.
  • a non-transitory computer readable medium encoded with programming instructions configurable to cause a controller in a flight deck system in an aircraft to perform a method for enhancing controller pilot datalink communication (CPDLC) operation comprises: receiving a CPDLC message having a CPDLC message type from a flight operation center (FOC) having an FOC name; retrieving an expected response time for the CPDLC message from an expected response time database containing expected response times for a plurality of CPDLC message types for FOCs; generating a timer function that causes the display of a timer (e.g., countdown timer) on an aircraft display device that has a set duration based on the expected response time; signaling the aircraft display device to display the timer; monitoring communications from flight crew for a response to the CPDLC message; and signaling the aircraft display device to end the display of the timer when a communication has been detected within the set duration that is responsive to the CPDLC message.
  • FOC flight operation center
  • the method may further comprise signaling the aircraft display device to display a Respond ASAP indication when a communication has not been detected within the set duration that is responsive to the CPDLC message.
  • the method may further comprise signaling the aircraft display device to end the display of the Respond ASAP indication when a communication has been detected that is responsive to the CPDLC message.
  • the expected response time database may be searchable via input of an FOC name and an uplink element number for retrieving an expected response time for a specific response time for a specific FOC.
  • Retrieving an expected response time for the CPDLC message from the expected response time database may comprise: generating a query request for the expected response time database that includes the FOC name for the FOC from which the CPDLC message originated and an uplink element number that corresponds to the CPDLC message type of the CPDLC message; querying the expected response time database, using the query request, for an expected response time for the received CPDLC message; and retrieving a query result from the expected response time database that includes the expected response for the CPDLC message.
  • the set duration of the timer may be equal to the expected response time retrieved from the expected response time database.
  • a flight deck system in an aircraft for enhancing controller pilot datalink communication (CPDLC) operation comprises a controller configured to: access an expected response time database containing expected response times for a plurality of CPDLC message types for FOCs, wherein the expected response times are searchable via input of a flight operation center (FOC) name and an uplink element number, wherein the expected response time database is preloaded onto the aircraft before flight or downloaded onto the aircraft during flight; receive a CPDLC message having a CPDLC message type from an FOC having an FOC name; generate a query request for the expected response time database that includes the FOC name for the FOC from which the CPDLC message originated and an uplink element number that corresponds to the CPDLC message type of the CPDLC message; query the expected response time database, using the query request, for an expected response time for the received CPDLC message; retrieve a query result from the expected response time database that includes the expected response for the CPDLC message; generate a timer function that causes the display of
  • Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
  • an embodiment of a system or a component may employ various integrated circuit components, e.g., memory elements, digital signal processing elements, logic elements, look-up tables, or the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices.
  • integrated circuit components e.g., memory elements, digital signal processing elements, logic elements, look-up tables, or the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium.
  • the storage medium may be integral to the processor.
  • the processor and the storage medium may reside in an ASIC.
  • the ASIC may reside in a user terminal.
  • the processor and the storage medium may reside as discrete components in a user terminal.

Landscapes

  • Engineering & Computer Science (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Traffic Control Systems (AREA)
EP22215484.1A 2022-01-07 2022-12-21 Systeme und verfahren zur verbesserung des datenverbindungsbetriebs Pending EP4210025A1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202211000999 2022-01-07
US17/655,915 US20230222923A1 (en) 2022-01-07 2022-03-22 Systems and methods for enhancing datalink operation

Publications (1)

Publication Number Publication Date
EP4210025A1 true EP4210025A1 (de) 2023-07-12

Family

ID=84569425

Family Applications (1)

Application Number Title Priority Date Filing Date
EP22215484.1A Pending EP4210025A1 (de) 2022-01-07 2022-12-21 Systeme und verfahren zur verbesserung des datenverbindungsbetriebs

Country Status (1)

Country Link
EP (1) EP4210025A1 (de)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1318492A2 (de) * 2001-12-05 2003-06-11 The Boeing Company System zur Überwachung des Abstands zum Boden und zur Alarmierung des Piloten mit Datenübertragung (compass)
US20080163093A1 (en) * 2005-02-18 2008-07-03 Tales Onboard Device for Managing Data Exchanged by an Aircraft with the Ground or Other Aircraft
US20100277347A1 (en) * 2009-05-04 2010-11-04 Honeywell International Inc. Aircraft uplink message response prompt
US20130141254A1 (en) * 2011-12-06 2013-06-06 Honeywell International Inc. Systems and methods for an active prompt for timed response controller pilot data link communication (cpdlc) messages
US20170039858A1 (en) * 2015-08-06 2017-02-09 Honeywell International Inc. Communication-based monitoring of compliance with aviation regulations and operating procedures

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1318492A2 (de) * 2001-12-05 2003-06-11 The Boeing Company System zur Überwachung des Abstands zum Boden und zur Alarmierung des Piloten mit Datenübertragung (compass)
US20080163093A1 (en) * 2005-02-18 2008-07-03 Tales Onboard Device for Managing Data Exchanged by an Aircraft with the Ground or Other Aircraft
US20100277347A1 (en) * 2009-05-04 2010-11-04 Honeywell International Inc. Aircraft uplink message response prompt
US20130141254A1 (en) * 2011-12-06 2013-06-06 Honeywell International Inc. Systems and methods for an active prompt for timed response controller pilot data link communication (cpdlc) messages
US20170039858A1 (en) * 2015-08-06 2017-02-09 Honeywell International Inc. Communication-based monitoring of compliance with aviation regulations and operating procedures

Similar Documents

Publication Publication Date Title
EP3128500B1 (de) Kommunikationsbasierte überwachung der einhaltung von luftfahrtvorschriften und betriebsverfahren
US9098996B2 (en) Methods and systems for integrating runway status and layout
US8244452B2 (en) Systems and methods integrated air traffic control management
US10593214B2 (en) System and method for real-time classification of NOTAMs messages
CN107257995B (zh) 用于显示飞行器相关信息的方法和系统、用于产生所述信息的装置以及相关计算机程序产品
US10992372B2 (en) Methods and systems for assisting radio frequency selection
US20200380875A1 (en) Method and system for flight safety analytics display
US10946977B2 (en) Method and system for integrating offboard generated parameters into a flight management system
US10902732B2 (en) Method and system for monitoring execution of conditional air traffic control clearances for an aircraft
US10732788B1 (en) System and method for displaying and using ATIS information
EP4210025A1 (de) Systeme und verfahren zur verbesserung des datenverbindungsbetriebs
US20230222923A1 (en) Systems and methods for enhancing datalink operation
CN112133133A (zh) 通过受保护的数据链路提供地形和跑道警报服务的系统和方法
US10569898B2 (en) Method and system for generating an alert for an aircraft potentially exceeding speed limits in restricted airspace
US11636768B2 (en) System and method for predicting ownship clearance and timing by modelling controller pilot conversations
EP3937153A1 (de) System und verfahren zum aufbau einer verbindung zwischen einer flugzeugwarnmeldung und einer elektronischen kontrollliste auf einer off-board-vorrichtung
EP3486848A1 (de) Verfahren und system zur integrierung von offboard-generierten parametern in ein flugmanagement-system
US20230215279A1 (en) Systems and methods for identifying context for cockpit alerts
US11790785B2 (en) System and method of producing relative active flight voice tags on a graphical display unit
EP4210023A1 (de) Systeme und verfahren zur identifizierung von kontext für cockpitwarnungen
EP3882889A1 (de) Verfahren und systeme zur abfrage von parameterabruf
US11743226B2 (en) Communication system processing external clearance message functions
US20240143937A1 (en) Transcription systems and methods for challenging clearances
EP4276794A1 (de) Transkriptionssysteme und damit zusammenhängende ergänzungsverfahren
US20230368682A1 (en) Transcription systems and related supplementation methods

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20240105

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR