IoT Negotiation Service Entity for Resource-Constrained Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
IoT devices face challenges in direct negotiation due to resource constraints, limited processing power, and lack of awareness or knowledge, making efficient negotiation between individual IoT entities inefficient or unfeasible.
Innovation Solution
A negotiation service entity is introduced to facilitate negotiations by receiving requests, determining negotiation targets, transmitting requests, and returning results, utilizing cognition capabilities and interfaces to manage and adapt negotiations on behalf of IoT entities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If direct negotiation is implemented between individual IoT entities, then negotiation capability and autonomy are improved, but device complexity and resource consumption increase beyond the capabilities of resource-constrained IoT devices
Solution Approach 1:
The patent introduces a negotiation service entity that acts as an intermediary between IoT entities seeking to negotiate. This mediator handles the complex negotiation processes, including receiving negotiation requests, determining negotiation targets, and managing the negotiation exchanges, thereby relieving resource-constrained IoT devices from the burden of direct negotiation while still enabling negotiation functionality.
2Adaptability or versatility
If each IoT entity maintains detailed negotiation information locally, then negotiation autonomy is improved, but memory and processing resources are exceeded
Solution Approach 1:
The patent extracts the negotiation information management function from individual IoT entities and centralizes it in the negotiation service entity. The negotiation service maintains the detailed negotiation information, negotiation targets, and negotiation state, while IoT entities only need to send simple requests and receive results, dramatically reducing their memory and processing requirements.
3Productivity
If IoT entities negotiate directly with each other, then communication efficiency is improved, but reliability decreases due to lack of awareness and knowledge among entities
Solution Approach 1:
The negotiation service entity serves as a knowledgeable intermediary that has awareness of multiple IoT entities and their capabilities. It determines appropriate negotiation targets based on this knowledge and manages the negotiation process to ensure successful outcomes, thereby improving reliability while maintaining communication efficiency through automated mediation.
4Adaptability or versatility
If resource-constrained IoT devices perform negotiation operations, then negotiation functionality is achieved, but energy consumption exceeds battery capacity
Solution Approach 1:
The patent uses the negotiation service entity as a mediator that performs the computationally intensive negotiation operations. Resource-constrained IoT devices only need to communicate simple requests and receive results from the mediator, dramatically reducing their energy consumption while still achieving full negotiation functionality.
5Productivity
If a negotiation service entity is introduced to facilitate negotiations, then negotiation efficiency and reliability are improved, but system complexity increases
Solution Approach 1:
The negotiation service entity is designed as a universal component that can serve multiple IoT entities and handle various types of negotiation requests. By consolidating negotiation functionality in a single multi-functional service rather than implementing negotiation capabilities in each individual device, the system achieves improved efficiency while managing complexity through centralization.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Disclosed herein are devices, methods, and systems for providing negotiation between IoT Things, IoT entities, and/or IoT applications as a service. IoT entities may be admitted to a negotiation service that may locate a target service and request service from the target service on behalf of the requesting IoT entity. A variety of services and related parameter may be negotiated, such as a work schedule for a set of devices performing a similar function in a similar space, price of service, and duration of service.