Mark J. Salamango Chief Pervasive Architect USA TACOM Tel: Fax: Pervasive Computing: Why did the logistics soldier cross the road?

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

Why did the logistics soldier cross the road?

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.

Pervasive Computing Broadband Local Loop Information Appliance Network Residential Gateway Internet Grocery Applications Games Real-time diagnostics Firmware updates On demand multimedia Energy Optimization Security Wireless Transport Information Vehicle Network Wireless Gateway Device Platform Core Platform (OS, Processor, I/O, Storage, Drivers) Communication Connection Mgmt Protocol Stack Compression Security Encryption Authentication Application Diagnostics Prognostics Theft Tracking Alarms Navigation Java Classes & Libs JVM

Pervasive Computing Broadband/Wireless Local Loop C4ISR Information Network Secure Gateway Internet Asset Readiness Movement Tracking Situational Awareness Supply Mgmt Remote System Mgmt On demand multimedia Security Wireless Transport Information Vehicle Network Wireless Gateway Device Platform Core Platform (OS, Processor, I/O, Storage, Drivers) Communication Connection Mgmt Protocol Stack Compression Security Encryption Authentication Application Diagnostics Prognostics Movement Tracking Database Navigation Situational Awareness IFF (ID Friend or Foe) Java Classes & Libs JVM Force Support Applications

Interim Dual In-Vehicle Architecture XML-Based Multi-Media Data 1 Bus (Soft Real Time) Vehicle Control Bus (Hard Real Time) Display N Control Panel N Satellite Transceiver(s) GPS Receiver Additional Transceivers Cellular, Wireless, etc. Transceiver(s) User Interface Systems External Communications Computer Systems Embedded Server Vehicle Control- Bus Gateway Multimedia, Image Processor Speaker, Mic System(s) Authentication System(s) 2 Control Panel 1 Display 1 Commodify All Hardware & Software Components Through the use of Standards 1 : Data (Audio, Video, Graphics, Animation, etc.) 2 : E.g., PDAs, Cell Phones, Games, Java Card, Java Ring, etc., (both active and passive systems) DVD/CD Players, etc. Signal Processors Amplifier, Encoder/Decoder Hard Drive & Embedded Data Base

In-Vehicle Software Architecture Core Java Libraries (CDC 1 /CLDC 2 ) Java Virtual Machine (JVM) RTOS Hardware (e.g., MAJC, etc.) (e.g., RT Linux, Neutrino, WinCE, pSOS, etc.) Applications & Services Java Chip Native Code JNI MIDP Foundation Java Comm. Java Telephony Java Media Framework Java Speech Jini (e.g., x86, PowerPC, Sparc, StrongARM, etc.) Java Device Profiles & Libraries Services Management Framework (OSGi) e.g., Diagnostics, Prognostics, Database, S/W Management, Security, etc. 1 : CDC: Connected Device Configuration 2 : CLDC: Connected Limited Device Configuration (e.g., C & C++ Apps, Drivers, Libraries, etc.)

Some Client Server Applications and their Communication Remote Process Management Message Queuing Database Remote Process Management Message Queuing Database Message Queuing Remote Process Management Database Other Core Back-end Services There are many other applications on both the client and server such as diagnostics/prognostics, and many more will evolve!

The Total Wireless Solution DeviceService Provider Enterprise Information Project Management System Integration Enterprise Portal Voice Access Data Access Subscriber Management Device Management Applications Collaboration Databases ServicesMiddlewareNetwork ProviderEnterprise

Man/Machine Interface Portal Server (“My Portal”) Have the data “your” way!

Conclusion  PvC is important!  It is here, and moving quickly.  Let’s 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.