User Terminal Emulation Server for Distributed I/O Device Coordination
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The challenge lies in providing advanced communication services within a portable handheld form factor, where traditional user terminals are costly and power-intensive, and users require constant connectivity, necessitating a solution that adapts to available input and output devices without the need for a feature-rich terminal.
Innovation Solution
A centralized user terminal emulation server identifies and combines proximately located input and output devices to provide a unified interface for communication services, allowing users to receive and initiate communications using a networked set of devices, reducing the need for a traditional user terminal.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional user terminals are used to provide advanced communication services, then communication functionality is improved, but device complexity and power consumption increase
Solution Approach 1:
The patent segments the user terminal functionality across multiple distributed I/O devices (smartphones, tablets, wearables, etc.) rather than requiring a single integrated terminal. The server emulates terminal functions by dynamically selecting and coordinating appropriate I/O devices based on user location and availability, thereby providing advanced communication services without requiring complex terminal hardware.
Solution Approach 2:
The server acts as an intermediary between communication network entities and user I/O devices. It emulates terminal behavior by receiving communication requests, determining appropriate I/O devices based on user location and capabilities, and routing signals to the correct devices. This mediator approach eliminates the need for complex terminal structures while maintaining full communication functionality.
2Adaptability or versatility
If feature-rich user terminals are integrated with more capabilities, then communication services are improved, but power consumption increases
Solution Approach 1:
Instead of requiring I/O devices to maintain full terminal capabilities continuously, the system activates only the necessary capabilities and devices needed for each specific communication service. The server determines which I/O devices and capabilities are required based on the communication request and user context, thereby reducing overall power consumption while providing comprehensive communication services when needed.
3Reliability
If users need to maintain constant connectivity, then communication availability is improved, but user convenience deteriorates
Solution Approach 1:
The server automatically manages terminal emulation by detecting user location, identifying available I/O devices, and routing communication signals without requiring user intervention. The system self-adjusts based on user movement and availability, maintaining communication reliability while eliminating the burden of manual terminal management and keeping users informed of their availability status.
4Device complexity
If a centralized server approach is used to emulate user terminal, then device complexity is reduced, but network dependency increases
Solution Approach 1:
The server performs preliminary determination of user location and available I/O devices before establishing communication services. By pre-identifying appropriate devices and capabilities based on user context and location data, the system reduces the need for complex real-time decisions during communication, thereby minimizing network dependency while maintaining simple device architecture.
Data Source
AI summary
A user terminal emulation server maintains a database identifying network addresses, UI capabilities, and communication protocols of I/O user devices. Communication sessions are established between a user terminal emulation application and a network entity and I/O user devices proximately located to a user and provide a combined I/O user interface. Delay profiles are determined between the application and the I/O user devices. A downlink flow from the network entity is split into a plurality of downlink flow components assigned to the I/O user devices. For each of the downlink flow components, the server formats the component for transmission to the assigned I/O user device, initiates transmission of the formatted downlink flow component to the assigned I/O user device, and controls timing for when the formatted downlink flow component is transmitted to the assigned I/O user device based on the delay profile associated with the assigned I/O user device.


