CoAP Media Access for IoT Streaming in 3D Scene Description
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing 3D modeling formats like glTF do not support media types such as video and audio, limiting their use in immersive media environments like virtual reality, augmented reality, and extended reality, and lack compatibility with constrained IoT devices using CoAP.
Innovation Solution
Extensions to glTF are developed to support video and audio syntax, incorporating MPEG extensions for immersive media, and integration of CoAP for media delivery and rendering, enabling compatibility with IoT devices through a HTTP-CoAP proxy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If HTTP-based protocols (REST, SOAP) are used for IoT communication, then interoperability and ease of implementation are improved, but energy consumption and processing overhead increase significantly for resource-constrained devices
Solution Approach 1:
The patent applies COAP, a lightweight protocol designed for resource-constrained IoT devices, replacing heavyweight HTTP protocols. COAP uses simpler message formats and operates over UDP rather than TCP, significantly reducing processing overhead and energy consumption while maintaining interoperability through standard RESTful principles.
Solution Approach 2:
The patent changes the communication protocol parameters from HTTP-based (REST/SOAP) to COAP-based, altering the fundamental transmission mechanism to better suit IoT constraints. This includes using observe options for state monitoring, block2 options for efficient data transfer, and format options for structured responses, all optimized for low-power operation.
2Adaptability or versatility
If HTTP protocols are used for streaming data transmission, then compatibility with web technologies is improved, but latency and real-time performance deteriorate
Solution Approach 1:
The patent employs COAP's lightweight stateless architecture replacing HTTP's connection-oriented model. COAP messages are independent and can be processed immediately without connection maintenance overhead, enabling real-time streaming with minimal latency while still supporting web-compatible data formats through the observe option mechanism.
Solution Approach 2:
The patent implements periodic data streaming using COAP observe options, where the server automatically sends periodic updates to clients without requiring continuous HTTP connections. This enables real-time monitoring and streaming applications with reduced latency compared to traditional HTTP polling or long-polling mechanisms.
3Ease of manufacture
If traditional HTTP streaming methods are used, then ease of implementation is improved, but scalability to large numbers of devices deteriorates
Solution Approach 1:
The patent implements a universal COAP-based streaming framework that handles multiple functions (data streaming, state monitoring, event notification) through a single protocol mechanism. The observe option provides multi-functional capability for both periodic updates and event-driven notifications, enabling scalable deployment across large numbers of IoT devices while maintaining implementation simplicity through standardized RESTful patterns.
Solution Approach 2:
The patent segments the streaming architecture into independent COAP message exchanges rather than maintaining persistent HTTP connections for each device. This segmentation allows the server to handle numerous concurrent device connections efficiently, with each COAP interaction being stateless and independently processable, thereby improving scalability to large device populations.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
Aspects of the disclosure provide methods and apparatus for accessing a Constrained Application Protocol (CoAP) server in a media scene description system. A CoAP request can be sent, by a media access function (MAF) of processing circuitry implementing the media scene description system using an application programming interface (API), to the CoAP server to request a media resource. The MAF can be configured as a CoAP client or a Hypertext Transfer Protocol (HTTP)-CoAP proxy. A CoAP response can be received, by the MAF using the API, from the CoAP server. In an example, the CoAP response includes the requested media resource. In an embodiment, the MAF is compatible with both the CoAP request according to a CoAP communication protocol and a proxy request according to an HTTP communication protocol.