Push Notification Device Token Updates with Match-Based Transmission

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The frequent need for applications to acquire and transmit device tokens to push notification request management servers leads to increased communication load, as device tokens are not changed frequently and thus unnecessary transmissions occur.

Innovation Solution

Implement a mechanism where an information processing apparatus transmits first identification information to a server and performs control processes to acquire and transmit second identification information only when the first and second identification information do not match, reducing unnecessary transmissions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the application acquires and transmits the device token every time it is started, then the push notification request management server always holds the latest device token, but the communication load of the push notification request management server is increased

Engineering Contradiction:

Improvedevice token freshnessVSAvoidcommunication load

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The application periodically acquires the device token from the push notification management server at predetermined intervals (e.g., every 24 hours) rather than continuously or on every startup. This periodic acquisition maintains device token freshness while significantly reducing communication load on the push notification request management server.

Inventive Principle:

Principle #19Periodic action

Solution Approach 2:

The application acquires the device token in advance from the push notification management server and stores it locally. This preliminary action ensures that the latest device token is available when needed for push notification distribution, eliminating the need for frequent real-time acquisitions and reducing communication load.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If the application communicates with the push notification management server whenever it is started, then the latest device token is always acquired, but unnecessary transmissions occur since the device token is not changed very frequently

Engineering Contradiction:

Improvedevice token accuracyVSAvoidcommunication frequency

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The application implements periodic communication with the push notification management server at predetermined intervals instead of communicating on every startup. This approach maintains device token accuracy by regularly updating the token while reducing unnecessary transmissions and communication time waste.

Inventive Principle:

Principle #19Periodic action

Solution Approach 2:

The application compares the newly acquired device token with the previously stored device token before transmission. If the tokens match (indicating no change), the application skips the transmission to the push notification request management server. This feedback mechanism ensures device token accuracy is maintained while eliminating unnecessary transmissions.

Inventive Principle:

Principle #23Feedback

3Reliability

If the device token is transmitted to the push notification request management server whenever the push notification-supporting application is started, then the server always has current token information, but the communication load is increased due to frequent transmissions

Engineering Contradiction:

Improvetoken information currencyVSAvoidcommunication efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The application compares the newly acquired device token with the previously stored device token and only transmits to the push notification request management server if they differ. This feedback-based transmission strategy ensures the server always has current token information while dramatically improving communication efficiency by eliminating redundant transmissions.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The application adopts periodic token acquisition at predetermined intervals rather than continuous transmission on every startup. This approach maintains token information currency while reducing the frequency of communications with the push notification request management server, thereby improving overall system productivity.

Inventive Principle:

Principle #19Periodic action

Data Source

PatentUS20250227159A1Storage medium storing program that can reduce communication load of device token, method of controlling information processing apparatus, and information processing apparatus

Publication Date: 2025.07.10 CANON KK

AI summary

A non-transitory computer-readable storage medium storing a program for causing a computer to execute a method of controlling an information processing apparatus in which an application has been installed. A host computer transmits a device token for identifying the application, acquired from a push notification management server, to a push notification request management server that issues a push notification to the host computer, based on the device token. The host computer acquires the latest device token from the push notification management server. The host computer transmits the latest device token to the push notification request management server in a case where the device token transmitted last time and the latest device token do not match, and does not transmit the latest device token to the push notification request management server in a case where the tokens match.