API-Based CCP Provisioning for Near-Real-Time Trunk Scaling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional methods for changing concurrent call paths (CCPs) require manual intervention and can take several days, increasing customer costs and inefficiency.

Innovation Solution

Implementing API-based CCP provisioning that allows near-real-time adjustments to CCPs and trunk groups based on network utilization data, reducing human interaction and enabling rapid changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual monitoring and ordering of CCP changes is used, then service provisioning can be implemented, but implementation time increases to several days and customer costs increase

Engineering Contradiction:
ImproveCCP provisioning speedVSAvoidImplementation time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent replaces manual mechanical processes (personnel monitoring traffic, manually calling to order changes) with an automated API-based electronic system. The API receives CCP provisioning requests, automatically determines trunk group assignments, and provisions CCPs without human intervention, reducing implementation time from several days to minutes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system enables self-service provisioning where the API autonomously processes CCP provisioning requests by automatically determining trunk group assignments and provisioning parameters without requiring manual customer service intervention. The system serves itself by making intelligent decisions based on received requests and network data.

Inventive Principle:
Principle #25Self-service

2Productivity

If manual CCP provisioning is used, then service changes can be made, but customer costs increase due to manual intervention

Engineering Contradiction:
ImproveProvisioning efficiencyVSAvoidCustomer cost
Core Design Contradiction:
ProductivityVSEase of manufacture

Solution Approach 1:

The patent replaces manual mechanical processes (personnel monitoring traffic, manually calling to order changes) with an automated API-based electronic system. The API receives CCP provisioning requests, automatically determines trunk group assignments, and provisions CCPs without human intervention, reducing implementation time from several days to minutes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system enables self-service provisioning where the API autonomously processes CCP provisioning requests by automatically determining trunk group assignments and provisioning parameters without requiring manual customer service intervention. The system serves itself by making intelligent decisions based on received requests and network data.

Inventive Principle:
Principle #25Self-service

3Loss of time

If API-based CCP provisioning is implemented, then provisioning time is reduced to minutes, but system complexity increases

Engineering Contradiction:
ImproveImplementation timeVSAvoidSystem complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent introduces an API as an intermediary layer between the customer and the network provisioning system. The API receives provisioning requests, automatically determines trunk group assignments using received data, and coordinates with the network system to provision CCPs. This intermediary automates complex decision-making processes, reducing implementation time while managing system complexity through structured interfaces.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20250323998A1Application programming interface (API)-based concurrent call path (CCP) provisioning
Publication Date: 2025.10.16 LEVEL 3 COMMUNICATIONS LLC
  • US20250323998A1 patent drawing
  • US20250323998A1 patent drawing
  • US20250323998A1 patent drawing

AI summary

Novel tools and techniques are provided for implementing application programming interface (“API”)-based concurrent call path (“CCP”) provisioning. In various embodiments, in response to receiving a CCP provisioning request, a computing system may determine whether such a request would affect a set of trunk groups assigned to a customer based at least in part on network utilization data. If not, the computing system may cause the nodes in the network to increase or decrease, in near-real-time, the number of CCPs in at least one trunk group assigned to the customer based on the CCP provisioning request. If so, the computing system may cause the nodes in the network to increase or decrease, in near-real-time, the number of trunk groups assigned to the customer and may cause the nodes in the network to increase or decrease, in near-real-time, the number of CCPs in the updated number of trunk groups.