SCA Next1

SCA Next
The Evolution of the SCA

November 10, 2010
Outline
Personal Introduction Objectives Background and History SCA Next Overview Overview of SCA Next Changes Summary PrismTech Products References and Resources Contact Information
Copyright PrismTech 2010
Vince Kovarik
Academic and Publications:
B.S & M.S. Computer Science, Ph.D. Computer Engineering Co-author with John Bard Software Defined Radio: The Software Communications Architecture, Wiley and Sons Chapter author for Cognitive Radio Technology, by Dr. Bruce Fette Awarded three patents
1980s: Harris and Software Productivity Solutions

Experience in Natural Language Understanding, Knowledge Representation and Acquisition and Temporal Reasoning. Initial OO design with Rumbaugh OMT, Booch OOD, and Jacobsen Use Cases. Development work in Smalltalk, LISP Flavors, and C/C++
1990s: STI/Exigent
Initial CORBA work as Chief SW Architect for the Ground Segment of Satellite Command and Control System for IRIDIUM, a large-scale distributed system. Started work in SDR in late 90s as a member of the MSRC. Domain Management ToolKit (dmTK) product manager, the first commercially available implementation of the SCA.
2001: Harris purchases Exigent

dmTK used as initial reference implementation by JTeL and Aeronix for JTAP development. SW Architect for the insertion of the DARPA XG DSA software into the Falcon III Tactical Radio and demonstration. Member of the Government Reference Architecture (GRA) team developing a SysML/UML reference model for SATCOM terminal systems.
Member of the SDR Forum Wireless Innovation Forum since 2000.

Currently chair of the Technical Committee on Advanced Wireless Networking and Infrastructure.
Objectives
This is the first of a series of technologyoriented presentations on the SCA and SDR. The objective of this presentation is to provide:
a historical overview of the SCA and an overview of the SCA Next initiative
Presentations on PrismTechs products in support of the SCA Next and other technology topics will be forthcoming.
Background
Despite rumors of its demise, SCA is alive and well. SCA has been applied successfully to a variety of radio systems including:
JTRS programs of record International radio systems Independently developed products
The international community has been moving forward with SCA, e.g. ESSOR and other programs.
However
The successes have not been without some problems.

Limited portability of waveforms Inadequate abstraction of DSP and FPGA Non-standard Device interfaces for common radio devices, e.g. AudioPort Footprint and performance
Rumbaugh OMT-1
Booch 91 Jacobson OMT-2 OOSE OOPSLA Unified Method 0.8 CORBA IIOP SpeakEasy-1 JCIT SDR Forum SpeakEasy-2 CORBA OMG
1990 Booch 93 Unified Method 0.9 CORBA 2 CCM UML 1.0 MSRC 2000 MDA MOF SCA 2.2 JTRS WDL OO SDR Arch FM3TR
A (partial) SCA/SDR History
CORBA Svcs
LW Log
SCA 2.2.1 OCL MARTE SysML 1.0 SoC SCA 2.2.2 SysML 1.1 SCA CF Impl
Cognitive Radio GNU Radio
UML 2.0 OMG and NCOSE
FM3TR Impl USRP DSA UML 2.3
???
2010
Rumbaugh OMT-1
1990 Booch 93 Unified Method 0.9 CORBA 2 CCM UML 1.0 MSRC 2000 MDA MOF JTRS SCA 2.2 UML 2.0 OMG and NCOSE OCL MARTE SysML 1.0 SoC SCA 2.2.2 SysML 1.1 UML 2.3 Early OO Modeling and Design Methodologies. Enabling standards and organizations. WDL OO SDR Arch Early SDR work. FM3TR
CORBA Svcs
A (partial) SCA/SDR History Enablers
LW Log
Cognitive Radio SCA 2.2.1 SCA CF Impl FM3TR Impl USRP DSA GNU Radio
???
2010
Rumbaugh OMT-1
1990 Booch 93 Unified Method 0.9 CORBA 2 CCM UML 1.0 MSRC 2000 MDA MOF SCA 2.2 JTRS WDL OO SDR Arch FM3TR
CORBA Svcs
LW Log
Cognitive Radio SCA 2.2.1 OCL MARTE SysML 1.0 GNU Radio SCA CF Impl SoC SCA 2.2.2 SysML 1.1
A (partial) SCA/SDR History Critical Mass
Modular Software Radio Consortium: Circa late 1990s Initial origins of the SCA
Early work on waveform and OO SDR architectures and design.
UML 2.3
Stable design formalism. UML 2.0 OMG and NCOSE
FM3TR Impl USRP DSA
???
2010
A (partial) SCA/SDR History Initial Projects

