CN105103125B - The acquisition methods and NFV devices of clock interrupt signal - Google Patents

Abstract

The present invention provides a clock interruption signal acquisition method and NFV functional entity, including: the NFV functional entity determines the clock interruption accuracy requirement of the VNF according to the VNFD description information, and then, the NFV functional entity determines the hardware clock for the VNF according to the clock interruption accuracy requirement address, and finally send the determined hardware clock address to the VNF, and the VNF can access the hardware clock according to the obtained hardware clock address and obtain a clock interrupt signal. The technical solution of the present invention does not need to call the underlying hardware clock interrupt signal through the virtual machine to generate the guest operating system software clock interrupt signal of the virtual machine, and then provide the software clock interrupt signal to the VNF for the clock signal transmission process of the VNF execution program scheduling, thereby avoiding It reduces the delay and delay jitter of the clock signal, ensures the timeliness of interrupt signal execution, and ensures that the program is scheduled in time.

Description

Method for acquiring clock interrupt signal and NFV device

technical field

The present invention relates to communication technology, in particular to a method for acquiring a clock interruption signal and an NFV functional entity.

Background technique

With the rapid development of smart terminals and data cards/notebook computers supporting the 3rd-Generation (3G for short), mobile Internet services have grown exponentially in the past few years. In order to cope with the ever-increasing data traffic, operators have proposed the concept of Network Functions Virtualization (NFV for short). Various network elements run in the virtual machine in the form of software. Using this architecture, operators will maintain a unified virtualization platform, and different network elements will run on the virtualization platform in the form of virtual machines, and new network elements or network element upgrades will be reflected as new virtual machines import or change of software version in the virtual machine. At the same time, since the virtualization technology shields the differences of the underlying physical platforms, the problem of sharing hardware resources across manufacturers will be easily solved. In addition, by utilizing features such as virtual machine dynamic migration and dynamic generation, combined with intelligent management of the virtualization platform, the dynamic expansion and reduction of network elements can be realized according to the change of business volume, so as to realize more efficient utilization of hardware resources.

In the prior art, in the virtual environment of NFV, the clock interrupt signal generated by the underlying hardware needs to be provided to the virtual machine, and the virtual machine simulates the software clock interrupt signal to transmit it to the virtualized network function (Virtualized Network Function, referred to as VNF). In one process, the clock signal obtained by the virtual network function is delayed because the software clock simulation program of the virtual machine cannot be scheduled in time, so that the program cannot be scheduled in time. Especially for many applications or network functions in the wireless network that require high real-time and clock accuracy, the delay of the clock signal will affect the processing of services by the network function and reduce network performance.

Contents of the invention

Embodiments of the present invention provide a method for acquiring a clock interrupt signal and an NFV functional entity, which have solved the delay and delay jitter of the clock signal caused by calling the underlying hardware clock interrupt signal.

The first aspect of the present invention provides a method for acquiring a clock interrupt signal, including:

The network function virtualization NFV functional entity determines the clock interruption precision requirement of the virtual network function VNF according to the description information in the virtual network function requirement description file VNFD;

The NFV functional entity determines a hardware clock address for the VNF according to the clock interruption precision requirement;

The NFV functional entity sends the address of the hardware clock to the VNF, so that the VNF accesses the hardware clock according to the address of the hardware clock to obtain a clock interrupt signal.

In a first possible implementation manner of the first aspect, the NFV functional entity is a network function virtualization orchestrator NFVO or a virtual network function manager VNFM.

With reference to the first possible implementation of the first aspect, in the second possible implementation of the first aspect, before the NFV functional entity determines the hardware clock address for the VNF according to the clock interruption accuracy requirement, further includes :

The NFV functional entity determines whether the VNF needs to directly access the hardware clock according to the clock interruption precision requirement of the VNF;

If it is determined that the NFVO or VNFM needs to directly access a hardware clock, the NFVO or VNFM determines a hardware clock address for the VNF.

With reference to the first possible implementation of the first aspect, in the third possible implementation of the first aspect, the NFV functional entity determines a hardware clock address for the VNF according to the clock interruption accuracy requirements of the VNF, specifically including:

The NFVO or VNFM sends a query request to the clock address manager, and the query request carries the identification information of the VNF and the identification information of the physical device mapped by the VNF;

The NFVO or VNFM receives the hardware clock address returned by the clock address manager.

With reference to the third possible implementation of the first aspect, in the fourth possible implementation of the first aspect, after the NFV functional entity receives the hardware clock address returned by the clock address manager, it further includes:

The NFVO or VNFM receives the access cycle and access duration of the VNF to the hardware clock address returned by the clock address manager.

With reference to the first possible implementation of the first aspect, in a fifth possible implementation of the first aspect, the NFV functional entity stores hardware clock information, and the NFV functional entity, according to the clock interruption accuracy requirements of the VNF, Determine the hardware clock address for the VNF, specifically including:

The NFVO determines the address of the hardware clock that the VNF can directly access according to the stored information of the hardware clock.

With reference to the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner of the first aspect, the NFV functional entity determines, according to the stored information of the hardware clock, the After the hardware clock address, also include:

The NFVO determines the access cycle and access duration of the VNF to the hardware clock address.

With reference to the fourth or sixth possible implementation of the first aspect, in the seventh possible implementation of the first aspect, after the NFV functional entity sends the address of the hardware clock to the VNF, further includes :

The NFVO sends the VNF's access period and access duration to the hardware clock address to the VNF.

With reference to the first possible implementation of the first aspect, in the eighth possible implementation of the first aspect, before the NFV functional entity determines the hardware clock address for the VNF according to the clock interruption precision requirement, further includes :

The NFVO determines a virtualized infrastructure manager VIM that satisfies the resources required by the VNF according to the clock interruption accuracy requirements of the VNF;

The NFVO sends a resource reservation request to the VIM;

The NFVO receives the resource reservation result returned by the VIM, and the resource reservation result carries the identifier of the physical device.

With reference to the eighth possible implementation manner of the first aspect, in the ninth possible implementation manner of the first aspect, the NFVO receives the resource reservation result returned by the VIM, and the resource reservation result carries the information of the physical device After identification, also include:

The VNFM requests the VIM to create and start a virtual machine.

With reference to the eighth or ninth possible implementation manner of the first aspect, in a tenth possible implementation manner of the first aspect, the resource reservation result includes: the hardware clock address;

The NFV functional entity determines a hardware clock address for the VNF, specifically including:

The NFVO acquires the hardware clock address from the resource reservation result.

With reference to the tenth possible implementation of the first aspect, in the eleventh possible implementation of the first aspect, the resource reservation result further includes: the VNF's access period and access to the hardware clock address duration.

With reference to the tenth possible implementation manner of the first aspect, in the twelfth possible implementation manner of the first aspect, after the NFV functional entity acquires the hardware clock address from the resource reservation result, further include:

The NFVO determines the access cycle and access duration of the VNF to the hardware clock address.

The second aspect of the present invention provides a network function virtualization NFV functional entity, including:

The first determination module is configured to determine the clock interruption precision requirement of the VNF according to the VNFD description information;

The second determination module is configured to determine a hardware clock address for the VNF according to the clock interruption precision requirement;

A sending module, configured to send the address of the hardware clock to the VNF, so that the VNF accesses the hardware clock according to the address of the hardware clock to obtain a clock interrupt signal.

In a second possible implementation manner of the second aspect, the NFV functional entity is NFVO or VNFM.

In combination with the first possible implementation of the second aspect, the second possible implementation of the second aspect further includes:

The third determination module is configured to determine whether the VNF needs to directly access the hardware clock according to the clock interruption precision requirement of the VNF before the second determination module determines the hardware clock address for the VNF according to the clock interruption precision requirement. ;

The second determination module is further configured to determine a hardware clock address for the VNF if it is determined that the NFVO or VNFM needs to directly access the hardware clock.

With reference to the first possible implementation of the second aspect, in a third possible implementation of the second aspect, the sending module is specifically configured to:

Sending a query request to the clock address manager, where the query request carries the identification information of the VNF and the identification information of the physical device mapped by the VNF;

The NFV functional entity further includes: a first receiving module, configured to receive the hardware clock address returned by the clock address manager.

With reference to the third possible implementation of the second aspect, in a fourth possible implementation of the second aspect, the first receiving module is further configured to receive the clock address manager returned by the second determining module After receiving the hardware clock address, the access period and access duration of the VNF to the hardware clock address returned by the clock address manager are received.

With reference to the first possible implementation of the second aspect, in the fifth possible implementation of the second aspect, the NFV functional entity is the NFVO, and the NFVO further includes:

The storage module is used for storing the information of the hardware clock;

The second determining module specifically: according to the stored information of the hardware clock, determine the address of the hardware clock that the VNF can directly access.

With reference to the fifth possible implementation of the second aspect, in the sixth possible implementation of the second aspect, the NFV functional entity is the NFVO, and the NFVO further includes:

The fourth determination module is configured to determine the hardware clock address that the NFV can directly access according to the second determination module, and then determine the access cycle and access duration of the VNF to the hardware clock address.

With reference to the fourth or sixth possible implementation of the second aspect, in the seventh possible implementation of the second aspect, the NFV functional entity is the NFVO, and the sending module is further configured to After sending the address of the hardware clock to the VNF, send the access period and access duration of the VNF to the address of the hardware clock to the VNF.

With reference to the first possible implementation of the second aspect, in the eighth possible implementation of the second aspect, the NFV functional entity is the NFVO, and the NFVO further includes:

The fifth determination module is configured to determine a VIM that meets the resource requirements of the VNF according to the clock interruption accuracy requirements of the VNF before the second determination module determines the hardware clock address for the VNF according to the clock interruption accuracy requirements;

The sending module is further configured to: send a resource reservation request to the VIM;

A second receiving module is also included, configured to receive the resource reservation result returned by the VIM, where the resource reservation result carries the identifier of the physical device.

With reference to the eighth possible implementation of the second aspect, in the ninth possible implementation of the second aspect, the NFV functional entity is the VNFM, and the VNFM further includes: a request module configured to After the fifth determining module receives the resource reservation result returned by the VIM, where the resource reservation result carries the identifier of the physical device, it requests the VIM to create and start a virtual machine.

With reference to the eighth or ninth possible implementation of the second aspect, in the tenth possible implementation of the second aspect, the NFV functional entity is the NFVO, and the resource reservation result includes: the hardware clock address;

The second determination module is specifically configured to: obtain the hardware clock address from the resource reservation result.

With reference to the tenth possible implementation of the second aspect, in the eleventh possible implementation of the second aspect, the resource reservation result further includes: the VNF's access cycle and access to the hardware clock address duration.

With reference to the tenth possible implementation manner of the second aspect, in the twelfth possible implementation manner of the second aspect, the NFV functional entity is the NFVO, and the NFVO further includes:

The sixth determination module is configured to determine the access cycle and access duration of the VNF to the hardware clock address after obtaining the hardware clock address from the resource reservation result according to the second determination module.

The third aspect of the present invention provides a network function virtualization NFV functional entity, including: a processor and a memory, the memory stores execution instructions, and when the acquisition system of the clock interrupt signal is running, the processor and the memory The processor executes the execution instruction so that the system for obtaining the clock interrupt signal executes the method according to any one of claims 1-13.

The embodiment of the present invention provides a method for acquiring a clock interruption signal and an NFV functional entity. The NFV functional entity determines the clock interruption accuracy requirement of the VNF according to the VNFD description information. Then, the NFV functional entity determines the hardware for the VNF according to the clock interruption accuracy requirement. clock address, and finally send the determined hardware clock address to the VNF, and the VNF can access the hardware clock according to the obtained hardware clock address and obtain a clock interrupt signal. Instead of calling the underlying hardware clock interrupt signal through the virtual machine to generate the guest operating system software clock interrupt signal of the virtual machine, and then providing the software clock interrupt signal to the VNF for the clock signal transmission process of the VNF execution program scheduling, thus avoiding the clock signal interruption Delay and delay jitter ensure the timeliness of interrupt signal execution and ensure that the program is scheduled in time.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description These are some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained according to these drawings without any creative effort.

FIG. 1 is a flowchart of a method for acquiring a clock interrupt signal provided in Embodiment 1 of the present invention;

FIG. 2 is a flowchart 1 of a method for acquiring a clock interrupt signal provided in Embodiment 2 of the present invention;

FIG. 3 is a first schematic diagram of the architecture and interface of the clock interrupt signal acquisition method provided by Embodiment 2 of the present invention;

FIG. 4 is a second schematic diagram of the architecture and interface of the clock interrupt signal acquisition method provided by Embodiment 2 of the present invention;

FIG. 5 is a third schematic diagram of the architecture and interface of the clock interrupt signal acquisition method provided by Embodiment 2 of the present invention;

FIG. 6 is a fourth schematic diagram of the structure and interface of the clock interrupt signal acquisition method provided by Embodiment 2 of the present invention;

FIG. 7 is a second flowchart of a method for acquiring a clock interrupt signal provided by Embodiment 2 of the present invention;

FIG. 8 is a flowchart of a method for acquiring a clock interrupt signal provided by Embodiment 3 of the present invention;

FIG. 9 is a first schematic diagram of the architecture and interface of the clock interrupt signal acquisition method provided by Embodiment 3 of the present invention;

FIG. 10 is a second schematic diagram of the architecture and interface of the clock interrupt signal acquisition method provided by Embodiment 3 of the present invention;

FIG. 11 is a flowchart of a method for acquiring a clock interrupt signal provided in Embodiment 4 of the present invention;

FIG. 12 is a first schematic diagram of the architecture and interface of the clock interrupt signal acquisition method provided by Embodiment 4 of the present invention;

FIG. 13 is a second schematic diagram of the architecture and interface of the clock interrupt signal acquisition method provided by Embodiment 4 of the present invention;

FIG. 14 is a first structural diagram of a network function virtualization NFV functional entity provided by Embodiment 5 of the present invention;

FIG. 15 is a second structural diagram of a network function virtualization NFV functional entity provided by Embodiment 5 of the present invention;

FIG. 16 is a third schematic structural diagram of a network function virtualization NFV functional entity provided by Embodiment 5 of the present invention;

FIG. 17 is a fourth schematic structural diagram of a network function virtualization NFV functional entity provided by Embodiment 5 of the present invention;

FIG. 18 is a fifth structural diagram of a network function virtualization NFV functional entity provided by Embodiment 5 of the present invention;

FIG. 19 is a sixth structural diagram of a network function virtualization NFV functional entity provided by Embodiment 5 of the present invention;

FIG. 20 is a schematic structural diagram VII of a network function virtualization NFV functional entity provided by Embodiment 5 of the present invention;

FIG. 21 is a schematic eighth structural diagram of a network function virtualization NFV functional entity provided by Embodiment 5 of the present invention;

FIG. 22 is a schematic diagram of a network function virtualization NFV functional entity provided by Embodiment 6 of the present invention.

detailed description

In order to make the purpose of the embodiments of the present invention: technical solutions and advantages clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

Fig. 1 is a flow chart of a method for acquiring a clock interrupt signal provided in Embodiment 1 of the present invention. As shown in Fig. 1, the method includes:

Step 101: The network function virtualization NFV functional entity determines the clock interruption accuracy requirement of the VNF according to the description information of the virtual network function requirement description file (Virtualized Network Function Descriptor, referred to as VNFD);

