Overview

The Architecture and Transport Architecture (ATA) Working Area (WA) has a rich history in defining various BNG architectures and requirements, from classic functions such as L2TP LAC to more recent functions such as Network Enhanced Residential Gateway (NERG) and Public Wi-Fi access in MS-BNG.  The MS-Disaggregated BNG (DBNG) is an on-going project at ATA.   TR-459 serve as a foundation document in defining the the architecture and requirements for a DBNG.  Standardizing interfaces and protocols will ensure interoperability between various types of control planes and user planes deployments.  One of the key objective TR-459 is to ensure the DBNG provides the same broadband service offerings as a classic MS-BNG. Compared to a classic MS-BNG, the MS-DBNG have several key advantages such as independent user plane and control plane scaling, independent control and user plane life cycle management, and centralized control plane for configuration.  The separation of the control plane and user plane enables more efficient use of resources and simplifies operations.  In addition, BBF is a forum that allows synergy amongst various work area and creates a unified vision for the broadband industry.  An example of this is WT-459 the protocol selected for the State Control Interface (SCI) named, Packet Forwarding Control Protocol (PFCP).  PFCP, a protocol defined by 3GPP in TS 29.244 for control and user plane separation (CUPS) communication, is used for 4G and 5G 3GPP architecture.  In WT-458, CUPS for fixed mobile convergence, BBF again selected PFCP for the SCI.  This is one of many examples of how BBF is providing a platform for all stakeholders to collaborate and create synergy across different Working Areas with a unified vision for Broadband.The DBNG project continue to define and study new architecture and new requirement of interest to service providers and vendors.  DBNG YANG modeling, DBNG CG-NAT, and DBNG User Plane traffic steering are just some of the current working projects related to DBNG.  New DBNG topics are encouraged to be brought to the ATA group through contributions, the following link provide the most up-to-date topics.

Project Deliverables under Development

See BBF Work in Progress - Projects, Project Streams, and Jira Links

Filter the table at the link above on Work Area = "ATA" and Project Stream = "Access Architecture"

Completed Project Deliverables

Project Overview

Purpose: BNGs and virtual BNGs are generally configured with SSH/telnet/SNMP protocols today. Current evolution of BNG function is requiring much more flexibility in terms of programmability thus requiring the BNGs and vBNGs to interface with SDN Controllers and/or new Element Managers. In order to achieve BNG and vBNG programmability, availability of BNG/vBNG YANG models is required.IETF has already created some YANG data modules that can be reused for being applied to BNG/vBNGs, some examples are:

• RFC8344 “A YANG Data Model for IP Management”

• RFC8022 “A YANG Data Model for Routing Management”

• RFC8347 “A YANG Data Model for the Virtual Router Redundancy Protocol (VRRP)”

• RFC8349 “A YANG Data Model for Routing Management (NMDA Version)”

• RFC8345 “A YANG Data Model for Network Topologies”

• RFC7317 “A YANG Data Model for System Management”

• RFC8294 “Common YANG Data Types for the Routing Area”

• Draft RFC “A YANG Data Model for Routing Policy Management”

However the above mentioned data models are not sufficient for configuring and managing a BNG/vBNG, in particular among the others data models for the subscriber management are missed as it is indeed one of functionalities of a BNG actually.

Motivation:

This project has been created in order to close a gap we currently have with respect to Access Node where projects on YANG data Models already exist since years, while none has been created for BNG/vBNG.

Scope:

The scope of this project is to define and develop the set of YANG data modules needed for configuration and monitoring (FCAPS) of BNGs/vBNGs as follows:

• Identification of Existing applicable YANG models in IETF or other SDO

• Development of YANG models to cover BNG functionalities that are not sufficiently covered by existing YANG models

This project can be managed as other projects in Common YANG PS (for example TR-383), that is it can be an ongoing project. When one or more YANG modules are ready for publication they will go through SB and FB in the same way as any other WT and it will be published, and then work on the next Amendment will immediately begin. The new BBF’s YANG DMs and those published by IETF for BNG/vBNG are expected to be cross referenced in future TR-413 Issue 2.

Project Deliverables under Development

See BBF Work in Progress - Projects, Project Streams, and Jira Links

Filter the table at the link above on Work Area = "ATA" and Project Stream = "Access Architecture"

Completed Project Deliverables

Project Overview

Purpose:

As Broadband Networks become more dynamic with SDN control and Cloud Central office, it is now possible to programmatically control which User Plane (UP) function each individual subscriber should be connected to.  This creates many advantages for an operator to offer different service propositions to different customers.At the same time, User Plane functions (such as the BNG) are becoming increasingly disaggregated and cloud native, with centralised control plane and subscriber state and the ability to scale out (add additional UP processing functions) to manage short term or long term changes in load. There is a need for a standardised approach for a disaggregated service function ,such as a disaggregated BNG (dBNG), to be able to be able to identify to which UP instance newly authenticating subscribers should be connected, or to request that existing subscribers should be redistributed or moved between UP instances.  In other words, we need to define an architecture and interfaces such that the access network can offer an ingress load-balancing capability towards cloud-native user plane functions

