Abstract: A method of data access control in an intermediation server includes: storing a record containing: a record identifier; a plurality of sections each containing data; and in association with each section, an owner identifier selected from a set of requester identifiers corresponding to respective requester subsystems; storing access control data corresponding to each requester identifier; wherein the access control data for a given requester identifier indicates which other requester identifiers are permitted to access a section of the record having the given requester identifier associated therewith as the owner identifier; responsive to receiving, from one of the requester subsystems, a request containing the record identifier and an active one of the requester identifiers corresponding to the active requester subsystem: granting access to a subset of the sections according to the active requester identifier, the owner identifiers and the access control data.

Abstract: A method of data access control in an intermediation server includes: storing a record containing: a record identifier; a plurality of sections each containing data; and in association with each section, an owner identifier selected from a set of requester identifiers corresponding to respective requester subsystems; storing access control data corresponding to each requester identifier; wherein the access control data for a given requester identifier indicates which other requester identifiers are permitted to access a section of the record having the given requester identifier associated therewith as the owner identifier; responsive to receiving, from one of the requester subsystems, a request containing the record identifier and an active one of the requester identifiers corresponding to the active requester subsystem: granting access to a subset of the sections according to the active requester identifier, the owner identifiers and the access control data.

Abstract: 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.

Abstract: Methods, systems, and computer program products for handling electronic miscellaneous documents in response to voluntary modifications of services. A request, which includes first data for a passenger name record, is received for the airline reservation change. Second data for a first electronic miscellaneous document, which is linked to the first data for the passenger name record, is also received. A determination is made as to whether the first electronic miscellaneous document can be exchanged by applying at least one exchange eligibility rule to the first and second data. If the first electronic miscellaneous document can be exchanged, a fare for a service associated with the first electronic miscellaneous document is obtained from a pricing engine associated with the first electronic miscellaneous document. In response to receiving the fare for the service, the passenger name record is updated with a second electronic miscellaneous document including the fare for the service.

Abstract: Methods, systems, and computer program products for handling electronic miscellaneous documents in response to involuntary modifications of services. A request, which includes first data for a passenger name record, is received for a change to an airline reservation. Second data for an electronic miscellaneous document that is linked to the first data for the passenger name record is also received. A determination is made as to whether the electronic miscellaneous document can be exchanged by applying at least one exchange eligibility rule to the first data for the passenger name record and the second data for the electronic miscellaneous document. If the electronic miscellaneous document can be exchanged, an exchange of the electronic miscellaneous document is automatically processed.

Abstract: 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.

Abstract: A computer-implemented method is disclosed for interacting with a user. The method includes receiving information from a user via a configuration tool, the information being related to a request made by the user to implement a user interface for a bilateral special service request (SSR); and using the received information, in conjunction with a passenger name record service framework (PSF), implementing a user-specific user interface to permit one or more passenger name record elements associated with an instance of the requested bilateral SSR to be included as an element of an instance of a passenger name record (PNR). Also disclosed is a system that is configured to perform the steps of the method with the use of at least one data processor.

Abstract: A method of providing data synchronization in a data processing architecture including a data store, a client-server or web server system for accessing said data store, and at least one, possibly heterogeneous, external system independent of said data store. A version merge mechanism handles concurrent update of a given user data in said data store occurring when said data are simultaneously modified by the user and by other processes operating on said external systems. A particular feature of said method is that user related data, including data from the external systems, are saved without risk of loss even if the user has started a user session and is still working on it, and user session is not forced to be saved until the user decides so. A system is described, with a system architecture that suits the disclosed method. Several system configurations and typical use scenarios are provided.

Abstract: A system and method of managing computer sessions are provided. The preferred method opens a session (such as for access to a database) and creates a token that includes a session opening time and a measure of the session duration. If the token is used within a predefined time window before the end of the session, the session is extended by updating the token to reflect a new session duration. The time window and duration of a session extension may be adjusted according to usage patterns of the system. The session may be extended recursively. The token expires when the last of the session extensions expires.

Abstract: A system and method of managing computer sessions are provided. The preferred method opens a session (such as for access to a database) and creates a token that includes a session opening time and a measure of the session duration. If the token is used within a predefined time window before the end of the session, the session is extended by updating the token to reflect a new session duration. The time window and duration of a session extension may be adjusted according to usage patterns of the system. The session may be extended recursively. The token expires when the last of the session extensions expires.