Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
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 Work Area wiki pages.
Table of Contents | ||
---|---|---|
|
ATA Work Area Project Streams and Projects
ATA New Project Initiation Forms (NPIFs)
Multiexcerpt | ||
---|---|---|
| ||
Project Page: ATA New Project Initiation Forms (NPIFs) Work Area Director: David Sinicrope, Ericsson Description: Proposed new projects for ATA or combination of Work Areas including ATA. |
ATA Non-PS Assigned Projects
Multiexcerpt | ||
---|---|---|
| ||
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 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.
ATA New Project Initiation Forms (NPIFs)
Multiexcerpt | ||
---|---|---|
| ||
Project Page: ATA New Project Initiation Forms (NPIFs) Work Area Director:Jonathan Newton , Vodafone. Description: Proposed new projects for ATA or combination of Work Areas including ATA. |
ATA Non-PS Assigned Projects
Multiexcerpt | ||
---|---|---|
| ||
Project Stream Page: ATA Non-PS Assigned Projects Work Area Director: Jonathan Newton , Vodafone. 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
Multiexcerpt | ||
---|---|---|
| ||
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:
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:
|
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Projects
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Projects Project Name and Page Link Project Overview
Multiexcerpt |
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 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.
Multiexcerpt |
--- | --- | --- | --- Multiexcerpt |
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.
Title
Subscriber Session Steering WT-474 WT-487 DBNG 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
-----------Phase 2: Architectural Aspects for DBNG in fixed access & Requirements for nodes and interfaces/protocols between CP and UP
-----------Phase 3: Protocol specific aspects
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 Multiexcerpt |
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
Multiexcerpt | ||
---|---|---|
| ||
Project Stream Page: Mobile Transport and Routing (MT&R) Project Stream 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. |
|
Performance, Experience, and Application Testing (PEAT) Project Stream
Multiexcerpt | ||
---|---|---|
| ||
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:
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:
|
Multiexcerpt | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Multiexcerpt | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Project Name and Page Link Project Overview
Multiexcerpt |
Project Deliverables Title | Number | Description | Resources | Editor(s) | 5G Transport Architecture and Requirements | WT-521 |
Ron Insler , RAD 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 |
TR-221 Amd 2 | MMBI LTE Tutorial | MR-234 | MMBI White Paper on Use of MPLS in LTE | MR-238 | Mobile – Transport Network Slice instance Management Interfaces (MTNSi)
Multiexcerpt |
Project Deliverables Title Number | Description | Resources Editor(s) MTNSI Architecture and Requirements | WT-522 | MTNSI Architecture and Requirements | Jira | server | BBF Jira | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
tbd | |
Performance, Experience, and Application Testing (PEAT) Project Stream
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Project Name and Page Link Project Overview
Multiexcerpt |
Project Deliverables Title Number | Description | Resources Editor(s) Application-Layer Test Traffic Architecture and Requirements WT-421 | Ken Ko, ADTRAN Daniel Moss, UNH IOL Application-Layer Testing Implementer's Guide WT-422 | Data Models for Application-Layer Test Traffic | WT-424 | Click Here | Martin Casey, Calix Jason Walls, QA Cafe Application Layer Testing: The Key to Optimizing Quality of Experience | MR-433 | Ken Ko, ADTRAN
Multiexcerpt |
Project Deliverables Title Number | Description | Resources Editor(s) Performance Measurement from Customer Equipment to IP Edge WT-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. | Guiu Fabregas , Nokia Performance Measurement from Customer Equipment to IP Edge | WT-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 | Gregory Mirsky , ZTE Broadband Quality Experience Delivered (Broadband QED) Project |
Multiexcerpt |
Project Deliverables Title Number | Description | Resources Editor(s) Broadband Quality Experience Delivered (Broadband QED) SD-452 | Broad-ranging study document |
Peter Thompson , PNSol Bruno Cornaglia, Vodafone Motivation for Quality Broadband (QED & Quality Attenuation) | MD-452.1 | First MD in the series for MD452, describing the motivation for QED |
Jonathan Newton , Vodafone Quality Attenuation Architecture and Requirements | TR-452.1 | First TR for the revised NPIF - in Final Ballot |
Peter Thompson , PNSol Rudy Hernandez , Spirent Quality Attenuation Measurements using TWAMP | WT-452.2 | Second WT for the revised NPIF |
Peter Thompson , PNSol Quality Attenuation Conformance Testing | WT-452.3 | Third WT for the revised NPIF |
Peter Thompson , PNSol proposed text for MD on QED for creation of application SLA | MD-452.2 | Proposes a draft for an MR in the MR-452.x series to cover the use of DeltaQ in managing customer SLA.
key | CONTRIB-22309 |
Jonathan Newton , Vodafone Presentation on QED | MD-452.3 | Slides for a presentation or webinar on QED |
Peter Thompson PNSol Text for MR on QED Uses in Lab Evaluation & Network Design | MD-452.4 | draft Marketing Document on use of Quality Attenuation in NW design & lab evaluation phases |
Gavin Young , Vodafone Peter Thompson , PNSol IP-Layer Capacity Metric, Related Metrics, and Measurement Methods Project |
|
Cloud Interconnect (CI) Project Stream
Multiexcerpt include | ||||||
---|---|---|---|---|---|---|
|
Packet Optical Evolution (POE) Project Stream
|
Work Area Overview
Mission Statement:
Multiexcerpt | ||
---|---|---|
| ||
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 ATA produces industry-agreed specifications for applications such as mobile transport infrastructure (fronthaul and backhaul), data center interconnect, broadband Internet access , etc. as 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 DirectorsDirector:
|
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 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 the ATA Calendar and Deadlines for details on conference calls and meetings.
See Also:
Children Display |
---|
...