WO2014194753A1

WO2014194753A1 - Method, device and system for generating service path

Info

Publication number: WO2014194753A1
Application number: PCT/CN2014/077696
Authority: WO
Inventors: 夏寅贲; 陈国义; 朱明明
Original assignee: 华为技术有限公司
Priority date: 2013-06-08
Filing date: 2014-05-16
Publication date: 2014-12-11
Also published as: CN104243301B; CN104243301A

Abstract

Disclosed are a method, a device and a system for generating a service path. The method comprises: a path computation element (PCE) receiving a path computation request (PCReq) message sent by a path computation client (PCC), the PCReq message comprising network function virtualization (NFV) function demand information; and the PCE generating a service path according to a network function virtualization database (NFVDB), an NFV function entity conforming to the NFV function demand information is on the service path. The embodiments of the present invention have the following beneficial effects: when a user service is changed, a PCE obtains NFV function demand information in a PCReq message sent by a PCC, and generates, according to an NFVDB, a service path conforming to an NFV function entity required in the NFV function demand information, so as to dynamically configure a service path of a user, and compared with static configuration of the service path of the user, the difficulty of configuration and maintenance is reduced.

Description

Method, device and system for generating business path

The present application claims priority to Chinese Patent Application No. CN 201310228225.8, entitled "A Method, Apparatus and System for Generating a Service Path", which is filed on June 8, 2013, the entire contents of which are incorporated by reference. Combined in this application.

Technical field

The present invention relates to the field of communications technologies, and in particular, to a method, device, and system for generating a service path. Background technique

The traditional carrier network includes many dedicated hardware devices with different functions, such as firewall servers, load balancing servers, Net Address Translation (NAT) servers, and Domain Name System (DNS) servers. In order to provide customers with personalized network services, operators often need to plan and deploy hardware devices located in different locations on the network. Due to the flexibility of network services, in order to adapt to a variety of network services, this pre-planning deployment and configuration becomes more and more complicated. In addition, when a new network service is provided, it may be necessary to integrate and deploy new hardware devices in the network to support new network services. In addition to complex integration and deployment work, it is necessary to arrange appropriate space and distribution. Electricity to match new hardware devices makes implementation difficult. At the same time, operators are also aware that as technology advances, the life cycle of hardware devices becomes shorter and shorter, and the elimination is faster and faster, increasing the cost of operations.

In order to solve the above problem of the traditional carrier network, Network Function Virtualization (NFV) technology has attracted the attention of operators. NFV technology is a network function that runs on software on a range of industry standard servers and can be used as needed Software that runs this network function is installed and uninstalled on servers in different locations on the network, so there is no longer a need to install new hardware devices. Through NFV technology, operators' costs and expenses are reduced, network new service deployment and time to market are shortened, and business changes are more flexible.

In the NFV scenario, NFV functional entities can run on different hardware platforms. Generally, operators provide various service services to users through static programming, that is, pre-configure users to NFV functional entities. However, because NFV functional entities can flexibly migrate between different hardware platforms, Each change of the user's path to the NF V functional entity is implemented through static configuration, and the service requirements of different users are also different. The service path of the NFV functional entity that different users pass through is also different. The operator needs to maintain each user to The path configuration information of the NVF functional entity. Therefore, in the prior art, the method of planning the user's service path by static configuration causes complicated configuration and difficult maintenance, which is not conducive to the development and application of the NFV technology.

Summary of the invention

The embodiments of the present invention provide a method, a device, and a system for generating an NFV service path, which are beneficial to solving the technical problem of complicated configuration and difficult maintenance caused by planning a user's service path in a static configuration manner in the prior art.

The first aspect provides a method for generating a service path, where the method includes: a Path Computation Element (PCE) receives a path calculation request (Path Computation Request) sent by a Path Computation Client (PCC) , PCReq) message, the PCReq message includes Network Function Virtualization (NFV) function requirement information;

The PCE generates a service path according to a Network Function Virtualization Database (NFVDB), and an NFV function entity that conforms to the NFV function requirement information is on the service path.

