Stateless Network Service Device State Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The strain on processing resources and communication bandwidth in network services caused by multiple devices relying on them for state data management degrades user experience by delaying function provision.

Innovation Solution

Devices are configured to provide only necessary state information within a URL reference, allowing network services to operate statelessly and efficiently manage device states across a fleet of devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If network services obtain and maintain device state data from multiple devices, then device functions can be provided, but processing resources are strained and communication bandwidth is consumed

Engineering Contradiction:
Improvedevice function provisionVSAvoidprocessing resources
Core Design Contradiction:
Adaptability or versatilityVSPower

Solution Approach 1:

The patent extracts only the necessary state information from devices and incorporates it directly into URL references. This allows the network service to obtain minimal required state data without maintaining comprehensive device state management, thereby reducing processing resource strain while still enabling device function provision.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Devices are configured to provide state information proactively within URL references without requiring continuous network service intervention. This self-service approach reduces the burden on network services to actively query and maintain device states, optimizing processing resource usage.

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If network services obtain and maintain device state data from multiple devices, then device functions can be provided, but communication bandwidth is consumed

Engineering Contradiction:
Improvedevice function provisionVSAvoidcommunication bandwidth
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent extracts only essential state information and embeds it directly into URL references rather than maintaining separate communication channels for state data exchange. This reduces the quantity of communication bandwidth required while still providing necessary device state information for function provision.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

URL references serve multiple functions: they identify devices, convey state information, and enable function invocation simultaneously. This multi-functionality eliminates the need for separate communication protocols for state data exchange, optimizing communication bandwidth usage.

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

3Loss of information

If network services actively manage device states, then comprehensive device information is available, but user experience is degraded by delays

Engineering Contradiction:
Improvedevice state informationVSAvoidfunction provision time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

Devices incorporate state information into URL references in advance before function invocation is needed. This preliminary action ensures that when a function is requested, the necessary state data is already available in the URL, eliminating delays associated with active state queries and management by network services.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8705052B2Communicating state data to a network service
Publication Date: 2014.04.22 HEWLETT PACKARD DEVELOPMENT COMPANY LP
  • US8705052B2 patent drawing
  • US8705052B2 patent drawing
  • US8705052B2 patent drawing

AI summary

An apparatus includes an interface builder, template engine, and an assembler. The template engine is operable to identify a reference template associated with an object selected from a first user interface. The assembler is operable to assemble a request from the identified reference template and state data corresponding to the reference template. The builder is operable to process a user interface description retrieved using the request to cause the display of a second user interface.