TWI714718B - Network function virtualization (nfv) performance measurement (pm) threshold monitoring operations - Google Patents

Abstract

Techniques for performing threshold monitoring operations (e.g., creation, deletion, or listing of one or more thresholds) in connection with virtual network function (VNF) related virtualization resource (VR) performance measurements (PMs) are discussed. A Network Manager (NM) can send a request to an Element Manager (EM) to perform a threshold monitoring operation, and the EM can send a request to a VNF manager (VNFM) to perform the threshold monitoring operation, which can send a request to a Virtualization Infrastructure Manager (VIM) to perform the threshold monitoring operation. The VIM can perform the threshold monitoring operation, and can send a reply to the VNFM indicating a result of the threshold monitoring operation, which can send a reply to the EM indicating the result of the threshold monitoring operation, which can send a reply to the NM indicating the result of the threshold monitoring operation.

Description

Network function virtualization (NFV) efficiency measurement (PM) threshold monitoring operation technology

Invention field

This article discloses the core network technology related to the communication network, and more particularly the operation technology related to the threshold of the virtual network function (VNF).

Background of the invention

Network function virtualization (NFV) involves replacing physical network nodes with virtual network functions (VNF) implemented by virtualized resources (VR) that perform the same functions as physical nodes.

According to an embodiment of the present invention, a device configured to be used inside a network manager (NM) is specifically proposed, which includes: a memory; and one or more processors configured with: A decision is made, where the decision is a decision used to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) performance measurement (PM) to delete a first existing Threshold to monitor the VNF related VR PM decision Or to obtain detailed information of one or more existing thresholds to monitor a decision of the VNF-related VR PM; send a request to a component manager (EM), where the request to the EM is: respond to the Decide to generate the new threshold to monitor the VNF-related VR PM request to the EM in response to the decision to delete the decision to delete the existing threshold to monitor the VNF-related VR PM's request to the EM, or a request to the EM that lists the thresholds identified by the threshold identifier of a list in response to the decision to obtain the decision; and receives a response from the EM, The response from the EM is: the response to the request to the EM is a response from the EM that is used to generate the request to the EM indicating a threshold to produce a result, and the response to the EM The request is a response from the EM that is used to delete the request to the EM and indicates a threshold value to delete a result, or the request to the EM is a response to the EM that is used to list A response from one of the EMs indicating the details of the one or more existing thresholds.

100: Evolved Packet Core (EPC) network

101: Network cutting film

102: Network sub-cutting piece

110: Home User Server (HSS)

120: Mobility Management Entity (MME)

130: Service Gateway (SGW)

140: Packet Data Network (PDN) Gateway (PGW)

150: Policy and Charging Rules Function (PCRF)

200: hardware resources

202: Hyper Manager

204: Peripherals

206: database

208: Network

210, 212, 214, 510: processor, processor core

220, 530: memory/storage device

240: bus

250: instruction

310: Network Manager (NM)

320: Network Function Virtualization (NFV) Planner (NFVO)

330: Network Component Manager (EM)

340: VNF Manager (VNFM)

350: NFV Infrastructure (NFVI)

360: Virtualized Infrastructure Manager (VIM)

370: Virtualized Network Function (VNF)

500: System

520: Communication circuit

600, 700, 800, 900: method

610-640, 710-770, 810-860, 910-950: Action block

Figure 1 is a schematic diagram illustrating the components of a network according to several embodiments.

Figure 2 is a block diagram illustrating that according to several specific embodiments, components can read instructions from a machine-readable or computer-readable medium (machine-readable storage medium) and perform any one or more of the methods discussed herein. By.

FIG. 3 is a schematic diagram of various frameworks for auxiliary VR efficiency measurement threshold monitoring and/or threshold crossing notification described herein.

FIG. 4 is a schematic diagram showing the flow of threshold generation for monitoring VR PM data according to the various procedures described in this article. It shows an example of the flow of monitoring VR efficiency measurement thresholds and generating notifications when threshold crossings or performance alarms are detected.

Fig. 5 is a block diagram of various systems for assisting VNF-related threshold monitoring and/or notification operations of VR PM according to the description herein.

Fig. 6 is a flowchart of various methods described herein for assisting threshold monitoring operations by NM.

FIG. 7 is a flowchart of various methods described herein for assisting threshold monitoring operations by EM.

Fig. 8 is a flowchart of various methods described herein for assisting threshold monitoring operations by VNFM.

Fig. 9 is a flowchart of various methods described herein for assisting threshold monitoring operations by VIM.

Detailed description of the preferred embodiment

The disclosure herein will now be described with reference to the accompanying drawings, in which similar element symbols are used to represent similar elements throughout the text, and such exemplary structures and devices are not necessarily drawn to scale. As used herein, the terms "component", "system", "interface", etc. are intended to refer to computer-related entities, hardware, software (for example, in execution), and/or firmware. For example, the component may be a processor (for example, a microprocessor, a controller, or other processing device), a processing program running on the processor, a controller, an object, an executable, a program, Storage devices, computers, tablet PCs, and/or user equipment with processing devices (for example, mobile phones, etc.). By way of illustration, applications and servers running on the server can also be components. One or more components can reside in a processing program, and a component can be limited to one computer and/or distributed between two or more computers. The elements of a set or other components of a set can be described herein, where the term "set" can be interpreted as "one or more."

In addition, these components can be executed from various computer-readable storage media having various data structures stored thereon, such as using modules. These components can be processed locally and/or remotely, such as based on having one or more data packets (e.g., data from one component and in the local system, distributed system, and/or cross-network, such as Internet Another component in a network, a local area network, a wide area network, or a similar network with a system interacts through signals).

As another example, a component can be a device with a specific function provided by a mechanical component operated by an electrical or electronic circuit, where the electrical or electronic circuit can be a software application or firmware executed by one or more processors Application operation. The one or more processors can be internal or external to the device and can execute at least part of software or firmware applications. As for yet another example, a component may be a device with a specific function provided by an electronic component without mechanical parts; the electronic component may include one or more processors therein to perform at least partly assigned to the electronic component The software and/or firmware of the function.

The use of text examples is intended to present concepts in specific ways. As used in this case, the term "or" is intended to include "or" Rather than mutually exclusive "or". In other words, unless stated otherwise or clearly self-evident from the context, "X adopts A or B" is intended to mean that any of the substitutions is naturally included. In other words, if X adopts A; X adopts B; or X adopts both A and B, then "X adopts A or B" is satisfied in either case. In addition, unless otherwise stated or clearly self-evident from the context indicating the singular form, the use of the articles "一(a)" and "一(an)" in this application and in the scope of the accompanying patent application usually requires interpretation To mean "one or more". Furthermore, to the extent that the terms "includes", "includes", "has", "has", "with" or their conjugates are used in the detailed description and the scope of the patent application, these terms are intended to be similar terms " The method of "include" is inclusive.

As used herein, the term "circuit" can refer to, can be a component thereof, or can include application-specific integrated circuits (ASIC), electronic circuits, processors (shared, dedicated, or group), and/or execute a Or memory (shared, dedicated, or grouped) of multiple software or firmware programs, combinational logic circuits, and/or other suitable hardware components that provide the functions. In some embodiments, the circuit can be implemented in, or the related functions of the circuit can be implemented by one or more software or firmware modules. In some embodiments, the circuit may include logic, and at least part of it may be operated in hardware.

The embodiments described herein can be implemented as a system using any suitably configured hardware and/or software. Figure 1 illustrates the components of a network according to several embodiments. In various aspects, connecting part or all of one or more of the components illustrated in FIG. 1 can be implemented as a virtual network function (VNF) connecting various aspects described herein. The Evolved Packet Core (EPC) network 100 is shown as including Home User Server (HSS) 110, mobile management Body (MME) 120, Service Gateway (SGW) 130, Packet Data Network (PDN) Gateway (PGW) 140, Policy and Charging Rules Function (PCRF) 150

The HSS 110 includes one or more databases for network users, including subscribing to relevant information to support the processing of network entities in the communication connection stage. For example, the HSS 110 can provide support for routing/roaming, authentication, authorization, naming/address resolution, and location dependency. Depending on the number of mobile users, equipment capacity, network organization structure, etc., the EPC network 100 may include one or more HSS 110.

The function of the MME 120 is similar to the control plane of the old General Packet Radio Service (GPRS) Support Node (SGSN). The mobility of the MME 120 to manage access is oriented to, for example, gateway selection and tracking area list management. The EPC network 100 may include one or more MMEs 120.

The SGW 130 ends the interface towards the E-UTRAN of the Evolved Universal Mobile Telecommunications System (UMTS), and determines the path of the data packet between the E-UTRAN and the EPC network 100. In addition, the SGW 130 can be a local mobility anchor for handover between evolved Node Bs, and can also provide an anchor for mobility between 3GPP. Other responsibilities may include lawful interception, billing, and several policy enforcement.

The PGW 140 ends the SGi interface towards the PDN. PGW PGW 140 arranges data packets between EPC network 100 and external networks, and can be a node for policy execution and charging data collection. The PCRF 150 is the policy and charging control element of the EPC network 100. In a non-roaming context, in the Internet Protocol Connectivity Access Network (IP-CAN) with the User Equipment (UE) There may be a single PCRF in the local public land mobile network (HPLMN) associated with the connection phase. In a roaming scenario with a breakthrough in local data volume, there may be two PCRFs associated with the UE’s IP-CAN connection phase: the local PCRF (H-PCRF) inside the HPLMN and the visit to the local public land mobile network ( VPLMN) internal visit PCRF (V-PCRF). PCRF 150 can be communicatively coupled to an application server (also called application function (AF)). In a nutshell, the application server uses Internet Protocol (IP) carrier resources with a core network (for example, UMTS packet service (PS) domain, long-term evolution (LTE) PS Data services, etc.). The application server can send PCRF 150 to instruct the new service process and select appropriate quality of service (QoS) and billing parameters. PCRF 150 can provide this rule as a policy and billing enforcement function (PCEF) (not shown in the figure) with appropriate data flow template (TFT) and QoS class (QCI) with identifier, such as loaded by the application server QoS and billing will begin tomorrow.

The components of EPC100 can be implemented in one physical node or separate physical nodes. In some embodiments, network function virtualization (NFV) is used to virtualize any of the previously described network node functions through executable instructions stored in one or more computer-readable storage media Or all (detailed later). A specific logical example of the EPC network 100 can be referred to as a network cutting piece 101. A specific logical example of a portion of the EPC network 100 may be referred to as the network sub-cut piece 102 (for example, the network sub-cut piece 102 is shown to include PGW 140 and PCRF 150).

