STANAG 4586 – Enabling Interoperability

2y ago
83 Views
12 Downloads
3.49 MB
44 Pages
Last View : 1m ago
Last Download : 2m ago
Upload by : Axel Lin
Transcription

STANAG 4586 – EnablingInteroperabilityTerry BandzulCDL Systems LtdCalgary, Canadawww.cdlsystems.com

Presentation Overview NATO STANAG 4586 OverviewSTANAG 4586 GoalsInteroperability ConceptsSTANAG 4586 In Actionwww.cdlsystems.com

Current Problems UAV products - “stovepipe” designs Little to no standardization between systems Proprietary telemetry and sensor datastreams No capability to interoperatewww.cdlsystems.com

NATO Project Group 35 (PG/35)BackgroundSTANAG No. 4586Edition 1NORTH ATLANTIC TREATY ORGANIZATION(NATO)NATO Standardisation Agency (NSA)STANDARDISATION AGREEMENT(STANAG)SUBJECT: Standard Interfaces of UAV Control System(UCS) for NATO UAV InteroperabilityPromulgated onChairman, NSAwww.cdlsystems.com Conceived in 1998 tostandardize UAV ControlSystem (UCS) interfaces tohelp enable UAVinteroperability NATO Specialist Teamformed from industry andgovernment to develop thestandard USN (PMA-263) isSTANAG 4586 custodian

NATO Project Group 35 (PG/35)Background Lead efforts to achieve UAV interoperability in Joint,Coalition Operations Lead efforts for UAV Autonomous Operationswww.cdlsystems.com

STANAG 4586STANAG 4586 is an Interface Control Definition (ICD)STANAG 4586 Defined two new interfaces- Data Link Interface, DLI- GCS Air Vehicle interface- Command and Control Interface, CCI- GCS Command Control Interface Non-existent Considered essential foundation for interoperable UAVsystemswww.cdlsystems.com

UAV Interfaces & StandardsPayload DataSTANAG 7023 Primary ImagerySTANAG 4545 Secondary ImagerySTANGA 4607 GMTI Radar DataSTANAG 4609 Motion ImageryData LinkSTANAG 7085AirVehicleFocus ofSTANAG 4586Payload&DataPayloadC2ImageryDigital MessagesC4I Nodeswww.cdlsystems.comTactical MessagesSTANAG 5500: ADatP-3GroundControl Station

STANAG Key DevelopmentPrinciples Data Link Interface (DLI) Messages are airvehicle and payload independent– Vehicle/Sensor specific messages are allowed Command and Control Interface (CCI) isC4I System/Node independent– Leverage existing Standards, e.g. STANAG 5500(USMTF)www.cdlsystems.com

STANAG 4586NATO addressing “technical issues” to enableinteroperability, these include;– DLI and CCI interface definitions– Functional architecture definition– System, subsystem component identification definesCommona “common”set ofdata elementsDataElementswww.cdlsystems.com

“Common” Data ElementsImplementation Guide:provides the comprehensive description of theintention of each message and data elementin the DLI interface, and makesrecommendations on a common approachfor implementation– Removes ambiguitywww.cdlsystems.com

Command & ControlInterface (CCI) STANAG 4586 provides an interfaceprofile that defines the specific choicesapplicable to UAVs within each standard,thereby ensuring interoperability.ETC.STANAG 4545USMTFADat-P3UAV/C4I INTERFACE PROFILEGCSwww.cdlsystems.comC4I Nodes

STANAG 4586In addition, STANAG 4586: uses standards, existing and developing– specifies other standards where possible– non-proprietary in nature– if shortfalls in standards, request updates. ie;CRD, extended CRD– not redefining standards defines relationship between the standardswww.cdlsystems.com

Allied Force InteroperabilitySTANAG focus:Achieve interoperabilitybetween NATO allied forcesCommon view of Interoperabilitywww.cdlsystems.com

Interoperability IdealIdeal goal of interoperabilityA UAV overhead a compliant GCS, for whichit has not been “natively” developed, couldbe passed for control to this compliantstation with the vehicle being safelycontrolled to 100 percent of its requiredcapabilitieswww.cdlsystems.com

Multi Vehicle, ModularNetworked OperationsAllows individual addressing of specific Systemcomponents- the generic interface anticipates that there will be multiple Vehiclesconnected to multiple CUCSs in a networked or standaloneconfiguration, addressing a shared data link resource, or multiple datalinkswww.cdlsystems.com

Interoperability Concept of Operations (CONOPS) and Doctrine “Neutral” Supports evolving CONOPS and DoctrineUS ArmyClass IV UAVUS NavyTactical UAVUnited KingdomWatch KeeperItalianPredatorwww.cdlsystems.com

CONOPSControl a single vehicle, of aspecific typeWhat is the advantage to usingSTANAG 4586 ?- Sharing the asset- considering futureexpandabilitywww.cdlsystems.com

CONOPSMultiple vehicles,single type,simultaneouslyMultiple Data Linkswww.cdlsystems.comSingle CommonData Link

CONOPSMany vehicle types, controlled serially from acommon GCSMultiple Data Links- One at a timewww.cdlsystems.comCommon Data Link- one at a time

