System and method for adaptive paths locator for virtual network function links
US-2016352578-A1 · Dec 1, 2016 · US
US10862763B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10862763-B2 |
| Application number | US-201916662349-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 24, 2019 |
| Priority date | Jun 12, 2015 |
| Publication date | Dec 8, 2020 |
| Grant date | Dec 8, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A network functions virtualization (NFV) network can be configured to operate according to NFV protocols that decouple software functionality from specific hardware elements. A referent system can be provided that identifies a precise physical location of devices associated with the NFV network relative to other equipment or devices associated with the NFV network.
Opening claim text (preview).
What is claimed is: 1. A device, comprising: a processor; and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations, comprising: receiving constraint data indicative of a constraint on a physical location of a processing device that is employed to execute a network function in a virtual environment; performing a selection procedure that selects the processing device that is to execute the network function, the selection procedure comprising: determining a target location that satisfies the constraint data; and matching the target location to referent identifier data that is assigned to the processing device, the referent identifier data comprising: device data that identifies the processing device relative to other devices other than the processing device and reference data that identifies the other devices. 2. The device of claim 1 , wherein the constraint data is determined to be satisfied in response to the network function being executed within a specified jurisdiction. 3. The device of claim 1 , wherein the constraint data is determined to be satisfied in response to the network function being executed within a specified geographical space. 4. The device of claim 1 , wherein the constraint data is determined to be satisfied in response to the network function being executed at a first location that is within a defined distance from a second location. 5. The device of claim 4 , wherein the defined distance is determined based on a latency calculation indicative of a latency that results from communication between the first location and the second location. 6. The device of claim 1 , wherein the operations further comprise instructing the processing device to execute the network function. 7. The device of claim 1 , wherein the operations further comprise instructing the processing device to associate the network function with the referent identifier data, resulting in a record of the physical location of the processing device that executes the network function. 8. The device of claim 1 , wherein the processing device is one of a group of processing devices situated on a floor of a building, and wherein the referent identifier data identifies the floor and the building. 9. The device of claim 1 , wherein the processing device is one of a group of processing devices situated in a shelf of a device bay, and wherein the referent identifier data identifies the shelf and the device bay. 10. The device of claim 1 , wherein the device data and the reference data are non-unique identifiers that, when combined, represent a unique identifier. 11. The device of claim 1 , wherein the operations further comprise, in response to a determination that the processing device has spare computing capacity, generating status data comprising the referent identifier data and an indicator that indicates the processing device has spare computing capacity. 12. The device of claim 1 , wherein the operations further comprise, in response to a determination that the processing device is to be serviced, generating status data comprising the referent identifier data and an indicator that indicates the processing device is to be serviced. 13. A machine-readable storage medium, comprising executable instructions that, when executed by a processor, facilitate performance of operations, comprising, comprising: receiving constraint data indicative of a constraint on a physical location of a processing device that is employed to execute a network function in a virtual environment; performing a selection procedure that selects the processing device that is to execute the network function, the selection procedure comprising: determining a target location that satisfies the constraint data; matching the target location to referent identifier data that is assigned to the processing device, the referent identifier data comprising: device data that identifies the processing device relative to other devices other than the processing device and reference data that identifies the other devices; and instructing the processing device to execute the network function. 14. The machine-readable storage medium of claim 13 , wherein the device data and the reference data are non-unique identifiers that, when combined, represent a unique identifier. 15. The machine-readable storage medium of claim 13 , wherein the constraint data is determined to be satisfied in response to the network function being executed within a specified geographical space that is specified by the constraint. 16. The machine-readable storage medium of claim 13 , wherein the constraint data is determined to be satisfied in response to the network function being executed at a first location that is within a defined distance from a second location. 17. A method, comprising: receiving, by a device comprising a processor, constraint data indicative of a constraint on a physical location of a processing device that is employed to execute a network function in a virtual environment; performing, by the device, a selection procedure that selects the processing device that is to execute the network function, the selection procedure comprising: determining, by the device, a target location that satisfies the constraint data; matching, by the device, the target location to referent identifier data that is assigned to the processing device, the referent identifier data comprising: device data that identifies the processing device relative to other devices other than the processing device and reference data that identifies the other devices; and instructing, by the device, the processing device to execute the network function. 18. The method of claim 17 , further comprising, instructing, by the device, the processing device to associate the network function with the referent identifier data, resulting in a record of the physical location of the processing device that executes the network function. 19. The method of claim 17 , further comprising, in response to a determination that the processing device has spare computing capacity, generating, by the device, status data comprising the referent identifier data and an indicator that indicates the processing device has spare computing capacity. 20. The method of claim 17 , further comprising, in response to a determination that the processing device is to be serviced, generating, by the device, status data comprising the referent identifier data and an indicator that indicates the processing device is to be serviced.
Hypervisor-specific management and integration aspects · CPC title
the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV · CPC title
using virtualisation of network functions or resources, e.g. SDN or NFV entities · CPC title
of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV] · CPC title
by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.