Motivation:

Network Operators will not be able to effectively deploy disaggregated service functions such as the dBNG without a standardized approach to balance and move subscribers between UP instances. Service Providers increasingly desire to differentiate the services that are offered to individual customers (eg low latency / by revenue / for high throughput).   This project will enable increasing differentiation by steering subscribers to a suitable UP function.  This could include UP that are deployed to offer different SLA (i.e edge services).  It may also include use cases where a subscriber-specific User Plane is created on demand, to which the subscriber session is then dynamically connected.Network Operators need new tools to be able to manage and upgrade networks as the industry moved to sdn/nfv.  Session Steering will enable software deployment approaches in line with the cloud paradigm (such as automated incremental upgrades with canary testing on a small number of subscribers), as well as additional network resilience.Our industry is under increasing pressure to reduce power usage.  The ability to dynamically move active subscribers between functions without service impact will allow hardware / software to be temporarily removed from service at certain times of the day.

Scope:

This project will create a WT that defines an architecture for Subscriber Session Steering, using the dBNG as an exemplary function.  

The following are in scope for inclusion in the project:Phase 1:

• Identification & definition of the opportunities and use cases for session steering.

Phase 2:

• How to identify the UP instances that can serve a subscribers requirements

• How to balance newly authenticating subscribers amongst the available UP instances that can meet their requirements.

• How to request that a subscriber or group of subscribers is moved from one UP instance to a different UP instance (without customer impact if at all possible).

• How a change in subscriber policy can trigger a change in the placement of a subscriber.

• Requirements on the SDN controller to support session steering

• Requirements for the Service Function (eg dBNG) to support session steering

• Identification of the protocols and interfaces that will be used

Note: the term 'Subscriber Session' is used within the context of this NPIF as per the definition in TR-146.  It is recognized that there may be use cases for steering with a different context of session (IP session or even IP Flow), but this is currently out of scope. 

Project Deliverables under Development

See BBF Work in Progress - Projects, Project Streams, and Jira Links

Filter the table at the link above on Work Area = "ATA" and Project Stream = "Access Architecture"

Completed Project Deliverables

Project Overview

Purpose:

This projects focuses on control/user plane separation of BNG in the case of wired access (e.g. PON, xDSL, etc). It will start with use case details, including deployment scenarios and operational aspects, then move to architectural framework and finally move to protocol considerationsThis project profiles DBNG aspects specific to MS-BNG aggregating subscribers over wired access networks, including fixed access(e.g. PPPoE, IPoE, L2TP, etc.), CGN, multicast, resilience, etc.It will define use case, architecture, requirements and CUPS protocol for wired access. 

Motivation:

Continue to promote BNG enhancements that allow more flexibility in terms of deployment models and multi-vendor interoperability between disaggregated components.Key business impact: benefits of network disaggregation applied to fixed subscriber management; additional deployment models to adapt to wide areas of operators requirementsScope:This project profiles DBNG aspects specific to MS-BNG aggregating subscribers over wireline access networks. The scope of this new project addresses a subset of the fixed access use cases found in TR-459 and potential additional fixed use cases.This project excludes any use cases that includes wireless access (4G/5G, Wi-Fi,…), hybrid access and wireless-wireline convergence. Such use cases are addressed by TR-459 cases in addition to the wireline baseline.The project is phased with checkpoints in-between phases, to ensure clear transitions between stage 1/ 2/ 3 aspects.

Phase 1: Scope and DBNG for wired access Use Cases

• Detailed scope/ non-scope for the document

• List and Describe use cases with wireline access

• Identify service-level aspects (e.g. high speed internet, voice, IPTV,…) and key enablers (e.g. HQoS, multicast, etc)

• Include deployment scenarios (e.g. distribution) and operational aspects

• Identify any candidate architectural extensions meeting use cases requirements and deployment scenarios 

• Include interoperability aspects

• Identify adjacent BBF projects if applicable (eg. Traffic steering)

• Refer to TR-459: deltas, including additional use cases, should be clearly highlighted, if any

-----------Phase 2: Architectural Aspects for DBNG in fixed access & Requirements for nodes and interfaces/protocols between CP and UP

• DBNG functional architecture – refer to TR-459 section 4.3, but limited to wireline access models and relevant functional blocks. Includes external interfaces (e.g., B interface)

• Define interfaces between CP and UP – Expecting Mi, SCi, CPRi to still be relevant; refer to TR-459, identify subsets and deltas in case of wired-only access.

