Project Streams
Multiexcerpt | ||||
---|---|---|---|---|
| ||||
|
George Dobrowski, Huawei Technologies
Multiexcerpt | ||
---|---|---|
| ||
|
|
Yves Hertoghs, VMWare
Ning Zong, Huawei Technologies
|
FTTx represents today a high-cost technology (in terms of Return on Investments) to enhance data rates to the end customers, but it requires a huge effort, in terms of CAPEX and OPEX for access network deployment. Due to this, some operators have recognized the need to partner in order to improve the return on investment of FTTx deployment.
Sharing the access network infrastructure is a viable way to expand the network and achieve an effective roll-out of new technologies.
FANS delivers one network sharing model with high flexibility for forward looking broadband network deployments and operations, facilitating the business innovation, enhancing the network efficiency and improving customer experience.
FANS also addresses the virtualization of that shared infrastructure such that each operator could have their own virtual access node.
Bruno Cornaglia, Vodafone
|
MultiExcerptName | SDN_PS_AIM |
---|
Wei Lin, Huawei Technologies
SDN and NFV Work Area Email List
sdn-nfv@broadband-forum.org: SDN and NFV meeting notification, agendas, discussion, etc.memgen@broadband-forum.org: All BBF Members, general information.
Join or Leave BBF Groups and Email Lists
Children Display |
---|
Completed specs (Public Web site)
Projects in Progress for this Work Area
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
WT/MD/SD#CloudCo ProjectsAbstractRelated ContributionsEditor(s) Anchor | wt408 | wt408 | WT-408CloudCO migration and co-existence | The purpose of this project is to suggest methods by which a existing/legacy broadband network may gradually migrate to one based on CloudCO and/or coexistence of the legacy and CloudCO architecture within segments of the same network. JIRA contributions | WT-411 | Definition of interfaces between
JIRA contributions |
Dharma Rajan, VMware
JIRA contributions |
Jira contributions | Huawei Technologies
WT-451 | vOMCI Interface Specification | The scope is to standardize the NBI and SBI of vOMCI function. The vOMCI function may support other administrative interfaces to modules (e.g., logging) to support non-OMCI related features, standardizing these interfaces are beyond the scope of this document. The vOMCI function is responsible for:
The OLT then would be responsible for:
Jira contributions | Tim CareyNokia Zhang Dechao ChinaMobile WT-454 | YANG Modules for Access Network Map & Equipment Inventory | In a CloudCO architecture, the management of physical nodes requires interfaces to expose Access Network Map (ANM) and Equipment Inventory information to the SDN Management and Control and other CloudCO functional blocks. For the support of multiple tenants, it’s also useful to expose to Tenants only relevant ANM and Equipment Inventory information over the NB API. The project is defining YANG data models for ANM and Equipment Inventory applicable to the BAA layer and the Access SDN Management and Control. Jira contributions | Application Notes | Application Notes (APPN) use the TR-384 framework to describe an implementable Use Case for a CloudCO 'application'. APPN includes
An Application Note Instance will then be created that details the exact components to be bootstrapped/installed onto an NFVI. ((i.e. it describes what VIM is chosen, etc, as well as e.g software releases etc). The APPN is then used to guide development of:
Jira contributions | Application Notes and how they relate to other work Coordinated by PSLs: Yves Hertoghs, VMWare | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
WT/MD/SD# | FANS Projects | Abstract | Related Contributions | Editor(s) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
WT-386 | FANS Access Network Sharing Interfaces | “FANS - Access Network Sharing Interfaces” investigates technical aspects related to the system interfaces associated with FANS. This document provides details and the necessary information required to effectively define these interfaces as well as the rules for communicating with them. | JIRA contributions | Peter Silverman, ASSIA | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
MD-453 | Fixed Access Network Sharing (FANS) Technical Overview | This paper discusses this evolution and the potential impact of Fixed Access Network Sharing (FANS) for those interested in business-related aspects. FANS enables broadband network infrastructure, and network management, to be shared amongst operators; thus sharing the costs of gigabit-class broadband deployment while enabling operators to run their own operations. Compared with deploying multiple parallel networks, FANS can lower capital costs. (previously listed as MD-426) | Jira Contributions | Ken Kerpez, ASSIA | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Multiexcerpt | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
WT/MD/SD#SDN AIM ProjectsAbstractRelated ContributionsEditor(s)WT-436 | Access & Home Network O&M Automation/Intelligence Over the past decade, growth in the Telco industry’s revenue has never outpaced growth in OPEX. As the scale of a network increases, OPEX increases with it. Therefore, it is expected that work needs to be done in order to reduce OPEX. This project will specify the logical framework of access & home network O&M automation, including necessary functional blocks, logical connection descriptions and information flows between the modules. In addition, this work will suggest possible applications of this framework to typical BBF service architectures. This identifies the information elements required in access & home network O&M automation, key use cases and KPIs, and analysis of the gaps with existing architectures to support these information elements. The project will describe what kinds of the information elements are required. YUE SUN , Ken Kerpez |