Software defined radio to enable Software defined radio to enable NNEC: NNEC:

Technical challenges and Technical challenges and opportunities for NATOopportunities for NATO

Dr Michael StreetDr Michael Street

2

Operational Impact of NNECOperational Impact of NNEC

Improved combat identificationImproved combat identification Improved communications interoperabilityImproved communications interoperability Improved shared situational awarenessImproved shared situational awareness Improved multinational command, control and Improved multinational command, control and

coordinationcoordination Reduced risk of fratricide and collateral death and Reduced risk of fratricide and collateral death and

damagedamage Improved mutual support between nationsImproved mutual support between nations

Improved combat effectivenessImproved combat effectiveness

3

Wireless system of systemsWireless system of systems

4

SDR to enable NNECSDR to enable NNEC

NNEC needs interoperabilityNNEC needs interoperability

Military need many wireless communications Military need many wireless communications capabilitiescapabilities

Leads to many NATO radio standardsLeads to many NATO radio standards (17 STANAGs for terrestrial radio)(17 STANAGs for terrestrial radio)

Plus national and proprietary systemsPlus national and proprietary systems Interoperability problem for multi-national forcesInteroperability problem for multi-national forces

SDR decouples capability from hardware procurementSDR decouples capability from hardware procurement Improve capability rapidly by fielding new softwareImprove capability rapidly by fielding new software

Not by procuring radios (with a 20+ year lifespan)Not by procuring radios (with a 20+ year lifespan)

Challenges for SDRChallenges for SDR

PortabilityPortability

Interoperability Interoperability

CapabilityCapability

TestingTesting

SecuritySecurity

6

PortabilityPortability

Radio interoperability Radio interoperability Is what NATO cares aboutIs what NATO cares about Radio behaviour is defined by softwareRadio behaviour is defined by software

SDRs running the same software should interoperateSDRs running the same software should interoperate But SDR software will not be But SDR software will not be plug and playplug and play

Radio hardware determined by Radio hardware determined by Size, weight and power supply of the platformSize, weight and power supply of the platform Manufacturer preferences - processor families etcManufacturer preferences - processor families etc

Software is determined by hardware so may not be Software is determined by hardware so may not be portableportable A standard for SDR design e.g. SCA, aids portabilityA standard for SDR design e.g. SCA, aids portability

7

InteroperabilityInteroperability

Multi-national radio interoperability exists due to: Multi-national radio interoperability exists due to: Strict requirements e.g. MC 195/6Strict requirements e.g. MC 195/6 Operational need – and urgent procurementsOperational need – and urgent procurements The same standard being available to allThe same standard being available to all

And takes a long time to establishAnd takes a long time to establish

SDR reduces interoperability … SDR reduces interoperability …

… … unless new SDRs support old ‘legacy’ standardsunless new SDRs support old ‘legacy’ standards

8

CapabilityCapability

State of the art, expensive, power hungry SDRs, State of the art, expensive, power hungry SDRs, supporting only legacy standards does not give supporting only legacy standards does not give any operational benefitany operational benefit

To offer enhanced capability, SDRs need to offer To offer enhanced capability, SDRs need to offer improved capability …improved capability …

… … and this capability must be interoperable and and this capability must be interoperable and securesecure Interoperable – fielded by all nationsInteroperable – fielded by all nations Secure – not using any sovereign cryptographySecure – not using any sovereign cryptography

9

Testing SDRTesting SDR

Aims of NNEC require interoperability Aims of NNEC require interoperability Currently little testing in NATO, only in nationsCurrently little testing in NATO, only in nations

Only the JTeL (US) can certify SCA complianceOnly the JTeL (US) can certify SCA compliance

What is the scope of required SDR testing ?What is the scope of required SDR testing ? Interop / complianceInterop / compliance InfrastructureInfrastructure Representative tests vs range of scenariosRepresentative tests vs range of scenarios

Standards-based products determined by the Standards-based products determined by the testing, not by the standards documents testing, not by the standards documents

10

SecuritySecurity

Military radio requires security functions for Military radio requires security functions for End to end encryption End to end encryption

trans-networktrans-network Link encryption Link encryption

to allow /protect routing & networkingto allow /protect routing & networking Transmission security Transmission security

For robustness For robustness

