Transcript No Slide Title
Software Communications Architecture and Related Specifications Overview
Kevin Richardson 09 April 2006 1
What is An Architecture?
It is an Enabler
• Definition of Software Architecture: A software architecture is characterized by a particular combination of software components and connections .
The SCA provides a framework, not functionality. • The JTRS Software Communications Architecture(SCA) Enables: – porting of “waveforms” – reuse of software (largely internal to development organization) – extensibility of hardware and software (emphasis on modeling) – interoperability between platforms – use of commercial product lines (as it gains commercial acceptance) 2
What is the SCA?
• The JTRS SCA specifies an open, non-proprietary architectural framework – Independent of waveform functionality – “Component oriented” – profiles describe HW / SW components – Defines SW Interfaces for data connection and management control
R F
D o m a i n M g r POSIX CORBA – Defines a common management framework • to configure, connect and tear-down distributed applications FPGA DSP DSP GPP GPP GPP Devices 3
How can the SCA Benefit DoD?
RF Analog ADC To Applications R F
POSIX CORBA GPP GPP FPGA DSP DSP GPP Devices D o m a i n M g r
“same” waveform software runs on different hardware sets R F
FPGA DSP POSIX CORBA GPP GPP Device s 4 i D o a n M g r
Criteria for the SCA
– Based on Open, Commercial Standards • OMG, IEEE, IETF – Supports a Family of Radios • Interoperable, • Programmable • Scaleable (handheld to fixed-station), – Maximizes Platform Independence of Software from Hardware • Application and Device Portability & Reuse • Rapid Technology Insertion Over Time – Extendible to New Waveforms and/or Hardware Components 5
SCA Software Structure
Operating Environment (OE) Applications Core Framework (CF) Commercial Off-the-Shelf (COTS) RF Non-CORBA Modem Components Physical API Modem Components Modem Adapter MAC API Non-CORBA Security Components Non-CORBA I/O Components Link, Network Components Security Adapter LLC/Network API Core Framework IDL Security Components Security API Security Adapter Link, Network Components LLC/Network API (“Logical Software Bus” via CORBA) I/O Adapter I/O Components I/O API CORBA ORB & Services (Middleware) CF Services & Applications Operating System Network Stacks & Serial Interface Services Board Support Package (Bus Layer) Black Hardware Bus CORBA ORB & Services (Middleware) CF Services & Applications Operating System Network Stacks & Serial Interface Services Board Support Package (Bus Layer) Red Hardware Bus
6
The SCA “Model”
• • • • Software – Operating Environment • POSIX-based operating system (OS) • CORBA / Interface Definition Language (IDL) • JTRS Core Framework (CF) • Domain Profile (XML-based) Hardware – Classes (Operations and Interfaces) Rules for Implementation – How the Architecture is applied to products The SCA does not … – specify implementation-level details – define all the elements or interfaces for a SDR – guarantee portability 7
SCA Core Framework Definition
• • The SCA CF is a “core” set of interfaces that provide an abstraction of the underlying software and hardware layers for software application designers CF Interfaces (defined in IDL) consist of: -
Base Application Interfaces
(
Port, LifeCycle, TestableObject, PortSupplier, PropertySet, ResourceFactory,
and
Resource
) that can be used by all software applications
Framework Control Interfaces
(
Application, ApplicationFactory, DomainManager, Device,
LoadableDevice, ExecutableDevice, AggregateDevice,
and
DeviceManager)
that provide control of the system
Framework Service Interfaces
(
File, FileSystem, and FileManager
)
that provide interfaces for distributed file access services to software application components
Domain Profile
that describes the properties of hardware devices and software components in the system and enables application deployment 8
Platform Mangement
Power activates: OS ORB Device Managers 1 Domain Manager
All Dev Mgrs report to Dom Mgr DCD 1 Domain Mgr 1 Device Mgr per CORBA-capable processor Each Device Manager responsible for booting its Devices and Services DCD tells Dev Mgr what HW devices exist C O R B A
CORBA-capable processor Domain Manager Device Manager
Hardware Devices Hardware Devices Hardware Devices • 1 Domain Mgr per JTR Set • 1 Device Mgr per CORBA Capable processor • Device Mgr starts up its device (in parallel) • Primarily works at “power on” 9
DCD defines characteristics of devices to be loaded
Domain Mgr Knows Devices, Applications, & Resources
HMI access uses Dom Mgr HMI SAD describes the components that comprise an application Domain Manager One Dev Mgr per CORBA capable processor An App Fac is created for each installapplication, i. e. SAD DCD Device Manager Application Factory SAD Application Hardware Devices On starting Application • • • •
XML Profiles provide application Metadata “resource” + Software Profile Descriptor = a “component” “install” creates an Application Factory An Application Factory starts up an Application instance
10
Resource
Start Stop Initialize Release Run Test Control Data
Collection of Functionality Programmer-Defined
User-Defined Interfaces Get Port • A resource “packages” together object code that runs within a processor • Provides set of “control” operations (primarily used by Core Framework) • Functionality and Interfaces (ports) are supplied by programmer 11
Device
Load Execute Start Stop Initialize Release Run Test Control Data
Collection of Functionality Programmer-Defined
User-Defined Interfaces Get Port State Aggregate Hardware • A Device IS a resource that provides a HW abstraction • State reflects state of the hardware: Usage, Admin, Operational 12
Core Framework IDL Relationships
<
Port
<
PropertySet
<
DeviceManager
<
PortSupplier
<
Device
<
LoadableDevice
<
ExecuteableDevice
<
LifeCycle
Implemented as Core Application Services Core Framework Interface Legend Implemented by Non-Core Applications Core Framework Interface
<
TestableObject
<
PropertySet
inherits from
<
Resource
uses
<
ResourceFactory
<
Application
<
ApplicationFactory
use s app lic ati 0..* on s
<
AggregateDevice
<
File
0..* devices 1..* deviceManagers 0..* applicationFactories
<
DomainManager
Base Application Interfaces Framework Control Interfaces 0..1
fileSys
<
FileSystem
1 fil eMgr Framework Services Interfaces
<
FileManager
13
SCA Base Application Interfaces
• Port – used to connect Resource Components • LifeCycle – used to initialize or release Resources • TestableObject – used to test a Resource • Port Supplier – used to obtain a specific port • PropertySet – provides operations to access Resource properties • ResourceFactory – Used to create / tear down Resources • Resource – provides common interface for Resource control and configuration 14
SCA Framework Control Interfaces
• Application – CF provided container for Resources that make up application • provides interfaces for control, configuration, status and tear-down • ApplicationFactory – used to create application (waveform) instances – based on Domain Profile • allocates SW (Resources) to HW (Devices) - allocates capacities • connects Resources that make up application • performs initial configuration • DomainManager – Provides interface for DeviceManager, Device and Application registration – Provides access to registered DeviceManagers, installed and Running applications, the platform’s FileManager – Provides interface to HCI to access the domain and its capabilities (Devices and Applications) 15
SCA Framework Control Interfaces (cont.)
• Device – A software proxy for a physical hardware device – Represents CF interface between applications and devices – Typically one Device per HW device – Loadable, Executable, and Aggregate Devices extend behavior of the Device Class • DeviceManager – Manages a set of logical Devices and services 16
SCA Framework Services Interfaces
• File – Provides access to files within the radio – Allows access across processor boundaries (distributed file systems) • FileSystem – Enable remote access to physical file systems – Allows creation, deletion, copying, etc of files • FileManager – Manages multiple distributed FileSystems – Looks like a FileSystem to client 17
SCA Domain Profile
• A set of files that describe HW and SW components making up an SCA system domain • eXtensible Markup Language (XML) format • Document Type Definitions (DTDs) describe the files [Customized to better address Software Radio Needs] 18
SCA Status
• SCA is being accepted by Industry – An “SCA equivalent” exists within the family of OMG Standards – Commercial tool vendors and industry have provided some SCA tools • PrismTech, Zeligsoft and CRC • The SCA has undergone three phases of architectural validation and provides the backbone for JTRS Cluster 1 • The SCA and its underlying technologies target a GPP based platform however many of the abstractions are applicable to other processing environments • The JTRS program office has a plan in place to continue to evolve the SCA 19
Software Communications Architecture
Schedule for standardization of SCA related specifications at the Object Management Group (OMG) Specification Adoption July 03 Nov 03 Nov 03 Feb 04 June 04 Finalization
Formal spec Adopted spec Finalized spec
Note: All dates represent estimated OMG schedules Jul 04 Nov 04 April 05 Sep 05
20
SWRadio MDA Principles
• UML Profile for SWRadio extends UML for SWRadio tool support: validation, system engineering, and SWRadio component development • PIM has been primarily structured as a set of facilities each addressing a key aspect of SWRadio • Well-defined set of modeling conventions – Naming conventions – Modeling conventions – Subset of UML notation – Specific semantics of this notation in the context of this PIM • Conforms to MDA – PIM can be transformed to different component platforms • CORBA-PSM, Java-PSM, etc.
• Compatible with existing OMG standards – MOF – UML 21
SWRadio MDA Principles, cont’d
Meta-Meta-Model Layer (M3) Meta Object Facility (MOF) Meta-Model Layer (M2)
«instanceOf» «extends»
OMG UML
Domain & Platform Technology profiles
UML Profiles for SWRadio, CORBA, Java, C++, XML Schema
Profiles M1 Data
PIM & PSM Layer (M1)
«instanceOf»
Waveform, Device, Radio Infrastructure & Service Components PIMs
«instanceOf» «refine»
Waveform, Device, Radio Infrastructure & Service Components PSMs, CF Interfaces, XML Descriptors
«instanceOf»
Runtime or Deployed Artifacts Layer (M0) Waveform, Device, Radio Infrastructure & Service PSM Components & Artifacts (XML Descriptors, Executables)
22
SWRadio Development Viewpoints
• To address the issues of the different actors involved in SWRadio product developments, the current profile was developed with three main viewpoints in mind: – the viewpoint of application and device developers, – the viewpoint of infrastructure/middleware providers, and – the viewpoint of SWRadio platforms providers.
• These three viewpoints define distinct sets of concepts (and stereotypes) that are required in different contexts.
23
SWRadio Development Viewpoints, cont’d
Infrastructure Providers Application and Device Providers SWRadio Platform Providers PIM Facility +commEquipment +deviceDriver DeviceDriver +deviceDriver
CommEquipment
RadioSet LogicalCommunicationChannel Radio Services Element Definitions +logicalDevice 1..* DeviceComponent ApplicationResourceComponent Radio Management RadioSystem Application Deployment (from SWRadio Deployment) +componentAssembly +appComponent Application Radio Control Facilities (from Facilities PIM) Common Radio Facilities (from Facilities PIM) Data Link Layer Facilities (from Facilities PIM) Common Layer Facilities (from Facilities PIM) Physical Layer Facilities (from Facilities PIM) 24
UML Profile for SWRadio
Communication Equipment Application and Device Components Infrastructure • To be consistent with the three development viewpoints, the UML Profile for SWRadio is partitioned in three main packages: – the Applications and Devices Components, – the Infrastructure, and – the Communication Equipment package. • Each package defines the set of concepts and UML stereotypes required to perform a specific role in the development of an SWRadio product.
25
• • • • • •
UML Profile for SWRadio Application & Device Components
Application Components – Contains the component stereotypes for application developers – Application, ApplicationResourceComponent, LayerResource (Data Link, MAC, Physical) Base Types – Contains the common types for defining SWRadio components.
Interface & Port Types – Contains the port and interface stereotypes for SWRadio interfaces and components Device Components – Contains the component stereotypes for device developers – Logical Device, Loadable and Executable Properties – Contains property stereotypes for SWRadio components – Configure, Query, Characteristic, Capacity Resource Components – Contains the interface and component stereotypes for waveform and device developers – ControllableComponent, LifeCycle, PropertySet, ResourceComponent, etc.
26
UML Profile for SWRadio Resource Components
<
UML Profile for SWRadio Infrastructure
• Radio Services – Common services within the radio platform that are utilized by applications – Managed component service • Radio Management – RadioSet, RadioSystem, and Device Management • Communication Channel – Physical, IO, Security, and Processing Channel – Captures the relationships between channels and SWRadio devices • Application Deployment – Components and Artifacts stereotypes for the deployment of: • Waveforms on communication channel’s distributed devices • Radio Services within the Radio Set 28
UML Profile for SWRadio Infrastructure, cont’d
<
<
UML Profile for SWRadio Communication Equipment
• Stereotypes for SWRadio devices • Communication Equipment describes the relationships and attributes that are appropriate for radio devices.
– Crypto Device - performs encryption and decryption on asset of data.
– I/O Device - describes the relationships and attributes that are appropriate for I/O devices • Antenna, Amplifier, Filter, Frequency Converter, audio, serial, etc.
– Power Supply provides electrical power to other devices.
– Processor Device - processes digital or analog data.
• Port Types – Analog & Digital • Property Types – Characteristic & Configure 30
UML Profile for SWRadio Communication Equipment, cont’d
<
<
SWRadio PIM Facilities
• Common Radio Facilities – Provides common service definitions that are applicable for all applications (waveforms or radio control) – File Services, OMG Lightweight Services (log, event, naming, etc.) • Common Layer Facilities – Provides interfaces that cross cut through facilities that correlate to layers. These interfaces can be viewed as building blocks for SWRadio components that realize multiple interfaces.
– Protocol Data Unit, Error Control, Flow Control, Measurement, Quality of Service, and Stream Facilities 32
SWRadio PIM Facilities, cont’d
• Data Link Facilities – Link Layer Control (LLC) facilities. LLC layer provides facilities to upper layers, for management of communication links between two or more radio sets. – Data Link Layer (Connectionless, ConnectionLess Ack, Connection), and Medium Access Control Facilities • I/O Facilities – Defines the configuration properties for Audio and Serial Facilities 33
SWRadio PIM Facilities, cont’d
• Physical Layer Facilities – Modem Facilities • The modem facilities include all digital signal processing elements required to convert bits into symbols and vice versa. – RF/IF Facilities • The RF/IF Facilities is used to configure and control the basic devices of the physical channel. The granularity at which these interfaces are implemented is not specified.
• Radio Control Facilities – Provides for interfaces for radio and channel management.
34
SWRadio PSM
• Automatic PSM generation from PIM and profile definitions – Transformation rule set specified in the specification • Platform Specific Model – CORBA Modules • CF – StandardEvent, PortTypes • DfSWRadio – CommonLayer, DataLinkLayer, CommonRadio, PhysicalLayer, RadioControl • DSFileServices – XML Schema • Properties • Communication Channel • Physical Layer Properties – POSIX • Other PSMs could be defined 35
SWRadio Lessons Learned
• Benefits – Promotes separation of design / development concerns • Nothing new (good SW Engineering principles) – MDA approach requires more formal/complete models • Enables artifact generation • Impediments to adoption – Lack of tools (transformation, generation, UML extension, MOF infrastructure) – Programmatic conflicts exist regarding integrating new specs into an existing product family 36
Summary
• The SCA provides a platform and development language independent architectural framework upon which SDR (and other distributed, component based) applications can be built.
• The underlying platform independent SCA model has been emphasized in areas such as the OMG family of specifications • The SCA “works” however there are areas for evolution – Resource Constrained processing environments – Extendiblity into other platform specific middlewares and OEs 37