Contenuti time-based e personalizzati sul cellularde

Contenuti time-based personalizzati ed in tempo reale sul tuo cellulare
Alberto Lagna
Chief Technology Officer Fluidtime

background
General trend : adoption of more flexible time habits
Business trend: business digitalisation and just in time
Need: communication of dynamic time information
Potential: providing acces to tailor-made content

potential areas for dynamic data
Travel: real-time information
Events: calendar planning
Business: keeping customers and logistics up to date
Resources: coordinating shared resources
Appliance: monitoring remote devices
Groups: synchronise communities

existing media for dynamic content Web extensive information stationary, difficult to navigate on mobile devices, requires constant data reload Mail simple and easy to use stationary, not useful for constant status updates, difficult information handling Sms widely accepted costly for constant updates Voice supported by all phones takes time to grasp information, difficult to manage multiple sources

mobile solutions from technically feasible to services with high usability and attractiveness
SMS - arrival time per text message
WAP - browser based information retrieval
Java - applications for focused information monitoring

SMS
Pro
• Is well known and supported by all mobile phones
• It is relatively easy to get an update for a single stop
telephone number? number of stop? what if the time on my phone is different? have to translate the informatio n! Con • Costs: 10 - 50 Cents per update • No integrated support

WAP
Pro
• Is known and supported by 95% of mobile phones
• cheaper than SMS
• WAP pages can support the search for information
difficult handling more information can be displayed Con • navigation can be difficult • less accepted than SMS • for each updated the entire content of the page has to be reloaded

Java Application (J2ME)
Pro
• basic information is stored locally and can be retrieved quickly
• fast and simple navigation
• personalisation without subscription
Con • supported by 60% of mobile phones • application has to be loaded onto the mobile phone combining several stops within one interface

requirements and success factors
Fast - Immediate access to information
“ I don’t want to browse a minute to reach content”
Simple - Coherent language and interaction
“ I don’t want to relearn a new interface for every content”
Low Cost - Transparent pricing schemes
“ I don’t understand todays complex tariff structures”
Useful - Emotional identification
“ I only make phone calls”

the Fluidtime answer
Fast - tuned for immediate access
Simple - Coherent language across horizontal domains
Low Cost - 3 Euro/month or free of charge
Useful - Being always up-to-date and informed while on the move

What is Fluidtime?
Fluidtime is a platform to deliver time-based content to mobile subscribers in a customised and real-time fashion.
(Alberto Lagna – CTO Fluidtime)

How is Fluidtime made?
a platform
to deliver time-based content
to mobile subscribers
in a customised
and real-time fashion.

Java Conference 2005 Fluidtime platform

Fluidtime time-based concepts
Server
following a Time Model
hosting Time Windows
used by Time Agents through Time Windows
Client
Mobile, web, within a calendar client
Time Window
the content

Fluidtime Time Agent
a user (human or software agent) that gets updated by the platform
a user (human or software agent) that updates the platform

Fluidtime server
Central unit for the data communication.
Similar to a standard web server
processes user requests
retrieves and manipulates external data from content providers
it stores and manages data
schedules user updates and mirrors all the content from the different mobile phone users.
Java 2 Enterprise Edition application, integrating with external system through web services and exposing HTTP and XMPP interfaces to clients

Fluidtime client
the client of the platform
digitally connected calendar
the user can set different heterogeneous “watches” (e.g. on a flight, on an event, on a meeting) and monitor the evolution of every watch through the client.
J2ME, web, WAP, standalone client, SMS version

Java Conference 2005 Fluidtime window
how the information is structured within the client
represents a certain information context in a multimedia manner.
enables users to interact with and see dynamic timings of public and private services, groups of people, the status of events, etc.

Java Conference 2005 TECH CONTENT AHEAD

How is Fluidtime made?
a platform
to deliver time-based content
to mobile subscribers
in a customised
and real-time fashion.

main use cases

supported channel

Technical architecture

Mobile Client – Server integration
pull
http, wap
push
xmpp (the jabber protocol), sms

Fluidtime client
The mobile client
is a java J2ME framework
developed by fluidtime
hosting TimeWindows
A Time Window
a GUI
specified in terms of the TimePilot framework objects
a set of rules
used by the TImePilot framework to render updates to the screen
Channels
java phone, web, wap, sms

Java Conference 2005 Layers and tiers user business workspace resource services infrastructure application Underlying technical and communication capabilities Common utility functions applied across tiers Application level business logic Tiers Layers Presentation and device independence User session and data manipulation Business processes and entities Shared enterprise resources

Fluidtime client components
A core framework
In the future could be released open source
To easily develop MVC, REST ws, dynamic mobile application
Made up of:
Cache
XML util (based on javolution.org)
REST ws multitransport
MVC made on tiles
Commons services (logger, command factory, date helper, navigation helper, prefs, RMS helper)

