XML Routing Protocol Encoding for Network Extensibility

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional routing protocols face challenges with extensibility, backwards compatibility, and interoperability due to fixed message formats, which lead to issues with version changes and different system architectures, making it difficult to handle new fields and debugging network problems.

Innovation Solution

The use of XML encoding for control plane protocol messages in content-based networks through the XML Link State Protocol (XLSP) and XML Subscription Management Protocol (XSMP) allows for flexible message formatting, ensuring forward extensibility and backwards compatibility, eliminating endian-ness concerns, and enabling easier debugging.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If fixed message formats with pre-defined fields are used, then message parsing is simple and deterministic, but the protocol lacks extensibility and requires version changes for new fields

Engineering Contradiction:

Improveprotocol extensibilityVSAvoidmessage format complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies dynamics by transitioning from static fixed-field formats to dynamic TLV structures where message formats can adapt to new requirements without changing the fundamental protocol structure. New fields can be added by simply creating new TLV entries rather than redefining the entire message format.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The invention changes the parameter representation from fixed-size fields to variable-length TLV structures. Each field is represented as a type-length-value triplet, allowing the length parameter to vary dynamically based on the actual data size rather than being predetermined.

Inventive Principle:

Principle #35Parameter changes

2Adaptability or versatility

If version numbers are incremented to add new fields, then the protocol can evolve, but backwards compatibility is broken

Engineering Contradiction:

Improveprotocol evolutionVSAvoidbackwards compatibility

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies preliminary action by defining a comprehensive type registry in advance that enumerates all possible field types. This allows receivers to understand any field type without requiring protocol version updates, as the type registry serves as a pre-established reference for all current and future field types.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The invention creates a universal type-length-value framework that can accommodate any field type through the type registry mechanism. The same TLV structure and type registry system handles both existing and new field types uniformly, eliminating the need for version-specific parsing logic.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If Type-Length-Value encoding is used, then message extensibility improves, but parsing complexity increases due to variable field sizes

Engineering Contradiction:

Improvemessage extensibilityVSAvoidmessage parsing ease

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent replaces the mechanical sequential parsing approach with a type-driven parsing mechanism. Instead of sequentially processing fixed-offset fields, the parser uses the type field to look up field definitions in the type registry, then uses the length field to precisely delimit each field's boundaries, simplifying the parsing logic despite variable sizes.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The type registry serves as an intermediary between the variable-length TLV message structure and the protocol's semantic meaning. It translates type codes into human-readable field names and validation rules, mediating between the flexible encoding format and the rigid requirements of protocol semantics.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Adaptability or versatility

If different system architectures with different endian-ness are supported, then interoperability improves, but encoding/decoding complexity increases

Engineering Contradiction:

ImproveinteroperabilityVSAvoidencoding complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies homogeneity by standardizing all multi-byte field encodings to network byte order (big-endian) in the TLV format. This creates a uniform encoding scheme that all systems must follow, eliminating the need for architecture-specific endianness handling and simplifying interoperability between different system architectures.

Inventive Principle:

Principle #33Homogeneity

Data Source

PatentUS7512125B2Coding of routing protocol messages in markup language

Publication Date: 2009.03.31 SOLACE CORP

AI summary

An implicit routing protocol for content-based networks having a plurality of XML routers includes an XML Link State Protocol and an XML Subscription Management Protocol that routes customer data based on XML content. The XML Link State Protocol and the XML Subscription Management Protocol includes several messages that must be exchanged between XML routers in the network. These messages are encoded using XML.