Dynamic Push SDK Architecture for Cross-Device Reliability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current push software development kits for smart terminal devices have varying push arrival rates across different mobile phone manufacturers, leading to inconsistent push effects and large errors in generated push data, resulting in a bulky APP size with high storage costs and unsatisfactory performance on non-manufacturer devices.
Innovation Solution
A method where the terminal device transmits its model to a server, which provides a suitable push software development kit and configuration file, allowing for initialization and registration, establishing a persistent connection for efficient push information transmission, and using secondary encapsulation to optimize the push software development kit without integrating multiple kits into the APP.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple push software development kits are integrated into the APP to support different device models, then the push arrival rate is improved across various manufacturers, but the APP size increases and storage costs rise
Solution Approach 1:
The patent extracts the push software development kit from the APP package and places it on the server. The terminal device downloads only the configuration file and necessary components locally, while the complete SDK remains on the server. This extraction resolves the contradiction by maintaining push reliability through server-side SDK availability while significantly reducing APP size by storing only essential local components.
Solution Approach 2:
The patent creates a universal push software development kit on the server that can serve multiple device models and manufacturers. Instead of integrating multiple manufacturer-specific SDKs into the APP, a single universal SDK on the server handles push operations for various devices by loading appropriate components based on device model identification, thus improving push arrival rate without increasing APP size.
2Reliability
If manufacturer-specific push software development kits are used, then push performance is optimized for that manufacturer's devices, but push effectiveness deteriorates on other manufacturers' devices
Solution Approach 1:
The patent implements a dynamic push software development kit architecture where the system identifies the terminal device model and dynamically loads the appropriate push components and configuration from the server. This dynamic adaptation allows the same universal SDK to optimize push performance for each specific device manufacturer while maintaining versatility across different platforms, resolving the contradiction between specialized performance and broad adaptability.
Solution Approach 2:
The patent applies local quality by having the universal push software development kit load manufacturer-specific components and configuration files tailored to each device model. The system maintains a repository of different push components on the server and selectively loads the appropriate ones based on device identification, ensuring optimal performance for each manufacturer while maintaining a single universal SDK structure.
3Measurement precision
If push software development kits are updated for each device model, then push data quality is improved, but the complexity of managing multiple kits increases
Solution Approach 1:
The patent introduces a configuration file as an intermediary between the push software development kit and the terminal device. The configuration file contains device model-specific parameters and initialization information, allowing the universal SDK to adapt to different devices without requiring separate SDKs for each model. This intermediary simplifies management by centralizing device-specific information in a structured format that the universal SDK can parse and apply automatically.
Solution Approach 2:
The patent uses parameter changes to adapt the push software development kit to different device models. Instead of maintaining separate SDKs, the system changes the configuration parameters and loaded components based on the identified device model. The configuration file stores these parameters, and the universal SDK dynamically adjusts its behavior by reading and applying the appropriate parameters for each device, thereby improving push data quality while maintaining a single manageable codebase.
Data Source
AI summary
A method for acquiring push information can be applied to a terminal device and include: transmitting a device model of the terminal device to a server; receiving a push software development kit corresponding to the device model, and a configuration file corresponding to the push software development kit transmitted by the server; initializing the push software development kit based on the configuration file, and completing a registration with the server; and receiving, through the push software development kit, push information transmitted by the server. The terminal device can therefore acquire its corresponding push software development kit according to the device model of the terminal device through a plug-in method, thereby increase push arrival rate and improve quality of operational data.