With reference to the first aspect, in a first possible implementation manner of the foregoing aspect, before the PCE receives the PCReq message sent by the PCC, the method further includes: Receiving, by the PCE, a resource registration message sent by the NFV function entity, where the resource registration message carries resource information, function description, and location information of the NFV function entity; the PCE describes the resource information and the function description And the location information is added to the NFVDB.

In conjunction with the first aspect or the first possible implementation of the first aspect, a second possible implementation of the first aspect is also provided, a second possible In an implementation manner, before the PCE receives the PCReq message sent by the PCC, the PCE further includes: the PCE pre-sets a Traffic Engineer Database (TEDB) and a Label Switch Path Database (LSPDB);

The generating, by the PCE, the service path according to the NFVDB, specifically: the PCE selects resource registration information of the NF V functional entity that meets the NF V function requirement information from the NFVDB, and according to the TEDB, LSPDB Generating the service path with the resource registration information.

A third possible implementation of the first aspect is also provided in combination with the first aspect or any one of the above possible implementations of the first aspect, a third possible aspect of the first aspect In an implementation manner, the PCReq message further includes NFV capacity requirement information or NF V execution order requirement information.

With reference to the first aspect, in a fourth possible implementation manner of the first aspect, the method further includes:

The PCE sends the information of the service path to the PCC through a Path Computation Reply (PCRep) message, and instructs the PCC to establish a forwarding path according to the information of the service path. A second aspect provides a method for generating a service path, where the method includes:

The PCC sends a PCReq message to the PCE, where the PCReq message includes NFV function requirement information, so that the PCE generates a service path that meets the NFV function requirement information; Receiving a PCRep message sent by the PCE, where the PCRep message includes information of the service path, and the PCC generates a forwarding path according to the information of the service path.

In conjunction with the second aspect, in a first possible implementation manner of the second aspect, the PCReq message further includes NFV capacity requirement information or NFV execution sequence requirement information.

In a third aspect, a path calculation unit PCE is provided, including:

a receiving unit, configured to receive a PCReq message sent by the PCC, where the PCReq message includes NFV function requirement information;

And a processing unit, configured to generate a service path according to the NFVDB, where the NFV functional entity that meets the NFV function requirement information is on the service path.

With reference to the third aspect, in a first possible implementation manner of the third aspect, the receiving unit is further configured to receive a resource registration message that is sent by the NFV function entity, where the resource registration message carries the The resource information, the function description, and the location information of the NFV functional entity; the processing unit is further configured to add the resource information, the function description, and the location information to the NFVDB.

With the third aspect or the first possible implementation manner of the foregoing third aspect, the second possible implementation manner of the foregoing third aspect is provided, and the second possible implementation manner of the third aspect The PCE further includes a setting unit, configured to set a TEDB and an LSPDB before the receiving unit receives the PCReq message sent by the PCC;

The processing unit is specifically configured to select, from the NFVDB, resource registration information of the NFV functional entity that meets the NFV function requirement information, and generate the service path according to the TEDB, the LSPDB, and the resource registration information. .

In conjunction with the third aspect, the first possible implementation of the third aspect, or the second possible implementation of the third aspect, a third possible implementation manner of the third aspect is provided In a third possible implementation manner of the third aspect, the PCReq message further includes NFV capacity requirement information or NFV execution sequence requirement information.

With reference to the third aspect, in a fourth possible implementation manner of the foregoing third aspect, And a sending unit, configured to send the information of the service path to the PCC by using a PCRep message, and instruct the PCC to establish a forwarding path according to the information of the service path.

In a fourth aspect, a path calculation client PCC is provided, including:

a sending unit, configured to send a PCReq message to the PCE, where the PCReq message includes NFV function requirement information, so that the PCE generates a service path that meets the NFV function requirement information;

a receiving unit, configured to receive a PCRep message sent by the PCE, where the PCRep message includes information about the service path;

And a processing unit, configured to generate a forwarding path according to the information of the service path.

In combination with the fourth aspect, in a first possible implementation manner of the fourth aspect, the PCReq message further includes NF V capacity requirement information or NF V execution order requirement information.

A fifth aspect provides a system for generating a service path, where the system includes a PCE and a PCC, where

