Mark J' Salamango

1
Pervasive Computing Why did the logistics
soldier cross the road?
Mark J. Salamango Chief Pervasive Architect USA
TACOM Tel [phone] Fax [phone] salamanm
_at_tacom.army.mil
2
Agenda

• Introduction Who is Mark Salamango?
• Why did the logistics soldier cross the road?
• What is Pervasive Computing (PvC)?
• Device Architecture
• The Back End
• Demonstration?
• Conclusion

3
Why did the logistics soldier cross the road?
4
What is Pervasive Computing (PvC)?

• The goal of pervasive computing (PvC) is to make
  data and application services available to any
  authorized user anywhere, anytime, and on any
  device.
• Create an environment where everything is a
  compute node which communicates wirelessly and
  interacts seamlessly with humans.

5
Pervasive Computing
Internet
Wireless Transport
Wireless Gateway
Information Vehicle Network
Communication
Application

• Connection Mgmt
• Protocol Stack
• Compression

• Diagnostics
• Prognostics
• Theft Tracking
• Alarms
• Navigation
• Java Classes Libs
• JVM

Security

• Encryption
• Authentication

• Grocery Applications
• Games
• Real-time diagnostics
• Firmware updates

• On demand multimedia
• Energy Optimization
• Security

Core Platform (OS, Processor, I/O, Storage,
Drivers)
Device Platform
6
Pervasive Computing
Internet
Wireless Transport
Wireless Gateway
Information Vehicle Network
Communication
Application

• Diagnostics
• Prognostics
• Movement Tracking
• Database
• Navigation
• Situational Awareness
• IFF (ID Friend or Foe)
• Java Classes Libs
• JVM

• Connection Mgmt
• Protocol Stack
• Compression

Force Support Applications
Security

• Encryption
• Authentication

• Asset Readiness
• Movement Tracking
• Situational Awareness
• Supply Mgmt
• Remote System Mgmt

• On demand multimedia
• Security

Core Platform (OS, Processor, I/O, Storage,
Drivers)
Device Platform
7
Interim DualIn-Vehicle Architecture
Commodify All Hardware Software Components
Through the use of Standards
External Communications
GPS Receiver
User Interface Systems
Hard Drive Embedded Data Base
Additional Transceivers
Cellular, Wireless, etc. Transceiver(s)
Speaker, Mic System(s)
Authentication System(s)2
XML-Based Multi-Media Data1 Bus (Soft Real Time)
Control Panel 1
Display 1
DVD/CD Players, etc.
Signal Processors Amplifier,Encoder/Decoder
Embedded Server
Control Panel N
Vehicle Control- Bus Gateway
Multimedia, Image Processor
Display N
Computer Systems
Vehicle Control Bus (Hard Real Time)
1 Data (Audio, Video, Graphics, Animation,
etc.) 2 E.g., PDAs, Cell Phones, Games, Java
Card, Java Ring, etc., (both active and passive
systems)
8
In-VehicleSoftware Architecture
Applications Services
e.g., Diagnostics, Prognostics, Database, S/W
Management, Security, etc.
Services Management Framework (OSGi)
Java Device Profiles Libraries
Java Media Framework
Java Telephony
MIDP
Foundation
Java Comm.
Jini
Java Speech
JNI
Core Java Libraries (CDC1/CLDC2)
Native Code
(e.g., C C Apps, Drivers,Libraries, etc.)
Java Virtual Machine (JVM)
RTOS
Java Chip
(e.g., RT Linux, Neutrino, WinCE, pSOS, etc.)
(e.g., MAJC, etc.)
Hardware
(e.g., x86, PowerPC, Sparc, StrongARM, etc.)
1 CDC Connected Device Configuration 2 CLDC
Connected Limited Device Configuration
9
Some Client Server Applicationsand their
Communication
Message Queuing
Remote Process Management
Database
Message Queuing
Remote Process Management
Database
There are many other applications on both the
client and server such as diagnostics/prognostics,
and many more will evolve!
10
The Total Wireless Solution
Enterprise Information
Device
Service Provider
Applications
Voice Access
Databases
Enterprise Portal
Data Access
Device Management
Collaboration
Subscriber Management
Project Management
System Integration
Services
Middleware
Network Provider
Enterprise
11
Man/Machine Interface
Portal Server (My Portal)
Have the data your way!
12
Conclusion

• PvC is important!
• It is here, and moving quickly.
• Lets pick an architecture that scales, offers
  security, and gives us a platform on which to
  build applications more rapidly.
• We need strong middleware on the device and on
  the back-end.