JCIT SDR Forum SpeakEasy-2 SpeakEasy-1 OO SDR Arch Cognitive Radio Circa 2002 JTRS Program initial award of Cluster 1 Ground Mobile Radios (GMR) WDL DSA
10
OMG
CORBA
CORBA Svcs
MSRC
JTRS
SCA 2.2.1
SCA CF Impl
Jacobson OMT-2 OOSE
Rumbaugh OMT-1
CORBA 2
Stable release of SCA released in November 2001
SCA 2.2.2
CORBA IIOP
SCA 2.2
FM3TR Impl USRP
FM3TR
GNU Radio
???
OOPSLA
LW Log
MDA
MOF
Unified Method 0.8
Unified Method 0.9
Booch 93
UML 1.0
UML 2.0 OMG and INCOSE
Booch 91
SysML 1.0
SysML 1.1
Development of MetaObject Facility
OCL MARTE
CCM
SoC
Collaboration initiated with International Council on Systems Engineering to develop Systems Modeling Language (SysML) 2000
1990
UML 2.3
2010
A (partial) SCA/SDR History - Maturation

JCIT SDR Forum SpeakEasy-2 SpeakEasy-1 OO SDR Arch Cognitive Radio DSA
11
CORBA
CORBA Svcs
MSRC
SCA 2.2.1
SCA 2.2.2
CORBA IIOP
SCA 2.2
SCA 2.2 refined and stable. JTRS APIs developed. Initial field testing of JTRS radios. Development of SCA compliant and JTRS certified radios not developed independently of JTRS program. JTRS
OMG
SCA CF Impl
FM3TR Impl USRP
FM3TR
WDL
GNU Radio
Jacobson OMT-2 OOSE
???
Rumbaugh OMT-1
CORBA 2
OOPSLA
LW Log
OCL MARTE
MOF
Unified Method 0.8
Unified Method 0.9
Booch 93
UML 1.0
UML 2.0 OMG and NCOSE
Booch 91
SysML 1.0
SysML 1.1
UML Profiles extend capabilities to capture more domain-specific modeling. MDA
CCM
SoC
Development of SysML to bridge gap between System and Software Engineering. 2000
1990
UML 2.3
2010
A (partial) SCA/SDR History Now

JCIT SDR Forum SpeakEasy-2 SpeakEasy-1 OO SDR Arch Cognitive Radio Initiation of SCA Next activity in Wireless Innovation Forum. Participants represent a cross section of the SCA community. Collaboration with the JTRS Joint Program Executive Office (JPEO) GNU Radio SCA CF Impl JTRS DSA
12
OMG
FM3TR Impl USRP
FM3TR
WDL
Lessons Learned
SysML 1.1 UML 2.3
CORBA
CORBA Svcs
MSRC
SCA 2.2.1
SCA 2.2.2
CORBA IIOP
SCA 2.2
SCA Next
Jacobson OMT-2 OOSE
Rumbaugh OMT-1
CORBA 2
OOPSLA
LW Log
MDA
OCL MARTE UML 2.0 OMG and NCOSE
CCM
MOF
Unified Method 0.8
Unified Method 0.9
Booch 93
Initial joint meeting of JTRS JPEO and WInF held August 2010 in Washington, DC Initial SCA Next rollout at the WInF SDR10 conference 2010
1990
Booch 91
UML 1.0
2000
SysML 1.0
SoC
SCA Next Goals and Objectives
13
Reduce Development Resources

Modification to support more reusability
Reduce Test and Certification Time

The cost of certification is substantial and labor intensive.
Improve Performance
Streamline initialization and deployment
Incorporate Lessons Learned

Apply knowledge gained through experience on existing programs
Independent Effort
14
SCA Next is not a formal project Strong support within the community
JTRS participants Wireless Innovation Forum Independent contributors
Approximately 60 changes were submitted

