mobile computing presentation

1
m3
An Adaptable Enterprise Architecture for Mobile
Computing
2
Overview

• m3 Why we do it
• m3 Platform
• m3 Project Status

3
Computing and Communications Growth

• Performance / Price x2 every 18 months (100x per
  decade)
• Aggregate bandwith x2 in 8 months
• 1.5 billion mobile phones in the next few years
• Devices / Users gtgt 1
• Increasing number of Internet transactions

4
Mobile constraints

• Bandwith fluctuation
• Capabilities variation
• Disconnection (voluntary)
• Radical Heterogeneity
• Hostile environments

5
Constraints will stay will they?

• gaps coverage
• wireless bandwith lt wired bandwith
• mobile cababilities ltlt fixed capabilities

Bet Adaptable Internet Service/Application
Driven Wireless Networks
6
The Goal

• Maximize the Enterprise productivity while
  minimizing constraints brought by mobility

7
Research Vision

• Not just about making applications mobile But
• Allowing enterprise applications to be deployed
  (used) in many different environments
  effectively.
• Innovative workplace technologies and concepts in
  a variety of mobile work situations.
• Demonstrate reference models, architectures and
  technologies that enable mobile enterprise roles
  to co-operate.

8
Mobility of hardware
Mobility of users
Mobility of data
Mobility of software
9
Platform Model
EnterpriseApplications
Mobile Enterprise Architecture Description
Interface
Adaptability Manager
Policy Manager
Context Manager
Security Manager
Service Interface
Trans-action
Tra- ding
Loca-tion
Notifi-cation
Avai lability
Blue- toothEnabler
WAPEnabler
JINI Enabler
HTTPS Enabler
Services
Network Programming Interface
Network
M3 Focus
Externally provided
10
Context Manager

• Observation and reporting of information relevant
  to the current context of devices, networks,
  users, applications
• Based on Composite capability/preference profile
  (CC/PP)
• Repository in RDF/XML (standardized vocabularies,
  extensible, indirect references)
• Context exchange protocol

11
Adaptability Manager

• Adapt to context changes
• Security, Presentation, Usage of Network,
  Enterprise Application specifics ...
• Changes in context are mainly due to
• mobility of users, computers
• disconnection
• Adaptation can be handled externally or
  internally for an application

12
Policy Manager

• Enforces dynamic enterprise policy
  specifications affected by mobility
• Obligation, prohibition, permission
• Takes into account
• Standards like RM-ODP
• Existing Policy Manager

13
Security Manager

• Enable security as intended and required by an
  application irrespective of the
• environment
• device
• Provide an application infrastructure to leverage
  technologies such as WAP-WTLS
• Enables the maximum security available on a
  device
• e.g., GSM phones with WAP and BlueTooth enable
  the best
• Close management of security aspects
• e.g., Certificate management issue expiry
  control

14
M3 How we fit in the Picture
EnterpriseSystems
15
Focus Technologies Standards

• WAP/WTLS, Bluetooth, Jini
• WAP forum and Bluetooth consortium
• XML
• W3C Mobile Access Activities, such as the
  Composite Capabilities/Preferences Profiles
  (CC/PP)
• SyncML Initiative Universal Standard for Data
  Synchronization
• GSM, UMTS, GRPS
• Devices WAP Phones, WAP Tops (easy interface),
  EPOC (Sony, Nokia, Ericsson, Psion, Motorola),
  Palm/Handspring

16
Project structure

• 11 Researchers involved (6.7 MY)/annum
• Research Students
• Distributed Team Brisbane (7), Melbourne (2),
  Sydney (1), Canberra (1)

17
Collaboration

• Partners
• RSA, Sun, Mincom, Telstra, Boeing, DSTO
• Projects
• Elemental, Pegamento, Ambience, Ene, Security
  Unit,
• Other
• SAP, Psion, Palm, Dascom, OTI, Motorola, Ericsson

18
m3-SAP

• Part of a joint world-wide research initiative
• Application of the platform model to an
  enterprise system
• Demonstration during Sapphire Brisbane (7/2000)

19
Roadmap

• Forming the Ground Flexible Architecture
• Year 1 Pervasive Computing (Based on existing
  Scenarios)
• Year 2 Ubiquitous Computing (Zillions of
  Devices)
• Using the Base
• Year 3 Extensions to Technologies/Architectures
  to support completely new Business Scenarios
• There will be a strong overlap!

20
Project Status

• On schedule
• Additional industrial background
• Publications 5 international conferences/workshop
  s
• Q2 Initial Specification of Architecture and
  Components
• Q3 First Demonstration
• Q4 Context Manager and CC/PP Report