Broadband Forum Fixed Access Network Sharing Architecture (FANS, TR-370)

Broadband Forum Fixed Access Network Sharing Architecture (FANS, TR-370)

1. What Is Broadband Forum Fixed Access Network Sharing Architecture (FANS, TR-370)?

The Broadband Forum Fixed Access Network Sharing architecture is a technical framework for allowing multiple operators to use one fixed broadband access network while retaining defined control over their services. FANS means Fixed Access Network Sharing; TR-370 is the Technical Report titled Fixed Access Network Sharing – Architecture and Nodal Requirements. It addresses network architecture and equipment requirements, rather than providing a conventional management matrix.

For telecommunications operators, the central question is practical: how can a shared network support differentiated retail services without surrendering infrastructure control or exposing another operator’s customers? Consultants should use FANS to translate a wholesale proposition into technical requirements, responsibilities, and implementation choices.

2. Origin and Background

Origin: Broadband Forum. TR-370’s first issue carries a November 2017 cover date. Its issue history records approval on November 27, 2017, and publication on January 12, 2018. Issue 2 was approved and published on April 10, 2020. Bruno Cornaglia is identified as issue editor; that does not establish him as the sole inventor of the architecture.

The underlying problem was that sharing connectivity did not necessarily give retail operators sufficient diagnostic visibility or service control. FANS extended virtual unbundling toward sharing management information and selected control functions, enabling greater service differentiation over shared infrastructure. Its original purpose remains technical; executives can use it to structure the operating model surrounding a wholesale access business.

3. How Broadband Forum Fixed Access Network Sharing Architecture (FANS, TR-370) Works

The acronym describes the architecture’s scope:

  • F — Fixed: Wireline broadband infrastructure.
  • A — Access: Subscriber connectivity.
  • N — Network: Access and aggregation resources.
  • S — Sharing: Controlled, logically isolated use by multiple operators.

TR-370 covers passive optical networks (PON), digital subscriber line (DSL), and G.fast access. Its scope includes Layer 2 interconnection, management interfaces, operational functions, security, and privacy—not simply sharing fiber strands.

Responsibilities and control boundaries

The Infrastructure Provider (InP) manages the physical infrastructure. A Virtual Network Operator (VNO) uses allocated resources to deliver subscriber services. A centralized management system coordinates shared resources and mediates operations. Virtual access nodes provide operator-specific representations or functions; port mapping connects virtual subscriber resources to physical connections. These technical boundaries must become explicit operational responsibilities.

Three sharing models

ModelCore mechanismExecutive interpretation
Management-system-basedSharing is implemented at management-system level, rather than through equipment-level virtual partitions.Evaluate how much tenant autonomy a mediated management approach can provide.
Virtual-access-node-basedVirtual access-node functions expose allocated ports and forwarding resources to VNOs.Assess virtualization capability, resource governance, and operational complexity.
Software-defined-networking-basedIssue 2 adds an SDN model in which virtual management and control entities represent tenant resources, while packet forwarding remains in physical access and aggregation equipment.Consider separating operator-facing control from physical forwarding without assuming all network functions must become software.

Logical isolation is not the same as unlimited capacity. Traffic management must reconcile subscriber profiles, operator allocations, shared uplinks, and congestion. Quality of service (QoS) and service-level agreements (SLAs) therefore require measurable capacity and enforcement rules, not merely distinct tenant identifiers.

4. When to Use Broadband Forum Fixed Access Network Sharing Architecture (FANS, TR-370)

Use FANS when evaluating a wholesale fiber platform, onboarding additional retail providers, modernizing virtual unbundling, or determining which service controls to delegate. It is particularly useful when the commercial proposition depends on partners doing more than reselling predefined broadband packages.

Start with equipment and software inventories, topology, busy-hour traffic, interface capabilities, subscriber-resource mappings, partner requirements, and fault-management processes. Involve network engineering, wholesale product management, operations, security, and systems integration. An executive workshop can establish alternatives; production readiness requires equipment validation and operational testing.

