Understanding LTE Model Internals and Interfaces
Understanding LTE Model Internals and Interfaces
Understanding LTE Model Internals and Interfaces
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
1581 <strong>Underst<strong>and</strong>ing</strong> <strong>LTE</strong> <strong>Model</strong> <strong>Internals</strong> <strong>and</strong> <strong>Interfaces</strong>RLC Code• All RLC functionality resides in models/std/lte/rlc_support.ex.c• The MACRO RLCC_MAX_TX_SDU_COUNT defined in rlc_support.hcontrols the RLC buffer size• <strong>Model</strong>ed as a constant with a capacity of 1500 packets for each radio bearer: Packetscan be of any size, though typical TCP/IP packets will be at most 1500 bytes• Enqueue/dequeue functions:• rlc_support_rlc_sdu_enqueue()• rlc_support_lte_rlc_pdu_create()• Other important functions• rlc_support_tx_queue_size_in_bits_get(): Get the size of the queue. This is how thescheduler would know if the queue is empty.• rlc_support_is_tx_window_stalled(): This is important for the scheduler to know. Astalled RLC window is treated the same as empty buffer• rlc_support_lte_min_pdu_header_size_get(): This is important for the framegenerator. If it does not have resources to allocate even the minimum RLC PDUheader, it should not allocate any resources at all.CONFIDENTIAL ─ RESTRICTED ACCESS: This information may not be disclosed, copied, or transmitted in any format without the prior written consent of OPNET Technologies, Inc. © 2010 OPNET Technologies, Inc.40