Data Continuity Service for M2M IoT Data Availability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing M2M/IoT system faces challenges in providing seamless data storage and value-added services to mobile Data Producers due to fragmented data storage across different service layers, leading to difficulties in maintaining data continuity and offering services like data integrity verification and aggregation.
Innovation Solution
The system introduces a Data Continuity service that allows Data Producers to negotiate and initiate data continuity with the M2M/IoT system, enabling autonomous decision-making for data set management, aggregation, and service layer mobility, with methods to store, update, and retrieve data sets while maintaining links between service layers for efficient data access and service provision.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data is stored in distributed service layers to enable mobile access, then data availability to mobile Data Producers is improved, but data fragmentation occurs making it difficult to maintain data continuity
Solution Approach 1:
The patent introduces a Data Continuity Service (DCS) as an intermediary component that mediates between distributed data storage and mobile data access. The DCS maintains context information including data set identifiers, service layer identifiers, and mapping relationships, enabling seamless data continuity as mobile devices move between service layers without requiring data to be physically centralized.
Solution Approach 2:
The patent segments the data continuity management function into distinct components: context information storage, data set tracking, and service layer mapping. This segmentation allows the system to independently manage different aspects of data continuity, enabling mobile devices to access fragmented data across multiple service layers while maintaining the appearance of continuous data availability.
2Stability of the object's composition
If data is centralized in a single service layer to maintain data integrity, then data continuity is improved, but system complexity and operational overhead increase
Solution Approach 1:
The Data Continuity Service acts as a lightweight intermediary that maintains context information without requiring physical data centralization. Instead of moving all data to a single location, the DCS stores metadata including data set identifiers, service layer identifiers, and mapping relationships, significantly reducing system complexity while maintaining data continuity.
Solution Approach 2:
The patent creates a contextual copy of data location information rather than copying the actual data. The context information includes references to where data is stored and how to access it, allowing the system to maintain continuity information without the overhead of duplicating large data sets across service layers.
3Adaptability or versatility
If data is fragmented across multiple service layers for mobile access, then adaptability is improved, but service provisioning complexity increases
Solution Approach 1:
The Data Continuity Service serves as an intermediary that simplifies service provisioning for fragmented data. It maintains mapping relationships between data sets and service layers, automatically resolving data access requests regardless of which service layer currently hosts the data, thereby reducing the operational complexity of provisioning services across distributed data locations.
Solution Approach 2:
The patent creates a universal access mechanism through the Data Continuity Service that works across all service layers and mobile devices. The context information and mapping relationships established by the DCS enable a single service provisioning interface to handle data access requests uniformly, regardless of data fragmentation, making service provisioning easier and more consistent.
4Adaptability or versatility
If data sets are transferred between service layers during mobility, then data availability is maintained, but data transfer time and latency increase
Solution Approach 1:
Instead of physically transferring data sets when mobile devices move between service layers, the system creates or updates contextual references to the data's current location. The context information includes service layer identifiers and data set identifiers that enable direct access to data regardless of its physical location, eliminating transfer time while maintaining availability.
Solution Approach 2:
The Data Continuity Service acts as an intermediary that manages data location tracking without requiring data movement. It maintains mapping relationships between mobile devices, data sets, and service layers, enabling the system to redirect data access requests to the current data location instantaneously, thereby eliminating the latency associated with physical data transfer during mobility events.
Data Source
AI summary
A Data Producer may be configured to negotiate and initiate a Data Continuity service with an M2M/IoT system. This service may be for specific data sets or all data sets generated by the Data Producer. The M2M/IoT system may be configured to autonomously decide to start a Data Continuity Service for a data set of a Data Producer. The Data Producer may interact directly with an Aggregator SL to store its aggregated data set, and may also be configured to update and delete entries in this data set and start a data service on this aggregated data set. A Local SL may be configured to manage all interactions with an Aggregator SL, and the Local SL may be configured to retarget requests from the Data Producer to the Aggregator SL, including a request to start a data service on the aggregated data set.