Click here to start
Table of contents
HTTP Session Mobility between Web Browsers using SIP
Aim and Objectives Motivation for the Research Work Related Work The Implementation & Data Flow Diagrams How it works Project Status & Future Work Summary & Recommendations Demonstration
Aim: To achieve HTTP Session Mobility using SIP (at the Application Layer of the OSI Layers). Objectives: 1. To extend the capabilities of existing Web browsers by integrating a SIP Stack into them. 2. To provide new HTTP Session Mobility Service namely Content Sharing and Session Hand-off considering the three methods of making HTTP Stateful. 3. Where necessary, to implement an Application Server which co-ordinates the HTTP Session Mobility without violating HTTP/1.1 security.
Current HTTP Session Mobility approaches are based on personal initiatives and some broke HTTP/1.1 Security rules. 1. Client-based Architectural Scheme 2. Proxy-based Architectural Scheme 3. Server-based Architectural Scheme
The need to ease Service and Personal Mobility between User Agents (e. g. session transfer from a Web browser on a desktop PC to a mobile device; or a Web browser to a Telephone in case of a Multi-channel Application). The need for adaptive user agents in converged applications (HTTP and SIP) where same user agent (e. g. a Web browser) can be used to perform SIP activities like voice call and video conferencing in addition to its existing capabilities.
- A service or application in the IMS (IP Multimedia Subsystem) Context where web content (e.g. video) can be pushed or shared between devices.
Slide 7
Slide 8
Slide 9
Slide 10
Slide 11
Slide 12
Slide 13
Slide 14
Slide 15
Slide 16
Slide 17
Slide 18
Slide 19
This implementation works in a Peer-to-Peer Environment where a SIP Application or Proxy Server isn’t required. However, a SIP Proxy with TLS support can provide needed Authentication, Confidentiality and Data Encryption. While SIP Proxy Server with TLS support offers aforementioned security features, S/MIME is preferred when this service will be used in an inter-domain communication because it offers end-to-end security unlike TLS which offers hop-by-hop security.
Demonstration of HTTP Session Mobility Service
Questions and Answers
Author:
Michael Adeyeye