Endpoint Cleanliness Scoring for VoIP Telephony

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The rapid cycling and recycling of phone numbers and communication endpoints due to increased usage in VoIP and other telephony applications lead to 'dirty' endpoints, causing unintended communication issues and network/protocol problems, which existing technologies fail to effectively address.

Innovation Solution

A method for providing clean endpoint addresses involves managing a collection of endpoints, testing their communication functionality, generating a cleanliness score, and filtering undesired communications, allowing for the reuse and reassignment of endpoints while preventing unwanted connections.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If phone numbers are rapidly cycled and recycled due to increased VoIP and telephony application usage, then the availability and versatility of endpoint addresses improve, but the cleanliness and reliability of endpoints deteriorate due to dirty endpoints receiving unintended communications

Engineering Contradiction:
Improveavailability of endpoint addressesVSAvoidcleanliness of endpoints
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary testing and evaluation of endpoints before assigning them to users. This includes monitoring incoming communications, analyzing communication patterns, and determining cleanliness scores in advance of assignment, ensuring that only clean endpoints are distributed while maintaining rapid recycling capability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system continuously monitors communication patterns on endpoints and provides feedback about cleanliness status. This feedback mechanism tracks incoming calls, identifies wrong number patterns, and updates endpoint cleanliness scores dynamically, allowing the system to maintain reliability while enabling rapid endpoint cycling

Inventive Principle:
Principle #23Feedback

2Reliability

If endpoints are monitored and tested for cleanliness before assignment, then the reliability and quality of telephony services improve, but the complexity of the endpoint management system increases

Engineering Contradiction:
Improvequality of telephony servicesVSAvoidendpoint management system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs self-testing and self-evaluation of endpoints through automated monitoring of communication patterns. The endpoint management system autonomously determines cleanliness scores by analyzing incoming communications without requiring manual inspection, reducing operational complexity while maintaining high reliability

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The monitoring system performs multiple functions simultaneously: it tracks incoming communications, analyzes communication patterns, determines cleanliness scores, and provides feedback for assignment decisions. This multi-functional approach consolidates what could be separate complex systems into a unified endpoint management platform

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS8416923B2Method for providing clean endpoint addresses
Publication Date: 2013.04.09 TWILIO INC
  • US8416923B2 patent drawing
  • US8416923B2 patent drawing
  • US8416923B2 patent drawing

AI summary

A method for providing clean endpoints including managing a collection of endpoints; testing communication of an endpoint of the collection of endpoints; and generating a cleanliness score for the endpoint according to results of the test. The method functions to create a metric that can be used to evaluate undesired communication activity and functionality of an endpoint. The method may be implemented by any suitable platform providing endpoint addresses to clients, which may include service providers, internet-telephony platforms, or any suitable entity. The method is preferably applied to telephony endpoints used in internet-telephony applications, but may be used in any suitable application.