The PCE is configured to receive a PCReq message sent by the PCC, generate a service path according to the NFVDB, and send the information of the service path to the PCC by using a PCRep message, where the PCReq message includes NFV function requirement information, and is consistent with The NFV functional entity of the NFV function requirement information is on the service path;

The PCC is configured to send the PCReq message to the PCE, receive the PCRep message sent by the PCE, and generate a forwarding path according to the information of the service path, where the PCReq message includes NFV function requirement information, to facilitate The PCE generates a service path that meets the NFV function requirement information; the PCRep message includes information of the service path.

The beneficial effects of the embodiment of the present invention are as follows: When the user service changes, the PCE obtains the PCR service sent by the PCC to obtain the requirement of the user service for the NFV functional entity, and then generates the service path according to the NF VDB, and conforms to the NF V function of the user service. The required NF V function entity is on the service path. When the NFV function entity moves in the location, the PCE receives the resource registration message sent by the NFV function entity, according to the NFV carried in the resource registration message. The information of the functional entity, such as the resource information, the function description, and the location information, is updated to the NFVDB, so as to dynamically configure the service path of the user, and solve the problem of complicated configuration and difficult maintenance caused by planning the user's service path through static configuration in the prior art. problem.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described. It is obvious that the drawings in the following description are only some embodiments of the present invention. Other drawings may also be obtained from those of ordinary skill in the art in light of the inventive work. 1 is a flowchart of a method for generating a service path according to an embodiment of the present invention; FIG. 2 is a flowchart of an implementation manner of a method for generating a service path shown in FIG. 1; A flowchart of another implementation manner of a method for generating a service path; FIG. 5 is a flowchart of another method for generating a service path according to an embodiment of the present invention; FIG. 6 is a PCE receiving resource according to Embodiment 6 of the present invention; FIG. 7 is a schematic diagram of a PCE receiving the PCReq message and transmitting the PCRep message according to Embodiment 6 of the present invention;

FIG. 8 is a schematic structural diagram of a first type of the PCE according to an embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of a first type of the PCC according to an embodiment of the present disclosure;

FIG. 10 is a schematic structural diagram of a second type of the PCE according to an embodiment of the present disclosure;

FIG. 11 is a schematic structural diagram of a second type of the PCC according to an embodiment of the present invention; FIG. 12 is a schematic structural diagram of a system for generating a service path according to an embodiment of the present invention. detailed description The technical solutions in the embodiments of the present invention are clearly described in conjunction with the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are Some embodiments, rather than all of the embodiments, are invented. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without departing from the inventive scope are the scope of the present invention. In order to solve the technical problem of the network configuration and maintenance in the prior art, the configuration of the network virtualization technology is provided in the embodiment of the present invention by using a static configuration manner to plan a technical problem that the configuration of the user's service path is complicated and difficult to maintain. Business path plan. In the solution for the user service, the PCE obtains the PCReq message sent by the PCC, obtains the requirement of the user service for the NFV functional entity, and then generates the service path according to the NFVDB, and the NFV functional entity that meets the NFV function requirement of the user service is in the service. On the path; when the NF V functional entity migrates (for example, from one virtual machine to another virtual machine), the PCE receives the resource registration message sent by the NFV function entity, according to the NFV carried in the resource registration message. The information of the functional entity, such as the resource information, the function description, and the location information, is updated with the NFVDB; thereby realizing the dynamic configuration of the user's service path, and solving the problem of complicated configuration and difficult maintenance caused by planning the user's service path through static configuration in the prior art. problem. Referring to FIG. 1, an embodiment of the present invention provides a method for generating a service path. The method includes: 101. A PCE receives a PCReq message sent by a PCC, where the PCReq message includes NFV function requirement information.

102. The PCE generates a service path according to the NFVDB, and the NFV functional entity that meets the NFV function requirement information is on the service path.

Optionally, before the PCE receives the PCReq message sent by the PCC, the method further includes:

201. The PCE receives a resource registration message sent by the NFV function entity, where the resource registration message carries resource information, function description, and location information of the NFV function entity. 202. The PCE adds the resource information, the function description, and the location information to the NFVDB.

