12
Mark J. Salamango Chief Pervasive Architect USA TACOM Tel: 586-574-7126 Fax: 586-574-6167 [email protected] Pervasive Computing: Why did the logistics soldier cross the road?

Mark J. Salamango Chief Pervasive Architect USA TACOM Tel: 586-574-7126 Fax: 586-574-6167

  • Upload
    nysa

  • View
    31

  • Download
    1

Embed Size (px)

DESCRIPTION

Pervasive Computing: Why did the logistics soldier cross the road?. Mark J. Salamango Chief Pervasive Architect USA TACOM Tel: 586-574-7126 Fax: 586-574-6167 [email protected]. Agenda. Introduction: Who is Mark Salamango? Why did the logistics soldier cross the road? - PowerPoint PPT Presentation

Citation preview

Page 1: Mark J. Salamango Chief Pervasive Architect USA TACOM Tel: 586-574-7126 Fax: 586-574-6167

Mark J. SalamangoChief Pervasive ArchitectUSA TACOMTel: 586-574-7126Fax: [email protected]

Pervasive Computing:Why did the logistics soldier

cross the road?

Page 2: Mark J. Salamango Chief Pervasive Architect USA TACOM Tel: 586-574-7126 Fax: 586-574-6167

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

Page 3: Mark J. Salamango Chief Pervasive Architect USA TACOM Tel: 586-574-7126 Fax: 586-574-6167

Why did the logistics soldier cross the road?

Page 4: Mark J. Salamango Chief Pervasive Architect USA TACOM Tel: 586-574-7126 Fax: 586-574-6167

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.

Page 5: Mark J. Salamango Chief Pervasive Architect USA TACOM Tel: 586-574-7126 Fax: 586-574-6167

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

Page 6: Mark J. Salamango Chief Pervasive Architect USA TACOM Tel: 586-574-7126 Fax: 586-574-6167

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

Page 7: Mark J. Salamango Chief Pervasive Architect USA TACOM Tel: 586-574-7126 Fax: 586-574-6167

Interim DualIn-Vehicle Architecture

XML-Based Multi-MediaData1 Bus

(Soft Real Time)

Vehicle Control Bus

(Hard Real Time)

Display N

ControlPanel N

SatelliteTransceiver(s)

GPSReceiver

AdditionalTransceivers

Cellular, Wireless,etc. Transceiver(s)

User InterfaceSystems

External Communications

Computer Systems

Embedded Server

Vehicle Control-Bus Gateway

Multimedia, ImageProcessor

Speaker, MicSystem(s)

AuthenticationSystem(s)2

ControlPanel 1

Display 1

Commodify All Hardware & SoftwareComponents 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/CDPlayers, etc.

Signal ProcessorsAmplifier,

Encoder/Decoder

Hard Drive &EmbeddedData Base

Page 8: Mark J. Salamango Chief Pervasive Architect USA TACOM Tel: 586-574-7126 Fax: 586-574-6167

In-VehicleSoftware Architecture

Core Java Libraries (CDC1/CLDC2)

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

MID

P

Fou

ndat

ion

Java

Com

m.

Java

T

elep

hony

Java

Med

iaF

ram

ewor

k

Java

Spe

ech

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.)

Page 9: Mark J. Salamango Chief Pervasive Architect USA TACOM Tel: 586-574-7126 Fax: 586-574-6167

Some Client Server Applicationsand their Communication

Remote Process Management

Message Queuing

Database

Remote Process Management

Message Queuing

Database

Message Queuing

Remote Process Management

Database

Other Core Back-endServices

There are many other applications on both the client and server such as diagnostics/prognostics, and many more will

evolve!

Page 10: Mark J. Salamango Chief Pervasive Architect USA TACOM Tel: 586-574-7126 Fax: 586-574-6167

The Total Wireless Solution

Device Service Provider Enterprise Information

Project Management

System Integration

En

terp

rise

Po

rtal

Voice Access

Data Access

Subscriber Management

Device Management

Applications

Collaboration

Databases

ServicesMiddleware Network Provider Enterprise

Page 11: Mark J. Salamango Chief Pervasive Architect USA TACOM Tel: 586-574-7126 Fax: 586-574-6167

Man/Machine Interface

Por

tal S

erve

r (“

My

Por

tal”)

Have the data “your” way!

Page 12: Mark J. Salamango Chief Pervasive Architect USA TACOM Tel: 586-574-7126 Fax: 586-574-6167

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.