WO2015117278A1

WO2015117278A1 - Method for obtaining clock interruption signal, and nfv functional entity

Info

Publication number: WO2015117278A1
Application number: PCT/CN2014/071929
Authority: WO
Inventors: 余芳; 熊春山; 朱雷
Original assignee: 华为技术有限公司
Priority date: 2014-02-10
Filing date: 2014-02-10
Publication date: 2015-08-13
Also published as: CN105103125B; CN105103125A

Abstract

The present invention provides a method for obtaining a clock interruption signal, and an NFV functional entity. The method comprises: an NFV functional entity determining a clock interruption precision demand of a VNF according to VNFD description information; then, the NFV functional entity determining a hardware clock address for the VNF according to the clock interruption precision demand; and finally, the NFV functional entity sending the determined hardware clock address to the VNF, so that the VNF can access a hardware clock according to the obtained hardware clock address and obtain a clock interruption signal. By using the technical scheme of the present invention, a software clock interruption signal of a user operating system of a virtual machine is generated without calling, by means of the virtual machine, a bottom layer hardware clock interruption signal, and then, the software clock interruption signal is provided to a VNF to enable the VNF to execute a clock signal transmission process of program scheduling, thereby avoiding the delay of the clock signal and the delay jitter, and ensuring the timeliness of the execution of the interruption signal and ensuring that a program is timely scheduled.

Description

Clock interrupt signal acquisition method and NFV functional entity

Technical field

The present invention relates to communication technologies, and in particular, to a method for acquiring a clock interrupt signal and an NFV functional entity. Background technique

With the rapid development of smart terminals and data cards/laptops supporting the 3rd-generation mobile communication technology (3G), the mobile Internet business has grown exponentially over the past few years. In order to cope with the increasing data traffic, operators have proposed the concept of Network Functions Virtualization (NFV). The main design idea of NFV is that the hardware platform adopts a general-purpose server, and the virtualization software runs on the server and generates virtual Machines, various network elements run in virtual machines in the form of software. With 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. The upgrade of new network elements or network elements will be reflected in the new virtual machine. Import or change of software version in the virtual machine. At the same time, because virtualization technology shields the differences between the underlying physical platforms, the issue of hardware resource sharing across vendors will be solved. In addition, the functions of virtual machine dynamic migration and dynamic generation are combined with the intelligent management of the virtualization platform to dynamically expand and shrink the network elements according to the change of the traffic volume, thereby achieving more efficient use of hardware resources.

In the prior art, in the virtual environment of the 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 to the virtualized network function (VNF). This process may cause the program to be unable to be scheduled in time because the virtual machine's software clock emulation program cannot guarantee that the clock signal acquired by the virtual network function is delayed due to timely scheduling. Especially for many applications or network functions in wireless networks that require high real-time and clock accuracy, this delay of the clock signal will affect the processing of the network function and reduce the network performance. Summary of the invention

Embodiments of the present invention provide a method for acquiring a clock interrupt signal and an NFV functional entity, which have been solved. The delay of the clock signal and the delay jitter caused by calling the underlying hardware clock interrupt signal. A first aspect of the present invention provides a method for acquiring a clock interrupt signal, including:

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

Determining, by the NFV functional entity, a hardware clock address for the VNF according to the clock interrupt precision requirement;

The NFV function entity sends an address of the hardware clock to the VNF, so that the VNF accesses the hardware clock according to an address of the hardware clock to acquire 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 manner of the first aspect, in a second possible implementation manner of the first aspect, the NFV function entity, before determining a hardware clock address for the VNF according to the clock interrupt precision requirement, further includes :

Determining, by the NFV function entity, whether the VNF needs to directly access the hardware clock according to the clock interrupt precision requirement of the VNF;

If it is determined that the NFVO or VNFM requires direct access to the hardware clock, the NFVO or VNFM determines the hardware clock address for the VNF.

In conjunction with the first possible implementation of the first aspect, in a third possible implementation manner of the first aspect, the NFV function entity determines a hardware clock address for the VNF according to a clock interrupt precision requirement of the VNF, and specifically includes:

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

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

In conjunction with the third possible implementation of the first aspect, in a fourth possible implementation of the first aspect, after the NFV functional entity receives the hardware clock address returned by the clock address manager, the method further includes:

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

In combination with the first possible implementation of the first aspect, the fifth possible implementation in the first aspect Wherein the NFV functional entity stores information of a hardware clock, and the NFV functional entity is configured according to

The clock interrupt precision requirement of the VNF, determining the hardware clock address for the VNF, specifically includes: the NFVO determining, according to the stored information of the hardware clock, the hardware clock address that the VNF can directly access.

In conjunction with the fifth possible implementation 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 NFV directly accessible After the hardware clock address, it also includes:

The NFVO determines an access period and an access duration of the VNF to the hardware clock address. With reference to the fourth or the sixth possible implementation of the first aspect, in a seventh possible implementation manner of the first aspect, after the NFV functional entity sends the address of the hardware clock to the VNF, the method further includes :

The NFVO sends an access period and an access duration of the VNF to the hardware clock address to the VNF.

With reference to the first possible implementation manner of the first aspect, in an eighth possible implementation manner of the first aspect, the NFV function entity, before determining a hardware clock address for the VNF according to the clock interrupt precision requirement, further includes :

Determining, by the NFVO, a virtualized infrastructure manager VIM that satisfies the VNF requirement resource according to a clock interruption accuracy requirement of the VNF;

Sending, by the NFVO, 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.

