Goals and objectives Project(s): MBH IA Phase 4 Transport for 5G Networks Purpose of the contribution: Input to MBH IA Phase 4 Abstract: Overview on the.

Slides:



Advertisements
Similar presentations
Geneva, Switzerland, 13 July 2013 Ethernet Protection and Packet Synchronization Seminars/ethernet/201307/Pages/default.aspx.
Advertisements

1 Introducing the Specifications of the Metro Ethernet Forum.
1 Introducing the Specifications of the Metro Ethernet Forum.
1 Introducing the Specifications of the Metro Ethernet Forum.
ACN: IntServ and DiffServ1 Integrated Service (IntServ) versus Differentiated Service (Diffserv) Information taken from Kurose and Ross textbook “ Computer.
1 Introducing the Specifications of the Metro Ethernet Forum.
Geneva, Switzerland, 13 July 2013 IEEE Time-Sensitive Networking Michael Johas Teener TSN chair, IEEE Joint IEEE-SA and ITU Workshop on Ethernet.
Distributed Multimedia March 19, Distributed Multimedia What is Distributed Multimedia?  Large quantities of distributed data  Typically streamed.
Software-defined architectures for convergent fixed-radio access Carlos Bock, Jordi Ferrer, Volker Jungnickel, David Levi, Victor Marques, Tiago Mendes,
Cable network and multimedia services Speaker: 陳羿仲 Advisor: 吳和庭 2012/12/05.
1 Presentation_ID © 1999, Cisco Systems, Inc. Cisco All-IP Mobile Wireless Network Reference Model Presentation_ID.
DetNet BoF IETF #93 DetNet Problem Statement Monday, July 20 th, 2015 Norman Finn draft-finn-detnet-problem-statement.
Modeling and Simulating Time- Sensitive Networking Harri Laine.
1 | © 2015 Infinera Open SDN in Metro P-OTS Networks Sten Nordell CTO Metro Business Group
Omniran CF00 1 VLANs in relation to P802.1CF NRM Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Internet Protocol Storage Area Networks (IP SAN)
© 2007 EMC Corporation. All rights reserved. Internet Protocol Storage Area Networks (IP SAN) Module 3.4.
Leveraging SDN for The 5G Networks: Trends, Prospects and Challenges ADVISOR: 林甫俊教授 Presenter: Jimmy DATE: 2016/3/21 1.
IETF DetNet and IEEE Time-Sensitive Networking
IEEE Distinguished Minimum Latency Traffic
Pedro Moreira CERN BE-CO-HT
Service Experience Assured Network (SEAN) Introduction and Demo
Instructor Materials Chapter 6: Quality of Service
Chapter 9 Optimizing Network Performance
Time Sensitive Networking within the scope of P802.1CF
Progress of Network Architecture Work in FG IMT-2020
DETNET crosshauling requirements draft-bernardos-detnet-crosshaul-requirements Carlos J. Bernardos (UC3M), Antonio de la Oliva (UC3M), Luca Cominardi (InterDigital),
draft-huang-detnet-xhaul-00
IEEE 802 OmniRAN Study Group: SDN Use Case
2 ATIS 5G OVERVIEW ATIS launched its 5G Ad Hoc in 2015 to advance regulatory imperatives, deliver an evolutionary path, address co-existence of technologies,
Wireless ATM & Congestion Control
IEEE Time-Sensitive Networking (TSN)
IEEE Time-Sensitive Networking (TSN)
P802.1CM Time-Sensitive Networking for Fronthaul
DetNet Service Model draft-varga-detnet-service-model-01
doc.: IEEE <doc#>
IEEE Time-Sensitive Networking (TSN)
Wi-Fi Time Sensitive Networking
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 6: Quality of Service Connecting Networks.
Mobile Synchronization Trends 4G to 4.5G to 5G
Submission Title: [FHSS Proposal] Date Submitted: [May 12, 2009]
Time Sensitive Networking within P802.1CF
Brief Introduction to IEEE P802.1CF
Time Sensitive Networking within the scope of P802.1CF
Reference Model Proposal
DetNet Data Plane Protection Implementation Report
November 18 July 2008 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Task Group 4e definitions Date.
Time Sensitive Networking for 5G
NTHU CS5421 Cloud Computing
Collaboration between 2.4/5 and 60 GHz
Carlos J. Bernardos, Alain Mourad, Akbar Rahman
RAN Functional Decomposition the options and interfaces…
TSN Yaakov (J) Stein.
Thoughts on IEEE 802 network integration with respect to P802.1CF
Time-Aware shaping (802.1Qbv) support in the MAC
IEEE 802 Scope of OmniRAN Abstract
IEEE Time-Sensitive Networking
Time-Aware Traffic Shaping over
Thoughts on IEEE 802 network integration with respect to P802.1CF
XRAN (eCPRI) S-Plane Sync Update
Computer Networking A Top-Down Approach Featuring the Internet
Time-Sensitive Applications Support in EHT
DetNet Configuration YANG Model Update
DetNet Bounded Latency-02
IEEE Time-Sensitive Networking (TSN)
DetNet Bounded Latency-04
Editors: Bala’zs Varga, Jouni Korhonen
DetNet Bounded Latency-01
TSN support in and potential extensions for TGbe
Large-Scale Deterministic Network Update
Presentation transcript:

Goals and objectives Project(s): MBH IA Phase 4 Transport for 5G Networks Purpose of the contribution: Input to MBH IA Phase 4 Abstract: Overview on the IEEE P802.1CM Time-Sensitive Networking for Fronthaul project Motion: no

IEEE P802.1CM Time-Sensitive Networking for Fronthaul János Farkas – Ericsson April 25, 2017 MEF 61035

Agenda Introduction Approach to Ethernet-based fronthaul IEEE 802.1 Time-Sensitive Networking (TSN) overview 5G overview, 5G fronthaul, Radio Base Station split Approach to Ethernet-based fronthaul IEEE 802.1CM TSN for Fronthaul – goals and objectives Collaborative effort of CPRI Cooperation and IEEE 802.1 Top Down Approach Requirements Fronthaul Profiles (so far) Summary of IEEE P802.1CM Potential MEF 22 – P802.1CM collaboration items

IEEE 802.1 Time-Sensitive Networking (TSN) Overview TSN Components Common Standards Time synchronization: Timing and Synchronization (802.1AS) includes a profile of IEEE 1588 Ultra reliability: Frame Replication and Elimination (P802.1CB) Path Control and Reservation (802.1Qca) Per-Stream Filtering and Policing (802.1Qci) Reliability for time sync (P802.1AS-Rev) Synchronization Reliability Latency Bounded low latency: Credit Based Shaper (802.1Qav) Frame preemption (802.3br & 802.1Qbu) Scheduled Traffic (802.1Qbv) Cyclic Queuing and Forwarding (802.1Qch) Asynchronous Traffic Shaping (P802.1Qcr) Resource Mgmt Dedicated resources & API Stream Reservation Protocol (802.1Qat) TSN configuration (P802.1Qcc) YANG (P802.1Qcp) Link-local Registration Protocol (P802.1CS) Zero congestion loss Guaranteed data transport with bounded low latency, low delay variation, and extremely low loss http://www.ieee802.org/1/pages/tsn.html API: Application Programming Interface; YANG: a data modeling language Note: selecting features is a task in the P802.1CM TSN for Fronthaul project

5G Overview Ethernet-based fronthaul is integral part of 5G 5G Radio Access 3 GHz 10 GHz 30 GHz 100 GHz Higher Frequencies Larger BW Spectrum Flexibility Access-backhaul Integration (incl. self-backhauling) Ultra-lean Design Device-to-Device Communication Inter-Site Cooperation Multi-antenna technologies 5G Core functionality Utilize NFV and SDN Network programmability Flexible deployment of network functions Service enablers and optimizations Multi-use case Common toolbox 5G Use Cases Broadband everywhere Smart vehicles transport and infrastructure Media everywhere Critical control of remote devices Interaction human IoT … and more Management Orchestration Network management Analytics Fixed access Cloud Infrastructure Network integrated compute and storage Legacy RATs 5G Transport SDN Backhaul Fronthaul Aggregation Network programmability Optical enablers Ethernet-based fronthaul is integral part of 5G

5G Fronthaul – Simplified Architecture Radio Base Station (RBS) backhaul RBS split Radio Equipment (RE) Radio Equipment Control (REC) fronthaul backhaul Radio Base Station (RBS) baseband