Figure 2 is a block diagram illustrating that according to several specific embodiments, components can be read from a machine readable or computer readable medium (machine readable storage Storage medium) read instructions and perform any one or more of the methods discussed herein. More specifically, FIG. 2 shows a diagrammatic representation of a hardware resource 200. The hardware resource 200 includes one or more processors (or processor cores) 210, one or more memory/storage devices 220, and one or more A plurality of communication resources 230, each of which is communicatively coupled through the bus 240. For embodiments that utilize node virtualization (for example, NFV), the hypervisor 202 may be executed to provide an execution environment for one or more network slices/sub slices to utilize the hardware resources 200.

Processor 210 (for example, central processing unit (CPU), reduced instruction set computer (RISC) processor, complex instruction set computer (CISC) processor, graphics processing unit (GPU), digital signal processor (DSP) such as baseband The processor, application-specific integrated circuit (ASIC), radio frequency integrated circuit (RFIC), other processors, or any suitable combination thereof) may include, for example, the processor 212 and the processor 214. The memory/storage device 220 may include a main memory, a disc storage device, or any suitable combination thereof.

The communication resource 230 may include interconnection and/or network interface components or other suitable devices to communicate with one or more peripheral devices 204 and/or one or more database 206 via the network 208. For example, the communication resource 230 may include wired communication components (for example, for coupling through a universal serial bus (USB)), cellular communication components, near field communication (NFC) components, Bluetooth® components (for example, Bluetooth® Low energy), Wi-Fi® components, and other communication components.

The instruction 250 may include software, programs, applications, applets, mobile phone applications, or other executable codes to make At least any of the processors 210 can perform any one or more of the methods discussed herein. The instructions 250 may reside completely or partially in at least one of the processor 210 (for example, inside the cache memory of the processor), the memory/storage device 220, or any suitable combination thereof. Furthermore, any part of the command 250 can be transferred to the hardware resource 200 from any combination of the peripheral device 204 and/or the database 206. Accordingly, the memory of the processor 210, the memory/storage device 220, the peripheral device 204, and the database 206 are examples of computer-readable and machine-readable media.

In various embodiments, the techniques described herein can be used to generate, delete, and/or list VNF-related virtualized resource (VR) efficiency measurement (PM) related thresholds, and/or generate such threshold crossings Notice.

To ensure that the virtualized network functions (VNF) deployed on the network function virtualization (NFV) infrastructure (NFVI) can deliver consistent and acceptable service quality to end users, and to isolate and correct faults in the most timely manner In this case, virtualized resource (VR) efficiency measurement (PM) can be used. This equivalent energy measurement reflects the way VNF is affected by NFVI services, and the unique properties of services are provided by NFVI, such as CPU, virtual machine, memory, and virtual network. Therefore, NFV efficiency measurement can be measured in VNF and NFVI.

However, in order to identify possible problems from the performance data, conventional operators first collect performance for days, weeks, or even months, and then screen a large amount of data, which may be time-consuming and expensive due to the processing power involved. Even if these conventional technologies may eventually be found from PM data exploration The problem may be too late to be alleviated because of the dynamic fluctuations of network traffic.

In the various embodiments discussed herein, threshold monitoring operations including threshold generation, threshold deletion, and threshold list can be used to monitor VNF-related VR efficiency measurements. When the metric crosses the threshold, a threshold cross notification can be reported.

Referring to FIG. 3, it illustrates a schematic diagram of an architecture that assists in the monitoring of the threshold value of the VR efficiency measurement and/or the threshold crossing notification according to various aspects described herein. In Figure 3, the various virtualized network function (VNF) performance energy measurement (PM) threshold generation flow (and optionally the threshold crossing notification) that can be connected to the description for adoption is illustrated as the threshold together with the threshold crossing notification flow. Monitoring operation instance. The system illustrated in Figure 3 includes a network manager (NM) 310, a network function virtualization (NFV) planner (NFVO) 320, a network element manager (EM) 330, and an NFV infrastructure (NFVI) 350 The virtualized resource (VR) is a set of virtualized network functions (VNF) 370 _i , VNF manager (VNFM) 340, and virtualized infrastructure manager (VIM) 360. The solid lines between these entities indicate various reference points that assist the data exchange between these entities, the dashed lines indicate the data flow associated with threshold generation, and the solid dashed lines indicate the data flow associated with threshold crossing notifications.

Referring to Figure 4, a schematic diagram showing the process of monitoring the threshold generation of the VR PM data program according to the various aspects described in this article, which shows the monitoring of the VR efficiency measurement threshold and the generation of notifications when threshold crossings or performance alarms are detected Process instance. In various aspects, the techniques described herein can be used to perform threshold monitoring operations (for example, threshold production Generation, deletion, list, etc.), and notify the NM and/or operator of these thresholds that cross. The flowchart in Figure 4 shows an example of a scenario involving the generation and subsequent triggering of the threshold.

In Figure 4-1, NM can send a request to EN to generate one or more thresholds that can be defined by parameters, such as iOCName (information target category (IOC) name), iOCInstanceList (IOC case list), thresholdInfoList (threshold information list, It can specify the threshold value of a specific type of efficiency measurement (for example, through one or more measurement types), etc. to monitor the VNF-related VR efficiency measurement.

At 2, the EM can send a request to the VNFM to generate a threshold for monitoring the measurement type specified in the thresholdInfoList on the VNF case identified by iOCName and iOCInstanceList.

In 3, the VNFM can send a request to the VIM to generate a threshold to monitor the virtualized resource identified by the resource selector parameter (in the orientation, the measurement type in the thresholdInfoList provided by EM can be mapped to the resource selector in many ways Either of them).

At 4, the VIM can send a response to the VNFM with a thresholdId (threshold identity) parameter that can identify the threshold (etc.) that has been generated.

At 5, the VNFM can send a response to the EM with the generated threshold identifier.

In 6, the EM can send a response to the NM with the monitorId (monitor identity) parameter, which can specify a unique identifier of the thresholdMonitor (for example, the threshold at which the PM is or can be connected to monitor). Value), which may have a status field with a Success value.

At 7, the VIM may send a ThresholdCrossedNotification to the VNFM, which may have a threshold ID (for example, through the thresholdId parameter) which indicates a threshold that has been crossed.

At 8, the VNFM can send a notification to the EM indicating that the threshold ID has been cross-identified by the threshold. VNFM can send VR performance alarm notification to EM.

At 9, EM can send VNF-related VR performance alert notifications to NM.

In various aspects, the techniques discussed in this article can be used in conjunction with threshold monitoring operations, such as threshold generation, threshold deletion, and threshold list. The following use cases provide contextual examples involving the generation, deletion, and listing of thresholds, and related actions that can be performed by NM, EM, VNFM, and/or VIM linking these threshold monitoring operations.

Table 1 below shows an example of a use case for threshold generation to monitor one or more VNF-related VR efficiency measures:

Table 2 below shows examples of use cases related to monitoring one or more VNF-related VR efficiency measurement threshold deletions:

Table 3 below shows an example of a use case for linking to monitor one or more VNF-related VR efficiency measurement thresholds:

In addition, in various aspects, the techniques discussed in this article can be linked to various thresholds to generate threshold crossing notifications. Table 4 below shows an example of a use case for the notification of VR efficiency measurement threshold crossing:

In addition, in various aspects, the functions of one or more of the reference points in FIG. 3 can be modified to support the threshold monitoring and notification operations discussed herein. For example, in various embodiments, the Ve-Vnfm-em reference point can have the following capabilities: (a) The Ve-Vnfm-em reference point can support This capability allows EM to request VNFM to generate thresholds to monitor VNF-related VR efficiency measurements; (b) The Ve-Vnfm-em reference point can support the following capabilities, allowing VNFM to notify the results of EM thresholds; (c) Ve-Vnfm- The em reference point can support the following capabilities, allowing EM to request the VNFM to delete the threshold used to monitor the VNF-related VR efficiency measurement; (d) The Ve-Vnfm-em reference point can support the following capabilities, allowing the VNFM to notify the result of the EM threshold deletion ; (E) The Ve-Vnfm-em reference point can support the following capabilities, allowing EM to request the VNFM list to monitor one, multiple, or all thresholds of the VNF-related VR efficiency measurement; (f) Ve-Vnfm-em reference The points can support the following capabilities, allowing VNFM to notify the results of the EM threshold list; (g) The Ve-Vnfm-em reference point can support the following capabilities, allowing VNFM to notify EM when it detects the threshold crossing of the VNF-related VR efficiency measurement. In the orientation, other reference points related to threshold monitoring and notification operations may similarly have the ability to support the operations described herein.

Referring to FIG. 5, a block diagram of a system 500 for assisting the threshold monitoring and/or notification operation of VR PM related to VNF according to various aspects described herein is illustrated. Depending on the embodiment, the system 500 may be used in conjunction with one or more of NM, EM, VNFM, or VIM. The system 500 may include one or more processors 510 (for example, it may include one or more of the processors 210, etc.), a communication circuit 520 (which may communicate with auxiliary data such as one or more reference points, networks, etc.) , And may include communication resources 230, etc.), and memory 530 (which may include any of a variety of storage media, and may store associated with at least one of one or more processors 510 or communication circuits 520 Commands and/or data, and may include memory/storage device 220 and/or processor 510 cache, etc.). In some aspects, one or more processors 510, communication circuits 520, and memory 530 may be included in a single device, while in other aspects, they may be included in different devices, such as components of a distributed architecture . As will be described in detail later, depending on the embodiment, the system 500 may assist in threshold monitoring and/or notification operations of any of NM, EM, VNFM, and/or VIM.

The first group of embodiments of the system 500 is related to the NM-related embodiments. In an embodiment of the system 500 associated with the NM, the processor 510 may determine to implement a threshold monitoring operation (eg, based on operator input, etc.). The determined threshold monitoring operation may be to generate a threshold to monitor the VNF-related VR PM, delete the threshold to monitor the VNF-related VR PM, or determine detailed information about one or more threshold monitoring VNF-related VR PM.

