Signaling compression
Page Module:Message box/ambox.css has no content.
 | This article needs additional citations for verification. (March 2026) |
Page Module:Message box/ambox.css has no content.
 | The accessibility of this article is in question. Relevant discussion may be found on the talk page. (January 2011) |
For data compression, signaling compression, or SigComp, is a compression method designed especially for compression of text-based communication data as SIP or RTSP. Originally been defined in Template:IETF RFC,Template:Ref RFC it and was later updated with Template:IETF RFC.Template:Ref RFC A Negative Acknowledgement Mechanism for Signaling Compression is defined in Template:IETF RFC.Template:Ref RFC The SigComp work is performed in the Robust Header Compression (ROHC) working group in the transport area of the IETF.
Overview
SigComp specifications describe a compression schema that is located in between the application layer and the transport layer (e.g. between SIP and UDP). It is implemented upon a virtual machine configuration which executes a specific set of commands that are optimized for decompression purposes (namely UDVM, Universal Decompressor Virtual Machine).
One strong point for SigComp is that the bytecode to decode messages can be sent over SigComp itself, so this allows to use any kind of compression schema given that it is expressed as bytecode for the UDVM. Thus any SigComp compatible device may use compression mechanisms that did not exist when it was released without any firmware change. Additionally, some decoders may be already been standardised, so SigComp may recall that code so it is not needed to be sent over the connection. To assure that a message is decodable the only requirement is that the UDVM code is available, so the compression of messages is executed off the virtual machine, and native code can be used.
As an independent system a mechanism to signal the application conversation (e.g. a given SIP session), a compartment mechanism is used, so a given application may have any given number of different, independent conversations, while persisting all the session status (as needed/specified per compression schema and UDVM code).
General architecture
References
Page Template:Reflist/styles.css has no content.
Related standards documents
- Template:IETF RFC – Signaling Compression (SigComp)
- Template:IETF RFC – Signaling Compression (SigComp) – Extended Operations
- Template:IETF RFC – The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)
- Template:IETF RFC – Compressing the Session Initiation Protocol (SIP)
- Template:IETF RFC – A Negative Acknowledgement Mechanism for Signaling Compression
- Template:IETF RFC – Signaling Compression (SigComp) Users' Guide
- Template:IETF RFC – Signaling Compression (SigComp) Torture Tests
- Template:IETF RFC – Signaling Compression (SigComp) Corrections and Clarifications
- Template:IETF RFC – Applying Signaling Compression (SigComp) to the Session Initiation Protocol (SIP)
- Template:IETF RFC – The Presence-Specific Static Dictionary for Signaling Compression (Sigcomp)
- 3GPP TR23.979 Annex C – Required SigComp performance
