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>Appendix C: What if Your SchedulerDoesn’t Produce the “Next Queue”• Case study: My scheduler already decided all the UEs to schedule <strong>and</strong>all the associated RBs…I also know how many blocks are given toeach RB…how do I interface my system to OPNET?• This problem can be solved as follows:• Step 1: Overwrite the output of lte_sched_support_next_q_get() with yourown (c_rnti, rb_id), so that frame generator will service your queue insteadof letting the callback choose one for you• When you are done, assign the variable return_ q_id the value<strong>LTE</strong>C_SCHED_Q_INVALID for termination• Step 2: Overwrite the calculation of the variables “num_alloc_blocks_ptr”<strong>and</strong> “small_alloc_blocks_ptr” in the functionlte_enb_as_dl_frame_gen_blocks_<strong>and</strong>_bits_compute()• “Small allocation blocks” is important to know for subframes withspecial channels such as primary/secondary synchronizations <strong>and</strong> BCCH.• That’s pretty much it!• As long as you have produced a “correct frame” (i.e. not allocating moreresources than what actually exist), things will work fineCONFIDENTIAL ─ 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.84
Change language