Regarding the aspect related to generating the threshold value at the NM, the processor 510 may send a request to the EM to generate a new threshold value, and may receive a response from the NM indicating the result of the request to the EM to generate the new threshold value. In a detailed example, the request sent by the processor 510 may specify one or more destination networks (DN) of one or more managed entity cases of one or more measurement types to be monitored by the generated threshold. , Which can be indicated by the IOC case list (iOCInstanceList) parameter. In these aspects, the request sent by the processor 510 may also include one or more IOC name (iOCName) parameters which specify the name of a managed entity category for each of the ManagedEntity cases specified by the iOCInstanceList parameter, And may include one or more threshold information lists (rhresholdInfoLisr) parameters which specify the specific measurement type for the new threshold to be generated. Processed by The response received from the EM by the device 510 may indicate the status of the request to the EM, for example, success, failure, or partial success, and may also indicate, such as indicating the identity of the generated threshold through the associated monitorId parameter.

In terms of the NM deletion threshold, the processor 510 may send a request to the EM to delete the current threshold, and may receive a response from the NM indicating the result of the EM request to delete the current threshold. In a detailed example, the request for EM can indicate the threshold to be suspended and removed through the associated identifier (for example, the monitorId parameter can specify the unique identifier of thresholdMonitor, which can indicate that the VNF related VR PM is monitored Or the associated threshold can be monitored, etc.), and the response from the NM can indicate the status of the request to the EM, for example, success or failure.

In the aspect related to the NM list threshold, the processor 510 may send a request to the EM to list one or more thresholds, and may receive a response from the NM indicating the result of the EM request to list one or more thresholds. In a detailed example, the request to EM may include parameters (for example, monitorIdList parameter) which indicates the threshold value to be listed, and the response from EM may indicate the status of the request (for example, success or failure), and may indicate that the match is The threshold of the standard stated in the request to EM. In some aspects, the request may include a list of blank thresholds, and the response may include a list of all thresholds.

In addition, in the NM embodiment of the system 500, the processor 510 can receive (e.g., from the EM, through the Itf-N reference point) and monitor one or more current thresholds of the VNF-related VR PM (e.g., through the threshold generation operation Generated threshold), which may indicate that the associated threshold has crossed.

Referring to FIG. 6, there is illustrated a flowchart of a method 600 for assisting the threshold monitoring operation by the NM according to various aspects described herein. In some aspects, method 600 can be performed at NM. In other aspects, the machine-readable medium can store the associated instructions of the method 600, which when executed can cause the NM to perform the actions of the method 600.

At 610, the VR PM associated with the VNF can select threshold monitoring operations, such as the generation of one or more thresholds, the deletion of one or more thresholds, or a list of one or more thresholds.

At 620, the request may be sent to the EM for selected threshold monitoring operations (eg, generate, delete, list, etc.).

At 630, a response can be received from the EM indicating the result of the selected threshold monitoring operation.

At 640, a threshold crossing notification may be received, which indicates that the current threshold (for example, a threshold generated through 610-630, or a previously generated threshold, etc.) has been crossed.

Referring again to FIG. 5, the second set of embodiments of the system 500 are related to EM-related embodiments. In an embodiment of the system 500 associated with the EM, the processor 510 may receive a first request from the NM to perform the indicated threshold monitoring operation (for example, generating a threshold to monitor VNF-related VR PM, delete monitoring VNF-related VR PM Thresholds, or list one or more thresholds of VR PM related to VNF monitoring).

Regarding the aspect of EM-related threshold generation, the processor 510 may receive a first request from the NM to generate a new threshold to monitor the VNF-related VR PM, and may send a second request to the VNFM to generate a new threshold. Place The processor 510 may receive the first response indicating the second request from the VNFM to generate the result of the new threshold, and may send the second response to the NM, the response may indicate the first request to generate the result of the new threshold. In the detailed example, the first request from the NM and the second response to the NM may include the parameters described in the NM embodiment of the connection system 500 above. In addition, the second request to the VNFM can include a source selector (sourceSelector) parameter, which can specify one or more measurement types associated with the new threshold, and can specify and new parameters through one or more additional parameters. Additional details associated with the threshold, such as performanceMetric parameters, thresholdType parameters, and/or thresholdDetails parameters. The first response from the VNFM may include the threshold value generated by the identification of the threshold ID parameter.

Regarding the aspect related to the threshold deletion in the EM, the processor 510 may receive a first request from the NM to delete the threshold of the VR PM related to the monitoring VNF, and may send a second request to the VNFM to delete the threshold. The processor 510 may receive the first response from the VNFM indicating the result of the second request to delete the threshold, and may send the second response to the NM which may indicate the result of the first request to delete the threshold. In the orientation, the first request from the NM and the second response to the NM may include the parameters described in the NM embodiment of the connection system 500 above.

Regarding the aspect related to the threshold list in the EM, the processor 510 may receive a first request from the NM to list one or more thresholds of the VNF-related VR PM, and may send a second request to the VNFM to list the thresholds. The processor 510 may receive the first response from the VNFM and instruct the second request to list the results of one or more thresholds, and may send the second response to the NM. Instruct the first request to list the results of one or more thresholds. In the orientation, the first request from the NM and the second response to the NM may include the parameters described in the NM embodiment of the connection system 500 above.

In addition, in the NM embodiment of the system 500, the processor 510 may receive (for example, from the VNFM, through the Ve-Vnfm-em reference point) a notification that the threshold on the VNF-related VR PM has crossed. In response, the processor 510 may add the VNF-related VR performance alarm associated with the crossed threshold to the alarm list, and may send a VNF-related VR performance alarm notification to the NM.

Referring to FIG. 7, there is illustrated a flowchart of a method 700 for assisting threshold monitoring operations by EM according to various aspects described herein. In some aspects, method 700 can be performed in EM. In other aspects, the machine-readable medium can store the associated instructions of the method 700, which when executed can cause the EM to perform the actions of the method 700.

At 710, a request may be received from the NM to perform a specified threshold monitoring operation (for example, threshold generation, threshold deletion, threshold list, etc.) associated with the VR PM of the VNF.

At 720, a request can be sent to the VNFM to perform a specified threshold monitoring operation.

At 730, a response indicating the result of the specified threshold monitoring operation (eg, success, failure, threshold list, etc.) may be received from the VNFM.

At 740, a response can be sent to the NM to indicate the result of the specified threshold monitoring operation.

Optionally, at 750, notifications can be received from VNFM The threshold (for example, specified by the thresholdId parameter) has crossed.

In 760, in response to the notification received at 750, by adding the VNF-related VR performance alarm to the alarm list based on the crossed threshold, a performance alarm can be determined to be generated.

In 770, based on the VNF-related VR performance alarms added by 760 to the alarm list, VNF-related VR performance alarm notifications can be sent to the NM.

Referring again to FIG. 5, the embodiment of the system 500 of the third set relates to an embodiment related to VNFM. The processor 510 may receive a request from the EM to perform a threshold monitoring operation, which may involve threshold generation, threshold deletion, or threshold list.

In the aspect related to the generation of the threshold of the VNFM, the processor 510 may receive a first request for generating a new threshold to monitor the VNF-related VR PM from the EM, and may send a second request for generating a new threshold to the VIM. The processor 510 may receive the first response indicating the result of the second request for generating the new threshold from the VIM, and may send the second response indicating the result of the first request for generating the new threshold to the EM.

In the aspect related to the threshold deletion of the VNFM, the processor 510 may receive a first request from the EM to delete the threshold value of the VR PM related to the monitoring VNF, and may send a second request to the VIM deletion threshold value. The processor 510 may receive the result of the first request indicating the deletion of the threshold in the first response from the VIM, and may send the result of the first request indicating the deletion of the threshold in the second response to the EM.

In relation to the VNFM threshold list, the processor 510 can receive the list from the EM to monitor one or more of the VNF related VR PM The first request for thresholds, and the second request for one or more thresholds that can be sent to the VNFM list. The processor 510 may receive the first response indicating the result of the second request for one or more thresholds from the VNFM, and may send the second response indicating the result of the first request for the one or more thresholds to the NM. In the orientation, the first request from the NM and the second response to the NM may include the parameters as described in the NM embodiment of the connection system 500 above.

In addition, the processor 510 can detect that the VNF-related VR PM has crossed the current threshold, which can be based on the threshold cross notification received from the VIM. In face-to-face, the threshold crossing notification from VIM may include one or more parameters indicating that the threshold has been crossed and/or the relevant details of the threshold crossing. Based on the processor 510 detecting that the threshold has been crossed, the processor 510 may send a threshold cross notification to the EM. The notification may include one or more parameters indicating that the threshold has crossed and/or the relevant details of the threshold cross, such as the objectInstanceId parameter, thresholdId Parameters, crossingDirection (crossing direction) parameters, performanceMetric parameters, and/or performanceValue (performance value) parameters.

Referring to FIG. 8, there is illustrated a flowchart of a method 800 for assisting threshold monitoring operations by VNFM in accordance with various aspects described herein. In some aspects, the method 800 can be performed in VNFM. In other aspects, the machine-readable medium can store the associated instructions of the method 800, which when executed can cause the VNFM to perform the actions of the method 800.

At 810, a request can be received from the EM to perform a specified threshold monitoring operation (for example, threshold generation, threshold deletion, threshold list, etc.) associated with VNF related VR PM.

At 820, a request can be sent to VIM to perform a specified threshold monitoring operation.

At 830, a response can be received from the VIM to indicate the result of the specified threshold monitoring operation (for example, success, failure, threshold list, etc.).

At 840, a response can be sent to the EM to indicate the result of the specified threshold monitoring operation.

Optionally, at 850, a notification threshold (for example, specified by the thresholdId parameter) has been crossed from the VNFM.

At 860, based on the notification threshold received from VIM has crossed, a threshold cross notification can be sent to EM.

Referring again to FIG. 5, the fourth set of embodiments of the system 500 relates to embodiments associated with VIM. The processor 510 may receive a request to perform a threshold monitoring operation from the EM, which may involve threshold generation, threshold deletion, or threshold list.

Regarding the aspect related to the generation of the threshold of the VIM, the processor 510 may receive a request for generating a new threshold from the VNFM, may generate a new threshold, and may send a response to the VNFM to indicate the result of the threshold generation (for example, a threshold identifier, etc.).

Regarding the aspect related to the threshold deletion in the VIM, the processor 510 may receive a threshold deletion request from the VNFM, may delete the threshold, and may send a response to the VNFM to indicate the result of the threshold deletion.