In conjunction with the eighth possible implementation of the first aspect, in a ninth possible implementation manner of the first aspect, the NFVO receives a resource reservation result returned by the VIM, where the resource reservation result carries a physical device After the identification, it also includes:

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

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

The determining, by the NFV function entity, the hardware clock address for the VNF, specifically: the NFVO acquiring the hardware clock address from the resource reservation result.

In conjunction with the tenth possible implementation of the first aspect, the eleventh possible implementation in the first aspect In the method, the resource reservation result further includes: an access period and an access duration of the VNF to the hardware clock address.

With the tenth possible implementation of the first aspect, in a twelfth possible implementation manner of the first aspect, after the NFV function entity obtains the hardware clock address from the resource reservation result, the method further includes:

The NFVO determines an access period and an access duration of the VNF to the hardware clock address. The second aspect of the present invention provides a network function virtualization NFV function entity, including: a first determining module, configured to determine a clock interrupt precision requirement of the VNF according to the VNFD description information;

a second determining module, configured to determine a hardware clock address for the VNF according to the clock interrupt precision requirement;

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

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

In conjunction with the first possible implementation of the second aspect, in a second possible implementation of the second aspect, the method further includes:

a third determining module, configured to determine, according to a clock interrupt precision requirement of the VNF, that the VNF needs to directly access the hardware clock before the second determining module determines a hardware clock address for the VNF according to the clock interrupt precision requirement ;

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

In conjunction with 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 identifier information of the VNF and the identifier 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.

In conjunction with the third possible implementation of the second aspect, in a fourth possible implementation manner of the second aspect, the first receiving module is further configured to receive, by the second determining module, the clock address Receiving the returned by the clock address manager after the hardware clock address returned by the processor

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

In conjunction with the first possible implementation of the second aspect, in a fifth possible implementation of the second aspect, the NFV functional entity is the NFVO, and the NFVO further includes:

a storage module, configured to store information of a hardware clock;

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

In conjunction with the fifth possible implementation of the second aspect, in a sixth possible implementation of the second aspect, the NFV functional entity is the NFVO, and the NFVO further includes:

And a fourth determining module, configured to determine, according to the second determining module, the access period and the access duration of the VNF to the hardware clock address after determining the hardware clock address that the NFV can directly access.

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

In conjunction with 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:

a fifth determining module, configured to determine, according to the clock interrupt precision requirement of the VNF, a VIM that satisfies the VNF requirement resource according to a clock interrupt precision requirement of the VNF, according to the clock interrupt precision requirement;

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

And a second receiving module, configured to receive a resource reservation result returned by the VIM, where the resource reservation result carries an identifier of the physical device.

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

In combination with the eighth or ninth possible implementation of the second aspect, the tenth aspect of the second aspect may In an implementation manner, the NFV function entity is the NFVO, and the resource reservation result includes: the hardware clock address;

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

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

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

And a sixth determining module, configured to determine, according to the second determining module, the access period and the access duration of the hardware clock address after the hardware clock address is obtained from the resource reservation result.

A third aspect of the present invention provides a network function virtualization NFV functional entity, including: a processor and a memory, wherein the memory stores an execution instruction, when the clock interrupt signal acquisition system is running, the processor and the memory In communication, the processor executes the execution instruction such that the acquisition system of the clock interrupt signal performs the method of any one of claims 1 to 13.

The embodiment of the invention provides a method for acquiring a clock interrupt signal and an NFV function entity. The NFV function entity determines a clock interrupt precision requirement of the VNF according to the VNFD description information, and then the NFV function entity determines the hardware for the VNF according to the clock interrupt precision requirement. The clock address is finally sent to the VNF by the determined hardware clock address. The VNF can access the hardware clock according to the obtained hardware clock address and obtain the clock interrupt signal. The virtual machine guest operating system software clock interrupt signal is generated without calling the underlying hardware clock interrupt signal by the virtual machine, and the software clock interrupt signal is provided to the VNF for VNF execution program scheduling clock signal transmission process, thereby avoiding the clock signal. Delay and delay jitter ensure the timeliness of interrupt signal execution and ensure that the program is scheduled in time. BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description of the drawings used in the embodiments or the prior art description will be briefly described below. The drawings are some embodiments of the invention, to those of ordinary skill in the art In other words, other drawings can be obtained based on these drawings without paying for creative labor.

1 is a flowchart of a method for acquiring a clock interrupt signal according to Embodiment 1 of the present invention; FIG. 2 is a flowchart of a method for acquiring a clock interrupt signal according to Embodiment 2 of the present invention, and FIG. 3 is an embodiment of the present invention. I: The architecture and interface diagram 1 of the method for obtaining the clock interrupt signal provided;

4 is a schematic diagram showing an architecture and an interface of a method for acquiring a clock interrupt signal according to Embodiment 1 of the present invention;

5 is a schematic diagram of an architecture and an interface of a method for acquiring a clock interrupt signal according to Embodiment 1 of the present invention;

6 is a schematic diagram of an architecture and an interface of a method for acquiring a clock interrupt signal according to Embodiment 1 of the present invention;

FIG. 7 is a flowchart of a method for acquiring a clock interrupt signal according to Embodiment 2 of the present invention; FIG. 8 is a flowchart of a method for acquiring a clock interrupt signal according to Embodiment 3 of the present invention; FIG. 9 is a flowchart of an embodiment of the present invention; I3: Architecture and interface of the method for obtaining the clock interrupt signal provided:

FIG. 10 is a schematic diagram showing the architecture and interface of a method for acquiring a clock interrupt signal according to Embodiment 3 of the present invention; FIG.

