(19) TZZ _Z_T

(11) EP 2 154 640 B1

(12) EUROPEAN PATENT SPECIFICATION

(45) Date of publication and mention (51) Int Cl.: of the grant of the patent: G06Q 10/00 (2012.01) H04L 12/58 (2006.01) 28.05.2014 Bulletin 2014/22 G06Q 10/10 (2012.01)

(21) Application number: 09006917.0

(22) Date of filing: 22.05.2009

(54) Cross-architecture flight tracking system Architekturübergreifendes Flugüberwachungssystem Système de suivi de trajectoire de vol avec architecture croisée

(84) Designated Contracting States: • ESPOSITO, Luigi AT BE BG CH CY CZ DE DK EE ES FI FR GB GR 81027 San Felice a Cancello (IT) HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL • VASSALLO, Nico PT RO SE SI SK TR 03035 Fontana Liri (FR) (IT)

(30) Priority: 04.08.2008 US 185523 (74) Representative: Müller-Boré & Partner Patentanwälte PartG mbB (43) Date of publication of application: Friedenheimer Brücke 21 17.02.2010 Bulletin 2010/07 80639 München (DE)

(73) Proprietor: Accenture Global Services Limited (56) References cited: Dublin 4 (IE) EP-A1- 1 372 095 EP-A2- 0 948 160 WO-A2-2005/010678 US-A1- 2003 046 296 (72) Inventors: • LIBONATI, Antonietta 36-00179 Rome (IT)

Note: Within nine months of the publication of the mention of the grant of the European patent in the European Patent Bulletin, any person may give notice to the European Patent Office of opposition to that patent, in accordance with the Implementing Regulations. Notice of opposition shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention). EP 2 154 640 B1

Printed by Jouve, 75001 PARIS (FR) 1 EP 2 154 640 B1 2

Description contact list update message flow, and a flight status up- date message flow. BACKGROUND OF THE INVENTION [0008] Figure 3 shows a flight status notification mes- sage flow. 1. Technical Field. 5 [0009] Figure 4 shows a subscriber registration flow diagram. [0001] This disclosure relates to the communication of [0010] Figure 5 shows an NSE subscriber registration object information, and in particular relates to the relaying flow diagram. of flight status information to an instant messaging client [0011] Figure 6 shows a flight entry object creation flow for display to a subscriber. 10 diagram. [0012] Figure 7 shows a flight status update message 2. Related Art. flow diagram. [0013] Figure 8 shows a flight status notification mes- [0002] Even as the world’s population continues to ex- sage flow diagram. pand, our ability to communicate with one another and 15 [0014] Figure 9 shows an alternative cross-architec- exchange ideas brings us closer together. These ave- ture flight tracking architecture. nues for communication also bring the world’s informa- [0015] Figure 10 shows a registration logic flow dia- tion within the reach of our fingertips. Different technol- gram. ogies have been developed to take advantage of a need [0016] Figure 11 shows an input logic flow diagram. for an individual to be connected. Many individuals utilize 20 [0017] Figure 12 shows a processing logic flow dia- multiple, different technologies to maintain their connect- gram for flight object creation. edness. With the plethora of technology available, a need [0018] Figure 13 shows a processing logic flow dia- exists for getting the right information in the right manner gram for flight status updating. to the right individual. [0019] Figure 14 shows a processing logic flow dia- 25 gram for flight status update notification. SUMMARY [0020] Figure 15 shows an output logic flow diagram. [0021] Figure 16 shows a subscriber endpoint contact [0003] A cross-architecture flight tracking system list rendering with a flight object. helps an individual keep track of the status of an airline [0022] Figure 17 shows a subscriber endpoint contact flight. A subscriber receives status updates intelligently 30 list rendering with a flight status update. and in real time based on the individual’s accessibility [0023] Figure 18 shows a subscriber endpoint contact over an instant messaging client. The system facilitates list rendering with a flight status notification. the status updates by maintaining and listing the flight as [0024] Figure 19 shows a subscriber endpoint with cli- a contact in the individual’s instant messaging client con- ent logic. tact list, processing status updates from the airline, and 35 [0025] Figure 20 shows a client logic flow diagram. dynamically passing the status updates to the subscriber through a channel that will successfully deliver the mes- DETAILED DESCRIPTION OF THE PREFERRED EM- sage. BODIMENTS [0004] Other systems, methods, features and advan- tages will be, or will become, apparent to one with skill 40 [0026] Figure 1 shows a cross-architecture flight track- in the art upon examination of the following figures and ing architecture 100. The architecture 100 includes a leg- detailed description. All such additional systems, meth- acy telecommunications network (LTN) 102, a notifica- ods, features and advantages are included within this tion system extension (NSE) 104 to the LTN, a commu- description, are within the scope of the claimed subject nications network 106, and subscriber endpoints (SE) matter, and are protected by the following claims. 45 108. The LTN 102 may communicate with a third-party gateway 110. The third-party gateway 110 may commu- BRIEF DESCRIPTION OF THE DRAWINGS nicate with a third party client 112. The third party client 112 may be an airline computer system, including, as [0005] The system may be better understood with ref- examples, a reservation system, flight status system, erence to the following drawings and description. The 50 passenger assignment system, or other airline process- elements in the figures are not necessarily to scale, em- ing system. As additional examples, the airline computer phasis instead being placed upon illustrating the princi- system may be an airline’s web server, a terminal oper- ples of the system. In the figures, like-referenced numer- ated by an airline representative, or any other third-party als designate corresponding parts throughout the differ- input source. The third party client 112 may be in com- ent views. 55 munication with a subscriber through the communica- [0006] Figure 1 shows a cross-architecture flight track- tions network 106. For example, the third party client may ing architecture. receive instructions from the subscriber, reformat the in- [0007] Figure 2 shows a flight object creation flow, a structions from the subscriber, and forward the reformat-

2 3 EP 2 154 640 B1 4 ted instructions to the third party gateway 110. The third- the NSE 104 to hypertext transfer protocol (HTTP) re- party gateway 110 may be internal or external to the LTN quests for the UD 120 or SO 114, and vice versa. 102. [0032] The network presence module 124 manages [0027] The legacy telecommunications network 102 in- presence information for any or all the legacy SEs 144. cludes a service orchestration (SO) module 114, a SO- 5 The network presence module 124 may include a notifi- presence server (SO-PS) interface 116, an internet pro- cation agent (NA). The NA may manage incoming pres- tocol (IP) multimedia subsystem (IMS) presence server ence information from a legacy SE 144. The NA may also 118, as an exemplary legacy presence server, a unified choose the right channel to send information to a sub- directory (UD) 120, a UD-session initiation protocol (SIP) scriber, e.g. via the NSE 104 or through a legacy com- gateway 122, a network presence module 124, a SIP 10 munication channel, such as the network connection in- application server (SIP AS) 126, and a network connec- terface 128. tion interface 128. Each of these components may be in [0033] The network presence module 124 may also communication with each of the other components, either include a presence network agent (PNA). The PNA may through the SO 114 or independent of the SO 114. The be in communication with the IMS presence server 118 SO 114 communicates with the third party gateway 110. 15 and the GLMS 130. The PNA as an exemplary legacy The LTN 102 may include a service delivery platform network presence register or part of an exemplary legacy (SDP) or an architecture that emulates SDP functions. network presence register may gather legacy subscriber Such functions may include translating events to and presence status information from a legacy SE 144 and from canonical formats and standardized messages, as publish this information on the IMS presence server. The well as processing service requests to and from applica- 20 PNA may query presence status information from legacy tions to individual network nodes and service platforms. subscribers according to the interface capability provided [0028] The SO 114 may orchestrate communications by the legacy network. The legacy presence status infor- andmessage translations betweenapplications, network mation may be stored in and retrieved from the unified nodes, and/or service platforms. The SO-presence serv- directory 120 as an exemplary legacy network presence er interface 116 may perform communications transla- 25 register or part of an exemplary legacy network presence tions between the SO 114 and the IMS presence server register. 118. For example, the SO-presence server interface 116 [0034] The SIP AS 126 communicates with the NSE may be a presence watcher (Pw) network gateway (Pw 104, for example, to send instant messages to an IMS- NGW). The SO-presence server interface 116 may also enabled SE 108. The network communication interface include an extensible markup language (XML) configu- 30 128 communicates with legacy SE 108 through the net- ration access protocol (XCAP) network gateway (XCAP work 106. A legacy SE 144 may be identified by a mobile NGW). The XCAP NGW may perform communications subscriber integrated services digital network (MSISDN) translations between the SO 114, the Pw NGW, or any number or a broadband/internet protocol (IP) television of the other LTN modules and a group list management (IPTV) subscriber identification, such as an e-mail ad- server (GLMS) 130. 35 dress. [0029] The IMS presence server 118 executes and [0035] The notification system extension 104 includes controls services based on the internet protocol (IP) pro- call session control functions (CSCF), such as a proxy- tocol, as well as manages NSE presence information. CSCF (P-CSCF) and an interrogating-CSCF (I-CSCF) NSE presence information may include IMS presence 132, as well as a serving-CSCF (S-CSCF) 134. The NSE information.A group list management server (GLMS)130 40 104 also includes a home subscriber server (HSS) 136. may be internal to the IMS presence server 118. Alter- The P-CSCF/I-CSCF 132 sits on the path of all signaling natively, the GLMS 130 may be external to and in com- messages, has the ability to inspect those messages, munication with the IMS presence server 118. The GLMS and authenticates subscribers. The S-CSCF 134 han- 130 may store a subscriber’s contact list and perform dles SIP registrations, sits on the path of all signaling functions such as adding, editing, and deleting groups 45 messages, has the ability to inspect those messages, and contacts from the subscriber’s contact list. decides which application servers (AS) to forward SIP [0030] The unified directory 120 stores subscriber in- messages, and routes messages. The S-CSCF may be formation such as legacy subscriber profile information an exemplary subscriber service or part of an exemplary and legacy subscriber presence information. The UD 120 subscriber service. The HSS 136 is a master database may communicate with the NSE 104 through the UD-SIP 50 that supports the other NSE components. The HSS 136 gateway 122, a SE 108 through the network presence may store subscription-related information, such as sub- module 124, and/or the SO 114. Hence, the UD-SIP gate- scriber profiles. The HSS 136 may be an exemplary sub- way 122 may be an exemplary gateway operable to ac- scriber service or part of an exemplary subscriber serv- cept a flight tracking request. ice.The NSE 104 may include other IMS control elements [0031] The UD-SIP gateway 122 exposes the UD 120 55 and/or be an IMS control system. to the NSE 104. The UD-SIP gateway 122 may include [0036] The communications network 106 may include an IMS service control (ISC) network gateway (ISC an IMS-enabled network 138 and a legacy network 140. NGW). The ISC NGW may translate SIP messages from The communications network 106 may include an xDSL

