Dynamic Parameter Negotiation via HTTP and UDP

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for communicating parameter data between machine components lack flexibility and adaptability, requiring a statically defined set of parameters and lacking backwards compatibility for new or upgraded components.

Innovation Solution

A system and method for dynamically negotiating groups of parameters using HTTP for initial requests and UDP for periodic updates, allowing clients to specify desired session timeouts and update periods, enabling flexible and backward-compatible communication of machine operational parameters.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a statically defined set of parameters is used for communication, then system complexity is reduced and ease of operation is improved, but adaptability and flexibility are worsened

Engineering Contradiction:
Improveease of operationVSAvoidadaptability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic parameter negotiation where the set of communicated parameters is not fixed but can be negotiated and adjusted between producer and consumer based on actual needs. This allows the system to adapt to different operational requirements while maintaining a structured communication framework through the use of negotiation sessions and capability exchanges.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If new or upgraded components are introduced, then adaptability is improved, but backwards compatibility is worsened when data sources lack capability to provide requested parameters

Engineering Contradiction:
ImproveadaptabilityVSAvoidbackwards compatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a capability negotiation mechanism where producers and consumers exchange information about their supported parameters and capabilities before actual data communication begins. This feedback loop allows new components to declare their capabilities, enabling the system to match consumers with compatible producers and maintain backwards compatibility through informed parameter selection.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The negotiation framework provides a universal interface that can accommodate different types of producers and consumers with varying capabilities. By establishing a standard negotiation protocol that works across different component types, the system achieves multi-functionality and backwards compatibility, allowing old and new components to coexist and communicate effectively.

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

3Adaptability or versatility

If dynamic parameter negotiation is implemented, then adaptability and flexibility are improved, but device complexity and communication overhead are worsened

Engineering Contradiction:
ImproveadaptabilityVSAvoiddevice complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent performs parameter negotiation and capability exchange in advance before actual data communication begins. By resolving which parameters will be communicated during an initial negotiation phase, the system eliminates the need for complex runtime decision-making and parameter matching, thereby reducing operational complexity while maintaining adaptability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10334052B2System and method for communicating negotiated groups of parameters
Publication Date: 2019.06.25 CATERPILLAR INC
  • US10334052B2 patent drawing
  • US10334052B2 patent drawing
  • US10334052B2 patent drawing

AI summary

A computer-implemented method for negotiating the communication of groups of parameters between a server and a client includes sending a first request for a parameter negotiating session from the client to the server using HTTP, specifying the client's desired session timeout for the session in the first request, receiving at the client an XML-formatted message sent from the server via HTTP specifying whether the server is able to support the requested session, and sending from the client a second request with an XML-formatted message via HTTP for a group of parameters desired from the server, wherein the second message includes the client's desired destination address, the client's desired update period for receiving updated parameter data, identification of a UDP port of the client for receipt of updated parameter data from the server in a UDP datagram, and identifiers of parameters desired by the client.