Search   

 Site Map 

 Contact Us 

 Return to home 

 

 español 

 português 

SIP and SIP-I

SIP and SIP-I

Session Initiation Protocol (SIP) is the core networking protocol used within IMS and is one of the more widely known examples of a session control protocol. Session control refers to the process used to create, modify, and terminate IP based communication sessions, and a session can include two-way voice communication, multimedia (text, audio, or video) conference collaboration, instant messaging, application sharing, and other contemplated but not yet fully specified services. Session control is accomplished through signaling between various network elements and endpoints using a session control protocol.

Although SIP is the most widely known session control protocol, SIP has a major limitation that is of great importance to any GSM/UMTS operator. It does not provide any method of directly inter-working with the PSTN because it was not created with the intention of it being fully backward compatible with legacy PSTN signaling mechanisms.

In addition to SIP, other examples of session control protocols include BICC, SIP-I and SIP-T.

BICC is the current protocol standardized in the 3GPP Release 4 architecture and deployed in some networks today. However, BICC is not an optimal choice for ongoing evolution because it has been limited to, and is predicted to remain limited to, operation within a GSM/UMTS context. BICC does not address domains beyond GSM/UMTS such as LTE; as a result, it does not automatically offer the future level of flexibility of continued development and evolution that would accompany the SIP with ISUP encapsulation variants (i.e. either SIP-T or SIP-I).

With a technical analysis of capabilities existing within the two SIP technologies with ISUP encapsulation variants, 3G Americas recommends SIP-I as the direction for evolution. There are four areas where SIP-I is better suited for a GSM/UMTS environment than SIP-T:

  • Assumptions regarding the trust and security environment.
  • Encapsulation procedures & message mapping.
  • Support of RFCs.
  • User plane interoperability.

Additional information

Q&A

SIP Services Will Generate $150 Billion in Annual Revenue by 2012 (ABI Research press release, Nov 2007)

web
stats