Military and Commercial SDR Same Objectives Different

Military and Commercial SDR – Same Objectives, Different Priorities Steve Jennis – Sr. VP, Prism. Tech OMG SBC Workshop Arlington, VA – Sept 15, 2004

Introducing Prism. Tech

Speaker Profile 4 Speaker: 4 Steve Jennis 4 Sr. VP, Corporate Development 4 Personal Profile: 4 Steve joined start-up Prism. Tech in 1994 after 15 years of international experience in sales, product marketing and management at Texas Instruments Inc 4 Prism. Tech has since evolved from a contract R&D software house to become a world leader in the supply of distributed and wireless software infrastructure products to blue-chip clients in the telecommunications and defense sectors 4 Steve has masterminded Prism. Tech’s overall product strategy, marketing focus and revenue growth. He is a member of the Prism. Tech board. 4 Steve is a Physics graduate of Loughborough University in the UK 3

Prism. Tech Snapshot 4 Market-led software products company 4 Telecom, Defense & Financial “Fortune 500” client base 4 Middleware for Distributed and Embedded Systems 4 50+ people operating in the US and the Europe 4 Aiming to achieve a leadership position in the emerging high-growth market for wireless infrastructure software for Software Defined Radio (SDR) applications, a segment of the overall SDR market, which is set to grow from $700 M in 2002 to over $30 Billion in 2008. Source: Pioneer Consulting. 4

World-Class Customer Base Noki a 5

JTRS Cluster 5 6

Agenda 4 Military and Commercial SDR perceived benefits 4 Same objectives, different priorities 4 Why synergy matters 4 SCA can provide a common basis, but… 4 Middleware vendors must produce “optimized” implementations 4 Conclusions 7

Military and Commercial SDR - Perceived Benefits

Information Sources 4 JTRS Community 4 Hardware vendors 4 Wireless Infrastructure Vendors 4 Market Research Reports 4 Research Projects 4 Commercial Telecom Standardization Efforts 4 Customers 9

SDR Perceived Benefits – Feature Based 4 Re-configurability 4 Application enhancement 4 Enable network resource optimization 4 Evolve with new standards 4 Multifunctional devices 4 Multi-mode 4 Multi-band 4 Shorter time-to-market 4 Differentiated products 4 Backward compatibility 10

SDR Perceived Benefits – Cost Based 4 Lower hardware costs 4 Re-use of devices 4 Use of more “standard” hardware components 4“Agile” wireless software infrastructure 4 Re-use of applications 4 Portable applications – write once, run anywhere 4 Adaptable applications (code reuse) 4 Improved developer productivity 4 Standard APIs, open architectures 4 3 rd party application “plugability” 4 Middleware utilities in COTS products 11

Same Objectives Different Priorities

Military Priorities – All of the Above! 4 Feature-based 4 Re-configurability 4 Application enhancement 4 Enable network resource optimization 4 Evolve with new standards 4 Multifunctional devices 4 Multi-mode 4 Multi-band 4 Shorter time-to-market 4 Differentiated products 4 Backward compatibility 4 Cost-based 4 Lower hardware costs 4 Re-use of devices 4 Use of more “standard” hardware components 4 Adaptable wireless software infrastructure 4 Re-use of applications 4 Portable applications – write once, run anywhere 4 Adaptable applications (code reuse) 4 Improved developer productivity 4 Standard APIs, open architectures 4 3 rd party application “plugability” 4 Middleware utilities in COTS products 13

Commercial Priorities – 3 G BS OEMs 4 Feature-based 4 Re-configurability 4 Application enhancement 4 Enable network resource optimization 4 Evolve with new standards 4 Multifunctional devices 4 Multi-mode 4 Multi-band 4 Shorter time-to-market 4 Differentiated products 4 Backward compatibility 4 Cost-based 4 Lower hardware costs 4 Re-use of devices 4 Use of more “standard” hardware components 4 Adaptable wireless software infrastructure 4 Re-use of applications 4 Portable applications – write once, run anywhere 4 Adaptable applications (code reuse) 4 Improved developer productivity 4 Standard APIs, open architectures 4 3 rd party application “plugability” 4 Middleware utilities in COTS products 14

Commercial Priorities – Drivers 4 Short-term commercial focus on market share and profitability 4 Stock price driven by revenue; less technology premium since 2000 4 Hence focus on cost reduction with only “mandatory” new features for short-term revenue growth 4 Urgent need to reduce base station development effort and cost 4 Improved 4 4 Use 4 developer productivity Standard waveform APIs, open architectures 3 rd party product integration Middleware/platform utilities in COTS middleware of “standard” components GPPs, DSP, FPGAs versus fully custom and ASIC 4 Continuous need to be first to market with next-generation products to increase market share 4 Shorter time-to-market 4 Medium-term need to support more waveforms in same base station (without costs rocketing) 4 Multifunctional devices 15