FIG. 11 is a flowchart of a method for acquiring a clock interrupt signal according to Embodiment 4 of the present invention; FIG. 12 is a schematic diagram showing a structure and an interface of a method for acquiring a clock interrupt signal according to Embodiment 4 of the present invention;

13 is a second schematic diagram of an architecture and an interface of a method for acquiring a clock interrupt signal according to Embodiment 4 of the present invention;

14 is a schematic structural diagram 1 of a network function virtualization NFV functional entity according to Embodiment 5 of the present invention;

FIG. 15 is a schematic structural diagram 2 of a network function virtualization NFV functional entity according to Embodiment 5 of the present invention;

16 is a schematic structural diagram 3 of a network function virtualization NFV functional entity according to Embodiment 5 of the present invention;

FIG. 17 is a schematic diagram of a network function virtualization NFV functional entity according to Embodiment 5 of the present invention; Schematic diagram four;

FIG. 18 is a schematic structural diagram 5 of a network function virtualization NFV functional entity according to Embodiment 5 of the present invention; FIG.

FIG. 19 is a schematic structural diagram 6 of a network function virtualization NFV functional entity according to Embodiment 5 of the present invention; FIG.

FIG. 20 is a schematic structural diagram 7 of a network function virtualization NFV functional entity according to Embodiment 5 of the present invention; FIG.

FIG. 21 is a schematic structural diagram VIII of a network function virtualization NFV functional entity according to Embodiment 5 of the present invention;

FIG. 22 is a schematic diagram of a network function virtualization NFV functional entity according to Embodiment 6 of the present invention. The technical solutions in the embodiments of the present invention will be clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. The embodiments are a part of the embodiments of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

FIG. 1 is a flowchart of a method for acquiring a clock interrupt signal according to Embodiment 1 of the present invention. As shown in FIG. 1 , the method includes:

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

The NFV functional entity may be a Network Function Virtualized Orchestrator (NFVO) or a Virtualized Network Function Manager (VNFM). The information described by the VNFD includes the configuration of the VNF deployment behavior and operational behavior. The deployment behavior includes, but is not limited to, the deployment environment required by the VNF. Specifically, the VNF refers to the Network Function Virtualized Infrastructure (NFVI) resource. Requirements, such as the number of virtual machines, the number of virtual machine images, the required computing resources, and storage resources. Operational behavior is mainly VNF Behaviors in the lifecycle management process, including but not limited to VNF topology, startup and shutdown, functional scripts that match VNF lifecycle events, and more.

VNFD is sent to NFVO by a third-party entity during VNF on-boarding. It is submitted by NFVO to the NFV catalog. NFVO reads VNFD from the NFV catalog when needed.

The third-party entity here can be any entity that represents the VNF provider, or an entity within the service provider management domain.

The VNF clock interrupt accuracy refers to the VNF's need for the frequency of the clock interrupt and the frequency stability. Step 102: The NFV functional entity determines a hardware clock address for the VNF according to a clock interrupt precision requirement;

Specifically, the NFV functional entity can first determine 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 VNF needs to directly access the hardware clock, the NFVO or VNFM can be a clock address as a feasible implementation manner. The manager sends a query request, where the query request carries the identification information of the VNF and the identification information of the physical device mapped by the VNF, and then the NFVO or VNFM receives the hardware clock address accessible by the VNF returned by the clock address manager, and the VNF accesses the hardware clock. Access period and access duration.

As another feasible implementation manner, the information of the hardware clock can also be pre-stored on the NFVO, so that the NFVO can directly determine the hardware clock address that the VNF can directly access according to the information of the stored hardware clock, and can further determine the VNF. The access period and access duration of the hardware clock.

The hardware clock address manager may be a business support system/Operation support system (Business Support System/Operation support system, NFVO, VNFM, or a virtualized infrastructure manager (Virtualized Infrastructure Manager). The invention is abbreviated as VIM) and the like.

Step 103: The NFV function 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 the clock interrupt signal.

The NFV functional entity sends the received hardware clock address returned by the clock address manager and the access period and access duration of the hardware clock to the VNF. The VNF then acquires the clock interrupt signal based on the received accessible hardware clock address.

The method for acquiring a clock interrupt signal provided by the present invention, the NFV functional entity is described according to VNFD The information determines the clock interrupt precision requirement of the VNF. Then, the NFV function entity determines the hardware clock address for the VNF according to the clock interrupt precision requirement, and finally sends the determined hardware clock address to the VNF, and the VNF can access according to the obtained hardware clock address. Hardware clock, and get the clock interrupt signal. The virtual machine guest operating system software clock interrupt signal is generated without calling the underlying hardware clock interrupt signal by the virtual machine, and the software clock interrupt signal is provided to the VNF for VNF execution program scheduling clock signal transmission process, thereby avoiding the clock signal. Delay and delay jitter ensure the timeliness of interrupt signal execution and ensure that the program is scheduled in time.

2 is a flowchart 1 of a method for acquiring a clock interrupt signal according to Embodiment 2 of the present invention. As shown in FIG. 2, in the implementation scenario provided by this embodiment, a clock address manager is maintained by an OSS/BSS system or a clock address server. And sending, by NFVO, a clock address query request to the clock address manager, the method comprising:

Step 200: Add VNF to the VNFD requirements for clock interrupt accuracy. Through the VNF loading process, the VNFD is sent to the NFVO by the third-party entity, and the NFVO submits the VNFD to the VNF directory, so that the NFVO and the VNFM can acquire the VNF. Peer needs.

