3GPP2 C TSG-C

Transcription

1 3GPP2 C TSG-C TITLE: Output metrics for UMB Performance Evaluation SOURCE: Yifei Yuan, Sudarshan Rao, Pichun Chen, Donghze Cui, Stan Vitebsky, Qi Bi, S. Vasudevan ABSTRACT: This contribution proposes a list of output metrics for comparing and calibrating the simulation results. The intention is to assist in discussion of output metric list for phase system evaluation. RECOMMENDATION: Discuss and adopt. Alcatel-Lucent Inc. grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it may include all or portions of this contribution; and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational Partner's standards publication. Alcatel-Lucent Inc. is also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner s standard which incorporates this contribution. This document has been prepared by Alcatel-Lucent Inc. to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on Alcatel-Lucent Inc.. Alcatel-Lucent Inc. specifically reserves the right to amend or modify the material contained herein and nothing herein shall be construed as conferring or offering licenses or rights with respect to any intellectual property of Alcatel- Lucent Inc. other than provided in the copyright statement above.

2 . Overview C This document provides a table of metrics that would assist in comparing results, across companies, obtained during simulation exercises. Table provides a summary. This list is not exhaustive and serves only as an aid for discussion. Additional metrics may be added if necessary. Figures through 3 is intended only to provide a visual indication of what the results may look like. Some generic example plots have been provided only for illustration purposes. The graphs and plots enclosed are not indicative of any actual or final simulation results at this point. 2. Output Metrics Summary Table Output metrics are summarized in Table. Item FL full buffer RL full buffer FL VoIP RL VoIP Aggregate sector throughput Yes Yes Optional Optional Edge (95%) user throughput Yes Yes No No PER after 6 HARQ trans. Yes Yes No No Normalized per user avg. throughput Yes Yes No No Short-term averaged sector throughput Optional Optional No No Transmission rate vs. C/I Yes No No No HARQ statistics (distribution) Yes Yes Yes Yes FLCS power overhead Yes No Yes No IoT of RL OFDM traffic No Yes No Yes RL packet format selection distribution No Yes No No Distribution of # of tiles assigned per request No Yes No No RL OFDM traffic Tx power distribution No Yes No No Average SINR per HARQ transmission No No Yes Yes 98% VoIP packet latency No No Yes Yes Tile occupancy No No Yes Yes Tx PSD per tile No No Yes No RoT of RL CDMA control No No No Yes Table : Summary of simulation output matrix. 2

3 C Illustrative Figures of Output Metrics User fairness curve, or of normalized per user average throughput as shown in Figure as a general example, should be provided for full-buffer data simulations. User throughput is normalized by the average user throughput which is average sector throughput divided by the average number of users per sector Example DV fairness criteria Normalized per user avg. throughput Figure : A general example of of normalized per user average throughput (fairness curve). Even with full-buffer traffic, sector throughput varies in time, due to fading channels, FLCS loading, scheduling etc. Figure 2 shows an example of of short-term averaged (3 PhyFrames = 28 ms) sector throughput Example Short-term averaged sector throughput (Mbps) 3

4 C Figure 2: A general example of short-term averaged sector throughput. Figure 3 shows an example of FL data transmission rate (excluding idle time) vs. longterm C/I (combined over Rx antennas) assuming single user scheduled each time. The curve reflects link level performance and link adaptation in various fading channels. 5 2 Example Mbps Long-term C/I (db) Figure 3: A general example of FL data transmission rate vs. C/I Figure 4 shows an example of HARQ statistics which reflect the link adaptation, PF selection and scheduler performance. HARQ statistics of both full-buffer and VoIP simulations should be provided..5.4 Mix chan. ChA ChB.3 PDF # HARQ transmissions Figure 4: A general example of HARQ statistics 4

5 C FL control power overhead should be provided as shown as an example in Figure FLCS power overhead (Watts) Figure 5: A general example of FL control power overhead. Interference-over-thermal (IoT) for RL OFDMA traffic should be provided as shown in Figure 6 for example Example IoT (db) Figure 6: A general example of IoT of RL OFDMA traffic. RL packet format selection distribution should be provided as shown in Figure 7 for example. It is especially useful when the received traffic PSD is set not the same across users. 5

6 C % 3% 25% 2% 5% % 5% % PF PF PF2 PF3 PF4 PF5 PF6 PF7 PF8 PF9 Packet Format Figure 7: A general example of RL packet format selection distribution. The distribution of number of tiles assigned per request should be provided as shown in Figure 8 for example. 2% 8% 5% 2% 9% 6% 3% % Number of tiles assigned per request Figure 8: A general example of distribution of number of tiles assigned per request. The distribution of RL OFDM traffic should be provided as shown in Figure 9 for example. 6

7 C % 4% 3% 2% % % RDCH Tx power (normalized to max Tx power) Figure 9: A general example of distribution of RL OFDM traffic Tx power. VoIP 98% packet delay for both FL and RL should be provided. Figure shows an example for certain number of Erlangs per sector xxx Erlang % packet delay (ms) Figure : A general example of of 98% packet delay for VoIP. Traffic tile occupancy for both FL and RL VoIP traffic should be provided as in the example of Figure. 7

8 C xxx Erlang # Occupied tiles Figure : A general example of of tile occupancy for VoIP. of transmit PSD per tile on FL for VoIP should be provided as in the example of Figure xxx Erlangs FL Tx PSD (dbw) per tile Figure 2: A general example of of transmit PSD per tile on FL for VoIP. of RoT for RL CDMA control in VoIP should be provided as in the example of Figure 3. 8

9 C xxx Erlangs RoT (db) Figure 3: A general example of RoT of RLCDMA control for VoIP. 9