Selective Service Redirection for Telecom Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The 'cap and grow' approach for transitioning from legacy telecommunication services to IP-based services is risky and resource-intensive, requiring a complete replacement of existing systems and redirection of all calls/orders, which is inefficient and high-risk.
Innovation Solution
A method that selectively redirects legacy service orders to IP-based services by determining availability and compatibility of upgrade components using hardware sensors, allowing for gradual substitution of services on an individual order basis without disrupting the entire system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a complete replacement service is built using cap and grow approach, then all legacy services can be migrated to IP-based services, but the system complexity and risk increase significantly
Solution Approach 1:
The patent segments the service migration process by treating individual service orders independently rather than migrating all services at once. Each service order is evaluated separately for upgrade eligibility, allowing selective migration to IP-based services while maintaining legacy services for other orders. This segmentation reduces overall system complexity by avoiding a monolithic replacement approach.
Solution Approach 2:
The patent applies partial action by migrating only the portion of services that are eligible for upgrade based on specific criteria (such as service type, customer profile, or technical readiness). Not all legacy services are migrated simultaneously, but only those that meet predetermined conditions, thereby reducing the immediate complexity burden while still achieving progressive modernization.
2Reliability
If a complete replacement service is built, then all calls can be redirected to the new service, but upfront work and risk increase significantly
Solution Approach 1:
The patent performs preliminary evaluation of each service order before migration to determine eligibility for upgrade. Criteria such as service type compatibility, customer readiness, and technical feasibility are assessed in advance. This preliminary action filters out unsuitable candidates early, reducing the risk of migration failures and avoiding time-consuming rework later in the process.
Solution Approach 2:
The migration approach is made dynamic by continuously assessing individual service orders against evolving criteria rather than using a fixed migration schedule. The system can adapt its migration strategy based on real-time conditions, customer feedback, and service characteristics, allowing flexible decision-making that reduces both upfront work and overall risk.
3Productivity
If all orders are sent to the new service for fulfillment, then complete service replacement is achieved, but the risk of service disruption increases
Solution Approach 1:
The patent segments service fulfillment into two parallel paths: legacy service fulfillment for non-eligible orders and IP-based service fulfillment for eligible orders. This segmentation allows the system to maintain legacy service capabilities while progressively adopting new IP-based services, preventing complete service disruption and ensuring continuous operational capability.
Solution Approach 2:
The patent introduces an intermediary evaluation and selection mechanism that determines which service orders should be routed to IP-based services and which should remain on legacy infrastructure. This intermediary layer acts as a filter and mediator, making informed routing decisions that balance productivity improvements with risk mitigation, ensuring that only appropriate services are migrated while others continue on proven legacy platforms.
Data Source
AI summary
A method, system, and/or computer program product improves an operation of an enterprise network. One or more processors receive an electronic request for delivery of a legacy component to an enterprise network of an enterprise. The processor(s) determine whether an upgrade component is available to the enterprise to replace the legacy component in the enterprise network based on predetermined request throttling parameters set by a receiver of the electronic request. The processor(s), in response to determining that the upgrade component is available to the enterprise, query a hardware sensor in the enterprise network for a sensor reading that indicates whether the upgrade component is compatible with an architecture of the enterprise network. The processor(s), in response to determining that the sensor reading indicates that the upgrade component is compatible with the enterprise network, reconfigure the enterprise network by an electronic installation of the upgrade component into the enterprise network.