Nested Request-Response Protocol for Device Capability Coordination

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing communication protocols, such as REST and HTTP, are inadequate for transactional tasks involved in coordinating capabilities between networked computing devices, leading to operational delays and inefficiencies.

Innovation Solution

The proposed solution involves adapting existing request-response protocols by nesting request-response communications to introduce stateful transactions, ensuring compatible operations between networked devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If individual instances of request-response protocol are used for communication, then web-based and network-based applications can operate, but coordination of capabilities between devices becomes inefficient and delayed

Engineering Contradiction:
Improvecoordination efficiencyVSAvoidoperational delay
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements nested request-response instances where a parent request-response pair encapsulates one or more child request-response pairs. This nesting structure allows multiple capability coordination tasks to be executed within a single communication transaction, eliminating the need for sequential individual exchanges and significantly improving coordination efficiency while reducing operational delays.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Adaptability or versatility

If existing request-response protocols are used, then widespread compatibility is maintained, but stateful transactions for capability coordination cannot be properly supported

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidcapability coordination
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces dynamic state management within nested request-response instances, where parent and child instances can transition between different states (pending, in-progress, completed, failed). This dynamic state tracking enables reliable capability coordination while maintaining compatibility with existing request-response protocols, as the state information is carried within the protocol messages themselves rather than requiring external state storage.

Inventive Principle:
Principle #15Dynamics

3Ease of operation

If asynchronicity is used in request-response communications, then device independence is achieved, but determination of aligned capability states becomes difficult

Engineering Contradiction:
Improvedevice independenceVSAvoidcapability state alignment
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent implements feedback mechanisms where each nested request-response instance carries state information and capability data that allows devices to determine alignment. The parent instance coordinates capability states by receiving feedback from child instances, and the nested structure preserves asynchronicity while enabling reliable state determination through structured information exchange and acknowledgment messages.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250193271A1Nested Request-Response Protocol Network Communications
Publication Date: 2025.06.12 SERVICENOW INC
  • US20250193271A1 patent drawing
  • US20250193271A1 patent drawing
  • US20250193271A1 patent drawing

AI summary

A controller computing device may include one or more processors and memory containing controller data representing controller computing device capabilities. The one or more processors may be configured to transmit on a first instance of a request-response protocol, a controller request, including the controller data, to an agent computing device. The controller computing device may then receive, from the agent computing device, an agent request on a second instance of the request-response protocol. The agent request may include agent data representing agent computing device capabilities. The controller computing device may store the agent data in the memory, and transmit on the second instance of the request-response protocol, to the agent computing device, a controller response acknowledging receipt of the agent request. The controller computing device may then receive on the first instance of the request-response protocol from the agent computing device, an agent response acknowledging receipt of the controller request.