1 / 14

Interconnecting P2PSIP and IMS

Interconnecting P2PSIP and IMS. Jani Hautakorpi ¹ , Arturo Salinas ¹ , Erkki Harjula ² , Mika Ylianttila ² ¹ Ericsson Research Nomadiclab ² MediaTeam Oulu Group, University of Oulu NGMAST’08 16-19th Sep 2008 Cardiff, Wales, UK. Content. Motivation and background

izzy
Download Presentation

Interconnecting P2PSIP and IMS

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. Interconnecting P2PSIP and IMS Jani Hautakorpi¹, Arturo Salinas¹, Erkki Harjula², Mika Ylianttila² ¹Ericsson Research Nomadiclab ²MediaTeam Oulu Group, University of Oulu NGMAST’08 16-19th Sep 2008 Cardiff, Wales, UK

  2. Content • Motivation and background • Interconnection architecture: • Overview • Preliminary procedures • Session establishment from P2PSIP to IMS • Session establishment from IMS to P2PSIP • Prototype • Future work • Conclusions NGMAST'08

  3. Motivation and Background (1/3) • Many ways to communicate • Quite often no interconnection mechanisms • This lead to separated islands NGMAST'08

  4. Motivation and Background (2/3) P2PSIP network IMS network AS S-CSCF SIP HSS P-CSCF NGMAST'08

  5. Motivation and Background (3/3) • Excluded topics: • IPv4/IPv6 interworking • NAT traversal • Media handling • Charging NGMAST'08

  6. Gateway AS Interconnection Architecture (1/6)Overview P2PSIP network IMS network P2PSIP to IMS IMS to P2PSIP NGMAST'08

  7. Interconnection Architecture (2/6)Preliminary Procedures • Gateway AS registers itself to the P2PSIP network • IMS users have to set up their iFCs • P2PSIP users do not have any preliminary procedures NGMAST'08

  8. Interconnection Architecture (3/6)Session Establishment from P2PSIP to IMS (1/2) P2PSIP UA (at p2p-domain.com) Novel URI handling mechanism SIP INVITE to user@ims-domain.com Does the host name match my domain? no get Get to H(ims-domain.com) P2PSIP network IPGW yes SIP INVITE to IPGW INVITE get Get to H(user@ p2p-domain.com) IPUSER SIP INVITE to IPUSER INVITE NGMAST'08

  9. Interconnection Architecture (4/6)Session Establishment from P2PSIP to IMS (2/2) NGMAST'08

  10. Gateway AS Interconnection Architecture (5/6)Session Establishment from IMS to P2PSIP (1/2) SIP INVITE to user@p2p-domain.com S-CSCF Evaluate the trigger point in iFC: Session case=Originating Request-URI=*@p2p-domain.com IMS UA P-CSCF HSS NGMAST'08

  11. Interconnection Architecture (6/6)Session Establishment from IMS to P2PSIP (2/2) NGMAST'08

  12. Prototype • We implemented a prototype from the Gateway AS • Used Open IMS Core • Used Sofia-SIP • Used SIPp • Result: Proposed architecture is valid NGMAST'08

  13. Future Work • Studies related to charging: Probably different mechanisms for each direction • Media handling: Possibly a need for intermediary media elements • IPv4/IPv6 interworking NGMAST'08

  14. Conclusions • We proposed an interconnection architecture between P2PSIP and IMS: • Contains novel URI handling mechanism • Does not require changes to IMS terminals • Prototype proves that the proposed architecture is valid NGMAST'08

More Related