For networking equipment manufacturers, turn the architecture into a demonstrable capability checklist: tenant-scoped information, permitted configuration changes, resource enforcement, and recovery behavior. Require evidence on the proposed software release and hardware configuration.

FANS is not a standalone answer to build-versus-buy economics, passive infrastructure leasing, or regulatory compliance. It can mislead when teams assume desired autonomy is technically available, shared capacity is sufficient, or interfaces eliminate integration work.

5. How to Apply Broadband Forum Fixed Access Network Sharing Architecture (FANS, TR-370): Step-by-Step

  1. Clarify the decision and scope.

    Specify whether the decision concerns wholesale launch, partner onboarding, or network modernization. Define the planning horizon, access technologies, geographic clusters, operator handoff points, and subscriber services included.

  2. Gather evidence, not product claims.

    Collect hardware and firmware inventories, traffic measurements, configuration limits, interface documentation, alarm behavior, and existing contracts. Ask prospective VNOs which controls they actually require and why.

  3. Define the units of analysis.

    Assess each VNO’s resources within an access-node or aggregation cluster. Examine subscriber connections, logical ports, capacity allocations, handoff interfaces, and tenant permissions—not just the network as one undifferentiated asset.

  4. Construct the architecture artifact.

    Draw physical infrastructure, tenant representations, management systems, interfaces, and traffic paths. Add a responsibility table showing who requests, approves, executes, and observes each operation. Distinguish mandatory requirements from optional capabilities.

  5. Interpret the gaps.

    Compare each sharing model against required autonomy, installed equipment, security boundaries, and operating effort. Separate software-upgrade gaps from hardware limitations and unresolved process ownership. Treat unknown capabilities as validation tasks, not positive scores.

  6. Translate the design into actions.

    Create workstreams for equipment changes, interface integration, tenant onboarding, capacity enforcement, assurance, and migration. Attach owners, acceptance criteria, dependencies, costs, and rollback arrangements to each workstream.

  7. Test alternative assumptions.

    Stress-test partner growth, traffic concentration, controller failure, access-node outages, and operator switching. Reassess conclusions if more tenants require direct control or committed capacity than initially assumed.

  8. Align stakeholders and iterate.

    Review the design jointly with the InP, participating VNOs, vendors, and operations teams. Resolve disputes through explicit service boundaries and testable requirements. Pilot before expanding the deployment.

Use the resulting requirements to guide technology vendor selection. Evaluate demonstrated interoperability, tenant isolation, operational tooling, and lifecycle costs alongside equipment price.

6. Example: Broadband Forum Fixed Access Network Sharing Architecture (FANS, TR-370) in Action

Fictional example: CedarLink Fiber owns a regional access network and wants to serve three independent retail providers. Its existing wholesale offer requires CedarLink staff to execute most service changes, making the proposed partner experience difficult to deliver.

The team selects FANS to clarify delegated control. It examines each provider’s logical subscriber ports, capacity allocation, diagnostic access, and handoff within one pilot cluster. Inputs include measured traffic, equipment inventories, partner interviews, and firmware tests.

The analysis supports a management-system-based pilot, with more extensive SDN-based control deferred. Testing reveals two launch blockers: alarms are insufficiently filtered by tenant, and the required capacity-enforcement behavior needs a software upgrade. Fiber availability is not the immediate constraint.

CedarLink commissions the upgrade, introduces tenant-specific information views, defines permissible service changes, and agrees joint fault-escalation procedures. It makes operator switching, congestion, and recovery tests prerequisites for expansion.

The rollout then requires program management support to coordinate vendor delivery, system integration, partner onboarding, and operational acceptance against one readiness plan.

7. Strengths and Limitations

Strengths

  • Clarifies control boundaries: It provides a technical basis for distinguishing infrastructure stewardship from retail service control.
  • Supports differentiated wholesale access: Broadband Forum demonstrations show multiple VNOs provisioning services through their own virtual instances over shared physical resources.
  • Structures implementation discussions: Architecture views can connect commercial promises with equipment requirements, interface work, and operational acceptance.

