PIPES

Copyright © 2010 Software Defined Radio Forum, Inc. All Rights Reserved
Wireless Innovation Forum
Policy Information Processing Exchange Systems
(PIPES)
June 23rd, 2010
Mainz Meetings
WINNF Contribution

PIPES: Communications for Users
George Bernard Shaw
“The problem with communication ... is the
illusion that it has been accomplished.”
Robert McCloskey
“I know that you believe you understand what
you think I said, but I’m not sure you realize
that what you heard is not what I meant”.

PIPES: Project Objectives
Policy: Typically described as a principle or rule to guide decisions
and achieve rational outcome.
Information Processing: is the change (processing) of information in
any manner detectable by an observer
Exchange: To give something, get something, swap, share or replace
something
Systems: complex whole formed from related parts: a combination of
related parts organized into a complex whole
PIPES: Development of a notional architecture based on the belief
effective communications imparts knowledge, and is based on sharing
information in the appropriate context.
Context: the circumstances or events that form the environment within
which something exists, takes place, or is understood.

Policy-Based Operation
Policy-based operation is a condition-action response
mechanism
• Provide automatic responses to conditions in the network
according to pre-defined policies
Translate end-to-end goals to system language
• Manage network resources through policies
Quantify QoS requirements for:
• Different applications (voice, video, data)
• Different users and their corresponding purpose
• Public safety network requires high reliability
Hierarchical organization/structure:
• Define command structure and mission profiles
• Priority levels for information distribution
• Security privileges (authentication & authorization)

Derived from work on the DARPA QNT Program 2005
Policy Information Processing Exchange Systems
Evolution to Policy Based Information Systems
• SDR à Software Defined Radios are reconfigurable
• CR à Cognitive Radio are SDR that are adaptive, primarily on
the signal and space layers of the communications link - based
on spectral and geospatial policies
• PIPES à Policy Information Processing Exchange Systems are
SDR platforms that are adaptive based on end-to-end
processing and exchange requirements for information
exchange in the native domain of the user.
• Driven by the need for ubiquitous information flow.
• Users don’t care where or how information is processed, only that it
reaches its intended destination in the desired/required form.
• Supports unprocessed data (Raw) and processed data (fused)
10/1/2004 10/1/2008
1/1/2005 1/1/2006 1/1/2007 1/1/2008
1/1/2006 1/1/2010
1/1/2007 1/1/2008 1/1/2009
1/1/2008 1/1/2012
1/1/2009 1/1/2010 1/1/2011
SDR – JTRS Based Systems
CR – XG and WNaN 4G
PIPES
It’s the
Radio
Stupid
It’s the
Network
Stupid
It’s the
Information
Stupid
Radios are priced to cost
Knowledge is price to value
Understanding is priceless
It’s in the
Understanding
Stupid

Evolution of Communication Systems
PIPES-4G design leverages existing consumer product 3G and emerging 4G architectures,processes,and
technology to build a scalable edge node architecture for disadvantaged highly mobile
communications – Enables Web 2.0 (ESB) convergence.
Mobile Architectures – Consumer Products
• 1G…Continuous Mode Design Techniques…1980s
• Based on COTS products…Voice only
• 90% of the existing warfighter communication systems are 1G products
• 2G…Burst Mode Design Techniques…Mid 1990s
• Based on ASICs and GPP…Primarily Voice
• 2.5G…Advanced Power Control…2002
• Advanced Memory Architectures and Process Technology
• Significant advances in RFIC technology
• Mixture of Voice & Data…Introduction of IP based systems
• Newer military radio systems based on linear mode design achieve 2.5G performance
• 3G…Adaptive Computing Processors – 2005
• Based on GPP/DSP cores for multilingual concurrent network operation
• (WCDMA/GSM) - MUOS
• Data centric multimedia network nodes
• UMTS Deployment – Universal Mobile Telecommunication Systems
• Replacement of ASIC technology with ASSP technology and generic waveform support
• 4G…MC-HCA/SCA…2010 – PIPES
• Supports BLOS/LOS Convergence
• Hosts applications for communication systems
• Supports delivery of information in context : Converges information with the appropriate context
• Supports integration of PNT, Sensors processing, Video compression, …
• Supports MILS (Multiple Independent Levels of Security)
• Completely reconfigurable high rate multimedia, information Processors
• Low Energy-per-Network-Bit (EpNB)
• Supports Cognitive Radio and Networks applications
• Enables Web 2.0 Edge Node Data Platform Architectures (ESB)

