CN104579889A - Method and device for calling NF (network function) - Google Patents
Method and device for calling NF (network function) Download PDFInfo
- Publication number
- CN104579889A CN104579889A CN201310486323.1A CN201310486323A CN104579889A CN 104579889 A CN104579889 A CN 104579889A CN 201310486323 A CN201310486323 A CN 201310486323A CN 104579889 A CN104579889 A CN 104579889A
- Authority
- CN
- China
- Prior art keywords
- mark
- nfv
- api
- privately owned
- middleware
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/76—Routing in software-defined topologies, e.g. routing between virtual machines
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
- Information Transfer Between Computers (AREA)
Abstract
An embodiment of the invention discloses a method for calling an NF (network function). The method comprises steps as follows: an NFV (network function virtualization) middleware device receives a first call message sent by a first NF device; the NFV middleware device determines an identifier of a first private API (application program interface) according to an identifier of a public API carried by the first call message, an identifier of a second NF carried by the first call message and a first correspondence relationship stored in the NFV middleware device; the NFV middleware device calls the second NF through the first private API corresponding to the identifier of the first private API. Thus, the first NF device can call the second NF through the public API which cannot directly call the second NF originally.
Description
Technical field
The present invention relates to the communications field, particularly relating to a kind of method for calling network function and device.
Background technology
In order to reduce network equipment cost, and service deployment faster, industry proposes network function virtual (english abbreviation is NFV, and English full name is network function virtualization) technology.NFV technology is by by proprietary hard-wired network function, is converted at standard or common information technoloy equipment, such as server, Ethernet switch or memory device, on by one or more network functions of software simulating.Through transforming, to obtain network function be not realized by specialized hardware due to described, but realized on described information technoloy equipment by software, therefore this network function is called as virtual network function (english abbreviation is VNF, English full name is virtual network function), to distinguish with by proprietary hard-wired network function.
Network function (english abbreviation is NF, and English full name the is Network Function) device that each VNF can realize this VNF with one is corresponding.Need to intercom mutually between multiple NF device, so that some functions of original private network device that cooperated, the content of communication comprises interactive control information and management information between NF device.But NF device identical is at present realized by different producers or different technology, and the interface type between different NF devices is often different, causes being difficult to realize a NF device calling another NF.
Summary of the invention
An object of an aspect of of the present present invention, for providing a kind of method being called NF by public application programming interfaces (english abbreviation is API), can realize calling NF when interface type is different between NF.
A first aspect of the present invention provides a kind of method for calling NF, and described method comprises:
NFV middleware device receives the first message call that a NF device sends, and carries the mark of the mark of public API and the 2nd NF of a described NF device request call in described first message call;
Described NFV middleware device determines the mark of the first privately owned API according to the first corresponding relation stored in the mark of described 2nd NF carried in the mark of the described public API carried in described first message call, described first message call and described NFV middleware device, wherein, described first corresponding relation comprises the mark of described public API, corresponding relation between the mark of described 2nd NF and the mark three of described first privately owned API, and described first privately owned API is the API that described NFV middleware device uses when calling described 2nd NF;
Described NFV middleware device is by the 2nd NF described in the described first privately owned API Calls corresponding with the mark of described first privately owned API.
In the first execution mode of described first aspect, determine the mark of described first privately owned API at described NFV middleware device before, described method also comprises:
Described NFV middleware device receives the first registration message, described first registration message is sent by described 2nd NF device, the mark of described first privately owned API and the mark of described 2nd NF is carried in described first registration message, wherein, described 2nd NF device is the device for realizing described 2nd NF;
Described NFV middleware device stores described first corresponding relation.
In the second execution mode of the first aspect of the first execution mode according to first aspect or first aspect, described method also comprises:
Described NFV middleware device receives the second message call that a described NF device sends, and described second message call carries the mark of the mark of described public API and the 3rd NF of a described NF device request call;
Described NFV middleware device is according to carrying the second corresponding relation stored in the mark of described 3rd NF and described NFV middleware device in the mark of the described public API carried in described second message call, described second message call, determine the mark of the second privately owned API, wherein said second corresponding relation comprises the mark of described public API, corresponding relation between the mark of the second privately owned API and the mark three of described 3rd NF, and described second privately owned API is the API that described NFV middleware device uses when calling described 3rd NF;
Described NFV middleware device is by the 3rd NF described in the described second privately owned API Calls corresponding with the mark of described second privately owned API.
In the third execution mode of described first invention of the second execution mode according to described first aspect, before described NFV middleware device determines described second privately owned API, described method also comprises:
Described NFV middleware device receives the second registration message, described second registration message is sent by the 3rd NF device, carry the mark of described second privately owned API and the mark of described 3rd NF in described second registration message, wherein, described 3rd NF device is the device for realizing described 3rd NF;
Described NFV middleware device stores described second corresponding relation.
According to first aspect in the 4th kind of execution mode of the first aspect of any one in the third execution mode of first aspect,
Described NFV middleware device, described 2nd NF device and a described NF device belong to different hardware devices respectively;
Or,
Described NFV middleware device and described 2nd NF device belong to same hardware device;
Or,
Described NFV middleware device and a described NF device belong to same hardware device.
A second aspect of the present invention provides a kind of NFV middleware device, comprising:
First receiving element, for receiving the first message call that a described NF device sends, carries the mark of the mark of public API and the 2nd NF of a described NF device request call in described first message call;
Determining unit, the first corresponding relation for storing in the mark of described 2nd NF of carrying in the mark according to the described public API carried in described first message call, described first message call and described NFV middleware device determines the mark of the first privately owned API, wherein, described first corresponding relation comprises the mark of described public API, corresponding relation between the mark of described 2nd NF and the mark three of described first privately owned API, and described first privately owned API is the API that described NFV middleware device uses when calling described 2nd NF;
Call unit, for by the 2nd NF described in the described first privately owned API Calls corresponding with the mark of described first privately owned API.
In the first execution mode of the second aspect according to described second aspect, described NFV middleware device also comprises:
Second receiving element, for determine described first privately owned API at described NFV middleware device mark before receive the first registration message, described first registration message is sent by described 2nd NF device, the mark of described first privately owned API and the mark of described 2nd NF is carried in described first registration message, wherein, described 2nd NF device is the device for realizing described 2nd NF;
Memory cell, stores described first corresponding relation for described NFV middleware device.
In the second execution mode of the second aspect of the first execution mode according to second aspect or second aspect,
Described first receiving element is also for receiving the second message call that a described NF device sends, and described second message call carries the mark of the mark of described public API and the 3rd NF of a described NF device request call;
Second corresponding relation of described determining unit also for storing in the mark of described 3rd NF of carrying in the mark according to the described public API carried in described second message call, described second message call and described NFV middleware device, determine the mark of the second privately owned API, wherein said second corresponding relation comprises the mark of described public API, corresponding relation between the mark of the second privately owned API and the mark three of described 3rd NF, and described second privately owned API is the API that described NFV middleware device uses when calling described 3rd NF;
Described call unit is also for by the 3rd NF described in the described second privately owned API Calls corresponding with the mark of described second privately owned API.
In the third execution mode of the second aspect of the second execution mode according to second aspect,
Described second receiving element also for determine described second privately owned API at described NFV middleware device mark before receive the second registration message, described second registration message is sent by the 3rd NF device, the mark of described second privately owned API and the mark of described 3rd NF is carried in described second registration message, wherein, described 3rd NF device is the device for realizing described 3rd NF;
Described memory cell is also for storing described second corresponding relation.
According in the 4th kind of execution mode of the second aspect of any one in the third execution mode from second aspect to second aspect,
Described NFV middleware device, a described NF device and described 3rd NF device belong to different hardware devices respectively;
Or,
Described NFV middleware device and described 2nd NF device belong to same hardware device;
Or,
Described NFV middleware device and a described NF device belong to same hardware device.
In one aspect of the invention, NFV middleware device receives the first message call that NF device sends, and according to the mark of the public API in the first message call and identified query first corresponding relation of the 2nd NF, determine the mark of the first privately owned API for calling the 2nd NF, to use the first privately owned API to call the 2nd NF.Like this, a described NF device can achieve calling described 2nd NF by the described public API that originally directly cannot call the 2nd NF.
Accompanying drawing explanation
Fig. 1 a is depicted as the method schematic diagram of an embodiment in the present invention;
Fig. 1 b is depicted as the method schematic diagram of an embodiment in the present invention;
Figure 2 shows that the method schematic diagram of an embodiment in the present invention;
Figure 3 shows that the method schematic diagram of an embodiment in the present invention;
Figure 4 shows that the schematic diagram of the NFV middleware device of an embodiment in the present invention;
Figure 5 shows that the schematic diagram of the NFV middleware device of an embodiment in the present invention;
Figure 6 shows that the schematic diagram of the network equipment of an embodiment in the present invention;
Figure 7 shows that the schematic diagram of the network equipment of an embodiment in the present invention.
Embodiment
Launch to describe in detail to the present invention below in conjunction with the drawings and specific embodiments.But it is noted that these embodiments below, be only help understand technical scheme for example, be not intended to limit the present invention.
As shown in Figure 1a, the content of one embodiment of the present of invention is as follows.
Alternatively, the present embodiment also comprises following content further.
1010, a NF device sends the first message call to NFV middleware device, described first message call comprises the mark of the 2nd NF of a described NF device request call and common application interface, and (English full name is application program interface, english abbreviation is API) mark, show that a NF device request is by the 2nd NF described in described public API Calls.
Described NFV middleware realizes the intermediate module that a NF device communicates with another NF device, realizes details, provide public NF application programming interfaces for what shield different NF.Described NFV middleware device is the device realizing described NFV middleware.
1015, described NFV middleware device is according to the first corresponding relation stored in the mark of the described public API carried in the mark of described 2nd NF carried in described first message call, described first message call and described NFV middleware device, determine the mark of the first privately owned API, namely determine and can call described 2nd NF by described first privately owned API.
Described first corresponding relation comprises the mark of described public API, corresponding relation between the mark of described first privately owned API and the mark three of described 2nd NF, and wherein said first privately owned API is that described NFV middleware device is for calling the API of described 2nd NF.
In the present embodiment, described public API can be a NF device configuration in advance before described NFV middleware device stores described first corresponding relation, also can be in the process setting up described first corresponding relation according to a certain rule be the one NF device configuration, such as random selecting one from multiple available public API.
Alternatively, a NF device can determining that NFV middleware device sends described first message call after storing the first corresponding relation.Such as, by the mode of active inquiry, a NF device can determine whether the first corresponding relation stores in NFV middleware device.One NF device can initiate inquiry to NFV middleware device, also can to determining that the equipment whether storing the first corresponding relation in NFV middleware device initiates inquiry.In addition, NFV middleware device also can send a notification message to a NF device, to notify that a NF device can use described public API Calls the one NF.Described first corresponding relation can be that NFV middleware device self is set up, and also can be that other devices are set up.
One NF device also can, according to configuration in advance, just be determined to use described public API to call the 2nd NF before the first corresponding relation is stored in NFV middleware device.Such as, described public API can be preconfigured to the acquiescence API of any one NF called in multiple NF.When calling any one NF in described multiple NF, acquiescence needs to use this public API to call.Therefore a NF device also can send described first message call before the first corresponding relation is stored in NFV middleware device.NFV middleware device can call according to the first message call after getting the first corresponding relation again.
1020, described NFV middleware device is by the 2nd NF described in described first privately owned API Calls.
Alternatively, the mark of described 2nd NF can be the type of described 2nd NF.When only having one and belonging to the NF of the type of described 2nd NF, then this unique NF is exactly described 2nd NF; When exist m(m be greater than 1 positive integer) individual belong to the NF of the type of described 2nd NF time, according to certain strategy, NFV middleware device can determine that from a described m NF at least one NF is described 2nd NF and calls.
In the present embodiment, the 2nd NF can represent a single function, also can represent the set of multiple function.When the 2nd NF represents the set of multiple function, call described 2nd NF and comprise calling the repertoire that the 2nd NF comprises, also can comprise calling the one or more functions in the 2nd NF.
By performing 1010-1020, NFV middleware device receives the first message call that NF device sends, and according to the mark of the public API in the first message call and identified query first corresponding relation of the 2nd NF, determine the mark of the first privately owned API for calling the 2nd NF, to use the first privately owned API to call the 2nd NF.Like this, a described NF device can achieve calling described 2nd NF by the described public API that directly cannot call the 2nd NF.
Alternatively, as shown in Figure 1 b, the present embodiment can also comprise following content.
1000, described 2nd NF device sends the first registration message to NFV middleware device, and described first registration message comprises the mark of described 2nd NF and the mark for the described first privately owned API that calls the 2nd NF.Described 2nd NF device is the device for realizing the 2nd NF.Described NFV middleware device according to the mark of the 2nd NF, can determine described 2nd NF.
1005, described NFV middleware device stores described first corresponding relation.Described first corresponding relation sets up according to the mark of described 2nd NF carried in the first registration message and the mark of described public API that gets for mark and the described NFV middleware device of the described first privately owned API that calls described 2nd NF.Because described first corresponding relation comprises these three elements of mark of the mark of described 2nd NF, the mark of described public API and the first privately owned API, therefore NFV middleware device is being known wherein after two elements, just can determine remaining 3rd element in these three elements according to the first corresponding relation, such as after the mark of the mark and described public API of knowing described 2nd NF, just can determine the mark of described first privately owned API, namely can determine a described API.The first corresponding relation that described NFV middleware device stores can be set up by described NFV middleware device oneself, also can be set up by other devices and send to described NFV middleware device.
1005 and 1010 is separate, and not Existence dependency relationship on execution sequence, 1005 can perform before 1010, also can perform after 1010, also can perform with 1010 simultaneously.In some cases, such as, be when being a NF device configuration in advance before described NFV middleware device stores described first corresponding relation at described public API, 1000 and 1010 is also not Existence dependency relationship on the sequencing performed.Show in Fig. 1 b by 1000 to 1020 execution sequence be a kind of feasible execution sequence in the present embodiment, be not unique execution sequence.Owing to needing to use the first corresponding relation preserved in NFV middleware device in 1015, therefore 1005 can perform before 1015.
In addition in the present embodiment, when described 2nd NF belong to one comprise the set of multiple NF time, (English full name is Network Function Block to the network element function block that described 2nd NF can be regarded as or be understood to be in described set, english abbreviation is NFB) set in other NF be also regarded as a NFB respectively, described set then can be considered to be the set that comprises multiple network element function block.
In the present embodiment, described NFV middleware device, a described NF device and described 2nd NF device can be three software modules.Each software module, after the hardware device being included processor and memory performs, can perform the function of described software module by described hardware device.These three devices can realize respectively in three different hardware devices; Also can such as, at a hardware device, a station server, middlely realize described NFV middleware device and a described NF device, in another hardware device, realize described 2nd NF device; Still can at a hardware device, the special hardware that such as router is this kind of, middlely realizes described NFV middleware device and the 2nd NF device, realizes a NF device in another hardware device.
As shown in Figure 2, the content of one embodiment of the present of invention is as follows.
The embodiment corresponding with Fig. 2 is the expansion to the embodiment corresponding with Fig. 1 a or Fig. 1 b, and the content of the 2000-2005 shown in Fig. 2 is identical with the content in the 1000-1005 in embodiment as shown in Figure 1 b.In addition, embodiment as shown in Figure 2 also comprises following content.
2010, the 3rd NF device sends the second registration message to described NFV middleware device, and described second registration message carries the mark of the second privately owned API for calling the 3rd NF and the mark of described 3rd NF.Described 3rd NF device is the device realizing described 3rd NF.Described NFV middleware device, according to the mark of the 3rd NF, can determine described 3rd NF.
2015, described NFV middleware device stores the second corresponding relation.Described second corresponding relation sets up according to the mark of described 3rd NF carried in the second registration message and the mark of described public API that gets for mark and the described NFV middleware device of the described second privately owned API that calls described 3rd NF.Described second corresponding relation comprises the corresponding relation of the mark three of the mark of described 2nd NF, the mark of described public API and the second privately owned API, therefore NFV middleware device is after the mark of the mark and described public API of knowing described 3rd NF, just can determine the mark of described second privately owned API, namely can determine described 2nd API.Described second corresponding relation that described NFV middleware device stores can be set up by described NFV middleware device oneself, also can be set up by other devices and send to described NFV middleware device.
Separate between 2000-2005 and 2010-2015 these two groups operation, therefore the execution sequence between these two groups operations is unrestricted, namely 2000-2005 prior to 2010-2015, also later in 2010-2015, also can can perform with 2010-2015 simultaneously.
The content of 2020-2030 is identical with the 1010-1020 in the embodiment corresponding with Fig. 1 a or Fig. 1 b.
The present embodiment also comprises following content.
2035, a NF device sends the second message call to NFV middleware device, described second message call comprises the mark of the 3rd NF and the mark of described public API of a described NF device request call, shows that a NF device request is by the 3rd NF described in described public API Calls.
2040, described NFV middleware device is according to the second corresponding relation stored in the mark of the described public API carried in the mark of described 3rd NF carried in described second message call, described second message call and described NFV middleware device, determine the mark of the second privately owned API, namely determine and can call described 3rd NF by described second privately owned API.Described second privately owned API is the API that described NFV middleware device uses when calling described 3rd NF
Alternatively, a NF device can determining that NFV middleware device sends described second message call after storing the second corresponding relation.Such as, by the mode of active inquiry, a NF device can determine whether the second corresponding relation stores in NFV middleware device.One NF device can initiate inquiry to NFV middleware device, also can to determining that the equipment whether storing the second corresponding relation in NFV middleware device initiates inquiry.In addition, NFV middleware device also can send a notification message to a NF device, to notify that a NF device can use described public API Calls the 3rd NF.Described second corresponding relation can be that NFV middleware device self is set up, and also can be that other devices are set up.
One NF device also can, according to configuration in advance, just be determined to use described public API to call the 3rd NF before the second corresponding relation is stored in NFV middleware device.Such as, described public API can be preconfigured to the acquiescence API that described NFV middleware device calls described 3rd NF.Like this, described NFV middleware device can call according to the second message call after getting the second corresponding relation again.Meanwhile, described public API can be pre-arranged as described NFV middleware device calls the acquiescence API of described 2nd NF.
2045, described NFV middleware device is by the 3rd NF described in described second privately owned API Calls.
Alternatively, the mark of described 3rd NF can be the type of described 3rd NF.When only having one and belonging to the NF of the type of described 3rd NF, then this unique NF is exactly described 3rd NF; When exist m(m be greater than 1 positive integer) individual belong to the NF of the type of described 2nd NF time, according to certain strategy, NFV middleware device can determine that from a described m NF at least one NF is described 2nd NF and calls.
2015 and 2035 is separate, and these two operate on execution sequence unrestricted, namely 2015 can perform before 2035, also can perform after 2035, also can perform with 2035 simultaneously.2010 and 2035 these two to operate in execution sequence also can be unrestricted, a described NF device first can send described second message call to described VNF middleware device, and described VNF middleware device can receive described second registration message and correspondingly store described second corresponding relation after receiving described second message call, and then perform 2040 and 2045.
In the present embodiment, a NF device can realize calling different NF by described public API.In like manner, a NF device can also use described public API to realize calling a large amount of NF
As shown in Figure 3, the method for one embodiment of the present of invention can comprise following operation.
3001, the router NF device for realizing router NF sends registration message to NFV middleware device, and described registration message comprises the mark of the mark of router NF, the mark of a NFB and the 2nd NFB, also comprises the mark of privately owned API.Router NF refers to the network function of router, and the router NF device in the present embodiment is equivalent to the 2nd NF device in the embodiment corresponding with Fig. 1 a, Fig. 1 b or Fig. 2.A described NFB refers to the access authentication function in router NF; 2nd NFB refers to the forwarding capability in router NF.One NFB and the 2nd NFB all belongs to router NF.Described privately owned API is the API for calling a NFB and the 2nd NFB.Alternatively, in the present embodiment, the mark belonging to the NFB in a NF may be identical with the mark of another NFB belonged in another NF, therefore only uses the mark of a NFB possibly cannot determine a corresponding NFB uniquely.In order to determine a NFB as far as possible uniquely, these two elements of mark of the mark of the NF belonging to this NFB and described NFB can be used simultaneously, such as, use the mark of a NFB and the mark of router NF to determine a NFB.
3002, described NFV middleware device is set up and the first corresponding relation and the second corresponding relation.Described first corresponding relation comprises the corresponding relation of the mark of the mark of public API, the mark of described privately owned API, the mark of described router NF and a described NFB, and described second corresponding relation comprises the corresponding relation of the mark of the mark of described public API, the mark of described privately owned API, the mark of described router NF and described 2nd NFB.A NFB can be determined according to the mark of router NF and the mark of a NFB, the 2nd NFB can be determined according to the mark of router NF and this locality mark of the 2nd NFB.Such as, if the NF of router be designated 01, this locality of a NFB is designated 001, and so the mark of a NFB can be expressed as 01001; In like manner, if the NF of router be designated 01, this locality of the 2nd NFB is designated 002, and so the mark of the 2nd NFB can be designated 01002.
Table 1 is a concrete example of the first corresponding relation, and table 2 is a concrete example of the second corresponding relation.
| The mark of public API | The mark of privately owned API | The mark of router NF | The mark of the one NFB |
Table 1
| The mark of public API | The mark of privately owned API | The mark of router NF | The mark of the 2nd NFB |
Table 2
Optionally, the method shown in Fig. 3 can also comprise following content.
3003, point-to-point protocol (english abbreviation is PPPoE) the VNF device on Ethernet sends the first message call to NFV middleware device, and described first message call comprises the mark of the mark of public API, the mark of router NF and a NFB.PPPoE VNF device in the present embodiment is equivalent to the NF device in the embodiment corresponding with Fig. 1 a, Fig. 1 b or Fig. 2.Described first message call is used for calling a NFB, namely for calling access authentication function.PPPoE VNF refers to the pppoe feature realized in virtual machine (english abbreviation is VM), and PPPoE VNF device just refers to the device realizing PPPoE VNF..
For example, PPPoE VNF device determines whether to call a NF by described public API by the mode of active inquiry.
Again for example, NFV middleware device can send a notification message to PPPoE VNF device, to notify that PPPoE VNF device can use a NF described in described public API Calls.
Again for example, PPPoE VNF device can determine according to configuration in advance that described public API is the acquiescence API calling arbitrary NF, therefore when needs call a NF, uses described public API to carry out calling.
3004, NFV middleware device determines the mark of described privately owned API according to this locality mark of the mark of public API, the mark of router NF and a NFB and the first corresponding relation, and namely determining can by described privately owned API Calls the one NFB.
3005, NFV middleware device is by described privately owned API Calls the one NFB.
Alternatively, the method shown in Fig. 3 can also comprise:
3006, PPPoE VNF device sends the second message call to NFV middleware device, and described second message call comprises this locality mark of the mark of public API, the mark of router NF and the 2nd NFB.Described second message call is used for calling the 2nd NFB, namely for calling forwarding capability.
3007, NFV middleware device determines the mark of described privately owned API according to this locality mark of the mark of public API, the mark of router NF and the 2nd NFB and the second corresponding relation, and namely determining can by described privately owned API Calls the 2nd NFB.
3008, NFV middleware device is by described privately owned API Calls the 2nd NFB.
Figure 4 shows that a kind of NFV middleware device 40 disclosed in the embodiment of the present invention.NFV middleware device 40 can be the NFV middleware device in the embodiment corresponding with arbitrary accompanying drawing in Fig. 1 a, Fig. 1 b, Fig. 2 and Fig. 3.
NFV middleware device 40 comprises the first receiving element 41, determining unit 42 and call unit 43.The first message call that described first receiving element 41 sends for receiving a described NF device, carries the mark of the mark of public API and the 2nd NF of a described NF device request call in described first message call.Described first message call shows that a described NF device request uses described public API to call the 2nd NF.Described determining unit 42 determines the mark of the first privately owned API for the first corresponding relation stored in the mark of described 2nd NF of carrying in the mark according to the described public API carried in described first message call, described first message call and described NFV middleware device, wherein, described first corresponding relation comprises the mark of described public API, corresponding relation between the mark of described 2nd NF and the mark three of described first privately owned API, and described first privately owned API is the API that described NFV middleware device uses when calling described 2nd NF.Described call unit 43 is for by the 2nd NF described in the described first privately owned API Calls corresponding with the mark of described first privately owned API.
Alternatively, described NFV middleware device also comprises: the second receiving element 44 and memory cell 45.
Described second receiving element 44 for determine described first privately owned API at described NFV middleware device mark before receive the first registration message, described first registration message is sent by described 2nd NF device, the mark of described first privately owned API and the mark of described 2nd NF is carried in described first registration message, wherein, described 2nd NF device is the device for realizing described 2nd NF.
Described memory cell 45 stores described first corresponding relation for described NFV middleware device.Described first corresponding relation stored in described memory cell set up by described NFV middleware device, or other devices are set up and send to described NFV middleware device.
According to above content, NFV middleware device can realize calling NF by a public API.
Described NFV middleware device, a described NF device and described 2nd NF device belong to different hardware devices respectively; Or described NFV middleware device and a described NF device belong to same hardware device; Or described NFV middleware device and described 3rd NF device belong to same hardware device.
Alternatively, described first receiving element is also for receiving the second message call that a described NF device sends, and described second message call carries the mark of the mark of described public API and the 3rd NF of a described NF device request call.Described second message call mark the one NF device request is by the 3rd NF described in described public API Calls.Second corresponding relation of described determining unit also for storing in the mark of described 3rd NF of carrying in the mark according to the described public API carried in described second message call, described second message call and described NFV middleware device, determine the mark of the second privately owned API, wherein said second corresponding relation comprises the mark of described public API, corresponding relation between the mark of the second privately owned API and the mark three of described 3rd NF, and described second privately owned API is the API that described NFV middleware device uses when calling described 3rd NF; Described call unit is also for by the 3rd NF described in the described second privately owned API Calls corresponding with the mark of described second privately owned API.
According to above content, NFV middleware device can pass through the different NF of a public API Calls.
Figure 5 shows that a kind of NFV middleware device 50 disclosed in the embodiment of the present invention, NFV middleware device as shown in Figure 5 comprises processor 51, memory 52, interface circuit 53 and bus 54.The computer instruction that described processor can perform is stored in described memory 52.Under the instruction of described computer instruction, described processor and described memory and interface circuit cooperatively interact, and perform following operation:
Receive the first registration message that the 2nd NF device sends, described first registration message comprises the mark of the first privately owned API for calling the 2nd NF and the mark of described 2nd NF;
Store the first corresponding relation, described first corresponding relation comprises the mark of public API, corresponding relation between the mark of described first privately owned API and the mark three of a described NF.Described first corresponding relation be stored is that the mark of the described public API used according to described first registration message and a NF device by described NFV middleware device or other devices is determined.
Receive the first message call that a NF device sends, described first message call comprises the mark of described public API and the mark of described 2nd NF;
Determine that described first privately owned API is the API for calling described 2nd NF according to the mark of the described public API carried in described first message call, the mark of described 2nd NF and described first corresponding relation;
By the 2nd NF described in described first privately owned API Calls.
Alternatively, described operation not only comprises calling the 2nd NF, can also comprise calling the 3rd NF.As follows to the concrete operations of calling of the 3rd NF.
Receive the second registration message that the 3rd NF device sends, described second registration message comprises the mark of the second privately owned API for calling the 3rd NF and the mark of described 3rd NF;
Store the second corresponding relation, described second corresponding relation comprises the mark of public API, corresponding relation between the mark of described second privately owned API and the mark three of described 3rd NF.
Receive the second message call that a NF device sends, described second message call comprises the mark of described public API and the mark of described 3rd NF;
Determine that described second privately owned API is the API for calling described 3rd NF according to the mark of the described public API carried in described second message call, the mark of described 3rd NF and described second corresponding relation;
By the 3rd NF described in described second privately owned API Calls.
Alternatively, NFV middleware device 50 shown in Fig. 5 is the NFV middleware device in the embodiment corresponding with Fig. 1 a, Fig. 1 b, Fig. 2 or Fig. 3, can perform any operation performed by the NFV middleware device in any embodiment corresponding with Fig. 1 a, Fig. 1 b, Fig. 2 and Fig. 3.
Figure 6 shows that a kind of network equipment 60 disclosed in the embodiment of the present invention, comprise processor 61, memory 62, interface circuit 63 and bus 64.The computer instruction that described processor can perform is stored in described memory 62.Described network equipment 60 is set up communicativeness by described interface circuit 63 with a NF device and is connected.Described network equipment 60 achieves the NFV middleware device in the embodiment corresponding with Fig. 1 a, Fig. 1 b or Fig. 2 and the operation performed by the 2nd NF device, the NFV middleware device in the embodiment corresponding with Fig. 3 and the operation performed by router NF device can also be realized, therefore can think that NFV middleware device and the 2nd NF device are integrated in described network equipment 60, or, think that NFV middleware device and router NF device are integrated in described network equipment 60.
Under the instruction of described computer instruction, described processor and described memory and interface circuit cooperatively interact, and perform following operation:
Obtain the first registration message, described first registration message comprises the mark of the first privately owned API for calling the 2nd NF and the mark of described 2nd NF.Alternatively, described first registration message is generated by described network equipment oneself, also can receive from other network equipments.
Store the first corresponding relation, described first corresponding relation comprises the mark of public API, corresponding relation between the mark of described first privately owned API and the mark three of described 2nd NF.Described first corresponding relation be stored is that the mark of the described public API used according to described first registration message and a NF device by described network equipment 60 or other devices is determined.A described NF device needs the device using the 2nd NF described in described public API Calls.
Alternatively, described operation also comprises the message call sent according to a described NF device and calls the 2nd NF, and the concrete operations of calling the 2nd NF are as follows:
Receive the first message call that a NF device sends, described first message call comprises the mark of described public API and the mark of described 2nd NF;
Determine that described first privately owned API is the API for calling described 2nd NF according to the mark of described 2nd NF carried in the mark of the described public API carried in described first message call, described first message call and described first corresponding relation;
By the 2nd NF described in described first privately owned API Calls.
Alternatively, described operation not only comprises calling the 2nd NF, can also comprise calling the 3rd NF.As follows to the concrete operations of calling of the 3rd NF.
Obtain the second registration message, described second registration message comprises the mark of the second privately owned API for calling the 3rd NF and the mark of described 3rd NF.Described first registration message is generated by described network equipment oneself, also can receive from other network equipments.
Store the second corresponding relation, described second corresponding relation comprises public API, corresponding relation between described second privately owned API and the mark three of described 3rd NF.
Receive the second message call that a NF device sends, described second message call comprises the mark of described public API and the mark of described 3rd NF.
Determine that described second privately owned API is the API for calling described 3rd NF according to the mark of described 3rd NF carried in the mark of the described public API carried in described second message call, described second message call and described second corresponding relation;
By the 3rd NF described in described second privately owned API Calls.
Can realize by the different NF of same public API Calls by operating above.
Figure 7 shows that a kind of network equipment 70 disclosed in the embodiment of the present invention, comprise processor 71, memory 72, interface circuit 73 and bus 74.The computer instruction that described processor 71 can perform is stored in described memory 72.Described network equipment 70 is set up communicativeness by described interface circuit with the 2nd NF device and the 3rd NF device and is connected, and the 2nd NF device is used for realizing the 2nd NF, and the 3rd NF device is used for realizing the 3rd NF.
Network equipment 70 can perform all operations of NFV middleware device in the embodiment corresponding with Fig. 1 a, Fig. 1 b or Fig. 2 and a NF device, also can perform all operations of NFV middleware device in the embodiment corresponding with Fig. 3 and PPPoE VNF device.
Under the instruction of described computer instruction, described processor 71 cooperatively interacts with described memory 72 and interface circuit 73, performs following operation:
Receive the first registration message that the 2nd NF device sends, described first registration message comprises the mark of the first privately owned API for calling the 2nd NF and described 2nd NF;
Determine that public API is that described network equipment calls the required API used of the 2nd NF;
Store the first corresponding relation, described first corresponding relation comprises the mark of public API, corresponding relation between the mark of described first privately owned API and the mark three of described 2nd NF.Described first corresponding relation be stored is that the mark calling according to described first registration message and network equipment 70 the described public API that the 2nd NF uses by described network equipment 70 or other devices is determined.
Alternatively, described operation also comprises:
Determine that described first privately owned API is the API for calling described 2nd NF according to the mark of described public API, the mark of described 2nd NF and described first corresponding relation;
By the 2nd NF described in described first privately owned API Calls.
So just can realize use one public API Calls NF.
Alternatively, described operation not only comprises calling the 2nd NF, can also comprise calling the 3rd NF.When also needing to realize the calling of the 3rd NF, the described operation that described network equipment performs also comprises:
Receive the second registration message that the 3rd NF device sends, described second registration message comprises the mark of the second privately owned API for calling the 3rd NF and the mark of described 3rd NF;
Store the second corresponding relation, described second corresponding relation comprises the mark of public API, corresponding relation between the mark of described second privately owned API and the mark three of described 3rd NF.
Alternatively, described operation also comprises:
After determining to need to call the 3rd NF, determine that described second privately owned API is the API for calling described 3rd NF according to the mark of described public API, the mark of described 3rd NF and described second corresponding relation;
By the 3rd NF described in described second privately owned API Calls.
So just can realize the NF using same public API Calls different.
One of ordinary skill in the art will appreciate that: all or part of step realizing said method embodiment can have been come by the hardware that program command is relevant, aforesaid program can be stored in a computer read/write memory medium, this program, when performing, performs the step comprising said method embodiment; And aforesaid storage medium comprises: ROM, RAM, magnetic disc or CD etc. various can be program code stored medium.
The above; be only the present invention's preferably embodiment, but protection scope of the present invention is not limited thereto, any people being familiar with this technology is in the technical scope disclosed by the present invention; the change that can expect easily or replacement, all should be encompassed within protection scope of the present invention.
Claims (10)
1. for calling a method of network function NF, it is characterized in that, comprising:
The virtual NFV middleware device of network function receives the first message call that first network function NF device sends, and carries the mark of the mark of common application interface API and the 2nd NF of a described NF device request call in described first message call;
Described NFV middleware device determines the mark of the first privately owned API according to the first corresponding relation stored in the mark of described 2nd NF carried in the mark of the described public API carried in described first message call, described first message call and described NFV middleware device, wherein, described first corresponding relation comprises the mark of described public API, corresponding relation between the mark of described 2nd NF and the mark three of described first privately owned API, and described first privately owned API is the API that described NFV middleware device uses when calling described 2nd NF;
Described NFV middleware device is by the 2nd NF described in the described first privately owned API Calls corresponding with the mark of described first privately owned API.
2. method according to claim 1, is characterized in that, determine the mark of described first privately owned API at described NFV middleware device before, described method also comprises:
Described NFV middleware device receives the first registration message, described first registration message is sent by described 2nd NF device, the mark of described first privately owned API and the mark of described 2nd NF is carried in described first registration message, wherein, described 2nd NF device is the device for realizing described 2nd NF;
Described NFV middleware device stores described first corresponding relation.
3. method according to claim 1 and 2, is characterized in that, described method also comprises:
Described NFV middleware device receives the second message call that a described NF device sends, and described second message call carries the mark of the mark of described public API and the 3rd NF of a described NF device request call;
Described NFV middleware device is according to carrying the second corresponding relation stored in the mark of described 3rd NF and described NFV middleware device in the mark of the described public API carried in described second message call, described second message call, determine the mark of the second privately owned API, wherein said second corresponding relation comprises the mark of described public API, corresponding relation between the mark of the second privately owned API and the mark three of described 3rd NF, and described second privately owned API is the API that described NFV middleware device uses when calling described 3rd NF;
Described NFV middleware device is by the 3rd NF described in the described second privately owned API Calls corresponding with the mark of described second privately owned API.
4. method according to claim 3, is characterized in that, before described NFV middleware device determines described second privately owned API, described method also comprises:
Described NFV middleware device receives the second registration message, described second registration message is sent by the 3rd NF device, carry the mark of described second privately owned API and the mark of described 3rd NF in described second registration message, wherein, described 3rd NF device is the device for realizing described 3rd NF;
Described NFV middleware device stores described second corresponding relation.
5. method according to any one of claim 1 to 4, is characterized in that,
Described NFV middleware device, described 2nd NF device and a described NF device belong to different hardware devices respectively;
Or,
Described NFV middleware device and described 2nd NF device belong to same hardware device;
Or,
Described NFV middleware device and a described NF device belong to same hardware device.
6. the virtual NFV middleware device of network function, is characterized in that, comprising:
First receiving element, for receiving the first message call that described first network function NF device sends, carries the mark of the mark of common application interface API and the 2nd NF of a described NF device request call in described first message call;
Determining unit, the first corresponding relation for storing in the mark of described 2nd NF of carrying in the mark according to the described public API carried in described first message call, described first message call and described NFV middleware device determines the mark of the first privately owned API, wherein, described first corresponding relation comprises the mark of described public API, corresponding relation between the mark of described 2nd NF and the mark three of described first privately owned API, and described first privately owned API is the API that described NFV middleware device uses when calling described 2nd NF;
Call unit, for by the 2nd NF described in the described first privately owned API Calls corresponding with the mark of described first privately owned API.
7. NFV middleware device according to claim 6, is characterized in that, described NFV middleware device also comprises:
Second receiving element, for determine described first privately owned API at described NFV middleware device mark before receive the first registration message, described first registration message is sent by described 2nd NF device, the mark of described first privately owned API and the mark of described 2nd NF is carried in described first registration message, wherein, described 2nd NF device is the device for realizing described 2nd NF;
Memory cell, stores described first corresponding relation for described NFV middleware device.
8. the NFV middleware device according to claim 6 or 7, is characterized in that,
Described first receiving element is also for receiving the second message call that a described NF device sends, and described second message call carries the mark of the mark of described public API and the 3rd NF of a described NF device request call;
Second corresponding relation of described determining unit also for storing in the mark of described 3rd NF of carrying in the mark according to the described public API carried in described second message call, described second message call and described NFV middleware device, determine the mark of the second privately owned API, wherein said second corresponding relation comprises the mark of described public API, corresponding relation between the mark of the second privately owned API and the mark three of described 3rd NF, and described second privately owned API is the API that described NFV middleware device uses when calling described 3rd NF;
Described call unit is also for by the 3rd NF described in the described second privately owned API Calls corresponding with the mark of described second privately owned API.
9. NFV middleware device according to claim 8, is characterized in that,
Described second receiving element also for determine described second privately owned API at described NFV middleware device mark before receive the second registration message, described second registration message is sent by the 3rd NF device, the mark of described second privately owned API and the mark of described 3rd NF is carried in described second registration message, wherein, described 3rd NF device is the device for realizing described 3rd NF;
Described memory cell is also for storing described second corresponding relation.
10. the NFV middleware device according to any one of claim 6 to 9, is characterized in that,
Described NFV middleware device, a described NF device and described 3rd NF device belong to different hardware devices respectively;
Or,
Described NFV middleware device and described 2nd NF device belong to same hardware device;
Or,
Described NFV middleware device and a described NF device belong to same hardware device.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310486323.1A CN104579889B (en) | 2013-10-16 | 2013-10-16 | A kind of method and device for being used to call network function |
| PCT/CN2014/088434 WO2015055102A1 (en) | 2013-10-16 | 2014-10-13 | Method and device for invoking network function |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310486323.1A CN104579889B (en) | 2013-10-16 | 2013-10-16 | A kind of method and device for being used to call network function |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104579889A true CN104579889A (en) | 2015-04-29 |
| CN104579889B CN104579889B (en) | 2018-03-09 |
Family
ID=52827662
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310486323.1A Active CN104579889B (en) | 2013-10-16 | 2013-10-16 | A kind of method and device for being used to call network function |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN104579889B (en) |
| WO (1) | WO2015055102A1 (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018120150A1 (en) * | 2016-12-30 | 2018-07-05 | 华为技术有限公司 | Method and apparatus for connection between network entities |
| CN109542964A (en) * | 2018-11-06 | 2019-03-29 | 用友网络科技股份有限公司 | A kind of data calling method and data calling system |
| CN109983736A (en) * | 2016-11-21 | 2019-07-05 | 华为技术有限公司 | A kind of processing method, equipment and the system of NF component exception |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9854048B2 (en) | 2015-06-29 | 2017-12-26 | Sprint Communications Company L.P. | Network function virtualization (NFV) hardware trust in data communication systems |
| US10116571B1 (en) | 2015-09-18 | 2018-10-30 | Sprint Communications Company L.P. | Network Function Virtualization (NFV) Management and Orchestration (MANO) with Application Layer Traffic Optimization (ALTO) |
| EP3203686B1 (en) | 2016-02-08 | 2019-12-11 | Comptel Corporation | Virtualized network function interworking |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101676875A (en) * | 2008-08-15 | 2010-03-24 | 北京北大众志微系统科技有限责任公司 | Method for seamless access remote Windows application program by Linux terminal and apparatus thereof |
| CN102136933A (en) * | 2010-09-30 | 2011-07-27 | 华为技术有限公司 | Equipment management method, middleware and machine communication platform, equipment and system |
| CN102882908A (en) * | 2011-07-15 | 2013-01-16 | 易云捷讯科技（北京）有限公司 | Cloud computing management system and cloud computing management method |
| US20130044629A1 (en) * | 2011-08-18 | 2013-02-21 | International Business Machines Corporation | Virtual network overlays and methods of forming thereof |
| CN103164286A (en) * | 2013-03-12 | 2013-06-19 | 无锡云动科技发展有限公司 | Implement method, resource manager and cloud calculating system of cloud computing platform arrangement |
-
2013
- 2013-10-16 CN CN201310486323.1A patent/CN104579889B/en active Active
-
2014
- 2014-10-13 WO PCT/CN2014/088434 patent/WO2015055102A1/en active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101676875A (en) * | 2008-08-15 | 2010-03-24 | 北京北大众志微系统科技有限责任公司 | Method for seamless access remote Windows application program by Linux terminal and apparatus thereof |
| CN102136933A (en) * | 2010-09-30 | 2011-07-27 | 华为技术有限公司 | Equipment management method, middleware and machine communication platform, equipment and system |
| CN102882908A (en) * | 2011-07-15 | 2013-01-16 | 易云捷讯科技（北京）有限公司 | Cloud computing management system and cloud computing management method |
| US20130044629A1 (en) * | 2011-08-18 | 2013-02-21 | International Business Machines Corporation | Virtual network overlays and methods of forming thereof |
| CN103164286A (en) * | 2013-03-12 | 2013-06-19 | 无锡云动科技发展有限公司 | Implement method, resource manager and cloud calculating system of cloud computing platform arrangement |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109983736A (en) * | 2016-11-21 | 2019-07-05 | 华为技术有限公司 | A kind of processing method, equipment and the system of NF component exception |
| CN109983736B (en) * | 2016-11-21 | 2021-02-12 | 华为技术有限公司 | NF component exception processing method, device and system |
| US11178000B2 (en) | 2016-11-21 | 2021-11-16 | Huawei Technologies Co., Ltd. | Method and system for processing NF component exception, and device |
| WO2018120150A1 (en) * | 2016-12-30 | 2018-07-05 | 华为技术有限公司 | Method and apparatus for connection between network entities |
| CN109542964A (en) * | 2018-11-06 | 2019-03-29 | 用友网络科技股份有限公司 | A kind of data calling method and data calling system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104579889B (en) | 2018-03-09 |
| WO2015055102A1 (en) | 2015-04-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104579889A (en) | Method and device for calling NF (network function) | |
| US8769040B2 (en) | Service providing system, a virtual machine server, a service providing method, and a program thereof | |
| JP5131239B2 (en) | IP address allocation control program, IP address allocation control device, and IP address allocation control method | |
| CN109981493B (en) | Method and device for configuring virtual machine network | |
| CN104243265A (en) | Gateway control method, device and system based on virtual machine migration | |
| CN104052789A (en) | Load balancing for a virtual networking system | |
| CN103516547B (en) | A kind of network parameter distribution method and device | |
| CN106031116A (en) | Method, apparatus and system for associating NS with VNF | |
| CN103677858A (en) | Method, system and device for managing virtual machine software in cloud environment | |
| CN111736955A (en) | Data storage method, device and equipment and readable storage medium | |
| CN102340410B (en) | Cluster management system and method | |
| CN108574613B (en) | Two-layer intercommunication method and device for SDN data center | |
| CN102420820A (en) | Fence method in cluster system and apparatus thereof | |
| CN103631652A (en) | Method and system for achieving virtual machine migration | |
| CN111538561A (en) | OpenStack large-scale cluster deployment test method and system based on KVM virtualization technology | |
| JP2016119583A (en) | Ip telephone network system, server, ip exchange unit and resource capacity expansion method | |
| CN114422350B (en) | Public cloud container instance creation method | |
| CN104426816B (en) | A kind of virtual machine communication method and device | |
| CN108540408B (en) | Openstack-based distributed virtual switch management method and system | |
| CN104092661A (en) | Serial port communication method and apparatus of virtual machines | |
| CN103020068B (en) | A kind of synchronous method and synchronous device | |
| CN102185881A (en) | Household digital equipment wireless multi-protocol space sharing storage manager and method | |
| CN105812434B (en) | Business chain control method and device after the virtualization of user's handheld device | |
| WO2016206399A1 (en) | Communication equipment, device and software version upgrade method utilized in communication equipment | |
| CN106330542B (en) | Access method, control device, system and equipment of remote backup switch |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |