CoSIP: A Constrained Session Initiation Protocol for the Internet of Things

  • Simone Cirani
  • Marco Picone
  • Luca Veltri
Part of the Communications in Computer and Information Science book series (CCIS, volume 393)

Abstract

The Internet of Things (IoT) refers to the interconnection of billions of constrained devices, denoted as “smart objects” (SO), in an Internet-like structure. SOs typically feature limited capabilities in terms of computation and memory and operate in constrained environments, such low-power lossy networks. As IP has been foreseen as the standard for smart-object communication, an effort to bring IP connectivity to SOs and define suitable communication protocols (i.e. CoAP) is being carried out within standardization organisms, such as IETF. In this paper, we propose a constrained version of the Session Initiation Protocol (SIP), named “CoSIP”, whose intent is to allow constrained devices to instantiate communication sessions in a lightweight and standard fashion. Session instantiation can include a negotiation phase of some parameters which will be used for all subsequent communication. CoSIP can be adopted in several application scenarios, such as service discovery and publish/subscribe applications, which are detailed. An evaluation of the proposed protocol is also presented, based on a Java implementation of CoSIP, to show the benefits that its adoption can bring about, in terms of compression rate with the existing SIP protocol and message overhead compared with the use of CoAP.

Keywords

Internet of Things service discovery communication protocols constrained applications SIP CoAP 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Shelby, Z., Hartke, K., Bormann, C.: Constrained Application Protocol (CoAP). IETF Internet-Draft draft-ietf-core-coap (May 2013), http://tools.ietf.org/id/draft-ietf-core-coap
  2. 2.
    Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., Schooler, E.: SIP: Session Initiation Protocol. RFC 3261 (Proposed Standard) (June 2002); Updated by RFCs 3265, 3853, 4320, 4916, 5393, 5621, 5626, 5630, 5922, 5954, 6026, 6141, 6665, 6878 (June 2002)Google Scholar
  3. 3.
    Roach, A.B.: Session Initiation Protocol (SIP)-Specific Event Notification. RFC 3265 (Proposed Standard) (June 2002); Obsoleted by RFC 6665, updated by RFCs 5367, 5727, 6446Google Scholar
  4. 4.
    Hartke, K.: Observing Resources in CoAP. IETF Internet-Draft draft-ietf-core-observe (February 2013), http://tools.ietf.org/id/draft-ietf-core-observe
  5. 5.
    Shelby, Z., Krco, S., Bormann, C.: CoRE Resource Directory. IETF Internet-Draft draft-ietf-core-resource-directory (June 2013), http://tools.ietf.org/id/draft-ietf-core-resource-directory
  6. 6.
    Shelby, Z.: Constrained RESTful Environments (CoRE) Link Format. RFC 6690 (Proposed Standard) (August 2012)Google Scholar
  7. 7.
    mjSIP project, http://mjsip.org/
  8. 8.
    mjCoAP project, http://mjcoap.org/
  9. 9.

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  • Simone Cirani
    • 1
  • Marco Picone
    • 1
  • Luca Veltri
    • 1
  1. 1.Department of Information EngineeringUniversity of ParmaParmaItaly

Personalised recommendations