Wherein, the NFV functional entity may be a network function virtualized orchestrator (Network Function Virtualized Orchestrator, NFVO for short) or a virtual network function manager (Virtualized NetworkFunction Manager, VNFM for short). The information described by VNFD specifically includes the configuration of VNF deployment behavior and operation behavior. The deployment behavior includes but is not limited to the deployment environment required by the VNF, specifically refers to the VNF's network function virtualized infrastructure (Network Function Virtualized Infrastructure, NFVI for short) resources The requirements, such as the number of virtual machines, the number of virtual machine images (image), required computing resources and storage resources, etc. Operational behaviors are mainly behaviors during the VNF lifecycle management process, including but not limited to VNF topology, startup and shutdown, and functional scripts matching VNF lifecycle events, etc.

VNFD is sent to NFVO by a third-party entity during the VNF loading (on-boarding) process, and NFVO submits it to the NFV catalog, and NFVO reads VNFD from the NFV catalog when needed.

The third-party entity here may be any entity representing the VNF provider, or an entity within the management domain of the service provider.

VNF clock interruption accuracy refers to the VNF's requirements for clock interruption frequency and frequency stability.

Step 102: The NFV functional entity determines the hardware clock address for the VNF according to the clock interrupt accuracy requirement;

Specifically, the NFV functional entity can first determine whether the VNF needs to directly access the hardware clock according to the clock interrupt accuracy requirements of the VNF. If it is determined that the VNF needs to directly access the hardware clock, as a feasible implementation, NFVO or VNFM can send the clock address The manager sends a query request, which carries the identification information of the VNF and the identification information of the physical device mapped by the VNF, and then NFVO or VNFM receives the address of the hardware clock accessible to the VNF returned by the clock address manager, and the address of the hardware clock that the VNF accesses. Visit period and visit duration.

As another feasible implementation, NFVO can also store hardware clock information in advance, so that NFVO can directly determine the address of the hardware clock that the VNF can directly access based on the stored hardware clock information, and can further determine the VNF's The access cycle and access duration of the hardware clock.

Wherein, the hardware clock address manager may be a business support system/operation support system (OSS/BSS for short), NFVO, VNFM or a virtualized infrastructure manager (Virtualized Infrastructure Manager, VIM for short) etc., the present invention is not limited thereto.

Step 103: The NFV functional entity sends the address of the hardware clock to the VNF, so that the VNF accesses the hardware clock according to the address of the hardware clock to obtain a clock interrupt signal.

The NFV functional entity sends the received hardware clock address returned by the clock address manager and the hardware clock access cycle and access duration to the VNF, and then the VNF obtains the clock interrupt signal according to the received accessible hardware clock address.

According to the acquisition method of the clock interruption signal provided by the present invention, the NFV functional entity determines the clock interruption accuracy requirement of the VNF according to the VNFD description information, and then, the NFV functional entity determines the hardware clock address for the VNF according to the clock interruption accuracy requirement, and finally the determined The hardware clock address is sent to the VNF, and the VNF can access the hardware clock according to the obtained hardware clock address and obtain a clock interrupt signal. Instead of calling the underlying hardware clock interrupt signal through the virtual machine to generate the guest operating system software clock interrupt signal of the virtual machine, and then providing the software clock interrupt signal to the VNF for the clock signal transmission process of the VNF execution program scheduling, thus avoiding the clock signal interruption Delay and delay jitter ensure the timeliness of interrupt signal execution and ensure that the program is scheduled in time.

Fig. 2 is the first flow chart of the method for obtaining the clock interrupt signal provided by the second embodiment of the present invention. As shown in Fig. 2, in the implementation scenario provided by this embodiment, the clock address manager is maintained by the OSS/BSS system or the clock address server , and the NFVO sends a clock address query request to the clock address manager, the method includes:

Step 200: Add the description of the VNF's requirements for clock interruption accuracy in the VNFD. Through the VNF loading process, the third-party entity sends the VNFD to the NFVO, and the NFVO submits the VNFD to the VNF directory, so that the NFVO and VNFM can obtain the synchronization of the VNF. need.

Wherein, the third-party entity may be any entity representing the VNF provider, or an entity within the management domain of the service provider.

VNFD is a configuration template that describes VNF deployment and operation behavior, specifically including the description of VNF deployment behavior and operation behavior configuration, where deployment behavior includes but not limited to the deployment environment required by VNF, specifically refers to the VNF’s requirements for NFVI resources, such as The number of virtual machines, the number of virtual machine images (image), required computing resources and storage resources, etc. Operational behaviors are mainly behaviors during the VNF lifecycle management process, including but not limited to VNF topology, startup and shutdown, and functional scripts that match VNF lifecycle events.

Step 201: The NFVO receives the request for instantiating the VNF sent by the trigger Sender.

This request is used to instantiate a new VNF;

Wherein, the Sender may be an OSS, a network element management system (Element Management System, EMS for short), or a VNFM.

Step 202: NFVO verifies the validity of the received request for instantiating the VNF sent by the Sender;

Among them, validity refers to the legality of the VNF request, including but not limited to the legality of the Sender and the legality of the instantiation request itself. Specifically, the validity of the Sender refers to whether the Sender is authorized to send the request; the instantiation request itself The legitimacy of the request refers to whether the security parameters carried by the request can prove that the request is legal and has not been tampered with by a third party.

Step 203: The NFVO reads the VNFD from the VNF directory, including reading the VNF's requirement for clock interruption.

Step 204: NFVO generates a VNF instance item, and adds the generated instance item to the "NFV instance (NFVInstances)" database.

The VNF instance item is specifically used for the NFVO and/or VNFM to query and maintain the relevant information of the VNF instance according to the VNF instance item during the operation of the VNF instance. The relevant information of the VNF instance specifically refers to the NFVI resources used by the VNF instance, the running status and performance of the virtual machine corresponding to the VNF instance, and the like.

Step 205a: NFVO submits instantiation parameters to VNFM.

The instantiation parameters include application-related parameters and non-application-related parameters, where the application-related parameters refer to application-related parameters running on the VNF, such as the service throughput to be satisfied by the VNF and/or the virtual machine on which the VNF is deployed, Parameters such as network bandwidth; non-application-related parameters refer to configuration parameters related to VNF deployment behavior and operation behavior, specifically referring to VNF’s requirements for NFVI resources and the limitation and description of behavior during the VNF lifecycle management process. The instantiation parameters are used together with the VNFD to describe and limit the requirements of the resources for deploying the VNF and the instantiation process of the VNF.

Steps 205b-205c: The VNFM obtains the VNFD and checks the instantiation parameters, and makes some modifications to the instantiation parameters if necessary.

Specifically, when the VNF instantiation parameters preset in VNFM are inconsistent with the requirement information described in VNFD and/or the instantiation parameters submitted by NFVO to VNFM, VNFM will modify the inconsistent instantiation parameters.

In step 203, the NFVO may not be able to directly read the relevant information about the description of the clock interruption requirement added in the VNFD. In this step, the VNFM will analyze the clock interruption requirement from the VNFD and send it to the NFVO.

Step 206a: The NFVO selects a VIM that can provide the VNF with resources that meet the requirements.

The "NFVI resource (NFVI resource)" database includes the records of the capabilities of the NFVI server, specifically including the description of the resources that the NFVI server can provide, including all the resources that can be provided, the resources that have been provided, the remaining resources that are available, and the resources that have been reserved. Reserve resources etc.

NFVO selects a VIM according to the records in the "NFVI resource" database, and the capability of the NFVI server managed by the VIM can meet the requirements of the VNF. The requirements here specifically refer to the requirements described in the VNFD and the requirements defined in the instantiation parameters.

Step 206b: The NFVO sends a resource reservation request to the VIM, which includes not only the VNF's demand for computing, storage and network resources, but also the VNF's demand for clock interruption (whether the VNF needs to directly access the hardware clock device to obtain clock interruption).

Step 206c: VIM checks the status of the managed resources, and returns the resource reservation result. Among them, in addition to considering the status of computing, storage and network resources, VIM also considers the status of managed clock device resources. If the clock device has a heavy load, step 206d can be performed, that is, return a resource reservation failure indication to NFVO, and NFVO restarts Steps 200-206c are executed until a suitable VIM is selected.

