Ringtone-Generation Engine for Personalized Caller ID and Ringback Services

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current telecommunication systems lack the ability for calling parties to influence their ringtones and require users to manually associate ringtones with each calling party, leading to inconsistencies and tedium in identifying different callers across different devices.

Innovation Solution

Implementing a system with ringtone-generation engines at both source and destination nodes in telecommunication networks to dynamically generate and provide audible Caller ID and ringback services, allowing for personalized ringtones based on calling-party or called-party information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If the receiving party manually associates ringtones with calling party numbers, then the receiving party can identify different calling parties, but the process becomes tedious and time-consuming

Engineering Contradiction:
Improvecalling party identification accuracyVSAvoidtime to associate ringtones with calling parties
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system enables automatic ringtone association by having the calling party select and transmit their preferred ringtone to the network. The network then automatically delivers this ringtone to the receiving party's device, eliminating the need for manual association by the receiving party while maintaining accurate calling party identification

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The calling party pre-selects their ringtone preference in advance during account setup or profile configuration. This preliminary action stores the ringtone association in the network database before actual calls occur, enabling automatic delivery without real-time manual intervention

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If each receiving telephone has its own ringtone-to-calling party number associations, then users can personalize their experience, but consistency across different devices is lost

Engineering Contradiction:
Improvepersonalization capabilityVSAvoidringtone association consistency
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The network acts as an intermediary that stores and manages ringtone associations centrally. When a call is made, the network retrieves the appropriate ringtone from its database and delivers it to the receiving party's device, ensuring consistent delivery across all devices while still allowing personalization through calling party preferences

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system provides universal ringtone delivery service that works across all receiving devices regardless of manufacturer or model. The network's central database serves all users uniformly, ensuring that the same calling party delivers the same ringtone to any receiving device, while still allowing individual customization through the calling party's preferences

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

3Ease of operation

If the receiving party selects ringtones from limited preprogrammed options, then the receiving party has control over their device, but the variety and personalization options are restricted

Engineering Contradiction:
Improveringtone selection controlVSAvoidringtone variety
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system transitions from static preprogrammed ringtones stored in device memory to dynamic ringtone delivery where the network provides ringtones on-demand. The receiving party's device can display and play ringtones that are delivered dynamically from the network, greatly expanding the available variety while maintaining user control through selection interfaces

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system adds a new dimension to ringtone availability by moving from local device storage to network-based delivery. This external dimension provides access to a much larger pool of ringtones stored on network servers, transforming the limited local library into an expansive on-demand collection

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

4Ease of operation

If the calling party cannot influence the ringtone, then the receiving party maintains full control, but the calling party's ability to communicate their identity is reduced

Engineering Contradiction:
Improvereceiving party controlVSAvoidcalling party identity expression
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The system inverts the traditional control model by allowing the calling party to select and transmit their ringtone preference to the network. The receiving party then receives this ringtone information from the network, effectively giving the calling party control over their identity expression while the receiving party maintains control through the ability to accept or reject the delivered ringtone

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentUS7602901B1System and method for providing calling-party identification and/or calling-party or called-party ringback services
Publication Date: 2009.10.13 SPRINT SPECTRUM LLC
  • US7602901B1 patent drawing
  • US7602901B1 patent drawing
  • US7602901B1 patent drawing

AI summary

A method and system for providing an audible calling party identification and/or an audible calling/called party ringback services (“services”) is disclosed. The system may include (and the method may perform the services in) a network having source, network, and destination nodes. The source and destination nodes may be equipped with ringtone-generation engines to generate ringtones. Each of the ringtones includes at least one audible tone.The method may include the source and/or destination node receiving from the network node information for producing a ringtone (“ringtone information”). The ringtone information is originated toward the destination node in response to the source node initiating a call to the destination node. After receipt, the source and/or destination nodes may generate the ringtone using their ringtone-generation engines and the ringtone information. After generating the ringtones, the source and/or destination ringtone-generation engines may provide them to users of the respective source and/or destination nodes.