1 / 3

ROHC 0-Byte Lite

ROHC 0-Byte Lite. Model 2 (Hybrid VoIP MS): ROHC 0-byte Lite, revised GEHCO operation. Why? To allow the PDSN to support model 2 and 3 with no extra complexity. The MS is “based” on GEHCO architecture. No other NRT applications are provided by the MS

eaton-henry
Download Presentation

ROHC 0-Byte Lite

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ROHC 0-Byte Lite

  2. Model 2 (Hybrid VoIP MS): ROHC0-byte Lite, revised GEHCO operation • Why? To allow the PDSN to support model 2 and 3 with no extra complexity. • The MS is “based” on GEHCO architecture. • No other NRT applications are provided by the MS • Full forward compatibility to ROHC is supported • Lite weight ROHC in MS handles the set up of the context and the exchange of 0-byte profile parameters with the PDSN ROHC HC. No compression occurs in the MS. • Upon detection by the PDSN of the MS capabilities, it initializes the non-transparency mode and it removes changes to header parameters. The effect will be that the ROHC 0-byte in the PDSN will always output No header packets to the MS. • Similar to GEHCO, 0-byte and SIP interface allow the transfer of static header field values . SIP* UDP IP Lite weight ROHC 0-byte EVRC codec PPP CDMA2000 specific layers Null RLP

  3. Conclusion • In the VoIP model, the legacy terminal could adopt the GEHCO architecture (I.e. no HC/HD in MS) but still be able to negotiate a 0-Byte profile truly based on ROHC • This will allow the PDSN to support both voice over IP models (EVRC on physical link (legacy) and as IP application), but within a single defined 0-Byte profile

More Related