name: VNFM
full_form: Virtualized Network Function Manager
context: 1. After NM, via EM, adjusts the configuration of the subject VNF and the nodes neighbour to the subject VNF if needed: - EM, or NM via EM requests capacity release for the VNF to the VNFM (see steps 2 to 5, in clause B.4.4.4 [2]) or - NM via NFVO requests VNFM to initiate VNF contraction. 2. VNFM notifies to the subscribed functional blocks (e.g., EM, NFVO) for lifecycle change notifications about initiating the scaling procedure. Note: [2] does not contain information of such notification. 3. VNFM starts the process to terminate a VNF component (see step 6, in clauses B.4.4.3, B.4.4.4 [2]). 4. Once the VNF component is gracefully terminated, the VNFM requests VIM directly to delete of the VM(s) (see step 7, in clauses B.4.4.3, B.4.4.4 [2]). 5. After VIM acknowledging the successful resources release, VNFM notifies EM that an existing VNF has been updated with requested capacity reduction (see steps 8, 10 in clauses B.4.4.3, B.4.4.4 [2]). 6. EM and VNFM update the VNF managed device
description: The Virtualized Network Function Manager (VNFM) is a network function responsible for managing the lifecycle of virtualized network functions (VNFs), including scaling, termination, and updating. It interacts with other network functions such as EM (Element Management) and NFVO (Network Functions Virtualization Orchestrator) to perform these tasks.
explanation: VNFM is classified as a Network Function based on its role in managing VNFs, as described in the context from 3GPP TS 32.842. The VNFM performs various actions such as adjusting configurations, terminating VNF components, and requesting resource releases, which are typical of network functions.
section_title: 5.5.18.4Description
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,B-Network Function,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,B-Network Function,O,O,B-Network Function,O,O
biotag_Description: O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Network Function,O,O,O,O,O,O,O,O