Java Conference 2005 FT Client components – The cache
Data lifecycle:
- Read from RMS (if not empty) else read from XML in jar
- Copy to cache (memory)
- Update cached objects from push or pull
- Before closing app save to RMS
The cache implements an interface similar to the hibernate Session
public void save(Entity e) throws ResourceException;
public void delete(Entity e) throws ResourceException;
public Entity find(String query) throws ResourceException;
public void reset() throws ResourceException;

FT Client components – XML utils
Based on the javolution OS library
the encoding of objects into XML
reconstruction of the object graph from XML.
Encoding specified through static inner classes:
Pros no schema needed
Cons no schema driven
Pull parser several times faster than conventional parsers.
An XMLAdapter to drive the conversions using the javolution support
Added the multiple reference concept (lacking in javolution)

FT Client components – XML utils
Sample of mapping (obj into XML) + refid support (through a Map)
public static final XmlFormat TIME_WINDOW_XML = new XmlFormat(
"com.fluidtime.timepilot.domain.TimeWindow") {
public void format(Object obj, XmlElement xml) {
TimeWindow tw = (TimeWindow) obj;
xml.setAttribute("id", tw.getId());
xml.setAttribute("name", tw.getName());
addIdToObjMap(tw);
}
where the refid is used:
xml.setAttribute("timeWindows", relationRef(twg.getTimeWindows()));

FT Client components – REST ws
Representational State Transfer (REST) is an architectural style for distributed hypermedia systems like the world wide web.
Simple web-based interface that uses XML and HTTP without the extra abstractions of MEP-based approaches like the web services SOAP protocol
used by Google, Yahoo, Amazon, eBAY, Flickr, Fluidtime (see http://backstage.bbc.co.uk/data/SearchApI?v=9w7)
our APIs
http://fluidtime.com/svr/mobile/TimeWindowGroup/ get.action ?id=1&id=2
http://fluidtime.com/svr/mobile/TimeWindowGroup/ post.action ?xml=.....

FT Client components – REST ws
Our REST web services approach is multi-transport :
HTTP
Bluetooth
to support inexpensive, ad-hoc network in closed area
using Ben Hui (www.benhui.net)
experimenting Jadabs (jadabs.berlios.de), an OSGI implementation of the TU of Zurich

FT Client components – MVC
Model-View-Controller (MVC) is a software architecture that separates
an application's data model,
user interface
and control logic
into three distinct components so that modifications to the view component can be made with minimal impact to the data model component.
view based on the MIDP2 CustomItem, building our own “tiles”

FT Client components – commons
Common services, usually available OS on J2SE/EE, not so standardised yet on J2ME:
Logger , inspired by log4j
CommandFactory , implementation of the command pattern to easy the development of the GUI
DateHelper , to easily manage Date conversion (ah, the J2SE DateFormatter!)
NavigationHelper , to easy the Windows navigation
public static Window getNext (int index)
public static Window getPrevious (int index)

FT Client components – commons
RMSHelper used to
easily serialize objects into the RMS ( Record Management System the persistent storage for MIDlets)
desialize them into the memory (in our case the cache)
public final static synchronized Object read ()
public static synchronized void save (Object o)
ResHelper , loads file from the res dir (imgs and txt) to the memory
Prefs , reads properties from the jad, keeps them in memory and stores update in RMS

Whole client optimisation
Using proguard to optimize the classes
free Java class file shrinker, optimizer, and obfuscator ( http://proguard.sourceforge.net/)
integrated in the WTK using ProGuardWTKGlue
with our own customisation
optimization - shrink - no obfuscation (due to the use of javolution)
from 300Kb to 180Kb...
no code optimization needed (done by proguard)

value chain Fluidtime facilitates the exchange of dynamic time information Content aggregation and management Mobile application development

Fluidtime references
Implementation of three service pilots:
Public transport Turin
in cooperation with Gruppo Torinese Trasporti
Laundry service Ivrea
in cooperation with Miele, Germany
Supply chain status service
in cooperation with Schachermayer, Austria
First live event
Java Conference Milano
23

Travel : public transport Torino 23

Appliance : laundry service 23

SupplyChain : production status 23

Event : Java Conference xx

Useful links
java2me.org
javolution.org
hibernate.org
webwork.org
benhui.net
jadabs.berlioz.de
wikipedia.org

Alberto Lagna
CTO [email_address]
Antonio Terreno
Mobile Development
[email_address]
www.fluidtime.com
Q&A

Contenuti time-based e personalizzati sul cellularde

by Alberto Lagna on Apr 18, 2008

Accessibility

Categories

Tags

Upload Details

Usage Rights

Statistics

Contenuti time-based e personalizzati sul cellularde — Presentation Transcript