1. SIMPLE MOBILE SERVICES FOR IMS A. Polidoro, G. Bartolomeo, S
SIMPLE MOBILE SERVICES FOR IMS A. Polidoro, G. Bartolomeo, S. Salsano, DIE - University of Rome “Tor Vergata”, Rome, Italy
Good Morning I’m Andrea Polidoro a Phd student from university of Rome “Tor Vergata” and I’’ll show you a work about Simple Mobile Services in IMS.
NGMAST’08

2. IST-SMS European Project Overview The SMS Architecture Elements:
Outline
IST-SMS European Project Overview
The SMS Architecture Elements:
The MOVE Application
The SMILE Framework
The SMILE/SIP binding
MOVE/SMILE over IMS
Testbed
This is the outline of my presentation. First of all we will see an overview about SMS Project, its goals its targets.
After I’ll show you the architecture elements of SMS, Particularly the Move Application, The SMILE framework and its binding with SIP protocol
Finally I’ll show you how its possible porting the MOVE/SMILE Architecture over IMS platform
16/11/2018
NGMAST 2008

3. SMS goals Mobile services have not (yet) reached the success of web
If mobile services are to repeat the success of the Web they have to be:
simple to use,
simple to find,
simple to trust,
simple to create/set up.
These are the design goals of our project “Simple Mobile Services”.
The goal of the sms project is to make a platform were is possible create, find trust and use service depicted for mobile terminals in order to repeat the web service success.
16/11/2018
NGMAST 2008

4. Service Authoring & Service Execution
Non-expert service author
Expert developer
(Create services)
SMS Service Authoring Platform
SMS Service Execution Platform
(Use services)
So this is the scenario were SMS works. Logically we are 2 platform one is the Service Auto… Platform. This platform is used to develop services, its has 2 kind of API, a not-expert interface and a expert interface. The second one is the Execution platform that is the platform were the service running and it will be used from the end user.
End users of mobile services
16/11/2018
NGMAST 2008

5. Architectural Vision Service Execution SMS Component Services
http, Web Services…
Service Execution
SMS Component Services
Non-SMS services and applications
SMS libraries
End-user of mobile services
SMILE
Mobile device
Server side
SMS Service Execution Platform
This is a more detailed vision of the SMS execution Platform. How you can see we have 2 side: a Mobile device that is equipment by Move, that is the application used from the terminal user to “browse” between the SMS services. This services could be locate inside the mobile device or in remote server that can communicate with MOVE by the SMILE framework.
MOVE
16/11/2018
NGMAST 2008

6. The MOVE application “Mobile Open and Very Easy”
The MOVE application is a sort of browser for mobile services running on the mobile terminal (open source)
MOVE provides the capability to search for services and present the most suitable services according to users’ preferences and current context
MOVE is a stand-alone J2ME (CLDC) application. It can run on a large set of terminals
MOVE (Mobile Open & Very Easy) is an example of a mobile application exploiting the SMS architecture. Implemented as a Java 2 Micro Edition MIDlet, MOVE is a “service browser” that allows users to access the required services among the available ones. Services are implemented by using several components, which may reside in the local MOVE application or may be located in a remote server and communicate through a lightweight middleware
16/11/2018
NGMAST 2008

7. MOVE screenshots
MEMs (Mobile Electronic Memos) messaging and handling. MEMs are electronic notes containing a structured set of attributes associated with a specific class of information and can be used by humans and applications to exchange information, for example related to a location, a person, a service, the status of an ongoing activity, etc. Figure 1-7 shows a possible use of a MEM describing a restaurant. Users “capture” MEMs from the environment or from other services, store them for future use (Figure 1-2 to Figure 1-4), share them with other users (Figure 1-8) and send them as input to other components (like the maps/navigation component, Figure 1-5). MEMs allow to drastically reduce the amount of information to be entered manually by users, which is a key feature for mobile services. The MEM concept [2] has been introduced by the SMS project and is considered an important enabler for simplifying the usage of mobile services.
16/11/2018
NGMAST 2008

8. Some features of MOVE
Showing and sharing “MEMs” (Mobile Electronic Memos)
Outdoor localization/navigation (GPS receiver + mashup of web based maps)
Indoor localization/navigation (may interact with indoor navigation systems)
Information services (Weather, travel, traffic, shops…)
16/11/2018
NGMAST 2008

9. SMILE Simple Middleware Independent LayEr
Interface Definition
(Java) Application
(Java) Application
(Java) Application
IDLight (or WSDL or SMS UML profile
SMILE APIs
SMILE
binding(s) to underlying mechanisms
SMILE ([4], see also [3]) is an abstraction layer written in Java which supplies a simple and unified framework for developing distributed, component-based applications. The components that need to interact are implemented as “SMILE peers”. SMILE features an application-level peer-to-peer communication paradigm, which allows each peer to communicate with other peers either by sending asynchronous messages or by using synchronous remote procedure calls, at their convenience. In addition, it offers support for peer lifecycle as well as registration and lookup facilitations which may be exploited by any peer to find other peers.
Being an abstraction layer, SMILE is not a self-contained middleware and needs a “binding” to an underlying mechanism in order to implement actual communications. Components can therefore be developed using the SMILE framework, irrespectively of the concrete mechanisms that will be used for the communication. This way, applications maintain their portability across different middleware platforms and devices.
JSON
SIP
JADE
RMI
CORBA
SOAP
HTTP
16/11/2018
NGMAST 2008

10. SMILE-JS for Simple Mobile services
SMS Service Execution Platform (Mobile device Side)
SMS Service Execution Platform (Server Side)
Interface Definition
Component Service
Component Service
Component Service
(Java) Application
(Java) Application
(Java) Application
IDLight (or WSDL or SMS UML profile
SMILE APIs
SMILE-JS
Formerly, we have implemented SMILE bindings on RMI, CORBA and JXTA middleware, all targeted to desktop platforms (e.g. using JAVA Standard Edition). In contrast, the JSON/SIP binding developed in the SMS Service Execution Platform allows all applications coded for SMILE to run on fixed hosts as well as on mobile devices implementing a J2ME virtual machine, without any change in their SMILE-based interfaces.
Binding to underlying mechanism
JSON
SIP
16/11/2018
NGMAST 2008

11. Modularity Adding SMILE-JS based server-side comp.
SMILE based components
SMILE yellow page
SIP Registrar and Proxy
Service discovery
SIP SBC
“provider” network
“provider” network
Internet
GPRS/UMTS/
WiFi access
SMILE middleware JSON notation SIP transport
Mobile Terminal
16/11/2018
NGMAST 2008

12. SMILE over IMS Private/Public identity management
Support to Service Route Discovery in the Registration and the Subscribe Notify Registration Package
Support the P-Preferred Identity ant P-Access Network
Merge All SMILE Peers Services Provider in only one Application Server (yellow pages server included):
Definition of a Services Dispatcher
Definition of 2 new attributes in the from/to SIP header (p-name p-type)
pType=MemReceiver, pName=istance0>;tag ;
SMILE PEER
pName=yp0
pType=YellowPages
SMILE PEER
pName=meteo0
pType=MeteoServer
SMILE PEER
pName=map1
pType=MapServer
Dispatcher
SIP STACK
:5060
16/11/2018
NGMAST 2008

13. Testbed Architecture
16/11/2018
NGMAST 2008

14. Thank You! Any Questions?