EP1435155A2 - Auswahl eines von mehreren netzwerken zur datenübertragung - Google Patents

Auswahl eines von mehreren netzwerken zur datenübertragung

Info

Publication number
EP1435155A2
EP1435155A2 EP02802550A EP02802550A EP1435155A2 EP 1435155 A2 EP1435155 A2 EP 1435155A2 EP 02802550 A EP02802550 A EP 02802550A EP 02802550 A EP02802550 A EP 02802550A EP 1435155 A2 EP1435155 A2 EP 1435155A2
Authority
EP
European Patent Office
Prior art keywords
message
messages
data link
military
civil
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.)
Ceased
Application number
EP02802550A
Other languages
English (en)
French (fr)
Inventor
James T. Sturdy
Curtis G. Cromwell
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
Application filed by Honeywell International Inc filed Critical Honeywell International Inc
Priority claimed from PCT/US2002/032331 external-priority patent/WO2003053013A2/en
Publication of EP1435155A2 publication Critical patent/EP1435155A2/de
Ceased legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]

Definitions

  • the invention relates to datalink communications for aircraft, spacecraft, surface vehicles, and ground-based communications infrastructures, and more particularly to a method and apparatus for an intelligent communications capability that enhances legacy military tactical datalink systems by creating an interface between disparate civil and military communications systems.
  • Each military tactical datalink radio is an independent system and was not designed with the idea of integrating with other radio systems.
  • an external communications management router for military tactical datalink radios had not been developed.
  • the military was focused on specific tactical radio point solutions rather than an integrated solution.
  • the military is in the process of addressing requirements in order to use civil airspace, and at the same time is developing and expanding tactical radios and datalink systems to use in the digital battlefield. Unfortunately, the
  • SmartBridge will interface with tactical datalink applications and service support applications used by the military and manage associated transport, network, link, and physical layers needed to interface with the military communications systems (JTIDS, MIDS, and MILSTAR), and other avionics devices and end systems. Additionally, SmartBridge will offer the military the capability to bridge between military and civil communications systems allowing messages to be routed transparently across all available systems. For example, a Link-16 message could be routed over a civil VHF radio system in the event that the Link-16 radio is failed or unavailable. Likewise, the Link-16 tactical radio could be used to route ATC messages in the event that civil radio [Satellite Date
  • SmartBridge function can provide interfaces between military and civil communications systems and bring previously non-connected networks together for enhanced interactions. Additionally, communications networks requiring interaction with data in other stove-piped networks can use SmartBridge to perform advanced data routing to these disparate networks.
  • Another objective of the present invention is to make it easier for the military to get real-time data when they want it and where they want it.
  • Another objective of the present invention is to provide a system to transmit and process a variety of different types of data link messages originating from or sent to disparate civil and military communication systems onboard an aircraft and ground vehicle as well as providing military interfaces to civil ground- based communications infrastructures.
  • a primary advantage of the present invention is to provide a system to manage the integration, configuration, and status of all available civil and military communications systems.
  • OSI Layers 250 are layered in accordance with the OSI Layers 250.
  • the OSI standard defines seven layers as application 251 , presentation (not shown), session (not shown), transport 254, network 255, link 256, and physical 257. Presentation and session layers are either not used or are incorporated by the software applications as required. External interfaces 258 through 295 are used by these software applications 100 through
  • Service support applications 110 represent software applications that provide services and/or support to tactical datalink applications 100 and the SmartBridge function 160.
  • SmartBridge 160 can send and receive AOC 150 messages using the JTIDS/MIDS datalink radio terminals 280 or the MILSTAR datalink radio terminals when they are available.
  • SmartBridge 160 uses the necessary decision processes 440 and message handling processes 470 to format AOC messages for transmission over the selected network path and to decode AOC messages received over each network path. Since the SmartBridge function 160 is implemented in both the vehicle equipment as well as the ground systems equipment, these decision processes 440 and message handling processes 470 ensure that each message is properly handled and distributed to the intended application(s).
  • the process used to handle AOC messages described in this example is the same process that will be used for the other applications (100 through 140).
  • A619 190 implements A619 protocols using ARINC 429 or Ethernet link 230 and physical 235 layers.
  • VDR 258 represents civil VDR equipment that applications 100 through
  • SDU, HFDR, MODE S 260 represents civil SDU equipment, HFDR equipment, or Mode S transponder equipment that applications 100 through 150 and end systems 265, 270, 275 or 290 communicate with.
  • CRITERIA 360 assesses message security constraints and updates SECURITY PROCESSING INSTRUCTIONS 365 with routing instructions. EVALUATE
  • SIZE/BANDWIDTH CRITERIA 380 assesses message size and bandwidth constraints and updates SIZE/BANDWIDTH PROCESSING
  • Section 3 390 illustrates the DATA COLLECTION AGENTS function as a series of processes 395, 405, 415, and 425. PROCESS AGENTS TO COLLECT
  • the decisions 445, 450, 455, 460 and 465 made in DECISION PROCESSES 440 use information saved in AVAILABLE NETWORKS & STATUS 315, ACP 335, PRIORITY PROCESSING INSTRUCTIONS 355, SECURITY PROCESSING INSTRUCTIONS 365, URGENCY PROCESSING INSTRUCTIONS 375, and SIZE/BANDWIDTH PROCESSING INSTRUCTIONS 385. These stored data items are used to select networks to be used for current requested message transactions.
  • TACNET SELECTED 445 determines availability of and criteria for using military tactical networks (examples are JTIDS, MIDS, MILSTAR, or others) using
  • A618 SELECTED 450 determines availability of and criteria for using various civil air-ground networks 258 and 260 of Fig.1 , in accordance with protocols defined by ARINC specification number 618 215 of Fig. 1.
  • A619 SELECTED 455 determines availability of and criteria for communicating with various civil end systems 265 and 270 of Fig.1 , in accordance with protocols defined by ARINC specification number 619 , 170, 190 of Fig.1.
  • A656 SELECTED 460 determines availability of and criteria for communicating with a flight management system using interfaces 265 or 270 of
  • Fig. 1 in accordance with protocols defined by ARINC specification number 656 175, 185 of Fig. 1.
  • ATN SELECTED 465 determines availability of and criteria for using various civil air-ground networks 258 and 260 of Fig. 1 in accordance with protocols defined by the ICAO ATN specification 195 through 210 of Fig. 1.
  • HANDLING PROCESSES 470 use information saved in stored data 325, 335, 400, 410, 420, and 430.
  • NETWORK FAULTS 325, ALERTS 430 and ACP 335 are used to automatically generate ad hoc messages reporting network faults, alerts and the overall communications performance capability.
  • DATA 400, TRENDS 410 and DECISION AIDES 420 are used to automatically generate ad hoc messages distributing this information to appropriate military agencies and/or organizations.
  • PROCESS MESSAGES OVER TACTICAL NETWORK 475 performs network management and message handling for available military tactical networks JTIDS/MIDS 280, MILSTAR 285 or others 295 of Fig.1.
  • PROCESS MESSAGES OVER A619 NETWORK 485 performs network management and message handling for end systems 265, 270, 275 and 290 of Fig. 1 , in accordance with protocols defined by ARINC specification number 619.
  • PROCESS MESSAGES OVER A656 NETWORK 490 performs network management and message handling for a flight management system in accordance with protocols defined by ARINC specification number 656.
  • SmartBridge capabilities are Network Configuration and Status 305,
  • Section 1 determining available network configuration and status 305 is illustrated in Fig.2a.
  • SmartBridge will receive datalink network status from both military and civil communications equipment in the form of digital data words.
  • SmartBridge will also receive datalink network configuration information from both military and civil communications equipment in the form of digital data words.
  • SmartBridge will use this data for building an integrated status of available communication devices along with their configuration and capabilities for use in intelligent routing that will reduce crew workload and increase the end- to-end message delivery success.
  • Health monitoring functions of SmartBridge will record and alert the crew of any faults detected from connected communications systems. Loss of connections will result in an alert to the crew along with an outgoing message over another available communication system informing the ground or other vehicles of the communications downgrade.
  • SmartBridge will also use this data to compute an ACP 335 indicator for the vehicle. With SmartBridge's understanding of the entire network configuration, it will be able to route outgoing messages over various networks using criteria built into message format or general downlink message conditions. Based on the network configuration, SmartBridge will differentiate between a secure and non- secure network and a military and non-military network, providing more robustness in message handling. SmartBridge will provide the conduit for uplink messages to military specific onboard applications 100, 110, 275 and 290 and civil applications 120, 130, 140, 150, 265 and 270 of Fig.1. This will allow datalink messages from ground-based communications infrastructures or other vehicles using the supported communications systems to be routed to supported applications (examples are a Link-16 message, secure ACARS message for military use, or a civil ATC clearance message).
  • Fig. 2a The process flow for section 2 or determining message routing criteria 340 is illustrated in Fig. 2a. SmartBridge will analyze routing criteria against datalink messages to determine proper message handling responses. Output of the criteria evaluation will be used to route messages to particular communications systems or other equipment on the vehicle or in the ground-based communications infrastructure. SmartBridge will evaluate various routing criteria associated with each message based upon construction of each message.
  • SmartBridge will execute routing operations to transmit messages to particular communications systems that can best achieve end results of getting messages to intended destinations, while at the same time meeting routing criteria requirements.
  • routing criteria include:
  • Priority 350 - SmartBridge will control message routing inside the system for all available networks. It will have the ability to prioritize messages scheduled for transmission. SmartBridge will differentiate message priority by definition of message requests and subsequently place messages ahead of or behind other messages to achieve desired operations. Prioritization will be established for each available network, as well as across all networks. Security 360 - SmartBridge will be able to format and route messages to networks that provide both secure and non-secure communications. Messages will contain data that identify whether or not messages should go over a secure datalink path.
  • Urgency 370 - SmartBridge will recognize urgency flags that are contained in messages. SmartBridge will recognize various levels of urgency and respond accordingly by routing messages over the most reliable datalink, moving messages ahead of other messages and adding formats to messages so receiving systems understand the level of urgency.
  • Size 380 - SmartBridge will recognize size of messages and route to the most efficient and cost-effective communications system. An example is that it is more cost-effective to transmit a large message over a VHF or HF link rather than a SATCOM link. Based on other routing criteria such as urgency, these large messages will be stored until a more cost-effective link is available and then transmitted at that time.
  • Bandwidth 380 Due to varying communications systems and varying transmission speeds, SmartBridge will route to particular systems based on bandwidth requirements that are contained in messages. Data will be included in messages to inform SmartBridge what bandwidth is acceptable to use for its routing decision making.
  • SmartBridge will execute software algorithms that process incoming and outgoing messages to identify selected information to automatically formulate message and distribution instructions.
  • Data collection agents will collect end system data from all available sources 395, analyze the data for trends 405, analyze any trends to determine decision aides 415, and generate automatic alerts 425.
  • equipment health data and mission data available from tactical datalinks and end systems will be collected.
  • SmartBridge uses this data to automatically generate ATC messages per ARINC specification number 623 and RTCA DO-219, and AOC messages in accordance with ARINC specification numbers 620 and 702A. This data will also be used to prepare military unique AOC messages for command and control operations as well as for maintenance organizations. Table 1 provides an example list of automatically generated messages.
  • SmartBridge provides specific destination system instructions based on routing criteria in the message and provides this information to the TACNET function 180.
  • A618 - SmartBridge will route messages to the A618 network layer 215 upon evaluation of message content against routing criteria. This is used to route messages over civil communications systems. Secure messages can also be routed to this layer for use with compatible secure ACARS communications systems. Depending on the message routing criteria, this civil datalink connection can be used for military messages created by the onboard military applications 100, 110, 275 and 290.
  • A619 - SmartBridge will route messages to other onboard end systems by evaluating message criteria and forwarding to the A619 network layer 170 or 190.
  • A656 - SmartBridge will route messages to the A656 network layer 175 or
  • ATN - SmartBridge interfaces with ATN applications to handle those message requests. SmartBridge will route any ATN type message from a military or civil ATN application to the required communications system.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
EP02802550A 2001-10-12 2002-10-10 Auswahl eines von mehreren netzwerken zur datenübertragung Ceased EP1435155A2 (de)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US32926101P 2001-10-12 2001-10-12
US329261P 2001-10-12
PCT/US2002/032331 WO2003053013A2 (en) 2001-10-12 2002-10-10 Selection of one among several networks for data transmissions

Publications (1)

Publication Number Publication Date
EP1435155A2 true EP1435155A2 (de) 2004-07-07

Family

ID=32507351

Family Applications (1)

Application Number Title Priority Date Filing Date
EP02802550A Ceased EP1435155A2 (de) 2001-10-12 2002-10-10 Auswahl eines von mehreren netzwerken zur datenübertragung

Country Status (3)

Country Link
EP (1) EP1435155A2 (de)
KR (1) KR20040041693A (de)
AU (1) AU2002364934A1 (de)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100950842B1 (ko) * 2008-02-28 2010-04-02 동서대학교산학협력단 헬스 케어 기반의 센서 네트워크에서 데이터 전송 경로설정 방법
KR101140253B1 (ko) * 2011-01-25 2012-04-26 국방과학연구소 Mil-std-188-220 프로토콜을 사용하는 통신 단말의 네트워크 가입 방법
CN102416821A (zh) * 2011-07-27 2012-04-18 中国国际航空股份有限公司 飞机系统数据处理方法
KR102496465B1 (ko) * 2022-11-08 2023-02-07 한화시스템(주) 전술 데이터링크 시스템 및 이의 전술메시지 처리 방법

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0889620A2 (de) * 1997-07-03 1999-01-07 Oki Electric Industry Co., Ltd. Sicheres Datenkommunikationsverfahren und Vorrichtung

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0889620A2 (de) * 1997-07-03 1999-01-07 Oki Electric Industry Co., Ltd. Sicheres Datenkommunikationsverfahren und Vorrichtung

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of WO03053013A3 *

Also Published As

Publication number Publication date
KR20040041693A (ko) 2004-05-17
AU2002364934A1 (en) 2003-06-30

Similar Documents

Publication Publication Date Title
US20030158963A1 (en) Smartbridge for tactical network routing applications
Darwish et al. LEO satellites in 5G and beyond networks: A review from a standardization perspective
US6353779B1 (en) Method for managing communication modes for an aircraft
US10453347B2 (en) Method and systems for increasing capacity and safety of aeronautical safety-of-life services and data links
CN101663842B (zh) 管理用于交换飞行器的数据的通信信道的方法和设备
US6931248B2 (en) Method for selecting a ground station within an aeronautical telecommunications network
EP2023685B1 (de) Datenlink-Netzwerkrouting für ein Flugzeug
EP3273424B1 (de) System und verfahren zur flugzeugüberwachung und -verfolgung
WO2003053013A2 (en) Selection of one among several networks for data transmissions
US20190007882A1 (en) Apparatus and method for communications management in an uav
Signore et al. The aeronautical telecommunication network (ATN)
US20080192693A1 (en) Method and Device for Determination of an Address Within an Aeronautical Telecommunication Network
EP1435155A2 (de) Auswahl eines von mehreren netzwerken zur datenübertragung
White Tactical data links, air traffic management, and software programmable radios
US9913199B1 (en) Providing communication over a plurality of networks
EP3335331B1 (de) Vorrichtung und verfahren zur kommunikationsverwaltung
EP3139515A1 (de) Vorrichtung und verfahren für kommunikationsverwaltung
Oishi Future applications and the aeronautical telecommunication network
Gallagher et al. Communication system architecture for air traffic management and weather information dissemination
Mukkamala Integration of LVLASO System with ATN
GB2541236A (en) Apparatus and method for communications management
Neale et al. Current and Future Unmanned Aircraft System Control & Communications Datalinks.
Balvedi et al. OPPORTUNITIES FOR THE USE OF HIGH PERFORMANCE INTERNET PROTOCOL SUITE (IPS) IN THE BRAZILIAN AIR TRAFFIC MANAGEMENT SCENARIO
EP3139514A1 (de) Vorrichtung und verfahren zur kommunikationsverwaltung
Correas et al. An XML Datalink Message Exchange Model (DMXM) for command and control data sharing

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

17P Request for examination filed

Effective date: 20040408

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR IE IT LI LU MC NL PT SE SK TR

AX Request for extension of the european patent

Extension state: AL LT LV MK RO SI

17Q First examination report despatched

Effective date: 20041111

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

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20060319