曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
UA SYSTEMS ENGINEERING
Implementing network interfaces between all UA systems and subsystems provides three key benefits:
(1) connects the UA to the GIG through either legacy, current, or programmed physical links - copper wire, optical fiber, RF, laser (2) enhances the GIG’s aggregate data handling capacity, and (3) facilitates separating UA functions, making it easier to create modular plug and play components.
Separate Physical Connection From Transport Protocol
UA systems do not have to wait until a net-centric wireless technology is fielded to connect to the GIG. The physical connection between two nodes, be it wire, radio waves or light, merely transfers a signal from one point in space to another. Embedded in that signal is the sequence of ones and zeros that constitute the data being passed. IP based network connections can be implemented using any physical connection. This makes it possible to connect legacy systems to the GIG by replacing tightly coupled, unique data transfer implementations with IP based network connections. Creating an IP network based transport layer separates the data transfer protocols from the physical connection and integrates UA into the GIG regardless of the wireless technology employed (C-band, CDL, JTRS, LaserComm).
APPENDIX C - COMMUNICATIONS
Page C-13
Contribute to the GIG’s Aggregate Bandwidth
Currently, UA communicate with their respective control elements via dedicated, point-to-point data links. These data links provide continuous information handling capacity between the nodes, up to the maximum data rate supported. During long cruise segments of a mission, however, traffic across the dedicated link may drop to nearly zero. The closed system design precludes other users from taking advantage of the unused bandwidth.
Implementation of an IP based, packet switched network interface, between UA systems with multiple data links, control elements and other nodes, provides a path through the UA communications links through which routers can pass packets during lulls in the primary system’s communications needs. Each UA system adds its individual throughput capacity to the larger network. Access priority can be controlled using QoS and COS technologies as defined by IEEE standard 802.1p giving top priority to the primary system’s communications requirements. Looking at the operating theater’s communications infrastructure as a whole, it becomes clear that implementing networked interfaces for all communications links, not just UA, significantly increases data handling in theater, with no compromise to the data needs of the primary system.
Separate UA Functions
In addition to migrating point to point links to network interfaces, UA components and functions must be separated, modularized and connected using network interfaces. In keeping with the net-centric approach to system design, Figure C-8 illustrates one approach to separating and modularizing UA components and functions, within the UA. The platform’s local area network (LAN) connects sensors, sensor management, and flight management units. The communications equipment connects to the WAN traffic manager and links the platform LAN to other Local Area Networks. Within the control station (ground, afloat, or airborne) the same approach applies. Consoles connect to the LAN, and the communications equipment provides pathways between that LAN and other LAN segments.
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
无人机系统路线图 Unmanned Aircraft Systems Roadmap(120)
