eCoMP:a usecase of the unified radio and optical control architecture
draft-zhang-ccamp-ecomp-00

Document Type Active Internet-Draft (individual)
Last updated 2019-06-16
Stream (None)
Intended RFC status (None)
Formats plain text pdf xml 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)
CCAMP Working Group                                          Z. Liu, Ed.
Internet-Draft                                             J. Zhang, Ed.
Intended status: Standards Track                             S. Liu, Ed.
Expires: December 18, 2019                                    Y. Ji, Ed.
                                                                    bupt
                                                           June 16, 2019

 eCoMP:a usecase of the unified radio and optical control architecture
                       draft-zhang-ccamp-ecomp-00

Abstract

   This document specifies a usecase, called enhanced coordinated multi-
   point (eCoMP), for integreting radio and optical networks.  It focus
   on the fronthaul flexibility that allows "any-RRH_A to any-BBU_A"
   connection to improve the eCoMP service performance.  The procedure
   of the usecase is based on the unified radio and optical control
   archtecture, and an extended OpenFlow protocol is introduced to
   realize the procedure.

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 https://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 December 18, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://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

Liu, et al.             Expires December 18, 2019               [Page 1]
Internet-Draft                    eCoMP                        June 2019

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Overview of eCoMP . . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Problem . . . . . . . . . . . . . . . . . . . . . . . . .   4
     5.2.  New Messages  . . . . . . . . . . . . . . . . . . . . . .   4
     5.3.  Normal Communication Procedure  . . . . . . . . . . . . .   6
       5.3.1.  Initialization Phase  . . . . . . . . . . . . . . . .   6
       5.3.2.  Lightpath Reconfiguration Request Sent by a
               Controller to a BBU_A . . . . . . . . . . . . . . . .   8
       5.3.3.  Lightpath Reconfiguration Request Sent by a
               Controller to a TN_A  . . . . . . . . . . . . . . . .   8
       5.3.4.  Lightpath Reconfiguration Reply Sent by a BBU_A to a
               Controller  . . . . . . . . . . . . . . . . . . . . .   9
       5.3.5.  Lightpath Reconfiguration Reply Sent by a TN_A to a
               Controller  . . . . . . . . . . . . . . . . . . . . .  10
   6.  the communication protocol Messages for eCoMP . . . . . . . .  11
     6.1.  The RRU_Feature_Req message . . . . . . . . . . . . . . .  11
     6.2.  The RRU_Feature_Rep message . . . . . . . . . . . . . . .  11
     6.3.  The TN_Feature_Req message  . . . . . . . . . . . . . . .  12
     6.4.  The TN_Feature_Rep message  . . . . . . . . . . . . . . .  12
     6.5.  The BBU_Feature_Req message . . . . . . . . . . . . . . .  12
     6.6.  The BBU_Feature_Rep message . . . . . . . . . . . . . . .  13
     6.7.  The RRU_A_Mod message . . . . . . . . . . . . . . . . . .  13
     6.8.  The RRU_A_Rep message . . . . . . . . . . . . . . . . . .  13
     6.9.  The TN_A_Mod message  . . . . . . . . . . . . . . . . . .  13
     6.10. The TN_A_Rep message  . . . . . . . . . . . . . . . . . .  14
     6.11. The BBU_A_Mod message . . . . . . . . . . . . . . . . . .  14
     6.12. The BBU_A_Rep message . . . . . . . . . . . . . . . . . .  14
   7.  Object Formats  . . . . . . . . . . . . . . . . . . . . . . .  14
     7.1.  Initialization Phase Object . . . . . . . . . . . . . . .  15
       7.1.1.  RRU feature request TLV . . . . . . . . . . . . . . .  15
       7.1.2.  TN feature request TLV  . . . . . . . . . . . . . . .  15
Show full document text