1. m3m3 An Adaptable Enterprise Architecture for Mobile Computing

2. Overview 4 m 3 – Why we do it 4 m 3 – Platform 4 m 3 – Project Status

3. Computing and Communications Growth 4 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 4Increasing number of Internet transactions

4. Mobile constraints 4 Bandwith fluctuation 4 Capabilities variation 4 Disconnection (voluntary) 4 Radical Heterogeneity 4 Hostile environments

5. Constraints will stay – will they? 4 gaps coverage 4 wireless bandwith < wired bandwith 4 mobile cababilities << 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 4 Not just about making applications mobile But 4 Allowing enterprise applications to be deployed (used) in many different environments effectively. 4 Innovative workplace technologies and concepts in a variety of mobile work situations. 4 Demonstrate reference models, architectures and technologies that enable mobile enterprise roles to co-operate.

8. Agents ComponentsTransaction Notification Sensitive Framework Security Recovery Billing Directory Replication CSCW QoS Enterprise modeling Adaptable Mobile Computations Mobility of users Mobility of data Mobility of software Mobility of hardware

9. Platform Model M3 Focus Enterprise Applications Network Externally provided Loca- tion Trans- action Adaptability Manager Policy Manager Mobile Enterprise Architecture Description Interface Tra- ding Notifi- cation Context Manager Service Interface Avai lability WAP Enabler JINI Enabler Security Manager Blue- tooth Enabler HTTPS Enabler Network Programming Interface

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

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

12. Policy Manager 4 Enforces “dynamic” enterprise policy specifications affected by mobility –Obligation, prohibition, permission 4 Takes into account –Standards like RM-ODP –Existing Policy Manager

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

14. M3: How we fit in the Picture Enterprise Systems

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

16. Project structure 4 11 Researchers involved (6.7 MY)/annum 4 Research Students 4 Distributed Team: Brisbane (7), Melbourne (2), Sydney (1), Canberra (1)

17. Collaboration 4 Partners: –RSA, Sun, Mincom, Telstra, Boeing, DSTO 4 Projects: –Elemental, Pegamento, Ambience, Ene, Security Unit, … 4 Other: –SAP, Psion, Palm, Dascom, OTI, Motorola, Ericsson

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

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

20. Project Status 4 On schedule 4 Additional industrial background 4 Publications: 5 international conferences/workshops 4 Q2: Initial Specification of Architecture and Components 4 Q3: First Demonstration 4 Q4: Context Manager and CC/PP Report