namic time assignment (DTA) for G.fast operating on coax, where the upstream and downstream bit rates are dynamically allocated based on customer traffic demand. This enables service providers to offer symmetric upstream and downstream service that is nearly equal to the aggregate bit rate to allow for higher speed services. AT&T also led the effort to stan- dardize the management of G.fast network terminating equipment (NTE) that is a standalone unit Network Access ONAP and AIC OSS/BSS Orchestration SDN Controller Network PMA Aggregation Logic VNF(s) NETCONF/YANG Management Service Path CO Routing Layer BNG / vBNG Access Aggregation OLT / vOLT NETCONF/YANG EOC (G.9701, G.997.2) FIGURE 11.6 Management architecture of G.fast. and not integrated with the customer premise equipment (CPE) or residential gateway. The NTE uses a Network Configuration Protocol (NETCONF) and Yet Another Next Generation (YANG) management model in combination with the embedded operations channel (EOC), which is the management communication channel between the G.fast DPU and NTE. This is critical for tran- sitioning the management of G.fast devices (DPU and NTE) to an SDN-controlled management solution using NETCONF/YANG. Figure 11.6 shows a high-level view of G.fast device management in the new access architecture. This is based on the BBF's TR301 management architecture, which introduced the persistent man- agement agent (PMA) that provides persistence and modification of the DPU configuration when a DPU is not powered. A PMA Aggregator (PMAA) provides aggregation of PMAs, and the PMAA exists as a virtualized management layer in the AIC. ONAP and AIC orchestration control the instantiation and resiliency of PMAAs. The OSS/BSS orchestration layer uses an SDN controller as an adapter to manage multiple PMAs, DPUs and NTEs through the PMAAs. The network solution includes passing in-band management traffic through the intermediate network layers (Broadband Network Gateways [BNGs] in Central Office routing, and OLTs/virtual OLTs [vOLTs] for ac