Message Envelope Dependency Sequencing for Multi-Standard Messaging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Message processing systems face challenges in maintaining the correct order of messages, especially in NDC reservations where multiple messages with dependencies need to be sent to message targets in a well-defined order, while also being backward compatible with legacy TTY message flows.

Innovation Solution

A message processing system that generates message envelopes and computes dependencies at both the message envelope and message levels to ensure correct sequencing, supporting both NDC and TTY message standards in a unified manner, allowing for integrated processing of messages with different types, functions, and priorities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple messages are sent to message targets in NDC reservations, then the functionality and coverage of message processing is improved, but the complexity of maintaining correct message ordering increases

Engineering Contradiction:
Improvemessage processing functionalityVSAvoidmessage ordering complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The message processing system segments messages into different message envelopes based on their destination and processing requirements. Each message envelope contains one or more messages that share common routing and ordering characteristics. This segmentation allows the system to manage complex ordering requirements by breaking them down into smaller, more manageable units that can be processed independently while maintaining overall message sequence integrity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary computation of message envelope dependencies and message dependencies before actual message transmission. By pre-calculating the required message order based on dependency relationships, the system establishes a sending sequence in advance, which simplifies the transmission phase and ensures correct ordering without requiring complex real-time decision-making during message delivery.

Inventive Principle:
Principle #10Preliminary action

2Manufacturing precision

If message envelope dependencies and message dependencies are computed, then message ordering accuracy is improved, but the processing time and computational load increase

Engineering Contradiction:
Improvemessage ordering accuracyVSAvoidprocessing time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The system computes message envelope dependencies and message dependencies in advance, before message transmission begins. This preliminary computation establishes the complete message sending sequence upfront, allowing the system to achieve high ordering accuracy without repeated calculations during transmission. The time cost is incurred once during setup rather than continuously during message delivery.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates dependency models and message sequence representations that can be reused for multiple messages with similar characteristics. By establishing template-based dependency relationships, the system avoids redundant computation for each individual message while maintaining precise ordering control across all messages in the system.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If the system supports both NDC and legacy TTY message standards, then backward compatibility is improved, but the system complexity increases

Engineering Contradiction:
Improvebackward compatibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The message processing system is designed with universal components that can handle multiple message standards (NDC and legacy TTY) through a common architecture. The dependency computation mechanism, message envelope structure, and sequencing logic are standardized to work with different message types and formats, allowing the system to support multiple standards without requiring separate processing paths for each standard.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system introduces message envelopes as an intermediary layer between the dependency computation mechanism and the actual message content. This envelope structure provides a standardized interface that abstracts away the differences between NDC and TTY message formats, allowing the core processing logic to remain simple while supporting diverse message standards through the uniform envelope wrapper.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10728205B2Multi-standard message processing
Publication Date: 2020.07.28 AMADEUS SAS
  • US10728205B2 patent drawing
  • US10728205B2 patent drawing
  • US10728205B2 patent drawing

AI summary

Messages are processed in a distributed messaging system by a message processing engine. Message targets operates according to a first standard or a second legacy standard. In response to receiving a database commit indication, a message envelope is generated for each message target to be notified operating according to the first standard and at least one messages within each message envelope. Message envelope dependencies between generated message envelopes for a same message target are computed. Message dependencies between the messages within each message envelope are computed based at least on the standard of the messages of the respective message envelope and functions of the messages. The messages are sent to the respective message target in a sequence based on the message envelope dependencies and the message dependencies.