The World of Convergence
Seamless Mobility provides users with the experience
of being connected anywhere, anytime and with
any service.
• Seamless emphasizes continuity of experience across
multiple spatial domains, devices, network protocols and
access technologies.
• Service convergence (voice, video, data)
• Device convergence (Cognitive & Software Defined Radios)
• Network convergence (achieve end-to-end goals)
• Mobility is the next phase of the internet revolution that
allows users to communicate and manipulate information
regardless of location.

PIPES Description
The PIPES architecture can be modularized into three
segments – Policy Definition, Cognitive Layer and Software
Adaptable Layer.
The Cognitive Layer is divided into 2 sub-layers to decouple
network decisions from the underlying network
technologies.
• Resource Managers (RM): technology independent layer
which coordinates domain-wide connection admission
control decisions, manages peering agreements with
neighboring domains, and controls the inter-domain routing
process.
• Resource Allocators (RA): technology dependent layer that
enforces the RM decisions for the specific (intra-domain)
devices.

Notional PIPES ArchitectureCognitiveLayerSoftwareAdaptableLayerPolicyDefinition
Cognitive
Element
Sensor
Reconfigurable Element
Inter-Domain
Communicator
Info. Processing/
Analyzer
Decision
Maker
Behavior
and Pattern
Resource Manager
Resource Allocator
Cognitive Element
Apply
Experience
Case
Parameters
NextDomain
Sensors provide feedback
information such as channel
condition and network congestion
level for the different layers
Application
Presentation
Session
Transport
Network
Data Link
Physical
Cross-LayerProtocol
StackManager
Reconfigurable Element
Sensor
Multi-Objective
Optimization
Execution/
Deployment
Configuration (XML)
Monitor/
Observer
Resource
Manager
Knowledge Base/
Learning Machine
Policies Generated
for End-to-end Goals
Policy Modifications
(Adaptation)
Policy Translator (API)
End-to-end Policy Specifications
Policy Manager
Policy Translator (API)
Customer GUI Input
Cognitive
ElementCognitive
Element
Inter-Domain
Communications
Sensor
Reconfigurable
Element
Sensor
Reconfigurable
Element
Sensor
Reconfigurable
Element
SoftwareAdaptableLayerCognitiveLayer
End-to-endQoSPathSetup
Technology-Specific Translator (API)Technology-Specific Translator (API)

Notional: Platform Architecture
PHY
Co-Processor
Power
Amplifier
RxRF Core
CI-BMCA
RxRF Core
CI-BMCACI-BMCA
VHF
TxRxRF Core
PHY
Co-Processor
Power
Amplifier
CI-BMCA
RxRF Core
CI-BMCACI-BMCA
UHF Terrestrial & SATCOM
TxRxRF Core
PHY
Co-Processor
Power
Amplifier
RxRF Core
CI-BMCA
RxRF Core
CI-BMCACI-BMCA
HF
TxRxRF Core
RxRF Core
IA
Crypto
Red GPP
Processor
Network
Processor
UHPI
GPIO
I2C
Timers
USB 2.0
OTG
EMAC
1553
PLL RTC
Switched Fabric Central
Resouces
MC-HCA Secure Network Processor
ARM Interrupt Controller
ARM11xx
D-Cache
8KB
I-Cache
16KB
SRAM 128 KB
Boot ROM
ARM SubSystem
Switched Fabric Central Resources
SPI
I2C
PWM (3)
GPIO
McBSP (2)
UART
Timer (6)
WDT (1)
L1D 80KB
C64x+
Core
L2-128KB
Cache
Boot
ROM
DSP SubSystem
L1P 32KB
PLL RTC
VIF
Camera
High Speed
I/F
Viterbi Coprocessor
USB 2.0
OTG
EMAC
Synchronous
EMIF-8B
w/ arbiter
Mobile
DDR/SDR
32b
MMC/SD
ATI
UHPI
DC-HCA Architecture
Synchronous
EMIF-32B
w/ arbiter
Future RFCorePA Waveform Expansion
PHY Processor Expansion Bus
UHF
VHF
HF
Architecture supports both HRDL and LRDL
waveforms and networks. Platform capability
determined by adaptive components of the
architecture
Initial implementation will support HF,
VHF and UHF waveforms as well as data,
voice, and video applications
PHY Processor Expansion Buss will
support 8-concurrent PHY/RFCores
Expansion Bus to facilitate design reuse
and future waveform support
Note: This 2005 Architecture Proposed
as part of the DARPA QNT Program

