Huawei carrier architectures distinguish subscriber service-edge functions, network transport, and backbone routing. Broadband gateways commonly supply subscriber service management, SRs provide VPN and business connectivity, OLTs aggregate optical subscribers, and CRs provide backbone connectivity. The logical routing design is independent of the physical interconnection design: simply connecting MSEs and SRs to a municipal CR does not determine that all three must belong to one AS. BGP autonomous-system membership is an operator-specific logical design choice. Consequently the common-AS assertion in C is inconsistent with the intended traditional metro-network diagram, though a shared AS could be a legitimate design in another topology.
Technical Deep Dive:
C is the intended incorrect statement. An MSE ordinarily provides HSI, VoIP, IPTV and subscriber management. The SR is a service-routing aggregation node commonly serving enterprise VPN connectivity; the CR aggregates and transports metro traffic toward the backbone; the OLT aggregates PON subscribers and uplinks to an MSE or suitable routing equipment. 4G backhaul and fixed services can share physical transport when traffic isolation, bandwidth engineering, and QoS are properly designed. What makes C problematic is treating a same-AS relationship as an intrinsic consequence of the MSE/SR/CR topology. Devices connected by physical or logical links can exchange routes through EBGP across distinct autonomous systems, or they may use IBGP and an IGP within one AS. This question assumes a particular Huawei metro-AS deployment. Under that assumed deployment C is incorrect; outside it, the statement is not universally impossible. The architectural premise is essential to a rigorous interpretation.
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit