http:// www.mobilegrids.org The Mobile Grid Concept Vicente Olmedo Technical University of Madrid
Http:// The Mobile Grid Concept Vicente Olmedo Technical University of Madrid.
Mar 27, 2015
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
htt
p:/
/ww
w.m
ob
ileg
rid
s.org
The MobileGrid Concept
Vicente OlmedoTechnical University of Madrid
htt
p:/
/ww
w.m
ob
ileg
rid
s.org
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
htt
p:/
/ww
w.m
ob
ileg
rid
s.org
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)
htt
p:/
/ww
w.m
ob
ileg
rid
s.org
Introduction (2/2)
NGMG = Mobile Network + Grid Services
Network
AApppplliiccaattiioonn SSeerrvviicceess
Network Middleware
Grid Application Support Services
Grid Middleware Services
Session Initiation Protocol (SIP)Session Initiation Protocol (SIP)
Session Session ManagementManagement
Mobility Mobility SupportSupport
Presence & Presence & ContextContext
htt
p:/
/ww
w.m
ob
ileg
rid
s.org
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.
htt
p:/
/ww
w.m
ob
ileg
rid
s.org
The Session Initiation Protocol (2/4)
User registration process
[email protected]@pc33.atlanta.com
Location Service Proxyatlanta.com
REGISTER [email protected]
[email protected]@atlanta.com
INVITE [email protected]
QUERY [email protected]
RESP [email protected]
INVITE [email protected]
htt
p:/
/ww
w.m
ob
ileg
rid
s.org
The Session Initiation Protocol (3/4)
Session establishment and termination
[email protected] [email protected]
Proxyatlanta.com
INVITE [email protected]
INVITE [email protected]
INVITE [email protected] Trying
100 Trying
108 Ringing
108 Ringing
108 Ringing200 OK
200 OK
200 OK
ACK
SESSION DATA
BYE
200 OK
htt
p:/
/ww
w.m
ob
ileg
rid
s.org
The Session Initiation Protocol (4/4)
Message format example
Request Line
Message body
(SDP)
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 138.4.3.130:3456CallID: [email protected]: sip:[email protected]: sip:[email protected]: 1 INVITEContent-type: application/SDPContent-Length: 117
v=0c=IN IP4 138.4.7.148m=application 8080 HTTP soap+xmla=setup:passivea=wsdl:http://138.4.7.148/service.wsdl
SIP Headers
htt
p:/
/ww
w.m
ob
ileg
rid
s.org
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.
htt
p:/
/ww
w.m
ob
ileg
rid
s.org
ws.dit.upm.es
200 OK (SOAP response)
Traditional, fixed scenario
GET http://ws.dit.upm.es/service.wsdl
200 OK (service.wsdl)
POST /method (SOAP request)
htt
p:/
/ww
w.m
ob
ileg
rid
s.org
[email protected](138.4.7.148)
Mobile, ubiquitous scenario
INVITE [email protected]
200 OK
(EPR: http://138.4.7.148/service.wsdl)
GET http://138.4.7.148/service.wsdl
200 OK (service.wsdl)
POST /method (SOAP request)
200 OK (SOAP response)
ACK
SIP session establishment
Classical SOAP interaction
htt
p:/
/ww
w.m
ob
ileg
rid
s.org
Extending SDP
SDP syntax can be extended by the definition of new attributes.
Request Line
Message body
(SDP)
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 138.4.3.130:3456CallID: [email protected]: sip:[email protected]: sip:[email protected]: 1 INVITEContent-type: application/SDPContent-Length: 117
v=0c=IN IP4 138.4.7.148m=application 8080 HTTP soap+xmla=setup:passivea=wsdl:http://138.4.7.148/service.wsdl
SIP Headers
htt
p:/
/ww
w.m
ob
ileg
rid
s.org
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.
htt
p:/
/ww
w.m
ob
ileg
rid
s.org Thank you!Thank you!
Questions?Questions?
Vicente Olmedo
Related Documents