Notional: RF Core Processor
Distributed Processing: Burst Mode Control Architecture
• Power control will be embedded in PHY Layer Co-Processors in
each RFCore. Current flow in linear elements of the RFCore will
be event triggered.
• Waveform application code will not be burdened with integrated
burst mode control applications.
• Intelligent API structures need to be developed.
PHY
Co-Processor
Power
Amplifier
IPF Filter
BMCA
RxRF Core
BMCABMCA
Waveform Specific RFCores
TxRxRF Core
L-Band
UHF
Secondary RFCore
PHY Processors
· PHY Co-Processors support multiple waveforms
· BMCA – Burst Mode Control Architecture provides
distributed Power Control based on event triggers
· DC-HCA interface support 8 RFCore processors
Note: This 2005 Architecture Proposed
as part of the DARPA QNT Program

PIPES Characteristics
Supports the SOA (Service-Oriented Architecture) framework
endorsed by DISA’s (Defense Information Systems Agency)
Global Information Grid that focuses on service and
information interoperability
Policy-based system that converts user-defined policies into
system parameters: Metadata to achieve end-to-end service
objectives
Multi-layered structure that decouples network decisions from
the underlying network technologies
Supports resource management and information distribution
across heterogeneous networks
Incorporates cognitive components that perform resource
optimization and adapts to dynamic network conditions

PIPES: End-to-End QoS Provision for
Heterogeneous Networks
User Defined Policies + SLA
EncryptionApplication Decryption Application
Resource
Manager
Resource
Manager
Resource
Manager
Sender Receiver
Resource
Allocator
Resource
Allocator
Resource
Allocator
QoS
Inter-Domain
Path
End-to-End QoS Path
QoS
Inter-Domain
Path
QoS
Domain Path
QoS
Domain Path
QoS
Domain Path
Autonomous
System
Autonomous
System
Satellite
System
Network Technology Independent Sub-layer
Network Technology Dependent Sub-layer
QoS
Request
QoS Enforce
SessionInitializationProtocol(SIP)
SessionInitializationProtocol(SIP)
Cross-Platform
Protocol
Cross-Platform
Protocol

PIPES-Streaming Video: Application
Resource Manager is responsible
for:
• End-to-end QoS provision
• Inter-domain routing
• Streaming Video and Data
Controller adaptation based on
underlying network conditions
and policies
Video application is responsible
for compressing and interleaving
video packets.
Data Controller is responsible for
IP encapsulation and selecting
the appropriate FEC based on
channel condition feedback and
importance of video frame (e.g. I-
Frames).
Video
Processor
Data
Controller
Physical
Layer

PIPES-Video Streaming: Sequence Diagram
Streaming
Video
Data
Controller
Physical
Layer

Unit Roles and Policies Structure
Communications Network Radio System (CNRS)
Unit
Supporting
Subsystems
Capabilities
Skill Equipment
UAV
(Recon Unit)
Sensors
Equipment
(Weapons)
Comm.
(Link16)
Soldier
(Infantry)
Supporting
Subsystems
Equipment
(Weapons)
Android

Recommended Reading
IPA: Information Processing Architecture
• Working Document WINNF-09-W-0007 V 00.06
• Joint Development by CRWG & PS SIG
• Authors: Peter G. Cook
James Rodenkirch
• Contributors:
Ihsan Akbar Fred Frantz Neal Mellen
James Neel Rick Taylor Roger Webb
Establishes the foundation for development of communication systems that
delivers information in the appropriate context share knowledge between
users.
“The Singularity is Near” – Raymond Kurzweil
• When Humans Transcend Biology – the point when
nanotechnology exceeds biotechnology

PIPES

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (15)

Similar to PIPES

Similar to PIPES (20)

PIPES