NGFI packet format for various functional splits

Transcription

1 Andrijana Popovska Avramova, Foxconn Aleksandra Checko, MTI Morten Høgdal, Foxconn IEEE 1914 f2f meeting, Beijing, China 01/17-19/2017

2 Compliance with IEEE Standards Policies and Procedures Subclause 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, and the IEEE- SA Standards Board Operations Manual, section 6.1, The IEEE Standards patent policy as stated in the IEEE-SA Standards Board Bylaws, section 6, and the IEEE-SA Standards Board Operations Manual, section 6.3, 2

3 IEEE 1914 Next Generation Fronthaul Interface Jinri Huang, Date: Author(s): Name Affiliation Phone [optional] [optional] Andrijana Popovska Avramova Aleksandra Checko Morten Høgdal Foxconn MTI Foxconn

4 Introduction defines the Ethernet frames transporting IQ symbols: Time domain (Option 8) Frequency domain (Option 7.1) How to approach the new options for split in the baseband chain currently being addressed by ? 4

5 Agenda Discuss the need for interface definition for functional split: Case study of Option 7.2 within Subclass 1 Case study of Option 5 within Subclass 2 Case study of Option 2 within Subclass 3 Generalization of the interfaces Goal: Discussion on how much we can generalize the interface for the concluded NGFI classes (within ) 5

6 CASE STUDY OF DIFFERENT SPLITS (DL) 6

7 PHY split: Option 7.2 DL Define the data format Define the DL control information (ex. DM-RS, codebook, resource assignment) Define the mappers (ex. CS-RS, port-antenna mapping) Layer mapping DL Data precoding Resource mapping Antenna mapping IFFT and CP insertion (OFDM signal generation) RF FH DM-RS Port-antenna Codebook? Ressource assignement CS-RS

8 MAC Split: Option 5 Define the data format: ex. MAC PDUs (MAC SDUs) Define the control information: ex. DCI, UCI Define the mappers: number of MIMO layers Control data RRC PDCP/RLC C-MAC DL Data FH D-MAC PHY Control data

9 PDCP-RLC split: Option 2 Define the data format: PDPC PDUs Define the control information: flow control, RRC setup Define the mappers: size of buffers, maximum buffer size per UE Control data RRC PDCP DL Data RLC MAC FH Control data

10 for NGFI classes Can we reuse the Ethernet type? RoE Header definition: Suggest definition of subtype Keep the flow ID Keep length and orderinginfo Payload and mappers to be defined by 3GPP, considerable effort to be clearly defined within IEEE 1914 group? Definition of a minimum set of mappers ID, Flow, src, dest, compression scheme, etc. (as defined) Any others that should be considered? 13

11 Current RoE subtypes tf3_1610_maiden_native-packet-types_2.pdf 14

12 Subtypes for NGFI Subclass definition Subtype is 8 bit field We suggest the following definition of subtype to accommodate different requirements: XXXb subclass 1 covers already specified split 8 and 7.1 space for 8 splits XXXb subclass 2 space for 8 splits XXXb subclass 3 space for 8 splits Not part of PAR to deal with non-iq Where to address it? A new filed in the header that defines the traffic type? embb, URLLC and emtc? 15

13 Motion # For amendments to : agree on subtypes definition for NGFI subclasses as : XXXb subclass XXXb subclass XXXb subclass 3 Mover: Aleksandra Checko Seconder: Yes: No: Abstain: (technical motion needs >= 2/3) 17