The third-party entity may be any entity that represents the VNF provider, or an entity within the service provider management domain.

VNFD is a configuration template that describes the VNF deployment and operational behavior. It includes a description of the VNF deployment behavior and operational behavior configuration. The deployment behavior includes but is not limited to the deployment environment required by the VNF. Specifically, the VNF needs for NFVI resources, such as The number of virtual machines, the number of virtual machine images, the required computing resources, and storage resources. The operational behavior is primarily the behavior of 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: NFVO receives a request from the trigger Sender to instantiate the VNF.

This request is used to instantiate a new VNF;

Among them, Sender can be OSS, Element Management System (EMS), VNFM.

Step 202: The NFVO verifies the validity of the received request for instantiating the VNF sent by the Sender; wherein, the 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 legality of the Sender refers to whether the sender is authorized to send the request; the legality of the instantiation request itself refers to whether the security parameter carried by the request can Prove that the request is legal and has not been tampered with by a third party.

Step 203: NFVO reads the VNFD from the VNF directory, including reading the VNF's need for a clock interrupt.

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

The VNF instance is specifically used to query and maintain information about the VNF instance according to the VNF instance item during the running of the VNF instance. The VNF instance information refers to the NFVI resources used by the VNF instance and the running status and performance of the VMs corresponding to the VNF instance.

Step 205a: NFVO submits the instantiation parameter to VNFM.

The instantiation parameters include application-related parameters and application-related parameters, where the application-related parameters refer to application-related parameters running on the VNF, such as VNF and/or the throughput of the service to be satisfied by the virtual machine deploying the VNF, Parameters such as network bandwidth; Non-application-related parameters refer to configuration parameters related to VNF deployment behavior and operational behavior, specifically the requirements of VNF for NFVI resources and the definition and description of behavior during VNF lifecycle management. Instantiation parameters and VNFD—used to describe requirements and requirements for resources and VNF instantiation processes that deploy VNF.

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

Specifically, when the VNF instantiation parameter preset in the VNFM is inconsistent with the demand information described in the VNFD and/or the instantiation parameter submitted by the NFVO to the VNFM, the VNFM modifies the inconsistent instantiation parameters.

In step 203, the NFVO may not directly read the information about the clock interrupt requirement added in the VNFD. In this step, the VNFM parses the clock interrupt request from the VNFD and sends it to the NFVO.

Step 206a: NFVO chooses a resource that is considered to provide VNF with a demand

The "NFVI resource" database includes a record of the capabilities of the NFVI server, including the resource descriptions that the NFVI server can provide, including all the resources that can be provided, the resources that have been provided, the remaining resources available, and the pre-requisites. Keep resources and so on.

NFVO selects a VIM based on the records in the "NFVI resource" database, the VIM The ability of the managed NFVI server to meet the needs 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 requirements for calculation, storage, and network resources, but also the VNF requirement for a clock interrupt (whether the VNF needs to directly access the hardware clock device to obtain a clock interrupt).

Step 206c: The VIM checks the status of the managed resource and returns the resource reservation result. In addition to considering the state of the computing, storage, and network resources, the VIM also considers the state of the clock resource that is managed. If the clock device is heavily loaded, step 206d may be performed, that is, the resource reservation failure indication is returned to the NFVO, NFVO. Re-execute steps 200-206c until the appropriate VIM is selected.

Step 207a: If the VNF needs to obtain a clock interrupt by directly accessing the hardware clock device, the NFVO sends a query request to the clock address manager, and the query request carries the VNF identification number (ID), the mapped physical The ID of the device (which may include one or more) information.

Steps 207b-207c: The clock address manager locally queries the hardware clock address that the VNF can directly access according to the query request, and confirms the access authority of the VNF, and returns the result to the NFVO. The result includes the address of the hardware clock, and may also include the VNF. Access to the hardware clock cycle and duration configuration information.

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

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

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

Step 21 Oa-210b: VNFM requests VIM to create and start a virtual machine based on VNFD request, including installing a software package, executing a startup script, sending configuration data, and connecting the virtual machine to the network.

Step 211: The VNFM indicates the hardware clock address, access period, and duration that the VNF can directly access.

Step 212: The VNF accesses the hardware clock according to the indication of the VNFM, acquires a hardware clock interrupt, and schedules the program. Step 213: The VNFM returns the VNF instantiation result to the NFVO.

Steps 214a-214b: The NFVO updates the resource status based on the VNF instantiation result returned by the VNFM.

Step 215: NFVO updates the "NFV Instances" and "NF VI 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 the interface. As shown in 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 a clock address server, which is responsible for managing and maintaining the status of each clock module/device in the network. address. And the clock module and the hardware can be connected through the interface. As shown in Figure 5, the clock module can also be integrated in the hardware, as shown in Figure 6.

According to the method for acquiring a clock interrupt signal provided by the embodiment of the present invention, the NFV function entity determines the clock interrupt precision requirement of the VNF according to the VNFD description information, and then, the NFV function entity determines the hardware clock address for the VNF according to the clock interrupt precision requirement, and finally 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 the clock interrupt signal. Instead of calling the underlying hardware clock interrupt signal by the virtual machine to generate the guest operating system software clock interrupt signal of the virtual machine, the software clock interrupt signal is provided to the VNF for the VNF execution program to schedule the clock signal transmission process, thereby avoiding the clock signal. Delay and delay jitter ensure the timeliness of interrupt signal execution and ensure that the program is scheduled in time.

