search

AMSP-04 / NETN-ORG

NATO Education and Training Network (NETN) Organisation (ORG) Module
Other
1 stars 1 forks source link

Communication Network #35

Closed LennartOlsson closed 4 years ago

LennartOlsson commented 4 years ago

A new attribute: Unit.CommunicationNet

Datatype, a fixed record with: Service (EnumCommunicationServiceType) (HLAinteger32BE) Id (HLAunicodeString)

LennartOlsson commented 4 years ago

Shall be a list with communication networks. A new attribute: Unit.CommunicationNetworks. A list of UniqueIds or FixedRecords?

Maybe we need a new Object Class: CommunicationNetwork, with attributes: UniqueId (UuidArrayHLAbyte16) Service (EnumCommunicationServiceType) (HLAinteger32BE) Id (HLAunicodeString) or shall the definition of a network be a specified in a FixedRecord?

Where shall such an Object Class be defined, in ORG or COM?

In the MSDL specification are networks defined as network instances at Units and not as individual instances. Networks does not have UUID in the MSDL. A UUID of Type-3 can be generated from the Id provided by the MSDL file. This UUID will be unchanged between different federation executions.

LennartOlsson commented 4 years ago

Previous comments are outdated!

CommunicationNetwork Instances in ORG FOM module

CommunicationNetwork instances is indirect defined in MSDL at the Unit definition, (UnitType.CommunicationNetInstances). CommunicationNetwork instances is refereed from an EquipmentItem in MSDL, (EquipmentItemType.CommunicationNetReferences).

In MSDL is the Communication Network instance identified by a String, not an UUID.

A producer of the identifier shall save it in a MSDL-file.

The ORG FOM module is highly associated with MSDL today. Applications that publish the ORG FOM data can normally manage MSDL.

The definition of a Communication Network instance should be placed in the ORG FOM module and contain static attributes. The dynamic attributes like MaxReach shall be managed in the COM FOM module. COM FOM data for Network instances which is fetched from the definition in ORG FOM can be published in the same way as NETN_Aggregate instance data fetched from the definition at ORG FOM Unit instance.

Approaches: 1. In MSDL, update ‘CommunicationNetInstanceType’ with a new attribute: name="ObjectHandle" type="msdl:patternUUID32"

In ORG FOM module, add object class: ORG_Root.CommunicationNetwork with attributes: UniqueId (inherit) Name (inherit) Service (CommunicationServiceTypeEnum32) Owner (Uuid, a Unit)

A UUID can be generated by the application that defines the instance and save in a MSDL formatted file.

2. Use the already specified Name in MSDL as the identifier (seed) and in application that publish the COM FOM module generate a UUID of Type-3 and assign it to COM_Root.Network instances.

In ORG FOM module, add object class: ORG_Root.CommunicationNetwork with attributes: Name (inherit) Service (CommunicationServiceTypeEnum32) Owner (Uuid, a Unit)

A UUID of Type-3 can be generated from the Name provided by the MSDL file. This UUID will be unchanged between different federation executions.

Is there a need for a new attribute: Unit.CommunicationNetworks, (list of UniqueIds or Strings)? Or is the owner attribute enough?

LennartOlsson commented 4 years ago

image

LennartOlsson commented 4 years ago

Communication Network is represented with a Fixed Record. Unit has a list with Communication Network instances. EquipmentItem has a list with references to Communication Network.