Receiving, by the PCE, the resource registration message sent by the NFV function entity, and updating the NFVDB according to the resource registration message, ensuring that the data in the NFVDB is valid data, which is beneficial to the service path calculation. Correctness and reliability.

Optionally, the resource registration message may be an extension of the PCEP message, and the PCEP message format is referred to the RFC 5440 issued by the IETF, where the resource registration message includes the following content:

<register-list>: :=<register> [<register-list>]

<resources>: :=<processor> <storage> <bandwidth> <interface>;

The NFV ID is an identifier of the NFV functional entity that sends the resource registration message, the functions are function descriptions of the NFV functional entity, the resources are resource information of the NFV functional entity, and the location is the NFV functional entity. location information.

It should be noted that the content of the resource registration message shown in the above example is only for clearer and more intuitive description of the resource registration message, and is not intended to limit the present invention. Those skilled in the art should be able to understand other methods consistent with the present invention. The format of the resource registration message (e.g., using different languages or different naming rules, etc.) or content changes may also achieve the object of the present invention, and when its implementation conforms to the idea of the present invention, it is still within the scope of the present invention.

The above steps in this embodiment are only a preferred combination for implementing the present invention. When used to periodically update the NFVDB, steps 201 and 202 may also be performed again or multiple times after completing steps 101 and 102. In this case, it is to maintain the validity of the NFVDB in order to prepare for the calculation of the next business path. Or, execute when the NFV functional entity is migrated. For example, when an NFV functional entity is migrated from one virtual machine to another virtual machine, resource information, function description, and location information of the NFV functional entity may occur. Change, at this time it is necessary to update the NFVDB; or the service path of the NFV functional entity changes due to the migration of the NFV functional entity, it is necessary to recalculate the service path at this time, of course, the above two situations can also occur simultaneously.

Optionally, referring to FIG. 3, before the PCE of the step 101 receives the PCReq message sent by the PCC, the method further includes:

301. The PCE presets the TEDB and the LSPDB.

After receiving the PCReq message sent by the PCC, the PCE of step 101 further includes:

302. The PCE selects, from the NFVDB, resource registration information of the NFV functional entity that meets the NFV function requirement information.

Step 102 includes: the PCE generating the service path according to the TEDB, the LSPDB, and the resource registration information of the NFV functional entity that meets the NFV function requirement information.

For the calculation of the service path in the network, the PCE is divided into a stateful PCE (Stateful PCE) and a stateless PCE. The stateless PCE uses the TEDB information to perform the forwarding path calculation. The information contained in the TEDB mainly includes the network topology and the link. The remaining bandwidth on the above, based on the above information, the stateless PCE can calculate the shortest path that satisfies the bandwidth requirement for the current request. In addition, the state-of-the-art PCE not only has the TEDB, but also obtains the LSPDB of the existing label switching path (LSP) and its storage status information on the network. The path can be adjusted according to the actual situation of the network.

In this embodiment, according to the TEDB, the LSPDB, and the NFVDB, the existing PCE computing service path capability is extended. When the user service is changed, the PCE can obtain the NFV function requirement information in the PCReq message sent by the PCC, and generate a conformity according to the NFVDB. The service path of the NF V functional entity required by the NFV function requirement information is implemented to dynamically configure the user's service path, which reduces the difficulty of configuration and maintenance compared to the static configuration of the user's service path.

Optionally, the PCReq message further includes NFV capacity requirement information or an NFV execution sequence. demand information. The PCReq message may refer to the RFC 5440 published by the IETF. The PCReq message in the embodiment of the present invention includes the following content:

<sequence-request> ...

Wherein, the functions-request is the NFV function requirement information, the apability-reques is the NFV capacity requirement information, and the sequence-request is the NF V execution order requirement information.

Optionally, referring to FIG. 4, the method further includes:

401. The PCE sends the information of the service path to the PCC by using a PCRep message, and instructs the PCC to establish a forwarding path according to the information of the service path.