3 5 EP 2 154 640 B1 6 network, an IP network, and/or a mobile network, or com- airline seat reservation. The subscriber instructs the SE binations thereof. The communications network 106 may 108 to communicate a flight tracking subscription com- include wired networks, wireless networks, or combina- mand to the third party gateway 110 (206). The third party tions thereof. The wireless network may be a cellular tel- gateway 110 may be an exemplary gateway operable to ephone network using data networking standards such 5 accept a flight tracking request. For example, the SE 108 as 1xRTT, UMTS, HSDPA, EDGE, or EVDO, or an may issue a command to the airline service, and the air- 802.11, 802.11 b, 802.11 g, 802.11n, 802.16, or 802.20 line service may forward that request to the third party network. Further, the network 106 may be a public net- gateway 110. Alternatively, the SE 108 may provide a work, such as the Internet, a private network, such as an command directly to the third party gateway 110. The intranet, or combinations thereof, and may utilize a vari- 10 third party gateway 110 then forwards that request to the ety of networking protocols now available or later devel- SO 114 (208). The SO 114 may optionally determine oped including, but not limited to TCP/IP based network- whether the SE 108 or the subscriber associated with ing protocols. Information provided by the network 106 the SE 108 has an account with the UD (210). The UD may be accessed through web browsers or mobile web 120 may confirm that the SE 108 or subscriber has an browsers. The browser may be the MICROSOFT (TM) 15 account (212) or deny that an account exists. INTERNET EXPLORER (TM) browser, MOZILLA (TM) [0041] The SO 114 then requests the IMS presence FIREFOX (TM) browser, APPLE (TM) SAFARI (TM) server 118 to insert a flight contact entry, e.g. a flight browser, MICROSOFT (TM) POCKET INTERNET EX- contact object, into the subscriber’s contact list. For ex- PLORER (POCKET IE) (TM) browser, OPERA (TM) ample, the IMS presence server 118 may add the flight MINI (TM) browser, ACCESS (TM) NETFRONT (TM) 20 contact entry into a subscriber contact list stored in the browser, PALM (TM) BLAZER (TM) browser, NOKIA GLMS 130. The flight contact entry may include flight (TM) MINI MAP (TM) browser, CINGULAR (TM) MEDIA identifiers and/or flight status information, such as a flight NET (TM) access, BLACKBERRY (TM) browser, or number, airline name, time and date of departure, termi- THUNDERHAWK (TM) browser. nal number, gate number, and/or seat number. [0037] The network 106 may include wide area net- 25 [0042] Once the IMS presence server creates the flight works (WAN), such as the internet, local area networks contact entry in the subscriber’s contact list, the IMS pres- (LAN), campus area networks, metropolitan area net- ence server notifies the SE 108 of the updated contact works, or any other networks that may allow for data com- list. For example, the IMS presence server sends the munication. The network 106 may be divided into sub- notification message to the NSE 104 (216). The NSE 104 networks. The sub-networks may allow access to all of 30 then converts and sends the notification message to the the other components connected to the network 106, or SE 108 (218). The SE 108 may then retrieve the updated the sub-networks may restrict access between the com- contact list. ponents connected to the network 106. The network 106 [0043] An airline may desire to notify the subscriber of may be regarded as a public or private network connec- changes of flight status. The airline may communicate to tion and may include, for example, a virtual private net- 35 the third party gateway 110 flight status update informa- work or an encryption or other security mechanism em- tion. The flight status update information may indicate a ployed over the public Internet, or the like. preference for a passive notification. A passive notifica- [0038] The subscriber endpoints (SE) 108 may include tion may include an update to the status message in a IMS-enabled clients142 and non-IMS compatible clients, contact list. The third party gateway 110 then communi- e.g. legacy SE 144. IMS-enabled clients 142 may include 40 cates the flight status update information to the SO 114 systems capable of running instant messaging applica- (220). The SO 114 then communicates the flight status tions. Legacy SE 144 may include global system for mo- update information to the IMS presence server 118 (222). bile communications (GSM) phones and/or broad- The IMS presence server may then update the status band/IPTV subscribers. information for the flight object. For example, the IMS [0039] Figure 2 shows a flight entry object creation45 presence server may update the status information for flow, a contact list update message flow, and a flight sta- the flight contact entry of a subscriber contact list stored tus update message flow 200. The SE 108 sends a mes- in the GLMS 130. The IMS presence server 118 then sage to the UD 120 notifying the UD 120 to register the notifies the SE 108 of the updated flight status. For ex- SE 108 as present and available (202). This message ample, the IMS presence server 118 communicates the may be sent through the network 106 and the network 50 updated flight status information to the NSE 104 (224). presence module 124. The SE 108 may also send a mes- The NSE 104 may then convert and send the updated sage to the NSE 104 to register the SE 108 as present flight status information to the SE 108 (226). The SE 108 and available (204). The second registration 204 may may then display the updated flight status information as occur, for example, when the SE 108 is running an IMS- status information associated with a contact within a con- enabled client, such as an instant messaging application. 55 tact list display. [0040] The subscriber may desire to subscribe to and [0044] Figure 3 shows a flight status notification mes- issue a flight tracking subscription command to subscribe sage flow 300. An airline may desire to actively notify the to a flight tracking feature upon, or subsequent to, an subscriber of changes of flight status. The airline may

4 7 EP 2 154 640 B1 8 communicate to the third party gateway 110 the flight the network presence module 124 may check with the status update information. The flight status update infor- UD 120 to see if the SE 108 has an account with the LTN mation may include a preference for active notification. 102. If the SE is not authorized, the network presence An active notification may include a pop-up instant mes- module 124 notifies the SE 108 that they are not author- sage window containing a message. The third party gate- 5 ized to use the LTN services (408). way 110 communicates the flight status update informa- [0049] If the SE 108 is authorized, the SE 108 may tion to the SO 114 (302). The SO 114 communicates the optionally register with the NSE 104 (410). This registra- flight status update information to the IMS presence serv- tion may occur, for example, when the SE 108 is running er 118 (304). The IMS presence server may update the an IMS compatible client, such as an instant messaging status information for the flight object. For example, the 10 application. The NSE 104 checks with the HSS 136 to IMS presence server may update the status information determine whether the SE 108 is authorized (412). If the for the flight contact entry of a subscriber contact list check determines that the SE 108 is authorized, the NSE stored in the GLMS 130. 104 acknowledges that the SE 108 is authorized (414). [0045] The IMS presence server 118 may determine If the SE 108 is not authorized, then the NSE 104 notifies which communication channel to use to actively notify 15 the SE 108 of the failure (408). the SE 108 of the updated flight status (306). For exam- [0050] Figure 5 shows an NSE subscriber registration ple, the IMS presence server 118 may determine whether flow diagram 410. The SE 108 first attempts to register theSE 108 isregistered as presentwith the IMS presence with the NSE 104 (502). The initial registration attempt server. If the SE 108 is registered as present with the may fail (504). The SE 108 then sends a registration com- IMS presence server 118, the IMS presence server 118 20 mand to the NSE 104 (506). The registration command may decide to send the flight status notification through may be sent to the P-CSCF. The P-CSCF then finds the the NSE 104. If the SE 108 is not registered as present home network entry point (508). The home network entry with the IMS presence server 118, the IMS presence point may be the I-CSCF. The P-CSCF then forwards server 118 may decide to send the flight status notifica- the registration request to that I-CSCF (510). The I-CSCF tion through an alternative communication channel. 25 queries the HSS 136 to find the allocated S-CSCF 134 [0046] The IMS presence server 118 may communi- for the SE 108 (512). If no S-CSCF 134 is allocated, or cate the updated flight status information to the NSE 104 if the SE 108 is otherwise not authorized for the NSE (308). The NSE 104 may convert and send the updated 104, the NSE 104 notifies the SE 108 that authorization flight status information to the SE 108 (310). The SE 108 does not exist (514). may actively display the updated flight status information, 30 [0051] If a S-CSCF 134 is allocated, or if the SE 108 e.g. through an instant message pop-up window. Alter- is otherwise authorized for the NSE 104, then the HSS natively or additionally, the IMS presence server 118 may 136 returns the address of the S-CSCF 134 allocated to communicate the updated flight status information to the the SE 108 (516). The I-CSCF forwards the registration SO 114 (312). The SO 114 may convert and send the request to the S-CSCF 134 (518). The HSS 136 also updated flight status information to the SE 108 (314). For 35 returns to the I-CSCF a profile containing filter criteria example, the SO 114 may send the updated flight status corresponding to the SE 108 (520). The I-CSCF forwards information through the network communication inter- the profile to the S-CSCF 134. The S-CSCF 134 evalu- face 128 to a legacy network infrastructure 140. The SE ates the filter criteria to determine whether the IMS pres- 108 may then actively display the updated flight status ence server 118 and/or the UD-SIP gateway 122 should information, e.g., as a short message service (SMS) text 40 be contacted (522). message. [0052] If the IMS presence server 118 should be con- [0047] Figure 4 shows a subscriber registration flow tacted, the S-CSCF 134 creates a new registration re- diagram 400. A subscriber first registers with a SE 108 quest and sends the new registration request to the IMS (402). For example, the subscriber may log in to a termi- presence server 118 (524). The IMS presence server nal, and once authenticated by the terminal, the subscrib- 45 may then acknowledge the request (526). If the UD-SIP er may then log in to an instant messaging application gateway 122 should be contacted, the S-CSCF 134 cre- and/or an instant messaging server. Alternatively, a sub- ates a new registration request and sends the new reg- scriber may initialize a SE 108, and the SE 108 may reg- istration request to the UD-SIP gateway 122 (528). The ister with a network. The subscriber may register with UD-SIP gateway 122 may then acknowledge the request more than one SE 108. For example, a subscriber may 50 (530). The UD-SIP gateway 122 may then notify the UD register through an instant messaging client and through 120 of the registration of the SE 108 (532). The S-CSCF a GSM phone. 134 may then notify the P-CSCF about the registration [0048] The SE 108 registers with a network presence success or failure (534). The P-CSCF may then notify module 124 (404). This registration informs the LTN 102 theSE 108 about theregistration success or failure (536). that the SE 108 is available for communication through 55 [0053] Figure 6 shows a flight object creation flow di- the communication network 106. The network presence agram 600. A subscriber notifies an airline about their module 124 communicates with the UD 120 to determine desire to subscribe to a flight tracking feature (602). The whether the SE 108 is authorized (406). For example, airline requests the third party gateway 110 to verify that

5 9 EP 2 154 640 B1 10 the subscriber has an account through which the flight ample, the SE 108 may update a status message within tracking feature may be implemented (604). The TGP a client window displaying a rendering of the subscriber’s 110 may determine whether the airline has authorization contact list. to request the flight tracking feature for the subscriber [0058] Figure 8 shows a flight status notification mes- (606). If the airline is not authorized then the TGP notifies 5 sage flow diagram 800. The airline sends a request to the airline that the request cannot be completed (608). the TPG 110 to notify the SE 108 of a flight status update [0054] If the airline is authorized then the TGP 110 con- (802). The TPG 110 forwards the request to the SO 114 tacts a service broker to verify that the SE 108 has an (804). The SO 114 checks with the UD 120 to determine associated account with the LTN 102 (610). For example, whether the SE 108 is present through the NSE 104 the TGP 110 may communicate with the SO 114 to re- 10 (806). If the SE 108 is present through the NSE 104, then quest the verification. The service broker contacts the the SO forwards the flight status update notification to UD 120 for the verification (612). If the UD 120 is unable the UD-SIP gateway 122 (808). The UD-SIP gateway to verify the existence of an account associated with the converts the information to an instant message notifica- SE 108, then the TGP 110 notifies the airline that the tion and sends the notification to the SE 108 through the request cannot be completed (608). If an account exists, 15 NSE 104 (810). When the SE 108 receives the instant then the UD 120 acknowledges the request to the TPG message notification, the SE 108 may cause the sub- 110 (614). The TPG 110 then passes the acknowledge- scriber’s client to open an instant message window and ment to the airline (616). display the flight status update information (812). If the [0055] The airline may send a request to the TPG 110 SE 108 is not present through the NSE 104, then the SO for the addition of a flight contact object entry to the sub- 20 114 may convert the information to an SMS text message scriber’s contact list (618). This request may be per- and send the message to the SE 108 through the network formed after or concurrently with the initial request to ver- connection interface 128 (814). When the SE 108 re- ify the existence of the subscriber 614. The TPG 110 ceives the SMS text message, the SE 108 may cause forwards the request to the SO 114 (620). The SO for- the subscriber’s client to display the SMS text message wards the request to the SO-presence server interface 25 (816). 116 (622). The SO-presence server interface 116 adds [0059] Figure 9 shows an alternative cross-architec- the flight contact object entry to the subscriber’s contact ture flight tracking architecture 900. In Figure 9, the sys- list in the GLMS 118 (624). For example, the XCAP NGW tem architecture 900 includes a centralized implementa- may receive the request from the SO 114 and commu- tion of the functionality noted above. In other words, the nicate the addition of the flight contact object entry to the 30 system need not be implemented with the distributed and GLMS 118. delineated architecture shown in Figure 1, but may be [0056] The SO-presence server interface publishes collapsed into fewer modules, systems, servers, or other status of the flight contact object entry to the IMS pres- realizations of the system. The architecture 900 includes ence server 118 (626). For example, the Pw NGW may a display 902, a processor 904, a memory 906, and com- receive notification from the XCAP NGW of the addition 35 munication logic 908. The communication logic 908 may of the flight contact object entry, and the Pw NGW may interface messages among the display 902, the proces- notify the IMS presence server 118 of the updated flight sor 904, the memory 906, and the networks 138 and 140. status. The UD-SIP gateway 122 may then notify the SE Each of the networks 138 and 140 may be in communi- 108 about the contact list update (628). For example, the cation with subscriber endpoints 108 and/or with each SO-presence server may notify the UD-SIP gateway 122 40 other. of the contact list update with an instruction to relay the [0060] The memory 906 includes flight tracking logic information to the SE 108. The UD-SIP gateway 122 may 910, legacy telecommunications logic 912, notification notify the SE 108 through the NSE 104. The SE 108 may system extension logic 914, a flight tracking request 916, then request and retrieve the updated contact list from and a contact list 918. The memory 906 may include one the GLMS 118 (630). 45 or multiple versions of these components. The flight [0057] Figure 7 shows a flight status update message tracking logic 910 may instruct the processor 904 to per- flow diagram 700. An airline communicates with the TPG form process flows for tracking of flight information. The 110of a flightstatus change (702). The TGP110 forwards LT logic 912 may instruct the processor 904 to perform the flight status change information through the SO 114 process flows consistent with operations of the LTN 102. to the SO-presence server interface 116 (704). For ex- 50 The NSE logic 914 may instruct the processor 904 to ample, the request may be forwarded to the Pw NGW. perform process flows consistent with operations of the The SO-presence server interface 116 publishes the NSE 104. The flight tracking request 916 stores informa- flight status to the IMS presence server 118 (706). For tion related to a flight tracking request. The contact list example, the Pw NGW may publish the status. The IMS 918 stores data related to a subscriber’s contact list. The presence server 118 then communicates to the SE 108 55 contact list 918 may be consistent with a contact list the flight status update (708). The communication may stored in the GLMS 130. be performed through the NSE 104. The SE 108 may [0061] The flight tracking logic 910 includes registra- change the status of the flight object entry (710). For ex- tion logic 920, input logic 922, processing logic 924, and

6 11 EP 2 154 640 B1 12 output logic 926. The registration logic 920 may instruct [0064] The flight tracking request 916 includes a flight the processor 904 to register a SE 108 with LT logic 912 identifier 944, a subscriber identifier 946, and preferred and/or withNSE logic 914.In other words, the registration SE information 948. The flight identifier 944 may be used logic 920 may be similar, in particular substantially iden- in the creation of a flight contact entry. The subscriber tical to or comprise/be comprised by legacy network pres- 5 identifier 946 may be used in finding a contact list in which ence register and/or the subscriber service. The input to enter a flight contact entry. The subscriber identifier logic 922 may instruct the processor 904 to handle com- 946 may also be used to identify the SE 108 to which a municationsfrom a SE108 oran airline tothe architecture contact list update notification message may be sent. The 900. In other words, the input logic 922 may be similar, preferred SE information 948 may be used to identify to inparticular substantiallyidentical to or comprise/be com- 10 which SE 108 associated with a subscriber any commu- prised by the gateway operable to accept a flight tracking nications should be preferably directed. For example, a request. The processing logic 924 may instruct the proc- subscriber may use an instant message client running essor 904 to process communications among the LT log- on a laptop, as well as a GSM phone. The subscriber ic 912, the NSE logic 914, a SE 108, and an airline. In may prefer notifications sent to the instant message client other words, the processing logic 924 may be similar, in 15 when the instant message client is available over text particular substantially identical to or comprise/be com- messages to the GSM phone. Alternatively or addition- prised by the legacy presence server. The output logic ally, an airline may prefer that SMS-compatible clients 926 may instruct the processor 904 to handle communi- be notified before IMS-enabled clients. cations from the architecture 900 to a SE 108 or an airline. [0065] The contact list 918 includes a subscriber ID In other words, the output logic 926 may be similar, in 20 950, a flight contact entry 952, a friend contact entry 954, particular substantially identical to or comprise/be com- and a work contact entry 956. The contact list may have prised by the legacy presence server. one or multiple versions of these components. For ex- [0062] The LT logic 912 includes LT presence infor- ample, a contact list 918 may have multiple subscriber mation 928 and flight update information 930. The LT IDs 950 corresponding to different platform-specific IDs, presence information 928 may include presence infor- 25 such as an AMERICA ONLINE (TM) INSTANT MES- mation for a SE 108. For example, the LT presence in- SENGER (AIM) (TM) ID, a YAHOO! (TM) MESSENGER formation 928 may indicate that a SE 108 is available for (TM) ID, and a WINDOWS (TM) LIVE MESSENGER communication through a legacy network architecture (TM) ID. Alternatively or additionally, a contact list 918 140. The flight update information 930 may be used to may have one or multiple flight contact entries 952, friend internally update flight information within the architecture 30 contact entries 954, and/or work contact entries 956. 900. Alternatively or additionally, the flight update infor- [0066] The subscriber ID 950 may be used to identify mation 930 may be used to notify a SE 108 for an updated the contact list 918. The flight contact entry 952 includes flight status. The flight update information 930 may in- a flight ID 958 and flight status information 960. The flight clude a subscriber identifier 932, a flight identifier 934, a ID 958 may be used to identify the flight contact entry flight status 936, and/or a method of notification 938. The 35 952. The flight status information 960 may be sent to subscriber identifier 932 may be used to direct a notifi- interested parties, such as a SE 108, for display to the cation message sent to a SE 108 or to identify a contact subscriber. The friend contact entry 954 includes a friend list 918 for updating. The flight ID 934 may be used to ID 962 and friend status information 964. The friend ID identify a flight contact entry for updating. Alternatively 962 may be used to identify the friend contact entry 954 or additionally, the flight ID 934 may be used in a notifi- 40 and may correspond to a subscriber ID 950 of another cation message sent to a SE 108 to identify the flight with contact list 918. The friend status information 964 may the update. The flight status 936 may be stored with a be sent to interested parties, such as a SE 108, for display contact list 918. Alternatively or additionally, the flight sta- to the subscriber. The work contact entry 956 includes a tus 936 may be sent to a SE 108 to inform a subscriber work contact ID 966 and work contact status information of, e.g., a flight delay or cancellation. A notification meth- 45 968. The work contact ID 966 may be used to identify od 938 may indicate whether an airline desires a sub- the work contact entry 952 and may correspond to a sub- scriber to receive a notification through a change of con- scriber ID 950 of another contact list 918. The work con- tact status, an instant message, or through an SMS text. tact status information 968 may be sent to interested par- [0063] The NSE logic 914 includes notification system ties, such as a SE 108, for display to the subscriber. extension presence information 940 and subscriber pro- 50 [0067] Figure 10 shows a flow diagram 1000 that may file information 942. The NSE presence information 940 be performed by registration logic 920. Registration logic may include presence information for a SE 108. For ex- 920 receives notification that a SE 108 is present (1002). ample, the NSE presence information 940 may indicate The notification may originate from the SE 108. Regis- that a SE 108 is available for communication through an tration logic 920 parses identification information from IMS network 138. The subscriber profile information 942 55 the notification (1004). The ID information may include a may be used to establish proper communication chan- subscriber identifier and/or a SE identifier. Registration nels. The subscriber profile information 942 may also logic 920 sends a notification along with the ID informa- contain filter criteria. tion to LT logic 912 (1006). This notification may be the

