Network Entity Call Processing Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for configuring telephony features are inconvenient, impractical, and inefficient, requiring users to interact with representatives or IVR systems to set up and modify call processing information, which can lead to errors and inefficiencies, especially when changes need to be made outside of regular interaction times.
Innovation Solution
A method and system that identifies previously-originated calls and uses information related to those calls to configure call processing information for future calls, allowing users to conveniently and efficiently manage their telephony features through a configuration entity that includes a communication unit and a configuration unit, enabling users to modify settings based on past call experiences.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If users interact with representatives or IVR systems to configure telephony features, then call processing information can be configured, but the process becomes inconvenient, impractical, and inefficient
Solution Approach 1:
The system enables users to automatically configure and modify call processing information without requiring interaction with representatives or IVR systems. The network entity autonomously receives configuration information from the user's communication device and updates the call processing settings directly, allowing the system to serve itself rather than requiring external assistance.
Solution Approach 2:
A network entity acts as an intermediary between the user's communication device and the call processing system. This intermediary receives configuration information from the user device and automatically implements the changes, eliminating the need for users to directly interact with representatives or complex IVR systems while ensuring accurate configuration.
2Adaptability or versatility
If users need to modify call processing information outside regular interaction times, then flexibility is improved, but existing methods become impractical
Solution Approach 1:
The system allows users to configure and modify call processing information at any time without needing to contact representatives during specific hours. Users can submit configuration requests through their communication devices, and the network entity automatically processes these requests regardless of the time of day, making the system adaptable to user needs outside regular business hours.
3Reliability
If comprehensive call processing information is configured upfront, then feature functionality is improved, but the complexity of configuration increases
Solution Approach 1:
The system allows users to configure call processing information incrementally rather than requiring all parameters to be set upfront. Users can provide basic configuration information initially, and the network entity can later update and refine the settings based on additional user input or observed call patterns, reducing the initial configuration complexity while ensuring reliable feature application.
Solution Approach 2:
The call processing configuration is made dynamic rather than static. The network entity can receive updates to configuration information at any time and automatically adjust the call processing behavior accordingly. This allows the system to adapt to changing user needs and ensures correct feature application without requiring users to anticipate all future scenarios during initial configuration.
Data Source
AI summary
A method implemented by a network entity. The method comprises identifying a previously-originated call involving a party. The method also comprises receiving information regarding processing of a potential future call related to the previously-originated call. The method further comprises using the information regarding processing of a potential future call related to the previously-originated call to cause configuration of call processing information associated with the party. Also provided is a configuration entity for implementing the method.


