Transporting HTTP Over XMPP via Compact HTTP Binding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current technologies fail to efficiently transport HTTP messages over XMPP networks and expose mobile device functions as web resources that can be manipulated by HTTP, limiting the use of REST services in mobile environments due to the lack of defined protocols for HTTP transport over XMPP.
Innovation Solution
The development of Compact HTTP, a lightweight protocol subset of HTTP 1.1, which binds HTTP to multiple messaging protocols like XMPP and SMS, enabling asynchrony and event-driven REST web services on mobile phones, and introduces hyperlink presence to mitigate broken link issues, along with a security profile for flexible security contexts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If HTTP is bound to UDP for asynchronous messages in Constrained REST Environments, then processing time and memory requirements are reduced, but mobile phones cannot be reached because they do not have reachable IP addresses
Solution Approach 1:
The patent introduces an XMPP server as an intermediary component that mediates between HTTP clients and mobile devices. The server receives HTTP requests, translates them into XMPP messages, and delivers them to mobile devices through the XMPP network infrastructure, thereby enabling HTTP communication without requiring direct IP reachability
2Adaptability or versatility
If a full HTTP protocol is implemented on mobile devices, then web resource manipulation capability is provided, but device complexity and resource consumption increase
Solution Approach 1:
The patent extracts the complex HTTP protocol implementation from the mobile device and relocates it to the XMPP server. The mobile device only needs to implement lightweight HTTP client functionality for initiating requests, while the server handles the full HTTP protocol stack, message translation, and complex protocol logic
Solution Approach 2:
The XMPP server acts as an intermediary that handles the complex HTTP protocol implementation, message formatting, and protocol translation. This allows mobile devices to access web resources without implementing the full HTTP protocol stack locally
3Speed
If XMPP protocol is used for bidirectional communication, then real-time notification flow is achieved, but HTTP messages cannot be transported over XMPP networks
Solution Approach 1:
The patent changes the parameter of message format and protocol structure by defining a mapping between HTTP messages and XMPP stanzas. HTTP requests are transformed into specific XMPP message types with structured bodies, and HTTP responses are similarly encoded in XMPP format, enabling HTTP semantics to be conveyed over XMPP transport
4Reliability
If mobile devices connect to cellular networks without public IP addresses, then network connectivity is provided, but REST services cannot accept outside HTTP requests
Solution Approach 1:
The XMPP server functions as a gateway intermediary that receives HTTP requests from external clients, translates them into XMPP messages, and forwards them to mobile devices on the cellular network. This enables REST services on devices without public IP addresses to be accessible from outside the network
Data Source
AI summary
Method to transport HTTP over XMPP, including: forming a first two-level URI template to identify web resources accessible by use of HTTP in an XMPP network, wherein a first level is XMPP-formatted and a second level is HTTP-formatted; binding HTTP to XMPP <message> and <iq> stanzas; transmitting the HTTP messages in those stanzas; receiving HTTP messages in those stanzas; and a XMPP mechanism to discover if an XMPP entity supports transporting HTTP over XMPP.