23 selected for resolution
Focus Areas
15
Platform Independent Specification Increase Compliance Points Better Component / Interface Separation Better Integration of Systems and Software Address Recurring Issues in Design and Deployment
Active Change Requests
16
Requirements Revision Enhance Automated Testing Deployment Optimization Lightweight Components CORBA Neutral / Evolution Architecture Consistency Application Enhancements Nested Apps
Active Change Requests
17
Application Enhancements Interconnected Applications Recommended C++ Features Interface Definition Language (IDL) Refactoring Lightweight AEP Service Deployment and Initialization Component Model Developers User Guide
Requirements Revisions
18
Enhanced Automated Testing Reviewed 123 of 484 OE requirements that do not have an automated test in JTAP and assigned to one of three categories:
Automatable (29 w/ 1 approved) Consider for re-write (58 may not be possible) Consider for removal (27 w/ 3 approved)
Automated Testing Issues
19
Some requirements are difficult if not impossible to force the test condition, e.g.
Raise FileException error on remove operation when a file-related error occurs.
Early versions of JTAP attempted to induce a file-related error by removing the file through a O/S command after opening through the CF::FileSystem. File is not removed until all processes that have an active handle to the file exit.
Push Registration and Static Ports
20
One of the more significant areas of proposed changes. Basic concept is to provide all necessary data with the registration call rather than utilize pull calls from the component receiving the registration call. Provides Ports may be defined as static, i.e. the lifecycle of the Port is tied to the lifecycle of the component and registered with the CF on instantiation.
Static Deployment
Optimize deployment for known radio systems and waveforms. Generate a static IOR for the Provides Port as part of the build process that maps to the target platform. The static IOR provides a priori knowledge during system boot and waveform instantiation eliminating lookup in the Name Service or other repository. Application instantiation time is streamlined by directly connecting the components through the static IORs. Impact to tools, build process and core framework.
21
CORBA Neutral Representation
22
Remove CORBA specific wording Modify SCA interface representation (UML) to one that can be mapped to other technologies Define mapping rules to create existing SCA equivalent. Define mapping rules for a alternate technology.
CORBA Neutral Challenges
23
Refactor the current specification into a well-formed UML model. Developed the initial transformation of the UML-based model into the equivalent CORBA model (PIM PSM) Develop second transformation that accurately maps into an alternate technology
CORBA Evolution
24
Objectives are to define profiles that:

Reduce resources, Allow more freedom to platform designers while still promoting portability Include widely used features
The profiles would apply to applications

The CF, Devices and Services may use (and may require) additional features.
Starting point is Minimum CORBA and CORBA/e

Full and Lightweight Profiles
25
Two profiles planned. Full Provides features for general platforms and applications Lightweight Provides minimal features for highly constrained resources.
Summary of Features
26
Allow additional ORB_init parameters to create a rootPOA with static, non-default policy settings. Any type only allowed in Full profile
Deprecate use of Any and other complex types
Full Profile
27
Similar to CORBA/e with some minor features removed Some features added such as:
Thread Pools Sever Security Model Server and Client ProtocolPolicy
Many of the added features are supported by current ORB vendors including PrismTech
Lightweight Profile
28
Eliminates the Any type and, consequently, does not support the Resource or PropertySet interfaces Only CORBA/e Basic types are recommended intended to enhance compatibility with FPGAs. Minimum management calls supported.
Lightweight Components Basic concept is to support only those interfaces required for a particular object implementation. Considered optional Realization and Inheritance relations. Preferred approach was to use optional inheritance to a common base interface, e.g. Resource. The waveform component would Realize the Resource interface which would have optional inheritance of other interfaces.
29
Resource Interfaces
Lightweight components provide an optional cardinality [0..1] to the generalization/specialization association. Additional interface changes and refactoring of IDL is proposed within this area. Potential impact may be significant.
class Resource Interface CORBAInterface PropertySet + + query(configProperties :Properties) : void configure(configProperties :Properties*) : void + CORBAInterface TestableObj ect runTest(testid :unsigned long, testValues :Properties*) : void
30
Optional inheritance
CORBAInterface LifeCycle + + initialize() : void releaseObject() : void + + +
CORBAInterface Resource identifier: string start() : void stop() : void
CORBAInterface PortSupplier + getPort(name :string) : Object
Wav eform Component
IDL Refactorization Current IDL

class CF Interfaces CORBAInterface PropertySet CORBAInterface LifeCycle CORBAInterface Port CORBAInterface Resource uses CORBAInterface ResourceFactory CORBAInte... TestableObj ect
31
CORBAInterface PortSupplier
CORBAInterface Application CORBAInterface AggregateDev ice uses uses CORBAInterface ApplicationFactory
CORBAInterface Dev ice
uses uses
CORBAInterface LoadableDev ice
CORBAInterface File
CORBAInterface DomainManager
uses CORBAInterface ExecutableDev ice CORBAInterface FileSystem
uses CORBAInterface FileManager
CORBAInterface Dev iceManager
IDL Refactorization
32
The OMG SW RADIO specification used as a starting point Develop separate IDL files for various elements, e.g. Device, LoadableDevice, etc. Minimize the amount of CORBA stub code generated and thereby reduce footprint Retain backward compatibility with the current IDL by incorporating the individual files in a CF module
Summary
SCA Next represents a significant shift in the SCA community. It has been initiated and performed largely by individuals and companies involved with the SCA or the JTRS program. It has been a collaborative effort between the industry participants and the JTRS JPEO. It is intended to be an open, international standard. More work is required to bridge the gap between a recommendation and incorporation into the standard
33
Spectra Support for SCA Next

