M2M Data Caching via Network Identifier Reuse
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing M2M communication systems face challenges in efficiently caching device-generated data, particularly in asynchronous scenarios where wireless network connectivity is unreliable, and require a mechanism for interim data storage that can uniquely identify and retrieve data from M2M devices without additional identifier provisioning.
Innovation Solution
The method employs the unique identifier used by the wireless communications network, such as IMEI, IMSI, or MSISDN, as a primary key for storing and retrieving device-generated data, allowing for efficient caching and retrieval even in the absence of a viable communication link, and enabling secure data storage and retrieval without the need for new unique identification numbers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a unique identity is provisioned for each M2M device for data storage, then data can be uniquely attributable to the correct device, but the system complexity increases significantly
Solution Approach 1:
The patent applies universality by making the existing device identifier serve multiple functions: it is used both for device identification in the wireless network and as the primary key for data storage and retrieval. This eliminates the need for separate unique identities for data storage, reducing system complexity while maintaining reliable data attribution to the correct device
Solution Approach 2:
The patent merges the device identification function and data storage identification function by using the same device identifier for both purposes. Instead of having separate identifier systems for network communication and data storage, the solution combines these functions into a single unified identifier system
2Reliability
If data is stored directly from M2M devices without interim storage, then data freshness is maintained, but data cannot be retrieved when communication link is unavailable
Solution Approach 1:
The patent applies preliminary action by storing device-generated data in an interim storage mechanism before it is finally consumed by the application. This allows data to be cached and made accessible in advance, so that when a retrieval request comes in (even when the device is unavailable), the data can be quickly returned from storage rather than requiring real-time device communication
3Productivity
If asynchronous data exchange is implemented, then network traffic peaks are smoothed, but data retrieval speed may be reduced
Solution Approach 1:
The interim storage mechanism pre-positions data in a readily accessible location before retrieval is needed. When an asynchronous retrieval request arrives, the data can be quickly copied from storage to the application without requiring slow device reconnection, thus maintaining fast retrieval speed while benefiting from asynchronous communication
Data Source
AI summary
There is provided a method of caching device generated data. The method comprises receiving device generated data from a device via a wireless communication network. The method further comprises retrieving a device identifier used by components within the wireless communication network to identify the device; and storing the device generated data with the device identifier.