1 / 11

Outline

Interworking between P2PSIP Overlays and IMS Networks – Scenarios and Technical Solutions Enrico Marocco – Antonio Manzalini – Marcello Samp ò – Gianni Canal Telecom Italia Lab. Outline. Services vs. Applications Fight or Cooperate? P2PSIP What is this? Interworking with SIP IMS

vui
Télécharger la présentation

Outline

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. Interworking between P2PSIP Overlays and IMS Networks – Scenarios and Technical SolutionsEnrico Marocco – Antonio Manzalini – Marcello Sampò – Gianni CanalTelecom Italia Lab

  2. Outline • Services vs. Applications • Fight or Cooperate? • P2PSIP • What is this? • Interworking with SIP • IMS • Interworking with SIP

  3. Telephony Service Providers Exploit IP to build one access-agnostic service provision architecture Emulation of legacy services Easy deployment of new services Try to increase revenues extending to Internet communications E.g. IM gateways, Wengophone, Second Life Communicator… Internet Companies Exploit IP to provide low-cost RTC services Enhancement of the web experience Try to increase adoption allowing communications with PSTN E.g. Skype, SIPPhone, Abbeyphone… What’s happening to RTC?

  4. What can _we_ do? • Ignore: it’s not our business! • Fight: keep them as far as possible! • Leverage: let users communicate from different worlds • Pro: more traffic • Con: margin erosion

  5. Telephony Service Providers Complex (expensive) architectures QoS Legacy requirements (Lawful Interception, Call Completion…) Strong focus on standards (IETF, 3GPP, 3GPP2, ETSI) Multi-vendor systems Interoperability Internet Companies Focus on resource saving Reuse resources on the endpoints as much as possible Non-standard Protocols / Proprietary applications E.g. Skype, MSN, Gtalk… Technologies

  6. REGISTER REGISTER INVITE INVITE INVITE INVITE INVITE Peer-to-peer SIP

  7. P2PSIP: What is it good for? • For Internet Companies • Build cheap solutions for providing best-effort communication services • Exploit user resources for expensive tasks (e.g. NAT traversal)... • … because it’s peer-to-peer • No critical mass required for providing a service... • … because it’s standard • For Telephony Service Providers • Provide value added services (e.g. interconnection with legacy networks) to users in uncontrolled overlays… • … because it’s standard • Provide services (e.g. identity) to subscribers when they are registered in uncontrolled overlays (e.g. while using a web-based p2p client)… • … because it’s SIP

  8. sip:example.com Get Proxy Get Relay INVITE Media P2PSIP – SIP Interworking RFC3263 p2psip.org ICE sip:alice@p2psip.org sip:bob@example.com

  9. sip:example.com INVITE Get Relay Media SIP – P2PSIP Interworking RFC3263 p2psip.org ICE sip:alice@p2psip.org sip:bob@example.com

  10. IMS is based on SIP, but… • Communications between SIP and IMS clients need little support • IPv4/IPv6 gateways • NAT traversal enabled on clients • Open peering policies • Registrations of SIP clients in IMS networks need at least Rel8 • Digest authentication • Lack of QoS controls

  11. Conclusions • Sometimes it’s a service, sometimes an application • Vote for the standard solution, even when you don’t care • Keep it open

More Related