CAPNET Program Context-aware Pervasive Networking Mobile Forum’s Research Focus Area
Contents Introduction to the CAPNET Program Further information on application scenarios illustrated in videos
CAPNET Program Aim the essential foundation for new information and communications technologies in the context-aware mobile ubiquitous computing domain. Focus the mobile user perspective, where other terminals and services are utilised via a personal mobile device in a gateway-like fashion. Goal iterative and progressive development of technologies enabling truly pervasive networking environments for applications, using existing and emerging computing platforms and environments as a technological basis.
Motivation for CAPNET Program • Pervasive networking is a promising area for creation of environment aware personalised mobile services. • The large penetration, capability increase and miniaturising of mobile networks and devices enable the creation of cheap pervasive services. => huge business potential exists! Next generation value nets will be built on physical sub-nets and smart personal spaces . Support infrastructure for pervasive services: (E.g. local mobile commerce, smart • Flexibility in network programmability communication, p2p interactions & • Multi-channel, multi-zoned service offering consumer-initiated content creation, • Advanced resource and profile management sharing of services/content, virtual value communities) • Easily adaptable, self-configurable services
Motivation for CAPNET Program • Pervasive networking is a promising area for creation of environment aware personalised Main Aim of the CAPNET Program mobile services. To create ubiquitous technology enablers – map lucrative • The large penetration, capability discontinuities increase and miniaturising of mobile networks and devices “Grow” necessary workforce/competence to launch ubi business: enable the creation of cheap spin-offs, new product businesses & services, fill white-spaces pervasive services. => huge business potential exists! Take lead in new exiting “4G” area in a concrete fashion Next generation value nets will be built on physical sub-nets and smart personal spaces . Support infrastructure for pervasive services: (E.g. local mobile commerce, smart • Flexibility in network programmability communication, p2p interactions & • Multi-channel, multi-zoned service offering consumer-initiated content creation, • Advanced resource and profile management sharing of services/content, virtual value communities) • Easily adaptable, self-configurable services
CAPNET Partner Network 2002 Ubicomp via mobile device MediaTeam IBM University of Oulu University of CAPNET Areas Nokia Linköping Ventures Organization Umiacs/LAMP ISG University of Maryland CCC University of Oulu HCI Hantro University of Oulu Nokia Mobile Phones Research Tekes Nets Programme Sonera Business
CAPNET Research Process
User Experience An application scenario driven research approach • to ensure that real human needs are the driving force for the technology development • research problems are derived from actual usage needs and scenarios • requirements derived from the application scenarios are used as a basis for architecture and technology development. • prioritised list of scenarios is used for defining the order of implementation of CAPNET demonstrations • selected application scenarios are illustrated in the visualizations at the end of this presentation and on the videos provided here User experience evaluation • methods and frameworks for evaluating and measuring the factors affecting to the user experience in ubiquitous environments • evaluation of CAPNET demonstrations and implementations from the user experience point of view
CAPNET Universe CAPNET Universe CAPNET Architecture CRE CAPNET RUNTIME ENVIRONMENT (CRE) CAPNET RUNTIME ENVIRONMENT (CRE) DYNAMIC CRE COMPONENT DYNAMIC COMPONENT DYNAMIC COMPONENT CRE DYNAMIC CORE COMPONENT COMPONENT ENGINE CRE CORE COMPONENT ENGINE • Each device contains a CAPNET Runtime Environment - which in turn contains the engines • Engines are the basic entities of a distributed system requiring very little resources as a basic setup • Engines consist of components • Core component offers basic functionality for an engine type • Dynamic component can be tailored according to services needs
Engines Are the Building Blocks for the Architecture … … Application Application level UI Logic … Value adding … Media Context Virtual service enablers Processing Management Storage … … Component Connectivity Service UBI enablers Management Management Discovery Each engine is targeted to a domain area • Component Management Engine controls all components and partitions application optimally • Connectivity Management Engine controls all connections • Service Discovery Engine finds components, engines and external services • Context Engine provides contextual information for other engines, etc. UBI enabler engines have to be included in every CRE Light engines in mobile terminals, more capable engines in the network
Architecture Taxonomy 1. Direct Engine-Application Connection (direct value add) or Browser Application E Local/Mobile Environment Main properties (cumulative 1-3): • Engine can be used directly from Web browser or application • Engine can be installed in mobile device or network server in local/global domain • Engine implements a micro-server functionality (calm: waits to be used, proactive: functions under scripts)
Architecture Taxonomy 2. Local Domain of Networked Engines (proximity value add) or Browser Application E E E E E Local/Mobile Environment Local Hosted Environment Main properties (cumulative 1-3): • Nature of connection may vary • Engine can establish temporary hierarchy • Engine can move to optimize service • Application can use multiple engines • Engine functionality can be upgraded • Engine can use engine(s) • Engines can be located in different local domains
Architecture Taxonomy 3. Hybrid Domains of Networked Engines (richest value add) or Browser Application E E E E E E E E Remote Hosted Environment (Global domain) Local Hosted Environment Local/Mobile Environment (Local domain) Main properties (cumulative 1-3): • Engines can form functionality islands • Engines can establish a fixed hierarchy (larger servers) coping with load, errors, • Engines can seek services offered by other engines QoS demands • Engine can function as a transparent gateway for other engines
Prototyping Implementing the architecture and selected application scenarios Aim is to • demonstrate service concepts • test developed architecture • test individual technologies within a complex system – e.g. new service discovery and routine learning algorithms First prototype • Scenario: Know your where abouts • Utilized existing technology: PersonalJava, XUL, XML-RPC, Jini • Implemented in Java but uses language independent communications
CAPNET Test Environment Provide a realistic platform for the deployment of software prototypes that are produced within Prototypes program area. • Basic architecture and common components can be tested and evaluated in the environment • Prototype software packet as a new service scenario can be verified in the environment • Provide feedback to refine both architecture and fundamental methodology creations New invented techniques as well as applications scenarios are to be evaluated in the test environment in terms of usability, from the viewpoint of perceived user experience • How the users experience the ubiquitous environment and its applications, • What parameters affect the user experience. • Evaluation results will provide feedback for the new application scenarios creation The test environment can be used for the demonstration of the concrete deliverables of the CAPNET program.
CAPNET Test Environment 1 st Test Environment focuses on indoor Wireless Local Area Network, based on IT-NET • With wireless positioning system; PDA as the main user device; simulating main building & offices Next Test Environment will be extended to outdoor WLAN & Wireless Wide Area Network • Outdoor WLAN based on SmartRotuaari; wireless positioning; urban downtown & business centre; • WWAN based on Octopus environments; GPRS connection; suburban, rural, general coverage; • Sensor technology for human activity analysis will provide context-information from the test environment.
Application Scenarios
Lunch Assistant Simo, Raimo, and other employees of CAPNET program are having a meeting in Tietotalo’s meeting room. While the chairman is speaking the display of Simo’s mobile device starts to blink. The device is in a meeting mode. � The device has recorded its locations from the beginning. The profile changes and the use of the device (times/places where/when he does not answer the phone etc.) have been saved into a database as well. From this data, the device has identified and analyzed Simo’s routines. � Enabling phenomena: routine learning.
Recommend
More recommend
