Packet Filter Translates RPC Protocols for Cross-Platform Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Client-server computing systems face challenges in interfacing between clients and servers due to proprietary protocols, particularly Microsoft's Remote Procedure Call (RPC), which restricts compatibility with non-Microsoft operating systems, limiting access to Microsoft services like Terminal Services Gateway (TSGW) without an RPC software stack.
Innovation Solution
A client-side solution that uses a specialized packet filter to 'hard code' input and output packets, allowing non-Microsoft clients to interface with Microsoft servers by translating between universal communication protocols like Secure Shell and proprietary RPC protocols, effectively bridging RPC requirements without an RPC software stack.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If proprietary RPC protocols are used for server communication, then service functionality is improved, but system compatibility deteriorates
Solution Approach 1:
The patent introduces a packet filter as an intermediary component that sits between non-Microsoft clients and Microsoft servers. This packet filter translates between universal protocols (like SSH) and proprietary RPC protocols, enabling compatibility without requiring clients to install Microsoft-specific software stacks. The intermediary handles protocol translation, allowing heterogeneous systems to communicate while preserving server functionality.
Solution Approach 2:
The patent replaces the traditional mechanical approach of installing RPC software stacks on client systems with a network-layer packet filtering and translation mechanism. Instead of modifying client operating systems to understand proprietary protocols, the solution substitutes a network intermediary that translates packets between different protocols, eliminating the need for client-side protocol installation while maintaining service access.
2Adaptability or versatility
If RPC software stack is installed on client, then access to Microsoft services is improved, but device complexity deteriorates
Solution Approach 1:
The packet filter acts as a mediator that eliminates the need for clients to install complex RPC software stacks. By placing the translation functionality in a network intermediary rather than on client devices, the solution reduces device complexity while maintaining service accessibility. The intermediary handles all protocol translation, allowing simple client systems to access Microsoft services through standard protocols.
3Adaptability or versatility
If specialized proxy interfacing is implemented, then protocol compatibility is improved, but device complexity deteriorates
Solution Approach 1:
The patent segments the protocol translation functionality into a separate packet filter component rather than integrating it into the client or server. This segmentation allows the complexity of protocol translation to be isolated in a dedicated intermediary layer, keeping client and server implementations simple while achieving broad protocol compatibility through the modular packet filter.
Data Source
AI summary
In particular embodiments, a first computing device associated with a web service may receive a connection from an HTML-compatible client. The first computing device may provide the client a script. A second computing device associated with the web service may receive connection information from the HTML-compatible client and assign the client a unique socket. The second computing device may launch a transcoding remote desktop client and receive a termination of the connection by the client.