Why Synergy Matters

Benefits of Commercial Take-Up to Do. D 4 JTRS JPO has a long-held goal of fostering COTS middleware products supporting the SCA specification 4 Military SCA OE Implementations 4 To reduce implementation complexity and customization (e. g. in the integration of RTOS, middleware, core framework, tools, etc. ) 4 To provide a choice of SCA COTS products for radio vendors 4 To allow radio vendors to focus on application “value-add”, not rebuilding infrastructure 4 Commercial Telecom SDR OE Products 4 To generate a commercial “critical-mass” for SCA-derived wireless infrastructure products – security of supply, lower costs 4 To feedback implementation experience and new technology from commercial software infrastructure into SCA products 4 To prevent the SCA being “marginalized” by alternative commercial approaches that are unsuitable for defense applications - and thus increase long term costs. 17

Benefits of SCA “Take-Up” to Telco Sector 4 Don’t reinvent the wheel – optimize it for your vehicle! 4 Waveform APIs (yes, even defined in CORBA IDL) can be directly re-used 4 Small form-factor Cluster 5 radios will “prove the SCA concept” for highly resource-constrained devices 4 Benefit from $Ms of military R&D invested in SCA middleware 4 Middleware scaleability is build-in – OMG beware… 4 International standardization effort underway via OMG SBC DTF 4 Credible middleware vendors already exist 4 Focus on added-value through new application features and lowering costs 18

Benefits of SCA “Take-Up” to Vendors 4 Broader market access leads to 4 High sales volumes for standardized products 4 Greater overall market share in SDR 4 Greater internal efficiencies – lower support costs 4 Cross-fertilize technical advances – feature enhancement 4 World-class technology 4 Serving customers better 19

SCA Can Provide a Common Basis, But…

SCA Origins and Objectives 4 US Do. D awarded a contract to the Modular Software Radio Consortium (MSRC) in late 1998 to develop a wireless software infrastructure specification which would be publicly available, open, non-proprietary and specify common radio interface formats 4 Successful MSRC Consortium included BAE Systems, Raytheon, Rockwell Collins ITT and others 4 Objectives 4 To facilitate waveform reuse and portability 4 To enable radio flexibility 4 To pioneer a “Windows-style platform” for SDR applications 4 To provide functionality not yet addressed by the commercial telecommunications sector 4 To foster competitive, yet interchangeable implementations 21

SCA Specification Maturing 22

SDR Origins & Evolution 1995 1986 1992 First SCA Based Radio Speak. Easy I 1989 JTRS Cluster 5, AMF Cluster & futures 2001 1995 1999 2002 1991 Courtesy of 23

SCA Specification Maturing 4 Currently v 3 4 Elements of the SCA specification being formally “standardized” through the Object Management Group SBC Domain Task Force (OMG) 4 On-going refinement through the JTRS Joint Project Office (JPO) 4 Including extension to the radio’s signal processing sub-system (SPSS), i. e. firmware resident on (re)programmable processors such as DSPs and FPGAs 4 Practical implementation feedback 4 Testing and compliance facilities established for JTRS suppliers (JTel) 24

Middleware Vendors Must Produce Optimized “SCA” Implementations

SDR Operating Environment (OE) 26

Optimized Products 4 For JTRS 4 SCA specification “granularity” 4 Optimized ORBs (e. g. e*ORB SDR) 4 Optimized core framework 4 Optimized development tools 4 Optimized integrated SCA Operating Environment 4 For commercial telecom OEMs 4 OMG SBC specification “granularity” 4 Optimized basestation middleware 4 Optimized development tools 27

Conclusions 4 Huge market opportunity for “SCA-derived” middleware beyond military – will benefit all SDR professionals 4 Do. D and Military contractors will benefit 4 Focus for commercial telecom will remain on cost saving through 3 G roll-out 4 Onus on OMG to ensure “flexibility” of SCA/SBC specs 4 Onus is on middleware vendors to “package” SCA/SBC-complaint middleware for different markets 4 Military radio OEMs need to view SCA as a product, not a “project” infrastructure - to achieve critical mass and “prove” SCA for broader markets 4 Timing is right, basestation vendors are re-looking at architectures for 3. x G – handsets/terminal designers look to basestations for technology guidance (+2 -5 yrs) 4 OMG SBC has the opportunity to be at the centre 28

About Prism. Tech 4 Visit our booth or with 4“Sam” Aslam-Mir - CTO 4 Andy Foster – e*ORB product manager 4 Murray Conarty – Account executive 4 Visit Prism. Tech’s Website at: 4 www. prismtech. com 29