Transcription
TENA LVC Object Model CollectionITEA LVC WorkshopJim BakTENA SDA17 September 2019
Change is Needed The TENA-Platform and related OMs (e.g. PlatformDetails,Engagement, Radar) were originally designed 15 years ago Early adopters were predominately from the simulation world Concepts followed the core DIS (Distributed Interactive Simulation) PDUs(Protocol Data Units) Currently, these OMs are heavily used by the user community with a large installbase of TENA-enabled applications2
Change is Needed The TENA-Platform and related OMs (e.g. PlatformDetails,Engagement, Radar) provide incomplete mappings to their respectiveDIS PDU counterparts Difficult to provide round-trip data translations (DIS - TENA - DIS) TENA is used to provide the WAN mechanism for data exchange with a largenumber of DIS-based systems that operate at different sites DIS-based systems has the majority of the market share in the simulation community Large percentage of Virtual and Constructive simulations communicate natively using asubset of DIS PDUs There has been a recent update to the IEEE DIS 1278.1 specification in 2012 Most notable change is to IFFIs it time to introduce TENA OM changes to reflect the evolving T&Eand test & training needs of our Warfighter?3
OM Limitations Data gaps within this subset of TENA Standard OMs have becomeexposed Entity RepresentationArticulated PartsAttached Parts4
OM Limitations Data gaps within this subset of TENA Standard OMs have becomeexposed Entity Representation Guise5
OM Limitations Data gaps within this subset of TENA Standard OMs have becomeexposed Electronic Warfare Emissions Jamming6
OM Limitations The TENA User community has generated their own OMs to bridgeidentified gaps in the current TENA Standard OMs InterTEC CCFW OM to augment TENA-Embedded-IFF (to include Mode 5), model Emissions forEW, and model Radio Communications (DIS Transmitter/Signal PDUs)ProLogic Simulating Link-16 JNTC JPARC LiveTraining USNNTTR Over 750 User Object Models!7
Assessing OM Gaps TENA SDA performed a gap analysis study of a subset of the TENAStandard OMs with their respective DIS PDU counterparts rmType-v2TENA-Embedded-v3 TENA-Emitter-v1.OM1127.5 candidate TENA-IFF-v1.OM1278.2 candidate to replace TENA-Embedded-IFF and InterTEC-CCFWIFFTo replace ion-v3TENA-RadioCommunication-v1.OM1279.2 candidate To replace InterTEC-CCFW-Transmitter/Signal8
Platform / PlatformDetails9
Platform / Platform Details Originally was partially based from the DIS Entity State PDUWhy two OMs? TENA::Platform represents attributes that require frequent data changesTENA::PlatformDetails represents attributes that either infrequently changes or isstatic from the beginningChallenges Difficult to provide complete round trip data translations DIS Entity State PDU TENA Platform/PlatformDetails DIS Entity State PDU is NOTa lossless communicationSoftware development confusion Is PlatformDetails even required?What if a DIS Translator tool receives Platform but not PlatformDetails? Should it translate and send an Entity State PDU anyways? Should it wait for the PlatformDetails?10
TENA::Platform(Partial UML Diagram)PlatformUniqueID-siteID: uint16-applicationID: uint16-objectID: uint32-platformID: UniqueID-platformType: PlatformType-pPlatformDetails: *PlatformDetails-designator: string-affiliation: Affiliation-damageState: DamageState-damageInPercent: float32-tspi: TSPI-sendTime: TENA-TimeTSPI-time: Time-position: Position-velocity: Velocity-acceleration: Acceleration-orientation: Orientation-angularVelocity: AngularVelocity-angularAcceleration: AngularAccelerationPlatformType(common use case represented)-entityType: DIS::EntityTypeDIS::EntityTypePlatformDetails(next slide)-kind: octet-domain: octet-country: uint16-category: octet-subcategory: octet-specific: octet-extra: octet11
TENA::PlatformDetails(Partial UML Diagram)AppearanceExerciseForce-exerciseID: UniqueID-owningOrganization: UniqueIDUniqueID-siteID: uint16-applicationID: uint16-objectID: uint32AssociatedPlatform-associatedPlatformID: UniqueID-association: Association-associationName: stringPlatformDetails-platformID: UniqueID-exerciseForce: ExerciseForce-callSign: string-instrumentationID: UniqueID-platformContext: PlatformContext-countryOfAllegiance: uint16appearance: Appearance-associatedPlatforms: AssociatedPlatforms -suppressed: boolean-isReplayData: boolean-isGeotranslated: boolean-instrumentationCommQualityInPercent: float32-deadReckoningAlgorithm: DeadReckoningAlgorithm-contamination: Contamination -platformUpdatePeriodInSeconds: float32-sendTime: TENA-Time-flaming: boolean-powerPlantOn: boolean-trailingSmoke: boolean-engineSmoke: boolean-camoulage: Camouflage-trailingEffects: TrailingEffectsContamination-agentType: AgentType-agentSource: AgentSource-contaminationLevel: NBCthreshold-percentContaminated: float3212
Entity State PDUPDU Header-Protocol Version: enum-Exercise ID: uint-PDU Type: enum 1-Protocol Family: enum 1-Timestamp: uint-Length: uint-PDU Status: recordPDU Status-Transferred Entity Indiator: enum-LVC Indicator: enum-Coupled Extension Indicator: enum-Detonation Type Indicator: enum 0-Radio Attached Indicator: enum 0-Intercom Attached Indicator: enum 0-IFF Simulation Mode: enum 0-Active Interrogation Indicator: enum 0Entity IDEntity State-PDU Header: record-Entity ID: record-Force ID: enum-Number of Variable Parameter Records: uint-Entity Type: record-Alternate Entity Type: record-Entity Linear Velocity: record-Entity Location: record-Entity Orientation: record-Entity Appearance: record-Dead Reckoning Parameters: record-Entity Marking: record-Capabilities: record-Variable Parameter Record: record -Site Number: uint-Application Number: uint-Entity Number: uintEntity Type/Alternate Entity Type-Entity Kind: enum-Domain: enum-Country: enum-Category: enum-Subcategory: enum-Specific: enum-Extra: enumEntity Appearance-An ugly 32-bit record that is dependanton the entity's domainCapabilities-Ammunition Supply: boolean-Fuel Supply: boolean-Recovery: boolean-Repair: boolean-ADS-B: boolean-Sling Load Carrier: boolean-Sling Loadable: boolean-IED Presence Indicator: boolean-Task Organizable: boolean-LAIRCM: booleanDead Reckoning Parameters-Dead Reckoning Algorithm: enum-Other Parameters: record based oncoordinate system-Entity Linear Acceleration: record-Entity Angular VelocityVariable Parameter-Record Type: enum-Record-specific Fields: 120 bitsEntity Marking-Character Set: enum-Character: uint Not supported by a TENA attributePartially supported by a TENA attribute13
Electromagnetic Emissions14
The InterTEC Story Once upon a time, the Interoperability Test & Evaluation Capability(InterTEC) Program made an investment in introducing ElectronicWarfare/Electronic Attack capabilities into their LVC distributed testenvironment All of the EW-capable sites that were recruited employed DIS-centric Virtualand Constructive simulationsInterTEC performed an assessment of the TENA-Radar OM Found it to be a bit overkill. Tons and tons of attributes that described thephysical part of the radar system. A small subset that described theemissions Did not want to always publish the physical part of the radar system for eachemission state update15
TENA::Radar(Partial UML Diagram)RadarSystemTargetData-trackID: UniqueID-isMasked: boolean-azimuthToTargetInRadians: float32-elevationToTargetInRadians: float32-rangeToTargetInMeters: float32-antennaID: uint16Transmitter-type: RadarType-function: Function-status: Status-maximumEffectiveTrackingDistanceInMeters: float32-targets: TargetData -transmitters: Transmitter -receivers: Receiver -antennas: Antenna -operatingMode: uint32-elnot: stringAntennaAperture-areaInMetersSquared: float32-majorAxisInMeters: float32-minorAxisInMeters: float32-azimuthDistribution: ApertureDistribution-elevationDistribution: ApertureDistributionGate-gateType: GateType-gateEdge1: float64-gateEdge2: float64TransmitBeam-frequencyInHertz: float64-pulsedRepititionFrequencyInHertz: float64-powerInWatts: float32-pulseWidthInMicroseconds: float32-frequencyRangeInHertz: float64-jammingTechnique: JammingTechnique-antennaID: uint16-antennaName: string-aperture: Aperture-mode: AntennaMode-scanType: ScanType-slewRateAzimuthInRadiansPerSecond: float32-slewRateElevationInRadiansPerSecond: float32-polarizationType: PolarizationType-polarizationAngleInRadians: float32-gates: Gate -transmitBeams: TransmitBeam -receiveBeams: Beam -gainInDecibels: float32-azimuthInRadians: float32-elevationInRadians: float32-rollInRadians: float32-offsetFrontInMeters: float32-offsetRightInMeters: float32-offsetDownInMeters: float32-antennaIDs: uint16 -transmitterType: TransmitterType-transmitterStatus: TransmitterStatusReceiver-antennaIDs: uint16 -receiverType: ReceiverType-receiverStatus: ReceiverStatusBeam-beamWidthAzimuthInRadians: float32-beamWidthElevationInRadians: float32-azimuthInRadians: float32-elevationInRadians: float32-scanRateInHertz: float32-slewRateAzimuthInRadiansPerSecond: float32-slewRateElevationInRadiansPerSecond: float32-active: boolean-sideLobes: SideLobe SideLobe-levelAzimuthInDecibels: float32-levelElevationInDecibels: float32-lobeAngleAzimuthInRadians: float32-lobeAngleElevationInRadians: float32InterTEC required only theEmissions part of this OM16
The InterTEC Story (cont’d) So, InterTEC decided to create their own object model to representEmissions for their EW/EA modeling requirement Creation of the Communications Control Framework Object Model (CCFWOM) containing Emissions An almost one for one mapping with the DIS Electromagnetic Emissions PDUAdditional attributes included to support the Joint Research Analysis andAssessment Center (JRAAC) HLA FOMAdditional attributes thrown in to enable the M&S of real-world emitters usingthe Electronic Warfare Integrated Reprogramming Database (EWIRDB)Not designed for high fidelity modeling of an electromagnetic waveform17
TENA::InterTEC::CCFW::Emission(Partial UML Diagram)CCFW::Emission-time: TIME-emissionUniqueID: UniqueID-eventNumber: uint16-stateUpdateIndicator: octet-operatingMode: uint32-ecmMode: EcmMode-elnot: string-amesIII ifile: string-emittingSystemGroup: EmittingSystem -sendTime: TimeEmittingSystem-emitterName: uint16-function: octet-emitterIdNumber: octet-beamGroup: Beam BeamFundamentalParamData-frequency: float32-frequencyRange: float32-effectiveRadiatedPower: float32-pulseRepetitionFrequency: float32-pulseWidth: float32-beamAzimuthCenter: float32-beamAzimuthSweep: float32-beamElevationCenter: float32-beamElevationSweep: float32-beamSweepSync: float32-beamIDNumber: octet-beamFunction: octet-highDensityTrack: octet-jammingModeSequence: uint32-powerSource: PowerSource-waveform: Waveform-jammerSignalRatio: float64-fundParamData: FundamentalParamData-jammingTargetGroup: JammerTarget -sideLobes: SideLobe JammerTarget-jammerTargetUniqueID: UniqueID-emitterID: octet-beamID: octetSideLobe-levelAzimuthInDecibels: float32-levelElevationInDecibels: float32-lobeAngleAzimuthInRadians: float32-lobeAngleElevationInRadians: float3218
Electromagnetic Emissions PDUElectromagnetic EmissionPDU Header-Protocol Version: enum-Exercise ID: uint-PDU Type: enum 23-Protocol Family: enum 6-Timestamp: uint-Length: uint-PDU Status: record-PDU Header: record-Emitting Entity ID: record-Event ID: record-State Update Indicator: enum-Number of Systems: uint-System Data Length: uint-Number of Beams: uint-Emitter System: record-Location: record-Beam: record Emitting Entity ID-Site Number: uint-Application Number: uint-Entity Number: uintFundamental Parameter Data-Frequency: float-Frequency Range: float-Effective Radiated Power: float-Pulse Repetition Frequency: float-Pulse Width: floatBeam Data-Beam Azimuth Center: float-Beam Azimuth Sweep: float-Beam Elevation Center: float-Beam Elevation Sweep: float-Beam Sweep Sync: floatEvent ID-Site Number: uint-Application Number: uint-Event Number: uintEmitter System-Emitter Name: enum-Emitter Function: enum-Emitter Number: uintBeam-Beam Data Length: uint-Beam Number: uint-Beam Parameter Index: uint-Fundamental Parameter Data: record-Beam Data: record-Beam Function: enum-Number of Targets: uint-High-Density Track/Jam: enum-Beam Status: record-Jamming Technique: record-Track/Jam Data: record Jamming Technique-Kind: enum-Category: enum-Sub-category: enum-Specific: enumLocation-x-component: float-y-component: float-z-component: floatBeam Status-Beam State: enumTrack/Jam Data-Site Number: uint-Application Number: uint-Entity Number: uint-Emitter Number: uint-Beam Number: uintNot supported by a CCFW::Emission attributePartially supported by a CCFW::Emission attribute19
The InterTEC Story (cont’d) However, all good stories come to an end InterTEC Program ended over five years agoBut this OM continues to be used in a number of TENA-based tools andapplicationsAnd this OM has been downloaded 199 times over the past 2 yearsAnd is used in many distributed test events on the JSN Most recently, the Interoperability Development & Certification Test (IDCT) seriesof distributed test events conducted by the NavyIs this because InterTEC’s CCFW OM nearly models the sameattributes that are in the DIS Electromagnetic Emission PDU?20
IFF21
IFF IFF has the same InterTEC story as Emissions So, we’ll spare you the UML eyechartsCurrently represented by TENA::Embedded::IFFTENA::Embedded::IFF evaluated by the InterTEC project InterTEC created TENA::CCFW::IFF to extend TENA::Embedded::IFF An almost one for one mapping of the DIS IFF PDUInterTEC updated TENA::CCFW::IFF to support IFF Mode 5 Some attributes were there, but, not allIFF Mode 5 data model support introduced in the IEEE Std 1278.1-2012specification – released 19 December 2012Currently used in the DIS Gateway (DISGW) ProductAnd is used in many distributed test events on the JSNAgain, is this because the CCFW OM nearly models the sameattributes that are in the DIS IFF PDU?22
The Proposal Propose to have an LVC OM Collection that is based on the DataModel from the DIS 1278.1-2012 PDU messages Entity StateIFFElectromagnetic EmissionFireDetonateTransmitterSignalPromote that DIS TENA DIS round-trip data translations arelosslessIntegration of this LVC OM Collection would require a mechanism forbackward compatibility to current users of the associated TENAStandard OMs “Behind the scenes” “transmogrifiers” from within the middleware/OMimplementation23
User Community Input Series of JMETC Technical Exchanges (JTEXs) have been held over thepast two years User Community in attendance during the LVC Track agreed that the core set ofTENA Standard OMs representing LVC needed to be refined User Community also agreed that the best path forward is to develop a TENA LVCOM Collection that aligned to the subset of DIS PDUs representing LVC Data attribute alignment Beware of bitbuckets!!24
TENA LVC OM Collection25
TENA LVC OM Collection The Collection TENA LVC Entity TENA LVC Engagement DIS Entity State TENA LVC Fire DIS Fire TENA LVC Detonation DIS Detonation TENA LVC Emissions DIS Electromagnetic Emissions TENA LVC IFF DIS IFF TENA LVC RadioCommunications TENA LVC Transmitter DIS Transmitter TENA LVC Signal DIS SignalTENA LVC EntityType DIS Entity Type26
TENA LVC OM Collection Based on IEEE 1278.1-2012 – IEEE Standard for Distributed InteractiveSimulation – Application Protocols, 19 December 2012 Based on SISO-REF-010-2016 – Reference for Enumerations forSimulation Interoperability, Version 22, 10 May 2016 Wiki page documenting the development progress Location of the TENA LVC Collection TDL files https://www.trmc.osd.mil/wiki/display/OM/TENA LVC OM CollectionThis is NOT a Final product Expect many, many more drafts and iterations to take place27
TENA::LVC::Entity(Partial UML Diagram)TENA LVC EntityEntityType-Entity Kind: enum-Domain: enum-Country: enum-Category: enum-Subcategory: enum-Specific: enum-Extra: her: rametersType-localYawInRadians: float32-localPitchInRadians: float32-localRollInRadians: float32-exerciseID: int16-time: TENA::Time-transferredEntityIndicatorIsSet: boolean-lvcIndicator: LVCindicator-entitySiteNumber: int16-entityApplicationNumber: int16-entityNumber: int16-forceID: ForceID-entityType: EntityType-alternateEntityType: EntityType (optional)-tspi: TENA::TSPI-deadReckoningParameters: DeadReckoningParameters (optional)-entityMarking: EntityMarking (optional)-articulatedPartVPR: ArticulatedPartVPR -attachedPartVPR: AttachedPartVPR -entityAssociationVPR: EntityAssociationVPR -entityTypeVPR: EntityTypeVPR -separationVPR: SeparationVPR TENA::TSPI-time: Time-position: Position-velocity: Velocity-acceleration: Acceleration-orientation: Orientation-angularVelocity: AngularVelocity-angularAcceleration: acterSet: characterSet-entityMarkingCharacterSetIfOther: string-entityMarking: PRSeparationVPREntityAssociationVPRSee Next Slide28
TENA::LVC::Entity(Partial UML Diagram)TENA LVC EntityLand Entity-appearance: Appearance-capabilities: CapabilitiesAir Entity-appearance: Appearance-capabilities: CapabilitiesSurface Entity-appearance: Appearance-capabilities: CapabilitiesSubsurface Entity-appearance: Appearance-capabilities: CapabilitiesSpace Entity-appearance: Appearance-capabilities: CapabilitiesMunition Entity-appearance: Appearance-capabilities: CapabilitiesLifeform Entity-appearance: Appearance-capabilities: CapabilitiesAppearance (Land Entity Example)NonHumanLifeform Entity-appearance: Appearance-capabilities: CapabilitiesEnvironmental Entity-appearance: Appearance-capabilities: CapabilitiesCulturalFeature Entity-appearance: Appearance-capabilities: CapabilitiesSupply Entity-appearance: Appearance-capabilities: CapabilitiesRadio Entity-appearance: Appearance-capabilities: CapabilitiesExpendable Entity-appearance: Appearance-capabilities: CapabilitiesSensorOrEmitter Entity-appearance: Appearance-capabilities: Capabilities-paintScheme: boolean-mobilityKilled: boolean-firePowerKilled: boolean-damage: enum-isSmokeEmanating: boolean-isEngineEmittingSmoke: boolean-trailingDustCloud: enum-primaryHatch: enum-headLightsOn: boolean-tailLightsOn: boolean-brakeLightsOn: boolean-isFlaming: boolean-launcherOperational: boolean-camouflageType: enum-concealedPosition: boolean-isFrozen: boolean-powerPlantOn: boolean-entityIsDeactivated: boolean-tentExtended: boolean-rampExtended: boolean-blackoutLightsOn: boolean-blackoutBrakeLightsOn: boolean-spotOrSearchLightOn: boolean-forwardInteriorLightsOn: boolean-occupantsSurrendered: boolean-entityIsMaskedOrCloaked: booleanCapabilities (Land Entity Example)-ammunitionSupply: boolean-fuelSupply: boolean-recovery: boolean-repair: boolean-slingLoadable: boolean-IEDpresenceIndicator: booleantaskOrganizable: boolean29
TENA::LVC::Fire(Partial UML Diagram)TENA LVC FireTENA LVC EntityType-Entity Kind: enum-Domain: enum-Country: enum-Category: enum-Subcategory: enum-Specific: enum-Extra: enum-exerciseID: int16-time: TENA::Time-lvcIndicator: enum-fireTypeIndicatorIsExpendable: boolean-pFiringEntity: * TENA::LVC::Entity-targetSiteNumber: int16-targetApplicationNumber: int16-targetNumber: int16-munitionSiteNumber: int16-munitionApplicationNumber: int16-munitionNumber: int16-eventNumber: int16-fireMissionIndex: int32-tspiAtFire: TENA::TSPI-munitionOrExpendableType: TENA::LVC::EntityType-warhead: int16-fuse: int16-quantity: int16-rate: int16-rangeToTargetInMeters: float3230
TENA::LVC::Detonation(Partial UML Diagram)TENA LVC DetonationTENA LVC EntityType-Entity Kind: enum-Domain: enum-Country: enum-Category: enum-Subcategory: enum-Specific: enum-Extra: enum-exerciseID: int16-time: TENA::Time-lvcIndicator: enum-detonationTypeIndicator: enum-detonationTypeIndicatorIfOther: string-pSourceEntity: * TENA::LVC::Entity-targetSiteNumber: int16-targetApplicationNumber: int16-targetNumber: int16-explodingEntitySiteNumber: int16-explodingEntityApplicationNumber: int16-expordingEntityNumber: int16-eventNumber: int16-tspiAtImpact: TENA::TSPI-explodingObjectType: TENA::LVC::EntityType-warhead: int16-fuse: int16-quantity: int16-rate: int16-explosiveMaterial: enum-explosiveMaterialIfOther: string-explosiveForceInJoulesPerKilogram: float32-detonationResult: enum-detonationResultIfOther: string-articulatedPartVPR: ArticulatedPartVPR -attachedPartVPR: AttachedPartVPR entityAssociationVPR: EntityAssociationVPR entityTypeVPR: EntityTypeVPR -separationVPR: SeparationVPR rationVPREntityAssociationVPR31
TENA::LVC::Emissions(Partial UML Diagram)Emissions-exerciseID: int16-time: TENA::Time-transferredEntityIndicatorIsSet: boolean-lvcIndicator: enum-pEntity: * TENA::LVC::Entity-eventNumber: int16-isStateUpdate: boolean-emitterSystem: EmitterSystem -emitterIsOn: boolean-emitterIsRotating: boolean-azimuthScanRate: float32-fieldOfRegardAzimuthHalfAngleInDegrees: float32-fieldOfRegardElevationHalfAngleInDegrees: float32-fieldOfRegardMaximumRange: float32EmitterSystem-emitterName: string-emitterFunction: enum-emitterFunctionIfOther: string-emitterNumber: int16-position: TENA::Position-relativePosXinMeters: float64-relativePosYinMeters: float64-relativePosZinMeters: float64-beamEmissions: Beam Beam-beamNumber: int16-beamParameterIndex: int16-frequencyInHz: float32-frequencyRangeInHz: float32-effectiveRadiatedPowerInDecibelMilliwatts: float32-pulseRepetitionFrequencyInHz: float32-pulseWidthInMicroseconds: float32-beamAzimuthCenterInDegrees: float32-beamAzimuthSweepInDegrees: float32-beamElevationCenterInDegrees: float32-beamElevationSweepInDegrees: float32-beamSweepSyncInPercent: float32-beamFunction: enum-beamFunctionIfOther: string-highDensityTrackJamSelected: boolean-beamIsNotActive: boolean-jammingTechnique: EntityType-trackJamData: TrackJamData TrackJamData-entitySiteNumber: int16-entityApplicationNumber: int16-entityNumber: int1632
time: TENA::Time-pEntity: * TENA::LVC::Entity-elnot: string-operatingMode: string-emitterTargetList: TrackJamData TrackJamData-entitySiteNumber: int16-entityApplicationNumber: int16-entityNumber: int16The ParametricEmissions class is used for emitters that are defined according to the Electronic Warfare IntegratedReprogramming Database (EWIRDB). The EWIRDB is the primary Department of Defense source for the technical parametric andperformance data on non communication electronic emitters and associated systems. The EWIRDB is the product of merged datafrom a number of different sources and it uses the NSA managed ELINT Notation (ELNOT) system as the primary label for anon communications emission. This database includes emitter files that provide parametric data, references, and commentsdescribing the electronic equipment that generates an electronic emission.33
TENA::LVC::IFF(Partial UML Diagram)IFF-exerciseID: int16-time: TENA::Time-transferredEntityIndicatorIsSet: boolean-lvcIndicator: enum-interrogationIsActive: boolean-pEmittingEntity: * TENA::LVC::Entity-eventNumber: int16-relativeAntennaPosXinMeters: float32-relativeAntennaPosYinMeters: float32-relativeAntennaPosZinMeters: float32-systemType: enum-systemTypeIfOther: string-systemName: enum-systemNameIfOther: string-systemMode: enum-systemModeIfOther: string-changeIndicatorIsSet: boolean-altMode4Capable: boolean-altModeCcapable: boolean-thisIsHeartbeat: boolean-systemIsInterrogator: boolean-simulationMode: enum-simulationModeIfOther: string-testModeIsOn: boolean-systemDesignator: int16-systemStatus: enum-systemStatusIfOther: string-altMode4ChallengeReply: enum-altMode4ReplyIfOther: string-militaryEmergencyIsOn: boolean-IDofPositionIsOn: boolean-IsUnmannedAircraft: boolean-mode1: int16-mode2: int16-mode3a: int16-mode4: int16-modeCaltitude: int32-rrb: int16-modeSinterrogator: int16-TCAS ACASstatus: enum-TCAS ACASstatusIfOther: stringIFF (cont'd)-layer2Emissions: EmissionsData-layer3Mode5: Mode5Data-layer4ModeS: ModeSData-dataCategory: enum-dataCategoryIfOther: string-IFFdata: IFFdataRecord EmissionsData (Layer 2)-beamAzimuthCenterInDegrees: float32-beamAzimuthSweepInDegrees: float32-beamElevationCenterInDegrees: float32-beamElevationSweepInDegrees: float32-beamSweepSyncInPercent: float32-operationalParameters: int16-iffFundamentalParameterData: iffFundamentalParameterData Mode5Data (Layer 3)ModeSData (Layer 4)IFFdataRecord-type: int32-fields: octet 34
TENA::LVC::RadioTransmitter(Partial UML Diagram)TENA LVC EntityType-Entity Kind: enum-Domain: enum-Country: enum-Category: enum-Subcategory: enum-Specific: enum-Extra: enumHAVE QUICK Parameters-netNumber: int16-frequencyTable: enum-frequencyTableIfOther: string-mode: enum-modeIfOther: string-MWODindex: int16-timeOfDayDelta: int32-wordOfDay1: int32-wordOfDay2: int32-wordOfDay3: int32-wordOfDay4: int32-wordOfDay5: int32-wordOfDay6: int32SINCGARS ModulationParameters-frequencyHoppingNetID: int16-hopSetID: int16-lockoutSetID: int16-isMessageStart: boolean-channelIsClear: boolean-freqHoppingSyncTimeOffsetInSeconds: int32-transmittionSecurityKey: int16RadioTransmitter-exerciseID: int16-time: TENA::Time-transferredEntityIndicatorIsSet: boolean-lvcIndicator: enum-radioAttachedIndicator: enum-pRadioReference: * TENA::LVC::Entity-radioSiteID: int16-radioApplicationID: int16-radioEntityReferenceNumber: int16-radioNumber: int16-radioType: TENA::LVC::EntityType-radioTransmitState: enum-inputSource: enum-inputSourceIfOther: string-antennaPosition: TENA::Position-relativeAntennaPosXinMeters: float32-relativeAntennaPosYinMeters: float32-relativeAntennaPosZinMeters: float32-antennaPatternType: enum-antennaPatternTypeIfOther: string-frequencyInHz: int64-transmitFreqBandwidthInHz: float32-powerInDecibelMilliwatts: float32-spreadSpectrumTechniqueIsFrequencyHopping: boolean-spreadSpectrumTechniqueIsPseudoNoise: boolean-spreadSpectrumTechniqueIsTimeHopping: boolean-majorModulation: enum-majorModulationIfOther: string-modulationDetail: enum-modulationDetailIfOther: string-radioSystem: enum-radioSystemIfOther: string-cryptoSystem: enum-cryptoSystemIfOther: string-pseudoCryptoKey: int16-cryptoMode: enum-cryptoModeIfOther: string-haveQuickParameters: HAVE QUICK Parameters-sincgarsModulationParameters: SINCGARS : JTIDS MIDS ModulationParameters-antennaPatterns: BeamAntennaPattern -VTP: VariableTransmitterPatterns JTIDS MIDS ModulationParameters-timeSlotAllocationLevel: enum-timeSlotAllocationLevelIfOther: string-isNetworkTimeReference: boolean-isJTIDSunitParticipant: boolean-terminalSecondaryMode: enum-terminalSecondaryModeIfOther: string-isCoarseSynchronized: boolean-isFineSynchronized: boolean-networkSynchronizationID: int32BeamAntennaPattern-beamDirectionPsiInRadians: float32-beamDirectionThetaInRadians: float32-beamDirectionPhiInRadians: float32-azimuthBeamwidthInRadians: float32-elevationBeamwidthInRadians: float32-electricFieldZmagnitude: float32-electricFieldXmagnitude: float32-phaseInRadians: float32VariableTransmitterParameters-recordType: int32-vtpFields: octet 35
TENA::LVC::RadioSignal(Partial UML Diagram)RadioSignal-exerciseID: int16-time: TENA::Time-transferredEntityIndicatorSet: boolean-lvcIndicator: enum-radioAttachedIndicator: enum-pRadioReference: * TENA::LVC::Entity-radioSiteID: int16-radioApplicationID: int16-radioEntityReferenceNumber: int16-transmittingRadioNumber: int16-encodingClass: enum-encodingClassIfOther: string-encodingType: enum-encodingTypeIfOther: string-tdlType: enum-tdlTypeIfOther: string-sampleOrDataRate: int32RadioSignalData36
JTEX-04 Summary An Object Model Tech Exchange (OMTE) was conducted on the TENALVC OM Collection All OMs reviewed in excruciating detail User community agreed to advance TENA-LVC-Entity, -Fire, -Detonation, -IFF, EntityType as TENA Standard OM candidates in the Collection TENA-LVC-Emission requires further review Although OM aligns with the DIS Standard, it does not represent how users modeland test Emissions today Need use cases of how emissions testing is performed and what it takes to model thisproperlyTENA-LVC-RadioCommunications requires further review The DIS 1278.1-2012 specification defines a Signal PDU with a bitbucket Need more of an interface control / data contract representation What signals need to be represented / modeled?37
In Summary This is the first of many foreseeable drafts of the TENA LVC OMCollection Really need the user community to engage and tell us what is wrong, whatneeds improvement, what should be changed, etcThe TENA LVC OM Collection is NOT intended to support only DISusers DIS support is just the first phase The goal is to support how LVC testing is performed today Are there any other OMs we should consider developing? We plan on holding additional reviews with participation from theuser community to help turn these draft OMs into candidates forconsideration as TENA Standard OMs JTEX-05, December 9 – 12, Charlotte, NC38
Propose to have an LVC OM Collection that is based on the Data Model from the DIS 1278.1-2012 PDU messages Entity State IFF Electromagnetic Emission Fire Detonate Transmitter Signal Promote that DIS TENA DIS round -trip data translations are lossless Integration of this LVC OM Collection would require a mechanism for
