{'fraction_non_alphanumeric': 0.016288539848749273, 'fraction_numerical': 0.006980802792321117, 'mean_word_length': 5.490566037735849, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Development of an airborne Internet architecture to support SATS: Trends and issues

NASA is undertaking the development of the Small Aircraft Transportation System (SATS). SATS could play a major role in decreasing the doorstop to destination times for travel and shipping. It is conceived to meet four major objectives: higher volume at non-towered/non-radar airports, lower landing minimums at minimally equipped landing facilities, increased single crew safety and mission reliability, and integrated procedures and systems for integrated fleet operations. SATS is to be prototyped in the 2005 timeframe. A key enabling technology for such a system is the development of an airborne Internet to provide aircraft to ground, ground to ground and aircraft to aircraft communications in support of air traffic management, fleet operations, and passenger support services. A critical first step in attaining the desirable capabilities of an airborne Internet is a well-conceived architecture. The architecture must be robust enough to enable the concept of operations envisioned for the 2025 timeframe yet flexible enough to support prototypes using technology and systems available in the 2005 timeframe. This paper addresses some of the trends and issues involved in developing an airborne Internet capable of achieving this goal. Understanding relationships between these trends, issues and objectives, and functional requirements of the program will allow various participants in this complex program to keep activities in proper perspective. The architecture process provides a robust framework to add functionality, systems and equipment. It must also describe the linkage to the existing National Airspace System.