18469435. DEVICE MANAGEMENT SYSTEM simplified abstract (Kyocera Document Solutions Inc.)
Contents
- 1 DEVICE MANAGEMENT SYSTEM
- 1.1 Organization Name
- 1.2 Inventor(s)
- 1.3 DEVICE MANAGEMENT SYSTEM - A simplified explanation of the abstract
- 1.4 Simplified Explanation
- 1.5 Potential Applications
- 1.6 Problems Solved
- 1.7 Benefits
- 1.8 Potential Commercial Applications
- 1.9 Possible Prior Art
- 1.10 Unanswered Questions
- 1.11 Original Abstract Submitted
DEVICE MANAGEMENT SYSTEM
Organization Name
Kyocera Document Solutions Inc.
Inventor(s)
Hisakazu Nishiyama of Osaka (JP)
DEVICE MANAGEMENT SYSTEM - A simplified explanation of the abstract
This abstract first appeared for US patent application 18469435 titled 'DEVICE MANAGEMENT SYSTEM
Simplified Explanation
The abstract describes a device management system with a frontend and a backend, where the frontend accesses a relay backend domain to handle client requests for APIs.
- The system includes a frontend and a backend.
- The frontend has a first domain, while the backend includes a relay backend domain.
- When a client request with a URL containing the first domain is received, the frontend accesses the relay backend domain.
- The backend generates a relay Cookie with the relay backend domain for session establishment.
- The frontend sends the relay Cookie to the client via the relay system.
Potential Applications
This technology could be applied in various industries such as IT, telecommunications, and IoT for managing devices and handling client requests efficiently.
Problems Solved
1. Efficient device management and client request handling. 2. Secure session establishment between frontend and backend.
Benefits
1. Improved system performance. 2. Enhanced security measures for session establishment. 3. Streamlined device management processes.
Potential Commercial Applications
Optimizing device management systems for businesses in IT, telecommunications, and IoT industries.
Possible Prior Art
One possible prior art could be the use of cookies for session management in web applications.
Unanswered Questions
How does the system handle multiple client requests simultaneously?
The abstract does not provide details on how the system manages multiple client requests at the same time.
What security measures are in place to protect the relay Cookie during transmission?
The abstract does not mention specific security protocols or encryption methods used to safeguard the relay Cookie during transmission.
Original Abstract Submitted
A device management system includes a frontend and a backend. The frontend includes a first domain. The backend includes a domain of a relay system as a relay backend domain that is a domain of the backend. The frontend accesses the relay backend domain when an access that uses a URL including the first domain as a domain name is received from a client via the relay system, and a request for an API is thus received from the client. The backend generates a relay Cookie including the relay backend domain as a domain used for establishing the session. The frontend transmits the relay Cookie to the client via the relay system.
