Black Friday VIP Hour Limited Time 75% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code = simple75
Pass the Huawei HCIP 5G H35-651 Questions and answers with Dumpstech
Exam H35-651 Premium Access
View all detail and faqs for the H35-651 exam
Which of the following are types of UNC VMs?
Select All that Apply
Options:
PBU-M
PBU-C
PBU-I
OMU
Exact Extract — Cloudification
“Full-stack cloudification and services: Full-stack cloudification (NFVI and VNF) enables quick resource orchestration, and full-stack services (AMF, SMF, UPF, PCF, UDM and IMS) enable quick function orchestration.”
— Huawei 5G Training Material, 5G Core Network Cloudification.
Technical Deep Dive
Huawei's virtualized core-network architecture separates management, service processing, and supporting functions across independently deployable virtual resources. This approach enables flexible capacity allocation, resource isolation, high availability, and operational management.
The proposed VM classification includes the following functional categories.
PBU-M: Associated with management and supporting platform functions. Certain Huawei UNC Common Service Database (CSDB) microservices are associated with this VM category.
PBU-C: Associated with the control and service-processing component category in the virtualized network element architecture.
PBU-I: Identified in the question as an interface-related PBU category, although its exact inclusion in the UNC release's VM inventory requires validation.
OMU: Operation and Maintenance Unit, providing the management framework used for configuration, fault monitoring, operational information, and maintenance activities.
These functional roles illustrate the separation between service execution and platform management. In a virtualized deployment, individual VMs can be allocated resources according to their processing requirements. For example, control-processing instances may need to scale independently of operational management components. Such architecture also supports redundancy and improved fault isolation.
Verification warning: The available Huawei PDF confirms the NFV architecture, but it does not contain the authoritative UNC VM inventory distinguishing all four options. PBU-M and OMU have supporting product documentation; the complete four-option key remains provisional and should not be treated as 100% verified.
In UNC 21.0, which of the following commands exports configurations from the OMU VM?
Options:
EXP MML
EXP OPTLOG
EXP STAT
EXP COMMAND
Exact Extract
“Full-stack cloudification and services: Full-stack cloudification (NFVI and VNF) enables quick resource orchestration, and full-stack services (AMF, SMF, UPF, PCF, UDM and IMS) enable quick function orchestration.”
— Huawei 5G Training Material, 5G Core Network Architecture, page 98.
Technical Deep Dive
The correct configuration export command is EXP MML . Huawei's Man-Machine Language (MML) provides an interface for configuring and maintaining telecommunications network elements. The Operation and Maintenance Unit (OMU) provides management capabilities used to maintain network element configuration and operational information.
The EXP MML command exports configuration data into an output file that can be downloaded through the supported O & M file transfer mechanism. A typical command is EXP MML; .
After execution, the management system generates the export output and provides information needed to retrieve the file. The exported configuration is useful for configuration backup, change audits, disaster recovery preparation, troubleshooting, and configuration comparison.
The alternatives have different intended functions. EXP OPTLOG relates to exporting operation logs rather than configuration data. EXP STAT suggests statistics export rather than configuration export. EXP COMMAND is not the documented configuration export operation.
Huawei's 5G Core Basic O & M training states that EXP MML exports configuration data from the UNC, UDG, UDM, and UPCF.
Engineers should protect exported configuration files because they may contain network topology details, IP addresses, subscriber-related configuration, and sensitive operational information. Therefore, A is correct.
The HTTP Routing Loop Prevention function allows the SCP to determine whether the Via header field in a received message contains the local FQDN. This assists in preventing HTTP routing loops.
Options:
TRUE
FALSE
Exact Extract — Service-Based Architecture
“All network functions on the control plane interact with each other through service-based interfaces. A service can be invoked by multiple network functions, reducing the coupling degree defined for interfaces between network functions.”
— Huawei Training Material, SBA Network Architecture, page 93.
Technical Deep Dive
The Service Communication Proxy (SCP) supports routing and forwarding of service-based communication between 5G network functions. In large 5G core deployments, a signalling request may pass through multiple SCP instances before reaching its destination NF.
Incorrect route configuration, service discovery results, or forwarding policies can cause requests to circulate repeatedly between proxy instances. HTTP provides the Via header field to identify intermediary systems through which a request has travelled.
For example:
Via: 2 scp-a.operator.example
Via: 2 scp-a.operator.example, 2 scp-b.operator.example
If an SCP receives a message whose Via information identifies that same SCP in the forwarding path, the message may have returned to a previously visited proxy. The SCP can use this information to detect potential HTTP signalling loops and prevent further forwarding.
The exact matching procedure depends on the SCP implementation, but the principle is to identify repeated forwarding through the same intermediary. This provides protection against unnecessary signalling traffic, repeated processing, network congestion, and signalling resource exhaustion.
In operational troubleshooting, engineers should examine the received Via field, destination URI, SCP forwarding policies, NF discovery results, and any routing-loop alarms. Therefore, the statement is TRUE.
Which of the following interfaces does the UPCF use to deliver AM policies?
Options:
N11
N7
N15
N5
Exact Extract
“Modularized network functions facilitate function decoupling and integration. Decoupled network functions are abstracted as network services, which can be independently expanded, evolved, and deployed on demand.”
— Huawei Training Material, SBA Network Architecture, page 93.
Technical Deep Dive
The N15 interface is the reference point between the PCF and AMF. It supports Access and Mobility (AM) Policy Control. The Huawei UPCF provides the PCF functionality required to communicate access and mobility policy decisions to the AMF.
Relevant policy information can influence service behaviour associated with access and mobility management, including applicable service-area restrictions and other authorized mobility-policy parameters.
The standardized service is Npcf_AMPolicyControl . During the AM policy association procedure, the AMF acts as the policy service consumer and the PCF provides policy decisions.
N11 connects the AMF and SMF for session-management-related interactions. N7 connects the PCF and SMF for session policy control. N5 connects the PCF and AF for application-related policy interactions. Only N15 is the specific reference point used for PCF-to-AMF access and mobility policy control.
Operational troubleshooting should verify the relevant PCF and AMF service registrations, SBI routing, AM policy association status, and HTTP response information. Therefore, C is correct.
Which external interfaces are offered by the UPCF?
Select All that Apply
Options:
N7
Rx
N9
Gx
Exact Extract — Service-Based Architecture
“All network functions on the control plane interact with each other through service-based interfaces. A service can be invoked by multiple network functions, reducing the coupling degree defined for interfaces between network functions.”
— Huawei 5G Training Material, SBA Network Architecture, page 93.
Technical Deep Dive
Huawei UPCF is a converged policy-control platform designed to support policy management across multiple mobile-network generations. The correct interfaces are N7, Rx, and Gx.
A. N7: N7 is the 5G service-based reference point between the Policy Control Function (PCF) and Session Management Function (SMF). It supports session policy control through the Npcf_SMPolicyControl service. The PCF provides policy decisions that the SMF uses to establish and modify QoS and charging-related session behaviour.
B. Rx: Rx is a Diameter-based interface used between an Application Function (AF) and the PCRF in EPC/IMS policy control architecture. In IMS deployments, Rx enables an application-side entity to request network resources associated with multimedia sessions. For example, IMS voice services can use application-related policy information to request suitable QoS treatment.
D. Gx: Gx connects the PCRF to the PCEF in the LTE/EPC architecture. It supports the exchange of PCC rules, session-level policy information, and charging-control instructions.
N9 is a user-plane interface between UPFs in a 5G core network. It carries user traffic between UPF instances, typically using GTP-U. It is not a policy-control interface offered by UPCF.
The distinction between N7, N9, and N5 is defined by the 5G core reference-point architecture, while Rx and Gx originate from the EPC policy-control architecture. Therefore, A, B, and D are correct.
Which of the following is not included in a UE-initiated PDU session establishment request?
Options:
DNN
Network slice information
SSC mode
QFI
Exact Extract
“Session management; UE IP address allocation; User-plane function selection and control; UPF service control; QoS and policy execution; Downlink data arrival notification.”
— Huawei Training Material, Main Network Functions of the 5GC, page 95.
Technical Deep Dive
During UE-initiated PDU session establishment, the UE sends information identifying the requested session and its service requirements. The request is transferred to the SMF through the AMF using the appropriate NAS transport and service-based signalling procedures.
A. DNN: The Data Network Name identifies the data network that the UE wishes to access. Examples include an operator Internet DNN or a dedicated enterprise DNN.
B. Network slice information: The S-NSSAI identifies the network slice associated with the requested PDU session. This information assists the network in selecting the appropriate SMF and applying the subscribed slice configuration.
C. SSC mode: Session and Service Continuity (SSC) mode identifies the requested continuity behaviour for the PDU session. The modes are SSC Mode 1, SSC Mode 2, and SSC Mode 3.
D. QFI: The QoS Flow Identifier identifies a QoS flow within a PDU session. The QFI is assigned or determined by the network's session and QoS control framework, rather than being a mandatory parameter supplied by the UE when initiating a new PDU session. The SMF controls QoS flow establishment and provides the relevant QoS information to the access network and UE.
A critical protocol distinction is that the DNN and S-NSSAI are normally transported in the accompanying NAS transport information, whereas the requested SSC mode is part of the PDU Session Establishment Request's session-management content. The QFI is associated with the QoS flows subsequently authorized and established by the network.
3GPP TS 23.501 and TS 23.502 define this session establishment and QoS flow framework. Therefore, D is correct.
Which statement below about 5G MM status is incorrect?
Options:
After an N2 context is established, the UE status is CM-CONNECTED on both the AMF and UE.
The CM status on the UE and AMF may be inconsistent.
After the UE receives the Registration Accept message, the UE status changes from RM-DEREGISTERED to RM-REGISTERED.
RM status and CM status are independent of each other.
Exact Extract — AMF Functionality
“The core network is responsible for: Providing user connections; Mobility management and session management; User authentication; Charging management; Providing interfaces for connecting to external networks.”
— Huawei Training Material, Position and Main Functions of the Core Network, page 88.
Technical Deep Dive
5G Mobility Management uses two state-management concepts. Registration Management (RM) describes whether the UE is registered with the network; the principal states are RM-DEREGISTERED and RM-REGISTERED . Connection Management (CM) describes the status of the NAS signalling connection between the UE and AMF; its principal states are CM-IDLE and CM-CONNECTED .
The RM and CM states represent different aspects of UE management. For example, a UE may be RM-REGISTERED while CM-IDLE. This means the subscriber remains registered but does not currently maintain an active NAS signalling connection.
During initial registration, the UE can establish a signalling connection before the registration procedure has completed. Therefore, RM-DEREGISTERED and CM-CONNECTED can temporarily coexist. When the UE receives a successful Registration Accept during initial registration, it enters RM-REGISTERED, consistent with Option C.
Why B is commonly selected in this examination: The intended examination interpretation is that the UE and AMF maintain corresponding CM states during normal, successfully coordinated connection-management procedures.
However, an important technical qualification is necessary. The UE detects release of its access-network signalling connection, whereas the AMF detects release of the corresponding N2 context. These events need not be observed at precisely the same instant. Temporary state discrepancies can therefore arise during failures or asynchronous release procedures.
Consequently, Option B is not universally false when interpreted literally. The examination's intended answer is B, but the question should be flagged as technically ambiguous because a transient inconsistency is possible.
Which of the following statements describe the advantages of IP address assignment by the UPF?
Select All that Apply
Options:
Adding SMFs and UPFs is easy, because peripheral devices do not need to be adjusted.
IP address assignment by the UPF provides simple planning and high address pool usage.
IP address assignment by the UPF is more applicable when one SMF is interconnected with multiple UPFs, or when one UPF is interconnected with multiple SMFs.
Not all address pools on the network need to be re-planned if SMFs need to be added to an SMF set.
Exact Extract
“The centralized CP simplifies O & M, improves O & M efficiency, and accelerates new service deployment. Distributed UP: The UP location is determined based on service delay requirements (for example, IoV services).”
— Huawei Training Material, Control and User Plane Separation, core-network architecture section.
Technical Deep Dive
In a 5G Standalone core network, UE IP addresses may be allocated by the SMF or by the UPF, depending on the operator's implementation and configuration. When UPF-based allocation is enabled, the UPF maintains or accesses the required IP address resources and performs address assignment under SMF control.
Option B: Locating address allocation at the UPF can simplify address management because subscriber address resources can be associated with the corresponding user-plane anchor. This can improve address-pool utilization and reduce unnecessary fragmentation across multiple SMF instances, provided that the UPF pools are correctly planned.
Option C: UPF-based allocation is particularly useful in many-to-many SMF–UPF topologies. Multiple SMFs can request address allocation from the same UPF without independently assigning overlapping addresses from its pool. Similarly, an SMF can select among several UPFs according to DNN, network slice, and service-area requirements.
Option D: When an additional SMF joins an SMF set, address allocation can remain under the existing UPF resource-management system. This reduces the need to repartition IP addresses among individual SMF instances.
Option A is incorrect because adding a UPF may require transport-network routing, address-pool advertisement, or other peripheral network configuration changes. UPF-based allocation does not universally eliminate those changes.
The SMF initiates IP allocation through PFCP signalling over N4. If the UPF performs allocation, it returns the allocated address in the PFCP response. A critical operational requirement is ensuring that address resources remain unique and that external routing correctly reaches the UPF anchoring the subscriber session.