Device Action Service Unifying Multi-Device Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users face inconsistencies and inefficiencies when managing multiple devices, as they often require interacting with each device separately and using different user interfaces to perform similar actions, leading to a frustrating and inefficient experience.

Innovation Solution

A device action service is introduced to identify and unify actions across various devices, providing a centralized platform where users can access and perform actions on multiple devices through a standardized interface, regardless of the device type, by communicating with manufacturers to determine supported actions and presenting them in a unified manner.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If users interact with each device individually to perform actions, then device-specific functionality is maintained, but user time and operational complexity increase significantly

Engineering Contradiction:
Improveease of device managementVSAvoidtime to perform actions
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system segments device management into two layers: a centralized service layer that handles action orchestration and device discovery, and individual device layers that execute specific actions. This allows users to manage multiple devices through a single interface while maintaining device-specific functionality through the segmented architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The device action service acts as an intermediary between users and multiple devices. It receives action requests, discovers relevant devices, determines compatibility, and orchestrates the execution of actions across devices, eliminating the need for users to directly interact with each device individually.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If different user interfaces are used for each device, then device-specific capabilities are preserved, but user experience consistency deteriorates

Engineering Contradiction:
Improvedevice capability supportVSAvoidinterface consistency
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The device action service provides a universal interface that can manage multiple types of devices with different capabilities. It determines which devices are compatible with requested actions and orchestrates execution across diverse device types, maintaining interface consistency while supporting device-specific functionality through the service layer.

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

3Productivity

If actions are performed on each device separately, then device autonomy is maintained, but operational efficiency decreases

Engineering Contradiction:
Improveaction execution efficiencyVSAvoidsystem coordination complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system merges the coordination of multiple device actions into a single centralized service. The device action service consolidates device discovery, compatibility checking, and action orchestration, allowing efficient execution of actions across multiple devices while managing coordination complexity centrally rather than requiring complex user-side coordination.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9037757B2Device action service
Publication Date: 2015.05.19 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9037757B2 patent drawing
  • US9037757B2 patent drawing
  • US9037757B2 patent drawing

AI summary

A user may operate many devices, each of which may provide a set of actions, such as installing firmware or software or viewing the contents of the device. However, in order to perform these actions, the user may have to interact with each device using a different user interface, resulting in an inconsistent user experience. Instead, a device action service may allow a user to identify his or her devices, may identify the actions available for each device (e.g., by interacting with a device source of each device, such as a manufacturer); and upon the request of the user, may present a list of the user's devices and the actions available for each device. The actions may comprise hyperlinks to various portions of the website of the device source (e.g., a driver page and a service registration page), or controls invoking the requested action upon the device.