ORB
CORBA/e Profile Enhanced performance through zero copy High-Performance transport C and C++ ORB support
34
Core Framework
Static deployment and device assignment sequence IDL refactorization Static deployment Push registration
Spectra CX Development Tool

CORBA neutral representation C/C++ code generation Testing automation
Spectra CX Tool
35
Spectra OE Studio
Spectra OE Flexible Architectures
36
GPP
Core Frame work
Waveform Component
DSP
Waveform Component
FPGA
DSP
Waveform Component
FPGA
ICO
e*ORB C & C++
e*ORB C
Extensible Transport Framework
DTP4500 Architecture
37
DTP4500 Hardware
38
RF Front End
Transceiver
Mistral Board with OMAP 35xx
References and Resources
39
SCA: http://sca.jpeojtrs.mil/sca.asp SCA Next: http://sca.jpeojtrs.mil/scanext.asp JTRS APIs: http://sca.jpeojtrs.mil/api.asp JTRS Portability Guidelines: http://sca.jpeojtrs.mil/_downloads/2009122 8_1.2.1_NEDTE_PORT_GUIDE.pdf
Note: This is a single, large PDF file.
Next Technology Webcast
40
When: January 2011 Objective: Explore one or two SCA Next topics in more detail.
Discuss impact and interaction with tooling, development and deployment
Your input is appreciated

Forward questions and topic suggestions to:
vince.kovarik@prismtech.com With SCA Next Webcast in the subject
For Information on Products and Services:
41
E-mail:
info@prismtech.com
www:
www.prismtech.com/spectra
Your PrismTech account manager

42
Thank You Any Questions?

SCA Next1

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SCA Next1

Hochgeladen von

Copyright:

Verfügbare Formate

SCA Next

The Evolution of the SCA

1980s: Harris and Software Productivity Solutions

2001: Harris purchases Exigent

Member of the SDR Forum Wireless Innovation Forum since 2000.

The successes have not been without some problems.

Copyright PrismTech 2010

A (partial) SCA/SDR History

Cognitive Radio GNU Radio

UML 2.0 OMG and NCOSE

FM3TR Impl USRP DSA UML 2.3

A (partial) SCA/SDR History Enablers

A (partial) SCA/SDR History Critical Mass

Early work on waveform and OO SDR architectures and design.

Stable design formalism. UML 2.0 OMG and NCOSE

FM3TR Impl USRP DSA

A (partial) SCA/SDR History Initial Projects

Jacobson OMT-2 OOSE

Stable release of SCA released in November 2001

FM3TR Impl USRP

Unified Method 0.8

Unified Method 0.9

UML 2.0 OMG and INCOSE

Development of MetaObject Facility

A (partial) SCA/SDR History - Maturation

FM3TR Impl USRP

Jacobson OMT-2 OOSE

Unified Method 0.8

Unified Method 0.9

UML 2.0 OMG and NCOSE

UML Profiles extend capabilities to capture more domain-specific modeling. MDA

A (partial) SCA/SDR History Now

FM3TR Impl USRP

Jacobson OMT-2 OOSE

OCL MARTE UML 2.0 OMG and NCOSE

Unified Method 0.8

Unified Method 0.9

SCA Next Goals and Objectives

Reduce Development Resources

Reduce Test and Certification Time

Incorporate Lessons Learned

Approximately 60 changes were submitted

Copyright PrismTech 2010

Active Change Requests

Active Change Requests

Automated Testing Issues

Push Registration and Static Ports

Copyright PrismTech 2010

CORBA Neutral Representation

CORBA Neutral Challenges

Objectives are to define profiles that:

The profiles would apply to applications

Starting point is Minimum CORBA and CORBA/e

Full and Lightweight Profiles

Copyright PrismTech 2010

Copyright PrismTech 2010

Copyright PrismTech 2010

CORBAInterface LifeCycle + + initialize() : void releaseObject() : void + + +

CORBAInterface Resource identifier: string start() : void stop() : void

CORBAInterface PortSupplier + getPort(name :string) : Object

Wav eform Component

Copyright PrismTech 2010