Finite State M2M Protocol for Constrained IoT Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing IoT protocols, such as CoAP, are too resource-intensive for constrained M2M devices, leading to complexity and inefficiency in tasks like controlling devices with limited battery, CPU, and memory, such as smart home sensors.

Innovation Solution

Implementing a method for M2M devices to be configured with a finite number of predetermined states and transitions, allowing for minimal communication with a server to execute these transitions, using a binary protocol with message formats that can be 1, 2, or 3 bytes long, reducing data transmission and processing load.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional Internet protocols like CoAP are used for M2M communication, then data integrity and interoperability are maintained, but the protocol becomes too heavy and complex for constrained devices with limited battery, CPU, and memory

Engineering Contradiction:
Improvedata integrityVSAvoidprotocol complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The communication protocol is segmented into discrete, manageable components: a finite number of predetermined states (0-255) and transitions between them. Each state represents a specific operational mode or data state, and transitions represent controlled changes between states. This segmentation allows the protocol to maintain reliability through structured state management while reducing overall complexity compared to traditional full-protocol implementations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The invention extracts only the essential functionality needed for M2M communication from traditional protocols like CoAP. By removing unnecessary protocol overhead and focusing solely on state management and transitions, the system achieves data integrity and interoperability without the burden of complete protocol implementations, thereby reducing device complexity and resource requirements.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If CoAP binary protocol with integrity checking and reliability confirmation is implemented, then data integrity and message reliability are ensured, but unnecessary processing burden is imposed on devices with very limited capabilities

Engineering Contradiction:
Improvemessage reliabilityVSAvoidprocessing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The protocol performs preliminary actions by pre-defining all possible states and transitions before communication begins. The M2M device is configured with a finite number of predetermined states and transitions in advance, eliminating the need for real-time protocol parsing and validation. This preliminary configuration ensures message reliability through predetermined state transitions while significantly improving processing efficiency by reducing on-device computational requirements.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If lightweight protocols like CoAP and MQTT are used for M2M devices, then device constraints are addressed, but the protocols remain too heavy for specific scenarios requiring minimal resource usage

Engineering Contradiction:
Improveprotocol adaptabilityVSAvoidbattery consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The invention changes the fundamental parameters of the communication protocol by using a finite state machine approach with predetermined states (0-255) and transitions. This parameter change enables the protocol to adapt to highly constrained environments by reducing the computational and energetic overhead associated with traditional lightweight protocols, while still maintaining versatility for various M2M application scenarios.

Inventive Principle:
Principle #35Parameter changes

4Device complexity

If finite number of predetermined states and transitions are configured in M2M device, then communication is simplified and data strain is reduced, but device flexibility to handle unexpected states is limited

Engineering Contradiction:
Improvecommunication complexityVSAvoidstate adaptability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The finite state machine framework provides universality by defining a comprehensive set of predetermined states and transitions that can handle a wide range of operational scenarios. The standardized state and transition definitions enable the same framework to serve multiple functions across different M2M applications, maintaining adaptability while simplifying communication through structured state management.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10869172B2Management of communication between M2M device and M2M server with finite state transitions created by the M2M device
Publication Date: 2020.12.15 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US10869172B2 patent drawing
  • US10869172B2 patent drawing
  • US10869172B2 patent drawing

AI summary

A method performed by a machine-to-machine, M2M, server for managing communication with a M2M device is disclosed. The method comprising configuring the M2M device with a finite number of predetermined states and predetermined transitions for moving the M2M device into one of its predetermined states, and sending a message to the M2M device for executing at least one of the predetermined transitions.