7 13 EP 2 154 640 B1 14 notification originally received by the registration logic include a subscriber identifier, a SE identifier, and/or a 920, or it may be a reformatted version of the original flight identifier. Input logic 922 also parses update infor- notification. Registration logic 920 determines whether mation from the message, such as updated flight status the ID information is authorized with the LT logic 912 information (1112). Input logic 922 then sends the parsed (1006). For example, the LT logic may compare the ID 5 information to processing logic 924 (1114). The parsed information against a list of authorized subscribers and information may include the ID information, the updated send a confirmation signal to the registration logic 920. information, and/or any additional information from the [0068] If registration logic 920 determines the ID is not request. authorized, then the registration logic 920 returns to the [0073] Figure 12 shows a flow diagram 1200 for flight requester a notification that the registration cannot be 10 object creation that may be performed by processing log- completed (1008). However, if registration logic 920 de- ic 924. Processing logic 924 receives a flight tracking termines the ID is authorized, then the registration logic request (1202). The request may originate from input log- 920 stores the ID as present with the LT logic 912 (1010). ic 922. Alternatively or additionally, the request may orig- For example, registration logic 920 may request the LT inate from the TPG 110, communication logic 908, or logic 912 store the ID as LT presence information 928. 15 from an airline. The request may include identification Registration logic 920 optionally sends a notification information, such as a subscriber identifier, a SE identi- along with the ID information to NSE logic 914 (1012). fier, and/or a flight identifier. The request may include This notification may be the notification sent to the LT additional information, such as initial flight status infor- logic 912, or it may be a reformatted version of that no- mation. tification. Registration logic 920 requests the NSE logic 20 [0074] Processing logic 924 attempts to locate a con- 914 to determine whether the ID information is authorized tact list 918 (1204). Processing logic 924 may use the (1014). For example, the NSE logic 914 may compare identification information to locate the contact list 918. the ID information with a list of authorized subscribers, For example, processing logic 924 may compare a sub- such as a collection of subscriber profile information 942, scriber identifier from the identification information and return a confirmation signal to the registration logic 25 against subscriber identifiers 950 from contact lists 918. 920. If a contact list cannot be located, processing logic 924 [0069] If registration logic 920 determines the ID is not may attempt to create a contact list. If processing logic authorized, then the registration logic 920 returns to the 924 determines that a list will not be created, processing requester a notification that the registration cannot be logic 924 returns to the requester a notification that the completed (1008). However, if registration logic 920 de- 30 flight tracking request cannot be added to the contact list termines the ID is authorized, then the registration logic 918 (1206). 920requests the NSE logic914 to store the ID as present. [0075] If a list does exist, processing logic 924 creates For example, the NSE logic 914 may store the ID infor- a flight contact object entry 952 (1208). Hence, the mation as NSE presence information 940. processinglogic may be similar, in particularsubstantially [0070] Figure 11 shows a flow diagram 1100 that may 35 identical to or comprise/be comprised by the orchestra- be performed by input logic 922. Input logic 922 receives tion module. The flight contact object entry may have a an incoming flight message (1102). The incoming flight format similar to a friend contact entry 954 and/or a work message may originate from an airline. The message contact entry 956. For example, processing logic 924 may be in response to a flight tracking request, a flight may store the flight identifier from the request as a flight status update, or another event. Input logic 922 deter- 40 identifier 958 in the flight contact entry 952. Alternatively mines the type of message (1104). Input logic 922 may or additionally, processing logic 924 may store the initial make this determination by reading type information sent flight status information from the request as flight status as part of the message. Alternatively or additionally, input info 960 in the flight contact entry 952. logic 922 may make the determination based on the in- [0076] Processing logic 924 then inserts the flight con- formation content sent along with the message. 45 tact entry 952 into the contact list 918 (1210). Processing [0071] If input logic 922 determines that the message logic 924 may insert the flight contact entry 952 into the is a flight tracking request, input logic 922 parses ID in- contact list 918 with a subscriber identifier 950 corre- formation from the request (1106). The ID information sponding with the subscriber identifier from the request. may include a subscriber identifier, a SE identifier, and/or Processing logic 924 stores the contact list with the new a flight identifier. Input logic 922 may optionally parse 50 flight contact entry 952 (1212). If no contact list exists additional information from the message, such as initial and processing logic 924 determines that a list should flight status information. Input logic 922 then sends the be created, then processing logic 924 may create a con- parsed information to processing logic 924 (1108). The tact list 918 using the subscriber identifier from the re- parsed information may include the ID information and/or quest before creating a flight contact entry. any additional information from the request. 55 [0077] Figure 13 shows a flow diagram 1300 for flight [0072] If input logic 922 determines that the message status updating that may be performed by processing is a flight update request, input logic 922 parses ID infor- logic 924. Processing logic 924 receives a flight status mation from the request (1110). The ID information may update (1302). The flight status update may originate

8 15 EP 2 154 640 B1 16 from input logic 922. Alternatively or additionally, the re- updated flight status information and NSE communica- quest may originate from the TPG 110, communication tion channel information to output logic 926 (1406). logic 908, or from an airline. The request may include [0083] If processing logic 924 determines that a SE is identification information, such as a subscriber identifier, not available through NSE communication channels, a SE identifier, and/or a flight identifier. 5 processing logic 924 locates an alternative contact chan- The request may include additional information, such as nel associated with the identification information (1408). updated flight status information. For example, processing logic 924 may inquire with LT [0078] Processing logic 924 attempts to locate a con- logic 912 to determine whether the identification informa- tact list 918 (1304). Processing logic 924 may use the tion corresponds to SE identification information in the identification information to locate the contact list 918. 10 LT presence information 928. If so, then processing logic For example, processing logic 924 may compare a sub- 924 may use a LT communication channel to contact the scriber identifier from the identification information SE. Processing logic 924 passes the flight status update against subscriber identifiers 950 from contact lists 918. information and the alternative contact channel informa- If a contact list cannot be located, processing logic 924 tion to output logic 926 (1410). may attempt to create a contact list. If processing logic 15 [0084] Figure 15 shows a flow diagram 1500 that may 924 determines that a list will not be created, processing be performed by output logic 926. Output logic 926 re- logic 924 returns to the requester a notification that the ceives a notification message (1502). The notification flight status update request cannot be performed (1306). message may originate from processing logic 924. Alter- [0079] If a list does exist, processing logic 924 locates natively or additionally, the message may originate from a flight contact object entry 952 within the contact list 918 20 input logic 922, communication logic 908, or from an air- (1308). Processing logic 924 may use the identification line. The message may include identification information, information to locate the flight contact object entry 952. such as a subscriber identifier, a SE identifier, and/or a For example, processing logic 924 may compare a flight flight identifier. The request may include additional infor- identifier from the identification information against flight mation, such as initial flight status information, updated identifiers 950 from the contact list 918. If a flight contact 25 flight status information, notification that an updated con- entry 952 cannot be located, processing logic 924 may tact list is available, and/or communication channel in- attempt to create a flight contact entry 952. If processing formation. logic 924 determines that a flight contact entry will not be [0085] Output logic 926 determines the type of notifi- created, processing logic 924 returns to the requester a cation message (1504). This determination may include notification that the flight status update request cannot 30 checking a type field within the message. Alternatively be performed (1306). or additionally, the determination may include checking [0080] Processing logic 924 updates the flight contact other information or information fields within the mes- entry with information from the request (1310). For ex- sage. ample, processing logic 924 may store the updated flight [0086] If output logic 926 determines the message is status information from the request as flight status infor- 35 an update message and the update is for a contact list, mation 960 within the flight contact entry 952. Processing output logic 926 retrieve NSE contact information asso- logic 924 stores the flight contact object entry (1312). ciated with a SE 108 (1506). For example, output logic [0081] Figure 14 shows a flow diagram 1400 for flight 926may request the NSE logic 914 to retrieve information status update notification that may be performed by from the NSE presence info 940 or the subscriber profile processing logic 924. Processing logic 924 receives a 40 info 942. Output logic 926 may then send a notification flight status update (1402). The flight status update may message to theSE 108 indicatingthat an updated contact originate from input logic 922. Alternatively or addition- list is available (1508). This notification message may be ally, the request may originate from the TPG 110, com- routed through an IMS-enabled network 138. munication logic 908, or from an airline. The request may [0087] If output logic 926 determines the message is include identification information, such as a subscriber 45 an update message and the update is for a status update, identifier, a SE identifier, and/or a flight identifier. The output logic 926 retrieves NSE channel information as- request may include additional information, such as up- sociated with a SE 108 (1510). For example, output logic dated flight status information. 926may request the NSE logic 914 to retrieve information [0082] Processing logic 924 attempts to locate a NSE from the NSE presence info 940 or the subscriber profile presence status based on the identification information 50 info 942. Output logic 926 may then send a status update (1404). Processing logic 924 may use the identification message to the SE 108 indicating a change in the status information to locate the NSE presence status. For ex- of a contact list entry (1512). This notification message ample, processing logic 924 may compare a SE identifier may be routed through an IMS-enabled network 138. from the identification information against SE identifiers [0088] If output logic 926 determines the message is stored in NSE presence information 940. If processing 55 an active notification message and the notification should logic924 locates corresponding identificationinformation be through an IMS-enabled channel, output logic 926 indicating a SE is registered and present through NSE receives the flight status update information (1514). The communication channels, processing logic 924 passes notification message may originate from processing logic

9 17 EP 2 154 640 B1 18

