ATA Work Area Project Streams and Projects
Project Deliverable and Document Numbering Note
Most projects use deliverable (e.g., tutorial slide deck) and document numbers assigned independent of inter-relation or project association. (e.g., TR-421, MR-433, MR-238, TR-224, TR-350, MR-367)
However, some deliverables or documents are numbered in a series associating them together as related or part of the same project using a suffix notation (e.g., TR-452.1, TR-452.2, TR-452.3, etc;. MR-452.1, MR-452.2, MR-452.3, etc.; TR-319 Base, TR-319 Part A, TR-319 Part B, etc.) The suffix, when used, is treated as an integral part of the document number for purposes of revision (e.g., TR.459.2 Issue 2), amendment (e.g. WT-390.2 Amendment 1), or correction (e.g., MD-521.2 Corrigendum 1). Note that the first deliverable in a series may or may not use the .1 suffix. (e.g., TR-459, TR-459.2, TR-459.3 vs. TR-452.1, TR-452.2, TR-452.3, etc., MR-521.1, MR-521.2, etc.).
Questions on ATA document numbering should be directed to the Work Area Directors.
Mission Statement:
Business Impact:
TBA
Scope:
TBA
ATA Project Streams and Deliverables
Multiexcerpt |
---|
|
|
Project Stream | Description | PS Leaders |
---|
Non-PS Assigned | 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.
|
Multiexcerpt |
---|
MultiExcerptName | ATANonProjects |
---|
|
WT/MD/SD# (JIRA Link) | Non-PS Assigned Projects | Related Contributions | Editor(s) |
---|
SD-452 | Broadband Quality Experience Delivered (Broadband QED) | | MD-455 | Multi Access Broadband - Performance Networking On Demand | | Multiexcerpt |
---|
MultiExcerptName | A&MApplicationLayerTestingPS |
---|
|
Project Stream | Description | PS Leaders |
---|
Application Layer Testing | To define how test traffic is specified and generated at the application layer. It supports specification of test traffic that exhibits the complexity resulting from multiple types of applications and subscribers aggregated in a common network. | |
Multiexcerpt |
---|
MultiExcerptName | A&MApplicationLayerTestingProjects |
---|
|
WT/MD/SD# | Application-Layer Testing Projects | Abstract | Related Contributions | Editor(s) |
---|
| Application-Layer Test Traffic Architecture and Requirements | This Working Text defines an architecture and requirements for the specification of test traffic generated at the application layer. It supports specification of test traffic that exhibits the complexity resulting from multiple types of applications and subscribers aggregated in a common network and competing for resources, The WT also enables test traffic to be specified using consistent, unambiguous parameters that support repeatable test results under complex scenarios across different test labs, service providers, and vendors. | Click Here | Ken Ko, ADTRAN Daniel Moss, UNH IOL |
WT-422 | Application-Layer Testing Implementer's Guide | This Working Text provides guidance for the use of application-layer traffic in test scenarios. The relative advantages of generating test traffic at different layers for different purposes are addressed. The WT discusses the issues associated with creating load profiles, as well as the test and analysis methodologies most appropriate for use with application-layer traffic. | Click Here | WT-424 | Data Models for Application-Layer Test Traffic | This project defines the data models used to instantiate the application and subscriber profiles associated with application-layer testing. | Click Here | |
Multiexcerpt |
---|
MultiExcerptName | ATAAAPSOverview |
---|
|
Project Stream Page: Access Architecture (AA) Project Stream Project Stream Leads: Jonathan Newton, Vodafone 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.
|
Multiexcerpt |
---|
MultiExcerptName | ATAAAPSProjects |
---|
|
Projects Project Name and Page Link | Project Overview |
---|
459 - Multi-Service Disaggregated BNG with CUPS |
Multiexcerpt |
---|
MultiExcerptName | ATADBNGOverview |
---|
| 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. |
| Subscriber Session Steering |
Multiexcerpt |
---|
MultiExcerptName | ATASSSOverview |
---|
| 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: 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. |
| 497 - Public Wi-Fi User Authentication |
Multiexcerpt |
---|
MultiExcerptName | ATAWIFIAUTHOverview |
---|
| 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. |
Multiexcerpt |
---|
MultiExcerptName | ATAWIFIAUTHDeliverables |
---|
| 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 Title | Number | Description | Resources | Editors |
---|
|
|
|
|
|
|
|
|
Multiexcerpt |
---|
MultiExcerptName | ATAMPEATPSOverview |
---|
|
Project Stream Page: Performance, Experience, and Application Testing (PEAT) Project Stream Project Stream Leads: Fabio Giudici Mission: The project stream mission is to advance testing in traditional and new areas to ensure quality connectivity leading to quality user experience. The project stream will focus mainly in two areas: Enhanced packet layer performance testing e.g.,bandwidth/capacity, min/average/max latency measurements and jitter, loss, etc and Testing that goes beyond traditional packet layer performance to test and analyze the application and service layer quality
Both are needed to provide insight into quality of experience and application outcomes such that the network, while essential, becomes an invisible part of the customer experience. Business Impact: Provide the information needed to analyze a network’s detailed performance allowing service providers to offer not only higher capacity connectivity services, but also higher quality connectivity services. This in turn enables and accelerates industry adoption and deployment of new services and infrastructure. Scope: Specifically the project stream covers the following areas of connectivity quality testing: CE to IP Edge testing extends 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. IP Layer Capacity Metrics and Measurements harmonizes the Industry around a specific set of Capacity metrics and measurement method with clear benefits of multi-dimensional performance assessment at existing and new Gigabit-rate access speeds. Quality Experience Delivered is a method of systems performance analysis that decomposes a round trip time into constituent components enabling the networks performance to be analyzed and traced to sources causing performance degradation (packet loss/delay), be they structural (architecture/design), network dimensioning (link speeds etc.) or network load/scheduling related. - Broadband Service Metrics Project aims to identify sets or suites of metrics or Key Performance Indicators (KPIs) that impact service delivery.
|
Multiexcerpt |
---|
MultiExcerptName | ATAPEATPSProjects |
---|
|
Project Name and Page Link | Project Overview |
---|
Performance Measurement from CE to IP Edge Project |
Multiexcerpt |
---|
MultiExcerptName | ATAPEATPSPerfTstOverview |
---|
| 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. |
Multiexcerpt |
---|
MultiExcerptName | ATAPEATPSPerfTstDeliverables |
---|
| 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 Title | Number | Description | Resources | Editor(s) |
---|
Performance Measurement from Customer Equipment to IP Edge | TR-390 | This specification extends 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. |
| | Performance Measurement from Customer Equipment to IP Edge | TR-390i2 | This specification extends 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. - Using STAMP |
| | Performance Measurement between Customer Equipment and IP Edge | TR-390.2a1 | Quality Attenuation Measurement in Broadband Access Network using STAMP |
| Gregory Mirsky, Ericson |
|
| Broadband Quality Experience Delivered (Broadband QED) Project |
Multiexcerpt |
---|
MultiExcerptName | ATAPEATPSQEDOverview |
---|
| 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. |
Multiexcerpt |
---|
MultiExcerptName | ATAPEATPSQEDDeliverables |
---|
| 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 Title | Number | Description | Resources | Editor(s) |
---|
Broadband Quality Experience Delivered (Broadband QED) |
| Documentation of broad-ranging study | Jira |
---|
server | BBF Jira |
---|
serverId | d92875e6-bce1-3b6b-a909-e9268944d601 |
---|
key | CONTRIB-21189 |
---|
|
| | Motivation for Quality Broadband (QED & Quality Attenuation) | MR-452.1 | First MD in the series for MD452, describing the motivation for QED | Jira |
---|
server | BBF Jira |
---|
serverId | d92875e6-bce1-3b6b-a909-e9268944d601 |
---|
key | CONTRIB-21664 |
---|
|
| | Text for MR on QED Uses in Lab Evaluation & Network Design | MR-452.4 | draft Marketing Document on use of Quality Attenuation in NW design & lab evaluation phases | Jira |
---|
server | BBF Jira |
---|
serverId | d92875e6-bce1-3b6b-a909-e9268944d601 |
---|
key | CONTRIB-22449 |
---|
|
| | proposed text for MD on QED for creation of application SLA | MR-452.2 | Proposes a draft for an MR in the MR-452.x series to cover the use of DeltaQ in managing customer SLA. | Jira |
---|
server | BBF Jira |
---|
serverId | d92875e6-bce1-3b6b-a909-e9268944d601 |
---|
key | CONTRIB-22309 |
---|
|
Jira |
---|
server | BBF Jira |
---|
serverId | d92875e6-bce1-3b6b-a909-e9268944d601 |
---|
key | CONTRIB-22673 |
---|
|
Jira |
---|
server | BBF Jira |
---|
serverId | d92875e6-bce1-3b6b-a909-e9268944d601 |
---|
key | CONTRIB-22674 |
---|
|
| | Quality Attenuation Architecture and Requirements | TR-452.1 | First TR for the revised NPIF - in Final Ballot | Jira |
---|
server | BBF Jira |
---|
serverId | d92875e6-bce1-3b6b-a909-e9268944d601 |
---|
key | CONTRIB-22003 |
---|
|
Jira |
---|
server | BBF Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | d92875e6-bce1-3b6b-a909-e9268944d601 |
---|
key | CONTRIB-22012 |
---|
|
Jira |
---|
server | BBF Jira |
---|
serverId | d92875e6-bce1-3b6b-a909-e9268944d601 |
---|
key | CONTRIB-22119 |
---|
|
Outstanding issues | | Quality Attenuation Measurements using Active Test Protocols | TR-452.2 | Second WT for the revised NPIF | Jira |
---|
server | BBF Jira |
---|
serverId | d92875e6-bce1-3b6b-a909-e9268944d601 |
---|
key | CONTRIB-22056 |
---|
|
Jira |
---|
server | BBF Jira |
---|
serverId | d92875e6-bce1-3b6b-a909-e9268944d601 |
---|
key | CONTRIB-22800 |
---|
|
Jira |
---|
server | BBF Jira |
---|
serverId | d92875e6-bce1-3b6b-a909-e9268944d601 |
---|
key | CONTRIB-22825 |
---|
|
| | Quality Attenuation Measurements Using L2 PM OAM | TR-452.5 | This Technical Report addresses the implementation of Quality Attenuation (∆Q) measurement using Data Link Layer (L2) Active Test Protocols. |
| Fabrizio Guidotti OutSys Fabio Giudici , OutSys |
|
| IP-Layer Capacity Metric, Related Metrics, and Measurement Methods Project |
Multiexcerpt |
---|
MultiExcerptName | ATAPEATPSIPCapOverview |
---|
| 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. |
Multiexcerpt |
---|
MultiExcerptName | ATAPEATPSIPCapDeliverables |
---|
| 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 Title | Number | Description | Resources | Editor(s) |
---|
Maximum IP-Layer Capacity Metric, Related Metrics, and Measurements | TR-471 TR-471i2 TR-471i3 |
| | | Maximum IP-Layer Capacity Metric and Measurement | MR-471.1 MR-471.2 |
| Click Here | |
|
| Broadband Service Metrics Project |
Multiexcerpt |
---|
MultiExcerptName | ATAPEATPSBBSvcMetricsOverview |
---|
| 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. |
Multiexcerpt |
---|
MultiExcerptName | ATAPEATPSBBSvcMetricsDeliverables |
---|
| 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 Title | Number | Description | Resources | Editor(s) |
---|
|
|
|
|
|
|
|
|