Service Capability Layer M2M Caching Coordination

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current M2M systems lack efficient caching mechanisms at the service capability layer, leading to increased latency and reduced throughput due to the inability to effectively manage and authenticate cached resources across M2M devices and servers.

Innovation Solution

Implementing a service capability layer with caching capabilities that provides complete resource discovery, intelligent security mechanisms, and flexible subscription options, along with an M2M cache manager to coordinate caching across multiple servers and virtualize resources, allowing for intelligent resource management and authentication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If caching is implemented at the service capability layer, then latency is reduced and throughput is improved, but device complexity increases due to the need for cache management and coordination mechanisms

Engineering Contradiction:
ImprovelatencyVSAvoidcache management complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The service capability layer acts as an intermediary between M2M applications and the network infrastructure, providing caching services that reduce latency while abstracting away the complexity of cache management from individual devices. The cache manager at the service capability layer coordinates caching operations across multiple servers, handling the complexity centrally rather than at each device level.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The caching system provides self-service capabilities through automatic cache validation, updating, and management. The service capability layer automatically handles cache coherence, validation tokens, and resource discovery, eliminating the need for manual cache management and reducing the operational complexity despite the added functionality.

Inventive Principle:
Principle #25Self-service

2Reliability

If complete resource discovery and intelligent security mechanisms are implemented, then security is improved, but device complexity increases due to additional authentication and resource management functions

Engineering Contradiction:
ImprovesecurityVSAvoidauthentication mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The service capability layer serves as an intermediary that centralizes security functions including authentication, authorization, and resource discovery. By moving these complex security mechanisms to the service capability layer rather than implementing them at each M2M device, the system achieves improved security while preventing the proliferation of complexity across the network.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If M2M service is virtualized in the cloud with coordination across multiple servers, then adaptability is improved, but device complexity increases due to the need for virtualization management and server coordination

Engineering Contradiction:
Improveservice virtualization flexibilityVSAvoidvirtualization coordination complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The service capability layer acts as an intermediary that manages service virtualization and coordination across multiple M2M servers. It provides a unified interface for resource access while handling the complexity of virtualization management, server coordination, and resource mapping internally, thereby enabling adaptability without exposing complexity to individual devices.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If caching resources at the service capability layer is implemented, then productivity is improved through faster data access, but device complexity increases due to the need for cache management infrastructure

Engineering Contradiction:
Improvedata access efficiencyVSAvoidcaching infrastructure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The service capability layer serves as an intermediary caching layer between M2M applications and the network, improving data access efficiency by serving cached resources locally. The complexity of cache management, including validation, updating, and coordination across servers, is handled by the service capability layer infrastructure rather than individual devices, thereby improving productivity without proportionally increasing device complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2829084B1Method and apparatus for supporting machine-to-machine caching at a service capability layer
Publication Date: 2021.05.05 IOT HOLDINGS INC
  • EP2829084B1 patent drawingFigure 1
  • EP2829084B1 patent drawingFigure 2
  • EP2829084B1 patent drawingFigure 3A

AI summary

A method and apparatus for supporting machine-to-machine (M2M) caching at a service capability layer are disclosed. A service capability layer of an M2M entity provides functions that are shared by the M2M applications and expose functionalities to the M2M applications through a set of open interfaces. The service capability layer may be configured to cache resources in a resource structure of the service capability layer. The service capability layer caching can provide complete cached resource discovery, and provide more intelligent and robust security mechanism to authenticate the clients, and subscription to the cached resource becomes flexible and feasible. M2M service may be virtualized in a cloud. An M2M cache manager may maintain a record of resources cached in a plurality of M2M servers and coordinate the M2M servers in caching the resources. The M2M cache manager may provide mapping between a virtualized cached resource and a real cached resource.