The beneficial effects of the embodiment of the present invention are as follows: when the user service is changed, the PCE acquires the NFV function requirement information in the PCReq message sent by the PCC, and generates a service path according to the NFVDB, the service path The NFV function entity meets the requirements of the NFV function requirement information, thereby dynamically configuring the user's service path, and reducing the difficulty of configuration and maintenance relative to the static configuration of the user's service path. Referring to FIG. 5, an embodiment of the present invention provides a method for generating a service path, where the method includes:

501. The PCC sends a PCReq message to the PCE, where the PCReq message includes NFV function requirement information, so that the PCE generates a service path that meets the NFV function requirement information.

502. Receive the PCRep message sent by the PCE, where the PCRep message includes information of a service path, and the PCC generates a forwarding path according to information of the service path.

Optionally, the PCReq message further includes NFV capacity requirement information or NFV execution order requirement information, and the PCReq message format is referred to the PCReq message format as above.

The beneficial effects of the embodiment of the present invention are as follows: When the service of the user changes, the PCC sends the NFV function requirement information related to the service of the user to the PCE. After the PCE completes the service path calculation, the PCE sends a forwarding path according to the PCRep message sent by the PCE, and cooperates with the PCE. The configuration of the service path of the user is dynamically configured. Compared with the service path of the static configuration user, the configuration and maintenance are difficult. The embodiments of the present invention will be described more clearly and will now be illustrated. Referring to FIG. 6, a schematic diagram of a PCE server receiving a resource registration message sent by an NFV function entity is shown in FIG. 7. After the user service is changed, the PCE receives a PCReq message sent by the PCC and sends a PCRep message to the PCC, as follows:

The NFV functional entity is set on the virtual machines VM1 to VM5, and to the PCC1 on the network side.

The PCC6 has a connection relationship as shown in FIG. 6; at the same time, the users UE1 to UE4 and the network side PCC1 to PCC6 have a connection relationship as shown in FIG. 6, where UE1 corresponds to service 1, UE2 corresponds to service 2, and UE3 corresponds to service 3. , UE4 corresponds to service 4. In this case, in the schematic diagram of the PCE receiving the NF V function entity sending the resource registration message, the resource registration message may be an extension of the PCEP message, where the resource registration message may carry the resource of the NFV functional entity. Information, function description and location information, the resource registration message contains the following: <Register Message>: :=<Common Header> <register-list>

<register-list>: :=<register> [<register-list>]

<resources>: :=<processor> <storage> <bandwidth> <interface>;

The NFV ID is an identifier of the NFV functional entity that sends the resource registration message, the functions are the function descriptions of the NFV functional entity, and the resources are the resource information of the NFV functional entity, where the location is The location information of the NFV functional entity.

When the service of the UE1 is changed from the service 1 shown in FIG. 6 to the service 2 shown in FIG. 7, the PCeq server receives the PCReq message sent by the PCC and the PCRep message sent to the PCC in the schematic diagram of the PCReq message. The NFV function information, capacity information, and execution order information required to carry the user-initiated NF V service may be carried in the following message format: <NFV request>: := <PR> <functions-request>

Wherein function-request is the NFV function requirement information.

Of course, the PCReq message may carry the user-initiated NFV service required by the a combination of NFV function information, the capacity information, and the execution order information or any combination of the information, the PCReq message may include:

<sequence-request> ...

Among them, apability-reques is NFV capacity requirement information, and sequence-request is NFV execution order requirement information.

The PCE obtains the NFV function requirement information in the received PCReq message, and generates a service path according to the NF V function requirement information, the NF VDB, the TEDB, and the LSPDB.

The NF V functional entity of the NF V functional requirements information is on this business path.

The beneficial effects of the embodiments of the present invention are as follows: The PCE in the network updates the NFVDB after receiving the resource registration message of the NFV function entity (such as the NFV function entity set on the virtual machines VM1 to VM5 in FIG. 6), and when the user service changes, the PCE Obtaining NFV function requirement information in the PCReq message sent by the PCC connected to the user (the NFV function requirement information is determined by the user service), thereby generating a service path conforming to the NFV function entity required by the NFV function requirement information according to the NFVDB. Therefore, the service path of the user is dynamically configured, which reduces the difficulty of configuration and maintenance compared to the static configuration of the user's service path. Referring to FIG. 8, an embodiment of the present invention provides a PCE 800, where the PCE 800 includes: a receiving unit 801, configured to receive a PCReq message sent by a PCC, where the PCReq message includes NFV function requirement information;

