Service Level Agreement Based Resource Allocation Prioritization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for allocating shared computing resources fail to efficiently account for the varying needs and service level agreements of different customers, leading to inefficient resource allocation and potential violations of service level agreements due to rapid changes and heavy network traffic.
Innovation Solution
A method that receives and prioritizes requests based on stored customer information, including service level agreements, to configure a shared infrastructure, ensuring that resources are allocated according to the terms and performance data of each customer, thereby optimizing resource utilization and minimizing violations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If all customers are treated alike with first-come, first-served allocation, then the allocation process is simple and fast, but resource allocation efficiency deteriorates because it does not account for customer differences and service level agreements
Solution Approach 1:
The patent applies local quality by differentiating allocation rules based on customer characteristics. Different customers receive different priority levels and resource allocation treatments according to their specific service level agreements and entitlements, rather than applying a uniform first-come first-served rule to all customers.
Solution Approach 2:
The system changes the allocation parameter from simple temporal order (first-come first-served) to a multi-dimensional parameter including customer priority level, service level agreement terms, and current resource availability. This allows the allocation mechanism to adapt to different customer needs while maintaining operational efficiency.
2Productivity
If resource allocation decisions are complex to account for customer differences, then resource allocation efficiency improves, but the complexity of the allocation system increases
Solution Approach 1:
The system performs preliminary actions by pre-establishing customer profiles, service level agreements, and priority levels before resource allocation decisions are needed. This pre-configuration allows the complex allocation logic to execute efficiently during actual resource requests, reducing real-time computational complexity.
Solution Approach 2:
The patent introduces an intermediary allocation manager that sits between resource requests and the actual resource allocation. This intermediary component handles the complex decision-making logic, evaluating customer entitlements and service level agreements, while presenting a simplified interface to both customers and resource providers.
3Speed
If rapid changes in resource allocation are implemented to handle fluctuations, then responsiveness to customer needs improves, but the likelihood of service level agreement violations increases due to heavy network traffic
Solution Approach 1:
The system implements feedback mechanisms that continuously monitor resource allocation status, customer service level agreement compliance, and system performance. This feedback loop allows the allocation manager to make real-time adjustments that maintain service level agreement compliance even during rapid allocation changes and high traffic conditions.
Solution Approach 2:
The patent applies dynamics by making the allocation system adaptable and flexible in response to changing conditions. Priority levels and allocation parameters can be dynamically adjusted based on current resource availability, customer needs, and service level agreement requirements, allowing the system to respond rapidly while maintaining reliability.
Data Source
AI summary
A solution provided here comprises receiving requests for a service from a plurality of customers, responding to the requests for a service, utilizing a shared infrastructure, and configuring the shared infrastructure, based on stored customer information. Another example of such a solution comprises:analyzing at least one provisioning request;assigning a priority to the provisioning request, based on performance data and stored customer information;configuring a shared infrastructure, according to the provisioning request and the priority; andresponding to requests for services, utilizing the shared infrastructure.