Intermediation Server API Management for MFP Print Services

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems face challenges in allowing a multifunctional peripheral device (MFP) to receive services from multiple service providers without storing numerous APIs, especially when the service providers change specifications, and in executing print commands for web page data without authentication information.

Innovation Solution

A communication system that includes an MFP, an intermediation server, and service providing servers, where the MFP uses Near Field Communication (NFC) to send location information of web page data to the intermediation server, which then communicates with service providers using APIs stored on the server, allowing the MFP to execute print commands without storing these APIs and without authentication information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the MFP stores multiple APIs to receive services from multiple service providers, then the MFP can receive services from different providers, but the device complexity increases and maintenance becomes difficult when service providers change specifications

Engineering Contradiction:
Improveability to receive services from multiple providersVSAvoidnumber of APIs stored in MFP
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediation server as a mediator between the MFP and multiple service providing servers. The intermediation server stores APIs for different service providers and manages authentication information, while the MFP only needs to communicate with the intermediation server through a standard interface. This resolves the contradiction by enabling multi-provider service reception without increasing MFP complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts the API storage and management function from the MFP and relocates it to the intermediation server. The MFP is relieved of the burden of storing and managing multiple service provider APIs, while the intermediation server assumes this responsibility. This extraction resolves the contradiction by maintaining service versatility while reducing MFP complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

2Ease of operation

If the MFP executes print commands without authentication information, then the operation becomes simpler and faster, but the reliability and security of service execution decreases

Engineering Contradiction:
Improvesimplicity of print command executionVSAvoidauthentication security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements preliminary authentication where the terminal device authenticates with the service providing server before obtaining location information, and the intermediation server authenticates with the service providing server before executing print commands. This preliminary authentication ensures reliability and security while allowing the MFP to execute print commands without handling authentication information, thus maintaining ease of operation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The intermediation server acts as an intermediary that handles authentication with service providing servers on behalf of the MFP. The MFP sends print commands without authentication information, while the intermediation server manages the authentication process with service providers, thus resolving the contradiction between operational simplicity and authentication security.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If the MFP stores numerous APIs for different service providers, then services from multiple providers can be received, but the loss of time for maintenance and updates increases

Engineering Contradiction:
Improvenumber of service providers supportedVSAvoidtime for API maintenance and updates
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The intermediation server serves as an intermediary that centralizes API storage and management for multiple service providers. When service providers change specifications, only the intermediation server needs to update its stored APIs, not the MFP. This resolves the contradiction by enabling support for multiple service providers while minimizing maintenance time.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts the time-consuming API maintenance task from the MFP and relocates it to the intermediation server. The MFP maintains a simple, stable interface while the intermediation server handles all API updates and maintenance for different service providers, thus resolving the contradiction between service versatility and maintenance time.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS9231934B2Control server, data processing device, and control device for data processing device
Publication Date: 2016.01.05 BROTHER KOGYO KK
  • US9231934B2 patent drawing
  • US9231934B2 patent drawing
  • US9231934B2 patent drawing

AI summary

A control server may receive first location information indicating a location of specific web page data via a data processing device, in a case where a terminal device comprising a web browser receives the specific web page data from a specific service providing server by using a first type of wireless communication and sends the first location information to the data processing device by using a second type of wireless communication. The control server may cause a display unit of the data processing device to display at least N items of account information among M items of account information currently stored in the data processing device, in a case where the first location information is received. Each of the N items of account information may be available for receiving a data providing service from the specific service providing server.