The processing unit 802 is configured to generate a service path according to the NFVDB, and the NFV functional entity that meets the NFV function requirement information is on the service path.

Optionally, the receiving unit 801 is further configured to receive a resource registration message sent by the NFV function entity, where the resource registration message carries resource information, function description, and location information of the NFV function entity;

The processing unit 802 is further configured to add the resource information, the function description, and the location information to the NFVDB. Optionally, the PCE further includes a setting unit 803, configured to: before receiving the PCReq message sent by the PCC, set a TEDB and an LSPDB;

The processing unit 802 is specifically configured to select, from the NFVDB, the resource registration information of the NFV functional entity that meets the NFV function requirement information, and according to the TEDB, the L SPDB, and the receiving unit. The resource registration information received by the 801 generates a service path.

Optionally, the PCReq message further includes NFV capacity requirement information or NFV execution order requirement information.

Optionally, the sending unit 804 is further configured to send information about the service path generated by the processing unit 802 to the PCC by using a PCRep message, and instruct the PCC to establish a forwarding path according to the information of the service path.

The PCE 800 provided by the embodiment provides an extension of the existing PCE computing service path capability according to the TEDB, the LSPDB, and the NFVDB. When the user service changes, the receiving unit 801 of the PCE acquires The NFV function requirement information in the PCReq message sent by the PCC, the processing unit 802 generates, according to the NFVDB, a service path that meets the NF V function entity required in the NF V function requirement information. Further, the sending unit 804 of the PCE may send the information of the service path generated by the processing unit 802 to the PCC by using a PCRep message, and instruct the PCC to establish a forwarding path according to the information of the service path; Dynamically configuring the user's service path reduces the difficulty of configuration and maintenance compared to statically configuring the user's service path. Referring to FIG. 9, an embodiment of the present invention provides a PCC900, including:

a sending unit 901, configured to send a PCReq message to the PCE, where the PCReq message includes

NFV function requirement information, so that the PCE generates a service path that meets the NFV function requirement information;

The receiving unit 902 is configured to receive a PCRep message sent by the PCE, where the PCRep The message includes information of the service path;

The processing unit 903 is configured to generate a forwarding path according to the information of the service path.

The PCC900 provided in this embodiment, when the user's service changes, the sending unit

The 901 sends the NF V function requirement information related to the service of the user to the PCE. After the PCE completes the service path calculation, the receiving unit 902 receives the PCRep message sent by the PCE, and the processing unit 903 is configured according to the PCRep. The message is set up with a forwarding path, and the PCE is configured to dynamically configure the service path of the user. Compared with the static configuration of the service path of the user, the configuration and maintenance are difficult. Referring to FIG. 10, an embodiment of the present invention provides a PCE1000, including:

The receiver 1001 is configured to receive a PCReq message sent by the PCC, where the PCReq message includes NFV function requirement information;

The processor 1002 is configured to generate a service path according to the NFVDB, where the NFV functional entity that meets the NFV function requirement information is on the service path.

Optionally, the receiver 1001 is further configured to receive a resource registration message sent by the NFV function entity, where the resource registration message carries resource information, function description, and location information of the NFV function entity;

The processor 1002 is further configured to add the resource information, the function description, and the location information to the NFVDB.

Optionally, the processor 1002 is configured to: before the receiver 1001 receives the PCReq message sent by the PCC, the TEDB and the LSPDB;

Selecting resource registration information of the NFV functional entity that meets the NFV function requirement information from the NFVDB, and generating the service path according to the TEDB, the LSPDB, and the resource registration information. Optionally, it also includes:

The sender 1003 is configured to send, by using a PCRep message, the information of the service path to the PCC, and instruct the PCC to establish a forwarding path according to the information of the service path.