In the aspect related to the threshold list in the VIM, the processor 510 may receive a request for listing one or more thresholds from the VNFM, may generate a list of one or more thresholds, and may send a response to the VNFM instruction list 1 Or multiple threshold request results (for example, a list of thresholds, etc.).

In addition, the processor 510 can detect threshold crossings associated with existing thresholds, and based on the detected threshold crossings, send a threshold crossing notification to the VNFM, which can identify the thresholds that have been crossed and can provide additional information about the threshold crossings. In some aspects, the processor 510 can detect threshold crossings based on monitoring the existing thresholds of the VNF-related VR PM link. In other aspects, the processor 510 detects the threshold crossing based on the threshold crossing notification received from the NFVI.

Referring to FIG. 9, there is illustrated a flowchart of a method 900 for assisting threshold monitoring operations by VIM according to various aspects described herein. In some aspects, the method 900 can be performed in VIM. In other aspects, the machine-readable medium can store the associated instructions of the method 900, which when executed can cause the VIM to perform the actions of the method 900.

At 910, a request can be received from the VNFM to perform a specified threshold monitoring operation (for example, for VNF related VR PM generation, deletion, or listing of one or more thresholds, etc.).

At 920, a specified threshold monitoring operation can be performed.

At 930, a response can be sent to the VNFM to indicate the result of the specified threshold monitoring operation.

At 940, optionally, a threshold (for example, generated at 920 or previously existing) connected to the VNF-related VR PM can detect threshold crossing. Threshold crossing can be detected by receiving notification from NFVI or by monitoring VNF-related VR PM related to the threshold.

At 950, based on the threshold detected by 940, the threshold The cross notification can be sent to the VNFM, which can identify the crossed threshold and additional information associated with the threshold cross.

Examples herein may include subject matter, such as methods, means of performing actions, or blocks of methods. At least one machine-readable medium includes executable instructions, which can be used by machines (eg, processors with memory, integrated circuits for specific applications). (ASIC), Field Programmable Gate Array (FPGA), etc.) are executed to enable the machine to perform the actions of the method of simultaneous communication or the actions of the device or system according to the described embodiments and examples using multiple communication technologies.

Example 1 is a device configured to be used inside a network manager (NM), which includes: a memory; and one or more processors configured to: make a decision, wherein the decision is made A decision to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) efficiency measurement (PM) to delete a first existing threshold to monitor the VNF related VR PM A decision to obtain detailed information about one or more existing thresholds to monitor the VNF related VR PM; send a request to a component manager (EM), where the request to the EM is: response When the decision is used to generate the decision to generate the new threshold to monitor a request to the EM of the VNF related VR PM, in response to the decision to delete the decision to delete the existing threshold to monitor the VNF A request to the EM of the relevant VR PM, or a request to the EM that lists the thresholds identified by the threshold identifier of a list in response to the decision to obtain the decision; and receives a request from the EM Response, where the response from the EM is: the response to the request to the EM is used to generate The request to the EM instructs a threshold to produce a result from a response from the EM, in response to the request to the EM to delete the request to the EM to instruct a threshold to delete a result A response from the EM, or a response from the EM in response to the request to the EM indicating the details of the one or more existing thresholds for listing the request to the EM.

Example 2 includes the subject matter of any change in any of Example 1, wherein the one or more processors are further configured to receive a VNF-related VR performance alert notification from the EM.

Example 3 includes the subject matter of any changes in any of Examples 1-2, wherein the request to the EM is the request to the EM to be generated.

Example 4 includes the subject matter of any changes in any of Example 3, where the request to the EM includes an information object category (IOC) case list (iOCInstanceList) parameter which states that its measurementTypes (measurement types) are to be monitored One or more destination networks (DN) of one or more ManagedEntity cases.

Example 5 includes the subject matter of any change in any of Example 4, where the request to the EM includes an IOC name (iOCName) parameter for one of the one or more Managed Entity cases specified by the iOCInstanceList parameter Each contains a ManagedEntity category name.

Example 6 includes the subject matter of any of the changes in any of Example 3, where the request to the EM includes specifying that one or more specific A threshold information list (thresholdInfoList) parameter of the new threshold of measurementTypes.

Example 7 includes the subject matter of any change in any of Examples 1-2, wherein the request to the EM is the request to the EM for deletion, and the request to the EM contains a description of the intention to be A monitor ID (monitorId) parameter of a ThresholdMonitor to stop and remove.

Example 8 includes the subject matter of any changes in any of Examples 1-2, wherein the request to the EM is the request to the EM for listing, and the request to the EM includes a statement that it is to be A monitor ID list (monitorIdList) parameter of ThresholdMonitors of the list.

Example 9 is a device configured to be used inside a component manager (EM), which includes: a memory; and one or more processors configured with: from a network manager (NM) Receive a first request, where the first request from the NM is: to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) efficiency measurement (PM) from the A first request from the NM to delete an existing threshold to monitor the VNF-related VR PM from the NM, or to list the thresholds identified by a list of threshold identifiers from the NM A first request; send a second request to a VNF manager (VNFM), where the second request to the VNFM is: the response to the first request from the NM is the generated from the NM The first request is used to generate the new threshold to monitor the VNF related VR PM to the VNFM one of the second Request, in response to the first request from the NM to delete the first request from the NM to delete the existing threshold to monitor the VNF related VR PM to the VNFM a second request, or response When the first request from the NM is to list the first request from the NM to list the thresholds identified by the threshold identifier of the list, a second request to the VNFM; from the The VNFM receives a first response, where the first response from the VNFM includes: responding to the second request to the VNFM to generate one or more thresholds of the second request to the VNFM An identifier is generated, in response to the second request to the VNFM for deleting the second request to the VNFM, one or more of the thresholds is deleted, or in response to The second request of the VNFM is the second request to the VNFM for listing and includes the details of one or more thresholds; and sending a second response to the NM, where the second response instruction to the NM : In response to the first response from the VNFM containing the one or more thresholds, the one or more identifiers are generated and indicate a result of the first request for generating the new threshold, the response is The first response of the VNFM includes the one or more identifiers of the one or more thresholds being deleted indicating a result of the first request to delete the existing threshold, or in response to a result from the VNFM The first response includes the details of one or more thresholds and indicates the details of the one or more thresholds.

Example 10 includes the subject matter of any change in any of Example 9, wherein the one or more processors are further configured to: receive a notification from a VNF manager (VNFM) related to the VNF The previous threshold of VR PM has been crossed; by adding a VNF-related VR performance alarm to an alarm list, it is determined to generate a performance alarm; and a VNF-related VR performance alarm notification is sent to the NM.

Example 11 includes the subject matter of any change in any of Examples 9-10, wherein the first request from the NM is used to generate the first request from the NM and the second request to the VNFM is used To generate the second request to the VNFM.

Example 12 includes the subject matter of any change in any of Example 11, wherein the second request to the VNFM includes a source selector parameter specifying one or more measurement types.

Example 13 includes the subject matter of any change in any of Example 11, wherein the second request to the VNFM includes a PerformanceMetric parameter, a thresholdType parameter, and a thresholdDetails parameter, which is generated for monitoring contained in the sourceSelector parameter The new threshold for the one or more measurement types.

Example 14 includes the subject matter of any change in any of Example 11, wherein the first response from the VNFM includes a threshold ID parameter indicating an identifier of the new threshold that has been generated.

Example 15 includes the subject matter of any change in any of Example 11, wherein the second response to the NM includes a monitor specifying a unique identifier of a ThresholdMonitor associated with the new threshold. The monitorId parameter includes a status parameter with a value of "Success".

Example 16 includes the subject matter of any change in any of Examples 9-10, wherein the first request from the NM is the first request from the NM for deletion and the second request to the VNFM is for In order to delete the second request to the VNFM, and the second response to the NM including a value with one of "Success" (success), "Failure", or "PartialSuccess" (partial success) State parameters.

Example 17 includes the subject matter of any of the changes in any of Examples 9-10, wherein the first request from the NM is the first request from the NM and the second request to the VNFM for the list. The list of the second request to the VNFM and the second response to the NM includes a monitor InfoList parameter that includes return information corresponding to ThresholdMonitors matching the input standard.

Example 18 includes the subject matter of any changes in any of Examples 11-12, wherein the second request to the VNFM includes a PerformanceMetric parameter, a thresholdType parameter, and a thresholdDetails parameter, which is generated for monitoring in the sourceSelector parameter The new threshold of the one or more measurement types specified in.

Example 19 includes the subject matter of any changes in any of Examples 11-12 or 18, wherein the first response from the VNFM includes Shows a threshold ID (thresholdId) parameter of an identifier of the new threshold that has been generated.

Example 20 is a device configured to be used in a virtualized network function (VNF) manager (VNFM), which includes: a memory; and one or more processors configured with: self The component manager (EM) receives a request, where the request from the EM is: to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) efficiency measurement (PM) A request from the EM, a request from the EM to delete an existing threshold to monitor the VNF-related VR PM, or a request from the EM to list the thresholds identified by a list of threshold identifiers ; And send a response to the EM, where the response instruction to the EM: in response to the request from the EM for the request from the EM to generate one or more identifiers indicating multiple thresholds Is generated in response to the request from the EM to delete the request from the EM indicating that one or more of the thresholds is deleted, or in response to the request from the EM to delete The details of the list indicating multiple thresholds from the EM request.

Example 21 includes the subject matter of any change in any of Example 20, wherein the one or more processors are further configured to detect that the VNF-related VR PM has crossed a first threshold.

Example 22 includes the subject matter of any change in any of Example 21, wherein the one or more processors are further configured to send a notification to the EM that the first threshold has crossed on the VNF-related VR PM .

Instance 23 includes the subject matter of any change in any of instances 22, wherein the notification includes a target instance id (objectInstanceId) parameter identifying the first threshold.

Example 24 includes the subject matter of any change in any of Example 22, wherein the notification includes a thresholdId parameter, a crossingDirection parameter, a performanceMetric parameter, and a performanceValue parameter, which indicate that the first threshold has been crossed.

Example 25 includes the subject matter of any changes in any of Example 21, wherein the one or more processors are further configured to be based on a threshold cross notification received from a virtualized infrastructure manager (VIM) It is detected that the VR PM has crossed the first threshold.

