Auction-Based SFC Placement in NFV Domains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems for managing service function chains (SFCs) in network function virtualization (NFV) domains face inefficiencies in allocating virtual resources across multiple domains, leading to suboptimal SFC placement and increased failure rates due to the lack of a robust, dynamic resource allocation mechanism.
Innovation Solution
An auction-based scheme is implemented where a decision domain sends bid requests to participating domains, ranks them based on resource availability, reputation, and inter-domain costs, and selects the highest-ranked domain to service SFC requests, with subsequent domains being tried if the initial selection fails.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a static resource allocation mechanism is used for SFC placement, then the system complexity is reduced, but the allocation efficiency and adaptability to dynamic resource demands deteriorate
Solution Approach 1:
The patent implements a dynamic resource allocation mechanism where the decision domain continuously monitors resource availability, domain reputation, and inter-domain costs to make real-time SFC placement decisions. The system adapts its allocation strategy based on changing conditions rather than using fixed predetermined rules, thereby improving placement efficiency while managing complexity through automated dynamic adjustment.
Solution Approach 2:
The system incorporates feedback loops where the decision domain receives information about resource utilization status, SFC placement success rates, and domain performance metrics. This feedback is used to update domain reputation scores and adjust future allocation decisions, creating a self-improving system that optimizes resource utilization over time without requiring manual intervention.
2Reliability
If multiple domains are considered for SFC placement, then the success rate and reliability improve, but the decision-making time and processing complexity increase
Solution Approach 1:
The system performs preliminary actions by pre-evaluating and ranking multiple domains based on their resource availability, historical performance, and current workload conditions. The decision domain maintains updated profiles of participating domains including their reputation scores and resource status, enabling rapid selection without requiring full re-evaluation of all domains during each placement decision.
Solution Approach 2:
The patent utilizes parameter changes by dynamically adjusting evaluation criteria such as domain reputation weights, resource availability thresholds, and inter-domain cost factors based on current system conditions. This allows the system to optimize the balance between considering multiple domains and making timely decisions by adapting the complexity of the evaluation process to current operational requirements.
3Ease of operation
If resource allocation is centralized in a single decision domain, then the control simplicity is improved, but the system scalability and load distribution deteriorate
Solution Approach 1:
The system segments the centralized control function by allowing multiple domains to participate as both service providers and potential decision-makers. While a primary decision domain maintains overall coordination, other domains can independently manage their own resources and make localized placement decisions, distributing the control burden and enabling better scalability without sacrificing operational simplicity.
Solution Approach 2:
The decision domain architecture is designed with multi-functionality where any domain can potentially serve as a decision domain depending on current system conditions and resource availability. This universal capability allows the system to scale by having different domains assume decision-making roles as needed, while maintaining a relatively simple control structure through standardized decision protocols.
Data Source
AI summary
A method for managing a service function chain (SFC) includes obtaining, by a SFC orchestrator of a first domain, a SFC creation request for a SFC, in response to the SFC creation request: generating a domain participation list of a set of potential domains that may service the SFC creation request, sending a bid request to each of the set of potential domains, receiving bid responses from the set of potential domains, ranking the set of potential domains, sending a SFC placement request to a second domain of the set of potential domains based on the ranking, and obtaining a SFC placement response from the second domain, wherein the SFC placement response specifies success of SFC placement in the second domain.