The PCE 1000 provided by the embodiment provides an extension of the existing PCE computing service path capability according to the TEDB, the LSPDB, and the NFVDB. When the user service changes, the receiver 1001 of the PCE acquires The NFV function requirement information in the PCReq message sent by the PCC, the processor 1002 generates a service path according to the NFVDB, and the function entity on the service path meets the requirement of the NF V function requirement information, Further, the transmitter 1003 of the PCE may send the information of the service path generated by the processor 1002 to the PCC by using a PCRep message, and instruct the PCC to establish a forwarding path according to the information of the service path; Configuring the service path of the user reduces the difficulty of configuration and maintenance compared to the service path of the static configuration user. Referring to FIG. 11, an embodiment of the present invention provides a PCC2000, including:

The transmitter 2001 is configured to send a path calculation request PCReq message to the path calculation unit PCE, where the PCReq message includes network function virtualization NFV function requirement information, so that the PCE generates a service path that meets the NF V function requirement information;

The receiver 2002 is configured to receive a path calculation reply PCRep message sent by the PCE, where the PCRep message includes information about the service path;

The processor 2003 is configured to generate a forwarding path according to the information of the service path.

The PCC2000 provided in this embodiment, when the user's service changes, the transmitter

Sending, by the PCE, the NF V function requirement information related to the service of the user to the PCE, after the PCE completes the service path calculation, the receiver 2002 receives the PCRep message sent by the PCE, and the processor 2003 according to the PCRep The message is set up with a forwarding path, and the PCE is configured to dynamically configure the service path of the user. Compared with the static configuration of the service path of the user, the configuration and maintenance are difficult. Referring to FIG. 12, an embodiment of the present invention provides a system 3000 for generating a service path, where the system includes:

The PCE3001 is configured to receive a PCReq message sent by the PCC, generate a service path according to the NFVDB, and send the information of the service path to the PCC by using the PCRep message, where the PCReq message includes NF V function requirement information, and the NF is met. The NFV functional entity of the V function requirement information is on the service path;

The PCC 3002 is configured to send the PCReq message to the PCE 3001, receive a PCRep message sent by the PCE 3001, and generate a forwarding path according to the information of the service path, where the PCReq message includes the NFV function requirement information, The PCE 3001 is configured to generate a service path that meets the NFV function requirement information; the PCRep message includes information of a service path.

In the system 3000 for generating a service path provided by the embodiment, the PCE 3001 implements the extension of the existing service path capability of the PCE 3001 according to the TEDB, the LSPDB, and the NFVDB. When the user service changes, the PCE 3001 can acquire the NFV in the PCReq message sent by the PCC 3002. The function requirement information is generated according to the NFVDB, and the NFV function entity on the service path meets the requirements of the NFV function requirement information; when the user service changes, the PCC3002 sends the NFV function requirement information related to the service of the user to the PCE3001. After the PCE3001 completes the service path calculation, it establishes a forwarding path based on the PCRep message sent by the PCE3001, and dynamically configures the service path of the user with the PCE3001. The PCE3001 and the PCC3002 cooperate to dynamically configure the service path of the user. , reducing the difficulty of configuration and maintenance.

A person skilled in the art can understand that all or part of the steps of implementing the foregoing method embodiments may be implemented by hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, and when executed, the program includes The foregoing steps of the method embodiment; and the foregoing storage medium may be at least one of the following: a read-only memory (ROM), a RAM, a magnetic disk, or an optical disk, and the like, which can store the program code. . Finally, it should be noted that the above embodiments are merely illustrative of the technical solutions of the present invention, and are not limited thereto; although the beneficial effects brought by the present invention and the present invention are described in detail with reference to the foregoing embodiments, the field A person skilled in the art should understand that the technical solutions described in the foregoing embodiments may be modified or equivalently replaced in some of the technical features; and the modifications or substitutions do not deviate from the essence of the corresponding technical solutions. The scope of the claims.

Claims

claims

1. A method for generating a service path, characterized in that the method includes: the path calculation unit PCE receives the path calculation request sent by the path calculation client PCC

PCReq message, the PCReq message contains network function virtualization NF V function requirement information; the PCE generates a service path according to the network function virtualization database NFVDB, and the NF V functional entity that meets the NF V function requirement information is in the service path superior.