924. Alternatively or additionally, the message may orig- information associated with the flight identifier rendered inate from input logic 922, communication logic 908, or in the flight identifier rendering 1606. For example, status from an airline. The message may include identification text rendering 1608 indicates that flight 629 is currently information, such as a subscriber identifier, a SE identi- running on time, that its departure time is 3:25pm on 3 fier, and/or a flight identifier. The request may include 5 April 2008, that the flight is out of O’Hare, gate L10, and additional information, such as updated flight status in- that the ticket for business class, seat 21 B has been formation and/or communication channel information. allocated to the subscriber. Alternatively or additionally, [0089] Output logic 926 sends the updated flight status other flight status information may be rendered, such as information to a SE 108 based on the communication other current status information, other departure times channel information (1516). For example, output logic 10 and dates, other airport or terminal information, or other 926may request the NSE logic914 toretrieve information class or seat information. Alternatively or additionally, the from the NSE presence info 940 or the subscriber profile status text rendering 1608 may include an estimated ar- info 942 corresponding to the channel information. The rival time, arrival airport or terminal information, and/or notification message may be routed through an IMS-en- connecting flight information. abled network 138. 15 [0096] The status indicator rendering 1610 indicates a [0090] If output logic 926 determines the message is status of the flight object 1604. For example, status indi- an active notification message and the notification should cator rendering 1610 is currently a white bubble and may be through an alternative communication channel, output indicate no problems with the current flight. Alternatively logic 926 receives the flight status update information or additionally, the status indicator rendering 1610 may (1518). The notification message may originate from20 include other shapes, colors, or forms for indicative pur- processing logic 924. Alternatively or additionally, the poses. The status indicator rendering 1610 may provide message may originate from input logic 922, communi- alternative or additional indications. For example, the sta- cation logic 908, or from an airline. The message may tus indicator rendering 1610 may indicate a delay, a can- include identification information, such as a subscriber cellation, and/or a gate change. identifier, a SE identifier, and/or a flight identifier. The 25 [0097] Figure 17 shows a subscriber endpoint contact request may include additional information, such as up- list rendering 1700 with a flight status update. The ren- dated flight status information and/or communication dering 1700 shows one example of the rendering 1600 channel information. after the SE 108 receives a flight status update message. [0091] Output logic 926 sends the updated flight status For example, status text rendering 1608 now indicates information to a SE 108 based on the communication 30 that flight 629 is delayed, and the new departure time is channel information (1520). For example, output logic 3:55pm. Additionally, the status indicator rendering 1610 926 may request the LT logic 912 to retrieve information is now a grey bubble and may indicate that the flight is from the LT presence info 928 corresponding to the chan- delayed. nel information. The notification message may be routed [0098] Figure 18 shows a subscriber endpoint contact through an legacy network architecture 140. 35 list rendering 1800 with a flight status notification. The [0092] Figure 16 shows a subscriber endpoint contact rendering 1800 shows one example of the rendering list rendering 1600 with a flight object. The rendering 1600 after the SE 108 receives a flight status notification. 1600 includes an objects section 1602. The objects sec- For example, the rendering 1800 includes an instant tion 1602 includes a flight object rendering 1604. Alter- messaging window 1802. The instant messaging window natively or additionally, the flight object rendering 1604 40 1802 may provide an active notification of flight status may be under a section with a different section identifier. update information. For example, the instant messaging Alternatively or additionally, the flight object rendering window 1802 includes an instant message 1804. 1604 may be under a "Friends" or any other display sec- [0099] The instant message 1804 may convey the tion. flight status update information to the subscriber. The [0093] The flight object rendering 1604 displays infor- 45 instant message 1804 includes a flight identifier render- mation associated with a flight object. For example, the ing 1806 and an instant message text 1808. The flight flight object rendering 1604 includes a flight identifier ren- identifier rendering 1806 may indicate the flight associ- dering 1606, a status text rendering 1608, and a status ated with the flight status update information. The flight indicatorrendering 1610. The flight object rendering1604 identifier rendering 1806 may include the same informa- may include more or less components. 50 tion as the flight identifier rendering 1606. The instant [0094] The flight identifier rendering 1606 indicates a message text 1808 may include flight status update in- flight identifier associated with the flight object rendering formation. The instant message text 1808 may include 1604. For example, the flight identifier rendering 1606 the same or similar information as status text rendering indicates that the flight object rendering 1604 corre- 1608. The instant message text 1808 may include addi- sponds to flight number 629. Alternatively or additionally, 55 tional information, such as instructions. For example, the the flight object rendering 1604 may indicate an airline instant message text 1808 includes both status informa- name or other flight indication information. tion indicating the flight has been cancelled and instruc- [0095] The status text rendering 1608 indicates status tions indicating that the subscriber should contact the

10 19 EP 2 154 640 B1 20 airline to reschedule. include receiving logic for receiving the status update [0100] Figure 19 shows an example of a subscriber message 1910 and/or the status notification message endpoint 1900 that supports status update messaging 1912. The instant messaging logic 1924 may further in- and status update notification processing in an instant clude rendering logic for rendering a display. The ren- messaging application. The subscriber endpoint 1900 in- 5 dering logic may render parts or all of the status update cludes a communication interface 1002 (e.g., an anten- message 1910 and/or the status notification message na, amplifier, filter, demodulator, or other signal process- 1912. For example, the rendering logic may render the ing logic), a processor 1904, and a memory 1906. The displays as shown in Figures 16, 17, and/or 18. communication interface 1902 may be a wired or wireless [0105] Figure 20 shows a flow diagram 2000 that may interface, and the transmitted signals may adhere to a 10 be performed by client logic 1908. The client logic 1908 diverse array of formats, modulations, frequency chan- receives notification of a contact list update (2002). The nels, bit rates, and encodings, such as those specified notification may be received from a communication in- by WiFi, Bluetooth, Global System for Mobile communi- terface 1902 in communication with, e.g., a NSE network cations (GSM), Time Division Multiple Access (TDMA), 138. The client logic 1908 retrieves an update contact Frequency Division Multiple Access (FDMA), Evolution- 15 list (2004). The updated contact list may be retrieved Data Optimized (EVDO), Code Division Multiple Access through the communication interface 1902 in communi- (CDMA), 3rd Generation Partnership Project (3GPP or cation with, e.g. a NSE network 138. The client logic 1908 3GPP2), or other wireless or wired protocols. renders the updated contact list in the client window [0101] The processor 1904 executes the client logic (2006). The updated contact list may appear similar to 1908 to carry out the status update messaging and status 20 rendering 1600. update notification processing explained above. [0106] The client logic 1908 receives a flight message Figure 19 shows that the memory 1906 provides storage (2008). The flight message may be received from the for a flight status update message 1910 and a flight status communication interface 1902. The flight status update notification message 1912. The flight status update mes- message may include a flight identifier, flight status in- sage 1910 and/or the flight status notification message 25 formation, and/or additional information. 1912 may be received over the communication interface [0107] If the client logic 1908 determines that the flight 1902. message is a contact list entry status update message, [0102] The flight status update message 1910 includes then the client logic 1908 parses the flight status update a flight identifier 1912, flight status information 1914, and message for statusupdate information(2010). The status additional information1916. The flight identifier 1912 may 30 update information may include an indicator that the flight serve to identify the object for which the status will be is on-time, delayed, cancelled, or any other flight status. updated. The flight status info 1914 may include an indi- The status update information may include any additional cation that the flight is on time, delayed, or cancelled. information, such as departure or arrival times, gate in- The flight status info 1914 may be a text field or a code formation, airport or terminal information, class or seat associated with predetermined statuses. The additional 35 information, or airline instructions. The client logic 1908 info 1916 may be information either the airline may wish renders the contact list in the client window to reflect the to communicate to the subscriber or that the subscriber status update information (2012). The rendering may ap- may wish to receive from the airline. The additional info pear similar to rendering 1700. 1916 may include departure and/or arrival times and/or [0108] If the client logic 1908 determines that the flight dates, airport and/or terminal information, gate informa- 40 message is an active notification, then the client logic tion, and/or class and/or seat information. 1908 parses the flight status notification message for [0103] The flight status notification message 1912 in- flight status update information (2014). The flight status cludes a flight identifier 1918, flight status information update information may include an indicator that the flight 1920, and additional information 1922. The flight identi- is on-time, delayed, cancelled, or any other flight status. fier 1918 may serve to identify the object for which the 45 The status update information may include any additional status will be updated. The flight status info 1920 may information, such as departure or arrival times, gate in- include an indication that the flight is on time, delayed, formation, airport or terminal information, class or seat or cancelled. The flight status info 1920 may be a text information, or airline instructions. The client logic 1908 field or a code associated with predetermined statuses. renders the client window to reflect the status update The additional info 1922 may be information either the 50 information (2016). The rendering may include a pop-up airline may wish to communicate to the subscriber or that window including the status update information. The ren- the subscriber may wish to receive from the airline. The dering may appear similar to rendering 1800. additional info 1922 may include departure and/or arrival [0109] The systems may be implemented in many dif- times and/or dates, airport and/or terminal information, ferent ways. For example, although some features are gate information, class and/or seat information, and/or 55 shown stored in computer-readable memories (e.g., as instructions from the airline. logic implemented as computer-executable instructions [0104] The client logic 1908 includes an instant mes- or as data structures in memory), all or part of the sys- saging logic 1924. The instant messaging logic 1924 may tems, logic, and data structures may be stored on, dis-

