Presentation on Smart Graphics

1
Presentation on Smart Graphics

• Frank Farance, Farance Inc.
• 1 212 486 4700frank_at_farance.com

2
Framework For Smart Graphics

• AGR numbers are strawmen
• Joint activities
• IEEE 1484.7 Tool/Agent Communication
• IEEE 1484.7 would be a single document
• AICC Smart Graphics Working Group
• Related activities
• ISO/IEC JTC1 SC25 WG1 ISO 15067-1
• Data and Control Transfer Protocol
• ISO/IEC JTC1 SC32 WG2 ISO 20944
• Metadata Query Service (API features)
• DMSO HLA Simulation

3
A Sample Smart Graphic
Conceptual Model Communicating over a bus
Implementations Can use APIs, protocols,shared
memory, etc., to communicate
4
Smart Graphics Codings, Data Elements
Topic-SpecificInformative Wording
Topic-SpecificNormative Wording
Requirements
Cross-TopicCodings e.g., XML
Various Standards
Functionality
Cross-Topic APIsNormative WordingJava,
JavaScript,C/C, Perl, Tcl, VB
Conceptual Model
Cross-Topic Protocolse.g. Session Layers
Cross-Topic APIsInformative Wording
Various Standards
Semantics
Bindings APIs
Bindings Codings
Bindings Protocols
EncodingsData Formats
Encodings VariousCommunication Layers
EncodingsCalling Conventions
?
5
AGR101 API/Environment

• Main requirements/features
• Session establishment, data transfer,
  subscription/multicast
• Example (not exact syntax)
• H connect ("altimeter 1", "ARINC",
• "10 samples/sec")
• V getvalue(H,atimiter_setting")
• putvalue(H,"altitude", 14250)

6
API/Environment Issues
Environment
Typical Messages - Connect -
GetValue/PutValue - Publish/Subscribe -
Probe features
7
AGR102 Transactions

• Main requirements/features
• Describing common transactions
• Examples
• Definition of initiation and termination of
  graphics objects
• Common data structures in objects
• Common operations render, repaint, print, start,
  stop, restart

8
Transactions
Typical Transaction Definitions -
Initiation - Termination - Render -
Repaint - Print - Start, Stop, Restart
- Error handling
9
AGR103 Protocol Configuration

• Main requirements/features
• Setting up protocol stack
• How is connection specified
• Need to handle standalone/nomadic access
• Session establishment, data transfer,
  subscription/multicast

10
Protocol Configuration
Protocol stack, e.g., ARINC, TCP/IP
Implementations Can use APIs, protocols, etc.,
to communicate
11
AGR104 Element Conversion

• Main requirements/features
• Translation of units, e.g., inches ltgt meters
• Formal definition of units
• Reference to ISO definitions
• Registration of units

12
Element Conversion
Dynamic conversion of elements
13
AGR105 Performance Negotiation

• Requirements and features
• How to probe and determine what features are
  available
• Useful for determining real-time performance,
  e.g., how many samples can send/receive per second

14
Performance Negotation
Determination of network/deviceperformance
parameters
15
Relationship to ISO 15067-1

• Development in ISO/IEC JTC1 SC25 WG1
• Collaboration with IEEE 1484.15 Data Interchange
  Protocols (learning technology-specific)
• Can use variety of encodings, e.g., XML, ASN.1,
  ARINC

16
ISO 15067-1 Protocol
Topic-SpecificInformative Wording
Topic-SpecificNormative Wording
Requirements
Cross-TopicCodings e.g., XML
Various Standards
Functionality
Cross-Topic APIsNormative WordingJava,
JavaScript,C/C, Perl, Tcl, VB
Conceptual Model
Cross-Topic Protocolse.g. Session Layers
Cross-Topic APIsInformative Wording
Various Standards
Semantics
Bindings APIs
Bindings Codings
Bindings Protocols
EncodingsData Formats
Encodings VariousCommunication Layers
EncodingsCalling Conventions
?
17
ISO 15067-1, Protocol-Based
Using ISO 15067-1 (DCTP) to Communicate
18
DCTP Overview

• Data and Control Transfer Protocol
• Intended to be 2-way
• Intended to be low cost, low bandwidth
• Incorporates many security technologies
• Working with IBM, Siemens, BT, Telcordia
  (formerly Bellcore), University of Colorado

19
DCTP Main Features

• Multiple sessions, views, sub-views
• Nomadic sessions for roaming, sometimes-connected
  learners
• Reliable multicast
• Pluggable security
• Low interactivity
• Encoding negotiations, e.g., ASN.1, XML, ARINC
  are possible
• DCTP is not an API

20
Collaboration WithISO/IEC JTC1 SC25 WG1

• Home electronic systems
• Exist for 10 years
• For DCTP, merge work done at BT Labs
• Experience in
• Multicast features
• Firewall/gateway bridges/tunnels
• Multimedia
• Security/privacy
• Incorporation into products

21
Relationship to ISO 20944

• Development in ISO/IEC JTC1 SC32 WG2
• Binding to many languages C, C, Java,
  JavaScript, VB, Perl, Tcl, LISP

22
ISO 20944 Metadata Query Service Is API-Like
Topic-SpecificInformative Wording
Topic-SpecificNormative Wording
Requirements
Cross-TopicCodings e.g., XML
Various Standards
Functionality
Cross-Topic APIsNormative WordingJava,
JavaScript,C/C, Perl, Tcl, VB
Conceptual Model
Cross-Topic Protocolse.g. Session Layers
Cross-Topic APIsInformative Wording
Various Standards
Semantics
Bindings APIs
Bindings Codings
Bindings Protocols
EncodingsData Formats
Encodings VariousCommunication Layers
EncodingsCalling Conventions
?
23
ISO 20944, API-Based
Using ISO 20944 Metadata Query Service (MQS)For
API communication
24
Summary

• Further drafts by 2000-12
• Collaboration with graphics vendors, discussion
  at 2001-01 AICC meeting
• Demonstration of portability