1. Roke Manor Research s 1 ROHC Implementation Experience Mark West mark.a.west@roke.co.uk

2. Roke Manor Research s 2 Overview  First steps towards a full ROHC implementation  Initial feel for memory and processor load  Updating original reference implementation  Clean separation of ROHC framework and EPIC packet processing  Make use of time and memory efficient algorithms (but still scope for optimisation…)  Designed to be used  In a test environment (e.g. running over UDP or TCP)  For initial tests in a ‘real’ environment  As an extensible test-bed for other protocols

3. Roke Manor Research s 3 ROHC 09 Compatible Headers  Described in draft-price-rohc-epic-compatibility-00.txt  Bitwise identical compressed headers to ROHC 09 Example input table for UOR-2 headers: Field(s)Encoding MethodProbability TSIRREGULAR(6)100% MIRREGULAR(1)100% SNLSB(6,-1)100% XIRREGULAR(1)100% CRCIRREGULAR(7)100% TscVALUE(“0”)100%

4. Roke Manor Research s 4 Architecture  Architecture of ROHC 09 implementation including EPIC Compressor Flow/packet classificationDecompressor Decompression front end Compression front end ROHC framework EPIC coder EPIC decoder ROHC framework Link HH tree Packet stream Decompressed Flows HH tree Compressed headers Feedback

5. Roke Manor Research s 5 Processing Requirements  Processing load  Memory usage  Implementation efficiency can be increased Encoder MIPSDecoder MIPSTotal MIPS ROHC + EPIC0.8 GSM EFR codec14.41.616.0 Program (Kbytes) Static tree data (Kbytes) RAM (Kbytes) ROHC + EPIC50130.4 GSM EFR codec14.41.6

6. Roke Manor Research s 6 Timing Breakdown  Compress 1 header 41  s  Decompress 1 header 56  s (all timings on 270MHz SUN Ultra-5)

7. Roke Manor Research s 7 Efficient Implementation  Existing techniques such as Canonical Huffman work with Hierarchical Huffman  Most mathematical operations can be simplified  Processing cost includes:  CRC  Reduce by lookup based CRC implementation  Selecting header format  Optimise by looking for most common format

8. Roke Manor Research s 8 A ROHC Bay Cough?

9. Roke Manor Research s 9 A ROHC Bay Cough? ‘Interoperability Test’

10. Roke Manor Research s 10 A ROHC Bay Cough? ‘Interoperability Test’ London

11. Roke Manor Research s 11 Questions  When?  Who?  What?  Where?  How?

12. Roke Manor Research s 12 Questions  When?  Just before IETF-51?  Who?  Anyone with enough of an implementation…  What?  Aim for basic interoperability  Where?  Siemens/Roke Manor  How?  Take technical aspects of getting implementations to ‘talk together’ to the list

13. Roke Manor Research s 13