I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.

Download Presentation

PowerPoint Slideshow about 'SBIR Phase II Discussion 2106' - bernad

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

Here the responsibility of aggregation, although it can be advised by a web service like BASS, is upon the sending federate that owns the models / entities. He must use the aggregated interface / msg. The benefit is a reduction in the amount of messages being generated over the network by one federate.

Here the responsibility of aggregation, although it can be advised by a web service like BASS, is upon the sending federate that owns the models / entities. He must use the aggregated interface / msg. The benefit is a reduction in the amount of messages being generated over the network by one federate.

Here the responsibility of aggregation, although it can be advised by a web service like BASS, is upon the sending federate that owns the models / entities. He must use the aggregated interface / msg. The benefit is a reduction in the amount of messages being generated over the network by one federate.

Entityinstances

Modelsused

SENDER

models

RECEIVER

entities

Interest level

BASS

Aggregate Triggers/Criteria

Proximity to a specific obstacle, entity or feature in the synthetic battlespace;

A change in the level of interest or significance regarding the specific domain a model supports; or

An increase (or decrease) in the physical entity load by the system and/or over the entire federation.

Here the responsibility of aggregation, although it can be advised by a web service like BASS, is upon the sending federate that owns the models / entities. He must use the aggregated interface / msg. The benefit is a reduction in the amount of messages being generated over the network by one federate.

entityaggregation

modelaggregation

SENDER

models

RECEIVER

entities

aggregate solution

Interest level

BASS

Aggregate Triggers/Criteria

Proximity to a specific obstacle, entity or feature in the synthetic battlespace;

A change in the level of interest or significance regarding the specific domain a model supports; or

An increase (or decrease) in the physical entity load by the system and/or over the entire federation.

Here the responsibility of aggregation, which is also advised by a web service like BASS, is upon the recipient federate(s). The idea here is that the messages, once received by the federate, can then be pooled and represented as an aggregate locally by that receiving federate rather than as individual models or object instances that it has to hold in memory. The benefit of this is that it helps reduce the memory load and computing burden for those federate recipients.

Here the responsibility of aggregation, which is also advised by a web service like BASS, is upon the recipient federate(s). The idea here is that the messages, once received by the federate, can then be pooled and represented as an aggregate locally by that receiving federate rather than as individual models or object instances that it has to hold in memory. The benefit of this is that it helps reduce the memory load and computing burden for those federate recipients.

Here the responsibility of aggregation, which is also advised by a web service like BASS, is upon the recipient federate(s). The idea here is that the messages, once received by the federate, can then be pooled and represented as an aggregate locally by that receiving federate rather than as individual models or object instances that it has to hold in memory. The benefit of this is that it helps reduce the memory load and computing burden for those federate recipients.

RECEIVER

Modelsused

Entity Instances

FEDERATE A

models

RemoteEntityinstances

FEDERATE B

entities

Interest level

models

BASS

Aggregate Triggers/Criteria

Proximity to a specific obstacle, entity or feature in the synthetic battlespace;

A change in the level of interest or significance regarding the specific domain a model supports; or

An increase (or decrease) in the physical entity load by the system and/or over the entire federation.

Here the responsibility of aggregation, which is also advised by a web service like BASS, is upon the recipient federate(s). The idea here is that the messages, once received by the federate, can then be pooled and represented as an aggregate locally by that receiving federate rather than as individual models or object instances that it has to hold in memory. The benefit of this is that it helps reduce the memory load and computing burden for those federate recipients.

RECEIVER

Modelsused

Entity Instances

FEDERATE A

models

RemoteInstanceAggs

FEDERATE B

entities

Interest level

aggregate solution

models

BASS

Aggregate Triggers/Criteria

Proximity to a specific obstacle, entity or feature in the synthetic battlespace;

A change in the level of interest or significance regarding the specific domain a model supports; or

An increase (or decrease) in the physical entity load by the system and/or over the entire federation.