• Call flows – protocol independent presentation

• Define general, protocol-independent requirements for each interface type

• Specify common call flow principles to define points and conditions in the flow that result in subscriber/node level UP programming and status reporting

• Specify common protocol requirements with regards to per node, per subscriber state programming and reporting, status / event-based updates, security, reliability, resilience, etc.

• For the requirements that have already been defined in TR-459, this project will not try to redefine them, instead, references to those requirements will be added.

-----------Phase 3: Protocol specific aspects

• Protocol analysis:

  • candidates and evaluation of protocol fit with requirements - goal is multi-vendor interoperability

  • PFCP evaluation – required subset to cover wireline only; analysis of flaws and deficiencies, if any

• Alternative protocol option(s)

• Depending on analysis results, create annexes in the same document describing use of specific protocol in the context of DBNG for wired access, possible protocol enhancements, specific attributes / extensions for BBF, etc.

• For now, the project does not make assumptions if one, two or more protocols can be applicable to support DBNG fixed-only.

• This annex/these annexes is/are the only content which is protocol specific.

Between each phase, consensus is required to agree to progress to the next phase. The goal is to proceed in a top-down fashion, encouraging the group to focus contributions relevant for the active phase, getting to a stable content before moving to the next level of detail.This project is expected to leverage the protocol-independent areas of TR-459 (e.g. architecture, functional decomposition,…) for what is relevant for fixed only. As much as possible, consistency with protocol independent aspects of TR-459 should prevail.It is understood that following issues/revisions of TR-459 will continue in parallel to this new project (eg. CGNAT and multicast support). This does not preclude this new project to cover these use cases.Upon completion of this working text, some Marketing Document can be generated to advertise BBF recommendations

Project Deliverables under Development

See BBF Work in Progress - Projects, Project Streams, and Jira Links

Filter the table at the link above on Work Area = "ATA" and Project Stream = "Access Architecture"

Completed Project Deliverables

Project Overview

Public Wi-Fi user authentication and data local forwarding technical requirements

Purpose:

This project aims to define the network architecture and technical requirements for Wi-Fi users to be uniformly authenticated by AC and local forwarding of user data, so that Wi-Fi devices developed by device manufacturers can meet the requirements of Wi-Fi networking and operation requirements. This project is to focus on the requirements and use case aligned and complementary to TR-321.

Motivation:

Further promote the development of Wi-Fi networking technology. The implementation of this project can realize the networking technology of Wi-Fi users focusing on AC authentication and management and local forwarding of user data. A variety of AC devices can be used for networking, including traditional dedicated AC and NFV based virtual  AC(vAC) , etc. AC can also be deployed in the cloud. This networking mode can meet the new requirements of operators.

Scope:

Based on the TR-321 architecture 3, the project contents including the following three aspects shall be carried out

1.Define networking scenarios.

1）The AC is deployed on the network cloud, and the AP connects to the AC through the Internet by a gateway device.

2）The AC is deployed on the edge of the metropolitan area network or on the access network side, and APs access the AC through dedicated lines.

2.Propose user cases and formulate operation processes,

1) User address allocation operation process.

2) User association process.

3) User online operation process.

4) User offline operation process.

3.Put forward equipment technical requirements.

Project Overview

Project Deliverables under Development

See BBF Work in Progress - Projects, Project Streams, and Jira Links

Filter the table at the link above on Work Area = "ATA" and Project Stream = "Mobile Transport and Routing (MT&R)"

Completed Project Deliverables

Project Overview

This project delivers documentation that gives the referece architecture, functions and requirements of MMI interfaces for providing an IETF Network Slice required in context of 5G network slice.

Project Deliverables under Development

See BBF Work in Progress - Projects, Project Streams, and Jira Links

Filter the table at the link above on Work Area = "ATA" and Project Stream = "Mobile Transport and Routing (MT&R)"

Completed Project Deliverables

Project Overview

To define how test traffic is specified and generated at the application layer. It supports specification of test traffic, as well as associated metrics and measurement methods, that reflects the complexity resulting from multiple types of applications and subscribers aggregated in a common network.

Project Deliverables under Development

See BBF Work in Progress - Projects, Project Streams, and Jira Links

Filter the table at the link above on Work Area = "ATA" and Project Stream = "Performance, Experience, and Application Testing (PEAT)"

Completed Project Deliverables

Project Overview

This project will extend Broadband Forum’s OAM framework with architectural and nodal requirements to enable Customer Equipment to IP Edge service assurance of broadband subscribers, both for business and residential connections.

The main business drivers for this work are:

• Define standardized mechanisms for performance measurement (e.g. delay, jitter, loss) between network side of the RG/CPE and access side of the BNG/PE
• Give service providers insight on how their access network is performing
• Ability to use existing but not currently deployed tools

