HTTP Virtual Server Handling Non-HTTP Data via HTTP Ports

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Telecom providers face challenges in delivering non-HTTP data services, such as streaming video and Voice over IP, as intermediary devices often do not handle non-HTTP data via HTTP ports, leading to service delivery issues due to uncertainty about open non-HTTP ports.

Innovation Solution

Implementing a Hypertext Transfer Protocol Virtual Server (HTTPVS) on an intermediary appliance to enable the transfer and processing of non-HTTP data through HTTP ports, allowing telecom providers to transmit both HTTP and non-HTTP data using known HTTP ports, thereby overcoming port compatibility issues.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If intermediary devices open HTTP ports to allow HTTP traffic, then HTTP communication is enabled, but security issues arise and non-HTTP traffic cannot be properly handled

Engineering Contradiction:

Improveprotocol handling capabilityVSAvoidsecurity issues

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an intermediary device (HTTPVS - HTTP Virtual Server) that acts as a mediator between non-HTTP applications and HTTP ports. This intermediary translates non-HTTP protocols into HTTP protocols, allowing applications to use secure HTTP ports without directly exposing non-HTTP traffic, thus resolving the security issue while maintaining protocol versatility

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the protocol parameter by translating non-HTTP protocols into HTTP protocol over the same port. This parameter transformation allows the system to maintain security benefits of HTTP while supporting non-HTTP applications, resolving the contradiction between security and adaptability

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If telecom providers use known HTTP ports for non-HTTP data transmission, then port compatibility is improved, but intermediary devices cannot handle non-HTTP data via HTTP ports

Engineering Contradiction:

Improveport compatibilityVSAvoidintermediary device capability

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent makes the intermediary device universal by enabling it to handle both HTTP and non-HTTP data through HTTP ports. The HTTPVS functionality allows a single intermediary device to process multiple protocol types, improving port compatibility without requiring separate handling mechanisms for different protocols

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The HTTPVS acts as an intermediary that bridges the gap between non-HTTP applications and HTTP ports. It translates non-HTTP protocols into HTTP protocols, allowing intermediary devices to properly handle non-HTTP data via HTTP ports while maintaining ease of implementation

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If non-HTTP data is transmitted through HTTP ports, then service delivery flexibility is improved, but intermediary devices may not be able to handle the data properly

Engineering Contradiction:

Improveservice delivery flexibilityVSAvoiddata handling capability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The HTTPVS intermediary ensures reliable data handling by properly translating and processing non-HTTP data before it reaches the HTTP port. This intermediary mechanism maintains data integrity and proper protocol handling, resolving the reliability issue while preserving service delivery flexibility

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the protocol parameters by translating non-HTTP data into HTTP protocol format. This parameter transformation ensures that intermediary devices can reliably handle the data using standard HTTP processing mechanisms, while still allowing flexible service delivery through HTTP ports

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentEP2267942B1Systems and methods of handling non-http client or server push on http vserver

Publication Date: 2014.08.13 CITRIX SYSTEMS INC

Figure 1A
Figure 1B
Figure 1C

AI summary

The present application presents systems and methods for handling by an HTTP virtual server (HTTPVS), connections via which non-HTTP data is transmitted between clients and servers. HTTPVS intercepts a request from a client to establish first transport layer connection (TLC) with a server. HTTPVS establishes second TLC with the servers in response to receiving an acknowledgment from a client to establish the first TLC. HTTPVS determines if a first network packet transmitted via first TLC comprises an HTTP payload or non-HTTP payload. If HTTPVP the first network packet includes HTTP payload, HTTPVS may process all transmissions from the first TLC in accordance with connection tracking and forward the processed transmissions to the server via the second TLC. If HTTPVS determines that the first network packet does not include an HTTP payload, HTTPVS may link the first TLC and the second TLC so the client and server exchange non-HTTP communication without interruption.