Mobile Device Identifier Mapping for Targeted Messaging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Third-party entities face challenges in directing mobile devices and users to specific content or portions of applications on mobile devices, as there is no direct correlation between mobile device identifiers known to them and registration identifiers assigned by messaging servers, leading to inefficient message delivery and resource consumption.

Innovation Solution

Creating a mapping between mobile device identifiers and registration identifiers received from message servers, allowing third parties to send targeted messages to mobile devices based on known identifiers, reducing network and computing resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If third parties use mobile device identifiers to send messages, then message targeting capability is improved, but message delivery fails because there is no correlation between mobile device identifiers and registration identifiers

Engineering Contradiction:
Improvemessage targeting capabilityVSAvoidmessage delivery success
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The patent introduces a mapping table as an intermediary data structure that correlates mobile device identifiers with registration identifiers. This mapping table acts as a mediator between the third party's known identifiers and the messaging server's required identifiers, enabling successful message delivery while maintaining precise targeting capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If third parties send messages to all mobile devices, then message delivery reliability is improved, but network and computing resource consumption increases

Engineering Contradiction:
Improvemessage delivery reliabilityVSAvoidnetwork and computing resource consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent enables selective message delivery by allowing third parties to target specific mobile devices using their known identifiers. The mapping table facilitates this localized targeting approach, so messages are sent only to intended recipients rather than all devices, reducing unnecessary network traffic and computing resource consumption while maintaining delivery reliability for targeted messages.

Inventive Principle:
Principle #3Local quality

3Measurement precision

If third parties create a mapping between identifiers, then message targeting precision is improved, but system complexity increases

Engineering Contradiction:
Improvemessage targeting precisionVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The mapping table serves as a simple intermediary structure that adds minimal complexity. It is essentially a data structure that stores identifier pairs, allowing the system to maintain high message targeting precision without requiring complex algorithms or procedures. The mapping table can be implemented as a straightforward lookup mechanism.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The mapping table is created and populated in advance before message sending occurs. This preliminary action allows the system to have the correlation data ready when needed, eliminating the need for complex real-time identifier resolution during message delivery, thus reducing operational complexity while maintaining precision.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10601957B2Sending messages to mobile devices
Publication Date: 2020.03.24 VERIZON PATENT & LICENSING INC
  • US10601957B2 patent drawing
  • US10601957B2 patent drawing
  • US10601957B2 patent drawing

AI summary

A device may receive a request for a mobile device to obtain an application. The request may include a mobile device identifier for the mobile device. The device may send, to the mobile device, a link to a web page. The device may receive, from the mobile device, a request for the web page. The device may send, to the mobile device, a redirect to a software distribution platform to obtain the application from the software distribution platform. The device may receive a registration identifier for the mobile device after the mobile device obtains the application from the software distribution platform. The device may send, to a message server, a request for a message to be sent to the mobile device. The request may be based on the registration identifier and the application.