Cloud Print Authentication via Browser Claim Code

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for authenticating user access to cloud-based printing operations often interrupt the printing process, as they require user authentication before submitting a print job, which can be challenging for applications like port monitors that interfere with the normal printing flow.

Innovation Solution

A method that generates a claim code for a print job on a cloud-based server, allowing the printing process to continue without interruption by redirecting the user to a web application for authentication, minimizing the need for a user interface in the printing application and offloading authentication to a browser.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If user authentication is required before submitting a print job to a cloud-based server, then security and user identification are improved, but the printing process is interrupted and complexity increases

Engineering Contradiction:
Improveauthentication securityVSAvoidprinting flow continuity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs authentication in advance by generating a claim code that is embedded in a URL. The user authenticates through a browser before the actual printing operation, so that when the print job is submitted to the cloud-based server, the authentication is already complete. This preliminary authentication action resolves the contradiction by ensuring security is established before the printing flow begins, eliminating interruptions during the actual printing process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces a browser as an intermediary component between the user and the cloud-based server. Instead of requiring direct authentication within the printing application, the system uses a browser-based authentication interface that the user accesses through a URL containing a claim code. This intermediary approach allows authentication to occur separately from the printing workflow, maintaining both security and workflow continuity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If a login dialog is displayed to authenticate a user, then user identification is ensured, but applications like port monitors that interfere with normal printing flow cannot easily show the login box

Engineering Contradiction:
Improveuser authenticationVSAvoidprinting application compatibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent moves the authentication interface from the traditional application window dimension to a web browser dimension. Instead of displaying a login dialog within the printing application's graphical interface, the system generates a URL that opens a browser-based authentication interface. This dimensional shift allows authentication to occur in a separate environment that doesn't interfere with the printing application's operation, particularly for systems like port monitors that have limited UI capabilities.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The browser serves as an intermediary that handles the authentication process externally. The printing application simply redirects to a browser with a claim code embedded in the URL, and the browser manages the authentication interaction with the cloud-based server. This intermediary approach resolves the compatibility issue by allowing authentication without requiring the printing application to display or manage login dialogs.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If authentication is performed within the printing application, then user permission is determined, but the application complexity increases and implementation becomes more difficult

Engineering Contradiction:
Improveaccess permission controlVSAvoidauthentication implementation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the authentication functionality from the printing application and relocates it to the cloud-based server and browser environment. The printing application's role is reduced to generating a claim code and redirecting to a browser URL. The actual authentication logic, user permission determination, and security verification are taken out and handled by the server-side components. This extraction significantly reduces application complexity while maintaining robust permission control.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The cloud-based server acts as an intermediary that handles all authentication logic and permission control. Instead of embedding complex authentication code within the printing application, the system uses server-side intermediaries (authentication endpoints, claim code validation services) that manage user verification. This approach separates concerns and reduces application complexity while ensuring reliable access control.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11321031B2Methods for authenticating printing operations from a cloud-based server
Publication Date: 2022.05.03 KYOCERA DOCUMENT SOLUTIONS INC
  • US11321031B2 patent drawing
  • US11321031B2 patent drawing
  • US11321031B2 patent drawing

AI summary

A cloud-based server and a port monitor on a device provide authentication of a user to access print jobs on the server. An application may print or perform other operations from the cloud-based server to a printing device. The port monitor uploads data for a document to the cloud-based server. Once the data for the document is uploaded, a claim code is generated by the cloud-based server. The port monitor receives the claim code. The port monitor initiates the launch of a browser having a uniform resource locator (URL) address for the server along with the claim code. The user is authenticated using a login page and the claim code associated to the user to allow access to the document on the server.