The BBF is in a unique position to give service providers the tools they need in this subject matter, defining a solution that allows measurement and exposure of RG/CPE to BNG/PE network performance and addresses the current gap.

Project Deliverables under Development

See BBF Work in Progress - Projects, Project Streams, and Jira Links

Filter the table at the link above on Work Area = "ATA" and Project Stream = "Performance, Experience, and Application Testing (PEAT)"

Completed Project Deliverables

Project Overview

This project will deliver documentation that gives a comprehensive overview of Quality Attenuation and its applicability to broadband networks. It will cover the theory, measurement technique, use-cases and benefits of the approach.

Project Deliverables under Development

See BBF Work in Progress - Projects, Project Streams, and Jira Links

Filter the table at the link above on Work Area = "ATA" and Project Stream = "Performance, Experience, and Application Testing (PEAT)"

Completed Project Deliverables

Project Overview

Standardize the IP-Layer Capacity Metric and Measurements with the benefit of BBF membership's unique expertise and perspectives. Ideally, to harmonize the Industry around a specific Capacity metric and method with clear benefits of multi-dimensional performance assessment at existing and new Gigabit-rate access speeds.

Project Deliverables under Development

See BBF Work in Progress - Projects, Project Streams, and Jira Links

Filter the table at the link above on Work Area = "ATA" and Project Stream = "Performance, Experience, and Application Testing (PEAT)"

Completed Project Deliverables

Project Overview

This project is to address the needs of an operator to monitor and assure a platform for service delivery, encompassing QoS flows or slices across the network as well as vital aspects of service origination such as computing platforms, resources and sessions. The scope is limited to identifying sets or suites of metrics or Key Performance Indicators (KPIs) that impact service delivery. Sets of metrics can each apply to a class of services or application flows, and there is also a common set of service metrics.

Project Deliverables under Development

See BBF Work in Progress - Projects, Project Streams, and Jira Links

Filter the table at the link above on Work Area = "ATA" and Project Stream = "Performance, Experience, and Application Testing (PEAT)"

Completed Project Deliverables

Project Overview

The project covers the support of following Ethernet services:

1. Ethernet services in Multi-service Broadband Network Architecture (TR-145)
2. Carrier Ethernet Services (MEF CE 2.0)

• Support MEF carrier Ethernet services
  • E-Line, E-LAN, E-Tree and E-Access
  • Support of service attributes for all services and service profiles (e.g., mobile transport front/backhaul for 5G)
  • Control, OAM, QoS, reliability and scalability
  • Multi-homing and load balancing
  • Support Carrier Ethernet services across multiple network domains

It is intended to apply the same understanding as has been used for WT-224 and WT-178 and to profile IETF and MEF standards.

This project specifically addresses the support of Ethernet services using BGP MPLS Based Ethernet VPNs (EVPN).

For more information, please see the New Project Information Form (NPIF) for the EVPN project.

Project Deliverables under Development

See BBF Work in Progress - Projects, Project Streams, and Jira Links

Filter the table at the link above on Work Area = "ATA" and Project Stream = "Cloud Interconnect (CI)"

Completed Project Deliverables

Project Overview

Provide architecture and nodal requirements to support broadband multi-service networks and MEF carrier Ethernet services. Use VPWS and VPLS in IP/MPLS networks and provides how service parameters are supported in MPLS network.  

The project covers the support of following Ethernet services:

1. Ethernet services in Multi-service Broadband Network Architecture (TR-145)
2. Carrier Ethernet Services (MEF CE 2.0)

• Support MEF carrier Ethernet services
  • E-Line, E-LAN, E-Tree* and E-Access (*Note that E-Tree cannot be fully supported as defined using VPLS or VPWS)
  • Support of service attributes for all services and service profiles (e.g., mobile transport front/backhaul for 5G)
  • Control, OAM, QoS, reliability and scalability
  • Multi-homing and load balancing
  • Support Carrier Ethernet services across multiple network domains

It is intended to apply the same understanding as has been used for WT-224 and WT-178 and to profile IETF and MEF standards.

This project specifically addresses the support of MPLS in Carrier Ethernet Networks.

Project Deliverables under Development

See BBF Work in Progress - Projects, Project Streams, and Jira Links

Filter the table at the link above on Work Area = "ATA" and Project Stream = "Cloud Interconnect (CI)"

Completed Project Deliverables

Project Overview

Integration of optical transceivers and IP routing equipment.  (e.g., IP over DWDM)

Project Deliverables under Development

See BBF Work in Progress - Projects, Project Streams, and Jira Links

Filter the table at the link above on Work Area = "ATA" and Project Stream = "Packet Optical Evolution (POE)"

Completed Project Deliverables