Cross-architecture flight tracking system

• US 8,634,862 B2
• Filed: 08/04/2008
• Issued: 01/21/2014
• Est. Priority Date: 08/04/2008
• Status: Active Grant

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture Global Services Limited (Accenture PLC)
• Inventors: Libonati, Antonietta, Esposito, Luigi, Vassallo, Nico
• Primary Examiner(s): Patel, Mahendra
• Assistant Examiner(s): Hua, Quan M
• Application Number:
  US12/185,523
• Publication Number:
  US 20100029254A1
• Time in Patent Office: 1,996 Days
• Field of Search: 455/412.1, 455/412.2, 455/414.1, 455/414.4, 455/431, 4554561-457, 455/466, 455/550.1, 455/556.1, 455/556.2, 455/566, 709/204, 709/206, 709/207, 709216-219, 705/1.1, 705/5, 340/963, 340/988
• US Class Current: 455/466
• 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 device with a legacy telecommunication network;

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

accepting a flight tracking request comprising a flight identifier;

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

after receiving the airline service flight update, inserting, into an existing contact list associated with the subscriber end point device, a flight contact entry linked to the flight identifier to obtain an updated contact list, wherein the existing contact list stores a plurality of contact entries, each contact entry being associated with a contact from which the subscriber endpoint device accepts messages;

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

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

determining whether the subscriber endpoint device is present and available to communicate with the notification system extension;

if the subscriber endpoint device is present and available to communicate with the notification system extension, communicating the flight status to the subscriber endpoint in a flight contact object status message for the existing contact list via the notification system extension; and

if the subscriber endpoint device is not present and available to communicate with the notification system extension, communicating the flight status to the subscriber endpoint device as a Short Message Service (SMS) via the legacy telecommunication network.

2. The method of claim 1, further comprising:

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

3. The method of claim 2, further comprising:

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

4. The method of claim 3, further comprising:

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

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

choosing a message service communication channel supporting the subscriber endpoint device 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 device 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 device with the notification system extension;

the legacy telecommunication network comprising;

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

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

an orchestration module operable to;

insert, into an existing contact list associated with the subscriber end point device and after receiving the flight tracking request, a flight contact entry linked to the flight identifier into an existing contact list for the subscriber endpoint device to obtain an updated contact list, wherein the existing contact list stores a plurality of contact entries, each contact entry being associated with a contact from which the subscriber endpoint device accepts messages; and

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

a legacy presence server operable to;

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

determine whether the subscriber endpoint device is present and available to communicate with the notification system extension;

if the subscriber endpoint device is present and available to communicate with the notification system extension, initiate communication of the flight status to the subscriber endpoint in a flight contact object status message for the existing contact list; and

if the subscriber endpoint device is not present and available to communicate with the notification system extension, initiate communication of the flight status to the subscriber endpoint device as a Short Message Service (SMS) via the legacy telecommunication network.

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 device.

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 device.

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 device 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 device 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 device 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 comprising at least one code section for tracking flight information; and

a processor in communication with the memory, wherein the at least one code section includes registration logic operable to cause the processor to;

register a subscriber endpoint device with a legacy telecommunication network ; and

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

wherein the at least one code section includes input logic operable to cause the processor 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, into an existing contact list associated with the subscriber end point device and after receipt of the airline service flight update, a flight contact entry linked to the flight identifier into an existing contact list for the subscriber endpoint device to obtain an updated contact list, wherein the existing contact list stores a plurality of contact entries, each contact entry being associated with a contact from which the subscriber endpoint device accepts messages; and

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

wherein the at least one code section includes output logic operable to cause the processor to;

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

determine whether the subscriber endpoint device is present and available to communicate with the notification system extension;

if the subscriber endpoint device is present and available to communicate with the notification system extension, communicate the flight status to the subscriber endpoint device in a flight contact object status message for the existing contact list via the notification system extension; and

if the subscriber endpoint device is not present and available to communicate with the notification system extension, communicate the flight status to the subscriber endpoint device as a Short Message Service (SMS) via the legacy telecommunication network.

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

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

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