Cloud-Connected Controller Architecture for Low-Latency Remote Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud-based gaming experiences significant latency issues due to the compounded delays in signal processing and transmission between the user's device and the cloud gaming service, which can exceed the preferred sub-20 millisecond response time for controller inputs.

Innovation Solution

A system and method for remotely controlling cloud-based client applications by emulating the client application on a cloud-based platform, streaming video and audio to the user's device, and allowing real-time interaction through a cloud-connected controller, separate from the user's device, to reduce signal latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If cloud-based client application is used, then hardware requirements are separated from application performance, but connection latency increases

Engineering Contradiction:
Improvehardware requirements separationVSAvoidconnection latency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

A cloud-connected controller serves as an intermediary device between the user and the cloud-based application. The controller connects directly to the cloud service via Wi-Fi, bypassing the client device's network connection. This intermediary architecture allows user inputs to be transmitted directly to the cloud application without traveling through the client device's network stack, thereby reducing latency while maintaining the cloud-based architecture's hardware independence.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If traditional cloud gaming setup is used, then platform restrictions are relieved, but controller latency compounds

Engineering Contradiction:
Improveplatform restriction reliefVSAvoidcontroller latency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system segments the control signal path from the display path. The controller connects directly to the cloud service for input transmission, while the client device handles only video streaming and display. This segmentation allows the control path to be optimized independently from the display path, enabling platform-agnostic cloud access while achieving low-latency controller response through the direct Wi-Fi connection between controller and cloud service.

Inventive Principle:
Principle #1Segmentation

3Ease of operation

If controller connects to client device in cloud gaming, then user can interact with application, but signal latency increases

Engineering Contradiction:
Improveuser interaction capabilityVSAvoidsignal latency
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The cloud service acts as an intermediary that receives controller inputs directly via Wi-Fi connection, bypassing the client device's processing chain. The controller establishes a direct communication channel with the cloud application, allowing user interactions to be registered immediately without the additional latency of routing signals through the client device's operating system and network stack.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12489816B2System and method for remotely controlling cloud-based client applications
Publication Date: 2025.12.02 SKILLZ PLATFORM INC
  • US12489816B2 patent drawing
  • US12489816B2 patent drawing
  • US12489816B2 patent drawing

AI summary

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for remotely controlling cloud-based client applications. The method can include: receiving a first request from a client device of a first user to initiate an interactive session with a cloud-based client application and a second request from a cloud-connected client application controller of the first user to connect to the interactive session, wherein the cloud-based client application is configured to execute on a computing platform different from the client device and the cloud-connected application controller, and wherein the cloud-connected application controller is separate from and in communication with the client device; reserving, in response to the first request, an application engine from a pre-instantiated application engine pool of a plurality of pre-instantiated application engine pools within which the cloud-based client application executes remotely from the client device and the cloud-connected application controller; connecting, in response to the second request, to the cloud-connected client application controller separately from the client device; receiving interaction data as the first user engages with first media data associated with the cloud-based client application via the cloud-connected client application controller as the first media data is displayed to the first user via a display application executing on the client device; modifying the cloud-based client application executing within the application engine based on the received interaction data; and providing second media data associated with the modified cloud-based client application to the first user via the display application executing on the client device for interaction via the cloud-connected application controller.