1 / 14
Télécharger la présentation

The Mobile Grid Concept

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The MobileGrid Concept Vicente Olmedo Technical University of Madrid

  2. Contents • Introduction • The Akogrimo Project • The Next Generation Mobile Grid Concept • The Session Initiation Protocol (SIP) • SIP fundamentals • The Session Description Protocol (SDP) • SIP usage for Web Service mobility

  3. Introduction (1/2) • The Akogrimo EU IST project is aimed to the design and implementation of a Next Generation Mobile Grid. • Concept: Next Generation Mobile Grid (NGMG) • Concept: Mobile Dynamic Virtual Organization (MDVO)

  4. Introduction (2/2) • NGMG = Mobile Network + Grid Services Session Initiation Protocol (SIP) Session Management Mobility Support Presence & Context

  5. The Session Initiation Protocol (1/4) • Standardized by the IETF in RFC 3261. • Signaling protocol targeted to the management of sessions in IP networks. • SIP is independent of the type of session being managed. • Basic messages (methods): REGISTER, INVITE, ACK, BYE, CANCEL, OPTIONS. • Extensible: new methods can be defined in order to support new functionalities. • Signaling entities also defined: User Agent, Proxy, Registrar.

  6. The Session Initiation Protocol (2/4) • User registration process

  7. The Session Initiation Protocol (3/4) • Session establishment and termination

  8. The Session Initiation Protocol (4/4) • Message format example Request Line INVITE sip:volmedo@dit.upm.es SIP/2.0 Via: SIP/2.0/UDP 138.4.3.130:3456 CallID: a2e3a@138.4.3.130 From: sip:villagra@dit.upm.es To: sip:volmedo@dit.upm.es Cseq: 1 INVITE Content-type: application/SDP Content-Length: 117 v=0 c=IN IP4 138.4.7.148 m=application 8080 HTTP soap+xml a=setup:passive a=wsdl:http://138.4.7.148/service.wsdl SIP Headers Message body (SDP)

  9. Web Services are getting mobile • Network architectures tend to convergence  access technology independence is a must. • Architectural design tends to Service Oriented Architectures. • User terminals becoming more and more powerful. • In Grid environments, users themselves can also be resources.

  10. Traditional, fixed scenario

  11. Mobile, ubiquitous scenario SIP session establishment Classical SOAP interaction

  12. Extending SDP • SDP syntax can be extended by the definition of new attributes. Request Line INVITE sip:volmedo@dit.upm.es SIP/2.0 Via: SIP/2.0/UDP 138.4.3.130:3456 CallID: a2e3a@138.4.3.130 From: sip:villagra@dit.upm.es To: sip:volmedo@dit.upm.es Cseq: 1 INVITE Content-type: application/SDP Content-Length: 117 v=0 c=IN IP4 138.4.7.148 m=application 8080 HTTP soap+xml a=setup:passive a=wsdl:http://138.4.7.148/service.wsdl SIP Headers Message body (SDP)

  13. Conclusions • SIP for signaling, SOAP for application. • Mobility and ubiquity for Web Services. • Web Services can make use of full SIP capabilities (e.g. session transfer). • No need to standardize new SIP mechanisms. • The new SDP attribute needs to be standardized.

  14. Thank you! Questions? Vicente Olmedo <volmedo@dit.upm.es>

More Related