RTP Sensor Measurement Streaming for Lower IoT Overhead

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing IoT protocols like CoAP and HTTP/2/3 face high overhead levels when handling high-frequency sensor data, and multimedia infrastructures often lack suitable transport mechanisms for such data.

Innovation Solution

Utilizing the Real-time Transport Protocol (RTP) to transmit sensor measurements, specifically through IoT devices, including constrained devices, by encoding sensor data using SenML and mapping relevant information to RTP packet headers or payloads, reducing overhead by streaming sensor data efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If RESTful protocols (CoAP, HTTP) are used to transmit sensor measurements, then scalability for client-server interactions is improved, but overhead levels increase for high-frequency data

Engineering Contradiction:
ImprovescalabilityVSAvoidoverhead
Core Design Contradiction:
Adaptability or versatilityVSLoss of substance

Solution Approach 1:

The patent segments the data transmission by separating sensor measurements into individual RTP packets with structured encoding. Each packet contains only the necessary data elements (sensor ID, measurement value, timestamp, unit) rather than complete RESTful protocol messages, reducing overhead while maintaining scalability through standardized packet formats

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the transmission parameter from RESTful protocol messages to RTP protocol packets with SenML encoding. This parameter change reduces message overhead by eliminating redundant HTTP/CoAP headers and using compact binary or text-based SenML formats optimized for sensor data, while RTP provides efficient streaming capabilities for high-frequency data

Inventive Principle:
Principle #35Parameter changes

2Loss of substance

If RTP protocol is used to transmit sensor measurements, then overhead is reduced for high-frequency data, but compatibility with existing IoT infrastructure may worsen

Engineering Contradiction:
ImproveoverheadVSAvoidcompatibility
Core Design Contradiction:
Loss of substanceVSAdaptability or versatility

Solution Approach 1:

The patent introduces SenML (Sensor Measurement Links) as an intermediary data format that bridges RTP protocol and existing IoT infrastructure. SenML provides a standardized encoding format for sensor measurements that can be easily translated to and from various IoT protocols, maintaining compatibility while enabling efficient RTP-based transmission with reduced overhead

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent makes the RTP-based sensor transmission system universal by adopting SenML as the data encoding format, which is designed to work with multiple transport protocols including RTP, UDP, and TCP. This allows the same sensor data format to be used across different IoT infrastructures, maintaining compatibility while leveraging RTP's efficient streaming capabilities

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

Data Source

PatentUS20250294075A1Devices and methods for provision of resource representations
Publication Date: 2025.09.18 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US20250294075A1 patent drawing
  • US20250294075A1 patent drawing
  • US20250294075A1 patent drawing

AI summary

A sending node is disclosed that is operable to provide a representation of at least one resource, wherein the resource comprises a sensor measurement, and wherein the representation is operable for transmission using an Internet of Things (IoT) transfer Protocol. The sending node comprises processing circuitry configured to generate a representation of the resource according to a data model, generate a Real-time Transport Protocol (RTP) data packet, wherein the RTP data packet comprises the generated representation of the resource, and send the generated RTP packet to a receiving node. Also disclosed are a receiving node and an intermediate node.