CONOPSMultiple vehicles, multipletypes simultaneouslyMultiple Data LinksAdditional requirements– Co-location versus networkedoperation– DLI across RF linkCommon Data Linkwww.cdlsystems.com

Scalable Interoperability Not always requirement to control 100% ofvehicle capabilities– Expensive undertaking Only control functionality required to beinteroperable– five Levels of Interoperability defined withinthe standardwww.cdlsystems.com

Levels of Interoperability Level I: Level II:Indirect receipt/transmission of UAVrelated payload data.Direct receipt of ISR/other data where“direct” covers reception of the UAVpayload data by the UCS when it hasdirect communication with the UAV. Level III: Control and monitoring of the UAV payloadin addition to direct receipt of ISR/other data. Level IV: Control and monitoring of the UAV,less launch and recovery. Level V: Control and monitoring of the UAV, pluslaunch and recovery functionswww.cdlsystems.com

Modular ControlModular Architecture- functional separation situation awareness AV mission execution andmonitoring Payload – monitor, control Data Links – monitor, controlScalablewww.cdlsystems.com

STANAG 4586 In Action VCS-4586, Common User Interface forrange of controlled vehicleswww.cdlsystems.com

VCS STANAG 4586Applications US Army One System– RQ-7B Shadow 200 - AAICorp– Warrior – GA ASIBarracuda (RIB) – MeggittDefence Systems CanadaGrasshopper – AdvancedSubsonicsRaven – AeroVironmentGolden Eye – AuroaAerosonde - AAI Corp.Grasshopper - AdvancedSubsonics & XiphosSilver Fox - Advanced CeramicsScan Eagle - BoeingKingfisher & Other - BAESystemsRTB (Research Test Bed) - CAE /CDL SystemsBlade - Ultrawww.cdlsystems.comShadow 200SilverfoxWarriorScan EagleAerosondeKingfisherGrasshopperHammerheadBlade

Mini UAV to MALE Currently, how is it that the sameCUCS software can be used to controlvehicles as diverse as a mini UAV anda MALE? VSMs are key, but not 100% of theanswer STANAG 4586 is scalable inimplementation, from a singleoperator, single laptop for a miniUAV, to dual operator workstationsfor MALE UAVs. STANAG 4586 is configurablethrough VSM messages and/or throughconfiguration fileswww.cdlsystems.com

VCS-4586Common User Interface Configuration Messages are used to request airvehicle and payload configuration information.–––– Expected range of vehicle parametersApplicability of generic parameters to vehicleAvailability of generic parameters from vehicleExtensibility of parametersThe CUCS uses this information to configure thedisplays for the Air Vehicle/ payload.www.cdlsystems.com

HCI - Configurable ElementsMessage #1201: Display Unit RequestThe CUCS uses the Display Unit Requestmessage to identify the display units that the VSMis required to use in Remote Displays.Examples: Distance Altitude Speed Temperature Mass/Weight Angles PressureMessage #1202: CUCS Resource ReportUsed to communicate to the VSM the resourcesavailable within the CUCS for managing remotedisplays to be presented at the CUCS.Examples: JAVA Engine Available PDF Reader Available X Window Server Available X Window Display Number X Window Screen Number Display Window Horizontal Widthwww.cdlsystems.comMessage #1303: Field Configuration CommandThis message is used by the CUCS to configureany GUI components associated with a formattedDLI message field, where the state of the field maybe altered in accordance with the contents of thismessage.This message is sent from the VSM to the CUCSwhenever the controllable state of a field or anenumeration within a field changes thus identifyingthe allowable states of control at the VSM for thespecified parameter.Examples:Altitude Command TypeHeading CommandSpeed TypeAltitude TypeAntenna TypeFlight Mode(over 30)

Parameter RangesCUCS supports full STANAG parameter ranges,But Configures the displays to suit the selectedvehicleAltitude scalemodifiedwww.cdlsystems.com

Parameter ApplicabilityCUCS must be capable of supporting allgeneric functionality,but is expected to remove functionalityunsupported by the controlled vehicleFlight modesremovedwww.cdlsystems.com

Vehicle LogicCUCS can not know the control logic for allvehicles,therefore the VSM identifies the current stateof vehicle parametersMission modeunavailablewww.cdlsystems.com

Parameter ExtensibilityAbility to extend generic capabilities with vehiclespecific capabilities, for specific parametersthrough the DLI mechanism,for tight integration into a single application- for operator ease of use- for flight criticality or flight safetyAdded custom Flightmode - Rollwww.cdlsystems.com

Private MessagingAbility to integrate generic capabilities with vehiclespecific capabilities, using privately defined DLImessages,to tightly integrate into a single application- for operator ease of usewww.cdlsystems.com

Configured PanelCompliantConfiguredwww.cdlsystems.com

What Interoperability Means UAV control systems can be developed to meet“national” requirements UAVs for Country A may use one user interface,regardless of UAV type; UAV controllers forCountry B could be using a completely differentuser interface, even though they may be operatingthe same UAVs UAV operated by Country A can be handed off toCountry B, even though the ground stations aredissimilarwww.cdlsystems.com

