Client Device Mobile Number Verification Code Management

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing mobile number verification processes on the server side are costly and inefficient due to the need for maintaining large databases of expired confirmation codes, as users often fail to complete the verification process or receive text messages.

Innovation Solution

Implementing a client-side verification process where a client device generates and manages a hidden code, transmits the user-entered mobile number and code to a server, and verifies the code's validity based on user input accuracy and time constraints, eliminating the need for server-side storage of codes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If server-side verification is used to ensure reliable mobile number validation, then verification accuracy is improved, but infrastructure cost and database maintenance burden increase significantly

Engineering Contradiction:

Improveverification accuracyVSAvoiddatabase storage requirements

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts the code generation and verification functionality from the server-side system and relocates it to the client device. The server only needs to send a trigger message to initiate verification, while the actual code generation, storage, and validation occur locally on the client device, eliminating the need for server-side code databases.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The client device performs self-service by autonomously generating verification codes, storing them locally, and validating user input against these codes without requiring server-side verification. The device serves itself by managing the entire verification process locally, reducing server infrastructure requirements.

Inventive Principle:

Principle #25Self-service

2Reliability

If server-side verification with comprehensive code storage is implemented, then verification reliability is improved, but operational cost increases due to database maintenance

Engineering Contradiction:

Improveverification reliabilityVSAvoidoperational cost

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts the code storage and verification functions from the server environment and implements them on the client device. This eliminates the need for servers to maintain large databases of verification codes and their expiration states, significantly reducing operational costs associated with database maintenance and infrastructure.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The verification codes are designed as temporary, short-lived objects that exist only on the client device for a limited time window. Once used or expired, they are discarded locally without needing to be stored or managed on server infrastructure, reducing long-term operational costs.

Inventive Principle:

Principle #27Cheap short-living objects (Disposable)

3Loss of energy

If client-side verification is implemented to reduce infrastructure cost, then operational cost is reduced, but device complexity increases

Engineering Contradiction:

Improveoperational costVSAvoidclient device complexity

Core Design Contradiction:

Loss of energyVSDevice complexity

Solution Approach 1:

The patent merges multiple functions into the client device: code generation, code storage, SMS message reception, and verification validation all occur on the client device. This consolidation eliminates the need for complex server-side infrastructure while distributing the functional load to the client device.

Inventive Principle:

Principle #5Merging (Combining)

4Stability of the object's composition

If server-side verification processes are used, then centralized control is maintained, but verification time increases due to database queries

Engineering Contradiction:

Improvecentralized controlVSAvoidverification time

Core Design Contradiction:

Stability of the object's compositionVSLoss of time

Solution Approach 1:

The verification code is generated and stored on the client device in advance, before verification is needed. When verification is required, the system only needs to compare the user input against the pre-generated code locally, eliminating time-consuming database queries and server-side validation processes.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS9160736B2System and method of verifying a number of a mobile terminal

Publication Date: 2015.10.13 SYNCHRONOSS TECHNOLOGIES INC

AI summary

A client device is coupled with a server. The client device prompts a user to enter a number associated with a mobile device, which can be the client device, and generates data including a code. The code is typically hidden from the user when the code is generated and is saved on the client device. The client device transmits the number entered by the user and the code generated by the client device to the server, which sends a message, including the code, to the mobile device associated with the number. The client device prompts the user to enter the code included in the message. Validity of the number is based on one or more factors, including the accuracy of the code entered by the user. In addition, validity of the number can also be based on whether the second user input was entered within a predetermined time limit.