SDR is reprogrammableSDR is reprogrammable Support different algorithmsSupport different algorithms

Security functionsSecurity functions

End to end crypto

PEPLink &

network Modem RF

VocoderClear voice

Vocoder

Secure data app

Secure voice

Data app PEP

WaveformLink & network layers

End to end cryptoPEP

Link & network

Modem RF

VocoderClear voice

Vocoder

Secure data app

Secure voice

Data app PEP

Link & network

Security Security

function for TRANSEC

OpportunitiesOpportunities

PortabilityPortability

Interoperability Interoperability

CapabilityCapability

TestingTesting

SecuritySecurity

13

PortabilityPortability

SCA – a standard for implementing SDRSCA – a standard for implementing SDR US DoD - developed for JTRS programmeUS DoD - developed for JTRS programme Followed by many national SDR programmesFollowed by many national SDR programmes

Rich, robust, capableRich, robust, capable Non-military suitabilityNon-military suitability

Defined interfaces, APIsDefined interfaces, APIs But not everything has been releasedBut not everything has been released

SCA compliant software can be ported to SCA SCA compliant software can be ported to SCA compliant hardware “easily”compliant hardware “easily” 70 % software reuse, 90% automated70 % software reuse, 90% automated

SCA compliant radios and waveforms fieldedSCA compliant radios and waveforms fielded Including TETRA and APCO-25Including TETRA and APCO-25

14

Legacy InteroperabilityLegacy Interoperability

Software definitions of legacy waveforms will give Software definitions of legacy waveforms will give legacy interoperability legacy interoperability

Widespread deployment of these waveformsWidespread deployment of these waveforms Not technically challenging Not technically challenging

Lessons learned fromLessons learned from STANAG 5066 STANAG 5066 Mil-Std 188-110BMil-Std 188-110B

15

““SCA-based” S’5066 SCA-based” S’5066 ImplementationImplementation

CORBA interface specificationCORBA interface specification abstract object-oriented interface abstract object-oriented interface

applicable to any modemapplicable to any modem remains constant as modem remains constant as modem

implementations changeimplementations change

modified earlier modified earlier hfstackhfstack design and design and implementation:implementation:

separate SW modules for hfstack and separate SW modules for hfstack and route56route56 synchronous serial interface synchronous serial interface

synchronous serial interface further synchronous serial interface further abstracted as a CORBA resource in abstracted as a CORBA resource in accordance with SCA design principlesaccordance with SCA design principles

Stack

Software Defined Radio

STANAG 5066 TCP SIS Interface

cas/ casinterface.h

Channel Access Sublayer

dts/ dtslistener.h

dts/ dtsinterface.h

Data Transfer Sublayer

mac/ maclistener.h

mac/macinterface.h

MAC Sublayer

com/ modeminterface.h

Subnet I nterface Sublayer

cas/ caslistener.h

com/ modeminterface.h

Corba IDL Modem Interface

Corba Modem Adapter

Corba Modem Server

Physical Layer / Software Defined Radio

CO

RB

A

towards an SDR modem implementationtowards an SDR modem implementation initial designs encapsulate route56 driver initial designs encapsulate route56 driver

interface to external modem via interface to external modem via synchronous-serial portsynchronous-serial port

ultimately replaced by SDR modemultimately replaced by SDR modem operates as independent:operates as independent:

HF modem server, registered with CORBA HF modem server, registered with CORBA name servername server

HF stack, which checks CORBA registry HF stack, which checks CORBA registry for available HF modem serversfor available HF modem servers

16

S5066 Software OverviewS5066 Software Overview

SCA design rules dictate modular software structureSCA design rules dictate modular software structure

Module interfaces are a significant part of the softwareModule interfaces are a significant part of the software

hfstackhfstack LayerLayer InterfaceInterface

SISSIS 1.51.5 0.80.8

CASCAS 1.41.4 2.02.0

DTSDTS 3.23.2 4.24.2

MACMAC 4.64.6 0.30.3

COMCOM 0.80.8 0.20.2

CORBACORBA -- 0.30.3

‘‘hfmodem’hfmodem’(i.e., serial interface)(i.e., serial interface) 0.40.4

Total = < 20 KSLOCTotal = < 20 KSLOC 11.911.9 7.87.8

libnc3alibnc3a

