Cloud Central Office Reference Architectural …

1 TECHNICAL REPORT The Broadband Forum. All rights reserved. TR-384 Cloud Central Office Reference Architectural Framework Issue: 1 Issue Date: January 2018 Cloud Central Office Reference Architectural Framework TR-384 Issue 1 January 2018 The Broadband Forum. All rights reserved 2 of 80 Notice The Broadband Forum is a non-profit corporation organized to create guidelines for broadband network system development and deployment. This Technical Report has been approved by members of the Forum. This Technical Report is subject to change. This Technical Report is copyrighted by the Broadband Forum, and all rights are reserved. Portions of this Technical Report may be copyrighted by Broadband Forum members. Intellectual Property Recipients of this Technical Report are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of this Technical Report, or use of any software code normatively referenced in this Technical Report, and to provide supporting documentation.

2 Terms of Use 1. License Broadband Forum hereby grants you the right, without charge, on a perpetual, non-exclusive and worldwide basis, to utilize the Technical Report for the purpose of developing, making, having made, using, marketing, importing, offering to sell or license, and selling or licensing, and to otherwise distribute, products complying with the Technical Report, in all cases subject to the conditions set forth in this notice and any relevant patent and other intellectual property rights of third parties (which may include members of Broadband Forum). This license grant does not include the right to sublicense, modify or create derivative works based upon the Technical Report except to the extent this Technical Report includes text implementable in computer code, in which case your right under this License to create and modify derivative works is limited to modifying and creating derivative works of such code.

3 For the avoidance of doubt, except as qualified by the preceding sentence, products implementing this Technical Report are not deemed to be derivative works of the Technical Report. 2. NO WARRANTIES THIS TECHNICAL REPORT IS BEING OFFERED WITHOUT ANY WARRANTY WHATSOEVER, AND IN PARTICULAR, ANY WARRANTY OF NONINFRINGEMENT IS EXPRESSLY DISCLAIMED. ANY USE OF THIS TECHNICAL REPORT SHALL BE MADE ENTIRELY AT THE IMPLEMENTER'S OWN RISK, AND NEITHER THE BROADBAND FORUM, NOR ANY OF ITS MEMBERS OR SUBMITTERS, SHALL HAVE ANY LIABILITY WHATSOEVER TO ANY IMPLEMENTER OR THIRD PARTY FOR ANY DAMAGES OF ANY NATURE WHATSOEVER, DIRECTLY OR INDIRECTLY, ARISING FROM THE USE OF THIS TECHNICAL REPORT. 3. THIRD PARTY RIGHTS Without limiting the generality of Section 2 above, BROADBAND FORUM ASSUMES NO RESPONSIBILITY TO COMPILE, CONFIRM, UPDATE OR MAKE PUBLIC ANY THIRD PARTY ASSERTIONS OF PATENT OR OTHER INTELLECTUAL PROPERTY RIGHTS THAT MIGHT NOW OR IN THE FUTURE BE INFRINGED BY AN IMPLEMENTATION OF THE TECHNICAL REPORT IN ITS CURRENT, OR IN ANY FUTURE FORM.

4 IF ANY SUCH Cloud Central Office Reference Architectural Framework TR-384 Issue 1 January 2018 The Broadband Forum. All rights reserved 3 of 80 RIGHTS ARE DESCRIBED ON THE TECHNICAL REPORT, BROADBAND FORUM TAKES NO POSITION AS TO THE VALIDITY OR INVALIDITY OF SUCH ASSERTIONS, OR THAT ALL SUCH ASSERTIONS THAT HAVE OR MAY BE MADE ARE SO LISTED. In addition to the notation above, the Forum draws attention to the fact that it is claimed that compliance with this Specification may involve the use of a patent ("IPR") concerning sections and The Forum takes no position concerning the evidence, validity or scope of this IPR. The holder of this IPR has assured the Forum that it is willing to License all IPR it owns and any third party IPR it has the right to sublicense which might be infringed by any implementation of this Specification to the Forum and those Licensees (Members and non-Members alike) desiring to implement this Specification.

5 Information may be obtained from: Trinity College Dublin College Green Dublin 02 Ireland Attention is also drawn to the possibility that some of the elements of this Specification may be the subject of IPR other than those identified above. The Forum shall not be responsible for identifying any or all such IPR. The text of this notice must be included in all copies of this Technical Report. Cloud Central Office Reference Architectural Framework TR-384 Issue 1 January 2018 The Broadband Forum. All rights reserved 4 of 80 Issue History Issue Number Approval Date Publication Date Issue Editor Changes 1 17 January 2018 31 January 2018 Georgios Karagiannis, Huawei Technologies Original Comments or questions about this Broadband Forum Technical Report s hould be directed to Editors: Georgios Karagiannis, Huawei Technologies Ding Hai, China Unicom SDN and NFV Work Area Director(s): George Dobrowski, Huawei Technologies Chris Croot, BT CloudCO Project Stream Leader(s): Yves Hertoghs, VMWare Ning Zong, Huawei Technologies Cloud Central Office Reference Architectural Framework TR-384 Issue 1 January 2018 The Broadband Forum.

