- Created by April Nowicki, last modified by David Sinicrope (GM) on Jun 22, 2021
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 41 Next »
Note: For work and wiki pages predating the January 2019 formation of the Access and Transport Architecture Work Area, see the retired Architecture and Migration Work Area and the Routing and Transport Work Area wiki pages.
ATA Project Streams and Projects
ATA New Project Initiation Forms (NPIFs)
ATA Non-PS Assigned Projects
Project Stream Page: ATA Non-PS Assigned Projects Work Area Director: David Sinicrope, Ericsson Description: Projects that don’t fit under the scope of an existing Project Stream or if they fit under the scope of more than one Project Stream, are developed under the Non-PS Assigned category.
Access Architecture (AA) Project Stream
DRAFT - under construction 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. The page Multi-Service Disaggregated BNG with CUPS was not found -- Please check/update the page name used in the MultiExcerpt-Include macro 2nd tabel Control and User Plane Separation for a Disaggregated BNG TR-459 defines the architecture, the requirements, and the protocol for a control and user plane separation of a disaggregated BNG. Multi-Service Disaggregated BNG with CUPS. Reference Architecture, Deployment Models, interface, and Protocol Specifications Reference Architecture, Deployment Models, interface, and Protocol Specifications". This is to further differentiate from WT-487. This Working Text further clarify call flows, requirements, and PFCP IEs updates for TR-459. IRA Issues Baseline Working Text (WT) draft CONTRIB-22737. This Working Text defines the architecture and requirements to support CG-NAT for a MS-DBNG defined in TR-459. IRA Issues Baseline Working Text (WT) draft CONTRIB-21341. ContributionsProject Name and Page Link Project Overview Title Number Description Resources Editors TR-459 WT-459 issue 2 This is an issue 2 of TR-459, renamed to "Multi-Service Disaggregated BNG with CUPS. Kenneth Wan CGN Functionality for Disaggregated BNG Project WT-459.2 IPTV Multicast for the Disaggregated BNG WT-459.3 This Working Text defines the architecture and requirements to support IP Multicast for a disaggregated BNG defined in TR-459. CONTRIB-22628 Nagaraj S Turaiyur
Mobile Transport and Routing (MT&R) Project Stream
The page Mobile Transport and Routing (MT&R) Project Stream was not found -- Please check/update the page name used in the MultiExcerpt-Include macro
Performance, Experience, and Application Testing (PEAT) Project Stream
MultiExcerpt named ATAPEATPSOverview was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro
Cloud Interconnect (CI) Project Stream
The page Cloud Interconnect (CI) Project Stream was not found -- Please check/update the page name used in the MultiExcerpt-Include macro
Packet Optical Evolution (POE) Project Stream
The page Packet Optical Evolution (POE) Project Stream was not found -- Please check/update the page name used in the MultiExcerpt-Include macro
Work Area Overview
Mission Statement:
The Access and Transport Architecture (ATA) Work Area (WA) defines and specifies the architecture and equipment requirements for access, routing and transport network infrastructure. ATA produces industry-agreed specifications for applications such as mobile transport infrastructure (fronthaul and backhaul), data center interconnect, broadband Internet access, etc. as well as specifications for managing, testing, and maintaining these networks and their applications. This work typically takes the form of architecture, equipment requirements, test & implementation guidance, and education materials. Work Area Directors:
Business Impact:
A critical element of the work is the long term support of existing network elements alongside virtualized software based network functions, resulting in a stable network that may be evolved over time. This enables seamless migration of new networking technologies based on their market acceptance, at the same time protecting existing infrastructure investment, and deployment into new different territories. ATA specifications underpin the network infrastructure, value-added services and application delivery for fixed and mobile access networks, and allow deployment at the pace of each relevant market. Co-existence of physical and virtualized solutions for static and dynamic services create a network infrastructure mitigating the risks to existing revenue at the same time it leverages new networking technology according to market demand.
Scope:
ATA maintains the primary architectures for the work of Broadband Forum. The architectures, requirements and other deliverables reflect the control, management, and data plane aspects of the access, transport and routed networks used to provide operator, enterprise and “over-the-top” Internet based connectivity services. The deliverables of the work area are designed to leverage and integrate new industry technologies while protecting investment of current deployments. These deliverables provide the industry with a collective and consistent methodology to drive product development and service deployment.
Email List:
ATA Work Area (WA): ata@broadband-forum.org
- used for ATA meeting notification, agendas, discussion, etc.
Join or Leave BBF Groups and Email Lists
- Go to your JIRA profile page to see all of your current BBF group memberships.
ATA Calls, Minutes, Agendas
Each Project has its own agenda and set of minutes.
See Also:
- No labels