FIG. 7 is a flowchart 2 of a method for acquiring a clock interrupt signal according to Embodiment 2 of the present invention. As shown in FIG. 7 , in the implementation scenario provided by this embodiment, a clock address manager is maintained by an OSS/BSS system or a clock address server. And sending, by the VNFM, a clock address query request to the clock address manager, the method comprising:

Step 300: Add a VNF requirement for clock interrupt accuracy in the VNFD. Through the VNF loading process, the VNFD is sent to the NFVO by the third-party entity, and the NFVO submits the VNFD to the VNF directory, so that the NFVO and the VNFM can acquire the VNF. Peer needs.

The third-party entity may be any entity that represents the VNF provider or an entity within the management domain of the service provider.

VNFD refers to a configuration template that describes the VNF deployment and operational behavior, including VNF. Description of the deployment behavior and operational behavior configuration, including but not limited to the deployment environment required by the VNF, specifically the VNF requirements for NFVI resources, such as the number of virtual machines, the number of virtual machine images, and the required Computing resources, storage resources, etc. The operational behavior is primarily the behavior of the VNF lifecycle management process, including but not limited to VNF topology, startup and shutdown, functional scripts that match VNF lifecycle events, and so on.

Step 301: NFVO receives a request for instantiating a VNF sent by Sender.

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 request sent by the Sender to instantiate the VNF. The 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 legality of the Sender refers to whether the sender is authorized to send the request; The legality 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: NFVO reads the VNFD from the VNF directory, including reading the VNF for the clock interrupt.

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

The VNF instance item is specifically used to query and maintain the information about the VNF instance according to the VNF instance item during the running of the VNF instance. The information about the VNF instance refers to the NFVI resource used by the VNF instance, the running status and performance of the VM corresponding to the VNF instance.

Step 305a: NFVO submits the 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 VNF and/or throughput of services to be satisfied by the virtual machine deploying the VNF. Parameters such as quantity and network bandwidth; non-application-related parameters refer to configuration parameters related to VNF deployment behavior and operational behavior, specifically the requirements of VNF for NFVI resources and the definition and description of behavior during VNF lifecycle management. The instantiation parameters are used together with the VNFD to describe requirements and requirements for the resources and VNF instantiation process for deploying the VNF.

Steps 305b-305c: VNFM obtains VNFD and checks for instantiation parameters, if needed Make some modifications to the instantiation parameters.

In step 303, the NFVO may not directly read the related information about the clock interrupt requirement added in the VNFD, and the VNFM will parse the clock interrupt request from the VNFD in this step and send it to the NFVO.

Step 306a: NFVO selects a VIM that is considered to provide VNF with a resource that satisfies the demand. The "NFVI resource" database includes a record of the capabilities of the NFVI server, including the resource descriptions that the NFVI server can provide, including all the resources that can be provided, the resources that have been provided, the remaining available resources, and the resources that have been reserved. Wait.

Based on the records in the "NFVI resource" database, NFVO selects a VIM capable of managing the NFVI server that meets the VNF requirements. 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 requirements for computing, storage, and network resources, but also a VNF requirement for a clock interrupt (whether the VNF needs to directly access the hardware clock device to obtain a clock interrupt).

Step 306c: The VIM checks the status of the managed resources and returns the resource reservation result. In addition to considering the state of the computing, storage, and network resources, the VIM also considers the state of the clock resource that is managed. If the clock device is heavily loaded, step 306d may be performed, that is, the resource reservation failure indication is returned to the NFVO, NFVO. Re-execute steps 300-306c until the appropriate VIM is selected.

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

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

Steps 309a-309b: The VNFM creates and starts a virtual machine based on the VNFD request VIM, including installing a software package, executing a startup script, sending configuration data, and connecting the VM to the network.

Step 310a: If the VNF needs to adopt a clock interrupt if the VNF needs to directly access the hardware clock device, the VNFM sends a query request to the clock address manager, carries the VNF ID, and maps the ID of the physical device (may include one or more Information).

VNFM also needs to request the address of the clock address manager from NFVO for clock address management. Send a query request;

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

Steps 310b-310c: The clock address manager locally queries the address of the hardware clock that the VNF can directly access, and confirms the access authority of the VNF, and returns the result to the NFVO. The result includes the address of the hardware clock, and may also include the VNF access. Hardware clock cycle and duration configuration

^ I Ft is self-defeating.

Step 311: VNFM indicates the hardware clock address, access period and duration of time that the VNF can directly access.

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

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

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

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

Step 315: NFVO updates the "NFV Instances" and "NF VI resource" databases. Step 316: NFVO returns the VNF instantiation result to Sender.

According to the method for acquiring a clock interrupt signal provided by the embodiment of the present invention, the NFV function entity determines the clock interrupt precision requirement of the VNF according to the VNFD description information, and then the NFV function entity determines the hardware clock address for the VNF according to the clock interrupt precision requirement, and finally 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 the clock interrupt signal. No need to generate a virtual machine by calling the underlying hardware clock interrupt signal through the virtual machine The guest operating system software clock interrupt signal, and then the software clock interrupt signal is provided to the VNF for the VNF execution program to schedule the clock signal transmission process, thereby avoiding the delay of the clock signal and the delay jitter, ensuring the timeliness of the execution of the interrupt signal, and Ensure that the program is scheduled in time.

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

Step 400: Add a VNF requirement for clock interrupt accuracy in the VNFD. Through the VNF loading process, the VNFD is sent to the NFVO by the third party entity, and the NFVO submits the VNFD to the VNF directory, so that the NFVO and the VNFM acquire the VNF.歩 demand.