11 21 EP 2 154 640 B1 22 tributedacross, or read from other machine-readable me- a legacy telecommunication network; registering the sub- dia. The media may include hard disks, floppy disks, CD- scriber endpoint as present with a notification system ex- ROMs, a signal, such as a signal received from a network tension to the legacy telecommunication network; ac- or partitioned into sections and received in multiple pack- cepting a flight tracking request comprising a flight iden- ets communicated across a network. The systems may 5 tifier; inserting a flight contact entry linked to the flight be implemented in software, hardware, or a combined identifier into an existing contact list for the subscriber form of software and hardware. endpoint to obtain an updated contact list; notifying the [0110] Furthermore, the systems may be implemented subscriber endpoint through the notification system ex- with additional, different, or fewer components. As one tension of the updated contact list including the flight con- example, a processor or any other logic may be imple- 10 tact entry; receiving an airline service flight update at the mented with a microprocessor, a microcontroller, a DSP, legacy telecommunication network; maintaining a flight an application specific integrated circuit (ASIC), program status responsive to the airline service flight update; and instructions, discrete analog or digital logic, or a combi- communicating the flight status to the subscriber end- nation of other types of circuits or logic. As another ex- point in a flight contact object status message for the ample, memories may be DRAM, SRAM, Flash or any 15 existing contact list. other type of memory. The systems may be distributed [0114] The method within the scope defined by the among multiple components, such as among multiple claims may further comprise: communicating a flight con- processors and memories, optionally including multiple tact object notification message regarding the flight sta- distributed processing systems. Logic, such as programs tus to the subscriber endpoint. The method may further or circuitry, may be combined or split among multiple 20 comprise: determining a communication channel for programs, distributed across several memories and communicating the flight contact object notification mes- processors, and may be implemented in or as a function sage to the subscriber endpoint. The method may further library, such as a dynamic link library (DLL) or other comprise: sending the flight contact object notification shared library. message to the subscriber endpoint through the commu- [0111] While various embodiments of the cross-archi- 25 nication channel. The method may further comprise: tecture flight tracking system have been described, it will choosing a message service communication channel be apparent to those of ordinary skill in the art that many supporting the subscriber endpoint through the notifica- more embodiments and implementations are possible tion system extension to the legacy telecommunication within the scope of the invention. Accordingly, the inven- network. The message service communication channel tion is not to be restricted except in light of the attached 30 may comprise an Instant Message communication chan- claims and their equivalents. nel. The method may further comprise: choosing a mes- [0112] In other implementations, the system may track sageservice communication channelsupporting thesub- events other than airline flights using contact list objects. scriber endpoint through the legacy telecommunication Examples of other events include news updates; invest- network. The message service communication channel ment quotes, such as stock, mutual fund, or bond quotes; 35 may comprise a Short Message Service communication online auction status; restaurant wait time updates; ve- channel. hicle repair status, e.g., to track when a repair shop is [0115] Another implementation may relate to a flight finished fixing a car; store sales alerts, e.g., to track when tracking system comprising: a notification system exten- an item goes on sale; and other events. As one specific sion to a legacy telecommunication network comprising: example for news updates, the subscriber may request 40 a subscriber service operable to register a subscriber a subscription for a news service to communicate a news endpoint as present with the notification system exten- story to the LTN 102. The LTN 102 may add the news sion; the legacy telecommunication network comprising: event as an object in the subscriber’s contact list, receive a legacy network presence register operable to register news updates from the news service in the same way the subscriber endpoint as present with the legacy tele- the LTN 102 receives flight updates from an airline, and 45 communication network; a gateway operable to accept communicate the news updates to the subscriber using a flight tracking request from the subscriber endpoint, the either the legacy network infrastructure 140 or the NSE flight tracking request comprising a flight identifier, and 104. Similar event tracking may occur with respect to the an airline flight status update; an orchestration module other examples given above, or an other event, by re- operable to: insert a flight contact entry linked to the flight ceiving an event subscription, creating a corresponding 50 identifier into an existing contact list for the subscriber event object entry in a contact list, sending the updated endpoint to obtain an updated contact list; and maintain contact list to a subscriber, receiving event updates, and a flight status responsive to the airline service flight up- communicating the event updates to the subscriber via date; a legacy presence server operable to: initiate noti- either a legacy network infrastructure or a network sys- fication to the subscriber endpoint of the updated contact tem extension. 55 list including the flight contact entry; and initiate commu- [0113] As a summary, the present invention as defined nication of the flight status to the subscriber endpoint in by the claims may relate to a flight tracking method com- a flight contact object status message for the existing prising: registering a subscriber endpoint as present with contact list.

12 23 EP 2 154 640 B1 24

[0116] Advantageously, the system according to the service flight update; and output logic which may be present application provides an improved man machine stored in the memory and/or be provided as a signal interaction, particularly including displaying an internal and/or as a data stream is operable to: notify the sub- state of the system, e.g. by the notification of the sub- scriber endpoint through the notification system exten- scriber endpoint of the updated contact list and/or by the 5 sion of the updated contact list including a flight contact communication of the flight status to the subscriber end- entry; and communicate the flight status to the subscriber point in the flight contact object status message for the endpoint in a flight contact object status message for the existing contact list. existing contact list. [0117] The legacy presence server may further be op- [0119] The output logic may further be operable to erable to initiate communication of a flight contact object 10 communicate a flight contact object notification message notification message regarding the flight status to the regarding the flight status to the subscriber endpoint. subscriber endpoint. The legacy presence server may The processing logic may further be operable to deter- further be operable to determine a communication chan- mine a communication channel for communicating the nel for communicating the flight contact object notification flight contact object notification message to the subscrib- message to the subscriber endpoint. The legacy pres- 15 er endpoint. The output logic may further be operable to ence server may further be operable to send the flight send the flight contact object notification message to the contact object notification message to the subscriber subscriber endpoint throughthe communication channel. endpoint through the communication channel. The leg- [0120] Other implementations allow an improved data acy presence server may further be operable to deter- provision through a computer system to a user of the mine the communication channel by: choosing a mes- 20 computer system, in particular of one or more elements sage service communication channel supporting the sub- of the computer system. The user may handle a compo- scriber endpoint through the notification system exten- nent of the computer system, such as a mobile device. sion to the legacy telecommunication network. The leg- The computer system may provide the user with data acy presence server may further be operable to choose through said mobile device. Data provision may be fully a message service communication channel comprising 25 automatic or semi automatic. Advantageously, the user an Instant Message (IM) communication channel. The may be provided with data, in particular an update of legacy presence server may further be operable to de- data, such as flight tracking data in an automatic or semi termine the communication channel by: choosing a mes- automatic manner which little or no interaction of the user sage service communication channel supporting the sub- with the network. In other words, the user might not nec- scriber endpoint through the legacy telecommunication 30 essarily request updates of the flight tracking data. Rath- network. The legacy presence server may further be op- er, the data is update automatically. Such an update may erable to choose a message service communication be triggered by a change of the flight tracking data. The channel comprising a Short Message Service (SMS) flight tracking data may comprise or consists of one or communication channel. more data objects. [0118] Another implementation may also relate to a 35 [0121] An improved data provision as well as an im- product, in particular to a computer program product pref- proved data exchange, in particular in an automatic or erably stored on a computer readable memory and/or semiautomatic manneris provided.Thereby, information provided as a signal and/or as a data stream, which when provision and recognition for the user is improved, so that loaded in the memory of a computer and executed by particularly the man machine interaction between the us- the computer urges the computer to carry out the method 40 er and the system is improved. as described above. The product may comprise and/or [0122] The present application is not limited to the access a memory, where registration logic which may be above described embodiments and examples but rather stored in the memory and/or be provided as a signal to the claims. Individual features of one or more of the and/or as a data stream is operable to: register a sub- above described examples/embodiments may be com- scriber endpoint as present with a legacy telecommuni- 45 bined to create one or more further examples/embodi- cation network; and register the subscriber endpoint as ments within that scope. In that respect, the description present with a notification system extension to the legacy relating to one or more of the above examples may also telecommunication network; input logic which may be be applicable, where possible, to the remaining exam- stored in the memory and/or be provided as a signal ples/embodiments and/or additional embodiments. In and/or as a data stream is operable to: accept a flight 50 particular, the description of figures 1 to 8 may be applied tracking request comprising a flight identifier; and receive to the examples/embodiments of figures 9 to 15 and also an airline service flight update at the legacy telecommu- figures 16 to 19. As examples, without limiting the above nication network; processing logic which may be stored description, the description of the LTN 102 is similarly in the memory and/or be provided as a signal and/or as applicable to the flight tracking logic 910. Moreover, the a data stream is operable to: insert a flight contact entry 55 description of the NSE 104 is similarly applicable to the linked to the flight identifier into an existing contact list NSE logic 914. Consequently, the functions and/or meth- for the subscriber endpoint to obtain an updated contact od steps as described with reference to the cross-archi- list; and maintain a flight status responsive to the airline tecture flight tracking architecture according to figures 1

13 25 EP 2 154 640 B1 26 to 8 may be similarly applied to the cross-architecture acy presence server is further operable flight tracking architecture according to figures 9 to 15. to determine the communication chan- nel by:

Claims 5 choosing a message service communica- tion channel supporting the subscriber end- 1. A computer aided flight tracking system comprising: point (108) through the notification system extension (104) to the legacy telecommuni- a notification system extension (104) to a legacy cation network (102); telecommunication network (102) comprising: 10 and to choose a message service commu- nication channel comprising an Instant a subscriber service operable to register a Message (IM) communication channel, subscriber endpoint (108) as present with wherein a unified directory (120) is adapted the notification system extension (104); to store subscriber information comprising 15 legacy subscriber profile information and the legacy telecommunication network (102) legacy subscriber presence information, comprising: wherein the unified directory (120) is adapt- ed to communicate with a notification sys- a legacy network presence register opera- tem extension (104) through a unified direc- ble to register the subscriber endpoint (108) 20 tory-SIP gateway (122), a subscriber end- as present with the legacy telecommunica- point (108) through a network presence tion network (102); module (124), and/or a service orchestra- a gateway operable to accept a flight track- tion module (114). ing request from the subscriber endpoint (108), the flight tracking request comprising 25 2. The system of claim 1, where the legacy presence a flight identifier, and an airline flight status server is further operable to determine the commu- update; nication channel by: an orchestration module operable to: choosing a message service communication insert a flight contact entry linked to the 30 channel supporting the subscriber endpoint flight identifier into an existing contact (108) through the legacy telecommunication list for the subscriber endpoint (108) to network (102). obtain an updated contact list; and maintain a flight status responsive to 3. The system of any of the preceding claims, where the airline service flight update; 35 the legacy presence server is further operable to choose a message service communication channel a legacy presence server operable to: comprising a Short Message Service (SMS) com- munication channel. initiate notification to the subscriber endpoint (108) of the updated contact 40 4. A computer implemented method for tracking flight list including the flight contact entry; data comprising: and initiate communication of the flight sta- computer aided registering of a subscriber end- tus to the subscriber endpoint (108) in point (108) as present with a legacy telecommu- a flight contact object status message 45 nication network (102); for the existing contact list, computer aided registering of the subscriber where the legacy presence server is endpoint (108) as present with a notification sys- further operable to initiate communica- tem extension (104) to the legacy telecommu- tion of a flight contact object notification nication network (102); message regarding the flight status to 50 accepting a flight tracking request comprising a the subscriber endpoint, to determine flight identifier; a communication channel for commu- automatic computer aided inserting of a flight nicating the flight contact object notifi- contact entry linked to the flight identifier into an cation message to the subscriber end- existing contact list for the subscriber endpoint point (108), to send the flight contact 55 (108) to obtain an updated contact list; object notification message to the sub- automatic computer aided notifying of the sub- scriberendpoint (108) throughthe com- scriber endpoint (108) through the notification munication channel and where the leg- system extension (104) of the updated contact

