PITP (Port Identification Transparent Transmission) is used on access networks to carry a user’s physical access-location to the upper AAA/BRAS. It has two working forms: P-mode (PPPoE+)—injecting location identifiers into PPPoE discovery—and V-mode (Vendor-tag)—carrying vendor/location tags transparently upstream. The purpose is to let the upper server associate user credentials with access location and, by policy, restrict roaming. Options A, B, D, and E correctly describe these behaviors/terms. Option C is inaccurate as written: PITP itself does not “bind the authentication” or inherently “avoid theft/roaming”; it only delivers location info. Preventing credential theft/roaming is achieved by AAA/BRAS policy that uses the PITP-carried location, not by PITP alone.

In GPON Type C dual-attribution protection, the ONU has dual PON connections to two OLT PON ports (or two OLTs). When the protection group is configured to track the OLT’s uplink Ethernet port, a Down state on that uplink is an OLT-side trigger. The OLT initiates the protection action (forces the working/standby role swap via PON protection signaling).

A — Correct behavior: After the OLT triggers protection, the ONU’s working PON interface becomes standby, and the protect interface becomes working.

B — Correct behavior: The OLT monitors and updates the ONU uplink status as part of the protection group state machine.

C — Correct behavior: After inversion, services egress the ONU via the protect PON port toward the OLT, i.e., traffic follows the configured protect path.

D — Incorrect (answer): In this scenario the trigger is the OLT’s uplink Ethernet status, not an ONU-detected failure. Therefore the ONU does not detect the fault nor initiate the switchover; the OLT does.

(Reference: HCIP-Access V2.5 – GPON protection mechanisms; Huawei OLT protection group behavior, Type C dual-homing with uplink-tracking.)

IGMP Snooping is a Layer-2 function that listens to IGMP control packets between hosts and the multicast querier. Upon receiving a host’s Membership Report (Join) for group G, the switch learns that the ingress port is a member port for G and adds that port to the group’s forwarding entry, so multicast traffic for G is forwarded only to those learned member ports (saving bandwidth and avoiding flooding). Huawei’s official documentation describes IGMP Snooping exactly in this way.

Huawei access security recommends limiting MAC learn counts per port/VLAN, and using anti-MAC-spoofing bindings: either automatic (dynamic) bindings generated by the system or manual static MAC bindings to the service/port. Simply replacing a terminal is not a network-side mitigation method and is not listed as a protection measure.

XGS-PON downstream line rate is ~10 Gbit/s. When 12 terminals share a PON tree concurrently, the rough per-terminal share is 10,000 Mbit/s ÷ 12 ≈ 833 Mbit/s, commonly expressed as “about 800 Mbit/s.” This aligns with planning examples in HCIP-Access where downstream concurrency on XGS-PON is calculated by dividing the port rate by the number of active ONUs/APs on the splitter.

Type B protection (OLT-side + feeder protection via 2×2 optical splitter) is designed for automatic protection switching (APS) upon detecting faults such as LOS/LOF on the working port or feeder. The system automatically switches to the standby PON port/feeder without manual intervention (manual cutover is optional but not required for protection).

(Reference: HCIP-Access V2.5 – GPON Type A/B/C protection definitions, trigger conditions, and APS behavior.)

In an H.248 (Megaco) control model, the MGC is the controller that issues provisioning/connection-control commands such as Add, Modify, Subtract, AuditValue, AuditCapabilities to the MG. The MG (Media Gateway) can initiate only specific messages toward the MGC to announce state changes or report detected events—namely ServiceChange (to indicate restart, failure, availability changes, etc.) and Notify (to report observed events collected per event descriptor). Therefore, among the listed options, the commands that the MG itself can send are ServiceChange and Notify.

Huawei VLAN planning considers overall VLAN scale, user categories and volume, service types (HSI/IPTV/VoIP) and their isolation, uplink/aggregation mode (e.g., QinQ, VXLAN interwork), and device/topology constraints (e.g., OLT slot/board distribution). All listed factors affect VLAN count, tagging scheme, and scalability.

For OLT uplink (NNI) protection groups (timedelay/weight, etc.), Huawei requires that each physical port belongs to one protection group only to avoid conflicting switchover control. A member port cannot be part of multiple protection groups simultaneously.

IPTV over FTTH relies on multicast control; therefore the essential U2000 template is the IGMP template, which defines IGMP behaviors, program authorization binding, and multicast parameters used by the OLT/ONT. MGC applies to voice (VoIP), and SNMP pertains to NMS communication rather than IPTV service logic; value-added templates are not mandatory for basic IPTV.