2. The method according to claim 1, characterized in that before the PCE receives the PCReq message sent by the PCC, it further includes:

The PCE receives the resource registration message sent by the NFV functional entity, and the resource registration message carries the resource information, function description and location information of the NFV functional entity; the PCE sends the resource information, the function description and the location information is added to the NFVDB.

3. The method according to claim 1 or 2, characterized in that, before the PCE receives the PCReq message sent by the PCC, it further includes:

The PCE pre-sets the traffic engineering database TEDB and label switching path database

LSPDB;

The PCE generates a service path according to the NFVDB, specifically including: the PCE selects the resource registration information of the NFV functional entity that meets the NFV functional requirement information from the NFVDB, and generates the service path according to the TEDB, LSPDB and the resource registration information to generate the service path.

4. The method according to any one of claims 1 to 3, characterized in that the PCReq message also contains NFV capacity requirement information or NFV execution sequence requirement information.

5. The method according to any one of claims 1 to 4, further comprising:

The PCE replies with a PCRep message through path calculation to send the information about the service path. To the PCC, instruct the PCC to establish a forwarding path based on the information on the service path.

6. A method for generating a service path, characterized in that the method includes: the path calculation client PCC sends a path calculation request PCReq message to the path calculation unit PCE, where the PCReq message contains network function virtualization NFV function requirement information, To facilitate the PCE to generate a service path that conforms to the NF V functional requirement information;

Receive the PCRep message sent by the PCE, where the PCRep message contains the information of the service path, and the PCC generates a forwarding path according to the information of the service path.

7. The method of claim 6, wherein the PCReq message also contains NFV capacity requirement information or NFV execution sequence requirement information.

8. A path calculation unit PCE, characterized by including:

A receiving unit configured to receive a path calculation request PCReq message sent by the path calculation client PCC, where the PCReq message contains network function virtualization NF V function requirement information;

A processing unit configured to generate a service path according to the network function virtualization database NFVDB, and the NFV functional entity that meets the NFV function requirement information is on the service path.

9. The PCE according to claim 8, characterized in that,

The receiving unit is also configured to receive a resource registration message sent by the NFV functional entity, where the resource registration message carries the resource information, function description and location information of the NFV functional entity;

The processing unit is also configured to add the resource information, the function description and the location information to the NFVDB.

10. The PCE according to claim 8 or 9, characterized in that the PCE further includes:

The setting unit is configured to set the traffic engineering database TEDB and the label switching path database LSPDB before the receiving unit receives the PCReq message sent by the PCC; the processing unit is specifically configured to select from the NFVDB that matches the required The resource registration information of the NFV functional entity describing the NFV functional requirement information, and based on the TEDB, LSPDB and the resource registration information to generate the service path.

11. The PCE according to any one of claims 8 to 10, further comprising:

A sending unit configured to send the service path information to the PCC through a path calculation reply PCRep message, and instruct the PCC to establish a forwarding path based on the service path information.

12. A path calculation client PCC, which is characterized by including:

A sending unit, configured to send a path calculation request PCReq message to the path calculation unit PCE, where the PCReq message contains network function virtualization NF V function requirement information, so that the PCE can generate a service path that meets the NF V function requirement information;

A receiving unit configured to receive a path calculation reply PCRep message sent by the PCE, where the PCRep message contains information about the service path;

A processing unit, configured to generate a forwarding path according to the information on the service path.

13. A system for generating service paths, characterized in that the system includes a path calculation unit PCE and a path calculation client PCC, where,

The PCE is configured to receive a path calculation request PCReq message sent by the PCC, generate a service path according to the network function virtualization database NFVDB, and send the service path information to the PCC through a path calculation reply PCRep message, where, The PCReq message contains network function virtualization NFV function requirement information, and the NFV functional entity that meets the NFV function requirement information is on the service path;

The PCC is configured to send the PCReq message to the PCE, receive the PCRep message sent by the PCE, and generate a forwarding path according to the information of the service path, wherein the PCReq message contains NFV function requirement information, In order to facilitate the PCE to generate a service path that conforms to the NFV function requirement information, the PCRep message contains the information of the service path.