![Page 1: Cover Page Using a Light Image - sagroups.ieee.org](https://reader031.vdocuments.us/reader031/viewer/2022030220/621e870a9765b02aff3313e5/html5/thumbnails/1.jpg)
Aleksandra Checko, MTI/Foxconn
IEEE 1914 f2f meeting, Dallas, TX, US
04/19-21/2017
Throughput requirements
![Page 2: Cover Page Using a Light Image - sagroups.ieee.org](https://reader031.vdocuments.us/reader031/viewer/2022030220/621e870a9765b02aff3313e5/html5/thumbnails/2.jpg)
Compliance with IEEE Standards Policies and Procedures
Subclause 5.2.1 of the IEEE-SA Standards Board Bylaws states, "While participating in IEEE standards development activities, all participants...shall act in accordance with all applicable laws (nation-based and international), the IEEE Code of Ethics, and with IEEE Standards policies and procedures."
The contributor acknowledges and accepts that this contribution is subject to
• The IEEE Standards copyright policy as stated in the IEEE-SA Standards Board Bylaws, section 7, http://standards.ieee.org/develop/policies/bylaws/sect6-7.html#7, and the IEEE-SA Standards Board Operations Manual, section 6.1, http://standards.ieee.org/develop/policies/opman/sect6.html
• The IEEE Standards patent policy as stated in the IEEE-SA Standards Board Bylaws, section 6, http://standards.ieee.org/guides/bylaws/sect6-7.html#6, and the IEEE-SA Standards Board Operations Manual, section 6.3, http://standards.ieee.org/develop/policies/opman/sect6.html
2
![Page 3: Cover Page Using a Light Image - sagroups.ieee.org](https://reader031.vdocuments.us/reader031/viewer/2022030220/621e870a9765b02aff3313e5/html5/thumbnails/3.jpg)
Throughput requirements
Date: 2017-04-10
Author(s):
Name Affiliation Phone [optional] Email [optional]
Aleksandra Checko MTI/FoxconnAleksandra.Checko
@mtigroup.com
IEEE 1914Next Generation Fronthaul Interface
Jinri Huang, [email protected]
![Page 4: Cover Page Using a Light Image - sagroups.ieee.org](https://reader031.vdocuments.us/reader031/viewer/2022030220/621e870a9765b02aff3313e5/html5/thumbnails/4.jpg)
Background
Way forward after Oct16 f2f [1]:
– Need to fill in the transport class table
– Requirements (following Prof. Choi’s contribution, Transport requirements for different splits (ATT) )
Contribution from Feb 2017 telco:
– Proposal to use latency requirement as primary factor for CoSspecification, instead of throughput [2]
[1] 201610 IEEE 1914 f2f meeting summary
[2] tf1_1702_cai_tazi_NGFI_COS_specification_1.pdf
2017-04-10 4Throughput requirements
![Page 5: Cover Page Using a Light Image - sagroups.ieee.org](https://reader031.vdocuments.us/reader031/viewer/2022030220/621e870a9765b02aff3313e5/html5/thumbnails/5.jpg)
Thoughts on throughput requirements
• Delay requirement can only be met is required throughout can be accommodated
• Delay is more critical in the context of CoS definition
• Still, there is a value in defining realistic deployment scenarios
• 1914.1 PAR: “5.2 Scope: This standard specifies: (…)
• 2) Requirements and definitions for the fronthaul networks, including data rates
• Proposal: Fronthaul dimensioning tool
• To facilitate analysis on deployment scenarios
• Invitation to share views on parameters and their values in foreseen deployment scenarios to be included in the standard (informative)
2017-04-10Throughput requirements 5
![Page 6: Cover Page Using a Light Image - sagroups.ieee.org](https://reader031.vdocuments.us/reader031/viewer/2022030220/621e870a9765b02aff3313e5/html5/thumbnails/6.jpg)
Considered architecture
From IEEE 1914, tf1_1701_huang_two-level-architecture_2.pdf
Calculations focused
here:
2017-04-10 6Throughput requirements
![Page 7: Cover Page Using a Light Image - sagroups.ieee.org](https://reader031.vdocuments.us/reader031/viewer/2022030220/621e870a9765b02aff3313e5/html5/thumbnails/7.jpg)
Considered functional splits
Splits naming convention based on 38.801. Splits 7.1, 7.2 and 7.3 edited by MTI
2017-04-10 7Throughput requirements
PDCPLow-RLC
High-MAC Low-MACResource mapping, precoding
iFFT, CP
PDCPLow-RLC
High-MAC Low-MACResource
de-mapping
FFT, CP
Option 5Option 4 Option 6 Option 7-1Option 2Option 1
RRC
RRC
RF
RF
Option 8
Data
Data
High-RLC
High-RLC
Option 3
High-PHY
High-PHY
Option 7-2
Encoding
Option 7-3
![Page 8: Cover Page Using a Light Image - sagroups.ieee.org](https://reader031.vdocuments.us/reader031/viewer/2022030220/621e870a9765b02aff3313e5/html5/thumbnails/8.jpg)
Presentation of the tool
2017-04-10 8Throughput requirements
![Page 9: Cover Page Using a Light Image - sagroups.ieee.org](https://reader031.vdocuments.us/reader031/viewer/2022030220/621e870a9765b02aff3313e5/html5/thumbnails/9.jpg)
Exemplary configurations
2017-04-10 9Throughput requirements
100 MHz16 or 8 antennas
Compression/bit width256 QAM
![Page 10: Cover Page Using a Light Image - sagroups.ieee.org](https://reader031.vdocuments.us/reader031/viewer/2022030220/621e870a9765b02aff3313e5/html5/thumbnails/10.jpg)
Needs for D0.2/D0.3
• Unified formula for throughput calculations
• Proposal to use formulas from Fronthaul dimensioning tool
• Unified definition of multiplexing gain
• Proposal: [sum of throughputs/aggregated throughput] satisfying delay requirements
• Here MG = (1+1+1)/1=3
2017-04-19 10Overview and requirements
1
1
1
1
![Page 11: Cover Page Using a Light Image - sagroups.ieee.org](https://reader031.vdocuments.us/reader031/viewer/2022030220/621e870a9765b02aff3313e5/html5/thumbnails/11.jpg)
Bandwidth vs data rate vs throughput
Agreement is needed on terminology:
• 3GPP – bandwidth of data transmission
• SCF – bandwidth interchanged with throughput
• NGFI whitepaper - bandwidth
• IEEE 1914 PAR – data rates of network
• IEEE 1914.1 – bandwidth and throughput
Proposal:
• Data rate – of a link in the network
• Bandwidth of RF channel
• Throughput – actual transfer. But on application level?
2017-04-10 11Throughput requirements
![Page 12: Cover Page Using a Light Image - sagroups.ieee.org](https://reader031.vdocuments.us/reader031/viewer/2022030220/621e870a9765b02aff3313e5/html5/thumbnails/12.jpg)
Strawman poll #_4_
• Terminology: use throughput in definitions saying it is a transport throughput unless otherwise specified in IEEE 1914.1 standard
• Mover: Aleksandra Checko
• Seconder: Richard Maiden
• Yes: _19_ No: _0_ Abstain: _2_ (technical motion needs >= 2/3)
2017-04-19Overview and requirements 12
![Page 13: Cover Page Using a Light Image - sagroups.ieee.org](https://reader031.vdocuments.us/reader031/viewer/2022030220/621e870a9765b02aff3313e5/html5/thumbnails/13.jpg)
Strawman poll #_5_
• Do we need more discussion on: “Remove throughput requirements from NGFI transport class of service definition. Refer to throughput as informative”?
• Mover: Aleksandra Checko
• Seconder: Stuart Whitehead
• Yes: _3__ No: _8__ Abstain: _8__ (technical motion needs >= 2/3)
2017-04-19Overview and requirements 13
![Page 14: Cover Page Using a Light Image - sagroups.ieee.org](https://reader031.vdocuments.us/reader031/viewer/2022030220/621e870a9765b02aff3313e5/html5/thumbnails/14.jpg)
Motion #_5_ (04/20/2017)
• Remove the throughput requirement column from Table 2 in IEEE 1914.1 D0.2 page 19.
• Mover: Aleksandra Checko
• Seconder: Stuart Whitehead
• Yes: _11_ No: _0_ Abstain: _0_ (technical motion needs >= 2/3)
2017-04-20Overview and requirements 14
![Page 15: Cover Page Using a Light Image - sagroups.ieee.org](https://reader031.vdocuments.us/reader031/viewer/2022030220/621e870a9765b02aff3313e5/html5/thumbnails/15.jpg)
Motion #_4_
• In an appendix, show formulas and parameter definitions from tf1_1704_Checko_FHDimensioning_1.xlsm as a baseline for throughput calculations. Add informative reference that LTE calculations are as in SCF 159 document and are extended with fronthaul parameters.
• Mover: Aleksandra Checko
• Seconder: Tony Tam
• Yes: _12_ No: _0_ Abstain: _0_ (technical motion needs >= 2/3)
2017-04-19Overview and requirements 15
![Page 16: Cover Page Using a Light Image - sagroups.ieee.org](https://reader031.vdocuments.us/reader031/viewer/2022030220/621e870a9765b02aff3313e5/html5/thumbnails/16.jpg)
Summary
• Proposal is to provide informative realistic throughput requirements, to be included in the standard
• Contributions to values of parameters to define deployment scenarios are welcome
2017-04-10 16Throughput requirements
Thank you