- Created by April Nowicki, last modified by David Sinicrope (GM) on Jun 23, 2021
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 55 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 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
Project Stream Overview Project Stream Leads: David Sinicrope (GM), Ericsson Mission: The project stream mission is to advance access broadband network architecture in traditional and new areas to ensure quality connectivity leading to quality user experience. Identify and document the key functionalities and relationships between entities to facilitate the transition of networks to encompass new practices such as virtualization while documenting the key functionalities that need to be brought forward to enable a seamless evolution path.A critical element of the work is the long term support of existing and new physical and statically management network elements alongside agile and virtualized functions in what effectively will be a stable hybrid network. This enables seamless migration based on market acceptance on new technologies, protection of existing infrastructure investment and normal spread of deployment in different territories.The project stream will focus on: New, distributed access network architectures, including some or all of which is virtualized. Defining the access (e.g., AN, BNG) function, interfaces and interactions of the equipment within these new architectures Defining the equipment requirements needed to support the new architectures Migration from existing access networks to those deployed leveraging the new architectures, functions and equipment Maintenance of existing access architecture, functions and equipment requirements Business Impact: The work creates the necessary foundation for all of the broadband network. It underpins new value-added services and application delivery for fixed access networks, for home and business that can now be deployed at the pace of each market. Co-existence of physical and virtualized solutions and from static and dynamic services will create a broadband network mitigating the risks to existing revenue and enabling market-paced migration. Drive evolution of the network to improve scale, resiliency, reliability and security. Scope: Specifically the project stream covers the following areas: Overall broadband access network architecture from RG through BNG. Conventional Broadband Network Gateway (BNG) - definition, architecture, function definition and requirements. Disaggregated Broadband Network Gateway - definition, architecture, function definition and requirements. Conventional Access Node (AN)- definition, architecture, function definition and requirements. Projects Project Name and Page Link Project Overview Project 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 Title Number Description Resources Editors Control and User Plane Separation for a Disaggregated BNG TR-459 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 WT-459 issue 2 This is an issue 2 of TR-459, renamed to "Multi-Service Disaggregated BNG with CUPS.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 IssuesBaseline Working Text (WT) draft CONTRIB-22737. WT-459.2 This Working Text defines the architecture and requirements to support CG-NAT for a MS-DBNG defined in TR-459. IRA IssuesBaseline Working Text (WT) draft CONTRIB-21341.Contributions 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. 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 Title Number Description Resources Editors 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 Title Number Description Resources Editors Subscriber Session Steering WT-474 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 Title Number Description Resources Editors DBNG for Wired Access WT-487 This 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.This project will include use case, reference architecture, requirements, interfaces, and protocol specifications for Wired Access DBNG. Baseline Working Text (WT) draftCONTRIB-22693
Mobile Transport and Routing (MT&R) Project Stream
Project Stream Overview Project Stream Leads: David Sinicrope (GM) , Ericsson Mission: To produce industry agreed specifications of the routing and transport network infrastructure and solutions for the transport of traffic in mobile networks, including 2G, 3G, LTE and 5G mobile networks. This work typically being in the form of architecture, equipment requirements, interoperability and conformance test plans, implementation guidance and education materials. Business Impact: This work accelerates industry adoption of new routing and transport technology and deployment of new services and infrastructure in mobile networks. The work includes the introduction of and migration to SDN and virtualization of the mobile transport network infrastructure where commercially viable. Scope: Control, management and data plane for the IP layer down to the physical layers, including time and synchronization, OAM, routing, resiliency, scalability, security, virtualization of the mobile transport infrastructure, and enablement of software driven networking. Projects Project Name and Page Link Project Overview Project Overview Project Deliverables Mobile – Transport Network Slice instance Management Interfaces (MTNSi) Project Overview This project will deliver stuff. Project Deliverables Title Resources Editor(s)
CONTRIB-21582
-
Getting issue details...
STATUS
Title Number Description Resources Editor(s) 5G Transport Architecture and Requirements WT-521
CONTRIB-20551
-
Getting issue details...
STATUS
5G Transport Tutorial MD-521.2 David Sinicrope , Ericsson 5G Transport Whitepaper MR-521.1 Joel Halpern , Ericsson MPLS in Mobile Backahul TR-221 MPLS in Mobile Backhaul Amendment 1 - adds support for enhanced services and small cells TR-221 Amd 1 2nd amendment to TR-221 MPLS in Mobile Backhaul Networks - adds architecture and requirements for
and other changes.TR-221 Amd 2 MMBI LTE Tutorial MR-234 MMBI White Paper on Use of MPLS in LTE MR-238 Number Description MTNSI Architecture and Requirements WT-522 MTNSI Architecture and Requirements tbd
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