3
m
An Adaptable Enterprise
Architecture
for Mobile Computing
Overview
m3 – Why we do it
m3 – Platform
m3 – Project Status
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 >> 1
Increasing number of Internet
transactions
Mobile constraints
Bandwith fluctuation
Capabilities variation
Disconnection (voluntary)
Radical Heterogeneity
Hostile environments
Constraints will stay – will
they?
gaps coverage
wireless bandwith < wired bandwith
mobile cababilities << fixed
capabilities
Bet: “Adaptable Internet Service/Application
Driven Wireless Networks”
The Goal
Maximize the Enterprise
productivity while minimizing
constraints brought by mobility
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.
Mobility of hardware
Mobility of users
Adaptable
Mobile
Computations
CSCW
Enterprise
modeling
QoS
Directory
Agents
Sensitive Framework
Notification
Components
Transaction
Replication
Billing
Mobility of software
Security
Recovery
Mobility of data
Platform Model
Enterprise
Applications
Mobile Enterprise Architecture Description Interface
Context
Adaptability
Policy
Security
Manager
Manager
Manager
Manager
Service Interface
Location
Trans- Traaction ding
Notification
Avai
lability
Blue-
JINI
tooth
Enabler
Enabler
WAP
Enabler
HTTPS
Enabler
Network Programming Interface
Network
M3 Focus
Externally provided
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
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
Policy Manager
Enforces “dynamic” enterprise policy
specifications affected by mobility
– Obligation, prohibition, permission
Takes into account
– Standards like RM-ODP
– Existing Policy Manager
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 WAPWTLS
 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]
M3: How we fit in the Picture
Enterprise
Systems
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
Project structure
11 Researchers involved (6.7
MY)/annum
Research Students
Distributed Team: Brisbane (7),
Melbourne (2), Sydney (1), Canberra
(1)
Collaboration
 Partners:
– RSA, Sun, Mincom, Telstra, Boeing, DSTO
 Projects:
– Elemental, Pegamento, Ambience, Ene, Security
Unit, …
 Other:
– SAP, Psion, Palm, Dascom, OTI, Motorola,
Ericsson
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)
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!
Project Status
 On schedule
 Additional industrial background
 Publications: 5 international
conferences/workshops
 Q2: Initial Specification of Architecture
and Components
 Q3: First Demonstration
 Q4: Context Manager and CC/PP Report