14 27 EP 2 154 640 B1 28

list including the flight contact entry; object notification message to the subscrib- computer aided receiving of an airline service er endpoint (108) through the communica- flight update at the legacy telecommunication tion channel. network (102); computer aided maintaining of a flight status re- 5 7. The method of any one of the preceding claims 4 to sponsive to the airline service flight update; and 6, where determining comprises: automatic computer aided communicating of the flight status to the subscriber endpoint (108) in computer aided choosing of a message service a flight contact object status message for the communication channel supporting the sub- existing contact list, 10 scriber endpoint (108) through the notification wherein the method further comprises the fol- system extension (104) to the legacy telecom- lowing steps munication network (102). initiating communication of a flight contact object notification message regarding the flight status 8. The method of any one of the preceding claims 4 to to the subscriber endpoint, 15 7, where the message service communication chan- determining a communication channel for com- nel comprises an Instant Message (IM) communica- municating the flight contact object notification tion channel. message to the subscriber endpoint (108), sending the flight contact object notification 9. The method of any one of the preceding claims 4 to message to the subscriber endpoint (108)20 8, further comprising: through the communication channel and where the legacy presence server is further operable computer aided choosing of a message service to determine the communication channel by: communication channel supporting the sub- scriber endpoint (108) through the legacy tele- choosing a message service communica- 25 communication network (102). tion channel supporting the subscriber end- point (108) through the notification system 10. The method of any one of the preceding claims 4 to extension (104) to the legacy telecommuni- 8, where the message service communication chan- cation network (102); nel comprises a Short Message Service (SMS) com- and choosing a message service commu- 30 munication channel. nication channel comprising an Instant Message (IM) communication channel, and 11. A computer program product comprising computer storing, in a unified directory (120), sub- readable instructions which when loaded in the scriber information comprising legacy sub- memory of a computer and executed by the compu- scriber profile information and legacy sub- 35 ter cause the computer to carry out the method ac- scriber presence information, wherein the cording to one or more of the claims 4 to 10. unified directory (120) communicates with a notification system extension (104) through a unified directory-SIP gateway Patentansprüche (122), a subscriber endpoint (108) through 40 a network presence module (124), and/or a 1. Computergestütztes Flugüberwachungssystem, service orchestration module (114). umfassend:

5. The method of claim 4, further comprising: eine Benachrichtigungssystemerweiterung 45 (104) für ein bisheriges Telekommunikations- computer aided communicating of a flight con- netz (102), umfassend: tact object notification message regarding the flight status to the subscriber endpoint (108). einen Teilnehmerdienst, der betriebsfähig ist, einen Teilnehmerendpunkt (108) als an- 6. The method of claim 4 or 5, further comprising: 50 wesend auf der Benachrichtigungssyste- merweiterung (104) zu registrieren; automatic computeraided determining of acom- munication channel for communicating the flight wobei das bisherige Telekommunikationsnetz contact object notification message to the sub- (102) umfasst: scriber endpoint (108) and/or further compris- 55 ing: ein bisheriges Netzwerkanwesenheitsre- gister, das betriebsfähig ist, den Teilnehme- computer aided sending of the flight contact rendpunkt (108) als anwesend in dem bis-