VNFD is a configuration template that describes the VNF deployment and operational behavior. It includes a description of the VNF deployment behavior and operational behavior configuration. The deployment behavior includes but is not limited to the deployment environment required by the VNF. Specifically, the VNF needs the NFVI resources. Such as the number of virtual machines, the number of virtual machine images, the required computing resources and storage resources. The operational behavior is primarily the behavior of the VNF lifecycle management process, including but not limited to VNF topology, startup and shutdown, functional scripts that match VNF lifecycle events, and so on.

Step 401: NFVO receives a request for instantiating a VNF sent by Sender.

This request is used to instantiate a new VNF;

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

Step 402: The NFVO verifies the validity of the request for instantiating the VNF sent by the Sender; wherein, the 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 legality of the instantiation request itself refers to whether the security parameter 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. VNF including reading the clock interrupt demand ₀

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

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

Step 405a: NFVO submits the instantiation parameters to VNFM.

Steps 405b-405c: VNFM takes VNFD and checks for instantiation parameters, and some modifications are made to the instantiation parameters if needed.

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

Step 406a: NFVO selects a VIM that is considered to provide the VNF with a resource that satisfies the demand. The "NFVI resource" database includes a record of the capabilities of the NFVI server, including the resource descriptions that the NFVI server can provide, including all the resources that can be provided, the resources that have been provided, the remaining available resources, and the resources that have been reserved. Wait.

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

Step 406c: The VIM checks the status of the managed resource and returns the resource reservation result. among them, In addition to considering the state of computing, storage, and network resources, VIM also considers the state of the clock resource that is managed. If the clock device is heavily loaded, step 406d can be performed, that is, the resource reservation failure indication is returned to NFVO, and NFVO is re-executed. Steps 400-406c, until the appropriate VIM is selected.

Step 407: If the VNF needs to directly access the hardware clock device to obtain a clock interrupt, 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 VNF. Access rights. Also configure the period and duration of the VNF access hardware clock.

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

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

Steps 410a-410b: The VNFM creates and starts a virtual machine based on the VNFD request VIM, including installing a software package, executing a startup script, sending configuration data, and connecting the VM to the network.

Step 411: VNFM indicates the hardware clock address, access period and duration of time that the VNF can directly access.

Step 412: The VNF accesses the hardware clock according to the indication of the VNFM, acquires a hardware clock interrupt, and schedules the program.

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

Steps 414a-414b: The NFVO performs resource status update based on the VNF instantiation result returned by the VNFM.

Step 415: NFVO updates the "NFV Instances" and "NF VI 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 FIG. 9, the clock address manager module can also be integrated in the hardware, as shown in FIG. Shown.

According to the method for obtaining a clock interrupt signal provided by the present invention, the NFV function entity determines the clock interrupt precision requirement of the VNF according to the VNFD description information, and then the NFV function entity locally queries the VNF to determine the hardware clock address, and then sends the determined hardware clock address. For the VNF, the VNF can access the hardware clock based on the obtained hardware clock address and obtain the clock interrupt signal. The virtual machine's guest operating system software clock interrupt signal is generated without calling the underlying hardware clock interrupt signal through the virtual machine, and then the software clock interrupt signal is provided to the VNF for the VNF to execute the program scheduling clock signal. The transmission process avoids the delay of the clock signal and the delay jitter, ensures the timeliness of the execution of the interrupt signal, and ensures that the program is scheduled in time.

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

Step 500: Add VNF to the VNFD requirements for clock interrupt accuracy. Through the VNF loading process, the VNFD is sent to the NFVO by the third-party entity, and the NFVO submits the VNFD to the VNF directory, so that the NFVO and the VNFM can acquire the VNF. Peer needs.

Step 501: NFVO receives a request for instantiating a VNF sent by Sender.

This request is used to instantiate a new VNF;

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

Step 502: The validity of the NFVO verification request.

The 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 legality of the Sender refers to whether the sender is authorized to send the request; The legality 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: NFVO reads the VNFD from the VNF directory, including the requirement to read the VNF for the clock interrupt.

Step 504: NFVO generates a VNF instance item and adds the generated instance item to the "NFV Inastances" database.

The VNF instance item is specifically used to query and maintain related information of the VNF instance according to the VNF instance item during the running of the VNF instance. Phase of the VNF instance The information about the NFVI resource used by the VNF instance and the running status and performance of the VM corresponding to the VNF instance.

Step 505a: NFVO submits the instantiation parameters to VNFM.

Steps 505b-505c: VNFM checks the instantiation parameters and obtains VNFD. It can also make some modifications to the instantiation parameters as needed.

In step 503, the NFVO may not directly read the related information about the clock interrupt requirement added in the VNFD. In this step, the VNFM parses the clock interrupt request from the VNFD and sends it to the NFVO.

Step 506a: NFVO selects a VIM that can provide the VNF with the required resources; wherein the "NFVI resource" database includes a record of the capabilities of the NFVI server, including a description of the resources that the NFVI server can provide, including all resources that can be provided. , resources already provided, remaining resources available, and reserved resources.

Step 506b: The NFVO sends a resource reservation request to the VIM that can provide the VNF with the required resource, which includes not only the VNF requirements for computing, storage, and network resources, but also the VNF requirement for the clock interrupt, which may be a VNF. Whether direct access to the hardware clock device is required to obtain a clock interrupt.

Step 506c: The VIM checks the status of the managed resource and returns the resource reservation result. If the VNF needs to obtain a 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 access hardware clock. In addition to considering the state of computing, storage, and network resources, VIM also considers the state of the clock resource that is managed. If the clock device is heavily loaded, step 506d can be performed to return the resource reservation failure indication to NFVO, and NFVO is re-executed. Steps 500-506c, until the appropriate VIM is selected.

