Client Apparatus Request Control for Shared Device Network Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems allow multiple ordering and user registration requests for shared devices, leading to resource wastage and inefficient network traffic due to lack of status information sharing between client apparatuses and servers.

Innovation Solution

A client apparatus and network system that acquires status information from devices, determines if requests are already made, and controls requests to prevent duplicates, using a status-information acquiring portion, requesting portion, determining portion, and instructing portion to manage requests and registrations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If multiple client apparatuses are allowed to independently request services for a shared device, then service availability and ease of operation are improved, but multiple duplicate orders and registrations occur, wasting network traffic and server resources

Engineering Contradiction:
Improveservice request capabilityVSAvoidnetwork traffic waste
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The system performs preliminary actions by having the device itself register with the server before client apparatuses make service requests. The device stores registration status information and provides it to client apparatuses, so that duplicate registrations are prevented before they occur. This preliminary registration action resolves the contradiction by enabling multiple clients to access services without causing duplicate server registrations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The device acts as an intermediary between multiple client apparatuses and the server. It maintains request status information locally and shares this information with all connected client apparatuses, mediating their access to the server. This intermediary role allows multiple clients to operate independently while preventing duplicate requests, thus improving ease of operation without wasting network resources.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If each client apparatus independently manages service requests, then operational independence is improved, but resource efficiency deteriorates due to duplicate requests to the server

Engineering Contradiction:
Improveclient independenceVSAvoidserver processing efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system merges the request management function into the device itself. The device maintains a centralized request status information that reflects the state of all service requests, combining the independence of multiple clients with centralized coordination. This merging allows each client to operate independently while the device ensures efficient server communication by preventing duplicate requests.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The device provides feedback to client apparatuses about the current request status by sharing stored status information. When a client makes a service request, the device checks its stored status information, determines whether the request has already been made, and communicates this feedback to the client. This feedback mechanism maintains client independence while improving server processing efficiency by eliminating duplicate requests.

Inventive Principle:
Principle #23Feedback

3Reliability

If status information is shared among client apparatuses through the device, then duplicate requests are prevented, but system complexity increases due to additional information management components

Engineering Contradiction:
Improverequest uniquenessVSAvoidinformation management structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The device performs self-service by automatically maintaining and managing its own request status information. It stores registration status, consumable order status, and other request states locally, and automatically provides this information to client apparatuses without requiring external management systems. This self-service approach improves request uniqueness while minimizing the increase in system complexity.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The device performs multiple functions: it serves as the shared peripheral, maintains request status information, provides this information to multiple clients, and coordinates service requests. By making the device universal and multi-functional, the system achieves reliable request management without adding separate complex information management infrastructure, thus improving reliability while limiting complexity increase.

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

Data Source

PatentUS9292802B2Client apparatus configured to communicate with device and server via network
Publication Date: 2016.03.22 BROTHER KOGYO KK
  • US9292802B2 patent drawing
  • US9292802B2 patent drawing
  • US9292802B2 patent drawing

AI summary

A client apparatus is configured to communicate with a device and with a server via network. A status-information acquiring portion acquires, from the device, status information indicative of status of the device. A requesting portion makes a predetermined request to the server based on the status information. A request-status-information acquiring portion acquires, from the device, request status information indicative of a request status of the predetermined request. A determining portion determines whether the predetermined request is already made to the server, based on the request status information acquired by the request-status-information acquiring portion. A request controlling portion determines that the predetermined request should be made to the server, if the determining portion determines that the predetermined request is not yet made. An instructing portion instructs the device to set the request status information to a requested state, if the request controlling portion determines that the predetermined request should be made.