IoT Compression Context Setup for LPWA Header Overhead

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Low Power Wide Area (LPWA) networks, such as NB-IoT, provide limited bandwidth, and existing IP-based IoT protocols are not optimized for low-bandwidth links, leading to wasteful traffic transmission and energy consumption, with protocols like RoHC and SCHC requiring complex implementations and context learning phases.

Innovation Solution

A mechanism for establishing a preconfigured IP capable compression context between an IoT controller and an IoT device, using a context pointer for retrieving compression contexts and a gateway interface for virtual IP address assignment, allowing the use of SCHC without implementing it in the cellular network, thus reducing traffic and energy consumption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If IP-based protocols are used for data transmission in LPWA networks, then data can be transmitted using standard protocols, but bandwidth is wasted and energy consumption increases

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidenergy consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies parameter changes by modifying the data transmission format through header compression. The SCHC mechanism changes the parameters of IP packets by compressing headers according to pre-configured context rules, transforming full IP packets into compressed representations that consume less bandwidth and energy while maintaining protocol compatibility for standard IoT devices.

Inventive Principle:
Principle #35Parameter changes

2Loss of energy

If RoHC or SCHC compression protocols are implemented in the cellular network, then header compression can be achieved, but implementation complexity increases and context learning phases are required

Engineering Contradiction:
Improveenergy consumptionVSAvoidimplementation complexity
Core Design Contradiction:
Loss of energyVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-configuring compression contexts before actual data transmission begins. The network node and IoT device establish compression contexts in advance using the SCHC mechanism, defining compression rules and parameters beforehand. This eliminates the need for complex runtime context learning phases and reduces implementation complexity while achieving effective header compression for energy savings.

Inventive Principle:
Principle #10Preliminary action

3Loss of energy

If compression context is established between application server and IoT device, then compression efficiency is maximized, but communication overhead and setup time increase

Engineering Contradiction:
Improvebandwidth consumptionVSAvoidcontext setup time
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The patent applies the intermediary principle by introducing a network node as a mediator between the application server and IoT device for context establishment. The network node receives context information from the application server and distributes it to the IoT device, or facilitates indirect context setup. This intermediary approach optimizes the balance between compression efficiency and setup time by streamlining the context establishment process without requiring direct prolonged communication between the application server and IoT device.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP3732842B1Compression context setup for data transmission for IoT devices
Publication Date: 2024.05.15 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP3732842B1 patent drawingFigure 1
  • EP3732842B1 patent drawingFigure 2
  • EP3732842B1 patent drawingFigure 3

AI summary

A method or enabling compression context setup for Internet-of-Thing, IoT, devices in a communication network is presented. The method is performed in an application server node (3) for IoT devices, and comprises sending (S300) a get context message to a gateway node (2), the get context message requesting a compression context setup comprising compression details for an IoT device (1), receiving (S310) an indication of the requested compression context setup for the IoT device from the gateway node, and compressing and decompressing (S340) messages sent to and from the IoT device based on the received indication. An IoT device, a gateway node, an application node, a computer program and a computer program product thereof are also presented.