IOBC Architecture

Report
ARINC 830 AGIE
Specification Outline
&
Notes
By: Rick Wilber – Boeing – 206-931-5561
With: Wolf Sonnenberg – Teledyne - 310-765-3745
Version: June 14, 2013
ARINC 830 Committee Discusions – Sept 2011 | 1
ARINC 830 Specification Notes
Goal is full draft in June and final in October
The specification has been updated per 5/29/13 Telecon
•
•
Spec changes for preparation
• Reformatted diagrams
• Bold & italics to see “shalls”
• Cleaned up AMQP references
• Fixed various typo’s & word-smithing
• Wolf made significant contributions to wording in section 1-3
Added TBD
Status
•
•
•
•
Sections 1, 2 & 3 are complete with actions
Section 4 & 5 are draft ready for review except where noted
Section 6 is structurally complete with interfaces placeholders
Appendices
• Glossary is complete
• Threads ready for review & tighter mapping to AMPQ appendix
• AMQP thread mapping is placeholder
2
Spec Top Level Section Outline
1.
2.
Introduction
Purpose & Objectives
•
•
•
3.
4.
5.
6.
7.
A.
B.
C.
D.
All business and level discussions
Introduction oriented not technically oriented
No shalls
AGIE Overview
•
•
•
•
Overview capabilities from user perspective
User oriented not technically oriented
Describe operational concepts, approach
No shalls
•
•
•
•
Operators perspective
All operational shalls
No functions
How to use AGIE
Appendices
Glossary
Threads
AMQP thread mapping
AGIE Interface Definitions
Papers references
1.
2.
3.
Functional specification
•
All technical discussions with functional view 4.
•
Developer focus
5.
•
All functional shalls
6.
AGIE Operations
Considerations for AGIE
Certification and Approval
AGIE DNS Use
Deferred AGIE Features
AGIE Demonstration and
Testing Scenarios
AGIE Topologies
AGIE Use Cases
Protocol interfaces
•
•
•
•
•
Functional interfaces between components
Functional interfaces to external components
XML interfaces for messages
Database descriptions
No shalls
3
ARINC 830 Specification Status
Major writing tasks remaining
•
AMQP section development
• 4.6.4 function mapping
• 5.1.1 operational considerations
• Appendix C thread mapping for functional flows
• Will cause Appendix B update
1. Validate protocol & interface lists
2. Describe protocols & interfaces
• Client XML interface templates
• Coordination interface templates
• Coordination database definitions
3. Appendix D AGIE interface definitions
• Each XML, coordination message & database will defined
4
ARINC 830 Specification Status
Major review tasks remaining
•
•
•
•
Section 4
• Review all concepts
• Validate all requirements
• Fill in TODOs
Section 5
• Review all concepts
• Validate all requirements
• Fill in TODOs
• Ensure appropriate scope (need ops inputs)
Section 6
• Review concepts & text
• Validate interface lists
• Define each interface & protocol
• Validate them against sections 4 & 5
Appendices
• After AMQP threads update AGIE threads
• After XML definitions make sure semantics flow
5
Section Status
1.
Introduction
1.
2.
3.
4.
5.
6.
2.
Purpose
Scope
Overview
Related documents
Regulatory
Compliance
3.
AGIE Overview
1.
2.
3.
Purpose & Objectives
1.
2.
3.
4.
5.
Objectives
Benefits
Approach
1.
Data exchange
2.
Concept of operations approach
3.
Development & validation
4.
Interoperability
Policy considerations
•
Operational (cost, performance, QoS)
•
Certification & approval
Security approach
4.
5.
6.
7.
Key
Placeholder – no or limited text
Partially complete – some text, more work needed
Draft - all text ready for initial review
Final Review – completed waiting for final review
Complete – updated only as errors, changes required
General description
•
Client-server
•
Service oriented
•
Priorities, paths, naming
concepts
Terminology
Architecture & topologies
•
Components, functions,
interfaces
Admin concepts
Messaging operations
Principles of operation
1.
AGIE organization
2.
Connection management
3.
Protocol binding
4.
Addressing
5.
Data delivery
6.
Prioritization
7.
Message management
List of operations
6
Section Status
4.
6.
Functional specification
1.
2.
3.
4.
5.
Top-level capabilities
Architecture
1.
Clients
2.
Servers
3.
Topologies
4.
Cross domain
5.
AGIE-AMQP
6.
Architectural security
Paths & routing
1.
IP routes
2.
Connections
3.
Paths & selection
Messaging & delivery
1.
Interface
2.
Attributes
3.
Services
4.
Flow control & priorities
Naming & addressing processing
1.
Name space
2.
Considerations
3.
AGIE descriptor
4.
Parsing
5.
Name resolution
6.
Address resolution
7.
AGIE name service
7.
5.
AGIE functions
1.
Client functions
2.
Server functions
3.
System and Primary functions
4.
AMQP functions
Security requirements
AGIE Operations
1.
2.
3.
4.
5.
6.
7.
System setup
1.
AMQP configuration
Configuration management
Naming
Priorities
Paths
Security & partitioning
Use case overview
Key
Placeholder – no or limited text
Partially complete – some text, more work needed
Draft - all text ready for initial review
Final Review – completed waiting for final review
Complete – updated only as errors, changes required
7
Section Status
6.
Protocol interfaces
1.
2.
3.
XML interfaces
1.
App-client-host interface XML
2.
Host-to-AGIE client-to-app XML
Coordination messages
•
Server – server
•
Sort list of services
Coordination databases
1.
Clients DB
2.
Servers DB
3.
Current associations DB
4.
Connection profiles DB
5.
Current paths DB
6.
Message types DB
7.
Best Path selection Table DB
7.
Appendices
A.
B.
C.
D.
Glossary
AGIE Threads
AMQP thread mapping
AGIE interface definitions
Key
Placeholder – no or limited text
Partially complete – some text, more work needed
Draft - all text ready for initial review
Final Review – completed waiting for final review
Complete – updated only as errors, changes required
8

similar documents