Message Router Partial Parsing to Reduce Routing Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing message routing systems in computer networks, particularly in augmented reality applications, face significant latency due to the need to fully decode messages for routing, which is time-consuming and detrimental to performance.
Innovation Solution
Partial decoding of messages at a message router to identify necessary routing information by inspecting fields for an envelope identifier, allowing for efficient routing without complete message deserialization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If a message router fully decodes a message to identify routing information, then routing accuracy is improved, but processing time increases significantly causing latency
Solution Approach 1:
The patent extracts only the essential routing information (envelope identifier) from the message envelope without performing complete message decoding. The message router identifies and extracts the envelope identifier field from the message envelope, which contains sufficient information for routing decisions, thereby avoiding the time-consuming full decoding process while maintaining routing accuracy.
Solution Approach 2:
The patent applies partial decoding by inspecting only the envelope portion of the message rather than the entire message structure. The router performs partial parsing of the envelope to locate the envelope identifier, which is sufficient for routing purposes, thereby reducing processing time while achieving the necessary routing information extraction.
2Adaptability or versatility
If a message router uses traditional full decoding for all messages, then all message types can be routed, but latency increases causing visible lag in AR sessions
Solution Approach 1:
The patent segments the message structure into envelope and payload components, and further segments the envelope processing into identifier detection and full decoding stages. By segmenting the routing decision process to rely only on the envelope identifier rather than full message decoding, the system achieves low-latency routing for AR sessions while maintaining the capability to handle various message types through the envelope structure.
Solution Approach 2:
The envelope identifier acts as an intermediary element that bridges the gap between different message types and the routing system. Instead of requiring full decoding of each message type, the router uses the envelope identifier as an intermediate key to determine routing actions, thereby reducing latency while maintaining adaptability to multiple message formats including protocol buffers.
3Loss of time
If a message router implements partial decoding for speed, then latency is reduced, but the ability to handle existing non-routable protocols is lost
Solution Approach 1:
The patent applies preliminary action by pre-defining envelope structures with standardized identifier fields that can be quickly parsed. Message formats are designed in advance to include recognizable envelope identifiers, allowing the router to perform rapid partial decoding without sacrificing protocol compatibility. This preliminary structuring enables both low-latency processing and broad protocol support.
Solution Approach 2:
The envelope structure serves as a universal container that can wrap various message types including existing non-routable protocols. The envelope identifier provides a common interface for routing decisions across different protocol types, allowing the router to handle both traditional and new message formats efficiently without requiring full decoding of each specific protocol.
Data Source
AI summary
A message router partially decodes messages to determine how to route the messages. The message router receives a message and identifies a field of the message as a candidate field for including an envelope identifier that indicates an envelope type of the message. The envelope type of the message indicates where information, such as where to route the message, is stored within the message. The message router attempts to decode the candidate field to determine whether the candidate field includes the envelope identifier, and responsive to the candidate filed including the envelope identifier, the message router determines the envelope type of the message. The message router routes the message according to the envelope type.