DETNET crosshauling requirements
draft-bernardos-detnet-crosshaul-requirements-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
DETNET WG                                                  CJ. Bernardos
Internet-Draft                                            A. de la Oliva
Intended status: Informational                                      UC3M
Expires: May 4, 2017                                        L. Cominardi
                                                            InterDigital
                                                           LM. Contreras
                                                                     TID
                                                        October 31, 2016

                    DETNET crosshauling requirements
            draft-bernardos-detnet-crosshaul-requirements-00

Abstract

   Future 5G networks will not make a clear distinction between
   fronthaul and backhaul transport networks, because varying portions
   of radio access network functionality might be moved toward the
   network as required for cost reduction and performance increase.
   This will pose additional challenges on the transport network,
   driving for a new design of integrated fronthaul and backhaul,
   usually referred to as crosshaul.

   This document present the crosshaul architecture framework being
   developed by the EU 5G-Crosshaul project, as well as identifies
   several key requirements for the transport network, with the goal of
   fostering discussion at the DETNET WG.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 4, 2017.

Bernardos, et al.          Expires May 4, 2017                  [Page 1]
Internet-Draft      DETNET crosshauling requirements        October 2016

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  5G-Crosshaul architecture . . . . . . . . . . . . . . . . . .   4
     3.1.  Data plane architecture . . . . . . . . . . . . . . . . .   6
   4.  Crosshaul requirements  . . . . . . . . . . . . . . . . . . .   6
   5.  Summary . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   8
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   According to recent predictions, mobile data traffic will increase
   11-fold between 2013 and 2018.  Fifth generation (5G) radio access
   network (RAN) technologies serving this mobile data tsunami will
   require fronthaul and backhaul solutions between the RAN and packet
   core to deal with this increased traffic load.  Furthermore, there
   will be a sizeable growth in the capillarity of the network since
   traffic load increase in the 5G RAN is expected to stem from an
   increased number of base stations with reduced coverage (i.e., mobile
   network densification).  To support the increased density of the
   mobile network (e.g., in terms of interference coordination) and
   achieve the required 5G capacity, extensive support for novel air
   interface technologies such as cooperative multipoint (CoMP), carrier
   aggregation (CA), and massive multiple-input multiple-output (MIMO)
Show full document text