Sponsored by the U.S. Department of Defense© 2008 by Carnegie Mellon University

page 1

Pittsburgh, PA 15213-3890

The Implications of a Single Mobile Computing Device

Len Bass and John Klein

© 2002 by Carnegie Mellon University page 2

Outline

Convergence

Issues• User Interface Software• Security• Reliability

© 2002 by Carnegie Mellon University page 3

Convergence - 1

Convergence is the use of a single mobile device to manage all of your computing needs

Two models of convergence• Convergence to the “cloud”

- Computation is performed by a collection of services existing on the network “somewhere”

• Convergence to the individual- Computation is performed by a device permanently

and privately associated with an individual.

Two models are the same with respect to communication and sharing with others.

© 2002 by Carnegie Mellon University page 4

Convergence – 2

Hardware assumptions

Both models assume independent I/O devices. Computer connects to the I/O devices through a wireless mechanism such as blue tooth.

Convergence to the cloud assumes computing device is primarily a communications mechanism

Convergence to the individual assumes computing device has large amounts of primary storage, very fast processors – e.g. cellphone.

© 2002 by Carnegie Mellon University page 5

User Interface Software

The question for both models is where does the user interface knowledge reside?• If in the I/O devices then knowledge of all potential

applications must be in the I/O devices• If in the applications then must maintain knowledge of

all potential I/O devices in the applications.• If shared (through mobile code) then linkage with I/O

devices must have sufficiently high bandwidth to support code mobility.

Research question is how is I/O knowledge distributed to support efficient development and efficient execution.

© 2002 by Carnegie Mellon University page 6

Security

Convergence to the cloud.• Assumes all communication to service providers are protected

and data stored by service providers is protected..• Different service providers will likely require different

authentication mechanisms.• Attackers have centralized targets.

Convergence to the individual • Assumes data on device is protected in case of loss or theft.• More susceptible to malware residing on I/O devices.• Trust needed only for back up data service provider.

Research questions: Is there a lightweight protection against malware residing on I/O devices.

© 2002 by Carnegie Mellon University page 7

Reliability

Convergence to the cloud:• Constant connectivity. Intermittent connectivity will require

synchronization mechanisms.• Replacement of lost or stolen devices is seamless.• Back up is handled by service providers and is unnecessary

for communications device since there is no non-replicated local data.

• The same data in different locations must be synchronized. E.g. address.

Convergence to the individual• Connectivity needed only for backups and collaboration with

others.• Intermittent connectivity can be used for incremental backups• Lost or stolen devices must be reset from back up data.• Two copies of each datum – one local and one in back up

store.

© 2002 by Carnegie Mellon University page 8

Summary

Convergence is coming

Unclear whether convergence is to the “cloud” or to the individual

Better methods are needed for:• Distributing user interface knowledge• Managing security and trust issues• Managing reliability issues.