Step 507: NFVO configures the period and duration of the VNF access hardware clock.

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

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

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

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

Step 511: VNFM indicates the hardware clock address, access period and duration that the VNF can directly access.

Step 512: The VNF accesses the hardware clock according to the instructions of the VNFM, acquires a hardware clock interrupt, 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 "NF VI resource" databases. Step 516: NFVO returns the VNF instantiation result to Sender.

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

According to the method for obtaining a clock interrupt signal provided by the present invention, the NFV function entity determines the clock interrupt precision requirement of the VNF according to the VNFD description information, and selects a VIM that can provide a resource, and the VIM returns a hardware clock address and configuration information, and the VNF can be obtained according to the VNF. The hardware clock address accesses the hardware clock and acquires a clock interrupt signal. Without calling the underlying hardware clock interrupt letter through the virtual machine The virtual machine's guest operating system software clock interrupt signal is generated, and the software clock interrupt signal is provided to the VNF for VNF execution program scheduling clock signal transmission process, thereby avoiding the delay of the clock signal and delay jitter, and ensuring the execution of the interrupt signal. Timeliness and guarantee that the program is scheduled in time.

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

The first determining module 101 is configured to determine, according to the VNFD description information, a clock interrupt precision requirement of the VNF;

a second determining module 102, configured to determine a hardware clock address for the VNF according to the clock interrupt precision requirement;

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

Specifically, the NFV functional entity is NFVO or VNFM.

As shown in FIG. 15, the NFV functional entity may further include: a third determining module 104, configured to determine, by the second determining module 102, the hardware for the VNF according to the clock interrupt precision requirement. Before the clock address, according to the clock interruption precision requirement of the VNF, determining whether the VNF needs to directly access the hardware clock;

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

Optionally, the sending module is specifically configured to:

As shown in FIG. 16, the foregoing NFV functional entity may further include: a first receiving module 105, configured to receive the hardware clock address returned by the clock address manager.

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

As shown in FIG. 17, for the NFV function entity, the NFV function entity is the NFVO, which may further include: a storage module 106, configured to store information of a hardware clock; The second determining module 102 is specifically configured to determine, according to the information about the hardware clock stored by the storage module 106, the hardware clock address that the VNF can directly access.

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

Optionally, the sending module 103 is further configured to: after the address of the hardware clock is sent to the VNF, send an access period and an access duration of the VNF to the hardware clock address to the The NFV functional entity is the NFV functional entity

NFVO, which can also be further included:

The fifth determining module 108 is configured to determine, after the second determining module 102 determines the hardware clock address for the VNF according to the clock interrupt precision requirement, according to the clock interrupt precision requirement of the VNF, determine that the VNF requirement resource is satisfied. VIM;

Further, the sending module 103 is further configured to send a resource reservation request to the VIM, and further include a second receiving module 109, configured to receive a resource reservation result returned by the VIM, where the resource reservation result is Carry the identity of the physical device.

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

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

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

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

Further, the resource reservation result further includes: an access period and an access duration of the VNF to the hardware clock address.

As shown in FIG. 21, for the 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, according to the second determining module 102, the hardware clock address from the resource reservation result, the access period and the access duration of the VNF to the hardware clock address.

The NFV function entity provided in this embodiment is an execution device of the method for acquiring a clock interrupt signal provided by the embodiment of the present invention. For the specific process of the method for acquiring the clock interrupt signal, refer to FIG. 1 and FIG. 2 to FIG. The related description in the method embodiment is not described here.

FIG. 22 is a schematic diagram showing the structure of a network function virtualization NFV function entity provided by the present invention. As shown in FIG. 22, the NFV function 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 execution instructions in the memory 22 for performing the following operations:

Determining the clock interruption accuracy requirement of the VNF according to the VNFD description information;

Determining, according to the clock interrupt precision requirement, a hardware clock address for the VNF; sending an address of the hardware clock to the VNF, so that the VNF accesses the hardware clock according to an address of the hardware clock to obtain a clock Interrupt signal.

The NFV functional entity is NFVO or VNFM.

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

Determining whether the VNF needs direct access to the hardware clock according to the clock interruption accuracy requirement of the VNF;

If it is determined that the NFVO or VNFM requires direct access to the hardware clock, the hardware clock address is determined 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, and specifically includes:

Receiving 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 an access period and an access duration of the VNF returned by the clock address manager to the hardware clock address. Optionally, the processor 21 may further store the information of the hardware clock, and the processor 21 determines the hardware clock address for the VNF according to the clock interrupt precision requirement of the VNF, and specifically includes: the processor 21 according to the stored location The information of the hardware clock determines the hardware clock address that the VNF can directly access.

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

The processor 21 determines an access period and an 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, the method further includes:

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

The processor 21 determines, according to the clock interruption precision requirement of the VNF, a VIM that satisfies the VNF requirement resource;

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, the method 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 determining, by the processor 21, the hardware clock address for the VNF, specifically: the NFVO acquiring the hardware clock address from the resource reservation result.

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

The processor 21 determines an access period and access time of the VNF to the hardware clock address Long.

The NFV functional entity provided by the embodiment of the present invention may be used to implement the technical solution of the foregoing method embodiment, and the implementation principle and the technical effect are similar, and details are not described herein again.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be implemented by hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, when executed, The foregoing storage unit includes: a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like can store program codes. Medium.