15 29 EP 2 154 640 B1 30 herigen Telekommunikationsnetz (102) zu stant Message - IM) umfasst, registrieren; wobei ein vereinheitlichtes Verzeichnis ein Gateway, das betriebsfähig ist, eine (120) angepasst ist, Teilnehmerinformatio- Flugüberwachungsanfrage vom Teilneh- nenzu speichern, diebisherige Teilnehmer- merendpunkt (108) zu akzeptieren, wobei 5 profilinformationen und bisherige Teilneh- die Flugüberwachungsanfrage eine Flug- meranwesenheitsinformationen umfassen, kennung und ein Airline-Flugstatusupdate wobei das vereinheitlichte Verzeichnis umfasst; (120) angepasst ist, mit einer Benachrichti- ein Orchestrierungsmodul, das betriebsfä- gungssystemerweiterung (104) über ein hig ist: 10 vereinheitlichtes Verzeichnis-SIP-Gateway (122), einem Teilnehmerendpunkt (108) einen mit der Flugkennung verknüpften über ein Netzwerkanwesenheitsmodul Flugkontakteintrag in eine bestehende (124) und/oder einem Dienstorchestrie- Kontaktliste für den Teilnehmerend- rungsmodul (114) zu kommunizieren. punkt (108) einzufügen, um eine aktu- 15 alisierte Kontaktliste zu erhalten; und 2. System nach Anspruch 1, wobei der bisherige An- einen auf das Airline-Dienstflug-Up- wesenheitsserver überdies betriebsfähig ist, den date reagierenden Flugstatus beizube- Kommunikationskanal zu bestimmen durch: halten; 20 Auswählen eines den Teilnehmerendpunkt einen bisherigen Anwesenheitsserver, der (108) unterstützenden Nachrichtendienstkom- betriebsfähig ist: munikationskanals durch das bisherige Tele- kommunikationsnetz (102). ein Benachrichtigen über die aktuali- sierte Kontaktliste, die den Flugkontak- 25 3. System nach einem der vorhergehenden Ansprü- teintrag enthält, an den Teilnehme- che, wobei der bisherige Anwesenheitsserver über- rendpunkt (108) auszulösen; und dies betriebsfähig ist, einen Nachrichtendienstkom- ein Kommunizieren des Flugstatus an munikationskanal auszuwählen, der einen Kommu- den Teilnehmerendpunkt (108) in einer nikationskanal für einen Kurzmitteilungsdienst Flugkontaktobjektstatusnachricht für 30 (Short Message Service - SMS) umfasst. die bestehende Kontaktliste auszulö- sen, 4. Computerimplementiertes Verfahren zum Überwa- wobei der bisherige Anwesenheitsser- chen von Flugdaten, umfassend: ver überdies betriebsfähig ist, ein Kom- munizieren einer Flugkontaktobjektbe- 35 computergestütztes Registrieren eines Teilneh- nachrichtigungsnachricht bezüglich merendpunktes (108) als anwesend in einem des Flugstatus an den Teilnehmerend- bisherigen Telekommunikationsnetz (102); punkt auszulösen, um einen Kommu- computergestütztes Registrieren des Teilneh- nikationskanal zum Kommunizieren merendpunktes (108) als anwesend in einer der Flugkontaktobjektbenachrichti-40 Benachrichtigungssystemerweiterung (104) für gungsnachricht an den Teilnehme- das bisherige Telekommunikationsnetz (102); rendpunkt (108) zu bestimmen, die Akzeptieren einer eine Flugkennung umfassen- Flugkontaktobjektbenachrichtigungs- den Flugüberwachungsanfrage; nachricht durch den Kommunikations- automatischescomputergestütztes Einfügen ei- kanal an den Teilnehmerendpunkt45 nes mit der Flugkennung verknüpften Flugkon- (108) zu senden, und wobei der bishe- takteintrags in eine bestehende Kontaktliste für rige Anwesenheitsserver überdies be- den Teilnehmerendpunkt (108), um eine aktua- triebsfähig ist, den Kommunikationska- lisierte Kontaktliste zu erhalten; nal zu bestimmen durch: automatisches computergestütztes Benach- 50 richtigen des Teilnehmerendpunkts (108) durch Auswählen eines den Teilnehmerendpunkt die Benachrichtigungssystemerweiterung (104) (108) unterstützenden Nachrichtendienst- über die aktualisierte Kontaktliste, umfassend kommunikationskanals durch die Benach- den Flugkontakteintrag; richtigungssystemerweiterung(104) für das computergestütztes Empfangen eines Airline- bisherige Telekommunikationsnetz (102); 55 Dienstflug-Updates in dem bisherigen Telekom- und um einen Nachrichtendienstkommuni- munikationsnetz (102); kationskanal auszuwählen, der einen Kom- computergestütztes Beibehalten eines auf das munikationskanal für Sofortnachrichten (In- Airline-Dienstflug-Update reagierenden Flug-

16 31 EP 2 154 640 B1 32

status; und hinsichtlich des Flugstatus an den Teilnehme- automatisches computergestütztes Kommuni- rendpunkt (108). zieren des Flugstatus an den Teilnehmerend- punkt (108) in einer Flugkontaktobjektstatus- 6. Verfahren nach Anspruch 4 oder 5, überdies umfas- nachricht für die bestehende Kontaktliste, 5 send:

wobei das Verfahren überdies die folgen- automatisches computergestütztes Bestimmen den Schritte umfasst: eines Kommunikationskanals zum Kommuni- zieren der Flugkontaktobjektbenachrichti- Auslösen des Kommunizierens einer 10 gungsnachricht an den Teilnehmerendpunkt Flugkontaktobjektbenachrichtigungs- (108), und/oder überdies umfassend: nachricht bezüglich des Flugstatus an den Teilnehmerendpunkt, computergestütztes Senden der Bestimmen eines Kommunikationska- Flugkontaktobjektbenachrichtigungsnach- nals für das Kommunizieren 15 der richt an den Teilnehmerendpunkt (108) Flugkontaktobjektbenachrichtigungs- durch den Kommunikationskanal. nachricht an den Teilnehmerendpunkt (108), 7. Verfahren nach einem der vorhergehenden Ansprü- Senden der Flugkontaktobjektbenach- che 4 bis 6, wobei das Bestimmen umfasst: richtigungsnachricht an den Teilneh- 20 merendpunkt (108) durch den Kommu- computergestütztes Auswählen eines den Teil- nikationskanal, und wobei der bisheri- nehmerendpunkt (108) unterstützenden ge Anwesenheitsserver überdies be- Nachrichtendienstkommunikationskanals triebsfähig ist, den Kommunikationska- durch die Benachrichtigungssystemerweite- nal zu bestimmen durch: 25 rung (104) für das bisherige Telekommunikati- onsnetz (102). Auswählen eines den Teilnehme- rendpunkt (108) unterstützenden 8. Verfahren nach einem der vorhergehenden Ansprü- Nachrichtendienstkommunikati- che 4 bis 7, wobei der Nachrichtendienstkommuni- onskanals durch die Benachrichti- 30 kationskanaleinen Kommunikationskanal für Sofort- gungssystemerweiterung (104) für nachrichten (IM) umfasst. das bisherige Telekommunikati- onsnetz (102); 9. Verfahren nach einem der vorhergehenden Ansprü- und Auswählen eines Nachrich- che 4 bis 8, überdies umfassend: tendienstkommunikationskanals, 35 umfassend einen Kommunikati- computergestütztes Auswählen eines den Teil- onskanal für Sofortnachrichten nehmerendpunkt (108) unterstützenden (IM), und Speichern von Teilneh- Nachrichtendienstkommunikationskanals merinformationen, umfassend bis- durch das bisherige Telekommunikationsnetz herige Teilnehmerprofilinformatio- 40 (102). nen und bisherige Teilnehmeran- wesenheitsinformationen, in ei- 10. Verfahren nach einem der vorhergehenden Ansprü- nem vereinheitlichten Verzeichnis che 4 bis 8, wobei der Nachrichtendienstkommuni- (120), wobei das vereinheitlichte kationskanal einen Kommunikationskanal für einen Verzeichnis (120) mit einer45 Kurznachrichtendienst (SMS) umfasst. Benachrichtigungssystemerweite- rung (104) über ein vereinheitlich- 11. Computerprogrammprodukt, umfassend computer- tes Verzeichnis-SIP-Gateway lesbare Anweisungen, die, wenn sie in den Speicher (122), einem Teilnehmerendpunkt eines Computers geladen und von dem Computer (108) über ein Netzwerkanwesen- 50 ausgeführt werden, den Computer veranlassen, das heitsmodul (124) und/oder einem Verfahren nach einem oder mehreren der Ansprü- Dienstorchestrierungsmodul (114) che 4 bis 10 auszuführen. kommuniziert.

5. Verfahren nach Anspruch 4, überdies umfassend: 55 Revendications

computergestütztes Kommunizieren einer 1. Système de suivi de trajectoire de vol assisté par Flugkontaktobjektbenachrichtigungsnachricht ordinateur, comprenant :

17 33 EP 2 154 640 B1 34 une extension de système de notification (104) communication, et dans lequel le ser- à un réseau de télécommunication précédent veur de présence précédent est en (102) comprenant : outre conçu pour déterminer le canal de communication en : un service d’abonné conçu pour enregistrer 5 un point final d’abonné (108) comme étant choisissant un canal de communication de présent avec l’extension de système de no- service de message supportant le point final tification (104) ; d’abonné (108) par l’extension de système de notification (104) au réseau de télécom- le réseau de télécommunication précédent10 munication précédent (102) ; (102) comprenant : et pour choisir un canal de communication de service de message comprenant un ca- un registre précédent de présence sur le nal de communication de message instan- réseau conçu pour enregistrer le point final tané (IM), d’abonné (108) comme étant présent avec 15 dans lequel un répertoire unifié (120) est le réseau de télécommunication précédent adapté pour stocker des informations (102) ; d’abonné, y compris des informations de une passerelle conçue pour accepter une profil d’abonné précédentes et des informa- demande de suivi de trajectoire de vol ve- tions de présence d’abonné précédentes, nant du point final d’abonné (108), la de- 20 dans lequel le répertoire unifié (120) est mande de suivi de trajectoire de vol com- adapté pour communiquer avec une exten- prenant un identifiant de vol et une mise à sion de système de notification (104) par le jour de statut de vol de la compagnie biais d’une passerelle SIP de répertoire uni- aérienne ; fié (122), un point final d’abonné (108) par un module d’orchestration conçu pour : 25 un module de présence sur le réseau (124) et/ou un module d’orchestration de service insérer une entrée de contact de vol as- (114). sociée à l’identifiant de vol dans une liste de contacts existante pour le point 2. Système selon la revendication 1, dans lequel le ser- final d’abonné (108) pour obtenir une 30 veur de présence précédent est en outre conçu pour liste de contacts actualisée ; et mainte- déterminer le canal de communication en : nir un statut de vol répondant à la mise à jour du vol de la compagnie aérienne ; choisissant un canal de communication de ser- vice de message supportant le point final un serveur de présence précédent conçu 35 d’abonné (108) par le biais du réseau de télé- pour : communication précédent (102).

initier la notification du point final 3. Système selon l’une quelconque des revendications d’abonné (108) concernant la liste de précédentes, dans lequel le serveur de présence contact actualisée comprenant l’entrée 40 précédent est en outre conçu pour choisir un canal de contact de vol ; et de communication de service de message compre- initier la communication du statut de vol nant un canal de communication de service de mes- au point final d’abonné (108), dans un sages courts (SMS). message de statut d’objet de contact de vol pour la liste de contacts existan- 45 4. Procédé exécuté par ordinateur pour le suivi de don- te, nées de trajectoire de vol, comprenant : dans lequel le serveur de présence pré- cédent est en outre conçu pour initier l’enregistrement assisté par ordinateur d’un la communication d’un message de no- point final d’abonné (108) comme étant présent tification d’objet de contact de vol con- 50 sur un réseau de télécommunication précédent cernant le statut de vol au point final (102) ; d’abonné, pour déterminer un canal de l’enregistrement assisté par ordinateur du point communication pour communiquer le final d’abonné (108) comme étant présent avec message de notification d’objet de con- une extension de système de notification (104) tact de vol au point final d’abonné (108), 55 au réseau de télécommunication précédent pour envoyer le message de notifica- (102) ; tion d’objet de contact de vol au point l’acceptation d’une demande de suivi de trajec- final d’abonné (108) par le canal de toire de vol comprenant un identifiant de vol ;

18 35 EP 2 154 640 B1 36 l’insertion automatique assistée par ordinateur 5. Procédé selon la revendication 4, comprenant en d’une entrée de contact de vol associée à l’iden- outre : tifiant de vol dans une liste de contacts existante pour le point final d’abonné (108) afin d’obtenir la communication assistée par ordinateur d’un une liste de contacts actualisée ; 5 message de notification d’objet de contact de la notification automatique assistée par ordina- vol concernant le statut de vol au point final teur du point final d’abonné (108) par le biais de d’abonné (108). l’extension de système de notification (104) de la liste de contacts actualisée, y compris l’entrée 6. Procédé selon la revendication 4 ou 5, comprenant de contact de vol ; 10 en outre : la réception assistée par ordinateur d’une mise à jour d’un vol de service de la compagnie aé- détermination automatique assistée par ordina- rienne sur le réseau de télécommunication pré- teur d’un canal de communication pour commu- cédent (102) ; niquer le message de notification d’objet de con- le maintien assisté par ordinateur d’un statut de 15 tact de vol au point final d’abonné (108) et/ou vol répondant à la mise à jour du vol de service comprenant en outre : de la compagnie aérienne ; et la communication automatique assistée par or- l’envoi assisté par ordinateur du message dinateur du statut de vol au point final d’abonné de notification d’objet de contact de vol au (108) dans un message de statut d’objet de con- 20 point final d’abonné (108) par le biais du ca- tact de vol pour la liste de contacts existante, nal de communication. dans lequel le procédé comprend en outre les étapes suivantes 7. Procédé selon l’une quelconque des revendications initiation d’une communication d’un message de précédentes 4 à 6, dans lequel la détermination notification d’objet de contact de vol concernant 25 comprend : le statut de vol au point final d’abonné, détermination d’un canal de communication le choix assisté par ordinateur d’un canal de pour communiquer le message de notification communication de service de message suppor- d’objet de contact de vol au point final d’abonné tant le point final d’abonné (108) par le biais de (108), 30 l’extension de système de notification (104) au envoi du message de notification d’objet de con- réseau de télécommunication précédent (102). tact de vol au point final d’abonné (108) par le biais du canal de communication, et le serveur 8. Procédé selon l’une quelconque des revendications de présence précédent étant en outre conçu précédentes 4 à 7, dans lequel le canal de commu- pour déterminer le canal de communication en : 35 nication de service de message comprend un canal de communication de Message instantané (IM). choisissant un canal de communication de service de message supportant le point final 9. Procédé selon l’une quelconque des revendications d’abonné (108) par le biais de l’extension précédentes 4 à 8, comprenant en outre : de système de notification (104) au réseau 40 de télécommunication précédent (102) ; le choix assisté par ordinateur d’un canal de et communication de service de message suppor- en choisissant un canal de communication tant le point final d’abonné (108) par le biais du de service de message comprenant un ca- réseau de télécommunication précédent (102). nal de communication de Message instan- 45 tané (IM), et 10. Procédé selon l’une quelconque des revendications en stockant, dans un répertoire unifié (120), précédentes 4 à 8, dans lequel le canal de commu- des informations d’abonné, y compris des nication de service de message comprend un canal informations de profil d’abonné précéden- de communication de service de messages courts tes et des informations de présence d’abon- 50 (SMS). né précédentes, dans lequel le répertoire unifié (120) communique avec une exten- 11. Produit de programme informatique comprenant des sion de système de notification (104) par le instructions lisibles par ordinateur, lesquelles amè- biais d’une passerelle SIP de répertoire uni- nent l’ordinateur à exécuter le procédé selon l’une fié (122), un point final d’abonné (108) par 55 ou plusieurs des revendications 4 à 10, lorsqu’elles le biais d’un module de présence sur le ré- sont chargées dans la mémoire d’un ordinateur et seau (124) et/ou un module d’orchestration exécutées par l’ordinateur. de service (114).

19 EP 2 154 640 B1

20 EP 2 154 640 B1

21 EP 2 154 640 B1

22 EP 2 154 640 B1

23 EP 2 154 640 B1

24 EP 2 154 640 B1

25 EP 2 154 640 B1

26 EP 2 154 640 B1

27 EP 2 154 640 B1

28 EP 2 154 640 B1

29 EP 2 154 640 B1

30 EP 2 154 640 B1

31 EP 2 154 640 B1

32 EP 2 154 640 B1

33 EP 2 154 640 B1

34 EP 2 154 640 B1

35 EP 2 154 640 B1

36