Radio Base Station Split Further splits are possible No split Current split (CPRI 7.0) Possible splits PDCP PDCP PDCP: Packet Data Convergence Protocol RLC: Radio Link Controller Layer 3 Layer 2 Layer 1 Radio Layer 3 Layer 3 Layer 3 Layer 3 RLC RLC Layer 2 Layer 2 Layer 2 Layer 2 MAC MAC PHY PHY eCPRI Layer 1 Layer 1 Layer 1 Layer 1 Radio Radio Radio Radio Radio Radio Current focus of P802.1CM is the functional split specified by the Common Public Radio Interface (CPRI) 7.0 Next step in P802.1CM is eCPRI (http://www.cpri.info/press.html) Further functional splits can be addressed in 802.1CM amendment

Approach to Ethernet-based Fronthaul RE fronthaul REC interface Radio Domain MEF Services MEF UNI IEEE 802.1/802.3 Ethernet network Packet Domain (Ethernet-based) Ethernet networking specified by IEEE 802.1CM TSN for Fronthaul

IEEE 802.1CM TSN for Fronthaul Goals & Objectives RE1 Bridged network for Fronthaul REC1 REC2 RE2 RE3 Standard TSN Profiles for fronthaul Enable the transport of fronthaul streams in a bridged network A TSN Profile Specifies aspects of bridge operation Set of feature and option selections Configuration guideline

Collaborative effort of CPRI Cooperation and IEEE 802.1 http://www.cpri.info/ Fronthaul experts Continuous development of CPRI specifications for 15 years eCPRI (http://www.cpri.info/press.html) IEEE 802.1 http://www.ieee802.org/1/ Ethernet networking experts Packet networking standards for decades Time-Sensitive Networking (TSN) Both organizations have proven that they deliver P802.1CM TSN for Fronthaul is a collaborative effort Joint sessions: face-to-face and virtual Common members Ethernet-based packet fronthaul is on its way

P802.1CM Project Takes Top Down Approach Collect requirements CPRI Cooperation provides use cases and requirements Collect the packet networking and synchronization features to address requirements Bridging features and characteristics Time-Sensitive Networking features Synchronization solutions and approaches ITU-T Q13/15 contributes (e.g., how to leverage the IEEE 1588 Telecom profile) Specify solution details Profiles specify how to meet the fronthaul requirements in an Ethernet network

Requirements – Contributed by CPRI Cooperation Class 1 RBS functional split is according to CPRI 7.0 CPRI information flows are separated from each other IQ data and the C&M data are independent data streams, NO CPRI  Eth mapping “as is” IQ data requirements maximum end-to-end One-way Frame Delay = 100 μs (no requirement on Frame Delay Variation) maximum Frame Loss Ratio = 10-7 C&M data requirement: maximum Frame Loss Ratio = 10-6 Class 2 eCPRI (to be added) Synchronization Synchronization is provided separately from IQ and C&M, e.g., GNSS, PTP 4 time synchronization requirement Categories for different 3GPP features

Fronthaul Profiles for Class 1 (so far) Profiles are engineered taking into account the worst-case Profile A Keep it as simple as possible Based on strict priority IQ data  high priority traffic class C&M data  lower priority traffic class Max frame size for all traffic: 2000 octets (IEEE 802.3) Profile B Leverage simple TSN features Based on strict priority and frame preemption (802.3br and 802.1Qbu) IQ data  high priority traffic class; express traffic C&M data  lower priority traffic class; preemptable traffic Frame size maximized for IQ data; arbitrary for other traffic

Ethernet-based Fronthaul with IEEE 802.1CM Radio Domain REC fronthaul flows are separated, e.g., by priority, VID synchronization is separated from fronthaul data flows RE user (IQ) fronthaul interface CPRI, eCPRI, etc. user (IQ) C&M C&M SaaS separated fronthaul flows separated fronthaul flows MEF Services MEF UNI edge ports perform std IEEE 802.1/802.3 Ethernet encapsulation Packet Domain IEEE 802.1CM IEEE 802.1CM Fronthaul Profiles meet the requirements of fronthaul flows Synchronization can be provided by packet network, e.g., Sync as a Service (SaaS) IEEE 802.1/802.3 Ethernet encapsulation

P802.1 CM Summary IEEE 802.1CM specifies TSN Profiles for Fronthaul It is a collaborative effort of CPRI Cooperation and IEEE 802.1 The project takes top down approach: requirements  solution Requirements are provided by CPRI Cooperation Current focus: RBS split according to CPRI 7.0 and the different fronthaul information flows are supported separately Two Fronthaul Profiles (so far) Support for eCPRI is next step Work in progress; Welcome to contribute! http://www.ieee802.org/1/pages/802.1cm.html

Potential MBH IA – P802.1CM Collaboration Items Sync as a Service (SaaS) SaaS provided by the Ethernet network is one of the options to provide synchronization for fronthaul if the requirements are met SaaS specified by MEF 22.2 and 22.2.1 is referred in IEEE 802.1CM Potential discussion items for MBH IA Phase 4 Transport for 5G 3 different CoS are needed for fronthaul: user (IQ) data + C&M + Sync Sync is already defined The requirements of user (IQ) data and C&M have to be met Any new CoS?