SIMPLE MOBILE SERVICES FOR IMS A. Polidoro, G. Bartolomeo, S

Slides:



Advertisements
Similar presentations
TSpaces Services Suite: Automating the Development and Management of Web Services Presenter: Kevin McCurley IBM Almaden Research Center Contact: Marcus.
Advertisements

Mobile Agents Mouse House Creative Technologies Mike OBrien.
An Introduction to Web Services Sriram Krishnan, Ph.D.
Web Service Ahmed Gamal Ahmed Nile University Bioinformatics Group
General introduction to Web services and an implementation example
Web Services Darshan R. Kapadia Gregor von Laszewski 1http://grid.rit.edu.
9.5 Software Architecture
J2ME Web Services Specification.  With the promise to ease interoperability and allow for large scale software collaboration over the Internet by offering.
Comparison of the RMI and the socket APIs
Component and Deployment Diagrams
Processing of structured documents Spring 2003, Part 6 Helena Ahonen-Myka.
Introduction SOAP History Technical Architecture SOAP in Industry Summary References.
Small Devices on DBGlobe System George Samaras Chara Skouteli.
1 HKU CSIS DB Seminar: HKU CSIS DB Seminar: Web Services Oriented Data Processing and Integration Speaker: Eric Lo.
Chapter 1 Lecture 2 By :Jigar M Pandya WCMP 1. Architecture of Mobile Computing The three tier architecture contains the user interface or the presentation.
Lecture 15 Introduction to Web Services Web Service Applications.
Architecting Web Services Unit – II – PART - III.
XML Registries Source: Java TM API for XML Registries Specification.
MobileMAN Internal meetingHelsinki, June 8 th 2004 NETikos activity in MobileMAN project Veronica Vanni NETikos S.p.A.
Web Services Based on SOA: Concepts, Technology, Design by Thomas Erl MIS 181.9: Service Oriented Architecture 2 nd Semester,
WebService. Outline Overview of Web Services SOAP (messaging) WSDL (service description) UDDI (registry)
XML and Web Services (II/2546)
Hwajung Lee.  Interprocess Communication (IPC) is at the heart of distributed computing.  Processes and Threads  Process is the execution of a program.
ECI – electronic Commerce Infrastructure “ An application to the Shares Market ” Demetris Zeinalipour ( Melinos Kyriacou
Kemal Baykal Rasim Ismayilov
Seminar on Service Oriented Architecture Distributed Systems Architectural Models From Coulouris, 5 th Ed. SOA Seminar Coulouris 5Ed.1.
REST By: Vishwanath Vineet.
Intro to Web Services Dr. John P. Abraham UTPA. What are Web Services? Applications execute across multiple computers on a network.  The machine on which.
Lecture VI: SOAP-based Web Service CS 4593 Cloud-Oriented Big Data and Software Engineering.
EGEE is a project funded by the European Union under contract IST Introduction to Web Services 3 – 4 June
From Coulouris, Dollimore, Kindberg and Blair Distributed Systems: Concepts and Design Edition 5, © Addison-Wesley 2012 Slides for Chapter 9 Web Services.
Real-Time Systems Laboratory Seolyoung, Jeong JADE (Java Agent DEvelopment framework )
Advance Computer Programming Market for Java ME The Java ME Platform – Java 2 Micro Edition (J2ME) combines a resource- constrained JVM and a set of Java.
12. DISTRIBUTED WEB-BASED SYSTEMS Nov SUSMITHA KOTA KRANTHI KOYA LIANG YI.
Java Web Services Orca Knowledge Center – Web Service key concepts.
Internet and Distributed Application Services
Sabri Kızanlık Ural Emekçi
WEB SERVICES From Chapter 19 of Distributed Systems Concepts and Design,4th Edition, By G. Coulouris, J. Dollimore and T. Kindberg Published by Addison.
Architecting Web Services
WEB SERVICES.
MCA – 405 Elective –I (A) Java Programming & Technology
Unit – 5 JAVA Web Services
Introduction to Web Services
Architecting Web Services
Distributed web based systems
Wireless Instant Messaging Using J2ME
#01 Client/Server Computing
Chapter 3: Windows7 Part 4.
Overview of Web Services
Introduction to Web Services and SOA
Service-centric Software Engineering
Goals Introduce the Windows Server 2003 family of operating systems
Service-centric Software Engineering 1
Architectures of distributed systems Fundamental Models
Bina Ramamurthy Chapter 9
Architectures of distributed systems Fundamental Models
Bina Ramamurthy Chapter 9
Bina Ramamurthy Chapter 9
Middleware, Services, etc.
WebServices Using JAX-RPC
Introduction to Web Services
Distributed System using Web Services
Architectures of distributed systems
WEB SERVICES From Chapter 19, Distributed Systems
Software interoperability in the NGN Service layer
Introduction to Web Services and SOA
Architectures of distributed systems Fundamental Models
Chengyu Sun California State University, Los Angeles
Distributed Systems Architectures
#01 Client/Server Computing
Presentation transcript:

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

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

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

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

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

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

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

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

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

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

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

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) From:<alice@neverland.net; pType=MemReceiver, pName=istance0>;tag 123456; SMILE PEER pName=yp0 pType=YellowPages SMILE PEER pName=meteo0 pType=MeteoServer SMILE PEER pName=map1 pType=MapServer Dispatcher sip:alice@neverland.net SIP STACK 192.168.1.15:5060 16/11/2018 NGMAST 2008

Testbed Architecture 16/11/2018 NGMAST 2008

Thank You! Any Questions? stefano.salsano@uniroma2.it andrea.polidoro@uniroma2.it giovanni.bartolomeo@uniroma2.it