Example 26 includes the subject matter of any change in any of Examples 20-25, wherein the one or more processors are further configured to: send an additional request to a virtualized infrastructure manager (VIM), Where the additional request instruction to the VIM is in response to the request from the EM for the request from the EM to be generated, and the request from the EM to be instructed to be generated in response to the request from the EM The request from the EM for deletion indicates the request from the EM for deletion, or in response to the request from the EM as the request from the EM for listing and indicates the request from the EM for listing The request of the EM; and receiving an additional response from the virtualization infrastructure manager (VIM), wherein the response to the additional request instruction to the VIM is used to generate the request from the EM and the additional response from the VIM In response to a result of the request generated from the EM, in response to the additional request to the VIM instruction to delete from the The request of the EM indicates the request from the EM to delete, or the request from the EM in response to the additional request to the VIM indicates the request from the EM to indicate the request from the EM to list .

Example 27 includes the subject matter of any change in any of Examples 20-25, where the request from the EM is the request from the EM for generation, and the response to the EM includes an indication that has been generated A threshold ID (thresholdId) parameter of one of the new threshold identifiers.

Example 28 is a device configured to be used inside a virtualized infrastructure manager (VIM), which includes: a memory; and one or more processors configured to: process from a virtualized network A request from a VNF manager (VNFM), where the request from the VNFM is associated with a virtualized network function (VNF) related virtualized resource (VR) efficiency energy measurement (PM) threshold monitoring , Where the request from the VNFM is a request from the VNFM to generate a new threshold to monitor the VNF-related VR PM to delete one of the existing thresholds for a set of the VNF-related VR PM to be monitored. A request from the VNFM for the existing threshold, or a request from the VNFM for one or more existing thresholds in the set indicated by the threshold identifier of a list; in response to a request from the VNFM The request is one of the following: in response to the request from the VNFM for the request from the VNFM to generate the new threshold to monitor the VNF related VR PM, and in response to the request from the VNFM The instructed to delete the set of existing thresholds for the request from the VNFM for deletion Or generate a list of existing thresholds for monitoring the second set of VR PM related to the VNF in response to the request from the VNFM for the request from the VNFM for listing; and send a response to the The VNFM responds to the result of the request from the VNFM for generating the new threshold indication, responds to the result of the request from the VNFM for deleting the indicated threshold indication, or responds to generating the result of the request from the VNFM The list indicates the result of the request from the VNFM to list.

Example 29 includes the subject matter of any change in any of Example 28, wherein the one or more processors are further configured to send a threshold associated with one of the set's existing thresholds that has crossed the existing threshold Cross notification to the VNFM, wherein the threshold cross notification indication is used for an associated identifier that has crossed one of the existing thresholds.

Example 30 includes the subject matter of any change in any of Example 29, wherein the one or more processors are further configured to detect a threshold crossing associated with the crossed existing threshold, and one of these Or multiple processors are configured to generate the threshold crossing notification in response to the threshold crossing.

Example 31 includes the subject matter of any change in any of Example 29, wherein the one or more processors are further configured to receive an additional threshold crossing notification from a network function virtualization infrastructure (NFVI), And the one or more processors are configured to generate the threshold crossing notification in response to the additional threshold crossing notification received from the NFVI.

Example 32 is a machine readable medium containing instructions that when executed cause a network manager (NM) to: A decision, where the decision is a decision used to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) performance measurement (PM), to delete a first existing threshold to Monitor a decision of the VNF-related VR PM, or obtain detailed information about one or more existing thresholds to monitor a decision of the VNF-related VR PM; send a request to a component manager (EM), where to the EM The request is: in response to a request to the EM that the decision is used to generate the decision to generate the new threshold to monitor the VNF-related VR PM, and in response to the decision to delete the decision to be used to delete Existing thresholds to monitor the VNF-related VR PM's request to the EM, or to list the thresholds identified by a list of threshold identifiers to the EM in response to the decision to obtain the decision; And receiving a response from the EM, where the response from the EM is: responding to the request to the EM to generate the request to the EM and indicating a threshold to produce a result from the EM Response, responding to the request to the EM to delete the request to the EM indicating a threshold to delete a result from the EM, or responding to the request to the EM to list The request to the EM indicates the details of the one or more existing thresholds in response from one of the EMs.

Example 33 includes the subject matter of any change in any of Example 32, wherein the instructions, when executed, further cause the NM to receive a VNF-related VR performance alert notification from the EM.

Example 34 includes the subject matter of any variation of any of Examples 32-33, wherein the request to the EM is the request to the EM to be generated.

Example 35 includes the subject matter of any change in any of Example 34, wherein the request to the EM includes an information object class (IOC) case list (iOCInstanceList) parameter which specifies one or more measurementTypes to be monitored One or more destination networks (DN) in a ManagedEntity case.

Example 36 includes the subject matter of any change in any of Example 35, wherein the request to the EM includes an IOC name (iOCName) parameter for one of the one or more ManagedEntity cases specified by the iOCInstanceList parameter Each contains a ManagedEntity category name.

Example 37 includes the subject matter of any change in any of Example 34, wherein the request to the EM includes a thresholdInfoList parameter specifying the new threshold for one or more specific measurementTypes.

Example 38 includes the subject matter of any change in any of Examples 32-33, wherein the request to the EM is the request to the EM for deletion, and the request to the EM includes a statement that it is intended to be A monitor ID (monitorId) parameter of a ThresholdMonitor to stop and remove.

Example 39 includes the subject matter of any of the changes in any of Examples 32-33, wherein the request to the EM is the request to the EM for listing, and the request to the EM includes a statement that it is intended to be A monitor ID list (monitorIdLisr) parameter of ThresholdMonitors of the list.

Example 40 is a machine-readable medium containing instructions that, when executed, cause an element manager (EM) to: receive a first request from a network manager (NM), where the instructions from the NM The first request is: a first request from the NM to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) efficiency measurement (PM) to delete a The existing threshold is used to monitor the first request from the NM of the VNF-related VR PM, or to list the threshold identified by the threshold identifier of a list of the first request from the NM; send a second request to A VNF Manager (VNFM), wherein the second request to the VNFM is: responding to the first request from the NM for generating the first request from the NM for generating the new threshold for monitoring A second request from the VNF-related VR PM to the VNFM in response to the first request from the NM for deleting the first request from the NM to delete the existing threshold to monitor the VNF-related VR PM’s second request to the VNFM, or in response to the first request from the NM to list the first request from the NM to list the threshold identifiers identified by the list Threshold value to a second request of the VNFM; receiving a first response from the VNFM, wherein the first response from the VNFM includes: responding to the second request to the VNFM for generating a response to the VNFM One or more identifiers of the second request one or more thresholds are generated, and the response to the second request to the VNFM is one of the one or more thresholds used to delete the second request to the VNFM Or multiple identifiers are deleted, or in response to the second request to the VNFM, the second request to the VNFM for listing includes one or more thresholds Value details; and sending a second response to the NM, where the second response instruction to the NM: responding to the one or more of the one or more thresholds in the first response from the VNFM The identifier is generated indicating a result of the first request to generate the new threshold, in response to the one or more identifiers containing the one or more thresholds being deleted in the first response from the VNFM And indicate one of the results of the first request to delete the existing threshold, or indicate the details of the one or more thresholds in response to the first response from the VNFM containing the details of one or more thresholds detail.

Example 41 includes the subject matter of any change in any of Example 40, wherein the instructions, when executed, further enable the EM to: receive a notification from a VNF manager (VNFM) on the VNF related VR PM A threshold has been crossed; by adding a VNF-related VR performance alarm to an alarm list, it is determined to generate a performance alarm; and a VNF-related VR performance alarm notification is sent to the NM.

Example 42 includes the subject matter of any of the changes in any of Examples 40-41, wherein the first request from the NM is used to generate the first request from the NM and the second request to the VNFM is used To generate the second request to the VNFM.

Example 43 includes the subject matter of any change in any of Examples 42, wherein the second request to the VNFM includes a sourceSelector parameter specifying one or more measurement types.

Example 44 includes the subject matter of any change in any of Example 42, wherein the second request to the VNFM includes a PerformanceMetric parameter, a thresholdType parameter, and a The thresholdDetails parameter generates the new threshold for monitoring the one or more measurement types specified in the sourceSelector parameter.

Example 45 includes the subject matter of any of the changes in any of Example 42, wherein the first response from the VNFM includes a threshold ID parameter indicating an identifier of the new threshold that has been generated.

Example 46 includes the subject matter of any change in any of Example 42, wherein the second response to the NM includes a monitor ID (monitorId) specifying a unique identifier of a ThresholdMonitor associated with the new threshold Parameters, and include a status parameter with a value of "Success".

Example 47 includes the subject matter of any change in any of Examples 40-41, wherein the first request from the NM is the first request from the NM for deletion and the second request to the VNFM is for deletion In order to delete the second request to the VNFM, and the second response to the NM, a status parameter having one of the values of "Success", "Failure", or "PartialSuccess" is included.

Example 48 includes the subject matter of any of the changes in any of Examples 40-41, wherein the first request from the NM is the first request from the NM and the second request to the VNFM for listing The second request to the VNFM in the list and the second response to the NM include a monitor information list (monitorInfoList) parameter It contains the return information corresponding to ThresholdMonitors matching the input standard.

Example 49 includes the subject matter of any changes in any of Examples 42-43, wherein the second request to the VNFM includes a PerformanceMetric parameter, a thresholdType parameter, and a thresholdDetails parameter, which is generated for monitoring in the sourceSelector parameter The new threshold of the one or more measurement types specified in.

Example 50 includes the subject matter of any change in any of Examples 42-43 or 49, wherein the first response from the VNFM includes a threshold ID parameter indicating an identifier of the new threshold that has been generated .

Example 51 is a machine-readable medium containing instructions that, when executed, cause a virtualized network function (VNF) manager (VNFM) to: receive a request from a component manager (EM), where The request from the EM is a request from the EM used to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) performance measurement (PM) to delete a Existing threshold to monitor the request from the EM of the VNF-related VR PM, or to list the threshold identified by the threshold identifier of a list from the EM; and send a response to the EM, where to The response instruction of the EM: in response to the request from the EM for the request from the EM to indicate that one or more identifiers of multiple thresholds are generated, in response to the request from the EM Indicate one of the thresholds for the request from the EM for deletion or The multiple identifiers are deleted, or the details of multiple thresholds are indicated in response to the request from the EM to list the request from the EM.