6 All rights reserved 5 of 80 TABLE OF CONTENTS EXECUTIVE SUMMARY .. 8 1 PURPOSE AND SCOPE .. 9 PURPOSE .. 9 Overview .. 9 Purpose of this Document .. 9 RELATIONSHIP TO OTHER WORK .. 9 SCOPE .. 10 2 REFERENCES AND TERMINOLOGY .. 11 CONVENTIONS .. 11 REFERENCES .. 11 DEFINITIONS .. 12 ABBREVIATIONS .. 14 3 TECHNICAL REPORT IMPACT .. 19 ENERGY EFFICIENCY .. 19 IPV6 .. 19 SECURITY .. 19 PRIVACY .. 20 4 INTRODUCTION .. 21 5 CHARACTERISTICS OF A Cloud Central Office .. 22 THE Cloud Central Office CONTEXT .. 22 DECOMPOSITION OF Central Office LEGACY ENTITIES .. 22 Disaggregation Considerations .. 23 Virtualization Considerations .. 24 PNF Requirements .. 27 Multi Tenancy Considerations .. 27 Decomposition of the BNG .. 29 Decomposition of the Access Node.

7 32 Decomposition of CPE .. 36 HYBRID ARCHITECTURES .. 36 6 Architectural FRAMEWORK .. 37 INTRODUCTION .. 37 CloudCO Macro-node Description .. 40 FUNCTIONALITY OF THE CLOUDCO .. 46 CLOUDCO DOMAIN ARCHITECTURE IN DETAIL .. 47 CloudCO Reference Points & Catalogs .. 51 CloudCO blocks role and functions .. 54 NETWORK QOS FRAMEWORK .. 61 Overview .. 61 Connectivity Constructs .. 63 Implications of a Shared UNI .. 67 Cloud Central Office Reference Architectural Framework TR-384 Issue 1 January 2018 The Broadband Forum. All rights reserved 6 of 80 Combining in and out of Profile Traffic .. 68 PHYSICAL AND VIRTUAL NETWORK FUNCTION RECONSTRUCTION .. 68 Distributed Routing Options .. 68 User plane Programming as a Result of Disaggregation .. 69 Virtualization Options.

8 69 Service Chaining .. 69 Offering Functionality As-a- service .. 69 Cloud Central Office Northbound API Description .. 70 Cloud Central Office Northbound API: Capabilities .. 71 7 DYNAMIC BEHAVIOR OF A CLOUDCO .. 72 CLOUDCO DOMAIN BOOTSTRAP .. 72 DYNAMIC BEHAVIOR OF CLOUDCO INTERFACES .. 74 Os-Ma-ccodo (CloudCO Northbound API) .. 74 Or-Vi .. 75 Occo-Nf-sdn-pnf .. 76 Occo-Nf-sdn-vnf .. 76 Mfc-sdn-dc-Nf .. 76 Minf/Ms .. 77 Mfc .. 77 8 NEXT STEPS .. 78 CLOUDCO APPLICATION NOTES .. 78 CLOUDCO INTERFACE DESCRIPTIONS .. 78 CLOUDCO TEST CASES .. 78 Cloud Central Office Reference Architectural Framework TR-384 Issue 1 January 2018 The Broadband Forum. All rights reserved 7 of 80 List of Figures Figure 1: Example of disaggregation and virtualization.

9 26 Figure 2: Alternative example of disaggregation and virtualization .. 27 Figure 3: Functional components inside BNG and the interactions with external entities .. 29 Figure 4: Control plane and user plane separation of the disaggregated BNG .. 31 Figure 5: Functional components inside BNG for scenario that both control plane and user plane are virtualized .. 32 Figure 6: Functional components in an Access Node .. 33 Figure 7: Functional components in OLT .. 34 Figure 8: CloudCO in context of end to end service orchestration .. 37 Figure 9: Example of deployment of multiple CloudCO Domain Orchestrators .. 39 Figure 10: CloudCO macro-node structure .. 41 Figure 11: Example of deployment of VNF over multiple sites .. 45 Figure 12: Example of deployment of a distributed switch fabric serving dispersed subscribers.

10 45 Figure 13: CloudCO Reference architecture .. 47 Figure 14: Broadband Access Abstraction layer .. 57 Figure 15: BAA within the CloudCO architecture .. 58 Figure 16: BAA applied to a PON AN .. 60 Figure 17: Possible connectivity configurations .. 63 Figure 18: 1:1 access model with a locally hosted VNF .. 64 Figure 19: n:1 access model with a locally hosted VNF .. 66 Figure 20: P2C WAN model .. 66 Figure 21: P2P WAN model .. 67 Figure 22: E2E transit .. 67 Figure 23: Baseline dynamics of CloudCO (CCO) Domain bootstrap .. 73 List of Tables Table 1: Multi-tenancy models and requirements .. 28 Table 2: ETSI NFV Reference Points .. 52 Table 3: BBF Reference Points .. 53 Table 4: ETSI NFV Data Repositories .. 54 Table 5: BBF Data Repositories .. 54 Table 6: New BBF Reference points .. 64 Cloud Central Office Reference Architectural Framework TR-384 Issue 1 January 2018 The Broadband Forum.