HTML5 Network Entity for Cross-Protocol Communication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
HTML5 applications are limited in their ability to communicate using network protocols other than HTTP and WebSocket, as they require native applications or plugins for each operating system and service type, restricting their functionality and compatibility.
Innovation Solution
A Network Entity running as a HTML5 Application (NEHA) is introduced, which includes a mirror network entity (MNE) to enable communication with desired network protocols without the need for native applications or plugins, using a HTTP server and a communicating unit to process requests and responses, allowing the NEHA to act as both a client and server for unsupported protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If native applications or plugins are installed per browser and per operating system to enable network protocol communication, then network protocol compatibility is improved, but device complexity and ease of operation deteriorate due to complex installation procedures
Solution Approach 1:
The patent implements a universal HTML5-based network client that can communicate with multiple network protocols (IGMP, UPnP, DLNA, etc.) through a single platform. The system uses a protocol adapter architecture where different network protocols are converted to work through a common HTML5 interface, eliminating the need for separate native applications for each protocol and operating system combination.
Solution Approach 2:
The patent introduces a protocol adapter as an intermediary component that sits between the HTML5 application and the target network protocol. This adapter translates and mediates communication between the standardized HTML5 interface and various proprietary network protocols, allowing the HTML5 application to interact with different protocols without requiring protocol-specific native code.
2Adaptability or versatility
If native applications or plugins are installed per service type to enable network functionality, then network functionality versatility is improved, but ease of operation worsens due to multiple individual installations required
Solution Approach 1:
The system provides a single HTML5 application that can perform multiple network functions (IGMP joining, UPnP device discovery, DLNA media streaming, etc.) through one unified interface. The protocol adapter framework allows the same HTML5 codebase to support multiple service types and network protocols without requiring separate installations for each function.
3Device complexity
If HTML5 applications are limited to HTTP and WebSocket protocols, then device complexity is reduced, but adaptability to different network protocols deteriorates
Solution Approach 1:
The protocol adapter serves as an intermediary layer that allows HTML5 applications to communicate with non-HTML5 network protocols. The adapter handles protocol-specific complexities while presenting a unified HTML5 interface to the application, thus maintaining HTML5 simplicity while extending protocol support.
Solution Approach 2:
The system segments the network communication functionality into separate protocol adapter modules, each handling a specific network protocol. This modular architecture allows the core HTML5 application to remain simple while adding protocol support through independent adapter components that can be loaded as needed.
Data Source
AI summary
Systems and devices for enabling any network functionality client or server in a HTML5 application. A Network Entity running as a HTML5 Application (NEHA) is for use in a system comprising a HTTP server, a network entity (NE) and a mirror network entity (MNE). The MNE is a mirror instance of the NE and a desired network protocol is run between the MNE and the NE. The NEHA includes a processor configured to create a first request for requesting the MNE, wherein the first request indicates the desired network protocol, send the first request to the HTTP server, receive a first response indicating the MNE from the HTTP server, process the first response, and communicate with the NE through the MNE using the desired network protocol.