Example 52 includes the subject matter of any change in any of Example 51, wherein the instructions, when executed, further cause the VNFM to detect that the VNF-related VR PM has crossed a first threshold.

Example 53 includes the subject matter of any change in any of Examples 52, wherein the instructions, when executed, further cause the VNFM to send a notification to the EM that the first threshold has crossed the VNF-related VR PM.

Instance 54 includes the subject matter of any changes in any of instances 53, wherein the notification includes an objectInstanceId parameter that identifies the first threshold.

Example 55 includes the subject matter of any change in any of Example 53, wherein the notification includes a thresholdId parameter, a crossingDirection parameter, a performanceMetric parameter, and a performanceValue parameter, which indicate that the first threshold has been crossed.

Example 56 includes the subject matter of any change in any of Examples 52, wherein the instructions, when executed, further cause the VNFM to detect the VNFM based on a threshold crossing notification received from a Virtualized Infrastructure Manager (VIM) VR PM has crossed this first threshold.

Example 57 includes the subject matter of any change in any of Examples 51-56, wherein the instructions, when executed, further enable the VNFM to: send an additional request to a virtualized infrastructure manager (VIM), The additional request instruction to the VIM responds to the EM The request is the request from the EM to be generated and the request from the EM to be generated is indicated in response to the request from the EM to be the request from the EM to be deleted. Delete the request from the EM, or in response to the request from the EM as the request from the EM for listing, indicate the request from the EM for listing; and manage from the virtualization infrastructure The VIM receives an additional response, where the response to the additional request to the VIM indicates the request generated from the EM, the additional response from the VIM indicates the request generated from the EM As a result, in response to the additional request instruction to the VIM to delete the request from the EM, the request from the EM instruction to delete, or in response to the additional request instruction to the VIM to generate The request from the EM indicates the request from the EM to list.

Example 58 includes the subject matter of any change in any one of Examples 51-56, where the request from the EM is the request from the EM for generation, and the response to the EM includes an indication that has been generated A threshold ID (thresholdId) parameter of one of the new threshold identifiers.

Example 59 is a machine-readable medium containing instructions that, when executed, cause a virtualized infrastructure manager (VIM) to: process data from a virtualized network function (VNF) manager (VNFM) A request, wherein the request from the VNFM is associated with a virtualized network function (VNF) related virtualized resource (VR) performance energy measurement (PM) threshold monitoring, wherein the request from the VNFM is used for Generate a new threshold to monitor the VNF related VR PM from one of the VNFM please Request to delete one of the indicated existing thresholds of a set of existing thresholds that monitor the VNF-related VR PM from a request from the VNFM, or to list the existing set of the set indicated by a list of threshold identifiers One of the thresholds or multiple existing thresholds is requested from one of the VNFMs; in response to the request from the VNFM, one of the following: the response to the request from the VNFM is the one generated from the VNFM Request to generate the new threshold to monitor the VNF-related VR PM, in response to the request from the VNFM for the request from the VNFM for deletion, to delete the indicated existing threshold in the set of existing thresholds, or In response to the request from the VNFM for listing the request from the VNFM, a list of existing thresholds for monitoring the second set of VR PMs related to the VNF is generated; and sending a response to the VNFM in response to generating the The new threshold indication is used to generate the result of the request from the VNFM, in response to deleting the indicated threshold indication to delete the result of the request from the VNFM, or in response to generating the list indication for listing The result of the request from the VNFM.

Example 60 includes the subject matter of any change in any of Example 59, wherein the instructions, when executed, further cause the VIM to send a threshold crossing notification associated with one of the set of existing thresholds that has crossed the existing threshold To the VNFM, where the threshold crossing notification indication is used for an associated identifier that has crossed one of the existing thresholds.

Example 61 includes the subject matter of any change in any of Example 60, wherein the instructions, when executed, further cause the VIM to detect a threshold crossing associated with the crossed existing threshold, and the Waiting for one or more processors to be configured to generate the threshold crossing notification in response to the threshold crossing.

Example 62 includes the subject matter of any change in any of Example 60, wherein the instructions, when executed, further cause the VIM to receive an additional threshold crossing notification from a network function virtualization infrastructure (NFVI), and among others The one or more processors are configured to generate the threshold crossing notification in response to the additional threshold crossing notification received from the NFVI.

Example 63 is a device configured to be used inside a network manager (NM), which includes: a component for storing commands; and a component for processing is configured to execute the commands to: A decision is made, where the decision is a decision used to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) performance measurement (PM), to delete a first existing threshold To monitor a decision of the VNF-related VR PM, or to obtain detailed information about one or more existing thresholds to monitor a decision of the VNF-related VR PM; send a request to a component manager (EM), where to the The request of EM is: in response to a request to the EM that the new threshold is generated to monitor the VNF-related VR PM in response to the decision to generate the decision, and to delete in response to the decision to delete the decision The existing threshold is used to monitor the VNF-related VR PM's request to the EM, or in response to the decision to obtain the decision and list the thresholds identified by a list of threshold identifiers to the EM request ; And receiving a response from the EM, where the response from the EM is: the response to the request to the EM is the request to the EM to be generated A response from the EM that indicates a threshold to produce a result, a response from the EM that responds to the request to the EM to delete the request to the EM, and a response from the EM that indicates a threshold to delete a result , Or in response to one of the EMs indicating the details of the one or more existing thresholds in response to the request to the EM for the request to the EM for listing.

Example 64 includes the subject matter of any change in any of Example 63, wherein the means for processing is further configured to execute the instructions to receive a VNF-related VR performance alert notification from the EM.

Example 65 includes the subject matter of any variation of any of Examples 63-64, wherein the request to the EM is the request to the EM to be generated.

Example 66 includes the subject matter of any change in any of Example 65, where the request to the EM includes an information object class (IOC) case list (iOCInstanceList) parameter which specifies one or more of its measurementTypes to be monitored One or more destination networks (DN) in a ManagedEntity case.

Instance 67 includes the subject matter of any change in any of instances 66, wherein the request to the EM includes an IOC name (iOCName) parameter for one of the one or more ManagedEntity cases specified by the iOCInstanceList parameter Each contains a ManagedEntity category name.

Example 68 includes the subject matter of any of the changes in any of Example 65, wherein the request to the EM includes specifying that one or more features Define a thresholdInfoList parameter of the new threshold of measurementTypes.

Example 69 includes the subject matter of any of the changes in any of Examples 63-64, wherein the request to the EM is the request to the EM for deletion, and the request to the EM includes a statement that it is intended to be A monitor ID (monitorId) parameter of a ThresholdMonitor to stop and remove.

Example 70 includes the subject matter of any of the changes in any of Examples 63-64, wherein the request to the EM is the request to the EM for listing, and the request to the EM includes a statement that it is to be A monitor ID list (monitorIdList) parameter of ThresholdMonitors of the list.

Example 71 is a device configured to be used inside an element manager (EM), which includes: a component for storing instructions; and a component for processing that is configured to execute the instructions to: The network manager (NM) receives a first request, where the first request from the NM is to generate a new threshold to monitor the virtualized resource (VR) efficiency of a virtualized network function (VNF) A first request from the NM of the test (PM) to delete an existing threshold to monitor the VNF-related VR PM. A first request from the NM to monitor the VNF, or to list the threshold identifiers identified by a list The threshold value of the NM is a first request; a second request is sent to a VNF Manager (VNFM), where the second request to the VNFM is: responding to the first request from the NM for The first request generated from the NM is used to generate the new threshold to monitor the VNF related A second request from the VR PM to the VNFM in response to the first request from the NM to delete the first request from the NM to delete the existing threshold to monitor the VNF related VR PM A second request of the VNFM, or in response to the first request from the NM to list the first request from the NM to list the thresholds identified by the threshold identifier of the list A second request of the VNFM; receiving a first response from the VNFM, wherein the first response from the VNFM includes: responding to the second request to the VNFM to generate the second request to the VNFM One or more identifiers of one or more thresholds are requested to be generated, and in response to the second request to the VNFM, one or more of the second request to the VNFM is used to delete one or more thresholds The identifier is deleted, or in response to the second request to the VNFM, the second request to the VNFM is used to list the details of one or more thresholds; and a second response is sent to the NM, Wherein the second response instruction to the NM: in response to the one or more identifiers containing the one or more thresholds in the first response from the VNFM being generated, indicating the new threshold used to generate the A result of the first request in response to the first response from the VNFM containing the one or more identifiers of the one or more thresholds being deleted and indicating the first request to delete the existing threshold A result, or in response to the first response from the VNFM containing the details of one or more thresholds, indicating the details of the one or more thresholds.

Example 72 includes the subject matter of any change in any of Example 71, wherein the component for processing is further configured to execute the instructions to: receive a notification from a VNF manager (VNFM) to the The previous threshold of the VNF-related VR PM has crossed; by adding a VNF-related VR performance alarm to an alarm list, it is determined to generate a performance alarm; and a VNF-related VR performance alarm notification is sent to the NM.

Example 73 includes the subject matter of any change in any one of Examples 71-72, wherein the first request from the NM is the first request from the NM to be generated and the second request to the VNFM is for To generate the second request to the VNFM.

Example 74 includes the subject matter of any variation of any of Example 73, wherein the second request to the VNFM includes a sourceSelector parameter specifying one or more measurement types.

Example 75 includes the subject matter of any change in any of Example 73, wherein the second request to the VNFM includes a PerformanceMetric parameter, a thresholdType parameter, and a thresholdDetails parameter, which is generated for monitoring contained in the sourceSelector parameter The new threshold for the one or more measurement types.

Example 76 includes the subject matter of any change in any of Example 73, wherein the first response from the VNFM includes a threshold ID parameter indicating an identifier of the new threshold that has been generated.

Example 77 includes the subject matter of any change in any of Example 73, wherein the second response to the NM includes a monitor specifying a unique identifier of a ThresholdMonitor associated with the new threshold. The monitorId parameter includes a status parameter with a value of "Success".

Example 78 includes the subject matter of any change in any of Examples 71-72, wherein the first request from the NM is the first request from the NM for deletion and the second request to the VNFM is for In order to delete the second request to the VNFM, and the second response to the NM, a status parameter having one of the values of "Success", "Failure", or "PartialSuccess" is included.

Example 79 includes the subject matter of any of the changes in any of Examples 71-72, wherein the first request from the NM is the first request from the NM and the second request to the VNFM is used to list The list of the second request to the VNFM and the second response to the NM includes a monitor InfoList parameter that includes return information corresponding to ThresholdMonitors matching the input standard.

