Messaging Client Contact Reconfiguration During Phone Number Changes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing messaging systems face challenges when users change their phone numbers, as the association between the user and their phone number breaks, leading to disruptions in message threads and communication.

Innovation Solution

A messaging system that updates contact information by receiving a contact phone number update, determining existing message threads, and sending notifications to users, allowing seamless communication using the new phone number, while maintaining existing message threads and group memberships.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If the messaging system uses phone number to identify users and message threads, then user identification and message threading are simplified, but the system cannot accommodate phone number changes without breaking the association

Engineering Contradiction:
Improveuser identification mechanismVSAvoidaccommodation of phone number changes
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The system proactively detects phone number changes by monitoring incoming messages from new phone numbers and automatically initiates the thread association process before the user needs to manually reconfigure anything. This preliminary detection and automatic association maintains simplicity while adapting to number changes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically updates message thread associations when phone number changes are detected. Instead of a static phone number-to-thread mapping, the system allows the association to be dynamically reconfigured by detecting messages from new numbers and automatically linking them to the appropriate existing threads, thus accommodating changes while maintaining simplicity.

Inventive Principle:
Principle #15Dynamics

2Reliability

If the system creates new message threads for each phone number, then each thread is clearly associated with a specific number, but the user experience is disrupted when phone numbers change

Engineering Contradiction:
Improvethread-phone number associationVSAvoiduser experience during number change
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system detects phone number changes proactively by monitoring for incoming messages from new phone numbers and automatically associates them with the correct message threads before the user experiences any disruption. This maintains reliable association while preserving ease of operation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses the message content and metadata as an intermediary to bridge the gap between the new phone number and the existing message thread. By analyzing the incoming message from the new number and matching it with the appropriate thread context, the system maintains reliable association without disrupting the user experience.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If the system manually updates contact information, then accuracy is maintained, but time and user effort are required

Engineering Contradiction:
Improvecontact information accuracyVSAvoidtime for manual update
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system automatically detects phone number changes by monitoring incoming messages and self-updates the contact information associations without requiring user intervention. This maintains accuracy through automatic detection while eliminating the time loss associated with manual updates.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses incoming messages as feedback signals to detect phone number changes. When a message arrives from a new phone number, the system analyzes this feedback and automatically updates the contact associations, maintaining accuracy without requiring user time for manual updates.

Inventive Principle:
Principle #23Feedback

4Device complexity

If the system loses message thread association during phone number changes, then the identification mechanism remains simple, but communication continuity is broken

Engineering Contradiction:
Improveidentification mechanismVSAvoidcommunication continuity
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system dynamically reassociates message threads with new phone numbers by detecting incoming messages and automatically updating the associations. This maintains the simplicity of the identification mechanism while ensuring communication continuity through adaptive reconfiguration.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system proactively detects phone number changes and automatically reestablishes thread associations before communication continuity is affected. This preserves the simple identification mechanism while preventing breaks in communication through preliminary detection and automatic recovery.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10313503B2Techniques to reconfigure messaging clients during contact information changes
Publication Date: 2019.06.04 WHATSAPP LLC
  • US10313503B2 patent drawing
  • US10313503B2 patent drawing
  • US10313503B2 patent drawing

AI summary

Techniques to reconfigure messaging clients during contact information changes are described. In one embodiment, an apparatus may comprise a messaging component operative to receive a contact phone number update at a messaging client on the client device from a messaging system, the contact phone number update associated with a contact with the messaging client, the contact phone number update comprising a previous phone number and an updated phone number; determine an existing message thread for the messaging client identified based on the previous phone number; and send a user message to the contact via the messaging system using the updated phone number as a destination address; and a user interface component operative to display a contact phone number change notification in the existing message thread; and receive the user message for the contact. Other embodiments are described and claimed.