Finally, it should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting thereof; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that The technical solutions described in the foregoing embodiments may be modified, or some or all of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the technical solutions of the embodiments of the present invention. range.

Claims

claims

1. A method for obtaining a clock interrupt signal, which is characterized by including:

The network function virtualization NFV functional entity determines the clock interrupt accuracy requirements of the virtualized network function VNF based on the description information in the virtual network function requirement description file VNFD;

The NFV functional entity determines the hardware clock address for the VNF according to the clock interrupt accuracy 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, characterized in that 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, characterized in that, before determining the hardware clock address for the VNF according to the clock interrupt accuracy requirement, the NFV functional entity further includes:

The NFV functional entity determines whether the VNF needs to directly access the hardware clock based on the clock interrupt accuracy requirements of the VNF;

If it is determined that the NFVO or VNFM needs to directly access the hardware clock, the NFVO or VNFM

The VNFM determines the hardware clock address for the VNF.

4. The method according to claim 2, characterized in that the NFV functional entity determines a hardware clock address for the VNF according to the clock interrupt accuracy requirement of the VNF, specifically including: the NFVO or VNFM reporting to a clock address manager Send a query request, which carries the identification information of the VNF and the identification information of the physical device mapped by the VNF;

5. The method according to claim 4, characterized in that, 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.

6. The method according to claim 2, characterized in that, the NFV functional entity stores hardware clock information, and the NFV functional entity determines the hardware clock address for the VNF according to the clock interrupt accuracy requirement of the VNF, specifically include:

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

7. The method according to claim 6, characterized in that, after the NFV functional entity determines the hardware clock address that the NFV can directly access based on 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, characterized in that, after the NFV functional entity sends the address of the hardware clock to the VNF, it further includes:

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

9. The method according to claim 2, characterized in that, before determining a hardware clock address for the VNF according to the clock interrupt accuracy requirement, the NFV functional entity further includes:

The NFVO determines the virtualization infrastructure manager VIM that meets the resources required by the VNF according to the clock interrupt accuracy requirement 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 identification 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 identification of the physical device, it also includes:

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

11. The method according to claim 9 or 10, characterized in that the resource reservation result includes: the hardware clock address;

The NFV functional entity determines a hardware clock address for the VNF, which specifically includes: the NFVO obtains the hardware clock address from the resource reservation result.

12. The method according to claim 11, characterized in that the resource reservation result further includes: the access cycle and access duration of the VNF to the hardware clock address.

13. The method according to claim 11, characterized in that, after the NFV functional entity obtains the hardware clock address from the resource reservation result, it further includes:

14. A network function virtualization NFV functional entity, which is characterized by including:

The first determination module is used to determine the clock interrupt accuracy of the VNF based on the VNFD description information. need;

The second determination module is used to determine the hardware clock address for the VNF according to the clock interrupt accuracy 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 functional entity according to claim 14, characterized in that the NFV functional entity is NFVO or VNFM.

16. The NFV functional entity according to claim 15, further comprising: a third determination module, configured to determine a hardware clock address for the VNF according to the clock interrupt accuracy requirement in the second determination module Previously, it was determined whether the VNF needed to directly access the hardware clock based on the clock interrupt accuracy requirements of the VNF;

The second determination module is also used 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 functional entity according to claim 15, characterized in that the sending module is specifically used for:

Send a query request to the clock address manager, the query request carrying the identification information of the VNF and the identification information of the physical device mapped by the VNF;

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

18. The NFV functional entity 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 cycle and access duration of the VNF to the hardware clock address returned by the clock address manager.

19. The NFV functional entity according to claim 15, wherein the NFV functional entity is the NFVO, and the NFVO further includes:

Storage module, used to store hardware clock information;

The second determination module is specifically: based on the stored information of the hardware clock, determine the hardware clock address that the VNF can directly access.

20. The NFV functional entity according to claim 19, wherein the NFV functional entity is the NFVO, and the NFVO further includes: The fourth determination module is configured to determine the access cycle and access duration of the VNF to the hardware clock address after determining the hardware clock address that the NFV can directly access according to the second determination module.

21. The NFV functional entity according to claim 18 or 20, wherein the NFV functional entity is the NFVO, and the sending module is further configured to send the address of the hardware clock to the After the VNF, the access cycle and access duration of the VNF to the hardware clock address are sent to the VNF.

22. The NFV functional entity according to claim 15, wherein the NFV functional entity is the NFVO, and the NFVO further includes:

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

The sending module is also used to: send a resource reservation request to the VIM;

It also includes a second receiving module, configured to receive the resource reservation result returned by the VIM, where the resource reservation result carries the identification of the physical device.

23. The NFV functional entity according to claim 22, wherein the NFV functional entity is the VNFM, and the VNFM further includes: a request module, configured to receive in the fifth determination module After the resource reservation result returned by the VIM carries the identification of the physical device, the VIM is requested to create and start a virtual machine.

24. The NFV functional entity according to claim 22 or 23, characterized in that:

The NFV functional entity is the NFVO, and the resource reservation result includes: the hardware clock address; and the second determination module is specifically configured to: obtain the hardware clock address from the resource reservation result.

25. The NFV functional entity according to claim 24, wherein the resource reservation result further includes: the access cycle and access duration of the VNF to the hardware clock address.

26. The NFV functional entity according to claim 24, wherein the NFV functional entity is the NFVO, and the NFVO further includes:

A sixth determination module, 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 functional entity, 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 processor and the memory communication, the processor executes the execution instruction to cause the clock interrupt signal acquisition system to execute the method according to any one of claims 1 to 13.