Pseudo Device Identifier Generation for Secure Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Computing and communication devices face challenges in securely using device identifiers, as they can be compromised for unauthorized access, violating policies that restrict certain identifiers from being used for identification.

Innovation Solution

Implementing a pseudo device identifier system, where a mobile DVR application generates a unique pseudo MDN using mathematical functions, ensuring secure communication by converting device identifiers into a format compatible with telephone number formats, thus preventing unauthorized use and policy violations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a device identifier (MDN) is used for communication and authentication, then the device can be identified and authenticated by other devices, but the identifier can be compromised enabling unauthorized access

Engineering Contradiction:
Improveauthentication securityVSAvoidunauthorized access
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces a pseudo device identifier as an intermediary between the actual device identifier and the communication system. The mobile DVR application generates a pseudo MDN that serves as a mediator - it allows the device to be identified and authenticated without exposing the actual device identifier, thus preventing unauthorized access while maintaining authentication functionality

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a copy of the device identifier in the form of a pseudo MDN. This copy has the same format and functionality as the original identifier for communication purposes, but it is not the actual identifier. The pseudo identifier can be compromised without affecting the security of the real device identifier

Inventive Principle:
Principle #26Copying

2Reliability

If certain identifiers are restricted from being used for identification to maintain security policies, then unauthorized access is prevented, but devices cannot be properly identified and authenticated

Engineering Contradiction:
Improvepolicy complianceVSAvoiddevice identification
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent creates a copy of the device identifier (pseudo MDN) that can be used in place of restricted identifiers. This copy maintains the necessary format and functionality for device identification and authentication while complying with security policies that restrict the use of certain actual identifiers

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent changes the parameter of the identifier by generating a pseudo MDN with the same format characteristics as a real MDN but with different actual values. This allows the device to present an identifier that appears valid to the system while actually being a secure alternative that complies with policy restrictions

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8369834B2User device identification using a pseudo device identifier
Publication Date: 2013.02.05 VERIZON PATENT & LICENSING INC
  • US8369834B2 patent drawing
  • US8369834B2 patent drawing
  • US8369834B2 patent drawing

AI summary

A system configured to receive a first request to generate a pseudo identifier associated with a user device; retrieve an identifier associated with the user device; and generate, using a mathematical function, the pseudo identifier based on the identifier associated with the user device, where the pseudo identifier may be generated in a format corresponding to a telephone number. The system is further configured to send a second request to register the user device, where the second request may include the pseudo identifier; receive a confirmation code that permits the user device to access information, associated with the server device, without using the identifier associated with the user device or a telephone number associated with the user device; send a third request for information associated with the server device, where the third request may include the confirmation code; and receive the information associated with the server device.