Signaling Compression (SigComp) Users' Guide

Signaling Compression (SigComp) Torture Tests

“…at (128) SORT-DESCENDING (256, 2, 23) 2,23) OUTPUT (302, 45) 0,0,0,0,0,0) at (256) word (10,10,17,7,22,3,3,3,19,1,16,14,8,2,13,20,18,23,15,21,12,6,9) word (28263,8297,30057,8308,26996,11296,31087,29991,8275,18031,28263,24864,30066,29284,28448,29807,28206,11776,28773,28704,28276,29285,28265) The output of the code is 0x466f 7264 2c20 796f 7527 7265 2074 7572 6e69 6e67 2069 6e74 6f20 6120 7065 6e67 7569 6e2e 2053 746f 7020 6974 2e, and the number of cycles required is 371. byte (97,98,99,…”

“…at (64) :byte_copy_left pad (2) MEMSET (32,4,65,1) ; Set first 4 bytes of the buffer to be ; 'ABCD' COPY (32,4,48) ; Copy from byte_copy_right (i.e., not ; in buffer)…”

“…at (64) :byte_copy_left pad (2) :byte_copy_right pad (2) at (128) LOAD (byte_copy_left, 128) ; sets up a circular buffer LOAD (byte_copy_right, 129) ; of 1 byte between 0x0080 and 0x0081 MEMSET (64,129,0,1) ; fills up the memory in the range ; 0x0040-0x007f with 0x00, ... 0x3f; ; then it writes successively at ; 0x0080 the following values 0x40, ... 0x80 ; as a side effect, the values of ; bcl and bcr are modified.…”

“…The SigComp User's Guide [1] gives examples of a number of different algorithms that can be used by the SigComp protocol. However, the bytecode for the corresponding decompressors is relatively well behaved and does not test the boundary and error cases that may potentially be exploited by malicious SigComp messages.…”

“…The following sections each provide code to test one or more UDVM instructions. In the interests of readability, the code is given using the SigComp assembly language: a description of how to convert this assembly code into UDVM bytecode can be found in the SigComp User's Guide [1].…”