The Mobile Grid Concept Vicente Olmedo Technical University of Madrid

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

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)

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

The Session Initiation Protocol (1/4) Standardized by the IETF in RFC 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.

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

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

The Session Initiation Protocol (4/4) Message format example Request Line Message body (SDP) INVITE SIP/2.0 Via: SIP/2.0/UDP :3456 CallID: From: To: Cseq: 1 INVITE Content-type: application/SDP Content-Length: 117 v=0 c=IN IP m=application 8080 HTTP soap+xml a=setup:passive a=wsdl: SIP Headers

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.

Traditional, fixed scenario

Mobile, ubiquitous scenario SIP session establishment Classical SOAP interaction

Extending SDP SDP syntax can be extended by the definition of new attributes. Request Line Message body (SDP) INVITE SIP/2.0 Via: SIP/2.0/UDP :3456 CallID: From: To: Cseq: 1 INVITE Content-type: application/SDP Content-Length: 117 v=0 c=IN IP m=application 8080 HTTP soap+xml a=setup:passive a=wsdl: SIP Headers

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.

Thank you! Questions? Vicente Olmedo