CROSS-ARCHITECTURE FLIGHT TRACKING SYSTEM

• US 20100029254A1
• Filed: 08/04/2008
• Published: 02/04/2010
• Est. Priority Date: 08/04/2008
• Status: Active Grant

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture SPA (Accenture PLC)
• Inventors: Esposito, Luigi, Vassallo, Nico, Libonati, Antonietta
• Granted Patent: US 8,634,862 B2
• Time in Patent Office: Days
• US Class Current: 455/414.200
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: G06Q 10/109 Time management, e.g. calendars, reminders, meetings or time accounting
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]

Abstract

A cross-architecture flight tracking system helps an individual keep track of the status of an airline flight. A subscriber receives status updates intelligently and in real time based on the individual'"'"'s accessibility over an instant messaging client. The system facilitates the status updates by maintaining and listing the flight as a contact in the individual'"'"'s instant messaging client contact list, processing status updates from the airline, and dynamically passing the status updates to the subscriber through a channel that will successfully deliver the message.

Claims

1. A flight tracking method comprising:

registering a subscriber endpoint as present with a legacy telecommunication network;

registering the subscriber endpoint as present with a notification system extension to the legacy telecommunication network;

accepting a flight tracking request comprising a flight identifier;

inserting a flight contact entry linked to the flight identifier into an existing contact list for the subscriber endpoint to obtain an updated contact list;

notifying the subscriber endpoint through the notification system extension of the updated contact list including the flight contact entry;

receiving an airline service flight update at the legacy telecommunication network;

maintaining a flight status responsive to the airline service flight update; and

communicating the flight status to the subscriber endpoint in a flight contact object status message for the existing contact list.

2. The method of claim 1, further comprising:

communicating a flight contact object notification message regarding the flight status to the subscriber endpoint.

3. The method of claim 2, further comprising:

determining a communication channel for communicating the flight contact object notification message to the subscriber endpoint.

4. The method of claim 3, further comprising:

sending the flight contact object notification message to the subscriber endpoint through the communication channel.

5. The method of claim 3, where determining comprises:

choosing a message service communication channel supporting the subscriber endpoint through the notification system extension to the legacy telecommunication network.

6. The method of claim 5, where the message service communication channel comprises an Instant Message (IM) communication channel.

7. The method of claim 3, further comprising:

choosing a message service communication channel supporting the subscriber endpoint through the legacy telecommunication network.

8. The method of claim 7, where the message service communication channel comprises a Short Message Service (SMS) communication channel.

9. A flight tracking system comprising:

a notification system extension to a legacy telecommunication network comprising;

a subscriber service operable to register a subscriber endpoint as present with the notification system extension;

the legacy telecommunication network comprising;

a legacy network presence register operable to register the subscriber endpoint as present with the legacy telecommunication network;

a gateway operable to accept a flight tracking request from the subscriber endpoint, the flight tracking request comprising a flight identifier, and an airline flight status update;

an orchestration module operable to;

insert a flight contact entry linked to the flight identifier into an existing contact list for the subscriber endpoint to obtain an updated contact list; and

maintain a flight status responsive to the airline service flight update;

a legacy presence server operable to;

initiate notification to the subscriber endpoint of the updated contact list including the flight contact entry; and

initiate communication of the flight status to the subscriber endpoint in a flight contact object status message for the existing contact list.

10. The system of claim 9, where the legacy presence server is further operable to initiate communication of a flight contact object notification message regarding the flight status to the subscriber endpoint.

11. The system of claim 10, where the legacy presence server is further operable to determine a communication channel for communicating the flight contact object notification message to the subscriber endpoint.

12. The system of claim 11, where the legacy presence server is further operable to send the flight contact object notification message to the subscriber endpoint through the communication channel.

13. The system of claim 11, where the legacy presence server is further operable to determine the communication channel by:

choosing a message service communication channel supporting the subscriber endpoint through the notification system extension to the legacy telecommunication network.

14. The system of claim 13, where the legacy presence server is further operable to choose a message service communication channel comprising an Instant Message (IM) communication channel.

15. The system of claim 11, where the legacy presence server is further operable to determine the communication channel by:

choosing a message service communication channel supporting the subscriber endpoint through the legacy telecommunication network.

16. The system of claim 15, where the legacy presence server is further operable to choose a message service communication channel comprising a Short Message Service (SMS) communication channel.

17. A product comprising:

a memory;

registration logic stored in the memory operable to;

register a subscriber endpoint as present with a legacy telecommunication network; and

register the subscriber endpoint as present with a notification system extension to the legacy telecommunication network;

input logic stored in the memory operable to;

accept a flight tracking request comprising a flight identifier; and

receive an airline service flight update at the legacy telecommunication network;

processing logic stored in the memory operable to;

insert a flight contact entry linked to the flight identifier into an existing contact list for the subscriber endpoint to obtain an updated contact list; and

maintain a flight status responsive to the airline service flight update; and

output logic stored in the memory operable to;

notify the subscriber endpoint through the notification system extension of the updated contact list including a flight contact entry; and

communicate the flight status to the subscriber endpoint in a flight contact object status message for the existing contact list.

18. The product of claim 17, where the output logic is further operable to communicate a flight contact object notification message regarding the flight status to the subscriber endpoint.

19. The product of claim 18, where the processing logic is further operable to determine a communication channel for communicating the flight contact object notification message to the subscriber endpoint.

20. The product of claim 19, where the output logic is further operable to send the flight contact object notification message to the subscriber endpoint through the communication channel.