Communication Endpoint Session Management for IPP over USB
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In communication apparatuses with multiple interface descriptors compliant with IPP over USB, maintaining HTTP sessions across different endpoints is challenging, leading to inconsistency in service control and session management, as existing solutions do not effectively address the determination of whether multiple HTTP communications are part of the same session.
Innovation Solution
A communication apparatus with a server unit and application that identifies communication endpoints and determines if requests are received through the same endpoints, processing requests as part of the same session if they are, even if received through different endpoints, using a first and second communication line with a determination unit and identification unit.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If HTTP session management is implemented in a communication apparatus with multiple interface descriptors compliant with IPP over USB, then service consistency and session management are improved, but determining whether multiple HTTP communications are in the same session becomes complex and difficult
Solution Approach 1:
The patent introduces an intermediary mechanism that maps multiple USB endpoints to a unified session identification system. The server unit acts as a mediator that receives HTTP requests from different endpoints, determines their session affiliation through coordinate information, and manages them consistently. This intermediary layer resolves the complexity of direct endpoint-to-session mapping while ensuring service consistency across multiple interfaces.
Solution Approach 2:
The patent implements a universal session management system that handles HTTP requests from multiple different USB endpoints through a single unified session determination mechanism. The server unit is designed to process requests from any endpoint using the same coordinate-based identification approach, making the session management system multi-functional and endpoint-agnostic, thereby improving reliability without proportionally increasing complexity.
2Adaptability or versatility
If multiple logical interfaces are used to receive HTTP requests, then communication versatility is improved, but determining whether requests from different endpoints belong to the same session becomes difficult
Solution Approach 1:
The patent implements a feedback mechanism where the server unit receives HTTP requests from multiple logical interfaces, determines session affiliation based on coordinate information from the identification unit, and uses this determination to consistently manage session state. The system feeds back session identification results to control subsequent request handling, ensuring that requests from different endpoints but same session are properly associated. This feedback loop resolves the difficulty of session detection while maintaining communication versatility.
Solution Approach 2:
The patent adds another dimension to session identification by introducing coordinate information that maps endpoints across multiple logical interfaces to unified session identifiers. Instead of relying solely on endpoint-specific identifiers, the system uses a multi-dimensional coordinate system that can represent relationships between endpoints from different interfaces, thereby enabling session detection across diverse communication paths without compromising versatility.
Data Source
AI summary
An application of a communication apparatus includes an identification unit configured to identify a communication line through which a first request and a second request are received, and a determination unit configured to identify communication endpoints having received the first request and the second request, and determine whether the communication endpoints are same, wherein, in a case where the determination unit determines that the communication endpoints having received the first request and the second request are not same communication endpoints and the identification unit determines that a communication line having received the first request and the second request is the first communication line, the first request and the second request are processed as a series of requests in a same session.