Example 80 includes the subject matter of any change in any one of Examples 73-74, wherein the second request to the VNFM includes a PerformanceMetric parameter, a thresholdType parameter, and a thresholdDetails parameter, which is generated for monitoring in the sourceSelector parameter The new threshold of the one or more measurement types specified in.

Example 81 includes the subject matter of any change in any one of Examples 73-74 or 80, wherein the first response from the VNFM includes Shows a threshold ID (thresholdId) parameter of an identifier of the new threshold that has been generated.

Example 82 is a device configured to be used in a virtualized network function (VNF) manager (VNFM), which includes: a component for storing instructions; and a component for processing that is configured to execute The commands are: receiving a request from a component manager (EM), where the request from the EM is: to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) A request from the EM for a performance measurement (PM) to delete an existing threshold to monitor the VNF-related VR PM. A request from the EM for a PM, or to list the thresholds identified by a list of threshold identifiers A request from the EM; and send a response to the EM, where the response indication to the EM: in response to the request from the EM, the request from the EM indicates a threshold value One or more identifiers are generated in response to the request from the EM to indicate that one or more of the multiple thresholds is deleted from the request from the EM, or in response to the request from the EM The request of the EM is used to list the details of the multiple thresholds from the request of the EM.

Example 83 includes the subject matter of any change in any of Example 82, wherein the means for processing is further configured to execute the instructions to detect that the VNF-related VR PM has crossed a first threshold.

Example 84 includes the subject matter of any change in any of Examples 83, wherein the means for processing is further configured to execute The instructions are used to send a notification to the EM that the first threshold has crossed the VNF-related VR PM.

Instance 85 includes the subject matter of any changes in any of instances 84, wherein the notification includes an objectInstanceId parameter that identifies the first threshold.

Example 86 includes the subject matter of any change in any of Example 84, wherein the notification includes a thresholdId parameter, a crossingDirection parameter, a performanceMetric parameter, and a performanceValue parameter, which indicate that the first threshold has been crossed.

Example 87 includes the subject matter of any change in any of Example 83, wherein the component for processing is further configured to execute the instructions to be based on a received from a virtualized infrastructure manager (VIM) Threshold crossing notification and detecting that the VR PM has crossed the first threshold.

Example 88 includes the subject matter of any change in any of Examples 82-87, wherein the processing component is further configured to execute the instructions to: send an additional request to a virtualized infrastructure manager (VIM), where the additional request instruction to the VIM responds to the request from the EM for the request generated from the EM and the instruction to generate the request from the EM responds to the request from the EM The request is the request from the EM to delete the request from the EM to indicate the request to delete, or the request from the EM to indicate the request from the EM to list The request from the EM in a list; and an additional response is received from the virtualized infrastructure manager (VIM), wherein the response to the additional request instruction to the VIM is used to generate from the EM The request is a result of the request from the EM that is generated from the additional response of the VIM, and the request from the EM is in response to the additional request to the VIM to be deleted and the request from the EM is to be deleted The request from the EM, or the request from the EM in response to the additional request instruction to the VIM to generate the request from the EM to indicate the request from the EM to list.

Example 89 includes the subject matter of any change in any of Examples 82-87, where the request from the EM is the request from the EM for generation, and the response to the EM includes an indication that has been generated A threshold ID (thresholdId) parameter of one of the new threshold identifiers.

Example 90 is a device configured to be used inside a virtualized infrastructure manager (VIM), which includes: a component for storing instructions; and a component for processing that is configured to execute the instructions to : Process a request from a virtualized network function (VNF) manager (VNFM), where the request from the VNFM is related to a virtualized network function (VNF) related virtualized resource (VR) efficiency measurement ( PM) is associated with threshold monitoring, where the request from the VNFM is a request from the VNFM to generate a new threshold to monitor the VNF-related VR PM to delete a set of the VNF-related VR PM that it monitors One of the existing thresholds is requested from one of the VNFMs of the indicated existing thresholds, or used to list one of the existing thresholds of the set indicated by a list of threshold identifiers or one of the existing thresholds from the VNFM Request; in response to the request from the VNFM, one of the following: in response to the request from the VNFM Used to generate the request from the VNFM to generate the new threshold to monitor the VNF-related VR PM, in response to the request from the VNFM to delete the request from the VNFM to delete the set of existing thresholds The indicated existing threshold, or in response to the request from the VNFM for the list of the request from the VNFM to generate a list of existing thresholds for monitoring the second set of VR PMs related to the VNF; and sending; A response to the VNFM in response to the result of the request from the VNFM that generated the new threshold indication for generation, and a response to the result of the request from the VNFM that the indicated threshold indication was used to delete, or In response to generating the list indicating the result of the request from the VNFM to list.

Example 91 includes the subject matter of any change in any of Examples 90, wherein the means for processing is further configured to execute the instructions for sending related to one of the existing thresholds of the set that has crossed the existing threshold A threshold crossing notification of the association is sent to the VNFM, wherein the threshold crossing notification indication is used for an associated identifier that has crossed one of the existing thresholds.

Example 92 includes the subject matter of any change in any of Example 91, wherein the means for processing is further configured to execute the instructions to detect a threshold crossing associated with the crossed existing threshold, and The one or more processors are configured to generate the threshold crossing notification in response to the threshold crossing.

Example 93 includes the subject matter of any change in any of Example 91, wherein the component for processing is further configured to execute the instructions for receiving from a network function virtualization infrastructure (NFVI) An additional threshold crossing notification and the one or more processors are configured to generate the threshold crossing notification in response to the additional threshold crossing notification received from the NFVI.

Example 94 is a device configured to be used inside a network manager (NM), which includes: a memory; and one or more processors configured to: select a virtualized network function (VNF) a threshold monitoring operation of related virtualized resource (VR) performance energy measurement (PM), wherein the selected threshold monitoring operation is the generation of a new threshold, the deletion of one of the existing thresholds, or one or more One of a list of existing thresholds; sending a request to a component manager (EM) to perform the selected threshold monitoring operation; and receiving a response from the EM indicating a result of the selected threshold monitoring operation .

Example 95 includes the subject matter of any variation of any of Examples 94, wherein the one or more processors are further configured to receive a VNF-related VR performance alert from the EM.

Example 96 is a device configured to be used inside a component manager (EM), which includes: a memory; and one or more processors configured with: from a network manager (NM) Receive a first request to perform a specified threshold monitoring operation for linking a virtualized network function (VNF) related virtualized resource (VR) efficiency measurement (PM), wherein the specified threshold monitoring operation is one of a new threshold Generate, delete one of the existing thresholds, or one of the list of one or more existing thresholds; send a second request to a VNF manager (VNFM) to perform the specified threshold monitoring operation; receive a threshold from the VNFM The first response is that it instructs the specified threshold monitoring operation Make a result; and send a second response to the NM indicating a result of the specified threshold monitoring operation.

Example 97 includes the subject matter of any change in any of Examples 96, wherein the one or more processors are further configured to: receive a notification from a VNF manager (VNFM) that a threshold has been set in the VNF Related VR PM crosses; by adding a VNF-related VR performance alarm to an alarm list, it is determined to generate a performance alarm; and a VNF-related VR performance alarm notification is sent to the NM.

Example 98 is a device configured to be used inside a component manager (EM), which includes: a memory; and one or more processors configured to: receive from a component manager (EM) A first request is used to perform a specified threshold monitoring operation for linking a VNF-related virtualized resource (VR) performance energy measurement (PM), wherein the specified threshold monitoring operation is generated by one of a new threshold and deleted by one of the existing thresholds , Or one of a list of one or more existing thresholds; sending a second request to a virtualized infrastructure manager (VIM) to perform the specified threshold monitoring operation; receiving a first response from the VIM to its instruction A result of the designated threshold monitoring operation; and sending a second response to the EM indicating a result of the designated threshold monitoring operation.

Example 99 includes the subject matter of any change in any of Example 98, wherein the one or more processors are further configured to detect that the VNF-related VR PM has crossed a first threshold.

Example 100 is a device configured to be used inside a virtualized infrastructure manager (VIM), which includes: a memory; And one or more processors are configured to: receive a request from a virtualized network function (VNF) manager (VNFM) to connect a VNF-related virtualized resource (VR) efficiency measurement (PM) A designated threshold monitoring operation, wherein the designated threshold monitoring operation is a generation of a new threshold, a deletion of an existing threshold, or one of a list of one or more existing thresholds; performing the designated threshold monitoring operation; and sending A response to the VNFM indicates the result of the specified threshold monitoring operation.

Example 101 includes the subject matter of any change in any of Example 100, where the one or more processors are further configured to send to the VNFM and one of the set of existing thresholds has crossed the existing thresholds. A threshold crossing notification of, wherein the threshold crossing notification indicates an associated identifier for the existing threshold that has been crossed.

The above description of the exemplary embodiments disclosed herein, including those described in the abstract description, is by no means intended to be exclusive or to limit the disclosed embodiments to the precise form disclosed. Although specific embodiments and examples are described herein for illustrative purposes, those skilled in the art will understand that various modifications deemed to fall within the scope of these embodiments and examples are possible.

In this regard, although when applicable, the subject matter disclosed herein has been described in connection with various embodiments and corresponding drawings, but it must be understood that other similar embodiments can be used or modifications and additions can be made to the described embodiments for this purpose The same, similar, substitute, or substitute function of the disclosed subject matter does not deviate from its scope. Therefore, the subject matter disclosed in this article should not be limited to this Any single embodiment described in the text must be interpreted in terms of scope and scope based on the scope of the patent application attached below.

Special consideration is given to the various functions performed by the components or structures (assembly, device, circuit, system, etc.) described above. Unless otherwise indicated, the terms used to describe these components (including the “component”) are intended to correspond Any component or structure that performs a specific function of the component (for example, it is functionally equivalent), even if it is not structurally equivalent to the disclosed structure performing the function in the specific embodiment exemplified herein. In addition, although a specific feature has been disclosed for only one of the several embodiments, such feature can be combined with one or more other features of other embodiments as desired and excellent for any given or specific application

310‧‧‧Network Manager (NM)

320‧‧‧Network Function Virtualization (NFV) Planner (NFVO)

330‧‧‧Network Component Manager (EM)

340‧‧‧VNF Manager (VNFM)

