Context-aware Pervasive Networking (CAPNET)
Mobile Forum’s Research Focus Area
Minna Isomursu
Aim, focus and goal of the 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.
Organization of RFA
RFA program is organized in following work modules:
Basic technology research (fundamentals; creation of new technology)
•
Long term (over whole RFA) research focusing on selected fundamental phenomena,
tacking tough problems. I.e. "grand challenge" problems that (when solved) offer high
potential for commercial or other means of exploitation.
Applied technology research (integration technologies; needed to connect developed basic
technology to future application areas)
•
Medium term (6months-2years) research, focusing on investigation of environment, endto-end technologies that provide new breakthrough possibilities by exploiting technology
convergence with entirely new technologies. I.e. "semi challenge" problems with more
practical functionalities in current real life environment
Cross-deployment research (future applications; preparing demonstrations of expected
future impacts)
•
Short term (3-9months) research, aimed at producing new application innovations,
concepting new promising application in the early stage of basic-applied research. I.e.
"window-to-the-future" application and tackling/foreseeing their problems (feedback to
fundamentals)
Motivation for CAPNET Program
• Pervasive networking is a promising
area for creation of environment
aware personalized mobile services
• The large penetration, capability
MAIN AIM OF CAPNET PROGRAM:
increase and minityriazation of
mobile networks and devices
enable the
creation of cheap
TO CREATE UBI TECNOLOGY ENABLERS – MAP LUCRATIVE
DISCONTINUITIES
pervasive services.
business
potential exist!
”GROW” NECESSARY WORKFORCE/COMPETENCE =>
TOhuge
LAUCH
UBI BUSINESS:
spin-offs, new product businesses & services, fill white-spaces
• Next generation value nets will be
on physical
sub-nets
& smart
TAKE LEAD IN NEW EXITING ”4G” AREA IN A CONRETE built
FASHION,
WITHOUT
HYPE.
personal spaces.
Support infrastructure for pervasive services:
• Flexibility in network progammability
• Multi-channel, multi-zoned services offering
• Advanced resource and profile management
• Easily tailorable, self-configurable services
(E.g. local mobile commerce, smart
communication, p2p interactions &
consumer initiated content creation, sharing of
services/content, virtual value communities)
CAPNET Partner Network 2002
Nokia
Ventures Organization
IBM
ISG
Univ. of Oulu
www.ee.oulu.fi/mvis/research/isg/
Zoned networking
Context solving
CCC
University of
Linköping
Proximity
Transactions
Adaptive content
MediaTeam
Univ. of Oulu
www.mediateam.oulu.fi
Intelligent SW
Environment
management
Ubicomp via
mobile device
Advanced UI
Hantro
Reliability
Content Processing
Ubi concepting
Umiacs/LAMP
Univ. of Maryland
www.umiacs.umd.edu
Capnet Areas
HCI
Univ. of Oulu
www.tol.oulu.fi/tutkimus/index.html
Research
Nokia
Mobile Phones
Business
Sonera
CAPNET Innovation Process
”What is it? Why is it important? Is it doable?”
Application
ideas
Scenario
analysis
Application
scenarios
Scenario
acceptance
Scenario
review
Review in
TEG partner
experts
List of desired
features
”dream functionality”
Classify features
according to
UBI architecture
Map selected features
to technology
candidates
Perform E2E check
& technology
consistency
Review classification
of features
”Select UBI-enabling features?”
Accept features to
UBI architecture
framework
”Chart architectural impacts?”
Perform research to
find optimum solution
”Technologies needed?”
Review
in RFASG
Review
in scientific
forums
CAPNET Research Process
CAPNET Architecture Building Blocks
CAPNET uses a unique engine-based approach to focus on value adding
functionalities and gain rapid creation of service functionality, e.g.
– Multimodal UI Engine
• Suitable input/output methods for current environment setup
*) Engines can reside either in device,
local domain or network server
• GUI adapts to situation, requires new approach to GUI
• Robustness when roaming between smart spaces
– Connectivity Management Engine
• Light engine in the device to take care of current connectivity and consistency of
application or content (being consumed)
• Network engine to offer optimum choice of connectivity setup required by
currently available applications/content or offered from current environment
CAPNET Architectural Entities
Multimodal UI
Engine
Application
Partitioning
Engine
Scripts or
Application
Logic
• Collaboration of different entities
Application Level UBI-Enablers
– Virtual Storage Engine
• Storing application and content should be transparent and seem local (e.g.
caching) from application point of view, although the actual data is distributed
between network and device
– Context Engine
Media
Intelligence
Engine
Context
Engine
AI
Engine
• Light engine in the device
• Network engine in service provider
Value Adding Service Enablers
• Their cooperation in resolving current contextual data
– Application Partitioning Engine
• Partition application optimally according to environment setup and application
preferences
Connectivity
Management
Engine
Virtual
Storage
Engine
Service
Discovery
Engine
• Use context engine and SD engine input to aid partitioning
– Service Discovery Engine
Core UBI Enablers
• Light engine in the device
• Network engine in service / local provider environment
=> Allows for rapid integration also to existing platforms
• Their cooperation in resolving current service portfolio
Basic design requirement: calm technology approach combined with mobility
UBI Engine Assesment
UBI Engine Structure
Architecture Taxonomy
1. Direct Engine-Application Connection
INTERFACE
DYNAMIC
MESSAGING
INTERFACE
UPGRADE FD
FUNCTIONS
..
Browser
DYNAMIC
FDn(n0..nx)=
FS1(k0..kx)=
Application
E
FD1(n0..nx)=
Local/Mobile Environment
2. Local Domain of Networked Engines
Browser
CORE
MESSAGING
INTERFACE
or
STATIC
• UBI Engines are independent ”micro-servers”
requiring very little resources
• Interface uses XML-syntax for maximum
environment compatibility
• STATIC block is mandatory, providing core
functions in Engine scope (Memory <<)
• DYNAMIC block can be tailored according
to environment needs
or
Application
E
E
E
E
E
Local/Mobile Environment
Local Hosted Environment
3. Hybrid Domains of Networked Engines
Browser
or
E
Application
E
E
E
E
Local/Mobile Environment
E
E
E
Remote Hosted Environment
Local Hosted Environment
Application Scenarios
ContextAwareWellbeing
Now I can
really start
‘extreming’…
Tom downloads an exercise planning
application written in Java.
The application automatically finds and recognizes the various health monitoring
gadgets which Tom is wearing.
While Tom is climbing, the application
monitors the details of Tom’s condition.
The application automatically develops a near-term fitness plan appropriate for Tom
given his current physical condition.
KnowYourWhereabouts
After one week…
I am going to
teach my
phone my
habits.
Looks cool!
Marie buys a new phone. She is
showing it to her friend Susie.
The device has learnt where Brandi likes to visit and what she does.
Your phone is
peeping
Marie gives names to positions.
Look, it
remembers!
Marie leaves to work, surprised that her phone helped her not to be late.
HotStone
I wish Brandi
and I had
more time
together.
Brandi is home alone, preparing her lecture for tomorrow.
Her husband, Tom, is working late again.
Tom feels lonely; he presses his HotStone.
How sweet.
I’ll give him a
call.
Brandi feels her own HotStone warming up...
...she knows that Tom is thinking
about her.
WishList
Shopping
LunchAssistant
Thank You!
Minna.Isomursu@oulu.fi