Total = ~ 19 KSLOCTotal = ~ 19 KSLOC

sisetherclientsisetherclient

Total = ~ 2.2 KSLOCTotal = ~ 2.2 KSLOC

Modularized/Object-Oriented Code:Modularized/Object-Oriented Code:

17

STANAGs in Software: 5066 STANAGs in Software: 5066

Subnetwork interfaceSubnetwork interface Developed collaboratively within NATODeveloped collaboratively within NATO

Standard & C code available for download, entirely IPR freeStandard & C code available for download, entirely IPR free Provides an exemplar implementationProvides an exemplar implementation

To test againstTo test against As a starting pointAs a starting point As a basis for further developmentAs a basis for further development

Software repository established: Software repository established:

https://s5066.nc3a.nato.int/S5066loginreq/software/https://s5066.nc3a.nato.int/S5066loginreq/software/

Need to follow SCANeed to follow SCA Even for ‘base waveform’ softwareEven for ‘base waveform’ software SCA impacts software designSCA impacts software design

18

Standards in software: 188-110BStandards in software: 188-110B

Data sequence randomizing generator Data sequence randomizing generator (pp. 45, 5.3.2.3.8.1)(pp. 45, 5.3.2.3.8.1)

The data sequence randomizing generator shall be a 12 The data sequence randomizing generator shall be a 12 bit shift register with the functional configuration shown bit shift register with the functional configuration shown on figure 6. At start of the data phase, the shift register on figure 6. At start of the data phase, the shift register shall be loaded with the initial pattern shown in figure 6 shall be loaded with the initial pattern shown in figure 6 (101110101101 (binary) or BAD (hexadecimal) and (101110101101 (binary) or BAD (hexadecimal) and advanced eight times. The resulting three bits, as advanced eight times. The resulting three bits, as shown, shall be used to supply the scrambler with a shown, shall be used to supply the scrambler with a number from 0 to 7. The shift register shall be shifted number from 0 to 7. The shift register shall be shifted eight times each time a new three bit number is eight times each time a new three bit number is required (every transmit symbol period). After 160 required (every transmit symbol period). After 160 transmit symbols, the shift register shall be reset to transmit symbols, the shift register shall be reset to BAD (hexadecimal) prior to eight shiftsBAD (hexadecimal) prior to eight shifts

19

Standards in software: 188-110BStandards in software: 188-110B

if bpc == 2 if bpc == 2 pw = [ 2 1]; pw = [ 2 1]; elseif bpc == 3 elseif bpc == 3 pw = [ 4 2 1];pw = [ 4 2 1];end;% if;end;% if;k = 1;k = 1;for i = 1 :bpc: Nsfor i = 1 :bpc: Ns % --| get scrambling sequence (3 bit number ) % --| get scrambling sequence (3 bit number ) scrambling_seq = sum(p2vect.* [rnd_shifter(10) rnd_shifter(11) rnd_shifter(12)]);scrambling_seq = sum(p2vect.* [rnd_shifter(10) rnd_shifter(11) rnd_shifter(12)]); % --| after 160 symbols, init with the sequence 'bad' and shift 8 times% --| after 160 symbols, init with the sequence 'bad' and shift 8 times if (symb_shift_counter == 160) if (symb_shift_counter == 160) init_PRS_to_defaults;init_PRS_to_defaults; %fprintf('.');%fprintf('.'); elseelse rnd_shifter = shift_by_8 (rnd_shifter);rnd_shifter = shift_by_8 (rnd_shifter); end; %ifend; %if ri = i + bpc -1;ri = i + bpc -1; nu = sum(pw.* input_data(i : ri ));nu = sum(pw.* input_data(i : ri )); m = mod(scrambling_seq + nu , 8);m = mod(scrambling_seq + nu , 8); % --| an array in Matlab is from one so we need to add 1 to m% --| an array in Matlab is from one so we need to add 1 to m % --| channelphase(m+1) represents phase of the signal% --| channelphase(m+1) represents phase of the signal out_data(k) = channel_phase(m + 1);out_data(k) = channel_phase(m + 1); k = k + 1; k = k + 1; symb_shift_counter = symb_shift_counter + 1;symb_shift_counter = symb_shift_counter + 1;end; %for end; %for fprintf('*');fprintf('*');

20

Base waveforms and Base waveforms and interoperabilityinteroperability

Text standards can be ambiguous, software is notText standards can be ambiguous, software is not

Single, high-level, generic software description Single, high-level, generic software description ‘‘Base waveform’ Base waveform’ Could be part of the standardisation processCould be part of the standardisation process Provides a base for porting to a variety of target radio Provides a base for porting to a variety of target radio

platforms. platforms.

Std

Open(filesys)GetParamaters()ConfigureSubSysLoadInitialDataDo BeSDRWhile(exit_trigger)ClearSubSys

ConfigDSPa=0Load(a)Process(a)Shift()XOR(mem,b)a++

101010101010101010101010101010101010101001010101010101010101010101010101010101010101001010101010101010101010101010101010101010101001010

Paper Std Base s/w Target s/w Executable

21

Government and industry rolesGovernment and industry roles

Different role of NC3A and industryDifferent role of NC3A and industry NC3A – high level and generic approach NC3A – high level and generic approach Industry – mature, highly optimized and reliable Industry – mature, highly optimized and reliable

solutionssolutionsOROR

Different type of waveformsDifferent type of waveforms Standards on the paperStandards on the paper Base waveforms - high level code running on GPP. Base waveforms - high level code running on GPP.

Non-real time. Non-real time. NC3A is mainly interested in this NC3A is mainly interested in this activity.activity.

Target waveforms – highly optimised for a particular Target waveforms – highly optimised for a particular radio HW/SW platform. This is the task of the industry.radio HW/SW platform. This is the task of the industry.

NIAG SDR report on business models for SDR NIAG SDR report on business models for SDR

22

Waveform libraryWaveform library

Technical issues are probably easiest to resolveTechnical issues are probably easiest to resolve Languages usedLanguages used

C, C++, Matlab, PythonC, C++, Matlab, Python DSP, VHDL, Obj ?DSP, VHDL, Obj ?

Structure of codeStructure of code SCASCA Design methodology e.g. modularity & conventional Design methodology e.g. modularity & conventional

software practices software practices

Base vs target waveformsBase vs target waveforms Business models and business sectorsBusiness models and business sectors

23

Current library “content”Current library “content”

Base waveforms, SCA based (but not SCA Base waveforms, SCA based (but not SCA certified)certified) STANAG 5066STANAG 5066 MS 188-110B (but not the complete suite)MS 188-110B (but not the complete suite)

RF data capture toolRF data capture tool RF data format for non real-time waveformsRF data format for non real-time waveforms

Functional elementsFunctional elements RF - STANAGs 4203–5 RF - STANAGs 4203–5 MFSK modemMFSK modem B/Q/8-PSK modemB/Q/8-PSK modem Synchronisation functionsSynchronisation functions

24

Future content ?Future content ?

Existing standards planned for further work Existing standards planned for further work Future narrow band waveform (V/UHF)Future narrow band waveform (V/UHF) MS 188-141 (HF ALE) – to complete part of HF houseMS 188-141 (HF ALE) – to complete part of HF house STANAG 4591 – for voice serviceSTANAG 4591 – for voice service

Full content, see paper on waveform library …Full content, see paper on waveform library … Rational assessment of the ‘wish list’Rational assessment of the ‘wish list’ 80 or more waveforms 80 or more waveforms 16 or less 16 or less

Existing software waveforms availableExisting software waveforms available STANAG 4203/4/5c, 5066, MS 188-110B / 141A, TDLs STANAG 4203/4/5c, 5066, MS 188-110B / 141A, TDLs STANAG 4285 (RTO)STANAG 4285 (RTO) STANAG 4538 (BLOSComms AHWG)STANAG 4538 (BLOSComms AHWG) STANAG 4539 (CRC)STANAG 4539 (CRC) STANAG 4444 (FRA) …….STANAG 4444 (FRA) ……. TETRA EN 300-39x (SWE / US)TETRA EN 300-39x (SWE / US) [ SATCOM STANAGs – NC3A for procurement tests ][ SATCOM STANAGs – NC3A for procurement tests ]

25

Radio capabilitiesRadio capabilities

No secure or net-centric tactical radio No secure or net-centric tactical radio interoperability between nations interoperability between nations

Secure

Interoperable

Net-centric

Nothing here

NATO

26

Future waveformsFuture waveforms

Tactical wireless architecture (TN1246) identified Tactical wireless architecture (TN1246) identified need for secure, networking waveformsneed for secure, networking waveforms Narrow band (land) – voice + data, VHF + UHFNarrow band (land) – voice + data, VHF + UHF Wide band (land) – data, UHFWide band (land) – data, UHF

Air-air variants also neededAir-air variants also needed

Narrow band waveform (land) in developmentNarrow band waveform (land) in development Draft STANAG for Layer 1 developed, CAN + DEUDraft STANAG for Layer 1 developed, CAN + DEU Layer 2 being designed – NORLayer 2 being designed – NOR Implementation of Layer 1 on SDR – NC3AImplementation of Layer 1 on SDR – NC3A Layers 1-3 being refined to support RBCILayers 1-3 being refined to support RBCI

27

Radio based combat IDRadio based combat ID

IFF being established and serves air to air and ground to airIFF being established and serves air to air and ground to air Ground to ground, and air to ground not well developedGround to ground, and air to ground not well developed

All rely on transmissions i.e. wirelessAll rely on transmissions i.e. wireless All need interoperability, security and speed All need interoperability, security and speed RBCID imposes very difficult requirementsRBCID imposes very difficult requirements

A to G

A to A

G to G

G to A

RBCI

Mode 5Mode 5

BTID

Rev IFF

/RB

CI

28

Testing SDRTesting SDR

Growing recognition of testingGrowing recognition of testing

Lessons learned from other NATO programmesLessons learned from other NATO programmes E.g. SCIPE.g. SCIP Recognition that testing is costlyRecognition that testing is costly No testing is more costlyNo testing is more costly

Opportunities to collaborate Opportunities to collaborate

29

NATO Security constraintsNATO Security constraints

3 programmable security functions …3 programmable security functions … 100,000 – 1,000,000 lines of code …100,000 – 1,000,000 lines of code … Network connection to other systems ….Network connection to other systems ….

A new, pragmatic approach to SDR security A new, pragmatic approach to SDR security accreditation may be necessaryaccreditation may be necessary Be “risk aware” rather than “risk averse” Be “risk aware” rather than “risk averse”

Nations and vendors recognise the problemNations and vendors recognise the problem Solution needs to be multinationalSolution needs to be multinational

For operational useFor operational use For export marketsFor export markets

No progress, but growing interestNo progress, but growing interest

30

SummarySummary

SDR enables varied capability: SDR enables varied capability: reqs are variedreqs are varied NATO wireless architecture user reqs & operational viewsNATO wireless architecture user reqs & operational views

SCA exists as an accepted standard to aid portingSCA exists as an accepted standard to aid porting Developments still needed e.g. Interfaces and Developments still needed e.g. Interfaces and securitysecurity Long term, international management Long term, international management TBDTBD

S/w waveform library can aid interoperabilityS/w waveform library can aid interoperability Need agreed s/w format Need agreed s/w format Distribution model – industry only, govt supported ?Distribution model – industry only, govt supported ?

Interoperability defined by testing, not standardsInteroperability defined by testing, not standards

31

SDR summarySDR summary

Many nations procuring SDRMany nations procuring SDR National focus is on national waveformsNational focus is on national waveforms Legacy support – needs legacy waveforms in softwareLegacy support – needs legacy waveforms in software

Or will loose interoperability with NATO legacy stdsOr will loose interoperability with NATO legacy stds

New waveforms are neededNew waveforms are needed For NNEC, efficiency and multi-national interoperabilityFor NNEC, efficiency and multi-national interoperability

SDR can aid fielding new waveformsSDR can aid fielding new waveforms Don’t need to replace Don’t need to replace and refit radio and refit radio hardwarehardware Waveform library saves cost and timeWaveform library saves cost and time Common SDR architecture aids waveform sharingCommon SDR architecture aids waveform sharing

SDR needs cooperation to get the full benefitSDR needs cooperation to get the full benefit

32

Thank you Thank you

Michael.Street@nc3a.nato.intMichael.Street@nc3a.nato.int

NSWAN: NC3A CISD TNSRC Street, MichaelNSWAN: NC3A CISD TNSRC Street, Michael

+31 70 374 3444+31 70 374 3444+31 65 142 1275+31 65 142 1275