SCIM Threshold Management for IMS Session Orchestration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current orchestration engines, such as SCIM, waste system resources due to constant updates of application thresholds across multiple applications, especially as system complexity and the number of applications increase, as all applications are notified of threshold changes, leading to inefficiencies.
Innovation Solution
Implementing a system where each application manages its own threshold and updates it only if the current threshold is lower, allowing applications to set and manage multiple thresholds independently without needing to update or cancel others, using a SCIM to notify applications when thresholds are met and enabling them to request new threshold values based on urgency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all applications are notified of threshold changes, then applications can maintain synchronized threshold states, but system resources are wasted due to constant updates across multiple applications
Solution Approach 1:
The patent extracts the threshold management functionality from the SCIM and places it within each application. Each application maintains its own threshold state locally, eliminating the need for SCIM to notify all applications of threshold changes. This extraction reduces system resource consumption while maintaining threshold synchronization through independent local management.
Solution Approach 2:
Each application independently manages its own threshold state without requiring notifications from the SCIM. The application autonomously determines when to update thresholds and executes business logic based on its own threshold conditions, eliminating the resource-intensive broadcast notification mechanism while maintaining reliable threshold state across the system.
2Device complexity
If multiple applications manage multiple thresholds independently, then application complexity is reduced, but coordination between applications becomes challenging
Solution Approach 1:
The patent introduces a parameter-based coordination mechanism where applications compare their desired threshold values against a current threshold parameter. Each application can request threshold updates by comparing its calculated threshold against the current value, and only updates if its value is lower (more urgent). This parameter comparison approach simplifies individual application logic while maintaining systematic coordination.
Solution Approach 2:
The system implements feedback through the SCIM notifying applications when thresholds are met. Each application receives feedback about threshold status and can autonomously decide whether to update its threshold based on its business logic. This feedback mechanism enables independent application operation while maintaining system-wide coordination through standardized notification protocols.
3Adaptability or versatility
If applications can update and cancel thresholds freely, then applications can adapt to changing conditions, but system control becomes difficult to manage
Solution Approach 1:
The patent implements dynamic threshold management where applications can update thresholds based on changing conditions, but the SCIM maintains control by managing the current threshold state. The system dynamically adapts to application needs while the SCIM orchestrates threshold updates centrally, preventing chaos through coordinated state management. Applications request updates, but the SCIM controls the actual threshold state transitions.
Solution Approach 2:
The SCIM acts as an intermediary between applications and the threshold control path. Applications communicate threshold requirements to the SCIM, which mediates the actual threshold updates and maintains the current threshold state. This intermediary role allows applications to adapt freely while the SCIM manages system control complexity by centralizing threshold state management and coordination.
Data Source
AI summary
In accordance with various embodiments, systems and methods that integrate threshold management into a SCIM/Service Broker are provided. Such a system can include a plurality of applications, executing on one or more application servers. The system can also include a SCIM/Service Broker which is operable to manage a threshold set by the applications. Each application can determine an application threshold, a current threshold and a met threshold. When an application receives a message from the SCIM/Service Broker, the application can determine if the met threshold exists and, if the met threshold exists, update the application threshold accordingly. The application can also determine if the application threshold has been met, and if the application threshold has been met, execute business logic associated with the application threshold and set a new application threshold. The application sends a request to SCIM/Service Broker requesting a new current threshold value be set.