Step 207a: If the VNF needs to directly access the hardware clock device to obtain the clock interrupt NFVO sends a query request to the clock address manager, the query request carries the VNF's identity number (Identity, ID for short), the ID of the mapped physical device ( may include one or more) information.

Steps 207b-207c: According to the query request, the clock address manager locally queries the address of the hardware clock that the VNF can directly access, and confirms the access rights of the VNF, and returns the result to NFVO. The result includes the address of the hardware clock, and can also include VNF access Configuration information for the period and duration of the hardware clock.

Step 208: The NFVO sends a VNF instantiation request to the VNFM, which carries the identifier of the corresponding VIM (such as Uniform Resource Locator (Uniform Resource Locator, URL, etc.) and hardware clock address and configuration information indication.

Optionally, the NFVO can also configure the period and duration of the VNF's access to the hardware clock in this step.

Steps 209a-209b: VNFM requests VIM to allocate resources for VNF.

Steps 210a-210b: VNFM requests VIM to create and start a virtual machine according to the VNFD request, including installing software packages, executing startup scripts, sending configuration data, and connecting the virtual machine to the network.

Step 211: VNFM instructs the VNF to directly access the hardware clock address, access cycle and duration.

Step 212: The VNF accesses the hardware clock according to the instruction of the VNFM, obtains the interrupt of the hardware clock, and schedules the program.

Step 213: VNFM returns the VNF instantiation result to NFVO.

Steps 214a-214b: NFVO performs resource status update according to the VNF instantiation result returned by VNFM.

Step 215: NFVO updates the "NFV Instances" and "NFVI resource" databases.

Step 216: NFVO returns the VNF instantiation result to Sender.

The clock address manager in this embodiment is maintained by the OSS/BSS system or the clock address server. Specifically, it can be maintained by the EMS in the OSS/BSS system, and the clock module and the hardware can be connected through an interface, as shown in the figure 3, the clock module can also be integrated in the hardware, as shown in Figure 4, or the clock address manager is maintained by the clock address server, where the clock module server is responsible for managing and maintaining the status and status of each clock module/device in the network address. Moreover, the clock module and the hardware may be connected through an interface, as shown in FIG. 5 , or the clock module may be integrated in the hardware, as shown in FIG. 6 .

According to the acquisition method of the clock interrupt signal provided by the embodiment of the present invention, the NFV functional entity determines the clock interrupt accuracy requirement of the VNF according to the VNFD description information, and then, the NFV functional entity determines the hardware clock address for the VNF according to the clock interrupt accuracy requirement, and finally transfers the The determined hardware clock address is sent to the VNF, and the VNF can access the hardware clock according to the obtained hardware clock address and obtain a clock interrupt signal. Instead of calling the underlying hardware clock interrupt signal through the virtual machine to generate the guest operating system software clock interrupt signal of the virtual machine, and then providing the software clock interrupt signal to the VNF for the clock signal transmission process of the VNF execution program scheduling, thus avoiding the clock signal interruption Delay and delay jitter ensure the timeliness of interrupt signal execution and ensure that the program is scheduled in time.

Fig. 7 is the second flow chart of the method for obtaining the clock interrupt signal provided by the second embodiment of the present invention. As shown in Fig. 7, in the implementation scenario provided by this embodiment, the clock address manager is maintained by the OSS/BSS system or the clock address server , and the VNFM sends a clock address query request to the clock address manager, the method includes:

Step 300: Add the description of the VNF's requirements for clock interruption accuracy in the VNFD, through the VNF loading process, the third-party entity sends the VNFD to the NFVO, and the NFVO submits the VNFD to the VNF directory, so that the NFVO and VNFM can obtain the synchronization of the VNF need.

Wherein, the third party entity may be any entity representing the VNF provider, and may also be an entity within the management domain of the service provider.

VNFD refers to a configuration template that describes VNF deployment and operation behavior, specifically including the description of VNF deployment behavior and operation behavior configuration, where deployment behavior includes but not limited to the deployment environment required by VNF, specifically refers to the VNF’s requirements for NFVI resources, Such as the number of virtual machines, the number of virtual machine images (image), required computing resources and storage resources, etc. Operational behaviors are mainly behaviors during the VNF lifecycle management process, including but not limited to VNF topology, startup and shutdown, and functional scripts that match VNF lifecycle events.

Step 301: The NFVO receives a request from the Sender to instantiate the VNF.

This request is used to instantiate a new VNF;

Among them, Sender can be OSS, EMS, VNFM.

Step 302: The NFVO verifies the validity of the VNF instantiation request sent by the Sender.

Among them, validity refers to the legality of the VNF request, including but not limited to the legality of the Sender and the legality of the instantiation request itself. Specifically, the validity of the Sender refers to whether the Sender is authorized to send the request; the instantiation request itself The legitimacy of the request refers to whether the security parameters carried by the request can prove that the request is legal and has not been tampered with by a third party.

Step 303: The NFVO reads the VNFD from the VNF directory, including reading the VNF's requirement for clock interruption.

Step 304: NFVO generates a VNF instance item, and adds the generated instance item to the "NFV Instances" database.

Wherein, the VNF instance item is specifically used for the NFVO and/or VNFM to query and maintain the relevant information of the VNF instance according to the VNF instance item during the operation of the VNF instance. The relevant information of the VNF instance specifically refers to the NFVI resources used by the VNF instance, the running status and performance of the virtual machine corresponding to the VNF instance, and the like.

Step 305a: NFVO submits instantiation parameters to VNFM.

The instantiation parameters include application-related parameters and non-application-related parameters, where the application-related parameters refer to application-related parameters running on the VNF, such as the service throughput to be satisfied by the VNF and/or the virtual machine on which the VNF is deployed Parameters such as volume and network bandwidth; non-application-related parameters refer to configuration parameters related to VNF deployment behavior and operation behavior, specifically referring to VNF’s requirements for NFVI resources and the limitation and description of behavior in the VNF life cycle management process. The instantiation parameters are used together with the VNFD to describe and limit the requirements of the resources for deploying the VNF and the instantiation process of the VNF.

Steps 305b-305c: The VNFM obtains the VNFD and checks the instantiation parameters, and modifies the instantiation parameters if necessary.

Specifically, when the VNF instantiation parameters preset in VNFM are inconsistent with the requirement information described in VNFD and/or the instantiation parameters submitted by NFVO to VNFM, VNFM will modify the inconsistent instantiation parameters.

In step 303, the NFVO may not be able to directly read the relevant information about the description of the clock interruption requirement added in the VNFD. In this step, the VNFM will analyze the clock interruption requirement from the VNFD and send it to the NFVO.

Step 306a: The NFVO selects a VIM that it believes can provide the VNF with resources meeting the requirements.

Among them, the "NFVI resource" database includes records of the capabilities of the NFVI server, specifically including resource descriptions that the NFVI server can provide, including all resources that can be provided, resources that have been provided, remaining available resources, and reserved resources Wait.

NFVO selects a VIM according to the records in the "NFVI resource" database, and the capability of the NFVI server managed by the VIM can meet the requirements of the VNF. The requirements here specifically refer to the requirements described in the VNFD and the requirements defined in the instantiation parameters.

Step 306b: The NFVO sends a resource reservation request to the VIM, which includes not only the VNF's demand for computing, storage and network resources, but also the VNF's demand for clock interruption (whether the VNF needs to directly access the hardware clock device to obtain clock interruption).

Step 306c: VIM checks the status of the managed resources, and returns the resource reservation result. Among them, in addition to considering the status of computing, storage and network resources, VIM also considers the status of managed clock device resources. If the clock device has a heavy load, step 306d can be performed, that is, return a resource reservation failure indication to NFVO, and NFVO restarts Steps 300-306c are executed until a suitable VIM is selected.

Step 307: The NFVO sends a VNF instantiation request to the VNFM, which carries the identifier (such as URL) of the corresponding VIM.

Steps 308a-308b: VNFM requests VIM to allocate resources to VNF.

Steps 309a-309b: VNFM requests VIM to create and start a virtual machine according to the VNFD request, including installing software packages, executing startup scripts, sending configuration data, and connecting the VM to the network.

Step 310a: If the VNF needs to directly access the hardware clock device to obtain the clock interrupt, the VNFM sends a query request to the clock address manager, carrying the ID of the VNF and the ID of the mapped physical device (may include one or more) information.

VNFM also needs to request the address of the clock address manager from NFVO in order to send a query request to the clock address manager;

Or in step 307, when the NFVO sends the VNF instantiation request to the VNFM, it carries the address of the clock address manager.

Steps 310b-310c: The clock address manager locally queries the address of the hardware clock that the VNF can directly access according to the request, and confirms the access rights of the VNF, and returns the result to the VNFM. The result includes the address of the hardware clock, and can also include the VNF access hardware Configuration information for the period and duration of the clock.

Step 311: VNFM instructs the VNF to directly access the hardware clock address, access cycle and duration.

Optionally, the VNFM can also configure the period and duration of the VNF's access to the hardware clock in this step.

Step 312: The VNF accesses the hardware clock according to the instruction of the VNFM, obtains the interrupt of the hardware clock, and schedules the program.

Step 313: VNFM returns the VNF instantiation result to NFVO.

Steps 314a-314b: NFVO performs resource status update according to the VNF instantiation result returned by VNFM.

Step 315: NFVO updates the "NFV Instances" and "NFVI resource" databases.

Step 316: NFVO returns the VNF instantiation result to Sender.

The clock address manager in this embodiment is maintained by the OSS/BSS system or the clock address server. Specifically, it can be maintained by the EMS in the OSS/BSS system, and the clock module and the hardware can be connected through an interface, as shown in the figure 3, the clock module can also be integrated in the hardware, as shown in Figure 4, or the clock address manager is maintained by the clock address server, where the clock module server is responsible for managing and maintaining the status and status of each clock module/device in the network address. Moreover, the clock module and the hardware may be connected through an interface, as shown in FIG. 5 , or the clock module may be integrated in the hardware, as shown in FIG. 6 .

According to the acquisition method of the clock interrupt signal provided by the embodiment of the present invention, the NFV functional entity determines the clock interrupt accuracy requirement of the VNF according to the VNFD description information, and then, the NFV functional entity determines the hardware clock address for the VNF according to the clock interrupt accuracy requirement, and finally transfers the The determined hardware clock address is sent to the VNF, and the VNF can access the hardware clock according to the obtained hardware clock address and obtain a clock interrupt signal. Instead of calling the underlying hardware clock interrupt signal through the virtual machine to generate the guest operating system software clock interrupt signal of the virtual machine, and then providing the software clock interrupt signal to the VNF for the clock signal transmission process of the VNF execution program scheduling, thus avoiding the clock signal interruption Delay and delay jitter ensure the timeliness of interrupt signal execution and ensure that the program is scheduled in time.

Fig. 8 is a flowchart of a method for obtaining a clock interrupt signal provided by Embodiment 3 of the present invention. As shown in Fig. 8, in the implementation scenario provided by this embodiment, the clock address manager is maintained by NFVO, and the method includes:

Step 400: Add the description of the VNF's requirements for clock interruption accuracy in the VNFD. Through the VNF loading process, the third-party entity sends the VNFD to the NFVO, and the NFVO submits the VNFD to the VNF directory, so that the NFVO and VNFM can obtain the synchronization requirements of the VNF. .

Wherein, the third party entity may be any entity representing the VNF provider, and may also be an entity within the management domain of the service provider.

VNFD refers to a configuration template that describes VNF deployment and operation behavior, specifically including the description of VNF deployment behavior and operation behavior configuration, where deployment behavior includes but not limited to the deployment environment required by VNF, specifically refers to the VNF’s requirements for NFVI resources, Such as the number of virtual machines, the number of virtual machine images (image), required computing resources and storage resources, etc. Operational behaviors are mainly behaviors during the VNF lifecycle management process, including but not limited to VNF topology, startup and shutdown, and functional scripts that match VNF lifecycle events.

Step 401: The NFVO receives a request from the Sender to instantiate the VNF.

This request is used to instantiate a new VNF;

Among them, Sender can be OSS, EMS, VNFM.

Step 402: NFVO verifies the validity of the received request for instantiating the VNF sent by the Sender;

Among them, validity refers to the legality of the VNF request, including but not limited to the legality of the Sender and the legality of the instantiation request itself. Specifically, the validity of the Sender refers to whether the Sender is authorized to send the request; the instantiation request itself The legitimacy of the request refers to whether the security parameters carried by the request can prove that the request is legal and has not been tampered with by a third party.

Step 403: NFVO reads the VNFD from the VNF directory. Including reading the VNF's need for clock interrupts.

Step 404: NFVO generates a VNF instance item, and adds the generated instance item to the "NFV Instances" database.

Wherein, the VNF instance item is specifically used for the NFVO and/or VNFM to query and maintain the relevant information of the VNF instance according to the VNF instance item during the operation of the VNF instance. The relevant information of the VNF instance specifically refers to the NFVI resources used by the VNF instance, the running status and performance of the virtual machine corresponding to the VNF instance, and the like.

Step 405a: NFVO submits instantiation parameters to VNFM.

The instantiation parameters include application-related parameters and non-application-related parameters, where the application-related parameters refer to application-related parameters running on the VNF, such as the service throughput to be satisfied by the VNF and/or the virtual machine on which the VNF is deployed Parameters such as volume and network bandwidth; non-application-related parameters refer to configuration parameters related to VNF deployment behavior and operation behavior, specifically referring to VNF’s requirements for NFVI resources and the limitation and description of behavior in the VNF life cycle management process. The instantiation parameters are used together with the VNFD to describe and limit the requirements of the resources for deploying the VNF and the instantiation process of the VNF.

Steps 405b-405c: The VNFM obtains the VNFD and checks the instantiation parameters, and modifies the instantiation parameters if necessary.

Specifically, when the VNF instantiation parameters preset in VNFM are inconsistent with the requirement information described in VNFD and/or the instantiation parameters submitted by NFVO to VNFM, VNFM will modify the inconsistent instantiation parameters.

In step 403, the NFVO may not be able to directly read the relevant information about the description of the clock interruption requirement added in the VNFD. In this step, the VNFM will analyze the clock interruption requirement from the VNFD and send it to the NFVO.

Step 406a: The NFVO selects a VIM that it believes can provide the VNF with resources meeting the requirements.

Among them, the "NFVI resource" database includes records of the capabilities of the NFVI server, specifically including resource descriptions that the NFVI server can provide, including all resources that can be provided, resources that have been provided, remaining available resources, and reserved resources Wait.

NFVO selects a VIM according to the records in the "NFVI resource" database, and the capability of the NFVI server managed by the VIM can meet the requirements of the VNF. The requirements here specifically refer to the requirements described in the VNFD and the requirements defined in the instantiation parameters.

Step 406b: NFVO sends a resource reservation request to VIM, which includes not only the VNF's requirements for computing, storage and network resources, but also the VNF's requirements for clock interruption (whether the VNF needs to directly access the hardware clock device to obtain clock interruption).

Step 406c: VIM checks the status of the managed resources, and returns the resource reservation result. Among them, in addition to considering the status of computing, storage and network resources, VIM also considers the status of managed clock device resources. If the clock device has a heavy load, step 406d can be performed, that is, return a resource reservation failure indication to NFVO, and NFVO restarts Steps 400-406c are executed until a suitable VIM is selected.

Step 407: If the VNF needs to obtain the clock interrupt by directly accessing the hardware clock device, the NFVO locally queries the address of the hardware clock that the VNF can directly access according to the ID of the physical device in the resource reservation result returned by the VIM, and confirms the address of the VNF access permission. At the same time, configure the period and duration of the VNF's access to the hardware clock.

Step 408: NFVO sends a VNF instantiation request to VNFM, which carries the corresponding VIM identifier (such as URL), hardware clock address and configuration information indication.

Steps 409a-409b: the VNFM requests the VIM to allocate resources to the VNF.

Steps 410a-410b: VNFM creates and starts a virtual machine according to the VNFD request VIM, including installing software packages, executing startup scripts, sending configuration data, and connecting the VM to the network.

Step 411: VNFM instructs the VNF to directly access the hardware clock address, access cycle and duration.

Step 412: The VNF accesses the hardware clock according to the instruction of the VNFM, obtains the interrupt of the hardware clock, and schedules the program.

Step 413: VNFM returns the VNF instantiation result to NFVO.

Steps 414a-414b: NFVO performs resource status update according to the VNF instantiation result returned by VNFM.

Step 415: NFVO updates the "NFV Instances" and "NFVI resource" databases.

Step 416: NFVO returns the VNF instantiation result to Sender.

The clock address manager in this embodiment is maintained by NFVO, and the clock address manager module and the hardware can be connected through an interface, as shown in Figure 9, or the clock address manager module can be integrated in the hardware, as shown in Figure 10 shown.

According to the acquisition method of the clock interrupt signal provided by the present invention, the NFV functional entity determines the clock interrupt accuracy requirement of the VNF according to the VNFD description information, and then, the NFV functional entity locally inquires to determine the hardware clock address for the VNF, and then sends the determined hardware clock address Give the VNF, the VNF can access the hardware clock according to the obtained hardware clock address, and obtain the clock interrupt signal. Instead of calling the underlying hardware clock interrupt signal through the virtual machine to generate the guest operating system software clock interrupt signal of the virtual machine, and then providing the software clock interrupt signal to the VNF for the clock signal transmission process of the VNF execution program scheduling, thus avoiding the clock signal interruption Delay and delay jitter ensure the timeliness of interrupt signal execution and ensure that the program is scheduled in time.

Fig. 11 is a flowchart of a method for obtaining a clock interrupt signal provided by Embodiment 4 of the present invention. As shown in Fig. 11, in the implementation scenario provided by this embodiment, the clock address manager is maintained by VIM, and the method includes:

Step 500: Add the VNF's requirement description for clock interruption accuracy in the VNFD, through the VNF loading process, the third-party entity sends the VNFD to the NFVO, and the NFVO submits the VNFD to the VNF directory, so that the NFVO and VNFM can obtain the synchronization of the VNF need.

Wherein, the third party entity may be any entity representing the VNF provider, and may also be an entity within the management domain of the service provider.

VNFD refers to a configuration template that describes VNF deployment and operation behavior, specifically including the description of VNF deployment behavior and operation behavior configuration, where deployment behavior includes but not limited to the deployment environment required by VNF, specifically refers to the VNF’s requirements for NFVI resources, Such as the number of virtual machines, the number of virtual machine images (image), required computing resources and storage resources, etc. Operational behaviors are mainly behaviors during the VNF lifecycle management process, including but not limited to VNF topology, startup and shutdown, and functional scripts that match VNF lifecycle events.

Step 501: The NFVO receives a request from the Sender to instantiate the VNF.

This request is used to instantiate a new VNF;

Among them, Sender can be OSS, EMS, VNFM.

Step 502: NFVO verifies the validity of the request.

Among them, validity refers to the legality of the VNF request, including but not limited to the legality of the Sender and the legality of the instantiation request itself. Specifically, the validity of the Sender refers to whether the Sender is authorized to send the request; the instantiation request itself The legitimacy of the request refers to whether the security parameters carried by the request can prove that the request is legal and has not been tampered with by a third party.

Step 503: The NFVO reads the VNFD from the VNF directory, which includes reading the VNF's requirement for clock interruption.

Step 504: NFVO generates a VNF instance entry, and adds the generated instance entry to the "NFV Instances" database.

Wherein, the VNF instance item is specifically used for the NFVO and/or VNFM to query and maintain the relevant information of the VNF instance according to the VNF instance item during the operation of the VNF instance. The relevant information of the VNF instance specifically refers to the NFVI resources used by the VNF instance, the running status and performance of the virtual machine corresponding to the VNF instance, and the like.

Step 505a: NFVO submits instantiation parameters to VNFM.

The instantiation parameters include application-related parameters and non-application-related parameters, where the application-related parameters refer to application-related parameters running on the VNF, such as the service throughput to be satisfied by the VNF and/or the virtual machine on which the VNF is deployed Parameters such as volume and network bandwidth; non-application-related parameters refer to configuration parameters related to VNF deployment behavior and operation behavior, specifically referring to VNF’s requirements for NFVI resources and the limitation and description of behavior in the VNF life cycle management process. The instantiation parameters are used together with the VNFD to describe and limit the requirements of the resources for deploying the VNF and the instantiation process of the VNF.

Steps 505b-505c: The VNFM checks the instantiation parameters and obtains the VNFD, and may also modify the instantiation parameters as required.

Specifically, when the VNF instantiation parameters preset in VNFM are inconsistent with the requirement information described in VNFD and/or the instantiation parameters submitted by NFVO to VNFM, VNFM will modify the inconsistent instantiation parameters.

In step 503, the NFVO may not be able to directly read the relevant information about the description of the clock interruption requirement added in the VNFD. In this step, the VNFM will analyze the clock interruption requirement from the VNFD and send it to the NFVO.

Step 506a: NFVO selects a VIM that can provide the VNF with resources meeting the requirements;

Among them, the "NFVI resource" database includes records of the capabilities of the NFVI server, specifically including resource descriptions that the NFVI server can provide, including all resources that can be provided, resources that have been provided, remaining available resources, and reserved resources Wait.

NFVO selects a VIM according to the records in the "NFVI resource" database, and the capability of the NFVI server managed by the VIM can meet the requirements of the VNF. The requirements here specifically refer to the requirements described in the VNFD and the requirements defined in the instantiation parameters.

Step 506b: The NFVO sends a resource reservation request to the selected VIM that can provide the VNF with resources that meet the requirements, which not only includes the VNF's requirements for computing, storage, and network resources, but also includes the VNF's requirements for clock interruption. Requires direct access to the hardware clock device for clock interrupts.

Step 506c: VIM checks the status of the managed resources, and returns the resource reservation result.

Among them, if the VNF needs to obtain the clock interrupt by directly accessing the hardware clock device, the resource reservation result includes the address information of the hardware clock and the period and duration configuration information of the VNF accessing the hardware clock. In addition to considering the status of computing, storage and network resources, the VIM also considers the status of the managed clock device resources. If the clock device is heavily loaded, step 506d can be performed to return a resource reservation failure indication to NFVO, and NFVO will re-execute step 500 -506c until a suitable vim is selected.

Step 507: The NFVO configures the cycle and duration of the VNF's access to the hardware clock.

If in step 506c the VIM has been configured and relevant configuration information is returned, then step 508 is directly executed without performing this step.

Step 508: NFVO sends a VNF instantiation request to VNFM, which carries the identifier of the corresponding VIM (such as URL, etc.), hardware clock address and configuration information indication.

Steps 509a-509b: VNFM requests VIM to allocate resources to VNF.

Steps 510a-510b: VNFM requests VIM to create and start a virtual machine according to the VNFD request, including installing software packages, executing startup scripts, sending configuration data, and connecting the VM to the network.

Step 511: VNFM instructs the VNF to directly access the hardware clock address, access cycle and duration.

Step 512: The VNF accesses the hardware clock according to the instruction of the VNFM, obtains the interrupt of the hardware clock, and schedules the program.

Step 513: VNFM returns the VNF instantiation result to NFVO.

Steps 514a-514b: NFVO performs resource status update.

Step 515: NFVO updates the "NFV Instances" and "NFVI resource" databases.

Step 516: NFVO returns the VNF instantiation result to Sender.

The clock address manager in this embodiment is maintained by VIM, and the clock address manager module and the hardware can be connected through an interface, as shown in Figure 12, and the clock address manager module can also be integrated in the hardware, as shown in Figure 13 shown.

According to the acquisition method of the clock interrupt signal provided by the present invention, the NFV functional entity determines the clock interrupt accuracy requirement of the VNF according to the VNFD description information, and selects a VIM that can provide resources, and the VIM returns the hardware clock address and configuration information, and the VNF can obtain it according to the obtained The hardware clock address accesses the hardware clock and gets the clock interrupt signal. Instead of calling the underlying hardware clock interrupt signal through the virtual machine to generate the guest operating system software clock interrupt signal of the virtual machine, and then providing the software clock interrupt signal to the VNF for the clock signal transmission process of the VNF execution program scheduling, thus avoiding the clock signal interruption Delay and delay jitter ensure the timeliness of interrupt signal execution and ensure that the program is scheduled in time.

FIG. 14 is a schematic structural diagram of a network function virtualization NFV functional entity provided in Embodiment 5 of the present invention. As shown in FIG. 14 , the NFV functional entity provided in this embodiment specifically includes:

The first determination module 101 is configured to determine the clock interruption accuracy requirement of the VNF according to the VNFD description information;

The second determination module 102 is configured to determine a hardware clock address for the VNF according to the clock interruption precision requirement;

The sending module 103 is configured to send the address of the hardware clock to the VNF, so that the VNF accesses the hardware clock according to the address of the hardware clock to obtain a clock interrupt signal.

Specifically, the NFV functional entity is NFVO or VNFM.

As shown in Figure 15, for the above-mentioned NFV functional entity, it may further include:

The third determination module 104 is configured to determine whether the VNF needs direct access according to the clock interruption precision requirement of the VNF before the second determination module 102 determines the hardware clock address for the VNF according to the clock interruption precision requirement. hardware clock;

Optionally, the second determination module 102 is further configured to determine a hardware clock address for the VNF if it is determined that the NFVO or VNFM needs to directly access the hardware clock.

Optionally, the sending module is specifically used for:

Sending a query request to the clock address manager, where the query request carries the identification information of the VNF and the identification information of the physical device mapped by the VNF;

As shown in Figure 16, for the above-mentioned NFV functional entity, it may further include:

The first receiving module 105 is configured to receive the hardware clock address returned by the clock address manager.

Optionally, the first receiving module 105 is further configured to receive the VNF pair returned by the clock address manager after the second determining module 102 receives the hardware clock address returned by the clock address manager. The access cycle and access duration of the above hardware clock address.

As shown in FIG. 17, for the above-mentioned NFV functional entity, the NFV functional entity is the NFVO, which may further include: a storage module 106, configured to store hardware clock information;

Wherein, the second determination module 102 is specifically configured to determine the address of the hardware clock that the VNF can directly access according to the information of the hardware clock stored in the storage module 106 .

As shown in FIG. 18, for the above-mentioned NFV functional entity, the NFV functional entity is the NFVO, which may further include: a fourth determining module 107, configured to determine that the NFV can be determined according to the second determining module 102 After directly accessing the hardware clock address, determine the access cycle and access duration of the VNF to the hardware clock address.

Optionally, the sending module 103 is further configured to, after sending the address of the hardware clock to the VNF, send the VNF's access period and access duration to the hardware clock address to the VNF.

As shown in Figure 19, for the above NFV functional entity, the NFV functional entity is the NFVO, which may further include:

The fifth determination module 108 is configured to determine, according to the clock interruption accuracy requirement of the VNF, the resources that meet the VNF requirement before the second determination module 102 determines the hardware clock address for the VNF according to the clock interruption accuracy requirement. VIM;

Further, the sending module 103 is also configured to send a resource reservation request to the VIM;

A second receiving module 109 is also included, configured to receive the resource reservation result returned by the VIM, where the resource reservation result carries the identifier of the physical device.

As shown in Figure 20, for the above NFV functional entity, the NFV functional entity is the VNFM, which may further include:

The requesting module 110 is configured to request the VIM to create and start a virtual machine after the fifth determining module 108 receives the resource reservation result returned by the VIM, the resource reservation result carrying the identifier of the physical device.

Further, the NFV functional entity is the NFVO, and the resource reservation result includes: the hardware clock address;

The second determination module 102 is specifically configured to: obtain the hardware clock address from the resource reservation result.

Further, the resource reservation result also includes: the access cycle and access duration of the VNF to the hardware clock address.

As shown in Figure 21, for the above NFV functional entity, the NFV functional entity is the NFVO, and the NFVO may further include:

The sixth determining module 111 is configured to determine the access cycle and access duration of the VNF to the hardware clock address after obtaining the hardware clock address from the resource reservation result according to the second determining module 102 .

The NFV functional entity provided in this embodiment is the execution device of the method for obtaining the clock interrupt signal provided in the embodiment of the present invention, and the specific process for executing the method for obtaining the clock interrupt signal can be referred to in FIG. 1, FIG. 2 to FIG. 13 Relevant descriptions in the method embodiments will not be repeated here.

FIG. 22 is a schematic structural diagram of a network function virtualization NFV functional entity provided by the present invention. As shown in FIG. 22 , the NFV functional entity provided in this embodiment includes: a processor 21 and a memory 22 . The memory 22 stores execution instructions, the processor 21 communicates with the memory 22, and the processor 21 calls the execution instructions in the memory 22 to perform the following operations:

According to the VNFD description information, determine the clock interruption accuracy requirements of the VNF;

Determine a hardware clock address for the VNF according to the clock interruption precision requirement;

Sending the address of the hardware clock to the VNF, so that the VNF accesses the hardware clock according to the address of the hardware clock to obtain a clock interrupt signal.

The NFV functional entity is NFVO or VNFM.

Optionally, before the processor 21 determines the hardware clock address for the VNF according to the clock interrupt precision requirement, further includes:

According to the clock interruption accuracy requirement of the VNF, determine whether the VNF needs to directly access the hardware clock;

If it is determined that the NFVO or VNFM needs to directly access the hardware clock, then determine a hardware clock address for the VNF.

Further, the processor 21 determines the hardware clock address for the VNF according to the clock interrupt precision requirement of the VNF, specifically including:

Sending a query request to the clock address manager, where the query request carries the identification information of the VNF and the identification information of the physical device mapped by the VNF;

Receive the hardware clock address returned by the clock address manager.

Further, after receiving the hardware clock address returned by the clock address manager, the processor 21 further includes:

The processor 21 receives the access cycle and access duration of the VNF to the hardware clock address returned by the clock address manager.

Optionally, information about the hardware clock may also be stored on the processor 21, and the processor 21 determines a hardware clock address for the VNF according to the clock interruption accuracy requirements of the VNF, specifically including:

The processor 21 determines an address of the hardware clock that the VNF can directly access according to the stored information of the hardware clock.

Further, after determining the address of the hardware clock that the NFV can directly access according to the stored information of the hardware clock, the processor 21 further includes:

The processor 21 determines the access cycle and access duration of the VNF to the hardware clock address.

Further, after the processor 21 sends the address of the hardware clock to the VNF, it further includes:

The processor 21 sends the access period and access duration of the VNF to the hardware clock address to the VNF.

Optionally, before the processor 21 determines the hardware clock address for the VNF according to the clock interrupt precision requirement, further includes:

The processor 21 determines, according to the clock interrupt precision requirement of the VNF, a VIM that meets the resources required by the VNF;

The processor 21 sends a resource reservation request to the VIM;

The processor 21 receives the resource reservation result returned by the VIM, where the resource reservation result carries the identifier of the physical device.

Further, the processor 21 receives the resource reservation result returned by the VIM, and after the resource reservation result carries the identifier of the physical device, it further includes:

The processor 21 requests the VIM to create and start a virtual machine.

Further, the resource reservation result includes: the hardware clock address;

The processor 21 determining the hardware clock address for the VNF specifically includes: the NFVO obtaining the hardware clock address from the resource reservation result.

Further, the resource reservation result also includes: the access cycle and access duration of the VNF to the hardware clock address.

Further, after the processor 21 obtains the hardware clock address from the resource reservation result, it further includes:

The processor 21 determines the access cycle and access duration of the VNF to the hardware clock address.

The NFV functional entity provided by the embodiment of the present invention can be used to execute the technical solution of the above method embodiment, and its implementation principle and technical effect are similar, and will not be repeated here.

Those of ordinary skill in the art can understand that all or part of the steps for realizing the above-mentioned method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the Including the steps of the foregoing method embodiments; and the aforementioned storage medium includes: various media that can store program codes such as a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, etc. .

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present invention, rather than limiting them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: It is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the various embodiments of the present invention. scope.

Claims (27)

1. A method for obtaining a clock interrupt signal, characterized in that, comprising: The network function virtualization NFV functional entity determines the clock interruption precision requirement of the virtual network function VNF according to the description information in the virtual network function requirement description file VNFD; The NFV functional entity determines a hardware clock address for the VNF according to the clock interruption precision requirement; The NFV functional entity sends the address of the hardware clock to the VNF, so that the VNF accesses the hardware clock according to the address of the hardware clock to obtain a clock interrupt signal. 2. The method according to claim 1, wherein the NFV functional entity is a network function virtualization orchestrator (NFVO) or a virtual network function manager (VNFM). 3. The method according to claim 2, wherein the NFV functional entity further comprises: The NFV functional entity determines whether the VNF needs to directly access the hardware clock according to the clock interruption precision requirement of the VNF; If it is determined that the NFVO or VNFM needs to directly access a hardware clock, the NFVO or VNFM determines a hardware clock address for the VNF. 4. The method according to claim 2, wherein the NFV functional entity determines the hardware clock address for the VNF according to the clock interruption accuracy requirements of the VNF, specifically comprising: The NFVO or VNFM sends a query request to the clock address manager, and the query request carries the identification information of the VNF and the identification information of the physical device mapped by the VNF; The NFVO or VNFM receives the hardware clock address returned by the clock address manager. 5. The method according to claim 4, wherein after the NFV functional entity receives the hardware clock address returned by the clock address manager, further comprising: The NFVO or VNFM receives the access cycle and access duration of the VNF to the hardware clock address returned by the clock address manager. 6. The method according to claim 2, wherein the information of the hardware clock is stored on the NFV functional entity, and the NFV functional entity determines the hardware clock address for the VNF according to the clock interruption accuracy requirements of the VNF, specifically include: The NFVO determines the address of the hardware clock that the VNF can directly access according to the stored information of the hardware clock. 7. The method according to claim 6, wherein, after the NFV functional entity determines the address of the hardware clock that the NFV can directly access according to the stored information of the hardware clock, it further includes: The NFVO determines the access cycle and access duration of the VNF to the hardware clock address. 8. The method according to claim 5 or 7, wherein after the NFV functional entity sends the address of the hardware clock to the VNF, further comprising: The NFVO sends the VNF's access period and access duration to the hardware clock address to the VNF. 9. The method according to claim 2, wherein the NFV functional entity further comprises: The NFVO determines a virtualized infrastructure manager VIM that satisfies the resources required by the VNF according to the clock interruption accuracy requirements of the VNF; The NFVO sends a resource reservation request to the VIM; The NFVO receives the resource reservation result returned by the VIM, and the resource reservation result carries the identifier of the physical device. 10. The method according to claim 9, wherein the NFVO receives the resource reservation result returned by the VIM, and after the resource reservation result carries the identifier of the physical device, it further includes: The VNFM requests the VIM to create and start a virtual machine. 11. The method according to claim 9 or 10, wherein the resource reservation result includes: the hardware clock address; The NFV functional entity determines a hardware clock address for the VNF, specifically including: The NFVO acquires the hardware clock address from the resource reservation result. 12 . The method according to claim 11 , wherein the resource reservation result further includes: an access period and an access duration of the VNF to the hardware clock address. 13 . 13. The method according to claim 11, wherein after the NFV functional entity obtains the hardware clock address from the resource reservation result, further comprising: The NFVO determines the access cycle and access duration of the VNF to the hardware clock address. 14. A network function virtualization NFV device, characterized in that, comprising: The first determination module is configured to determine the clock interruption precision requirement of the VNF according to the VNFD description information; The second determination module is configured to determine a hardware clock address for the VNF according to the clock interruption precision requirement; A sending module, configured to send the address of the hardware clock to the VNF, so that the VNF accesses the hardware clock according to the address of the hardware clock to obtain a clock interrupt signal. 15. The NFV device according to claim 14, wherein the NFV device is NFVO or VNFM. 16. The NFV device according to claim 15, further comprising: The third determination module is configured to determine whether the VNF needs to directly access the hardware clock according to the clock interruption precision requirement of the VNF before the second determination module determines the hardware clock address for the VNF according to the clock interruption precision requirement. ; The second determination module is further configured to determine a hardware clock address for the VNF if it is determined that the NFVO or VNFM needs to directly access the hardware clock. 17. The NFV device according to claim 15, wherein the sending module is specifically used for: Sending a query request to the clock address manager, where the query request carries the identification information of the VNF and the identification information of the physical device mapped by the VNF; The NFV device further includes: a first receiving module, configured to receive the hardware clock address returned by the clock address manager. 18. The NFV device according to claim 17, wherein the first receiving module is further configured to, after the second determining module receives the hardware clock address returned by the clock address manager, receive The access period and access duration of the VNF to the hardware clock address returned by the clock address manager. 19. The NFV device according to claim 15, wherein the NFV device is the NFVO, and the NFVO further comprises: The storage module is used for storing the information of the hardware clock; The second determining module specifically: according to the stored information of the hardware clock, determine the address of the hardware clock that the VNF can directly access. 20. The NFV device according to claim 19, wherein the NFV device is the NFVO, and the NFVO further comprises: The fourth determination module is configured to determine the hardware clock address that the NFV can directly access according to the second determination module, and then determine the access cycle and access duration of the VNF to the hardware clock address. 21. The NFV device according to claim 18 or 20, wherein the NFV device is the NFVO, and the sending module is further configured to send the address of the hardware clock to the VNF , sending the access period and access duration of the VNF to the hardware clock address to the VNF. 22. The NFV device according to claim 15, wherein the NFV device is the NFVO, and the NFVO further comprises: The fifth determination module is configured to determine a VIM that meets the resource requirements of the VNF according to the clock interruption accuracy requirements of the VNF before the second determination module determines the hardware clock address for the VNF according to the clock interruption accuracy requirements; The sending module is further configured to: send a resource reservation request to the VIM; A second receiving module is also included, configured to receive the resource reservation result returned by the VIM, where the resource reservation result carries the identifier of the physical device. 23. The NFV device according to claim 22, wherein the NFV device is the VNFM, and the VNFM further comprises: a request module, configured to receive the VNFM in the fifth determination module After the resource reservation result returned by the VIM carries the identifier of the physical device, the VIM is requested to create and start the virtual machine. 24. The NFV device according to claim 22 or 23, wherein the NFV device is the NFVO, and the resource reservation result includes: the hardware clock address; The second determination module is specifically configured to: obtain the hardware clock address from the resource reservation result. 25. The NFV device according to claim 24, wherein the resource reservation result further includes: an access period and an access duration of the VNF to the hardware clock address. 26. The NFV device according to claim 24, wherein the NFV device is the NFVO, and the NFVO further comprises: The sixth determination module is configured to determine the access cycle and access duration of the VNF to the hardware clock address after obtaining the hardware clock address from the resource reservation result according to the second determination module. 27. A network function virtualization NFV device, characterized in that it includes: a processor and a memory, the memory stores execution instructions, and when the clock interrupt signal acquisition system is running, the relationship between the processor and the memory The processor executes the execution instruction so that the system for obtaining the clock interrupt signal executes the method according to any one of claims 1-13.