350‧‧‧Network Function Virtualization (NFV) Infrastructure (NFVI)

360‧‧‧Virtualized Infrastructure Manager (VIM)

370 ₁ 、370 ₂ ‧‧‧Virtualized Network Function (VNF)

Claims (29)

A device configured to be used inside a network manager (NM), which includes: a memory; and one or more processors, which are configured to: make a decision, wherein the decision is used A decision to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) efficiency measurement (PM) is to delete a first existing threshold to monitor a VNF-related VR PM To determine, or to obtain detailed information of one or more existing thresholds to monitor a decision of the VNF related VR PM; send a request to a component manager (EM), where the request to the EM is: respond to the Decide to generate the new threshold to monitor the VNF-related VR PM request to the EM in response to the decision to delete the decision to delete the existing threshold to monitor the VNF-related VR PM's request to one of the EMs, or a request to the EM that lists thresholds identified by a list of threshold identifiers in response to the decision to obtain the decision; and receiving a response from the EM , Wherein the response from the EM is: in response to the request to the EM to generate the request to the EM to indicate a threshold to produce a result, the response from the EM to the EM The request is the request to the EM to delete and indicates a threshold to delete a result from the A response from the EM, or a response from the EM in which the request to the EM indicates the details of the one or more existing thresholds in response to the request to the EM for listing. Such as the equipment of claim 1, wherein the one or more processors are further configured to receive VNF-related VR performance alarm notifications from one of the EMs. Such as the equipment of claim 1, wherein the request to the EM is the request to the EM to be generated. Such as the equipment of claim 3, where the request to the EM includes one or more destination networks (DN) of one or more Managed Entity cases whose measurementTypes (measurement types) are to be monitored An information object category (IOC) case list (iOCInstanceList) parameter. Such as the device of claim 4, where the request to the EM includes an IOC name (iOCName) parameter specifying a ManagedEntity category name for each of the one or more ManagedEntity cases specified by the iOCInstanceList parameter . Such as the device of claim 3, wherein the request to the EM includes a thresholdInfoList parameter specifying the new threshold for one or more specific measurementTypes. For example, the device of claim 1, where the request to the EM is the request to the EM for deletion, and the request to the EM includes a ThresholdMonitor to be stopped and removed A monitor ID (monitorId) parameter. For example, the equipment of request item 1, wherein the request to the EM is the request to the EM for listing, and the request to the EM includes a monitor ID list (monitorIdList) specifying ThresholdMonitors to be listed )parameter. A device configured to be used inside a component manager (EM), comprising: a memory; and one or more processors, which are configured to: receive data from a network manager (NM) A first request, wherein the first request from the NM is: to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) efficiency measurement (PM) from the NM A first request to delete an existing threshold to monitor the VNF-related VR PM from the NM, or to list the thresholds identified by a list of threshold identifiers from the NM The first request; send a second request to a VNF manager (VNFM), where the second request to the VNFM is: responding to the first request from the NM to generate the first request from the NM A request for generating the new threshold to monitor the VNF-related VR PM's second request to the VNFM, and responding to the first request from the NM to delete the first request from the NM Used to delete the existing threshold to monitor the VNF-related VR PM's second request to the VNFM, or to respond to the first request from the NM to list the first request from the NM List by the A second request to the VNFM of the thresholds identified by the list of threshold identifiers; receiving a first response from the VNFM, wherein the first response from the VNFM includes: responding to the first response to the VNFM The second request is the second request to the VNFM to be generated, one or more identifiers of one or more thresholds are generated, and in response to the second request to the VNFM, the second request to the VNFM is to be deleted The second request, one or more of one or more of the thresholds is deleted, or the response to the second request to the VNFM is one or more of the second request to the VNFM for listing The details of the threshold; and sending a second response to the NM, where the second response instruction to the NM: response to the one or more identifiers containing the one or more thresholds is generated from the VNFM The first response threshold is used to generate a result of the first request of the new threshold, in response to the first request from the VNFM for which the one or more identifiers including the one or more thresholds are deleted A response threshold is used to delete a result of the first request of the existing threshold, or in response to the one or more thresholds from the first response threshold of the VNFM that includes the details of one or more thresholds Of these details. Such as the device of claim 9, wherein the one or more processors are further configured to: receive a notification from a VNF manager (VNFM) that a threshold on the VNF-related VR PM has been crossed; By adding a VNF-related VR performance alarm to an alarm list, A performance alarm is generated; and a VNF-related VR performance alarm notification is sent to the NM. For example, the device of claim 9, wherein the first request from the NM is the first request from the NM for generation, and the second request to the VNFM is the first request to the VNFM for generation Two requests. Such as the device of claim 11, where the second request to the VNFM includes a sourceSelector parameter specifying one or more measurement types. For example, the device of claim 11, where the second request to the VNFM includes a PerformanceMetric (efficiency energy meter) parameter, a thresholdType (threshold type) parameter, and a thresholdDetails (threshold details) parameter, which are generated for monitoring in The new threshold of the one or more measurement types specified in the sourceSelector parameter. Such as the device of claim 11, wherein the first response from the VNFM includes a threshold ID parameter indicating an identifier of the new threshold that has been generated. For example, the device of claim 11, where the second response to the NM includes a monitor ID parameter specifying a unique identifier of a ThresholdMonitor associated with the new threshold, and includes A status parameter with a value of "Success". Such as the device of claim 9, wherein the first request from the NM is the first request from the NM to delete, and to the The second request of the VNFM is the second request to the VNFM used to delete, and the second response to the NM includes "Success", "Failure", or "PartialSuccess" (Partially successful) A status parameter of one value. Such as the device of claim 9, wherein the first request from the NM is the first request from the NM for listing, and the second request to the VNFM is the first request to the VNFM for listing Two requests, and the second response to the NM includes a monitor InfoList parameter, and the monitor InfoList parameter includes return information corresponding to ThresholdMonitors matching input standards. A device configured to be used inside a virtualized network function (VNF) manager (VNFM), which includes: a memory; and one or more processors, which are configured to: receive from a component A request from the manager (EM), where the request from the EM is: to generate a new threshold to monitor a virtualized network function (VNF) related virtualized resource (VR) efficiency measurement (PM) from A request from the EM to delete an existing threshold to monitor the VNF-related VR PM request from the EM, or to list the threshold identified by a threshold identifier list from the EM; And send a response to the EM, where the response instruction to the EM: the response to the request from the EM is used to generate the For the request of EM, one or more identifiers of one or more thresholds are generated, and the response to the request from the EM is to delete the request from the EM, one or more of the one or more thresholds The identifier is deleted, or the response to the request from the EM is used to list the details of one or more thresholds of the request from the EM. Such as the device of claim 18, wherein the one or more processors are further configured to detect that the VNF-related VR PM has crossed a first threshold. Such as the device of claim 19, wherein the one or more processors are further configured to send a notification to the EM that the first threshold has been crossed on the VNF-related VR PM. For example, the device of claim 20, wherein the notification includes a target instance identifier (objectInstanceId) parameter identifying the first threshold. For example, the device of claim 20, where the notification includes a thresholdId parameter, a crossingDirection (crossing direction) parameter, a performanceMetric (efficiency energy meter) parameter, and a performanceValue (performance value) parameter, which indicates that the first threshold has been crossed . Such as the device of claim 19, wherein the one or more processors are further configured to detect that the VR PM has crossed the threshold based on a threshold crossing notification received from a virtualized infrastructure manager (VIM) The first existing threshold. Such as the device of claim 18, wherein the one or more processors are further configured with: Send an additional request to a virtualized infrastructure manager (VIM), where the additional request indication to the VIM in response to the request from the EM is used to generate the request from the EM to generate from The request of the EM indicates that the response to the request from the EM is to delete the request from the EM to delete the request from the EM, or the instruction to respond to the request from the EM is for use List the request from the EM to list the request from the EM; and receive an additional response from the Virtual Infrastructure Manager (VIM), where the additional response from the VIM responds to The additional request indication of the VIM used to generate the request from the EM and the indication used to generate a result of the request from the EM, in response to the additional request indication to the VIM from the EM The request indicates the request from the EM to delete, or in response to the request from the EM that the additional request indicates to generate the request from the EM to indicate the request to list. For example, the device of request item 18, wherein the request from the EM is the request from the EM to be generated, and the response to the EM includes a threshold indicating an identifier of the new threshold that has been generated Identity (thresholdId) parameter. A device configured to be used inside a virtualized infrastructure manager (VIM), which includes: a memory; and one or more processors, which are configured to: process functions from a virtualized network (VNF) Manager (VNFM) is a request, wherein the request from the VNFM is associated with a virtualized network function (VNF) related virtualized resource (VR) efficiency measurement (PM) threshold monitoring, wherein the VNFM from the VNFM The request is a request from the VNFM used to generate a new threshold to monitor the VNF-related VR PM, and is used to delete one of the existing thresholds in a set of the VNF-related VR PM. The indicated existing threshold is from the VNFM A request, or a request from the VNFM to list one or more existing thresholds of the set indicated by a list of threshold identifiers; in response to the request from the VNFM, perform the following One of: in response to the request from the VNFM to generate the request from the VNFM to generate the new threshold to monitor the VNF-related VR PM, in response to the request from the VNFM to delete The request of the VNFM deletes the indicated existing threshold in the set of existing thresholds, or responds to the request from the VNFM for the list of the request from the VNFM to generate monitoring of the VNF related VR PM A list of the existing thresholds of the second set; and sending a response to the VNFM, the response indicating the result of the request from the VNFM used to generate the new threshold, indicating that the response is to delete the indicated The threshold is used to delete the result of the request from the VNFM, or indicates the result of the request from the VNFM used to generate the list. Such as the device of claim 26, wherein the one or more processors are further configured to send a threshold crossing notification associated with an existing threshold that one of the set of existing thresholds has crossed to the VNFM, wherein The threshold crossing notification indicates an identifier associated with one of the existing thresholds that has been crossed. Such as the device of claim 27, wherein the one or more processors are further configured to detect the crossing of a threshold associated with the existing threshold that has been crossed, and the one or more processors are The configuration is configured to generate the threshold crossing notification in response to the threshold crossing. Such as the device of claim 27, in which the one or more processors are further configured to receive notifications from a network function virtualization infrastructure (NFVI) that an additional threshold has passed, and the one or more The processor is configured to generate the threshold crossing notification in response to the additional threshold crossing notification received from the NFVI.

Images