Network Service Access via Token-Based Device Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network services often require user interaction on devices that lack interactive capabilities, limiting their ability to access and utilize services, and typically require proprietary client applications for rights management, which can be cumbersome and inefficient.

Innovation Solution

A system and method that allows multiple devices to cooperate in accessing network services, where a user interface device handles user interactions and communicates tokens and identifiers to a playback device, enabling it to access network services without direct user interaction and using an intermediary rights management service to manage access and usage across various services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If network services require user interaction on devices, then service accessibility is improved, but device functionality is limited to those with interactive capabilities

Engineering Contradiction:
Improveservice accessibilityVSAvoiduser interaction requirement
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system divides the network service access function into two separate devices: a first device that handles user interface operations (authentication, service selection) and a second device that handles content retrieval and playback. This segmentation allows non-interactive devices to access network services by delegating interaction tasks to another device in the same network session.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The first device acts as an intermediary between the user and the network service, performing user interface operations on behalf of the second device. The system uses tokens and identifiers as intermediaries to transfer authentication credentials and service access rights between devices, enabling the second device to access services without direct user interaction.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If proprietary client applications are used for rights management, then service security is improved, but system complexity and ease of use deteriorate

Engineering Contradiction:
Improveservice securityVSAvoidproprietary application requirement
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements a universal rights management mechanism using tokens and identifiers that work across multiple network services and device types. Instead of requiring separate proprietary client applications for each service, the same token-based authentication and rights management approach can be used universally, reducing device complexity while maintaining security.

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

Solution Approach 2:

The system replaces the mechanical approach of installing proprietary client applications with a lighter-weight token-based authentication mechanism. The rights management functionality is substituted from application-level implementation to a simpler token verification process that can be implemented in any device, reducing complexity while maintaining service security.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Adaptability or versatility

If multiple devices access network services independently, then device autonomy is improved, but service coordination and rights management worsen

Engineering Contradiction:
Improvedevice autonomyVSAvoidrights management coordination
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system establishes feedback loops between devices in the network session, where the first device monitors and reports on user interface operations, and the second device reports on content access and playback status. This feedback mechanism enables coordinated rights management while preserving device autonomy, as each device operates independently but maintains synchronization through structured communication protocols.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP2926526B1System and method for use of network services in receiving content and data
Publication Date: 2021.05.26 QUALCOMM ATHEROS INC
  • EP2926526B1 patent drawingFigure 1
  • EP2926526B1 patent drawingFigure 2
  • EP2926526B1 patent drawingFigure 3A~3B

AI summary

A first device implements an application platform that is shared with a second device. The application platform can be implemented so that the first device and the second device operate to have a same identity to at least the network service. The first device provides a user interface in order to receive input for accessing or using the network service. Additionally, the first device communicates input received in response to providing the user interface to the network service. The first device can receive a token from the network service in response to communicating the input. Additionally, the first device can communicate a set of data items to the second device. The set of data items includes the token and one or more identifiers that enable the second device to access and use the network service while appearing as the first device to the network service.