Limitations

  • Logical separation does not remove physical constraints: Access and aggregation capacity still require traffic engineering. An apparently isolated service can encounter shared bottlenecks.
  • It is not a complete business case: Assess wholesale demand, partner revenue, integration costs, support effort, and upgrade investment separately.
  • Reference architecture is not deployment proof: Require testing of the specific equipment, controller, interfaces, and software versions proposed.
  • Operational dependencies remain: Plan for common infrastructure failures and coordinated maintenance; do not interpret tenant autonomy as infrastructure independence.

8. Common Pitfalls and How to Avoid Them

  • Starting with an undefined “slice”: Teams may mean a subscriber group, virtual node, or bandwidth allocation. Define its resources, permissions, service commitments, and lifecycle before comparing solutions.
  • Confusing traffic separation with complete isolation: Management information and configuration access also require tenant boundaries. Test what one VNO can read or change about another.
  • Promising autonomy without mediation rules: VNO requests remain subject to infrastructure-provider controls. Specify permitted changes, rejection conditions, and escalation paths before selling self-service capabilities.
  • Ignoring migration and release: Include service termination, resource reassignment, stale configuration removal, and information-access revocation in acceptance tests.
  • Stopping at the network diagram: Design the order, activation, assurance, and billing handoffs as well. Broadband Forum demonstrations explicitly include operational and business-support-system integration.

9. How Broadband Forum Fixed Access Network Sharing Architecture (FANS, TR-370) Relates to Other Frameworks

TR-386: Interface detail alongside architecture

TR-370 establishes architectural and nodal requirements; TR-386, Fixed Access Network Sharing – Access Network Sharing Interfaces, develops the system-interface detail. Use them together when moving from an operating concept to integration specifications. They are complementary reports, not competing management tools.

TM Forum Business Process Framework: Operational completeness

The Business Process Framework, also known as eTOM, classifies service-provider business processes and their relationships. Use it before or alongside FANS to define service-delivery and support requirements. Prefer it when the principal problem is process fragmentation rather than network-sharing architecture.

RACI: Accountability after technical boundaries

A RACI matrix identifies who is Responsible, Accountable, Consulted, and Informed. Apply it to provisioning, fault restoration, maintenance, and capacity changes after defining technical authority. RACI assigns organizational responsibility; it does not determine whether network equipment can enforce that authority.

10. Key Takeaways

  • Use FANS to structure shared-access control and technical requirements—not to substitute for commercial analysis.
  • Compare management-system, virtual-access-node, and SDN-based models against the actual deployment.
  • Define tenant resources, permissions, capacity commitments, and operational ownership explicitly.
  • Validate equipment capabilities and information isolation before promising partner autonomy.
  • Make migration, failure recovery, and end-to-end service processes part of launch readiness.

11. FAQs About Broadband Forum Fixed Access Network Sharing Architecture (FANS, TR-370)

What is the difference between FANS and ordinary bitstream wholesale?

FANS extends shared access toward management visibility and selected control functions, rather than concentrating only on delivered connectivity. The degree of autonomy depends on the implemented architecture and agreed wholesale offer.

Does FANS require replacing the entire access network?

No. TR-370 addresses both existing-network migration through software upgrades and requirements applicable to new nodes. Determine what the installed equipment supports before committing to either reuse or replacement.

Is TR-370 still relevant?

The Broadband Forum technical library lists Issue 2 as in force. Its published demonstrations also continue to use FANS for wholesale and open-access scenarios. Relevance does not imply universal adoption or suitability for every deployment.

What data is needed to begin?

Start with topology, equipment and software versions, subscriber-resource mappings, traffic measurements, interface capabilities, and partner control requirements. Add fault history and migration procedures before judging production readiness.

Can a smaller broadband operator use FANS?

Yes, but keep the initial scope narrow. Evaluate one cluster and a limited wholesale offer first. Prioritize clear responsibilities, enforceable resource limits, and proven integration over an ambitious virtualization program.

How to get started

1

arrow-down-blue

Tell us about your project

2

arrow-down-blue

Interview candidates

(We’ll provide bios within 48 hours on average)

3

Select your consultant and start work

Find a Consultant

or email us at: [email protected]