Aggregation Record for Multi-PNR Ancillary Service EMDs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The current electronic ticketing systems face complexity and increased computational overhead due to the need for multiple Electronic Miscellaneous Documents (EMDs) when an itinerary spans across multiple Passenger Name Records (PNRs), especially when segments are booked through different carriers or agents, leading to confusion for travelers and service providers.
Innovation Solution
A method and apparatus that aggregate data from multiple PNRs into a single Electronic Miscellaneous Document (EMD) by creating an aggregation record and a mapping record, allowing a single EMD to be issued for ancillary services across multiple service providers, thereby simplifying the issuance and management of EMDs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a separate EMD is issued for each PNR to provide ancillary services across multi-carrier itineraries, then the system maintains accuracy in service allocation, but the document complexity and computational overhead increase significantly
Solution Approach 1:
The patent merges multiple PNR-specific EMDs into a single consolidated EMD that serves the entire itinerary. The system creates an aggregation record that combines traveler data, segment data, and EMD data from multiple PNRs into one unified document, eliminating the need for separate EMDs while maintaining service allocation accuracy through the mapping record that links the consolidated EMD to its source PNRs.
Solution Approach 2:
The consolidated EMD serves multiple functions simultaneously: it acts as the ancillary service entitlement document for the entire itinerary, maintains associations with multiple source PNRs through mapping records, and provides a single point of management for service providers. This universal document replaces multiple specialized EMDs while preserving their individual associations.
2Adaptability or versatility
If multiple EMDs are issued for itineraries spanning multiple PNRs, then each carrier's departure control system can independently manage its segments, but traveler confusion and operational overhead increase
Solution Approach 1:
The system segments the EMD management process into two distinct components: the consolidated EMD that provides a unified view for travelers, and the mapping record that maintains individual associations with source PNRs for each carrier's departure control system. This segmentation allows both traveler simplicity and system independence to coexist.
Solution Approach 2:
The mapping record acts as an intermediary between the consolidated EMD and the multiple source PNRs. It enables carrier departure control systems to independently manage their segments by providing direct links to their respective PNR data, while travelers interact with a single simplified EMD without needing to understand the underlying multi-PNR structure.
3Measurement precision
If separate EMDs are maintained for each PNR in multi-carrier itineraries, then computational precision in tracking ancillary services is preserved, but processing time and system resources increase
Solution Approach 1:
The system creates a consolidated copy of the essential EMD data from multiple source PNRs into a single aggregation record. This copy contains all necessary traveler data, segment data, and ancillary service information needed for accurate tracking, while the mapping record preserves the links to source systems. Processing operates on the single consolidated copy rather than multiple originals, reducing computational overhead while maintaining precision.
Data Source
AI summary
Methods, systems, and computer program products for managing an Electronic Miscellaneous Document (EMD). In response to receiving a request for an ancillary service, an aggregation module generates an aggregation record. The aggregation module may obtain passenger and segment data from a plurality of Passenger Name Records (PNRs), and add this data to the aggregation record. The aggregation record may thereby provide a database object including passenger and segment data from multiple PNRs associated with an itinerary. The aggregation record may be associated with an EMD, and may be configured so that a single EMD can be issued to a traveler for an ancillary service provided across an itinerary comprising multiple PNRs. A mapping record may also be generated that links the EMD, aggregation record, and PNRs. The mapping record may thereby provide an index that enables a database to quickly identify relationships between EMDs, aggregation records, and PNRs.