What Does S4586 Do for Me? Reduces Costs - Capital and O&MSimplifies C4ISR Systems IntegrationReduces Logistics TailDecouples UAV development from GCS Integration Supports National GCS Development with ownCONOPS and Training In Coalition Operations, STANAG 4586 SupportsMultinational Partners Sharing Data from multipleUAVs from multiple countries.www.cdlsystems.com

Acquisition of UAV SystemsThe acquisition of air vehicles canoccur independent of other elementsof the UAV system (eg. the GCS).STANAG 4586 StandardGCS/Air Vehicle InterfaceGroundControl StationThe GCS can be sustained, upgradedand produced in multipleconfigurations independent of theother elements of the system.STANDARDIZED INTERFACE DECOUPLESTHE GCS & AIR VEHICLEwww.cdlsystems.com

Interoperability Does Not Mean Common User Interface for All Users– French Operator does not sit in a Germanshelter Common Training– Train for your own systemwww.cdlsystems.com

Trends Affecting STANAG Bandwidth Reduction – Common Protocol viaRF Link Trend toward network-centric CONOPS-SOA (service-oriented architecture) – provideservices to the network. Trend toward increasing system autonomy-Autonomy messages added to the STANAG 4586,operators become system supervisors Trend toward collaboration among systems-Ship to ship messaging and interactionswww.cdlsystems.com

ConclusionsIs Interoperability possible? STANAG 4586 Edition 2 is ready.STANAG 4586 is implementable.STANAG 4586 is implemented on several realUAVs.A common User Interface per User is achievable.UAV interoperability is now possible.www.cdlsystems.com

STANAG 4586: m

A NATO UAV SystemAIR COMPONENTControlAIR VEHICLEELEMENTStatusPAYLOAD ELEMENTPayload DataData LinkSTANAG 4586www.cdlsystems.comAir DataTerminal7085Ground 4ISystems7023, 4545,4607, 4609

STANAG 4586 Goals Interoperability amongst Allied Forces Diverse Concepts of Operations Network Centric Operations.Secondary considerations: Common ground control station per user vrs Scalability One operator, many vehicles Modular designwww.cdlsystems.com

Interoperability - ONE SystemUS Army TUAV ProjectOffice has introduced“ONE System” to fly: Shadow 200– (AAI Corp.) Hunter– (Northrop Grumman) Sky Warrior– (General Atomics - ASI)Based on the VCS by CDL Systems Ltd.www.cdlsystems.comQuickTime and aTIFF (LZW) decompressorare needed to see this picture.

STANAG 4586 is an Interface Control Definition (ICD) STANAG 4586 Defined two new interfaces - Data Link Interface, DLI -GCS Air Vehicle interface - Command and Control Interface, CCI -GCS Command Control Interface Non-existent Consid

Related Documents:

(STANAG 4746) Airworthiness, “Lite” UAS (STANAG 4703) Airworthiness, Rotary Wing (STANAG 4702) Airworthiness, Fixed Wing (STANAG 4671) Weapons Integ. (STANAG 4737) Interoperability, (STANAG 4586) Data Link (STANAG 4660) Command & Control . C2 . ISR Data NATO Standardization Activities.

STANAG 4586, will ease this process and likely UAV system combinations can be certified in advance. [4]. On this basis, UAV s that are compliant with STANAG 4586 will increase NATO Combined/Joint Service flexibility and efficiency to meet mission objectives through the sharing of assets and

STANAG 4586 will be maintained and updated to correct any latent errors, add improvements from lessons learned, and incorporate new requirements by the STANAG Custodian, supported by a multinational Custodian Support Team (CST). The STANAG has a high degree of continuing attention from the CST. As newFile Size: 1MB

(STANAG 4586), common data links (STANAG 7085), and a plethora of other open format standards. STANAG 4586 has emerged in the forefront in defining interface standards to move towards plug and play systems for UAVs. Put forth by NATO, it is gaining acceptance within the UAS community. Th

Auto-ignition Temperature - STANAG 4491 ( C) 200 C Critical diameter 76 mm Friction sensitivity - STANAG 4489 33 J Impact Sensitivity - STANAG 4487 70 N Card Gap Test Ø40mm - STANAG 4488 80 cards Capacity discharge - STANAG 4490 No reaction Warhead Main charge explosive : B2211D

STANAG 4586 is ubiquitous amongst the UAV community Soon to be a required messaging standard UCS is a well-established, Mature, well-funded UCS is migrating under the AS4 umbrella UCS extensions can be created to allow for interoperability between STANAG 4586 and AS4-JAUS UAS Control

(STANAG) 4586 [3] defines requirements for a standard set ofUCS interfaces . It has been developed over the last decade to promote interoperability among UAS manufacturers and coalition partners. Consistent with the STANAG 4586 functional UAS Architecture, figu

C is much more flexible than other high-level programming languages: C is a structured language. C is a relatively small language. C has very loose data typing. C easily supports low-level bit-wise data manipulation. C is sometimes referred to as a “high-level assembly language”. When compared to assembly language .